zte mfe626 (modem comcel colombia) en linux

Feliz navidad a todos (yo que soy el único que me leo :p) recientemente me traslade a la capital colombiana y deje muchas cosas atrás (sniffff sniff) pero también muchas cosas nuevas dentro de ellas la forma de conectar mi debian a internet, joder lo primero que llego y me encuentro es que no hay linea telefónica y nada por el estilo solo un modem el cual viene preparado para trabajar bajo windows (incluye programita y todo el cuento), investigando por la inet hay muchos modulos de como montar modem 3g en otros países pero no en Colombia, entonces cacharreando (viendo las conf del windows) un poco encontré la solución, requisitos y herramientas utilizadas en este caso.

Requisitos (lo que tengo instalado en este momento)

kernel: Linux w-andrey 2.6.30-2-686 #1 SMP i686 GNU/Linux

programa wvdial (apt-get install wvdial)

En este caso el kernel ya esta en capacidad de detectar los modems 3G pero con el inconveniente que mi entorno kde4 me monta una unidad de cd (Si!! un dispositivo usb lo detecta como cd), en fin es cuestión de desmontarlo para que el kernel ejecute el modulo usbserial.

Entonces cuando se conecta el modem tenemos lo siguiente en el log /var/log/messages

Dec 27 10:22:00 De-andrey kernel: [ 61.164067] usb 1-3: new high speed USB device using ehci_hcd and address 4

Dec 27 10:22:00 De-andrey kernel: [ 61.308775] usb 1-3: New USB device found, idVendor=19d2, idProduct=2000

Dec 27 10:22:00 De-andrey kernel: [ 61.308780] usb 1-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0

Dec 27 10:22:00 De-andrey kernel: [ 61.308783] usb 1-3: Product: ZTE CDMA Technologies MSM

Dec 27 10:22:00 De-andrey kernel: [ 61.308786] usb 1-3: Manufacturer: ZTE, Incorporated

Dec 27 10:22:00 De-andrey kernel: [ 61.308891] usb 1-3: configuration #1 chosen from 1 choice

Dec 27 10:22:00 De-andrey kernel: [ 61.313242] scsi3 : SCSI emulation for USB Mass Storage devices

Dec 27 10:22:00 De-andrey kernel: [ 61.515387] usbcore: registered new interface driver usbserial

Dec 27 10:22:00 De-andrey kernel: [ 61.515402] USB Serial support registered for generic

Dec 27 10:22:00 De-andrey kernel: [ 61.515422] usbcore: registered new interface driver usbserial_generic

Dec 27 10:22:00 De-andrey kernel: [ 61.515424] usbserial: USB Serial Driver core

Dec 27 10:22:00 De-andrey kernel: [ 61.598073] USB Serial support registered for GSM modem (1-port)

Dec 27 10:22:00 De-andrey kernel: [ 61.598115] usbcore: registered new interface driver option

Dec 27 10:22:00 De-andrey kernel: [ 61.598117] option: v0.7.2:USB Driver for GSM modems

Dec 27 10:22:05 De-andrey kernel: [ 66.315316] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0

En este punto tenemos un dispositivo en /dev llamado sr1 entonces tenemos que desmontarlo.

eject /dev/sr1

Una ves echo esto el kernel detecta el modem:

Dec 27 10:24:20 De-andrey kernel: [ 201.420097] usb 1-3: new high speed USB device using ehci_hcd and address 5

Dec 27 10:24:20 De-andrey kernel: [ 201.556666] usb 1-3: New USB device found, idVendor=19d2, idProduct=0031

Dec 27 10:24:20 De-andrey kernel: [ 201.556670] usb 1-3: New USB device strings: Mfr=2, Product=1, SerialNumber=3

Dec 27 10:24:20 De-andrey kernel: [ 201.556673] usb 1-3: Product: ZTE CDMA Technologies MSM

Dec 27 10:24:20 De-andrey kernel: [ 201.556675] usb 1-3: Manufacturer: ZTE, Incorporated

