Are you a spammer

Please note, that the first 3 posts you make, will need to be approved by a forum Administrator or Moderator before they are publicly viewable.
Each application to join this forum is checked at the Stop Forum Spam website. If the email or IP address appears there when checked, you will not be allowed to join this forum.
If you get past this check and post spam on this forum, your posts will be immediately deleted and your account inactivated.You will then be banned and your IP will be submitted to your ISP, notifying them of your spamming. So your spam links will only be seen for an hour or two at most. In other words, don't waste your time and ours.

This forum is for the use and enjoyment of the members and visitors looking to learn about and share information regarding the topics listed. It is not a free-for-all advertising venue. Your time would be better spent pursuing legitimate avenues of promoting your websites.

Nvidia drivers,extra kernel,Adept Manager,dynamic disksSOLV

Help & Support for Ultimate Edition 1.5


Nvidia drivers,extra kernel,Adept Manager,dynamic disksSOLV

Postby DaddyX3 » Wed Oct 17, 2007 11:01 am

Hello all,
I'm new to the world of linux distro's. I've chosen to use the Ultimate Edition 1.5 because of all the additional packages pre-installed with the distro, which saves much headache for the noob. I can't thank TheeMahn enough for this really cool distro and all his hard work. Thank You! I do however have a couple of Q's:
1. After installing the Nvidia drivers and having ENVY change the xorg.conf file for me, I now have two kernels in the Grub menu. If I let grub boot to its default (the new kernel) I get the "no X server found" message and have to go back and start from my old kernal (the original). The original works just fine and from what I can tell includes any driver changes made by Nvidia (Nvidia Control Manager works). How do I hide this extra kernal from the Grub menu and use the original kernel by default?
2. Any body have a clue on how to mount a "dynamic" disk created by Vista? I've had success with a basic volume and simple, but no idea about the dymamic volume! Its very important to me since it has all my media on it!?
3. Adept Manager says that I can not install any packages or make any system changes because I don't have any administrative privileges. I have only the one user and I checked permissions and says that I have permissions!?
Any Idea's? Thanx in advance:)
Intel Core 2 Quad Q9300 2.5GHz 45nm/Gigabyte EP35C-DS3R M.B. w/ddr3 1333
G.Skill 2X1GB DDR3 1333MHz/Gigabyte 8800GT PCIe 2.0 512MB GDDR3 OC'd to 700Mhz/ WD160 gig, 2- WD250 gig in RAID-0 (500GB), WD640 gig e-SATA external

AMD 64 X2 3800+/ASUS A8N32-SLI Deluxe/G.Skill 2X1GB Matched Pair ddr400
/EVGA 6800GS Nvidia Graphics 256MB/WD160gig drive

HTPC Box:AMD 64 X2 4400+/ BIOSTAR TF7050PV HDMI MicroATX/G.Skill 2X1GB /Matched Pair DDR800/Integrated video and audio/WD160gig drive
User avatar
DaddyX3
U.E. God
U.E. God
 
Posts: 2407
Joined: Wed Oct 17, 2007 9:22 am
Location: Central Coast - California
Age: 44
Operating System: Ultimate Edition 2.3 32 BIT



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby TheeMahn » Wed Oct 17, 2007 11:50 am

DaddyX3 wrote:Hello all,
I'm new to the world of linux distro's. I've chosen to use the Ultimate Edition 1.5 because of all the additional packages pre-installed with the distro, which saves much headache for the noob. I can't thank TheeMahn enough for this really cool distro and all his hard work. Thank You! I do however have a couple of Q's:
1. After installing the Nvidia drivers and having ENVY change the xorg.conf file for me, I now have two kernels in the Grub menu. If I let grub boot to its default (the new kernel) I get the "no X server found" message and have to go back and start from my old kernal (the original). The original works just fine and from what I can tell includes any driver changes made by Nvidia (Nvidia Control Manager works). How do I hide this extra kernal from the Grub menu and use the original kernel by default?
2. Any body have a clue on how to mount a "dynamic" disk created by Vista? I've had success with a basic volume and simple, but no idea about the dymamic volume! Its very important to me since it has all my media on it!?
3. Adept Manager says that I can not install any packages or make any system changes because I don't have any administrative privileges. I have only the one user and I checked permissions and says that I have permissions!?
Any Idea's? Thanx in advance:)


Welcome aboard & Thanks...

1. I suggest a read of the F.A.Q. for installing.

