Results 1 to 5 of 5
I have a Ubuntu 7.04-fiesty fawn on my machine and it has problem with synaptic.
When I try to install any package by aptitude,dpkg or by synaptic it says segmentation ...
- 10-16-2007 #1Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
synaptic
I have a Ubuntu 7.04-fiesty fawn on my machine and it has problem with synaptic.
When I try to install any package by aptitude,dpkg or by synaptic it says segmentation fault(core dumped).
I have done one thing as suggested by some guys familiar with linux
I have gone to location /var/cache/apt/archives and deleted the lock file that was there.
Can anypne help me with this.
Regards,
tech_rex....
- 10-16-2007 #2
Hi and Welcome !
Execute this
Post exact error message here, if any.Code:sudo apt-get clean all sudo apt-get update
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 10-16-2007 #3Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
thanks for your reply here is the error that I get
root@fablab-desktop:/home/fablab# sudo apt-get clean all
root@fablab-desktop:/home/fablab# sudo apt-get update
Segmentation fault (core dumped)
[ALSO WHEN I TRY synaptic here is the thing that I get
root@fablab-desktop:/home/fablab# synaptic
Segmentation fault (core dumped)
root@fablab-desktop:/home/fablab#
- 10-16-2007 #4
Post the contents of limits.conf file here.
Code:cat /etc/security/limits.conf
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 10-17-2007 #5Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
fablab@fablab-desktop:~$ cat /etc/security/limits.conf
# /etc/security/limits.conf
#
#Each line describes a limit for a user in the form:
#
#<domain> <type> <item> <value>
#
#Where:
#<domain> can be:
# - an user name
# - a group name, with @group syntax
# - the wildcard *, for default entry
# - the wildcard %, can be also used with %group syntax,
# for maxlogin limit
#
#<type> can have the two values:
# - "soft" for enforcing the soft limits
# - "hard" for enforcing hard limits
#
#<item> can be one of the following:
# - core - limits the core file size (KB)
# - data - max data size (KB)
# - fsize - maximum filesize (KB)
# - memlock - max locked-in-memory address space (KB)
# - nofile - max number of open files
# - rss - max resident set size (KB)
# - stack - max stack size (KB)
# - cpu - max CPU time (MIN)
# - nproc - max number of processes
# - as - address space limit
# - maxlogins - max number of logins for this user
# - maxsyslogins - max number of logins on the system
# - priority - the priority to run user process with
# - locks - max number of file locks the user can hold
# - sigpending - max number of pending signals
# - msgqueue - max memory used by POSIX message queues (bytes)
# - nice - max nice priority allowed to raise to
# - rtprio - max realtime priority
#
#<domain> <type> <item> <value>
#
#* soft core 0
#* hard rss 10000
#@student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
#ftp hard nproc 0
#@student - maxlogins 4
# End of file
tech_rex,
Pune..


Reply With Quote