Dec 27 10:24:20 De-andrey kernel: [ 201.556678] usb 1-3: SerialNumber: 1234567890ABCDEF

Dec 27 10:24:20 De-andrey kernel: [ 201.556779] usb 1-3: configuration #1 chosen from 1 choice

Dec 27 10:24:20 De-andrey kernel: [ 201.559925] option 1-3:1.0: GSM modem (1-port) converter detected

Dec 27 10:24:20 De-andrey kernel: [ 201.560039] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0

Dec 27 10:24:20 De-andrey kernel: [ 201.560160] option 1-3:1.1: GSM modem (1-port) converter detected

Dec 27 10:24:20 De-andrey kernel: [ 201.560218] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1

Dec 27 10:24:20 De-andrey kernel: [ 201.560713] scsi4 : SCSI emulation for USB Mass Storage devices

Dec 27 10:24:20 De-andrey kernel: [ 201.560968] option 1-3:1.3: GSM modem (1-port) converter detected

Dec 27 10:24:20 De-andrey kernel: [ 201.561079] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2

Dec 27 10:24:25 De-andrey kernel: [ 206.561936] scsi 4:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2

Dec 27 10:24:25 De-andrey kernel: [ 206.562435] sd 4:0:0:0: Attached scsi generic sg3 type 0

Dec 27 10:24:25 De-andrey kernel: [ 206.565442] sd 4:0:0:0: [sdc] Attached SCSI removable disk

Ahora tenemos tres nuevos dispositivos en /dev, como podemos ver en el log estos dispositivos son: ttyUSB0, ttyUSB1,ttyUSB2.

Muy bien el kernel ya detecta correctamente el modem ahora lo que tenemos que hacer es configurar el wvdial, editamos o creamos el fichero que se encuentra en /etc/wvdial.conf el cual queda de la siguiente forma:

[Dialer Defaults]

#Created by wvdialconf:

Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Init1 = ATZ

Modem = /dev/ttyUSB2

Phone = *99#

Idle Seconds = 300

Modem Type = USB Modem

Stupid Mode = 1

Compuserve = 0

Baud = 460800

Auto DNS = 1

Dial Command = ATDT

Ask Password = 0

ISDN = 0

Username = COMCELWEB

Password = COMCELWEB

New PPPD = yes

Como podemos ver el único dispositivo útil en este caso es el /dev/ttyUSB2.

Ahora solo nos queda ejecutar wvdial pelado y nos conectara a la red comcel:

De-andrey:/home/xxxxx# wvdial

--> WvDial: Internet dialer version 1.60

--> Cannot get information for serial port.

--> Initializing modem.

--> Sending: ATZ

OK

--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

OK

--> Modem initialized.

--> Idle Seconds = 300, disabling automatic reconnect.

--> Sending: ATDT*99#

--> Waiting for carrier.

ATDT*99#

CONNECT

--> Carrier detected. Starting PPP immediately.

--> Starting pppd at Sun Dec 27 10:24:33 2009

--> Pid of pppd: 3495

--> Using interface ppp0

--> pppd: �������[08][18]t�[08][01]

--> pppd: �������[08][18]t�[08][01]

--> pppd: �������[08][18]t�[08][01]

--> pppd: �������[08][18]t�[08][01]

--> pppd: �������[08][18]t�[08][01]

--> pppd: �������[08][18]t�[08][01]

--> local IP address 190.125.100.145

--> pppd: �������[08][18]t�[08][01]

--> remote IP address 10.64.64.64

--> pppd: �������[08][18]t�[08][01]

--> primary DNS address 10.11.12.13

--> pppd: �������[08][18]t�[08][01]

--> secondary DNS address 10.11.12.14

--> pppd: �������[08][18]t�[08][01]

Y listo.

tips:

Comcel tiene un defecto con la asignación dns, y es que me he dado cuenta que estos dns no funcionan muy bn:

--> primary DNS address 10.11.12.13

--> pppd: �������[08][18]t�[08][01]

--> secondary DNS address 10.11.12.14

Por lo cual coloco el siguiente dns primario en /etc/resolv.conf

nameserver 4.2.2.3

