Lotus 9.0.X sur mageia 4 64bits KDE 4 crash de Lotus
willyk2 Membre non connecté
-
- Voir le profil du membre willyk2
- Inscrit le : 08/12/2009
Je me bagarre, pour faire fonctionner Lotus notes 9.0.x sur Mageia 4 64 bits KDE 4 :
Voici les messages d'erreur que j'ai dans la console au plantage :
Caché :
/opt/ibm/notes/framework/../notes %F
[01699:00002-4068419712] GetSystemMenu() returned a null handle
[01699:00002-4068419712] 17/02/2015 09:55:48,22 DeskClientOpenInt> Calling CreateProgramRCP pszRCPCmdLine[/authenticate ] bDeskProvisioningRestart [0]
[01699:00002-4068419712] 17/02/2015 09:55:48,22 DeskClientOpenInt> Executed CreateProgramRCP
[01728:00002-4149880576] 17/02/2015 09:55:54,12 InitGlobalProcessInfo> PID [1728]!= [0]
libpng warning: Application built with libpng-1.2.31 but running with 1.6.16
libpng warning: Application built with libpng-1.2.31 but running with 1.6.16
[01699:00002-4068419712] 17/02/2015 09:56:01 Connecté au serveur PARMAIL102/SERVERS/GROUP
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration démarré
[02088:00002-4101208576] 17/02/2015 09:56:15 Initialisation de Dynamic Client Configuration
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations de politique
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration : application des signets de politique
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations sur le site
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,24 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,24 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,33 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,33 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Arrêt de Dynamic Client Configuration
(pid 1699 ) X lib error (11:BadAlloc (insufficient resources for operation)) occurs
(pid 1699 ) X lib error (4:BadPixmap (invalid Pixmap parameter)) occurs
(pid 1699 ) X lib error (4:BadPixmap (invalid Pixmap parameter)) occurs
[01699:00002-4068419712] (MailSendNoteActual)- after lookup Total recipients 1
Unhandled exception
Type=Segmentation error vmState=0xf6c98480
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
Handler1=F72C5CDA Handler2=F729B021 InaccessibleAddress=00000004
EDI=F7326760 ESI=09059690 EAX=00000004 EBX=E2395000
ECX=00000001 EDX=E0F4BF94
EIP=E235BC5E ES=002B DS=002B ESP=FF921744
EFlags=00010202 CS=0023 SS=002B EBP=FF92177C
Module=/lib/libgobject-2.0.so.0
Module_base_address=E2345000 Symbol=g_object_get_qdata
Symbol_address=E235BC40
Target=2_40_20130704_155156 (Linux 3.14.27-desktop-1.mga4)
CPU=x86 (4 logical CPUs) (0x1eace2000 RAM)
----------- Stack Backtrace -----------
(0xF728EB76 [libj9prt24.so+0xbb76])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF728EC09 [libj9prt24.so+0xbc09])
(0xF728ED2C [libj9prt24.so+0xbd2c])
(0xF728E9A8 [libj9prt24.so+0xb9a8])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF728EA1C [libj9prt24.so+0xba1c])
(0xF72C6AA6 [libj9vm24.so+0xfaa6])
(0xF72C6726 [libj9vm24.so+0xf726])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF72C5F0B [libj9vm24.so+0xef0b])
(0xF72C5D5E [libj9vm24.so+0xed5e])
(0xF729B199 [libj9prt24.so+0x18199])
__kernel_rt_sigreturn+0x0 (0xF77B2410 [linux-gate.so.1+0x410])
(0xE0F4C016 [<unknown>+0x0])
JVM_InvokeMethod+0x92 (0xF73899C4 [libjvm.so+0xa9c4])
JVM_InvokeMethod+0x58 (0xF7797398 [libjvm.so+0x3398])
Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x34 (0xE39C9804 [libjava.so+0x12804])
(0xE6631BF7 [<unknown>+0x0])
JVM_InvokeMethod+0x92 (0xF73899C4 [libjvm.so+0xa9c4])
JVM_InvokeMethod+0x58 (0xF7797398 [libjvm.so+0x3398])
Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x34 (0xE39C9804 [libjava.so+0x12804])
(0xE6631BF7 [<unknown>+0x0])
(0xF72D5D85 [libj9vm24.so+0x1ed85])
(0xF730BABD [libj9vm24.so+0x54abd])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF730BB9B [libj9vm24.so+0x54b9b])
(0xF72D637D [libj9vm24.so+0x1f37d])
(0xF72D43C4 [libj9vm24.so+0x1d3c4])
startJavaJNI+0x418 (0xF77AB3D9 [eclipse_1407.so+0x83d9])
startJavaVM+0x24 (0xF77AC878 [eclipse_1407.so+0x9878])
run+0x59d (0xF77A614B [eclipse_1407.so+0x314b])
(0x080490EE [notes2+0x10ee])
__libc_start_main+0xf3 (0xF75BDB33 [libc.so.6+0x19b33])
---------------------------------------
JVMDUMP039I Traitement de l'événement de vidage "gpf", détails "" à 2015/02/17 09:58:10 - Veuillez patienter.
JVMDUMP032I La machine virtuelle Java a demandé un vidage System en utilisant '/home/will/lotus/notes/data/workspace/logs/core.20150217.095810.1728.0001.dmp' en réponse à un événement
JVMDUMP010I Vidage System écrit dans /home/will/lotus/notes/data/workspace/logs/core.20150217.095810.1728.0001.dmp
JVMDUMP032I La machine virtuelle Java a demandé un vidage Java en utilisant '/home/will/lotus/notes/data/workspace/logs/javacore.20150217.095810.1728.0002.txt' en réponse à un événement
JVMDUMP010I Vidage Java écrit dans /home/will/lotus/notes/data/workspace/logs/javacore.20150217.095810.1728.0002.txt
JVMDUMP032I La machine virtuelle Java a demandé un vidage Snap en utilisant '/home/will/lotus/notes/data/workspace/logs/Snap.20150217.095810.1728.0003.trc' en réponse à un événement
JVMDUMP009I Le vidage Snap est indisponible
JVMDUMP013I Evénement de vidage traité "gpf", détails "".
[01699:00015-3602619200] Thread=[01699:00015-3602619200]
[01699:00015-3602619200] Stack base=0xD6BB92C8, Stack size = 13384 bytes
[01699:00015-3602619200] PANIC: The notes2 process (pid=1728) exited unexpectedly.
Stack base = 0xd6bb92c8, Stack size = 15256 bytes
Fatal Error signal = 0x0000000b PID/TID = 1699/-692348096
17/2/2015 9:58:32 Exécution de NSD
NSD is in progress .................
[1]+ Stoppé /opt/ibm/notes/framework/../notes %F
/opt/ibm/notes/framework/../notes %F
[01699:00002-4068419712] GetSystemMenu() returned a null handle
[01699:00002-4068419712] 17/02/2015 09:55:48,22 DeskClientOpenInt> Calling CreateProgramRCP pszRCPCmdLine[/authenticate ] bDeskProvisioningRestart [0]
[01699:00002-4068419712] 17/02/2015 09:55:48,22 DeskClientOpenInt> Executed CreateProgramRCP
[01728:00002-4149880576] 17/02/2015 09:55:54,12 InitGlobalProcessInfo> PID [1728]!= [0]
libpng warning: Application built with libpng-1.2.31 but running with 1.6.16
libpng warning: Application built with libpng-1.2.31 but running with 1.6.16
[01699:00002-4068419712] 17/02/2015 09:56:01 Connecté au serveur PARMAIL102/SERVERS/GROUP
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
libpng warning: Application built with libpng-1.2.24 but running with 1.6.16
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration démarré
[02088:00002-4101208576] 17/02/2015 09:56:15 Initialisation de Dynamic Client Configuration
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations de politique
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration : application des signets de politique
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations sur le site
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,24 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,24 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,25 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Dynamic Client Configuration met à jour les informations d'emplacement à l'aide de la politique
[02088:00002-4101208576] 17/02/2015 09:56:15,33 DynConfig> Found $DPLocked field: $DPLocked on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15,33 DynConfig> Found $DPLocked field: $DPLockedUnstripped on policy note. Copying to location doc
[02088:00002-4101208576] 17/02/2015 09:56:15 Arrêt de Dynamic Client Configuration
(pid 1699 ) X lib error (11:BadAlloc (insufficient resources for operation)) occurs
(pid 1699 ) X lib error (4:BadPixmap (invalid Pixmap parameter)) occurs
(pid 1699 ) X lib error (4:BadPixmap (invalid Pixmap parameter)) occurs
[01699:00002-4068419712] (MailSendNoteActual)- after lookup Total recipients 1
Unhandled exception
Type=Segmentation error vmState=0xf6c98480
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000001
Handler1=F72C5CDA Handler2=F729B021 InaccessibleAddress=00000004
EDI=F7326760 ESI=09059690 EAX=00000004 EBX=E2395000
ECX=00000001 EDX=E0F4BF94
EIP=E235BC5E ES=002B DS=002B ESP=FF921744
EFlags=00010202 CS=0023 SS=002B EBP=FF92177C
Module=/lib/libgobject-2.0.so.0
Module_base_address=E2345000 Symbol=g_object_get_qdata
Symbol_address=E235BC40
Target=2_40_20130704_155156 (Linux 3.14.27-desktop-1.mga4)
CPU=x86 (4 logical CPUs) (0x1eace2000 RAM)
----------- Stack Backtrace -----------
(0xF728EB76 [libj9prt24.so+0xbb76])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF728EC09 [libj9prt24.so+0xbc09])
(0xF728ED2C [libj9prt24.so+0xbd2c])
(0xF728E9A8 [libj9prt24.so+0xb9a8])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF728EA1C [libj9prt24.so+0xba1c])
(0xF72C6AA6 [libj9vm24.so+0xfaa6])
(0xF72C6726 [libj9vm24.so+0xf726])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF72C5F0B [libj9vm24.so+0xef0b])
(0xF72C5D5E [libj9vm24.so+0xed5e])
(0xF729B199 [libj9prt24.so+0x18199])
__kernel_rt_sigreturn+0x0 (0xF77B2410 [linux-gate.so.1+0x410])
(0xE0F4C016 [<unknown>+0x0])
JVM_InvokeMethod+0x92 (0xF73899C4 [libjvm.so+0xa9c4])
JVM_InvokeMethod+0x58 (0xF7797398 [libjvm.so+0x3398])
Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x34 (0xE39C9804 [libjava.so+0x12804])
(0xE6631BF7 [<unknown>+0x0])
JVM_InvokeMethod+0x92 (0xF73899C4 [libjvm.so+0xa9c4])
JVM_InvokeMethod+0x58 (0xF7797398 [libjvm.so+0x3398])
Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x34 (0xE39C9804 [libjava.so+0x12804])
(0xE6631BF7 [<unknown>+0x0])
(0xF72D5D85 [libj9vm24.so+0x1ed85])
(0xF730BABD [libj9vm24.so+0x54abd])
(0xF729A66C [libj9prt24.so+0x1766c])
(0xF730BB9B [libj9vm24.so+0x54b9b])
(0xF72D637D [libj9vm24.so+0x1f37d])
(0xF72D43C4 [libj9vm24.so+0x1d3c4])
startJavaJNI+0x418 (0xF77AB3D9 [eclipse_1407.so+0x83d9])
startJavaVM+0x24 (0xF77AC878 [eclipse_1407.so+0x9878])
run+0x59d (0xF77A614B [eclipse_1407.so+0x314b])
(0x080490EE [notes2+0x10ee])
__libc_start_main+0xf3 (0xF75BDB33 [libc.so.6+0x19b33])
---------------------------------------
JVMDUMP039I Traitement de l'événement de vidage "gpf", détails "" à 2015/02/17 09:58:10 - Veuillez patienter.
JVMDUMP032I La machine virtuelle Java a demandé un vidage System en utilisant '/home/will/lotus/notes/data/workspace/logs/core.20150217.095810.1728.0001.dmp' en réponse à un événement
JVMDUMP010I Vidage System écrit dans /home/will/lotus/notes/data/workspace/logs/core.20150217.095810.1728.0001.dmp
JVMDUMP032I La machine virtuelle Java a demandé un vidage Java en utilisant '/home/will/lotus/notes/data/workspace/logs/javacore.20150217.095810.1728.0002.txt' en réponse à un événement
JVMDUMP010I Vidage Java écrit dans /home/will/lotus/notes/data/workspace/logs/javacore.20150217.095810.1728.0002.txt
JVMDUMP032I La machine virtuelle Java a demandé un vidage Snap en utilisant '/home/will/lotus/notes/data/workspace/logs/Snap.20150217.095810.1728.0003.trc' en réponse à un événement
JVMDUMP009I Le vidage Snap est indisponible
JVMDUMP013I Evénement de vidage traité "gpf", détails "".
[01699:00015-3602619200] Thread=[01699:00015-3602619200]
[01699:00015-3602619200] Stack base=0xD6BB92C8, Stack size = 13384 bytes
[01699:00015-3602619200] PANIC: The notes2 process (pid=1728) exited unexpectedly.
Stack base = 0xd6bb92c8, Stack size = 15256 bytes
Fatal Error signal = 0x0000000b PID/TID = 1699/-692348096
17/2/2015 9:58:32 Exécution de NSD
NSD is in progress .................
[1]+ Stoppé /opt/ibm/notes/framework/../notes %F
Merci pour votre aide.
lebarhon Membre non connecté
-
- Voir le profil du membre lebarhon
- Inscrit le : 09/10/2010
- Groupes :
-
Équipe Mageia
-
Membre d'Honneur
On voit ici
http://www-10.lotus.com/ldd/nd85forum.nsf/dba3ca7e515d55ff85256a0700727b35/9df8888f01c9f0e185257d4600693b03?OpenDocument
que ce message d'erreur est générique, on ne sait pas ce qui le cause.
Mais d'un autre coté, cela tend à disculper Mageia.
willyk2 Membre non connecté
-
- Voir le profil du membre willyk2
- Inscrit le : 08/12/2009
/opt/ibm/notes/framework/../notes %F
Quelqu'un peut-il me dire que signifie ce %F ?
Lorsque, je lance l'applis avec le bouton je n'ai pas message graphique d'erreur sur son lancement.
En revanche, lorsque j'utilise cette commande dans un terminal, j'ai un message d'erreur graphique sur ce fameux %F.
???
Akien Membre non connecté
-
- Voir le profil du membre Akien
- Inscrit le : 12/06/2011
- Groupes :
-
Équipe Mageia
Seul le fichier .desktop connaît cette syntaxe, si tu utilises exactement la même commande dans un terminal, tu as une erreur car Lotus notes essaie d'ouvrir un fichier appelé « %F ». Pour lancer Lotus notes en ligne de commande, il te faut soit virer le %F, soit le remplacer par un ou plusieurs noms de fichiers à ouvrir.
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie