Visualizza post

Questa sezione ti permette di visualizzare tutti i post inviati da questo utente. N.B: puoi vedere solo i post relativi alle aree dove hai l'accesso.


Topics - jojek

Pagine: [1]
1
Connessioni e Reti / Disco di rete Lacie
« il: 21 Marzo 2015 ore 22:14 »
Salve a tutti, vorrei se possibile un aiuto per montare correttamente in automatico un disco di rete.
Il disco è diviso in tre, due utenti protetti dalle loro password e una partizione condivisa Family e vorrei renderlo disponibile all'avvio o alla sua accensione in dolphin, magari mantenendo le password dei due utenti
Nello specifico per montare le unità uso da terminale i seguenti comandi:

per la partizione condivisa
Codice: [Seleziona]
sudo mount -t cifs //192.168.1.6/Family /mnt/
per utenti uno e due
Codice: [Seleziona]
sudo mount -t cifs //192.168.1.6/utente /mnt/ -o username=nomeutente,password=passwordutente
Ho provato a creare le partizioni in /media e editare il fstab facendo qualche tentativo ma non sono ancora arrivato alla soluzione
Posto il mio ultimo tentativo
# 
# /etc/fstab: static file system information
#
# <file system>   <dir>   <type>   <options>   <dump>   <pass>
UUID=63dc304c-3c57-4c7e-9bca-4ca25a0ae490 / ext4 defaults 0 1
UUID=e18c068b-90fa-4f98-bc25-ff779cfbe165 swap swap defaults 0 0
UUID=6e29fd15-fb44-4197-b4ec-4a50e7062dd6 /home ext4 defaults 0 0
//192.168.1.6/pippo /mnt/PIPPO cifs defaults,rw,nounix,noatime,noauto,x-systemd.automount,users,workgroup=Workgroup,ip=192.168.1.6,file_mode=0777,dir_mode=0777 0 0
//192.168.1.6/pluto /mnt/PLUTO cifs defaults,rw,nounix,noatime,noauto,x-systemd.automount,users,workgroup=Workgroup,ip=192.168.1.6,file_mode=0777,dir_mode=0777 0 0
//192.168.1.6/Family /mnt/FAMILY cifs defaults,rw,nounix,noatime,noauto,x-systemd.automount,users,workgroup=Workgroup,ip=192.168.1.6,file_mode=0777,dir_mode=0777 0 0
Ringrazio tutti in anticipo per eventuali consigli e chiarimenti

2
Consigli e discussioni generali sul Software / Problemi con Akonadi
« il: 17 Febbraio 2014 ore 15:23 »
Saluti a tutti da qualche tempo, dopo l'avvio del sistema, due volte su tre il server akonadi non parte dandomi errori vari
Codice: [Seleziona]
Akonadi Server Self-Test Report
===============================

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/jejo/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-jejo.WCsdh2/mysql.socket"
ServerPath=/usr/bin/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/bin/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/bin/mysqld  Ver 5.5.34-MariaDB-log for Linux on x86_64 (MariaDB Server)


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

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

