Can't start mageia control center [Solved]

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

Can't start mageia control center [Solved]

Postby RagingRaven » Aug 10th, '15, 17:08

When I try to start Mageia Control Center from the task bar (KDE) or from the start menu, nothing happens.
I also tried starting MCC from a root Konsole using 'mcc', but I get: Segmentation fault
I also get a segmentation fault when running drakconf from a root konsole.

I wanted to upgrade from mageia 4 to 5 so before starting the upgrade process I updated all packages.
I then started the upgrade process, but it failed due to insufficient space on /boot (which I have for raid, but is not important right now).
I only noticed it not working after trying the upgrade when I wanted to remove some kernels, so It could be both the upgrade process or the package updates that have caused this.

Before trying the upgrade it used to work/start fine.
What could be causing this problem?
Last edited by RagingRaven on Aug 18th, '15, 09:13, edited 1 time in total.
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby doktor5000 » Aug 10th, '15, 17:52

An impartial upgrade? One of the first packages is perl-URPM, perl and rpmdrake, drakconf comes much later.
Please continue via https://wiki.mageia.org/en/Mageia_5_Rel ... _.28CLI.29
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18058
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Can't start mageia control center

Postby RagingRaven » Aug 11th, '15, 09:27

That's probable, but in order to continue the installation I need to make room on /boot and I believe for that I need to remove some older kernels.
I'm not really sure how to do this without the software management tool in MCC.

I'm guessing I could do this with urpme, but I'm not really sure what the older/oldest kernels are called?

After that I can follow the urpmi cli method.

By the way in the 'Please note!' section it says to test with 'urpmi --replacefiles --auto-update --auto --download-all --test' and if everything looks ok install with the same command: 'urpmi --replacefiles --auto-update --auto --download-all --test', but I'm guessing to actually install I would have to remove the --test part?
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby RagingRaven » Aug 11th, '15, 13:41

I did some more searching and was able to remove a few older kernels with urpme.
I then followed the uprmi cli method to upgrade and so far everything appears to have updated correctly.

MCC also appears to be functioning normally again so that's good as well.

a few question I have left:
Can/should I run 'urpme --auto-orphans' as the last output from the upgrade said there were a lot of orphans.
After upgrading I got a notification saying there was a new version of Mageia distribution, does that mean something went wrong? Should I ignore that message or should I follow that wizard just to make sure everything went ok?
Is there any point in keeping 1-2 mga4 kernels or won't they work at all? Same question for any other mga4 packages.

Thank you for your help
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby doktor5000 » Aug 11th, '15, 21:02

RagingRaven wrote:I'm guessing I could do this with urpme, but I'm not really sure what the older/oldest kernels are called?

You seem to have removed already sufficient older kernels for the upgrade to complete, but anyways:
Code: Select all
rpm -qa | grep ^kernel | sort -V

Will show you all the installed kernels including their version number. Version number is compared alphanumerically, from left to right.
Higher number, higher version. Letters are "higher" then numbers.
Code: Select all
┌─[doktor5000@Mageia5]─[20:13:27]─[~]
└──╼ rpm -qa | grep ^kernel | sort -V
kernel-desktop-3.19.3-1.mga5-1-1.mga5
kernel-desktop-3.19.4-1.mga5-1-1.mga5
kernel-desktop-3.19.4-2.mga5-1-1.mga5
kernel-desktop-3.19.6-1.mga5-1-1.mga5
kernel-desktop-3.19.6-2.mga5-1-1.mga5
kernel-desktop-3.19.7-1.mga5-1-1.mga5
kernel-desktop-3.19.8-1.mga5-1-1.mga5
kernel-desktop-3.19.8-2.mga5-1-1.mga5
kernel-desktop-3.19.8-3.mga5-1-1.mga5
kernel-desktop-devel-3.19.3-1.mga5-1-1.mga5
kernel-desktop-devel-3.19.4-1.mga5-1-1.mga5
kernel-desktop-devel-3.19.4-2.mga5-1-1.mga5
kernel-desktop-devel-3.19.6-1.mga5-1-1.mga5
kernel-desktop-devel-3.19.6-2.mga5-1-1.mga5
kernel-desktop-devel-3.19.7-1.mga5-1-1.mga5
kernel-desktop-devel-3.19.8-1.mga5-1-1.mga5
kernel-desktop-devel-3.19.8-2.mga5-1-1.mga5
kernel-desktop-devel-3.19.8-3.mga5-1-1.mga5
kernel-desktop-devel-latest-3.19.8-3.mga5
kernel-desktop-latest-3.19.8-3.mga5
kernel-firmware-20150309-1.mga5
kernel-firmware-nonfree-20150510-1.mga5.nonfree
kernel-userspace-headers-3.19.8-3.mga5

