Home › › Pagina 10

fredflinstone

Pubblicato il da

Risposte al Forum Create

Stai vedendo 15 articoli - dal 136 a 150 (di 175 totali)
1 2 3 … 9 10 11 12
  • Autore
    Articoli
  • 5 Maggio, 2019 alle 19:11 in risposta a: Crash Dolhin e Blocco Plasma #32806
    fredflinstone
    Partecipante

    Ciao !

    Anch’io ho un problema con plasma che pare si inchiodi dopo un certo periodo di inattività.
    Ho seguito i vari suggerimenti dei post precedenti e ho anche disinstallato il driver intel per far girare tutto sotto modeset.
    Però il problema persiste.
    Diro’ come ulteriore informazione che andando col puntatore in alto a sinistra dello schermo le finestre attive diventano accessibili e ci si può lavorare, ma se lancio un qualsiasi programma da shell non parte nulla.

    Negli ultimi due riavvii ho notato che il sistema dice ” resuming from hibernate ” con riferimento all’ hard disk che ospita OM.
    E’ possibile che il SO si iberni dopo un certo periodo di inattività ?
    Se si, come riavviare il tutto ?
    Grazie.

    24 Aprile, 2019 alle 15:46 in risposta a: mldonkey #32801
    fredflinstone
    Partecipante

    OK !
    Grazie.

    13 Aprile, 2019 alle 09:13 in risposta a: driver virtualbox #32798
    fredflinstone
    Partecipante

    Ciao !

    Ti ringrazio molto.
    Ora funziona tutto perfettamente.

    12 Aprile, 2019 alle 16:22 in risposta a: driver virtualbox #32796
    fredflinstone
    Partecipante

    Ciao !

    adesso funziona tutto.

    un’ ultima cosa : per utilizzare i device usb su VB dovrei avere i permessi in vboxusers.

    Ho provato ma non son riuscito a trovare il gruppo …. cosa faccio ?

    Grazie.

    11 Aprile, 2019 alle 19:50 in risposta a: driver virtualbox #32794
    fredflinstone
    Partecipante

    Ciao !

    dato il comando di cui sopra mi ha caricato i driver.

    però dopo un controllo :

    systemctl status dkms
    ● dkms.service – Builds and install new kernel modules through DKMS
    Loaded: loaded (/lib/systemd/system/dkms.service; enabled; vendor preset: enabled)
    Active: active (exited) since Thu 2019-04-11 20:44:36 CEST; 1min 35s ago
    Docs: man:dkms(8)
    Process: 3518 ExecStart=/bin/sh -c dkms autoinstall –verbose –kernelver $(uname -r)>
    Main PID: 3518 (code=exited, status=0/SUCCESS)

    apr 11 20:44:36 blackmamba sh[3518]: Error! echo
    apr 11 20:44:36 blackmamba sh[3518]: Your kernel headers for kernel 4.14.94mamba-64GB c>
    apr 11 20:44:36 blackmamba sh[3518]: /lib/modules/4.14.94mamba-64GB/build or /lib/modul>
    apr 11 20:44:36 blackmamba sh[3518]: Error! echo
    apr 11 20:44:36 blackmamba sh[3518]: Your kernel headers for kernel 4.14.94mamba-64GB c>
    apr 11 20:44:36 blackmamba sh[3518]: /lib/modules/4.14.94mamba-64GB/build or /lib/modul>
    apr 11 20:44:36 blackmamba sh[3518]: Error! echo
    apr 11 20:44:36 blackmamba sh[3518]: Your kernel headers for kernel 4.14.94mamba-64GB c>
    apr 11 20:44:36 blackmamba sh[3518]: /lib/modules/4.14.94mamba-64GB/build or /lib/modul>
    apr 11 20:44:36 blackmamba systemd[1]: Started Builds and install new kernel modules th>
    lines 1-17/17 (END)

    succede questo.

    grazie.

    11 Aprile, 2019 alle 13:57 in risposta a: driver virtualbox #32792
    fredflinstone
    Partecipante

    Ciao !

    chiedo scusa per il mancato riferimento.

    Comunque dato il comando non appare nulla…….

    ecco qua :

    [root@blackmamba claudio]# dkms status
    dato l’invio torna a quanto sotto senza dire nulla
    [root@blackmamba claudio]# dkms status

    Grazie.

    10 Aprile, 2019 alle 21:04 in risposta a: driver virtualbox #32790
    fredflinstone
    Partecipante

    Ciao !

    ecco tutti i comandi e relative risposte :

    # systemctl status dkms
    ● dkms.service – Builds and install new kernel modules through DKMS
    Loaded: loaded (/lib/systemd/system/dkms.service; enabled; vendor preset: enabled)
    Active: active (exited) since Wed 2019-04-10 13:30:46 CEST; 1h 11min ago
    Docs: man:dkms(8)
    Process: 3531 ExecStart=/bin/sh -c dkms autoinstall –verbose –kernelver $(uname -r)>
    Main PID: 3531 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
    Memory: 11.5M
    CGroup: /system.slice/dkms.service

    Warning: Journal has been rotated since unit was started. Log output is incomplete or u>
    [root@blackmamba claudio]# yum install kernel-mamba-x86_64-headers
    Plugin abilitati:refresh-packagekit
    Impostazione processo di installazione
    Nessun pacchetto kernel-mamba-x86_64-headers disponibile.
    Errore: Niente da fare
    [root@blackmamba claudio]# systemctl restart dkms
    [root@blackmamba claudio]# modprobe vboxdrv vboxpci vboxnetadp vboxnetflt
    modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.14.94mamba-64GB

    10 Aprile, 2019 alle 13:49 in risposta a: driver virtualbox #32787
    fredflinstone
    Partecipante

    Ciao !

    gli headers del kernel risultano installati.

    dando l’ ultimo comando indicato la risposta è questa :

    ” modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.14.94mamba-64GB ”

    Aggiungo che ho un pc datato a 32 ….

    Grazie.

    • Questa risposta è stata modificata 5 anni, 7 mesi fa da fredflinstone.
    26 Dicembre, 2016 alle 20:43 in risposta a: kmail #32252
    fredflinstone
    Partecipante

    Ciao !
    Risolto con nuovo aggiornamento.
    Grazie.

    17 Dicembre, 2016 alle 19:08 in risposta a: Vivaldi browser #32235
    fredflinstone
    Partecipante

    Ciao !
    ti ringrazio, ora funziona.
    Devo dire che ‘sto browser è veloce come pochi .
    Un saluto.

    31 Dicembre, 2015 alle 15:26 in risposta a: Auguri #31661
    fredflinstone
    Partecipante

    Ciao !
    Auguri a tutti di buon anno !
    … e in ritardo di buon Natale ( che fino al 6 gennaio si può !! )

    5 Ottobre, 2015 alle 15:26 in risposta a: Chrome pepper-plugin #31445
    fredflinstone
    Partecipante

    ciao !

    Comando group :

    bash: group: command not found…

    3 Ottobre, 2015 alle 08:02 in risposta a: Chrome pepper-plugin #31436
    fredflinstone
    Partecipante

    Ciao !
    Oggi riaccendendo il pc mi si è ripresentata la proposta di installazione del plugin che eseguita dice che non è andata a buon fine.

    questo è il messaggio col comando di cui sopra :

    Package name: chromium-pepper-flash
    Installed version: 45.0.2454.101-1mamba
    Last version: 45.0.2454.101-1mamba

    da root il plugin si è installato.

    Grazie

    2 Ottobre, 2015 alle 09:39 in risposta a: Chrome pepper-plugin #31435
    fredflinstone
    Partecipante

    Ciao !

    Lanciando il comando suggerito , come su , il plugin si è installato senza problemi.
    Grazie.

    29 Settembre, 2015 alle 18:38 in risposta a: Knotify #31429
    fredflinstone
    Partecipante

    Ciao !

    Ecco il backtrace :

    Application: KNotify (knotify4), signal: Segmentation fault
    Using host libthread_db library “/lib/libthread_db.so.1”.
    [Current thread is 1 (Thread 0xb5bf1a80 (LWP 13620))]

    Thread 2 (Thread 0xb4323b40 (LWP 13621)):
    #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/i386/i586/../i486/lowlevellock.S:146
    #1 0x43ed6f31 in __GI___pthread_mutex_lock (mutex=0x43cde4c4 <_rtld_global+1220>) at ../nptl/pthread_mutex_lock.c:116
    #2 0x43ccbb2f in tls_get_addr_tail (ti=ti@entry=0x444a09cc, dtv=0x99ed278, the_map=0xb623f030) at dl-tls.c:765
    #3 0x43cccc12 in update_get_addr (ti=0x444a09cc) at dl-tls.c:808
    #4 0x44400918 in __cxa_get_globals () from /usr/lib/libstdc++.so.6
    #5 0x444007e4 in std::uncaught_exception() () from /usr/lib/libstdc++.so.6
    #6 0x451a5c6e in ?? () from /usr/lib/libQtCore.so.4
    #7 0x451a5e49 in qWarning(char const*, …) () from /usr/lib/libQtCore.so.4
    #8 0x452f08cd in ?? () from /usr/lib/libQtCore.so.4
    #9 0x43f5cdf6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
    #10 0x43f5d3c5 in ?? () from /usr/lib/libglib-2.0.so.0
    #11 0x43f5d578 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
    #12 0x452f10b4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #13 0x452c0222 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #14 0x452c054f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #15 0x451addf0 in QThread::exec() () from /usr/lib/libQtCore.so.4
    #16 0x452a12cc in ?? () from /usr/lib/libQtCore.so.4
    #17 0x451b08f3 in ?? () from /usr/lib/libQtCore.so.4
    #18 0x43ed4629 in start_thread (arg=0xb4323b40) at pthread_create.c:334
    #19 0x43ddb82e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

    Thread 1 (Thread 0xb5bf1a80 (LWP 13620)):
    [KCrash Handler]
    #6 0x43d680b5 in __GI_strcmp (p1=0x135d9f90 <error: Cannot access memory at address 0x135d9f90>, p2=0xae0cc153 “QMap<QString,QVariant>”) at strcmp.c:34
    #7 0xae01c644 in QMetaType::registerNormalizedType(QByteArray const&, void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void const*), int, QFlags<QMetaType::TypeFlag>, QMetaObject const*) () from /usr/lib/libQt5Core.so.5
    #8 0xae32337c in ?? () from /usr/lib/libQt5Gui.so.5
    #9 0x43cc9201 in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0xbfbd6224, env=env@entry=0x999a540) at dl-init.c:72
    #10 0x43cc9322 in call_init (env=<optimized out>, argv=<optimized out>, argc=<optimized out>, l=<optimized out>) at dl-init.c:30
    #11 _dl_init (main_map=main_map@entry=0x9aeafb0, argc=1, argv=0xbfbd6224, env=0x999a540) at dl-init.c:120
    #12 0x43cceb2d in dl_open_worker (a=0xbfbd4c7c) at dl-open.c:564
    #13 0x43cc9076 in _dl_catch_error (objname=objname@entry=0xbfbd4c74, errstring=errstring@entry=0xbfbd4c78, mallocedp=mallocedp@entry=0xbfbd4c73, operate=operate@entry=0x43cce500 <dl_open_worker>, args=args@entry=0xbfbd4c7c) at dl-error.c:187
    #14 0x43ccded7 in _dl_open (file=0x9ae9c40 “/usr/lib/vlc/plugins/gui/libqt4_plugin.so”, mode=-2147483647, caller_dlopen=caller_dlopen@entry=0xb37f9418 <module_Load+40>, nsid=<optimized out>, argc=argc@entry=1, argv=argv@entry=0xbfbd6224, env=0x999a540) at dl-open.c:649
    #15 0x43ec7c68 in dlopen_doit (a=0xbfbd4e40) at dlopen.c:66
    #16 0x43cc9076 in _dl_catch_error (objname=0x98b5f44, errstring=0x98b5f48, mallocedp=0x98b5f40, operate=0x43ec7bd0 <dlopen_doit>, args=0xbfbd4e40) at dl-error.c:187
    #17 0x43ec84b6 in _dlerror_run (operate=operate@entry=0x43ec7bd0 <dlopen_doit>, args=args@entry=0xbfbd4e40) at dlerror.c:163
    #18 0x43ec7d27 in __dlopen (file=0x9ae9c40 “/usr/lib/vlc/plugins/gui/libqt4_plugin.so”, mode=1) at dlopen.c:87
    #19 0xb37f9418 in module_Load () from /usr/lib/libvlccore.so.8
    #20 0xb37de259 in module_InitDynamic () from /usr/lib/libvlccore.so.8
    #21 0xb37de564 in AllocatePluginDir () from /usr/lib/libvlccore.so.8
    #22 0xb37de4ae in AllocatePluginDir () from /usr/lib/libvlccore.so.8
    #23 0xb37de9ac in AllocatePluginPath () from /usr/lib/libvlccore.so.8
    #24 0xb37def7a in module_LoadPlugins () from /usr/lib/libvlccore.so.8
    #25 0xb3768475 in libvlc_InternalInit () from /usr/lib/libvlccore.so.8
    #26 0xb373a133 in libvlc_new () from /usr/lib/libvlc.so.5
    #27 0xb38a4e02 in LibVLC::init() () from /opt/kde/lib/kde4/plugins/phonon_backend/phonon_vlc.so
    #28 0xb388945e in Phonon::VLC::Backend::Backend(QObject*, QList<QVariant> const&) () from /opt/kde/lib/kde4/plugins/phonon_backend/phonon_vlc.so
    #29 0xb388a0ac in qt_plugin_instance () from /opt/kde/lib/kde4/plugins/phonon_backend/phonon_vlc.so
    #30 0x452a5839 in QPluginLoader::instance() () from /usr/lib/libQtCore.so.4
    #31 0xb3b17717 in Phonon::KdePlatformPlugin::createBackend (this=0x9bd6a60, newService=…) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/phonon/platform_kde/kdeplatformplugin.cpp:130
    #32 0xb3b17e86 in Phonon::KdePlatformPlugin::createBackend (this=0x9bd6a60) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/phonon/platform_kde/kdeplatformplugin.cpp:183
    #33 0xb7212009 in Phonon::FactoryPrivate::createBackend() () from /usr/lib/libphonon.so.4
    #34 0xb721273c in Phonon::Factory::backend(bool) () from /usr/lib/libphonon.so.4
    #35 0xb7212ea8 in Phonon::Factory::createAudioOutput(QObject*) () from /usr/lib/libphonon.so.4
    #36 0xb7209ed1 in Phonon::AudioOutputPrivate::createBackendObject() () from /usr/lib/libphonon.so.4
    #37 0xb7207978 in Phonon::AudioOutputPrivate::init(Phonon::Category) () from /usr/lib/libphonon.so.4
    #38 0x08054851 in Player (this=<optimized out>) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/notifybysound.cpp:58
    #39 PlayerPool::getPlayer (this=0x99e2f24) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/notifybysound.cpp:98
    #40 0x08055b68 in NotifyBySound::notify (this=0x99d8748, eventId=5, config=0x9c57740) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/notifybysound.cpp:242
    #41 0x08051be9 in KNotify::emitEvent (this=0xbfbd614c, e=0x9c57738) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/knotify.cpp:230
    #42 0x08052be2 in KNotify::event (this=0xbfbd614c, event=…, appname=…, contexts=…, title=…, text=…, image=…, actions=…, timeout=-1, winId=14680500) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/knotify.cpp:149
    #43 0x080535c0 in KNotifyAdaptor::event (this=0xae0cc153, event=…, fromApp=…, contexts=…, title=…, text=…, image=…, actions=…, timeout=-1, winId=<optimized out>) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/knotify.cpp:289
    #44 0x080538f3 in KNotifyAdaptor::qt_static_metacall (_o=0xae0cc153, _o@entry=0x99f0830, _id=-1373099136, _id@entry=4, _a=0xae0cc153, _a@entry=0xbfbd5a20, _c=<optimized out>) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/build/knotify/knotify.moc:217
    #45 0x08053a5e in qt_static_metacall (_a=0xbfbd5a20, _id=4, _c=QMetaObject::InvokeMetaMethod, _o=0x99f0830) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/build/knotify/knotify.moc:258
    #46 KNotifyAdaptor::qt_metacall (this=0x99f0830, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfbd5a20) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/build/knotify/knotify.moc:259
    #47 0x44daca7f in ?? () from /usr/lib/libQtDBus.so.4
    #48 0x44dadd60 in ?? () from /usr/lib/libQtDBus.so.4
    #49 0x44dae3d2 in ?? () from /usr/lib/libQtDBus.so.4
    #50 0x44dae81d in ?? () from /usr/lib/libQtDBus.so.4
    #51 0x452dadc8 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
    #52 0xb67308e9 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
    #53 0xb6737191 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
    #54 0xb74829ae in KApplication::notify (this=0xbfbd613c, receiver=0xbfbd614c, event=0x9c8af08) at /var/autodist/RPM/BUILD/kdelibs-4.14.10/kdeui/kernel/kapplication.cpp:311
    #55 0x452c1767 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
    #56 0x452c4cd4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
    #57 0x452c5225 in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
    #58 0x452f0f1e in ?? () from /usr/lib/libQtCore.so.4
    #59 0x43f5d1a1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
    #60 0x43f5d4a9 in ?? () from /usr/lib/libglib-2.0.so.0
    #61 0x43f5d578 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
    #62 0x452f109a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #63 0xb67e0819 in ?? () from /usr/lib/libQtGui.so.4
    #64 0x452c0222 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #65 0x452c054f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
    #66 0x452c5f1b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
    #67 0xb672ebf5 in QApplication::exec() () from /usr/lib/libQtGui.so.4
    #68 0x0804fe05 in main (argc=1, argv=0xbfbd6224) at /var/autodist/RPM/BUILD/kde-runtime-4.14.3/knotify/main.cpp:74

    Grazie.

  • Autore
    Articoli
Stai vedendo 15 articoli - dal 136 a 150 (di 175 totali)
1 2 3 … 9 10 11 12