Mageia forum

I don't remember how now, but I did such a thing many years ago, I think that was Mandrake 7.2 and 8.1. I could if successful bug-check I don't think I'm qualified, but I have got time. They did both used the same /home partition though I do remember that.

Are you asking how to install mga4 and mga5 in a dual-boot setup?

This is possible if you have (or create) space for mga5 on your hard disk. Boot an mga5 installation disk and proceed, using the free space. (It is possible to shrink one of your mga4 partitions during the installation of mga5 in order to create space.) Personally, I would not use my working home partition in a development version and so would create a separate home partition for mga5.

An alternative, perhaps easier and safer option, is to install mga5 in a VM, using Virtual Box.

Whichever route you choose, it's probably best to wait for beta1 of mga5, which, hopefully, will be released soon. (There are presently some problems with the mga5 installer, which are being worked on.)

You don't need any special qualifications to check for bugs. For example, you could start by making sure that applications, that you are familiar with, run properly in mga5, and report any problems that you encounter.

Jim

I was thinking as I've got my system installed on a SSD and HD, I could put the / and /user partitions perhaps the /var too of both M4 and M5 on the SSD then keep the /swap, /home, and /tmp on the hdd. I remember booting the 7.2 system by floppy, so the system looked and worked like a 8.1 the 7.2 only accessible with the floppy. Now if I made the M4 the visible system and the M5 beta as the hidden that I could boot with as SD or a USB stick.

I had an hour or so free this Sunday morning so I installed M4 and M5 alpha 2 as a dual boot, not quite as I described, as they both appear on the boot list (have I failed to notice the demise of lilo or grub)

Please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks

It's even less as I described as I haven''t got M5 at all as the graphics server didn't install correctly so there was only a black screen after boot. I installed 4.1 in that partition. So in effect I've only achieved placement of the partitions and as lilo isn't offered to boot, I haven't got a hidden partition accessed by a boot device. That's my effort maybe someone else can make a suggestion because I'm still not were I want to be.

So you currently have two Mageia 4 installation, and you want to upgrade the 4.1 one to Mageia 5 / cauldron?

Well kind of, it happens that the 4.1 is at the start of the disc so boots if I leave it (I change the delay to 1 second) it boots without intervention. The 4.0 edition is second and that one I'd like to upgrade I'd even like to boot it with lilo on an SD or small flash drive. Jim said it might be best to wait until the beta is out. On 4.1 everything seems to work, my bluetooth mouse doesn't yet but it has it's probably a pin issue. 4.0 I haven't done the updates and I won't need to.

Then boot the 4.0 installation and remove your urpmi repositories and replace them with cauldron: https://wiki.mageia.org/en/Cauldron#How ... a_Cauldron
Then

Code: Select all

urpmi --auto-update --auto

until it says packages up to date. Then reboot. Voila, Mageia 5.

Well, I tried to do that, but I couldn't make it work. So I waited for the notice that the beta was out downloaded it and tried to install it. So The thing to do is wait for the Beta.

And there were no reasons or error messages that prevented to "make it work" ?

The beta is out already: http://blog.mageia.org/en/2014/11/12/th ... ding-road/

This time it was installed off a flash stick and must have installed the Alfa live in error. my bad

Now the problem is my memory storage is half SSD hosting the /,/usr,and /var and a HDD hosting swap ,/hmoe and /tmp on a re-boot it looses the /ftab settings,but that bug may have been already cured as my /home partition is being installed now.

FWIW, your posts seem really confused.

My posts might be confused but so is my installation, on my equipment M5 doesn't recognise my disks so I cant bug search can't boot have to do a fresh install to do anything .maybe I better wait until the beta II or even the release candidate it was quick, though, mighty quick, I liked that bit.

Now my copy of kmail is disabled, Ascona won't start because the log contains anomalies that may well be due to my swopping between M4 and M5 does anyone know where the log is so I can deleet it.

dwhite wrote:Ascona won't start because the log contains anomalies that may well be due to my swopping between M4 and M5 does anyone know where the log is so I can deleet it.

What is Ascona? Do you maybe mean Akonadi, the storage where KDE PIM applications as kmail or korganizer save messages, events and such stuff?
And could you at least post the error message you see when running it from a terminal?

Apart from that, please reconsider. Within one thread, you jump from topic to topic.
First your problems with partitioning and bootloader, then installation media, then upgrade question - now an application doesn't work.

I think all of them are to do with me doing that

Code: Select all


Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/dwhite64/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-dwhite64.VQyWFH/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3:  SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4:  SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 5.5.40-MariaDB for Linux on x86_64 (Mageia MariaDB Server)


Test 5:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/dwhite64/.local/share/akonadi/db_data/mysql.err'>/home/dwhite64/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/dwhite64/.local/share/akonadi/db_data/mysql.err':
141122 21:07:22 [ERROR] mysqld: Can't lock aria control file '/home/dwhite64/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
141122 21:07:53 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/dwhite64/.local/share/akonadi/db_data/aria_log_control'
141122 21:07:53 [ERROR] Plugin 'Aria' init function returned error.
141122 21:07:53 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
141122 21:07:53 InnoDB: The InnoDB memory heap is disabled
141122 21:07:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141122 21:07:53 InnoDB: Compressed tables use zlib 1.2.8
141122 21:07:53 InnoDB: Using Linux native AIO
141122 21:07:53 InnoDB: Initializing buffer pool, size = 80.0M
141122 21:07:53 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
141122 21:07:53  InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.


Test 6:  SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[client]
default-character-set=utf8


Test 7:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/dwhite64/.local/share/akonadi/mysql.conf'>/home/dwhite64/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/dwhite64/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

[client]
default-character-set=utf8


Test 9:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.11.0


Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  SUCCESS
--------

Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.

Test 13:  SUCCESS
--------

Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.

Test 14:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 15:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
skroogeakonadiresource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'

Test 16:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/dwhite64/.local/share/akonadi/akonadiserver.error'>/home/dwhite64/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/dwhite64/.local/share/akonadi/akonadiserver.error':
"
Sql error: Duplicate entry '1-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x454889]
1: akonadiserver() [0x454b14]
2: /lib64/libc.so.6(+0x349f0) [0x7f3dc992c9f0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f3dc992c969]
4: /lib64/libc.so.6(abort+0x148) [0x7f3dc992df98]
5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f3dcb450ac4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa0) [0x456ac0]
7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f3dcb4eb760]
8: /lib64/libQtCore.so.4(+0x11ae5d) [0x7f3dcb4fae5d]
9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f3dcb503a43]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x628) [0x459718]
11: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f3dcb57569e]
12: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f3dcb55d6ad]
13: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f3dcb56057f]
14: /lib64/libQtCore.so.4(+0x1aa9b3) [0x7f3dcb58a9b3]
15: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f3dc8ff8146]
16: /lib64/libglib-2.0.so.0(+0x48498) [0x7f3dc8ff8498]
17: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f3dc8ff853c]
18: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f3dcb58a275]
19: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f3dcb55c27f]
20: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f3dcb55c575]
21: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f3dcb5617fb]
22: akonadiserver(main+0x1d3) [0x44de33]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f3dc9919c85]
24: akonadiserver() [0x44e546]
]
"


Test 17:  ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/dwhite64/.local/share/akonadi/akonadiserver.error.old'>/home/dwhite64/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/dwhite64/.local/share/akonadi/akonadiserver.error.old':
"
Sql error: Duplicate entry '1-' for key 'PartTable_pimItemIdNameIndex' QMYSQL: Unable to execute query
Query: CREATE UNIQUE INDEX PartTable_pimItemIdNameIndex ON PartTable (pimItemId,name)"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x454889]
1: akonadiserver() [0x454b14]
2: /lib64/libc.so.6(+0x349f0) [0x7f5d16b3c9f0]
3: /lib64/libc.so.6(gsignal+0x39) [0x7f5d16b3c969]
4: /lib64/libc.so.6(abort+0x148) [0x7f5d16b3df98]
5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f5d18660ac4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa0) [0x456ac0]
7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f5d186fb760]
8: /lib64/libQtCore.so.4(+0x11ae5d) [0x7f5d1870ae5d]
9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f5d18713a43]
10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x628) [0x459718]
11: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f5d1878569e]
12: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f5d1876d6ad]
13: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ef) [0x7f5d1877057f]
14: /lib64/libQtCore.so.4(+0x1aa9b3) [0x7f5d1879a9b3]
15: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f5d16208146]
16: /lib64/libglib-2.0.so.0(+0x48498) [0x7f5d16208498]
17: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f5d1620853c]
18: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f5d1879a275]
19: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f5d1876c27f]
20: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f5d1876c575]
21: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b) [0x7f5d187717fb]
22: akonadiserver(main+0x1d3) [0x44de33]
23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5d16b29c85]
24: akonadiserver() [0x44e546]
]
"


Test 18:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 19:  SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

[code/]
I tried to post the results of booting it in a console but there wasn't any

Please guys and girls, place that unreadable pieces of code between [CODE]-tags.
If i can do it, i am sure anyone can!!!!!

Obviously not Isadora Sorry
I've noticed that doing the unusual type of upgrade I do. keeping the home partition the log file accumulating errors disabling kmail

I've managed to get a fully working installation of 5, Akonadi works I had to upgrade up from M4, but I didn't delete the orphans, it is a beta One doesn't' expect it to work!!!

When trying to update M5 I'm getting an error that error says the mirror I'm using hasn't up to date packages. Which repository should I be using? I'm thinking one in France.

Check this page to find an up-to-date mirror:
http://mirrors.mageia.org/status

Jim