Also the -latest metapackages will tell you the version number of the newest installed kernel
- although you need to pay attention that it won't tell you if you already booted from that kernel, e.g. if you've not rebooted since you installed last kernel update.
uname -r will show you the version of the currently running kernel

You can simply uninstall some of the older kernel packages.
You shall NOT remove the -latest packages, kernel-firmware* or kernel-userspace-headers packages

Hope that helps, if something is still unclear just ask.

RagingRaven wrote:By the way in the 'Please note!' section it says to test with 'urpmi --replacefiles --auto-update --auto --download-all --test' and if everything looks ok install with the same command: 'urpmi --replacefiles --auto-update --auto --download-all --test', but I'm guessing to actually install I would have to remove the --test part?

Good catch, and yes - I've adjusted that. FWIW, you could also have corrected that, don't be afraid ;) It's a wiki, and the important pages are under watch, so "wrong" edits will usually be corrected pretty quickly.

RagingRaven wrote:a few question I have left:
Can/should I run 'urpme --auto-orphans' as the last output from the upgrade said there were a lot of orphans.

No, better not. Please post the output of urpmq --auto-orphans here and we can go through it.
For the dangers in running urpme --auto-orphans please carefully read through https://wiki.mageia.org/en/Removing_packages

A better method of "cleaning up" is using urpmq --not-available, which will show all
packages that are not available from the currently configured repos. This will usually show up
old libraries, or 3rd party packages and such. But better enable the nonfree and tainted repos before you do that ;)


RagingRaven wrote:After upgrading I got a notification saying there was a new version of Mageia distribution, does that mean something went wrong? Should I ignore that message or should I follow that wizard just to make sure everything went ok?
Is there any point in keeping 1-2 mga4 kernels or won't they work at all? Same question for any other mga4 packages.

For the upgrade notification, that is weird. Did you run
Code: Select all
urpmi --auto-update
after the upgrade again?
Please also post the content of your /etc/product.id

You can keep 1 or 2 mga4 kernels, but if the mga5 kernels work, there's not much point in that, better run later kernels.
But all the other mga4 packages should be kept, as not all of them have been rebuilt for mga5, some for technical reasons.
Better stick to the hint above with urpmq --not-available as that will also cover all those mga4 packages which are not available from the current repos.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18058
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Can't start mageia control center

Postby RagingRaven » Aug 12th, '15, 11:05

@dokter thanks for your reply.

Yes I allready found the info needed in some other topic about older kernels, i used
rpm -qa | grep kernel | sort, so almost the same and also used uname -a to find out the running kernel.

doktor5000 wrote:FWIW, you could also have corrected that, don't be afraid ;) It's a wiki, and the important pages are under watch, so "wrong" edits will usually be corrected pretty quickly.

Ah didn't know that, usually you need to have some priviledges first to edit wiki's.

doktor5000 wrote:You can simply uninstall some of the older kernel packages.
You shall NOT remove the -latest packages, kernel-firmware* or kernel-userspace-headers packages

I allready removed some, but I was wondering if there is any point in keeping 1-2 mga4 kernels, but you allready addressed this further in your post.