File content of '/home/jejo/.local/share/akonadi/db_data/mysql.err':
140217 13:05:54 InnoDB: The InnoDB memory heap is disabled
140217 13:05:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140217 13:05:54 InnoDB: Compressed tables use zlib 1.2.8
140217 13:05:54 InnoDB: Using Linux native AIO
140217 13:05:54 InnoDB: Initializing buffer pool, size = 80.0M
140217 13:05:54 InnoDB: Completed initialization of buffer pool
140217 13:05:54 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140217 13:05:54  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140217 13:05:55  InnoDB: Waiting for the background threads to start
140217 13:05:56 Percona XtraDB (http://www.percona.com) 5.5.34-MariaDB-31.1 started; log sequence number 6031284
140217 13:05:56 [Note] Plugin 'FEEDBACK' is disabled.
140217 13:05:56 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
140217 13:05:56 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
140217 13:05:56 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
140217 13:05:56 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.5.34-MariaDB'  socket: '/tmp/akonadi-jejo.WCsdh2/mysql.socket'  port: 0  MariaDB Server


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

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

File content of '/usr/share/config/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/jejo/.local/share/akonadi/mysql.conf'>/home/jejo/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/jejo/.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

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

[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
vcarddirresource.desktop
vcardresource.desktop

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

Test 16:  SUCCESS
--------

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

Test 17:  SUCCESS
--------

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

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.
Per tamponare all'inconveniente faccio logout login e tutto funziona sino al prossimo riavvio di sistema, questo mi succede sia sul desktop che sul portatile ( che tra l'altro ho appena rinfrescato con un installazione nuova di zecca con l'ultima iso di Chakra )
Cercando in rete ho trovato una discussione riguardo a problemi simili inerenti ad akonadi che parlava di una certa incompatibilità con alcuni driver Nvidia ( uso Nvidia sia sul fisso che sul portatile ) il che spiegherebbe perché il problema è nato più o meno nel periodo in qui ho effettuato questo aggiornamento http://chakra-project.it/notizie/?p=1511
A voi è capitato nulla di simile e/o avete consigli su una soluzione ?
Grazie per la cortese attenzione  :beer:

3
Pacchetti / kmail e cestino posta
« il: 04 Novembre 2012 ore 11:57 »
Salve a tutti, dopo il passaggio a sitemd sulla mia vecchia Chakra e dopo aver riscontrato una serie di problemi poco attendibili mi sono deciso di reinstallare con Chakra 2012.09.
Da li sono passato a sistemd senza apparenti problemi, ma ho ritrovato dei piccoli cambiamenti, ad esempio in kmail ho importato il mio account gmail e poi ho creato altri due account tiscali e mi sono ritrovato sotto gmail la classica gerarchia di cartelle ( bozze, cestino, importanti .....) ma ho notato che cestinando un messaggio cuesto non viene spostato nel cestino.
Per gli altri due account la cartella cestino non esiste nemmeno e cestinando un messaggio questo scompare e basta.
Alla fine non vorrei ritrovarmi il pc pieno di robaccia cestinata stipata chissadove.

4
Pacchetti / Dragon player
« il: 24 Gennaio 2012 ore 22:10 »
Da circa un giorno, credo post aggiornamento di ieri sera, DragonPlayer si comporta in maniera anomala.
Cuando tento di riprodurre un file ( AVI, WMV, MPG, ecc. ) l'audio si sente correttamente ma il video è completamente nero e mi apre un ulteriore finestra di VLC Colour asCii art che si chiude solo allo spegnimento di Dragonplayer.
Ho verificato in associzione file e i formati video interessati sono tutti associati a Dragonplayer  ???

5
Pacchetti / Problemi con Amarok e Clementine
« il: 15 Novembre 2011 ore 14:11 »
Ciao a tutti, ho sempre usato Amarok come player sulle mie distro ( Chakra compresa ) ma da un qualche tempo mi da dei problemucci all'avvio della sessione.
Subito dopo il login mi ritrovo un utilizzo della cpu esagerato da parte di Amarok che dura una decina di minuti, la cosa strana è che se clicco sull'icona di Amarok nel vassoio di sistema e massimizzo l'applicazione questa smette di succhiarmi risorse sino ad un nuovo login.
Avevo già aperto un post per chiedere aiuto ma non avendo trovato soluzioni mi sono limitato ad attendere magari che la cosa si sistemasse con degli aggiornamenti, ma così non è stato.
Premetto che ho già provato a disinstallare Amarok, rimuovere i suoi file di configurazione, reinstallarlo ma senza successo.
Ho lo stesso problema sul desktop e sul portatile entrambe con Chakra Stabile x86_64.
A questo punto ho provato a installare Clementine ma quando provo a riprodurre qualcosa mi da questo errore
Codice: [Seleziona]
GStreamer could not create the element: volume. Please make sure that you have installed all necessary GStreamer plugins (e.g. OGG and MP3)Avevo già installato gstreamer con tutti i suoi plugins  ???

6
Pacchetti / Amarok dopo aggiornamento kde 4.7
« il: 04 Agosto 2011 ore 03:16 »
Ciao a tutti, dopo l'ultimo aggiornamento effettuato su due diversi pc ( con Chakra 64 stabile ) ho riscontrato , oltre che a un leggero aumento del consumo di risorse generale, che ad ogni avvio della sessione Amarok mi ciuccia il 40% di cpu e una notevole porzione di memoria fino a quando non clicco sulla sua icona nel vassoio di sistema massimizzandolo dopo di che sembra rimettersi tutto apposto fino al prossimo riavvio di sessione.

7
Consigli e discussioni generali sul Software / Crash Nepomuk
« il: 14 Giugno 2011 ore 22:16 »
Ciao, dopo l'ultimo aggiornamento mi si presenta continuamente la finestra del gestore degli errori di Kde con il crash di Nepomuk.
Il problema si presenta sia sul portatile sia sul desktop, tutti e due aggiornati con i repo stabili.

[allegato eliminato da un amministratore]

8
PC Portatili / ( Risolto ) hp pavilion dv9690 batteria / AC
« il: 11 Aprile 2011 ore 23:02 »
Salve a tutti e da poco che sono alle prese con Chakra e questo è il mio primo post quindi ne approfitto per porgervi i miei saluti e i complimenti per il bel lavoro che state portando avanti.
Bando alle ciance, ho questo piccolo problema, sembra che il sistema non riconosca quando il cavo AC sia inserito o no.
Se avvio il sistema in batteria mi ritrovo con il powersave inserito correttamente, se attacco il cavo mi torna su prestazioni come giusto che sia, ma se lo stacco mi resta l'icona connessa al'AC la luminosità non cala e rimane in prestazioni sino all'esaurirsi della batteria.
Premetto che la batteria del portatile non è nelle condizioni ottimali, ma con Kubuntu ( e se non erro nemmeno con Chakra prima di vari aggiornamenti ) il problema non si presenta.
Qualcuno sa darmi delle dritte, consigli, o indicazioni  sul da farsi ?

Pagine: [1]
Template by Homey | Sito ufficiale | Disclaimer