2. I suggest the tool NTFS Configuration to mount your volume and make it writable. Applications >> System Tools>> NTFS Configuration Tool (see screenshot)

3. Are you using sudo with Adept Manager?
Attachments
snapshot1.png
NTFS Configuration Tool
snapshot1.png (15.58 KiB) Viewed 5669 times
Home of Ultimate Edition. Got a question? Please review the F.A.Q. Browse the How to section.

Main O/S: Builder of O/S Guess.
Mainboard: ASUS Hero VI (AM4)
CPU: AMD 1700X water cooled (Deepcool Captain Genome Cooling tower)
Ram: 16 GB GSkill Trident RGB Series Dual Channel DDR4 3200
Video: MSI RX470 8GB Gaming card.
Hard Disks: MASSIVE on the network.(10 Gigabit, 48 port, multiple servers)
Monitors: Dual 4K 43" LG, 4K Samsung 28"
750 Watt modular PSU (Rosswell)
1100 Watt Amp & 4 X 600 Watt speakers

Servers in the basement.
User avatar
TheeMahn
Site Admin
 
Posts: 4201
Joined: Fri Oct 12, 2007 10:02 am
Location: U.S.A.
Age: 48
Operating System: Ultimate Edition Developer



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby drama » Wed Oct 17, 2007 12:08 pm

DaddyX3 wrote:1. After installing the Nvidia drivers and having ENVY change the xorg.conf file for me, I now have two kernels in the Grub menu. If I let grub boot to its default (the new kernel) I get the "no X server found" message and have to go back and start from my old kernal (the original). The original works just fine and from what I can tell includes any driver changes made by Nvidia (Nvidia Control Manager works). How do I hide this extra kernal from the Grub menu and use the original kernel by default?


im not sure if thats normal for envy to add a new kernal like that. also dont know about the no xserver error as ive never used envy. i always install my drivers (ati) the old fashioned way. however i can help you with hiding the new kernal and making the old one default.

open a terminal window.

type
Code: Select all
 sudo gedit /boot/grub/menu.lst 


this will open your grub menu in a text editor. note: gedit is for gnome. if you are using kde i believe its kate or kedit (cant remember exactly) just replace gedit with kate or kedit if you are on kde. also be very careful when editing this file as you could make your system unbootable if you mess up. anyway you will see something similar to this

# menu.lst - See: grub(, info grub, update-grub(
# grub-install(, grub-floppy(,
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0


## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdb3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel memtest86+
root (hd1,2)
kernel /boot/memtest86+.bin
savedefault
boot


### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Home Edition
root (hd0,0)
savedefault
makeactive
chainloader +1


note: the above is just an example yours will look slightly different as this is from an older version (just copied it from another web page). now for the editing (ive highlighted the parts we will be editing in red)

now scroll to where it says end default options. your kernels are listed below this line. place a # at the beginning of the title line for the kernal that you dont want to show in the boot menu.

example:

title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

changed to:

#title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

now this entry is no longer shown in the grub boot menu.

do this to each kernal you want hidden. if there is a recovery corrosponding to the kernal you hid you can hide it also.

now change:

# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

to:

# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 2

note: changing it to 2 may not be the correct choice in your case as i dont know what kernals you have listed. but it starts with 0. 0 being the first entry. 1 being the second and so on.

but for example if i had

kernal 1
kernal1 recovery
kernal2
kernal2 recovery

setting default 1 would make kernal1 recovery the default. default 2 would be kernal2 and so one.

after you have made these changes id check through it just to make sure its right. then save it overwriting if promted. now reboot and it should now boot into the kernal you set as default.

if you have any probs just post back.
ULTIMATE EDITION 2.5 X64/ARCHLINUX X64 DUAL BOOT
Antec 900two case
3 antec 120mm tri cool blue led fans (1 rear exaust 2 front intake)
1 antec 220mm "bigboy" tri cool blue led fan (top exaust)
Amd Phenom II X4 955 Black Edition Am3 Cpu OC'D @ 4.2 Rev C3
MSI NF980-G65 Am3 Socket DDR3 Tri-sli ATX Mainboard
Nvidia 980A Sli Chipset
Corsair 2GB Dual Channel ram (1GBx2) DDR3 @ 1600 MHZ
EVGA Nvidia GTS-250 1GB PCI Express Graphics Card
Lite-On Dual Layer Sata Dvd Burner
3x 1TB Seagate Sata Hdd's 32Mb cache
ASUS VH235 23 Inch Lcd Wide Screen Monitor
OCZ ModXStream Pro 700Watt Psu
Rosewill 3.5" Internal USB 2.0 Card Reader w/ Floppy Drive
User avatar
drama
U.E. Master
U.E. Master
 