doktor5000 wrote:No, better not. Please post the output of urpmq --auto-orphans here and we can go through it.
For the dangers in running urpme --auto-orphans please carefully read through https://wiki.mageia.org/en/Removing_packages

Yeah I read that topic, that's exactly why I asked if I should run it, In the past I usually just ran auto-orphans, but after reading that I was hesitant to do so again.
Output given:
Code: Select all
avahi
avalon-framework
avalon-logkit
clutter-gtk-i18n
clutter-i18n
cogl-i18n
cups-filesystem
cups-filters
dleyna-server
gnome-desktop3
gnome-python
gnome-python-bonobo
gnome-python-canvas
gnome-python-desktop
gnome-python-gnomekeyring
grilo
grilo-plugins
gstreamer0.10-dirac
gstreamer0.10-mms
gstreamer0.10-plugins-good
gstreamer0.10-resindvd
gstreamer0.10-xvid
gstreamer1.0-a52dec
gstreamer1.0-dv
gstreamer1.0-farstream
gstreamer1.0-gstclutter
gstreamer1.0-mms
gstreamer1.0-mpeg
gstreamer1.0-plugins-bad
gstreamer1.0-plugins-good
gstreamer1.0-plugins-ugly
gstreamer1.0-rtmp
gstreamer1.0-soundtouch
gstreamer1.0-soup
gstreamer1.0-x264
gupnp-av-common
gvfs
icu-data
kwallet
lcms2
lib64OpenEXR20
lib64SDL_gfx14
lib64SDL_sound1.0_1
lib64art_lgpl2
lib64ass4
lib64avahi-core7
lib64avfilter3
lib64avformat55
lib64bonoboui2_0
lib64boost_program_options1.54.0
lib64boost_signals1.54.0
lib64boost_system1.54.0
lib64boost_thread1.54.0
lib64camel1.2_45
lib64cfitsio1
lib64chromaprint0
lib64clutter-gst2.0_0
lib64clutter-gtk1.0_0
lib64clutter1.0_0
lib64cmis0.3_3
lib64cogl-pango1
lib64cogl-pango20
lib64cogl15
lib64cogl20
lib64cups-filters1
lib64dbusmenuqt52
lib64digikamcore3
lib64digikamdatabase3
lib64dirac0
lib64directfb1.7_0
lib64dleyna-connector-dbus
lib64dleyna-core1.0_3
lib64dmapsharing3.0_2
lib64ebackend1.2_7
lib64ebook-contacts1.2_0
lib64ebook1.2_14
lib64ecal1.2_16
lib64edata-book1.2_20
lib64edata-cal1.2_23
lib64edataserver1.2_18
lib64evdev1
lib64exempi3
lib64exiv2_12
lib64farstream0.2_2
lib64gail18
lib64girepository-gir2.0
lib64gjs-gir1.0
lib64gjs0
lib64glamor0
lib64glew1.10
lib64gmime2.6_0
lib64gnome-desktop3_10
lib64gnome2_0
lib64gnomecanvas2_0
lib64gnomeui2_0
lib64gom1.0_0
lib64gpsd20
lib64grilo0.2_1
lib64grlnet0.2_0
lib64grlpls0.2_0
lib64gstbadbase1.0_0
lib64gstbadvideo1.0_0
lib64gstbasecamerabinsrc1.0_0
lib64gstbasevideo0.10_0
lib64gstcodecparsers1.0_0
lib64gstgl1.0_0
lib64gstmpegts1.0_0
lib64gstphotography1.0_0
lib64gsturidownloader1.0_0
lib64gstwayland1.0_0
lib64gupnp-av1.0_2
lib64gupnp-dlna2.0_3
lib64hd20
lib64icu52
lib64ijs1
lib64ilmbase10
lib64input5
lib64iptcdata0
lib64iso9660_8
lib64kactivities_models1
lib64kdcraw22
lib64kdepim-copy4
lib64kf5notifications5
lib64kf5wallet5
lib64kf5walletbackend55
lib64kface2
lib64kgeomap1
lib64kipiplugins3
lib64kolabxml0
lib64kpeople0
lib64kpeoplewidgets0
lib64ktpcommoninternalsprivate6
lib64ktploggerprivate6
lib64ktpmodelsprivate6
lib64ktpwidgetsprivate6
lib64lcms1
lib64magick-6Q16_1
lib64marblewidget16
lib64mediaart1.0_0
lib64mediastreamer3
lib64mesaopenvg1
lib64mikmod3
lib64mimic0
lib64mms0
lib64mozjs17
lib64mozjs24
lib64mtdev1
lib64mwaw1
lib64nm-glib4
lib64nm-util2
lib64odfgen0
lib64okularcore3
lib64openal1
lib64orcus0.6_0
lib64packagekit-glib16
lib64peas-gir1.0
lib64peas-gtk1.0_0
lib64peas1.0_0
lib64phonon4qt5_4
lib64plist1
lib64podofo0
lib64poppler43
lib64postproc52
lib64pyglib-gi2.0_0
lib64python3.3
lib64qpdf13
lib64qtdesigner5
lib64quvi0.9_0.9.3
lib64quvi0.9_0.9.4
lib64rtmp0
lib64sdl2.0_0
lib64seed0
lib64shout3
lib64swresample0
lib64swscaler2
lib64totem-gir1.0
lib64totem-plparser-gir1.0
lib64totem-plparser-mini18
lib64totem-plparser18
lib64totem0
lib64tracker0.16_0
lib64tracker1.0_0
lib64upower-glib1
lib64visio0
lib64wayland-egl1
lib64webp4
lib64wnck1_22
lib64wpd0.9_9
lib64wpg0.2_2
lib64wps0.2_2
lib64xcb-sync0
lib64xine1
lib64xres1
lib64zbar0
lib64zeitgeist2.0_0
libbonoboui
libdvdcss2
libgnome2
libgnome2-schemas
libgnomecanvas
libgnomeui2
libiptcdata-i18n
libpeas-data
libquicktime
libquicktime-dv
libquicktime-x264
libquicktime0
libquvi-scripts
libwnck
log4j
lua5.1
mpage
mpeg2dec
openal
phonon4qt5
php-pear-Mail_mimeDecode
php-pear-SOAP
poppler
pyorbit
python-cups
python-curl
python-dbus
python-notify
python-pyxdg
python-smbc
raptor2
soprano-plugin-redland
task-codec-video
tomcat-servlet-3.0-api
totem
totem-pl-parser
totem-pl-parser-i18n
usbmuxd
x264
xalan-j2
xerces-j2
xine-plugins
xml-commons-apis
xml-commons-resolver


