Contenu | Rechercher | Menus

Annonce

Si vous rencontrez des soucis à rester connecté sur le forum (ou si vous avez perdu votre mot de passe) déconnectez-vous et reconnectez-vous depuis cette page, en cochant la case "Me connecter automatiquement lors de mes prochaines visites".
nombre réponses : 25

#0 -1 »  aide rootkit infection vers » Le 03/03/2015, à 18:40

Geronimo12
Réponses : 13

Bonjour,

je viens de faire ce qui est affiché ici : http://doc.ubuntu-fr.org/rootkit

avec Rkhunter, j'ai eu ceci :

Warning: The command '/usr/bin/unhide.rb' has been replaced by a script: /usr/bin/unhide.rb: Ruby script, ASCII text
Warning: User 'postfix' has been added to the passwd file.
Warning: Group 'postfix' has been added to the group file.
Warning: Group 'postdrop' has been added to the group file.
Warning: Suspicious file types found in /dev:
         /dev/.udev/rules.d/root.rules: ASCII text
Warning: Hidden directory found: /etc/.java: directory 
Warning: Hidden directory found: /dev/.udev: directory 
Warning: Hidden file found: /dev/.initramfs: symbolic link to `/run/initramfs' 
ixblanco@ixblanco-K53U:~$ 
ixblanco@ixblanco-K53U:~$ sudo rkhunter --propupd
[ Rootkit Hunter version 1.4.0 ]
File updated: searched for 168 files, found 135

avec chkrootkit :

j'ai eu ceci :

sudo apt-get install chkrootkit
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  chkrootkit
0 mis à jour, 1 nouvellement installés, 0 à enlever et 1 non mis à jour.
Il est nécessaire de prendre 319 ko dans les archives.
Après cette opération, 1 054 ko d'espace disque supplémentaires seront utilisés.
Réception de : 1 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main chkrootkit amd64 0.49-4.1ubuntu1.14.04.1 [319 kB]
319 ko réceptionnés en 0s (999 ko/s)
Préconfiguration des paquets...
Sélection du paquet chkrootkit précédemment désélectionné.
(Lecture de la base de données... 198735 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../chkrootkit_0.49-4.1ubuntu1.14.04.1_amd64.deb ...
Dépaquetage de chkrootkit (0.49-4.1ubuntu1.14.04.1) ...
Traitement des actions différées (« triggers ») pour man-db (2.6.7.1-1ubuntu1) ...
Paramétrage de chkrootkit (0.49-4.1ubuntu1.14.04.1) ...
ixblanco@ixblanco-K53U:~$  sudo chkrootkit -q

/usr/lib/python2.7/dist-packages/PyQt4/uic/widget-plugins/.noinit /usr/lib/jvm/.java-1.6.0-openjdk-amd64.jinfo

Warning: /sbin/init INFECTED
eth0: PACKET SNIFFER(/sbin/dhclient[1100])
user ixblanco deleted or never logged from lastlog!
 The tty of the following user process(es) were not found
 in /var/run/utmp !
! RUID          PID TTY    CMD
! root         1152 tty7   /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

pouvez vous m'aider ?

j'ai bien envie de faire les autres (lynis, tiger ) mais je crois que là je suis infecté ? non ?

#1 Re : -1 »  aide rootkit infection vers » Le 03/03/2015, à 22:45

Geronimo12
Réponses : 13

merci, voici :

#
#ALLOWHIDDENDIR="/etc/.java"
#ALLOWHIDDENDIR="/dev/.static"
#ALLOWHIDDENDIR="/dev/.SRC-unix"
#ALLOWHIDDENDIR="/etc/.etckeeper"

#
# Allow the specified hidden files to be whitelisted.
#
# This is a space-separated list of filenames. The option may
# be specified more than once. The option may use wildcard
# characters.
# 
#ALLOWHIDDENFILE="/etc/.java"
#ALLOWHIDDENFILE="/usr/share/man/man1/..1.gz"
#ALLOWHIDDENFILE="/etc/.pwd.lock"
#ALLOWHIDDENFILE="/etc/.init.state"
#ALLOWHIDDENFILE="/lib/.libcrypto.so.0.9.8e.hmac /lib/.libcrypto.so.6.hmac"
#ALLOWHIDDENFILE="/lib/.libssl.so.0.9.8e.hmac /lib/.libssl.so.6.hmac"
#ALLOWHIDDENFILE="/usr/bin/.fipscheck.hmac"
#ALLOWHIDDENFILE="/usr/bin/.ssh.hmac"
#ALLOWHIDDENFILE="/usr/lib/.libfipscheck.so.1.1.0.hmac"
#ALLOWHIDDENFILE="/usr/lib/.libfipscheck.so.1.hmac"
#ALLOWHIDDENFILE="/usr/lib/.libgcrypt.so.11.hmac"
#ALLOWHIDDENFILE="/usr/lib/hmaccalc/sha1hmac.hmac"
#ALLOWHIDDENFILE="/usr/lib/hmaccalc/sha256hmac.hmac"
#ALLOWHIDDENFILE="/usr/lib/hmaccalc/sha384hmac.hmac"
#ALLOWHIDDENFILE="/usr/lib/hmaccalc/sha512hmac.hmac"
#ALLOWHIDDENFILE="/usr/sbin/.sshd.hmac"
#ALLOWHIDDENFILE="/usr/share/man/man5/.k5login.5.gz"
#ALLOWHIDDENFILE="/etc/.gitignore"
#ALLOWHIDDENFILE="/etc/.bzrignore"

#
# Allow the specified processes to use deleted files. The
# process name may be followed by a colon-separated list of
# full pathnames. The process will then only be whitelisted
# if it is using one of the given files. For example:
#
#     ALLOWPROCDELFILE="/usr/libexec/gconfd-2:/tmp/abc:/var/tmp/xyz"
#
# This is a space-separated list of process names. The option
# may be specified more than once. The option may use wildcard
# characters, but only in the file names.
#
#ALLOWPROCDELFILE="/sbin/cardmgr /usr/sbin/gpm:/etc/X11/abc"
#ALLOWPROCDELFILE="/usr/lib/libgconf2-4/gconfd-2"
#ALLOWPROCDELFILE="/usr/sbin/mysqld:/tmp/ib*"
#ALLOWPROCDELFILE="/usr/lib/iceweasel/firefox-bin"
#ALLOWPROCDELFILE="/usr/bin/file-roller"

#
# Allow the specified processes to listen on any network interface.
#
# This is a space-separated list of process names. The option
# may be specified more than once.
#
#ALLOWPROCLISTEN="/sbin/dhclient /usr/bin/dhcpcd"
#ALLOWPROCLISTEN="/usr/sbin/pppoe /usr/sbin/tcpdump"
#ALLOWPROCLISTEN="/usr/sbin/snort-plain"

#
# Allow the specified network interfaces to be in promiscuous mode.
#
# This is a space-separated list of interface names. The option may
# be specified more than once.
#
#ALLOWPROMISCIF="eth0"

#
# SCAN_MODE_DEV governs how we scan '/dev' for suspicious files.
# The two allowed options are: THOROUGH or LAZY.
# If commented out we do a THOROUGH scan which will increase the runtime.
# Even though this adds to the running time it is highly recommended to
# leave it like this.
#
#SCAN_MODE_DEV=THOROUGH

#
# The PHALANX2_DIRTEST option is used to indicate if the Phalanx2 test is to
# perform a basic check, or a more thorough check. If the option is set to 0,
# then a basic check is performed. If it is set to 1, then all the directries
# in the /etc and /usr directories are scanned. The default value is 0. Users
# should note that setting this option to 1 will cause the test to take longer
# to complete.
#
PHALANX2_DIRTEST=0

#
# Allow the specified files to be present in the /dev directory,
# and not regarded as suspicious.
#
# This is a space-separated list of pathnames. The option may
# be specified more than once. The option may use wildcard
# characters.
#
#ALLOWDEVFILE="/dev/shm/pulse-shm-*"
#ALLOWDEVFILE="/dev/shm/sem.ADBE_*"

#
# This setting tells rkhunter where the inetd configuration
# file is located.
#
#INETD_CONF_PATH=/etc/inetd.conf

#
# Allow the following enabled inetd services.
#
# This is a space-separated list of service names. The option may
# be specified more than once.
#
# For non-Solaris users the simple service name should be used.
# For example:
#
#     INETD_ALLOWED_SVC=echo
#
# For Solaris 9 users the simple service name should also be used, but
# if it is an RPC service, then the executable pathname should be used.
# For example:
#
#     INETD_ALLOWED_SVC=imaps
#     INETD_ALLOWED_SVC="/usr/sbin/rpc.metad /usr/sbin/rpc.metamhd"
#
# For Solaris 10 users the service/FMRI name should be used. For example:
#
#     INETD_ALLOWED_SVC=/network/rpc/meta
#     INETD_ALLOWED_SVC=/network/rpc/metamed
#     INETD_ALLOWED_SVC=/application/font/stfsloader
#     INETD_ALLOWED_SVC=/network/rpc-100235_1/rpc_ticotsord
#
#INETD_ALLOWED_SVC=echo

#
# This setting tells rkhunter where the xinetd configuration
# file is located.
#
#XINETD_CONF_PATH=/etc/xinetd.conf

#
# Allow the following enabled xinetd services. Whilst it would be
# nice to use the service names themselves, at the time of testing
# we only have the pathname available. As such, these entries are
# the xinetd file pathnames.
#
# This is a space-separated list of service names. The option may
# be specified more than once.
#
#XINETD_ALLOWED_SVC=/etc/xinetd.d/echo

#
# This option tells rkhunter the local system startup file pathnames.
# The directories will be searched for files. By default rkhunter
# will use certain filenames and directories. If the option is set
# to 'none', then certain tests will be skipped.
#
# This is a space-separated list of file and directory pathnames.
# The option may be specified more than once. The option may use
# wildcard characters.
#
#STARTUP_PATHS="/etc/init.d /etc/rc.local"

#
# This setting tells rkhunter the pathname to the file containing the
# user account passwords. This setting will be worked out by rkhunter,
# and so should not usually need to be set. Users of TCB shadow files
# should not set this option.
#
#PASSWORD_FILE=/etc/shadow

#
# Allow the following accounts to be root equivalent. These accounts
# will have a UID value of zero. The 'root' account does not need to
# be listed as it is automatically whitelisted.
#
# This is a space-separated list of account names. The option may
# be specified more than once.
#
# NOTE: For *BSD systems you will probably need to use this option
# for the 'toor' account.
#
#UID0_ACCOUNTS="toor rooty sashroot"

#
# Allow the following accounts to have no password. NIS/YP entries do
# not need to be listed as they are automatically whitelisted.
#
# This is a space-separated list of account names. The option may
# be specified more than once.
#
#PWDLESS_ACCOUNTS="abc"

#
# This setting tells rkhunter the pathname to the syslog configuration
# file. This setting will be worked out by rkhunter, and so should not
# usually need to be set. A value of 'NONE' can be used to indicate
# that there is no configuration file, but that the syslog daemon process
# may be running.
#
# This is a space-separated list of pathnames. The option may
# be specified more than once.
#
#SYSLOG_CONFIG_FILE=/etc/syslog.conf

#
# This option permits the use of syslog remote logging.
#
ALLOW_SYSLOG_REMOTE_LOGGING=0

#
# Allow the following applications, or a specific version of an application,
# to be whitelisted. This option may be specified more than once, and is a
# space-separated list consisting of the application names. If a specific
# version is to be whitelisted, then the name must be followed by a colon
# and then the version number. For example:
#
#     APP_WHITELIST="openssl:0.9.7d gpg httpd:1.3.29"
#
# Note above that for the Apache web server, the name 'httpd' is used.
#
#APP_WHITELIST=""

# 
# Scan for suspicious files in directories containing temporary files and
# directories posing a relatively higher risk due to user write access.
# Please do not enable by default as suspscan is CPU and I/O intensive and prone to
# producing false positives. Do review all settings before usage.
# Also be aware that running suspscan in combination with verbose logging on,
# RKH's default, will show all ignored files.
# Please consider adding all directories the user the (web)server runs as has 
# write access to including the document root (example: "/var/www") and log
# directories (example: "/var/log/httpd"). 
#
# This is a space-separated list of directory pathnames.
# The option may be specified more than once.
#
#SUSPSCAN_DIRS="/tmp /var/tmp"

#
# Directory for temporary files. A memory-based one is better (faster).
# Do not use a directory name that is listed in SUSPSCAN_DIRS.
# Please make sure you have a tempfs mounted and the directory exists.
#
SUSPSCAN_TEMP=/dev/shm

#
# Maximum filesize in bytes. Files larger than this will not be inspected.
# Do make sure you have enough space left in your temporary files directory.
#
SUSPSCAN_MAXSIZE=10240000

#
# Score threshold. Below this value no hits will be reported.
# A value of "200" seems "good" after testing on malware. Please adjust
# locally if necessary. 
#
SUSPSCAN_THRESH=200

#
# The following option can be used to whitelist network ports which
# are known to have been used by malware. This option may be specified
# more than once. The option is a space-separated list of one or more
# of four types of whitelisting. These are:
#
#   1) a 'protocol:port' pair       (e.g. TCP:25)
#   2) a pathname to an executable  (e.g. /usr/sbin/squid)
#   3) a combined pathname, protocol and port
#                                   (e.g. /usr/sbin/squid:TCP:3801)
#   4) an asterisk ('*')
#
# Only the UDP or TCP protocol may be specified, and the port number
# must be between 1 and 65535 inclusive.
#
# The asterisk can be used to indicate that any executable which rkhunter
# can locate as a command, is whitelisted. (See BINDIR in this file.)
#
# For example:
#
#     PORT_WHITELIST="/home/user1/abc /opt/xyz TCP:2001 UDP:32011"
#
# NOTE: In order to whitelist a pathname, or use the asterisk option,
# the 'lsof' command must be present.
#
#PORT_WHITELIST=""

#
# The following option can be used to tell rkhunter where the operating
# system 'release' file is located. This file contains information
# specifying the current O/S version. RKH will store this information
# itself, and check to see if it has changed between each run. If it has
# changed, then the user is warned that RKH may issue warning messages
# until RKH has been run with the '--propupd' option.
#
# Since the contents of the file vary according to the O/S distribution,
# RKH will perform different actions when it detects the file itself. As
# such, this option should not be set unless necessary. If this option is
# specified, then RKH will assume the O/S release information is on the
# first non-blank line of the file.
#
#OS_VERSION_FILE="/etc/debian_version"

#
# The following two options can be used to whitelist files and directories
# that would normally be flagged with a warning during the various rootkit
# and malware checks. If the file or directory name contains a space, then
# the percent character ('%') must be used instead. Only existing files and
# directories can be specified, and these must be full pathnames not links.
#
# Additionally, the RTKT_FILE_WHITELIST option may include a string after the
# file name (separated by a colon). This will then only whitelist that string
# in that file (as part of the malware checks). For example:
#
#     RTKT_FILE_WHITELIST="/etc/rc.local:hdparm"
#
# If the option list includes the filename on its own as well, then the file
# will be whitelisted from rootkit checks of the files existence, but still
# only the specific string within the file will be whitelisted. For example:
#
#     RTKT_FILE_WHITELIST="/etc/rc.local:hdparm /etc/rc.local"
#
# To whitelist a file from the existence checks, but not from the strings
# checks, then include the filename on its own and on its own but with
# just a colon appended. For example:
#
#     RTKT_FILE_WHITELIST="/etc/rc.local /etc/rc.local:"
#
# NOTE: It is recommended that if you whitelist any files, then you include
# those files in the file properties check. See the USER_FILEPROP_FILES_DIRS
# configuration option.
#
# These are space-separated lists of file and directory pathnames.
# The options may be specified more than once.
#
#RTKT_DIR_WHITELIST=""
#RTKT_FILE_WHITELIST=""

#
# The following option can be used to whitelist shared library files that would
# normally be flagged with a warning during the preloaded shared library check.
# These library pathnames usually exist in the '/etc/ld.so.preload' file or in
# the LD_PRELOAD environment variable.
#
# NOTE: It is recommended that if you whitelist any files, then you include
# those files in the file properties check. See the USER_FILEPROP_FILES_DIRS
# configuration option.
#
# This is a space-separated list of library pathnames.
# The option may be specified more than once.
#
#SHARED_LIB_WHITELIST="/lib/snoopy.so"

#
# To force rkhunter to use the supplied script for the 'stat' or 'readlink'
# command, then the following two options can be used. The value must be
# set to 'BUILTIN'.
#
# NOTE: IRIX users will probably need to enable STAT_CMD.
#
#STAT_CMD=BUILTIN
#READLINK_CMD=BUILTIN

#
# In the file properties test any modification date/time is displayed as the
# number of epoch seconds. Rkhunter will try and use the 'date' command, or
# failing that the 'perl' command, to display the date and time in a
# human-readable format as well. This option may be used if some other command
# should be used instead. The given command must understand the '%s' and
# 'seconds ago' options found in the GNU date command.
#
# A value of 'NONE' may be used to request that only the epoch seconds be shown.
# A value of 'PERL' may be used to force rkhunter to use the 'perl' command, if
# it is present.
#
#EPOCH_DATE_CMD=""

#
# This setting tells rkhunter the directory containing the available
# Linux kernel modules. This setting will be worked out by rkhunter,
# and so should not usually need to be set.
#
#MODULES_DIR=""

#
# The following option can be set to a command which rkhunter will use when
# downloading files from the Internet - that is, when the '--update' or
# '--versioncheck' option is used. The command can take options.
#
# This allows the user to use a command other than the one automatically
# selected by rkhunter, but still one which it already knows about.
# For example:
#
#     WEB_CMD=curl
#
# Alternatively, the user may specify a completely new command. However, note
# that rkhunter expects the downloaded file to be written to stdout, and that
# everything written to stderr is ignored. For example:
#
#     WEB_CMD="/opt/bin/dlfile --timeout 5m -q"
#
# *BSD users may want to use the 'ftp' command, provided that it supports
# the HTTP protocol:
#
#     WEB_CMD="ftp -o -"
#
#WEB_CMD=""

#
# Set the following option to 0 if you do not want to receive a warning if
# any O/S information has changed since the last run of 'rkhunter --propupd'.
# The warnings occur during the file properties check. The default is to
# issue a warning if something has changed.
#
#WARN_ON_OS_CHANGE=1

#
# Set the following option to 1 if you want rkhunter to automatically run
# a file properties update ('--propupd') if the O/S has changed. Detection
# of an O/S change occurs during the file properties check. The default is
# not to do an automatic update.
#
# WARNING: Only set this option if you are sure that the update will work
# correctly. That is, that the database directory is writeable, that a valid
# hash function is available, and so on. This can usually be checked simply
# by running 'rkhunter --propupd' at least once.
#
#UPDT_ON_OS_CHANGE=0

#
# Set the following option to 1 if locking is to be used when rkhunter runs.
# The lock is set just before logging starts, and is removed when the program
# ends. It is used to prevent items such as the log file, and the file
# properties file, from becoming corrupted if rkhunter is running more than
# once. The mechanism used is to simply create a lock file in the TMPDIR
# directory. If the lock file already exists, because rkhunter is already
# running, then the current process simply loops around sleeping for 10 seconds
# and then retrying the lock.
#
# The default is not to use locking.
#
USE_LOCKING=0

#
# If locking is used, then rkhunter may have to wait to get the lock file.
# This option sets the total amount of time, in seconds, that rkhunter should
# wait. It will retry the lock every 10 seconds, until either it obtains the
# lock or the timeout value has been reached. If no value is set, then a
# default of 300 seconds (5 minutes) is used.
#
LOCK_TIMEOUT=300

#
# If locking is used, then rkhunter may be doing nothing for some time if it
# has to wait for the lock. Some simple messages are echo'd to the users screen
# to let them know that rkhunter is waiting for the lock. Set this option to 0
# if the messages are not to be displayed. The default is to show them.
#
SHOW_LOCK_MSGS=1

#
# If the option SCANROOTKITMODE is set to "THOROUGH" the scanrootkit() function
# will search (on a per rootkit basis) for filenames in all of the directories (as defined
# by the result of running 'find / -xdev'). While still not optimal, as it 
# still searches for only file names as opposed to file contents, this is one step away
# from the rigidity of searching in known (evidence) or default (installation) locations.
#
# THIS OPTION SHOULD NOT BE ENABLED BY DEFAULT.
#
# You should only activate this feature as part of a more thorough investigation which
# should be based on relevant best practices and procedures. 
#
# Enabling this feature implies you have the knowledge to interpret the results properly. 
#
#SCANROOTKITMODE=THOROUGH

#
# The following option can be set to the name(s) of the tests the 'unhide' command is
# to use. In order to maintain compatibility with older versions of 'unhide', this
# option defaults to 'sys'. Options such as '-m' and '-v' may also be specified, but
# will only take effect when they are seen. The test names are a space-separated list,
# and will be executed in the order given.
#
#UNHIDE_TESTS="sys"

#
# If both the C 'unhide', and Ruby 'unhide.rb', programs exist on the system, then it
# is possible to disable the execution of one of the programs if desired. By default
# rkhunter will look for both programs, and execute each of them as they are found.
# If the value of this option is 0, then both programs will be executed if they are
# present. A value of 1 will disable execution of the C 'unhide' program, and a value
# of 2 will disable the Ruby 'unhide.rb' program. The default value is 0. To disable
# both programs, then disable the 'hidden_procs' test.
#
DISABLE_UNHIDE=1

INSTALLDIR="/usr"

#2 Re : -1 »  aide rootkit infection vers » Le 03/03/2015, à 22:46

Geronimo12
Réponses : 13

et mon scan avec clamav a donné ceci :

---------- SCAN SUMMARY -----------
Known viruses: 3756234
Engine version: 0.98.6
Scanned directories: 30747
Scanned files: 163748
Infected files: 44
Total errors: 18726
Data scanned: 21860.10 MB
Data read: 275836.97 MB (ratio 0.08:1)
Time: 9745.212 sec (162 m 25 s)


mais je ne sais pas quoi faire avec ces résultats ???

#3 Re : -1 »  aide rootkit infection vers » Hier à 09:54

Geronimo12
Réponses : 13

merci beaucoup de ta réponse super claire Tiramiseb,

voici la réponse à la commande : file /sbin/init
/sbin/init: ELF 64-bit LSB  shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=7a4c688d009fc1f06ffc692f5f42ab09e68582b2, stripped


pour ixblanco, c'est mon nom d'utilisateur sur lequel je me connecte toujours ??? je ne comprend pas ??

#4 Re : -1 »  aide rootkit infection vers » Hier à 10:17

Geronimo12
Réponses : 13

voici la réponse :

ixblanco pts/0        :0               Wed Mar  4 09:52   still logged in   
ixblanco :0           :0               Wed Mar  4 09:35   still logged in   
ixblanco :0           :0               Wed Mar  4 08:51 - down   (00:06)    
ixblanco :0           :0               Tue Mar  3 23:01 - down   (00:15)    
ixblanco pts/11       :0               Tue Mar  3 18:18 - 18:18  (00:00)    
ixblanco pts/0        :0               Tue Mar  3 18:16 - 22:55  (04:38)    
ixblanco :0           :0               Tue Mar  3 18:07 - down   (04:49)    
ixblanco :0           :0               Tue Mar  3 10:24 - down   (00:16)    
ixblanco :0           :0               Tue Mar  3 09:11 - down   (01:08)    
ixblanco :0           :0               Mon Mar  2 22:24 - down   (00:46)    
ixblanco :0           :0               Mon Mar  2 14:28 - down   (03:53)    
ixblanco pts/6        :0               Mon Mar  2 13:59 - down   (00:27)    
ixblanco pts/6        :0               Mon Mar  2 13:03 - 13:50  (00:46)    

wtmp begins Mon Mar  2 13:03:37 2015

et pour les résultats de l'antivirus clamav, c'est bon pour toi ?

#5 Re : -1 »  aide rootkit infection vers » Hier à 16:28

Geronimo12
Réponses : 13

non je t'ai mis tout ce qu'il a affiché... neutral

#6 Re : -1 »  aide rootkit infection vers » Aujourd'hui à 09:51

Geronimo12
Réponses : 13

merci,
bizarre je n'ai pas de partition windosienne ;-)

j'ai installé clamav en ligne de commande ici :
http://doc.ubuntu-fr.org/clamav

puis après j'ai vu qu'il y avait une interface graphique mais seulement après le scan complet du disque dur...

ya peut-être moyen de récupérer l'historique en ligne de commande mais dans avec l'interface graphique, l'historique est vide pour le coup...

#7 -1 »  aide suppression ancien noyaux [RESOLU] » Le 02/03/2015, à 14:03

Geronimo12
Réponses : 18

Bonjour,

afin de ne pas faire d'erreur, en gardant les deux derniers apparemment, mais comme je les vois en double, je préfère demander

pourriez vous me dire lesquels je dois absolument garder svp parmis cette liste :

~$ dpkg -l | grep -Ei "linux-headers|linux-image"
ii  linux-headers-3.13.0-36                          3.13.0-36.63                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-36-generic                  3.13.0-36.63                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-37                          3.13.0-37.64                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-37-generic                  3.13.0-37.64                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-38                          3.13.0-38.65                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-38-generic                  3.13.0-38.65                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-39                          3.13.0-39.66                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-39-generic                  3.13.0-39.66                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-40                          3.13.0-40.69                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-40-generic                  3.13.0-40.69                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-41                          3.13.0-41.70                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-41-generic                  3.13.0-41.70                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-43                          3.13.0-43.72                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-43-generic                  3.13.0-43.72                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-44                          3.13.0-44.73                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-44-generic                  3.13.0-44.73                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-45                          3.13.0-45.74                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-45-generic                  3.13.0-45.74                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-3.13.0-46                          3.13.0-46.76                                        all          Header files related to Linux kernel version 3.13.0
ii  linux-headers-3.13.0-46-generic                  3.13.0-46.76                                        amd64        Linux kernel headers for version 3.13.0 on 64 bit x86 SMP
ii  linux-headers-generic                            3.13.0.46.53                                        amd64        Generic Linux kernel headers
ii  linux-image-3.13.0-36-generic                    3.13.0-36.63                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-37-generic                    3.13.0-37.64                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-38-generic                    3.13.0-38.65                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-39-generic                    3.13.0-39.66                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-40-generic                    3.13.0-40.69                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-41-generic                    3.13.0-41.70                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-43-generic                    3.13.0-43.72                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-44-generic                    3.13.0-44.73                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-45-generic                    3.13.0-45.74                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.13.0-46-generic                    3.13.0-46.76                                        amd64        Linux kernel image for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-3.2.0-68-generic                     3.2.0-68.102                                        amd64        Linux kernel image for version 3.2.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-36-generic              3.13.0-36.63                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-37-generic              3.13.0-37.64                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-38-generic              3.13.0-38.65                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-39-generic              3.13.0-39.66                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-40-generic              3.13.0-40.69                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-41-generic              3.13.0-41.70                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-43-generic              3.13.0-43.72                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-44-generic              3.13.0-44.73                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-45-generic              3.13.0-45.74                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-extra-3.13.0-46-generic              3.13.0-46.76                                        amd64        Linux kernel extra modules for version 3.13.0 on 64 bit x86 SMP
ii  linux-image-generic                              3.13.0.46.53                                        amd64        Generic Linux kernel image

#8 Re : -1 »  aide suppression ancien noyaux [RESOLU] » Le 02/03/2015, à 14:07

Geronimo12
Réponses : 18

est-ce que ubuntu tweak est viable ?

merci ;-)

#9 Re : -1 »  aide suppression ancien noyaux [RESOLU] » Le 03/03/2015, à 18:29

Geronimo12
Réponses : 18

merci à tous, j'ai utilisé ubuntu tweak et tout vas très bien...

#10 Re : -1 »  aide suppression ancien noyaux [RESOLU] » Le 03/03/2015, à 22:49

Geronimo12
Réponses : 18

amusant de voir le partage sur un sujet :-)

voulez vous que je le mette en résolu ? ou attendre ?

#11 -1 »  problème montage disque dur externe » Le 11/02/2015, à 13:36

Geronimo12
Réponses : 1

Bonjour,

Je n'arrive pas à connecter mon disque dur externe WD, utilisé avant sur un mac...

voici le message d'erreur :

mini_187024Capturedu20150211132742.png

Pouvez-vous m'aidez svp ?

merci d'avance

#12 -1 »  étrange : bruit de fond musical permanent ???[RÉSOLU] » Le 21/01/2015, à 16:00

Geronimo12
Réponses : 10

Bonjour,

me voila avec un étrange problème,

j'ai un ordi portable sur lequel sont branché mes enceintes...

mais voila, il n'y a rien qui tourne sur mon ordi mais pourtant j'ai un fond musical ou le son est très bas en permanence dans mes enceintes ????

comme si je captais une radio ??? vous voyez ??

merci d'avance pour vos éclaircissements

ps, je suis en wifi...

#13 Re : -1 »  étrange : bruit de fond musical permanent ???[RÉSOLU] » Le 22/01/2015, à 06:30

Geronimo12
Réponses : 10

merci, voici :

  PID  PGID   SID TTY          TIME CMD
    2     0     0 ?        00:00:00 kthreadd
    3     0     0 ?        00:00:00   ksoftirqd/0
    5     0     0 ?        00:00:00   kworker/0:0H
    6     0     0 ?        00:00:01   kworker/u4:0
    7     0     0 ?        00:00:01   rcu_sched
    8     0     0 ?        00:00:00   rcuos/0
    9     0     0 ?        00:00:01   rcuos/1
   10     0     0 ?        00:00:00   rcu_bh
   11     0     0 ?        00:00:00   rcuob/0
   12     0     0 ?        00:00:00   rcuob/1
   13     0     0 ?        00:00:00   migration/0
   14     0     0 ?        00:00:00   watchdog/0
   15     0     0 ?        00:00:00   watchdog/1
   16     0     0 ?        00:00:01   migration/1
   17     0     0 ?        00:00:00   ksoftirqd/1
   19     0     0 ?        00:00:00   kworker/1:0H
   20     0     0 ?        00:00:00   khelper
   21     0     0 ?        00:00:00   kdevtmpfs
   22     0     0 ?        00:00:00   netns
   23     0     0 ?        00:00:00   writeback
   24     0     0 ?        00:00:00   kintegrityd
   25     0     0 ?        00:00:00   bioset
   26     0     0 ?        00:00:00   kworker/u5:0
   27     0     0 ?        00:00:00   kblockd
   28     0     0 ?        00:00:00   ata_sff
   29     0     0 ?        00:00:00   khubd
   30     0     0 ?        00:00:00   md
   31     0     0 ?        00:00:00   devfreq_wq
   32     0     0 ?        00:00:02   kworker/1:1
   33     0     0 ?        00:00:00   kworker/0:1
   34     0     0 ?        00:00:00   khungtaskd
   35     0     0 ?        00:00:00   kswapd0
   36     0     0 ?        00:00:00   ksmd
   37     0     0 ?        00:00:00   khugepaged
   38     0     0 ?        00:00:00   fsnotify_mark
   39     0     0 ?        00:00:00   ecryptfs-kthrea
   40     0     0 ?        00:00:00   crypto
   52     0     0 ?        00:00:00   kthrotld
   63     0     0 ?        00:00:02   kworker/0:2
   74     0     0 ?        00:00:00   deferwq
   75     0     0 ?        00:00:00   charger_manager
  122     0     0 ?        00:00:00   scsi_eh_0
  123     0     0 ?        00:00:00   scsi_eh_1
  124     0     0 ?        00:00:00   scsi_eh_2
  125     0     0 ?        00:00:00   scsi_eh_3
  129     0     0 ?        00:00:00   scsi_eh_4
  130     0     0 ?        00:00:00   scsi_eh_5
  132     0     0 ?        00:00:00   kpsmoused
  134     0     0 ?        00:00:00   kworker/1:2
  149     0     0 ?        00:00:00   jbd2/sda1-8
  150     0     0 ?        00:00:00   ext4-rsv-conver
  316     0     0 ?        00:00:00   kworker/u5:1
  373     0     0 ?        00:00:00   cfg80211
  424     0     0 ?        00:00:00   kvm-irqfd-clean
  452     0     0 ?        00:00:00   hd-audio0
  457     0     0 ?        00:00:00   hd-audio1
  497     0     0 ?        00:00:00   led_workqueue
  528     0     0 ?        00:00:00   krfcommd
 1185     0     0 ?        00:00:00   firegl
 1186     0     0 ?        00:00:00   firegl
 1187     0     0 ?        00:00:00   firegl
 1208     0     0 ?        00:00:00   kauditd
 2582     0     0 ?        00:00:00   kworker/u4:1
 2692     0     0 ?        00:00:00   kworker/u4:2
    1     1     1 ?        00:00:04 init
  273   271   271 ?        00:00:00   upstart-udev-br
  277   277   277 ?        00:00:00   systemd-udevd
  443   443   443 ?        00:00:02   dbus-daemon
  467   467   467 ?        00:00:00   rsyslogd
  507   507   507 ?        00:00:00   bluetoothd
  574   574   574 ?        00:00:00   systemd-logind
  613   611   611 ?        00:00:00   avahi-daemon
  614   611   611 ?        00:00:00     avahi-daemon
  680   680   680 ?        00:00:00   ModemManager
  763   763   763 ?        00:00:02   NetworkManager
 1285  1285   763 ?        00:00:00     dhclient
 1397  1397   763 ?        00:00:00     dnsmasq
  824   443   443 ?        00:00:01   polkitd
  854   853   853 ?        00:00:00   upstart-socket-
  857   856   856 ?        00:00:00   upstart-file-br
  883   883   883 ?        00:00:00   wpa_supplicant
  908   908   908 tty4     00:00:00   getty
  912   912   912 tty5     00:00:00   getty
  920   920   920 tty2     00:00:00   getty
  921   921   921 tty3     00:00:00   getty
  925   925   925 tty6     00:00:00   getty
 1013  1013  1013 ?        00:00:00   cron
 1014  1014  1014 ?        00:00:00   atd
 1017  1017  1017 ?        00:00:00   acpid
 1029  1029  1029 ?        00:00:00   kerneloops
 1091  1091  1091 ?        00:00:00   cups-browsed
 1131  1131  1131 tty1     00:00:00   getty
 1137  1137  1137 ?        00:00:00   whoopsie
 1153  1153  1153 ?        00:00:00   lightdm
 1166  1166  1166 tty7     00:01:11     Xorg
 1266  1153  1153 ?        00:00:00     lightdm
 1793  1793  1793 ?        00:00:00       init
 1867  1867  1867 ?        00:00:01         dbus-daemon
 1876  1876  1876 ?        00:00:00         upstart-event-b
 1881  1881  1881 ?        00:00:02         ibus-daemon
 1916  1881  1881 ?        00:00:00           ibus-dconf
 1928  1881  1881 ?        00:00:01           ibus-ui-gtk3
 1977  1881  1881 ?        00:00:00           ibus-engine-sim
 1885  1885  1885 ?        00:00:00         window-stack-br
 1903  1903  1903 ?        00:00:01         unity-settings-
 1991  1903  1903 ?        00:00:00           syndaemon
 1906  1867  1867 ?        00:00:00         gvfsd
 1910  1867  1867 ?        00:00:00         gvfsd-fuse
 1922  1922  1922 ?        00:00:02         hud-service
 1925  1923  1923 ?        00:00:00         upstart-dbus-br
 1927  1927  1927 ?        00:00:00         at-spi-bus-laun
 1934  1927  1927 ?        00:00:00           dbus-daemon
 1929  1929  1929 ?        00:00:00         gnome-session
 2156  1929  1929 ?        00:00:56           compiz
 2168  1929  1929 ?        00:00:00           polkit-gnome-au
 2171  1929  1929 ?        00:00:01           nm-applet
 2176  1929  1929 ?        00:00:02           my-weather-indi
 2180  1929  1929 ?        00:00:04           nautilus
 2182  1929  1929 ?        00:00:00           unity-fallback-
 2456  1929  1929 ?        00:00:00           update-notifier
 2564  1929  1929 ?        00:00:00           deja-dup-monito
 1939  1881  1881 ?        00:00:00         ibus-x11
 1942  1927  1927 ?        00:00:00         at-spi2-registr
 1943  1943  1943 ?        00:00:06         unity-panel-ser
 1953  1944  1944 ?        00:00:00         upstart-dbus-br
 1955  1954  1954 ?        00:00:00         upstart-file-br
 1968  1867  1867 ?        00:00:01         bamfdaemon
 1993  1867  1867 ?        00:00:00         dconf-service
 1999  1998  1998 ?        00:00:24         pulseaudio
 2003  1998  1998 ?        00:00:00           gconf-helper
 2005  1867  1867 ?        00:00:00         gconfd-2
 2012  1867  1867 ?        00:00:00         indicator-keybo
 2032  2032  2032 ?        00:00:00         indicator-messa
 2037  2037  2037 ?        00:00:00         indicator-bluet
 2040  2040  2040 ?        00:00:00         indicator-power
 2044  2044  2044 ?        00:00:00         indicator-datet
 2045  2045  2045 ?        00:00:00         indicator-sound
 2050  2050  2050 ?        00:00:00         indicator-print
 2057  2057  2057 ?        00:00:00         indicator-sessi
 2070  2070  2070 ?        00:00:00         indicator-appli
 2081  1867  1867 ?        00:00:00         evolution-sourc
 2102  1867  1867 ?        00:00:01         notify-osd
 2164  1867  1867 ?        00:00:00         goa-daemon
 2167  1867  1867 ?        00:00:01         evolution-calen
 2196  1867  1867 ?        00:00:00         gvfs-udisks2-vo
 2209  1867  1867 ?        00:00:00         mission-control
 2214  1867  1867 ?        00:00:00         gvfs-gphoto2-vo
 2220  1867  1867 ?        00:00:00         gvfs-mtp-volume
 2228  1867  1867 ?        00:00:00         gvfs-afc-volume
 2242  1867  1867 ?        00:00:00         gvfsd-burn
 2260  1867  1867 ?        00:00:00         gvfsd-trash
 2313  1867  1867 ?        00:00:00         gvfsd-metadata
 2331  1929  1929 ?        00:05:29         firefox
 2648  1929  1929 ?        00:04:34           plugin-containe
 2344  1929  1929 ?        00:00:44         thunderbird
 2380  1867  1867 ?        00:00:00         unity-webapps-s
 2523  1929  1929 ?        00:00:00         oosplash
 2542  1929  1929 ?        00:00:05           soffice.bin
 2724  1929  1929 ?        00:00:01         gnome-terminal
 2732  1929  1929 ?        00:00:00           gnome-pty-helpe
 2733  2733  2733 pts/0    00:00:00           bash
 2781  2781  2733 pts/0    00:00:00             ps
 1169   443   443 ?        00:00:00   accounts-daemon
 1305   443   443 ?        00:00:00   upowerd
 1344   443   443 ?        00:00:00   rtkit-daemon
 1578   443   443 ?        00:00:00   colord
 1768  1768  1768 ?        00:00:00   cupsd
 1772  1772  1768 ?        00:00:00     dbus
 1773  1773  1768 ?        00:00:00     dbus
 1774  1774  1768 ?        00:00:00     dbus
 1791  1790  1790 ?        00:00:00   gnome-keyring-d
 2199   443   443 ?        00:00:00   udisksd

et :

ps -U root -u root u -jH
USER       PID  PGID   SID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         2     0     0  0.0  0.0      0     0 ?        S    06:13   0:00 [kt
root         3     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root         5     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root         6     0     0  0.1  0.0      0     0 ?        S    06:13   0:01   [
root         7     0     0  0.1  0.0      0     0 ?        S    06:13   0:01   [
root         8     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root         9     0     0  0.1  0.0      0     0 ?        S    06:13   0:01   [
root        10     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        11     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        12     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        13     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        14     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        15     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        16     0     0  0.1  0.0      0     0 ?        S    06:13   0:01   [
root        17     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        19     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        20     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        21     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        22     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        23     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        24     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        25     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        26     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        27     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        28     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        29     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        30     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        31     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        32     0     0  0.2  0.0      0     0 ?        S    06:13   0:02   [
root        33     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        34     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        35     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        36     0     0  0.0  0.0      0     0 ?        SN   06:13   0:00   [
root        37     0     0  0.0  0.0      0     0 ?        SN   06:13   0:00   [
root        38     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        39     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root        40     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        52     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        63     0     0  0.2  0.0      0     0 ?        S    06:13   0:02   [
root        74     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root        75     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       122     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       123     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       124     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       125     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       129     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       130     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       132     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       134     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       149     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root       150     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       316     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       373     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       424     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       452     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       457     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       497     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root       528     0     0  0.0  0.0      0     0 ?        S<   06:13   0:00   [
root      1185     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root      1186     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root      1187     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root      1208     0     0  0.0  0.0      0     0 ?        S    06:13   0:00   [
root      2582     0     0  0.1  0.0      0     0 ?        S    06:19   0:00   [
root      2692     0     0  0.1  0.0      0     0 ?        S    06:24   0:00   [
root         1     1     1  0.4  0.0  33912  3188 ?        Ss   06:13   0:04 /sb
root       273   271   271  0.0  0.0  19608   912 ?        S    06:13   0:00   u
root       277   277   277  0.0  0.0  51760  1980 ?        Ss   06:13   0:00   /
root       507   507   507  0.0  0.0  19292  1464 ?        Ss   06:13   0:00   /
root       574   574   574  0.0  0.0  43544  1912 ?        Ss   06:13   0:00   /
root       680   680   680  0.0  0.1 330236  4416 ?        Ssl  06:13   0:00   /
root       763   763   763  0.3  0.2 344112  8928 ?        Ssl  06:13   0:03   N
root      1285  1285   763  0.0  0.1  10232  3720 ?        S    06:13   0:00    
root       824   443   443  0.1  0.1 280944  4980 ?        Sl   06:13   0:01   /
root       854   853   853  0.0  0.0  15656   980 ?        S    06:13   0:00   u
root       857   856   856  0.0  0.0  15936  1200 ?        S    06:13   0:00   u
root       883   883   883  0.0  0.0  30608  2736 ?        Ss   06:13   0:00   /
root       908   908   908  0.0  0.0  18536   944 tty4     Ss+  06:13   0:00   /
root       912   912   912  0.0  0.0  18536   948 tty5     Ss+  06:13   0:00   /
root       920   920   920  0.0  0.0  18536   944 tty2     Ss+  06:13   0:00   /
root       921   921   921  0.0  0.0  18536   944 tty3     Ss+  06:13   0:00   /
root       925   925   925  0.0  0.0  18536   960 tty6     Ss+  06:13   0:00   /
root      1013  1013  1013  0.0  0.0  23656  1008 ?        Ss   06:13   0:00   c
daemon    1014  1014  1014  0.0  0.0  19140   164 ?        Ss   06:13   0:00   a
root      1017  1017  1017  0.0  0.0   4368   704 ?        Ss   06:13   0:00   a
root      1091  1091  1091  0.0  0.0  75484  3416 ?        Ss   06:13   0:00   /
root      1131  1131  1131  0.0  0.0  18536   948 tty1     Ss+  06:13   0:00   /
root      1153  1153  1153  0.0  0.1 351620  3820 ?        SLsl 06:13   0:00   l
root      1166  1166  1166  8.1  4.0 466096 148564 tty7    Ss+  06:13   1:19    
root      1266  1153  1153  0.0  0.1 174624  3800 ?        Sl   06:13   0:00    
root      1169   443   443  0.0  0.1 287464  6272 ?        Sl   06:13   0:00   /
root      1305   443   443  0.0  0.1 239408  4664 ?        Sl   06:13   0:00   /
root      1768  1768  1768  0.0  0.1  77476  4500 ?        Ss   06:14   0:00   /
root      2199   443   443  0.1  0.1 371424  5156 ?        Sl   06:16   0:00   /

#14 Re : -1 »  étrange : bruit de fond musical permanent ???[RÉSOLU] » Le 24/01/2015, à 13:22

Geronimo12
Réponses : 10

merci, je viens de tester killall firefox... et la je n'ai plus rien.. cool
merci beaucoup f.x0

#15 Re : -1 »  étrange : bruit de fond musical permanent ???[RÉSOLU] » Le 25/01/2015, à 15:16

Geronimo12
Réponses : 10

merci, tiramiseb, que veux tu dire par : "ne garde pas un onglet de firefox sur Deeze"

#16 Re : -1 »  étrange : bruit de fond musical permanent ???[RÉSOLU] » Le 29/01/2015, à 16:39

Geronimo12
Réponses : 10

ok merci tiramiseb de ta précision mais non je n'avais rien d'ouvert ;-)

#17 -1 »  ghostery, extension firefox, remise a zero a chaque nouvelle ??? » Le 23/10/2014, à 15:29

Geronimo12
Réponses : 10

Bonjour,

Ghostery se remet à zéro à chaque mise à jour ?

comment éviter si cela est évitable ? merci d'avance

#18 Re : -1 »  ghostery, extension firefox, remise a zero a chaque nouvelle ??? » Le 26/10/2014, à 16:01

Geronimo12
Réponses : 10

ai je posté ce post dans la mauvaise rubrique ?

#19 Re : -1 »  ghostery, extension firefox, remise a zero a chaque nouvelle ??? » Le 21/01/2015, à 15:51

Geronimo12
Réponses : 10

je reformule mon soucis, à chaque mise a jour de firefox, je perds les paramètres ghostery, en gros a chaque fois je dois tout rebloquer...

je vais essayer ce que dit zigzagonal, merci a tous

suite a la prochaine mise a jour car j'en ai eu une hier ;-)

#20 Re : -1 »  ghostery, extension firefox, remise a zero a chaque nouvelle ??? » Le 29/01/2015, à 16:38

Geronimo12
Réponses : 10

voila la mise a jour de firefox faite, Ghostery est remis à zéro....ggrrrr...

je dois encore reprogrammer, recocher tous les mouchards...

quelqu'un aurait-il une autre solution ?

#21 -1 »  télécharger et installer un paquet » Le 31/12/2014, à 11:50

Geronimo12
Réponses : 2

bonjour,

lorsque je clic sur le forum, sur un lien de paquets à télécharger, ma fenêtre d'ouverture me met automatiquement sur la logithèque.

je souhaite donc savoir sur quel logiciel je dois mettre l'ouverture du paquet afin qu'il s'installe tout seul ???

ou alors j'ai pas bien compris ???

merci d'avance

#22 -1 »  impossible d'acceder a disque audio » Le 25/10/2014, à 11:52

Geronimo12
Réponses : 1

comme dans le titre, voila je n’accède pas à mes disques audio, PC portable asus x53u

voici le message : Message did not receive a reply (timeout by message bus)

avez vous une solution svp ?

merci d'avance

#23 Re : -1 »  impossible d'acceder a disque audio » Le 26/10/2014, à 16:02

Geronimo12
Réponses : 1

quelqu'un a -t-il une solution svp ?

#24 Re : -1 »  autorisation suppression fichier lecteur mp3 » Le 03/05/2014, à 16:43

Geronimo12
Réponses : 2

quelqu'un peut-il m'aider ? ou ma question n'est pas assez précise ?
merci d'avance