y con esto se resuelve.

Adicionalmente les dejo el archivo de configuración para conectarse a movistar (no recuerdo el modem)

[Dialer Defaults]

Phone = *99***1#

Username = movistar

Password = movistar

Stupid Mode = 1

Dial Command = ATDT

[Dialer reset]

Modem = /dev/ttyUSB0

Init1 = AT

[Dialer movistar]

Phone = *99#

Modem = /dev/ttyUSB0

Baud = 460800

Init2 = ATZ

Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

ISDN = 0

Modem Type = Analog Modem

Init5 =AT+CGDCONT=1,"IP","internet.movistar.com.co";

Espero que os sirva en algo o a alguien jeje..

Akonadi Server Self-Test Report - (Chorrada de errores iniciando akonadi)

Sigo con las experiencias el debian (me resisto a cambiarme de SO :p) esta ves el problema fue una actualizacion del servidor de akonadi en las cuales algunas cosas salieron mal, dentro de las cuales estan que los registros de mysql se reventaron (no me pregunteis

detalles que no tengo idea del detalle), como tambien que el servidor como tal de akonadi se corrompio, solucion: cargarse las conf si no tienes nada importante y esto me da pie para otra cosa haced backups de vuetros datos cada ves que hagas actualizaciones y ya no quiero decir si estas en un sistema inestable:

los errores que me salen en el reporte son los siguientes:

Akonadi Server Self-Test Report
===============================

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

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL.
Make sure the required driver is installed.

File content of '/home/andrey/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
User=
Password=
Options="UNIX_SOCKET=/home/andrey/.local/share/akonadi/db_misc/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


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

MySQL server found.
Details: You currently have 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 locations varies depending on the distribution.

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

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.37-2 for debian-linux-gnu on i486 ((Debian))


Test 4: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file '/home/andrey/.local/share/akonadi/db_data/mysql.err' contains errors.

File content of '/home/andrey/.local/share/akonadi/db_data/mysql.err':
091017 14:41:34 [Note] Plugin 'FEDERATED' is disabled.
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.
091017 14:41:34 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.


Test 5: SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at /etc/akonadi/mysql-global.conf.

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
#
[mysqld]
skip_grant_tables
skip_networking

# 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

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2



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

MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is readable at /home/andrey/.config/akonadi/mysql-local.conf

File content of '/home/andrey/.config/akonadi/mysql-local.conf':
user=andrey


Test 7: SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at /home/andrey/.local/share/akonadi/mysql.conf and is readable.

File content of '/home/andrey/.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
#
[mysqld]
skip_grant_tables
skip_networking

# 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

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# 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
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
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2

user=andrey


Test 8: 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.2.1


Test 9: 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 10: 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 11: 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 12: 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 /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 to.

Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
distlistresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
microblog.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
strigifeeder.desktop
vcarddirresource.desktop
vcardresource.desktop
Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
distlistresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
microblog.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
strigifeeder.desktop
vcarddirresource.desktop
vcardresource.desktop

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

Test 13: ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server did report error during startup into /home/andrey/.local/share/akonadi/akonadiserver.error.

File content of '/home/andrey/.local/share/akonadi/akonadiserver.error':
"Unable to add column 'id' to table 'CollectionTable'.
Query error: 'Table 'akonadi.collectiontable' doesn't exist QMYSQL3: Unable to execute statement'"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x8051e25]
1: akonadiserver [0x80522d6]
2: [0xb8038400]
3: [0xb8038424]
4: /lib/i686/cmov/libc.so.6(gsignal+0x50) [0xb79613d0]
5: /lib/i686/cmov/libc.so.6(abort+0x185) [0xb7964a85]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x8d) [0xb7cd042d]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8052f54]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x9e) [0xb7d62cbe]
9: /usr/lib/libQtCore.so.4 [0xb7d6fc05]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb7d6ff28]
11: akonadiserver(_ZN6QDebugD1Ev+0x44) [0x804dc34]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x641) [0xb7f20f91]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x56) [0xb7f21cd6]
14: akonadiserver(main+0x398) [0x804d038]
15: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb794c7a5]
16: akonadiserver [0x804cbd1]
]
"


Test 14: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into /home/andrey/.local/share/akonadi/akonadiserver.error.old.

File content of '/home/andrey/.local/share/akonadi/akonadiserver.error.old':
"Unable to add column 'id' to table 'CollectionTable'.
Query error: 'Table 'akonadi.collectiontable' doesn't exist QMYSQL3: Unable to execute statement'"
Unable to initialize database.
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x8051e25]
1: akonadiserver [0x80522d6]
2: [0xb7fef400]
3: [0xb7fef424]
4: /lib/i686/cmov/libc.so.6(gsignal+0x50) [0xb79183d0]
5: /lib/i686/cmov/libc.so.6(abort+0x185) [0xb791ba85]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x8d) [0xb7c8742d]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8052f54]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x9e) [0xb7d19cbe]
9: /usr/lib/libQtCore.so.4 [0xb7d26c05]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x68) [0xb7d26f28]
11: akonadiserver(_ZN6QDebugD1Ev+0x44) [0x804dc34]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x641) [0xb7ed7f91]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x56) [0xb7ed8cd6]
14: akonadiserver(main+0x398) [0x804d038]
15: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb79037a5]
16: akonadiserver [0x804cbd1]
]
"


Test 15: SUCCESS
--------

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

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

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

bueno aqui el comando magico que lo encontre en :

http://forum.kde.org/viewtopic.php?f=18&t=29061

killall mysqld & killall akonadictl & killall akonadi_control & killall akonadiserver & rm -rf ~/.config/akonadi/ & rm -rf ~/.local/share/akonadi

la exlicacion rapida es: cargate todos los servicios relacionados con mysql y akonadi, despues de esto hacele palos a los directorios de configuracion del akonadi, y listo reinicas por ejemplo el kontact y mola como comienza a migrar las cosillas que hay pendientes por ahi.

salutes para mi mismo que soy quien me escribo jajjajaj..


amarok no reproduce mp3 - con los codecs instalados

vaya que alegría poder volver a postear algo (escribo para mi solo jeje), estoy en constantes instalaciones y de un momento a otro me quede sin audio, despues de algunas pruebas me di cuenta que el problema solo era con los mp3 los wma si lo reproduce bien.

después de investigar un poco encontré que el problema es que cuando se actualizan los paquetes del sistema algo pasa con las variables del xine.
Solución cargarse las configuraciones del xine que están en el home de tu usuario.

el proceso:

borra el directorio de configuración de xine:

cd /home/tu_usuario
rm -r .xine

ahora intenta iniciar el amarok.

a joder no me digas que tira crash, a pues facil cargarte también las configuraciones del amarok y lo que tiene en cache.. ¿donde guarda eso :s?

rm -r .kde/share/apps/amarok/

y listo a hacerte pajas con la cualquier musica grotesca que te haga falta.

saludos pues.

tap click desactivado del touch mouse.

Siguiendo con este mundillo que es linux, y tambien siguiendo en la idea de decorar cada ves mas nuestro debian (Si ya se que no debo decorarlo tanto, los recursos por dios los recursos!!), despues de pasarme a kde4 y hacer alguna maniobras un poco inprudentes y convinando repositorios me quede sin la opcion del tap click en my touch mouse (para los que no sabeis que es tap click, es el toque rapido sobre el touch mouse y este envia un doble click), viendo a ver si eran mala config del kde4 busque mucho y nada, no es problema del kde4 (esto lo digo porque el teclado si me lo desconfiguro, a pesar de que en las X dijera otra cosa).


Bueno al grano, lo que se hizo fue primero habilitar esta opcion en el archivo de configuracion de las X en la seccion del mouse (inputdevice):

Option "SHMConfig" "true"

despues descargarnos el siguiente paquete:

apt-get install gsynaptics

una ves descargado ejecutamos el comando "gsynaptics" en una sesion grafica y nos mostrará algo como esto.





y con esto ya tendremos el tap click activado, espero que se de ayuda en algo.