Output of urpmq --not-available:
Code: Select all
lib64gpsd20-3.9-3.mga4.x86_64
lib64avformat55-2.0.7-1.mga4.tainted.x86_64
lib64digikamcore3-3.5.0-3.2.mga4.x86_64
lib64wps0.2_2-0.2.9-4.mga4.x86_64
lib64plist1-1.10-2.mga4.x86_64
lib64boost_system1.54.0-1.54.0-8.mga4.x86_64
lib64ktpcommoninternalsprivate6-0.7.0-1.mga4.x86_64
lib64kipiplugins3-3.5.0-3.2.mga4.x86_64
lib64edataserver1.2_18-3.10.2-1.2.mga4.x86_64
lib64poppler43-0.24.3-2.mga4.x86_64
lib64python3.3-3.3.2-13.5.mga4.x86_64
lib64swresample0-2.0.7-1.mga4.tainted.x86_64
lib64kolabxml0-0.8.4-5.mga4.x86_64
lib64iso9660_8-0.90-2.mga4.x86_64
lib64kface2-3.5.0-3.2.mga4.x86_64
lib64pyglib-gi2.0_0-3.10.2-1.mga4.x86_64
lib64kdcraw22-4.11.4-2.mga4.x86_64
lib64webp4-0.3.1-2.mga4.x86_64
lib64kactivities_models1-4.12.5-1.mga4.x86_64
lib64directfb1.7_0-1.7.0-2.1.mga4.x86_64
lib64ktploggerprivate6-0.7.0-1.mga4.x86_64
lib64camel1.2_45-3.10.2-1.2.mga4.x86_64
kernel-desktop-3.14.43-1.mga4-1-1.mga4.x86_64
lib64systemd-login0-208-10.5.mga4.x86_64
lib64avcodec55-2.0.7-1.mga4.tainted.x86_64
lib64okularcore3-4.12.5-1.1.mga4.x86_64
lib64upower-glib1-0.9.23-1.1.mga4.x86_64
lib64ebackend1.2_7-3.10.2-1.2.mga4.x86_64
lib64marblewidget16-4.11.4-1.mga4.x86_64
lib64boost_iostreams1.54.0-1.54.0-8.mga4.x86_64
lib64marblewidget17-4.12.5-1.1.mga4.x86_64
lib64evdev1-0.4-4.mga4.x86_64
lib64avfilter3-2.0.7-1.mga4.tainted.x86_64
lib64odfgen0-0.0.2-4.mga4.x86_64
lib64mediastreamer3-3.6.1-4.mga4.x86_64
kernel-desktop-3.14.32-1.mga4-1-1.mga4.x86_64
lib64boost_thread1.54.0-1.54.0-8.mga4.x86_64
lib64ktpmodelsprivate6-0.7.0-1.mga4.x86_64
lib64ecal1.2_16-3.10.2-1.2.mga4.x86_64
lib64orcus0.6_0-0.5.1-9.mga4.x86_64
lib64ilmbase10-2.0.1-3.mga4.x86_64
lib64llvm3.3-3.3-2.1.mga4.x86_64
lib64magick-6Q16_1-6.8.7.0-2.3.mga4.x86_64
lib64cdio14-0.90-2.mga4.x86_64
lib64ktpwidgetsprivate6-0.7.0-1.mga4.x86_64
lib64ebook-contacts1.2_0-3.10.2-1.2.mga4.x86_64
lib64hd20-20.1-3.mga4.x86_64
lib64cfitsio1-3.350-4.mga4.x86_64
lib64wpd0.9_9-0.9.9-2.mga4.x86_64
lib64cogl15-1.16.0-2.mga4.x86_64
lib64postproc52-2.0.7-1.mga4.tainted.x86_64
lib64tracker0.16_0-0.16.2-5.mga4.x86_64
lib64mesaopenvg1-10.0.5-1.1.mga4.tainted.x86_64
lib64glew1.10-1.10.0-2.mga4.x86_64
lib64x264_133-0.133-0.20130823.stable.2.mga4.tainted.x86_64
lib64boost_program_options1.54.0-1.54.0-8.mga4.x86_64
lib64xcb-sync0-1.9.1-2.1.mga4.x86_64
lib64ass4-0.10.1-3.mga4.x86_64
lib64kpeoplewidgets0-0.1.0-1.mga4.x86_64
lib64ebook1.2_14-3.10.2-1.2.mga4.x86_64
lib64raw_r9-0.15.4-2.1.mga4.x86_64
lib64folderarchive4-4.12.5-1.mga4.x86_64
lib64cmis0.4_4-0.4.1-2.mga4.x86_64
lib64kgeomap1-3.5.0-3.2.mga4.x86_64
lib64cogl-pango1-1.16.0-2.mga4.x86_64
lib64boost_signals1.54.0-1.54.0-8.mga4.x86_64
lib64SDL_gfx14-2.0.24-3.mga4.x86_64
lib64boost_date_time1.54.0-1.54.0-8.mga4.x86_64
lib64quvi0.9_0.9.3-0.9.3-2.mga4.x86_64
lib64systemd-id128_0-208-10.5.mga4.x86_64
lib64systemd-journal0-208-10.5.mga4.x86_64
lib64glamor0-0.5.1-2.mga4.x86_64
lib64wxgtku2.9_5-2.9.5-2.mga4.x86_64
lib64packagekit-glib16-0.8.14-3.1.mga4.x86_64
lib64podofo0-0.9.2-2.mga4.x86_64
lib64swscaler2-2.0.7-1.mga4.tainted.x86_64
lib64wpg0.2_2-0.2.2-2.mga4.x86_64
lib64systemd-daemon0-208-10.5.mga4.x86_64
lib64icu52-52.1-2.5.mga4.x86_64
lib64kpeople0-0.1.0-1.mga4.x86_64
lib64edata-book1.2_20-3.10.2-1.2.mga4.x86_64
lib64avutil52-2.0.7-1.mga4.tainted.x86_64
lib64mwaw1-0.1.11-2.mga4.x86_64
lib64OpenEXR20-2.0.1-2.mga4.x86_64
lib64visio0-0.0.31-3.mga4.x86_64
icu-data-52.1-2.5.mga4.noarch
lib64exiv2_12-0.23-4.mga4.x86_64
lib64rtmp0-2.4-0.git20111228.5.mga4.x86_64
lib64digikamdatabase3-3.5.0-3.2.mga4.x86_64
lib64edata-cal1.2_23-3.10.2-1.2.mga4.x86_64
lib64protobuf-c0-0.15-3.mga4.x86_64