Posts: 580
Joined: Wed Oct 17, 2007 11:26 am
Location: eastern iowa, united states
Age: 37
Operating System: Ultimate Edition 3.2 32 BIT



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby TheeMahn » Wed Oct 17, 2007 12:30 pm

drama1981 wrote:
DaddyX3 wrote:1. After installing the Nvidia drivers and having ENVY change the xorg.conf file for me, I now have two kernels in the Grub menu. If I let grub boot to its default (the new kernel) I get the "no X server found" message and have to go back and start from my old kernal (the original). The original works just fine and from what I can tell includes any driver changes made by Nvidia (Nvidia Control Manager works). How do I hide this extra kernal from the Grub menu and use the original kernel by default?


im not sure if thats normal for envy to add a new kernal like that. also dont know about the no xserver error as ive never used envy. i always install my drivers (ati) the old fashioned way. however i can help you with hiding the new kernal and making the old one default.

open a terminal window.

type
Code: Select all
 sudo gedit /boot/grub/menu.lst 


this will open your grub menu in a text editor. note: gedit is for gnome. if you are using kde i believe its kate or kedit (cant remember exactly) just replace gedit with kate or kedit if you are on kde. also be very careful when editing this file as you could make your system unbootable if you mess up. anyway you will see something similar to this

# menu.lst - See: grub(, info grub, update-grub(
# grub-install(, grub-floppy(,
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0


## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdb3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel memtest86+
root (hd1,2)
kernel /boot/memtest86+.bin
savedefault
boot


### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Home Edition
root (hd0,0)
savedefault
makeactive
chainloader +1


note: the above is just an example yours will look slightly different as this is from an older version (just copied it from another web page). now for the editing (ive highlighted the parts we will be editing in red)

now scroll to where it says end default options. your kernels are listed below this line. place a # at the beginning of the title line for the kernal that you dont want to show in the boot menu.

example:

title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

changed to:

#title Ubuntu, kernel 2.6.10-5-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

now this entry is no longer shown in the grub boot menu.

do this to each kernal you want hidden. if there is a recovery corrosponding to the kernal you hid you can hide it also.

now change:

# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

to:

# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 2

note: changing it to 2 may not be the correct choice in your case as i dont know what kernals you have listed. but it starts with 0. 0 being the first entry. 1 being the second and so on.

but for example if i had

kernal 1
kernal1 recovery
kernal2
kernal2 recovery

setting default 1 would make kernal1 recovery the default. default 2 would be kernal2 and so one.

after you have made these changes id check through it just to make sure its right. then save it overwriting if promted. now reboot and it should now boot into the kernal you set as default.

if you have any probs just post back.


Drama Thank you for your input it is posts like these that make me proud to be a part of the linux community. Fellow man helping out fellow man, keep up the good work.
Home of Ultimate Edition. Got a question? Please review the F.A.Q. Browse the How to section.

Main O/S: Builder of O/S Guess.
Mainboard: ASUS Hero VI (AM4)
CPU: AMD 1700X water cooled (Deepcool Captain Genome Cooling tower)
Ram: 16 GB GSkill Trident RGB Series Dual Channel DDR4 3200
Video: MSI RX470 8GB Gaming card.
Hard Disks: MASSIVE on the network.(10 Gigabit, 48 port, multiple servers)
Monitors: Dual 4K 43" LG, 4K Samsung 28"
750 Watt modular PSU (Rosswell)
1100 Watt Amp & 4 X 600 Watt speakers

Servers in the basement.
User avatar
TheeMahn
Site Admin
 
Posts: 4201
Joined: Fri Oct 12, 2007 10:02 am
Location: U.S.A.
Age: 48
Operating System: Ultimate Edition Developer



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby DaddyX3 » Wed Oct 17, 2007 1:38 pm

WOW! That was a very fast reply!:) Thank you so much!

TheeMahn - I have performed what you have suggested and still ... to no avail. I did this quite a while ago, and from what I can tell, Ubuntu does not like a "dynamic" volume. To be honest with you, I don't recall why it is a dynamic volume anyway. I was working in Vista and somehow that is what I ended up with. It works just fine in Vista, but not Ubuntu.
... That is ok if I don't get it figured out though, I will just try to shift things around little by little on to other drives that is recognizable (only prob. is that it is much larger than my other drives installed, but maybe that'll make me weed out some of the junk I don't really need/ watch/ listen too! :lol: )
ps - by the way, how do you sudo Adept Manager? I tried a few times but I know that I was taking blind shots at it within terminal. (:sudo adept ? , :sudo adept manager ? - both got me nowhere) sory for the ignorance:(

drama1981 - Thank you so much for the extensive and very detailed response! You have gone beyond the call of duty! I'm not quite sure on why ENVY has created the second kernel either, but it has done it on both of my machines. Weird. Its not the end of the world, however I do feel that it is a scary thing to happen to a noob like myself. I've invested quite a bit of time tracking down fixes for strage happenings ever since the beginning of my linux-base adventures. I do have confidence that everything will come out ok though and with great help from a community of linux users, like yourself, I have the utmost confidence. Thank you for your time and efforts. I will try this and post back here to let you know how it has turned out.
User avatar
DaddyX3
U.E. God
U.E. God
 
Posts: 2407
Joined: Wed Oct 17, 2007 9:22 am
Location: Central Coast - California
Age: 44
Operating System: Ultimate Edition 2.3 32 BIT



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby DaddyX3 » Thu Oct 18, 2007 9:21 am

Thank you, It worked like a charm drama1981.
I asked in a earlier post, how do you run sudo for programs? For example, TheeMahn asked if I was using sudo for Adept Manager, how do I? I tried taking some wild shots at it but didn't work. If anybody could explain to me a simple way to find out how to run programs in sudo I would greatly appriciate it. (ie., typing in to terminal to find out executable file name for a specific program, how would I find out the name?) Thank you in advance!
User avatar
DaddyX3
U.E. God
U.E. God
 
Posts: 2407
Joined: Wed Oct 17, 2007 9:22 am
Location: Central Coast - California
Age: 44
Operating System: Ultimate Edition 2.3 32 BIT



Re: Nvidia drivers extra kernel,Adept Manager, dynamic disks

Postby drama » Thu Oct 18, 2007 10:49 am

DaddyX3 wrote:Thank you, It worked like a charm drama1981.
I asked in a earlier post, how do you run sudo for programs? For example, TheeMahn asked if I was using sudo for Adept Manager, how do I? I tried taking some wild shots at it but didn't work. If anybody could explain to me a simple way to find out how to run programs in sudo I would greatly appriciate it. (ie., typing in to terminal to find out executable file name for a specific program, how would I find out the name?) Thank you in advance!


glad to hear that :) as far as running something with the sudo command. i would use gksudo instead for gui based apps. this is because sometimes if you just use sudo it sometimes screws up permissions. gparted being one of them (used sudo once instead of gksudo for this and ended up with partitions i couldnt access). however im not sure what the command is for adept. it may not be adept. an example of this is gedit. while its the default editor i dont think its actually listed as gedit in the menu i think its text editor. but the terminal command is gedit. one solution may be to right click it in the menu and select edit or properties i believe. look at where it says command that should help. sorry i cant check it myself as im not on my linux box currently. sorry i couldnt be of much help but i thought i try to shed some light on it.

p.s. i think it might be gksudo adept_manager
ULTIMATE EDITION 2.5 X64/ARCHLINUX X64 DUAL BOOT
Antec 900two case
3 antec 120mm tri cool blue led fans (1 rear exaust 2 front intake)
1 antec 220mm "bigboy" tri cool blue led fan (top exaust)
Amd Phenom II X4 955 Black Edition Am3 Cpu OC'D @ 4.2 Rev C3
MSI NF980-G65 Am3 Socket DDR3 Tri-sli ATX Mainboard
Nvidia 980A Sli Chipset
Corsair 2GB Dual Channel ram (1GBx2) DDR3 @ 1600 MHZ
EVGA Nvidia GTS-250 1GB PCI Express Graphics Card
Lite-On Dual Layer Sata Dvd Burner
3x 1TB Seagate Sata Hdd's 32Mb cache
ASUS VH235 23 Inch Lcd Wide Screen Monitor
OCZ ModXStream Pro 700Watt Psu
Rosewill 3.5" Internal USB 2.0 Card Reader w/ Floppy Drive
User avatar
drama
U.E. Master
U.E. Master
 
Posts: 580
Joined: Wed Oct 17, 2007 11:26 am
Location: eastern iowa, united states
Age: 37
Operating System: Ultimate Edition 3.2 32 BIT


Return to Ultimate Edition 1.5

Who is online

Users browsing this forum: No registered users and 0 guests