doktor5000 wrote:For the upgrade notification, that is weird. Did you run urpmi --auto-update after the upgrade again?

Yes I did, 2 times in fact and also went to MCC and 'update your system' to see if there were any packages needing updates, but no packages were found.
I just checked again and today there are a few updates, but I'm guessing that's just coincidence:
Code: Select all
firefox
firefox-en_GB
firefox-en_ZA
flash-player-plugin
lib64nss3
lib64user1
libuser
nss
rootcerts
rootcerts-java


Contents of /etc/product.id:
Code: Select all
vendor=Mageia.Org,distribution=Mageia,type=Basic,version=5,branch=Official,release=5,arch=x86_64,product=Default


Screenshot:
dis_upgrade.png
Distribution upgrade message
dis_upgrade.png (868.11 KiB) Viewed 2466 times
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby RagingRaven » Aug 15th, '15, 11:47

After a few reboots I've not seen the upgrade message anymore, so I'm guessing it was just a fluke.
If/when it comes back I'll let you know.

So all that remains is orphans, how can I tell which orphans are safe to remove and which are not, is this just a matter of experience or is there some way/command to figure this out?
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby doktor5000 » Aug 15th, '15, 21:04

RagingRaven wrote:So all that remains is orphans, how can I tell which orphans are safe to remove and which are not, is this just a matter of experience or is there some way/command to figure this out?

That is just a matter of experience. From your output, if you would remove all those "orphans" you would probably break cups (printing), gnome desktop, remove many vide/audio codecs for everything that uses gstreamer framework,
digikam, evolution, all GTK2 stuff, totem, dvd playback, and some more probably.

E.g. you would want to mark task-codec-video and all the packages it suggested mark as "un-orphaned".urpme $(urpmq --not-available)
You can also selectively remove orphans or mark them not orphaned via qt4urpm, which is in the Mageia repos, and created by a contributor.
Explained shortly at https://wiki.mageia.org/en/Removing_pac ... ge_Orphans

An option that looks much better is look at what urpmi would want to remove with
Code: Select all
urpme --test $(urpmq --not-available)

and check the output if it wants to remove some essential stuff.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18058
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Can't start mageia control center

Postby RagingRaven » Aug 17th, '15, 12:31

Ok seeing as knowing which packages to remove and which to mark as un-orphaned is a matter of experience and I don't have the required experience, would it be better to mark all as un-orphaned or leave things as is? I'm guessing it doesn't really matter other than 'urpme --auto-orphans' showing no orphans.

By the way urpme --test $(urpmq --not-available) output:
Code: Select all
testing removal of icu-data-52.1-2.5.mga4.noarch kernel-desktop-3.14.32-1.mga4-1-1.mga4.x86_64 kernel-desktop-3.14.43-1.mga4-1-1.mga4.x86_64 lib64OpenEXR20-2.0.1-2.mga4.x86_64 lib64SDL_gfx14-2.0.24-3.mga4.x86_64 lib64ass4-0.10.1-3.mga4.x86_64 lib64avcodec55-2.0.7-1.mga4.tainted.x86_64 lib64avfilter3-2.0.7-1.mga4.tainted.x86_64 lib64avformat55-2.0.7-1.mga4.tainted.x86_64 lib64avutil52-2.0.7-1.mga4.tainted.x86_64 lib64boost_date_time1.54.0-1.54.0-8.mga4.x86_64 lib64boost_iostreams1.54.0-1.54.0-8.mga4.x86_64 lib64boost_program_options1.54.0-1.54.0-8.mga4.x86_64 lib64boost_signals1.54.0-1.54.0-8.mga4.x86_64 lib64boost_system1.54.0-1.54.0-8.mga4.x86_64 lib64boost_thread1.54.0-1.54.0-8.mga4.x86_64 lib64camel1.2_45-3.10.2-1.2.mga4.x86_64 lib64cdio14-0.90-2.mga4.x86_64 lib64cfitsio1-3.350-4.mga4.x86_64 lib64cmis0.4_4-0.4.1-2.mga4.x86_64 lib64cogl-pango1-1.16.0-2.mga4.x86_64 lib64cogl15-1.16.0-2.mga4.x86_64 lib64digikamcore3-3.5.0-3.2.mga4.x86_64 lib64digikamdatabase3-3.5.0-3.2.mga4.x86_64 lib64directfb1.7_0-1.7.0-2.1.mga4.x86_64 lib64ebackend1.2_7-3.10.2-1.2.mga4.x86_64 lib64ebook-contacts1.2_0-3.10.2-1.2.mga4.x86_64 lib64ebook1.2_14-3.10.2-1.2.mga4.x86_64 lib64ecal1.2_16-3.10.2-1.2.mga4.x86_64 lib64edata-book1.2_20-3.10.2-1.2.mga4.x86_64 lib64edata-cal1.2_23-3.10.2-1.2.mga4.x86_64 lib64edataserver1.2_18-3.10.2-1.2.mga4.x86_64 lib64evdev1-0.4-4.mga4.x86_64 lib64exiv2_12-0.23-4.mga4.x86_64 lib64folderarchive4-4.12.5-1.mga4.x86_64 lib64glamor0-0.5.1-2.mga4.x86_64 lib64glew1.10-1.10.0-2.mga4.x86_64 lib64gpsd20-3.9-3.mga4.x86_64 lib64hd20-20.1-3.mga4.x86_64 lib64icu52-52.1-2.5.mga4.x86_64 lib64ilmbase10-2.0.1-3.mga4.x86_64 lib64iso9660_8-0.90-2.mga4.x86_64 lib64kactivities_models1-4.12.5-1.mga4.x86_64 lib64kdcraw22-4.11.4-2.mga4.x86_64 lib64kface2-3.5.0-3.2.mga4.x86_64 lib64kgeomap1-3.5.0-3.2.mga4.x86_64 lib64kipiplugins3-3.5.0-3.2.mga4.x86_64 lib64kolabxml0-0.8.4-5.mga4.x86_64 lib64kpeople0-0.1.0-1.mga4.x86_64 lib64kpeoplewidgets0-0.1.0-1.mga4.x86_64 lib64ktpcommoninternalsprivate6-0.7.0-1.mga4.x86_64 lib64ktploggerprivate6-0.7.0-1.mga4.x86_64 lib64ktpmodelsprivate6-0.7.0-1.mga4.x86_64 lib64ktpwidgetsprivate6-0.7.0-1.mga4.x86_64 lib64llvm3.3-3.3-2.1.mga4.x86_64 lib64magick-6Q16_1-6.8.7.0-2.3.mga4.x86_64 lib64marblewidget16-4.11.4-1.mga4.x86_64 lib64marblewidget17-4.12.5-1.1.mga4.x86_64 lib64mediastreamer3-3.6.1-4.mga4.x86_64 lib64mesaopenvg1-10.0.5-1.1.mga4.tainted.x86_64 lib64mwaw1-0.1.11-2.mga4.x86_64 lib64odfgen0-0.0.2-4.mga4.x86_64 lib64okularcore3-4.12.5-1.1.mga4.x86_64 lib64orcus0.6_0-0.5.1-9.mga4.x86_64 lib64packagekit-glib16-0.8.14-3.1.mga4.x86_64 lib64plist1-1.10-2.mga4.x86_64 lib64podofo0-0.9.2-2.mga4.x86_64 lib64poppler43-0.24.3-2.mga4.x86_64 lib64postproc52-2.0.7-1.mga4.tainted.x86_64 lib64protobuf-c0-0.15-3.mga4.x86_64 lib64pyglib-gi2.0_0-3.10.2-1.mga4.x86_64 lib64python3.3-3.3.2-13.5.mga4.x86_64 lib64quvi0.9_0.9.3-0.9.3-2.mga4.x86_64 lib64raw_r9-0.15.4-2.1.mga4.x86_64 lib64rtmp0-2.4-0.git20111228.5.mga4.x86_64 lib64swresample0-2.0.7-1.mga4.tainted.x86_64 lib64swscaler2-2.0.7-1.mga4.tainted.x86_64 lib64systemd-daemon0-208-10.5.mga4.x86_64 lib64systemd-id128_0-208-10.5.mga4.x86_64 lib64systemd-journal0-208-10.5.mga4.x86_64 lib64systemd-login0-208-10.5.mga4.x86_64 lib64tracker0.16_0-0.16.2-5.mga4.x86_64 lib64upower-glib1-0.9.23-1.1.mga4.x86_64 lib64visio0-0.0.31-3.mga4.x86_64 lib64webp4-0.3.1-2.mga4.x86_64 lib64wpd0.9_9-0.9.9-2.mga4.x86_64 lib64wpg0.2_2-0.2.2-2.mga4.x86_64 lib64wps0.2_2-0.2.9-4.mga4.x86_64 lib64wxgtku2.9_5-2.9.5-2.mga4.x86_64 lib64x264_133-0.133-0.20130823.stable.2.mga4.tainted.x86_64 lib64xcb-sync0-1.9.1-2.1.mga4.x86_64
Removal is possible

But again my experience isn't great enough to know what most packages do.
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center

Postby doktor5000 » Aug 17th, '15, 20:32

Well, hardest are the library packages. Better don't care about it and mark all orphans as non-orphan via
https://wiki.mageia.org/en/Removing_pac ... n-orphaned

And then, please finally mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks :)
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18058
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Can't start mageia control center

Postby RagingRaven » Aug 18th, '15, 09:13

Will do, thank you for your time and effort :)
User avatar
RagingRaven
 
Posts: 60
Joined: Aug 18th, '14, 16:40
Location: Oud-Beijerland, Near Rotterdam, The Netherlands

Re: Can't start mageia control center [Solved]

Postby lightblue » Oct 10th, '15, 16:28

Hi,
I have this issue but nothing has fixed it yet. i can't start MCC, unless i restart my system.
Do i have to search for orphans and non orphans packages and so?
User avatar
lightblue
 
Posts: 45
Joined: Jun 10th, '14, 20:52

Re: Can't start mageia control center [Solved]

Postby doktor5000 » Oct 10th, '15, 17:49

Please note that the last reply in this thread was nearly 2 months ago. For your issue please read viewtopic.php?p=59728#p59728 and reply there.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18058
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest