Re: SOLVED !!! Re: Help!!! Music player Amarok has error about DCOP communications
Hi,
I am not sure if you are aware that linux.conf.au will be in Hobart
later this month. This is one of the best Linux conferences around -
although it is quite technical.
If you can't afford the time (or ticket price) you should try to make
it along to the openday - see
http://linux.conf.au/programme/about_programme#OpenDay
I am not sure about the Mint crew, but there will be people from
Australian Ubuntu community. There will also be other projects and
distros represented at the open day. It might be a good chance for you
to meet some more local Linux geeks.
Cheers
Dave
On Tue, 2009-01-06 at 18:43 +1100, Peter Williams wrote:
Hello Everyone (I'm doing a reply to all - for this email) *SMILE*
thank you Paul, for your nice email. *GRIN*
2009/1/4 Paul Shirren shi...@shirro.com
Hi Peter,
Peter Williams wrote:
To my great happiness (poor wording, I know!!!) - my
Ubuntu Mint (Elyssa) OS is now working almost
perfectly!!! *BIG SMILE HAPPY
GRIN**!!!
Well done.
Can you please not refer to Mint Linux as Ubuntu Mint. Mint
and Ubuntu are two separate projects with their own
developers, forums and mailing lists.
Okay, I will try to keep that in mind and refer to my OS by its
correct name; Mint Linux.
I get quite a bit confused about its correct name. I think that the
Mint Linux ppl also call it Ubuntu Mint Linux etc etc. :-) There seems
to be quite a lot of jargon buzz-words etc involved for the OS { Not
that I'm objecting! SMILE }. Also, I find that the sheer volume of
information and facts, knowledge and 'wisdom' of the Gurus developing
the Mint Linux project -- well, it's information overload!! Too much
for me to know where to begin looking. *SIGH*
Note: I'm still only a Linux Newbie although I've used many many
different computer systems over my life... since I was a young
teenager (or even younger!). Our family's first computer was a
Commodore PET (Personal Electronic Transactor) with 16 KB of RAM
expandable to 32KB RAM. Actually, it was a pretty good machine -- it
had a 6502 processor and it communicated with peripherals with a
IEEE-488 port and also had a programmable 'user port' !!! It was
amazing!!! And also very powerful. Actually, it's OS was Commodore PET
BASIC which was written by Micro$oft! and was a combination of BASIC
programming language with DOS commands included also!!! It was
powerful but it bit tricky to learn!!! [ THOSE WERE THE DAYS!!! -
e.g. circa the 1970's ]
We are all in the same big happy open source family but there
are issues
of branding and trademark. The Ubuntu trademark is owned by
Canonical
and I am sure they would not want it to be diluted. I am sure
the Mint
people are proud of their work and feel the same.
Thank you for explaining that. I'm very very pleased with my OS -
although it still has its little querks (spelling?!). The nice people
at Canonical are amazingly clever and I admire and thank them ###
HAPPY GRIN ###
Then I discovered that the repositories were wrong!!! The were
pointing to Ubuntu repositories instead of Ubuntu Mint
(Elyssa) ones.
I don't know if this is a consequence of not understanding
that Ubuntu and Mint are two separate projects.
Yes, it probably is!!! (SMILE). I'll admit that I'm still a newbie
beginner at Mint Linux; although I'll admit that I've been 'learning'
Linux for more than one year!!! I'm just happy to get help from the
those wonderfully clever and friendly Linux users!!!
I had a Ford made by Mazda. You could probably replace
suspension and engine parts with Mazda parts but other would
have been to Ford specs. A person in that situation might ask
about after market accessories on a Mazda forum and get
friendly and useful advice but might also get completely
misleading advice if Ford had changed the spec on some parts.
That's an interesting analogy, and I think I understand. Thanks for
that. #SMILE#
Yours Sincerely,
PEW - poet, computer geek, amiable human being and Christian
--
Fond Regards,
Peter Eric (aka 'pew') WILLIAMS
from Hobart, Tasmania, Australia -- phone (03) 6236-9675
My free website is: http://pewtas.googlepages.com (or)
http://tinyurl.com/yuyejs
(please visit my free website and let me know what you think about
it.)
--
ubuntu-au mailing list
ubuntu-au@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: SOLVED !!! Re: Help!!! Music player Amarok has error about DCOP communications
Hi Dave and Everyone,
2009/1/7 Dave Hall dave.h...@skwashd.com
Hi,
I am not sure if you are aware that linux.conf.au will be in Hobart
later this month. This is one of the best Linux conferences around -
although it is quite technical.
If you can't afford the time (or ticket price) you should try to make
it along to the openday - see
http://linux.conf.au/programme/about_programme#OpenDay
I went to the above mentioned link and found this webpage:
http://keysigning.org/event/lca2009
quote from the website
---
This keysigning will use the
'Sassaman-Projectedhttp://keysigning.org/methods/sassaman-projected'
method, which is well suited to large groups.
*Getting Ready*
To participate in the LCA 2009 keysigning you will need to submit your
public key prior to *2009-01-16 16:00:00*. NB: that's according to the
system time of this server, which is currently 2009-01-07 01:20:30. It's *
not* relative to your local time.
The simplest way to do this is to export your public key in ascii-armored
format and email it to 'lca2009-k...@keysigning.org'. On a typical Linux
system you can do this by typing:
gpg --export-options export-minimal --export -a *KeyID* | mail -s
keysigning lca2009-k...@keysigning.org
where *KeyID* is actually your unique key ID, something like '64011A8B'.
After your key has been processed and added to the event keyring you will
receive an email confirmation.
Further instructions will be posted here closer to the event.
*Keys accepted into the event keyring:* check this
listhttp://keysigning.org/keylist/lca2009.txtto see if your key has
been added. The list is updated in real time.
---
Now please bear in mind that I'm still a Mint Ubuntu newbie... I'm using
Gnome Desktop 2.22.3.
I eventually worked out that I needed to do was select the menu:
Applications / System Tools / Terminal Program - Super
I am not sure about the Mint crew, but there will be people from
Australian Ubuntu community. There will also be other projects and
distros represented at the open day. It might be a good chance for you
to meet some more local Linux geeks.
Cheers
Dave
On Tue, 2009-01-06 at 18:43 +1100, Peter Williams wrote:
Hello Everyone (I'm doing a reply to all - for this email) *SMILE*
thank you Paul, for your nice email. *GRIN*
2009/1/4 Paul Shirren shi...@shirro.com
Hi Peter,
Peter Williams wrote:
To my great happiness (poor wording, I know!!!) - my
Ubuntu Mint (Elyssa) OS is now working almost
perfectly!!! *BIG SMILE HAPPY
GRIN**!!!
Well done.
Can you please not refer to Mint Linux as Ubuntu Mint. Mint
and Ubuntu are two separate projects with their own
developers, forums and mailing lists.
Okay, I will try to keep that in mind and refer to my OS by its
correct name; Mint Linux.
I get quite a bit confused about its correct name. I think that the
Mint Linux ppl also call it Ubuntu Mint Linux etc etc. :-) There seems
to be quite a lot of jargon buzz-words etc involved for the OS { Not
that I'm objecting! SMILE }. Also, I find that the sheer volume of
information and facts, knowledge and 'wisdom' of the Gurus developing
the Mint Linux project -- well, it's information overload!! Too much
for me to know where to begin looking. *SIGH*
Note: I'm still only a Linux Newbie although I've used many many
different computer systems over my life... since I was a young
teenager (or even younger!). Our family's first computer was a
Commodore PET (Personal Electronic Transactor) with 16 KB of RAM
expandable to 32KB RAM. Actually, it was a pretty good machine -- it
had a 6502 processor and it communicated with peripherals with a
IEEE-488 port and also had a programmable 'user port' !!! It was
amazing!!! And also very powerful. Actually, it's OS was Commodore PET
BASIC which was written by Micro$oft! and was a combination of BASIC
programming language with DOS commands included also!!! It was
powerful but it bit tricky to learn!!! [ THOSE WERE THE DAYS!!! -
e.g. circa the 1970's ]
We are all in the same big happy open source family but there
are issues
of branding and trademark. The Ubuntu trademark is owned by
Canonical
and I am sure they would not want it to be diluted. I am sure
the Mint
people are proud of their work and feel the same.
Thank you for explaining that. I'm very very pleased with my OS -
although it still has its little querks (spelling?!). The nice people
at Canonical are amazingly clever and I admire and thank them ###
HAPPY GRIN ###
Then I discovered that the repositories were wrong!!! The were
pointing to Ubuntu repositories instead of Ubuntu Mint
(Elyssa) ones.
I don't know if this is a
Re: Old Kernels . . .(never die!)
On Fri, 2009-01-02 at 09:21 +1100, Dave Hall wrote: I personally keep the previous kernel for a few days to make sure that everything works properly. 3. How would I go about deleting them? Using GNOME go system admin synaptic package manager Search for linux-image Don't try to remove the highest numbered entry (that will be the kernel you are running) For the remaining linux-image-2.6.xx-y* entries, just right click on them and select Mark for complete removal. It will ask you to confirm that you also want to remove the related restricted modules package as well. When done click Apply. Confirm that you are happy with the changes by clicking apply. Wait for synaptic to work its magic. I did all of that Dave. Actually, I did the above for Kernel #16, as a test. Upon re-booting the pesky #16 was still there. So I re-booted and selected #16 and got the error message: file not found. I have tried all the remedies suggested by the other members but nothing seems to get rid of the long list of Kernels at start-up. Not that it's all that important really. It's just a matter of aesthetics. And the frustration at trying to fix something that should be quite easy -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
On Wed, Jan 7, 2009 at 8:03 AM, The Wassermans dw...@optusnet.com.au wrote: On Fri, 2009-01-02 at 09:21 +1100, Dave Hall wrote: I personally keep the previous kernel for a few days to make sure that everything works properly. 3. How would I go about deleting them? Using GNOME go system admin synaptic package manager Search for linux-image Don't try to remove the highest numbered entry (that will be the kernel you are running) For the remaining linux-image-2.6.xx-y* entries, just right click on them and select Mark for complete removal. It will ask you to confirm that you also want to remove the related restricted modules package as well. When done click Apply. Confirm that you are happy with the changes by clicking apply. Wait for synaptic to work its magic. I did all of that Dave. Actually, I did the above for Kernel #16, as a test. Upon re-booting the pesky #16 was still there. So I re-booted and selected #16 and got the error message: file not found. I have tried all the remedies suggested by the other members but nothing seems to get rid of the long list of Kernels at start-up. Not that it's all that important really. It's just a matter of aesthetics. And the frustration at trying to fix something that should be quite easy Just as a matter of - hey this is how I manager my old kernels. I'm not sure sure about the gui way of doing it, but to see a list of kernels and kernel related packages I have installed, from the command line I use: dpkg -l | grep linux If I then want to filter it to a specific kernel I would copy the kernel version and paste it at the end of the line instead of linux: dpkg -l | grep 2.6.27-7 I can then remove an old kernel using the names of the packages listed, eg: sudo apt-get remove linux-headers-2.6.27-7 linux-headers-2.6.27-7-generic linux-image-2.6.27-7-generic linux-restricted-modules-2.6.27-7-generic It is safe to just remove only the image package too and leave the rest. They will not be used by most systems after the image is gone anyway. And by the sounds of the symptoms of your grub file, it is not being updated automatically anymore by update-grub. If you run: sudo update-grub It should list the kernels as Found kernel and update /boot/grub/menu.lst at the end. It is probably not completing it's task anymore because of the manual changes to /boot/grub/menu.lst. I would not go replacing my menu.lst file with someone else's without a bit of experience, but if I did, I would need to update the kopt and groot lines to reflect my ubuntu partitions UUID (as found in your current menu.lst. Then on running sudo update-grub the kernel lines would be generated again and invalid entries removed. I know it's a bit light on details, but just ask if there is anything you want clarified above. (I'm used to working in a quiet office without human contact). - Karl -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
On Wed, 2009-01-07 at 08:03 +1100, The Wassermans wrote: On Fri, 2009-01-02 at 09:21 +1100, Dave Hall wrote: I personally keep the previous kernel for a few days to make sure that everything works properly. 3. How would I go about deleting them? Using GNOME go system admin synaptic package manager Search for linux-image Don't try to remove the highest numbered entry (that will be the kernel you are running) For the remaining linux-image-2.6.xx-y* entries, just right click on them and select Mark for complete removal. It will ask you to confirm that you also want to remove the related restricted modules package as well. When done click Apply. Confirm that you are happy with the changes by clicking apply. Wait for synaptic to work its magic. I did all of that Dave. Actually, I did the above for Kernel #16, as a test. Upon re-booting the pesky #16 was still there. So I re-booted and selected #16 and got the error message: file not found. I have tried all the remedies suggested by the other members but nothing seems to get rid of the long list of Kernels at start-up. Not that it's all that important really. It's just a matter of aesthetics. And the frustration at trying to fix something that should be quite easy I know in earlier versions of ubuntu that the menu.lst wasn't always properly updated. try running sudo update-grub from a terminal/the console. Sorry for not replying to your previous post, been distracted by work and the heat :( Cheers Dave -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
On Wed, 2009-01-07 at 08:46 +1100, Dave Hall wrote: try running sudo update-grub from a terminal/the console. Sorry for not replying to your previous post, been distracted by work and the heat :( No worries Dave. Somebody has to do it! On Fri, 2009-01-02 at 09:21 +1100, Dave Hall wrote: I know it's a bit light on details, but just ask if there is anything you want clarified above. (I'm used to working in a quiet office without human contact). Plenty of detail thank you Karl. (Watch out for dem humans!) === Thank you Karl and Dave, I ran sudo update-grub and this is what I got:- A new version of /boot/grub/menu.lst is available, but the version │ │ installed currently has been locally modified. │ │ │ │ What would you like to do about menu.lst? │ │ │ │ install the package maintainer's version │ │ keep the local version currently installed │ │ show the differences between the versions │ │ show a side-by-side difference between the versions │ │ show a 3-way difference between available versions │ │ do a 3-way merge between available versions (experimental) │ │ start a new shell to examine the situation │ │ │ │ │ │Ok What does it mean? What should I do now, please? Dave W -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: SOLVED !!! Re: Help!!! Music player Amarok has error about DCOP communications
Peter Williams wrote: I went to the above mentioned link and found this webpage: http://keysigning.org/event/lca2009 Don't worry about the keysigning Peter. That is for developers attending the conference. The Open Day is on Saturday 24th January at the University of Tasmania, Sandy Bay campus. It is free and open to the general public if you are interested. Still waiting for details on the start and finish time. When there is more info it will probably appear here: http://linux.conf.au/programme/open_day -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
2009/1/7 Paul Gear p...@libertysys.com.au: Karl Bowden wrote: ... Not that it's all that important really. It's just a matter of aesthetics. And the frustration at trying to fix something that should be quite easy Just as a matter of - hey this is how I manager my old kernels. Just to chime in with a me too, my method is this: DON'T DO ANYTHING. A kernel package is never likely to fill your disk, and leaving it there costs absolutely nothing. More importantly, you have a fallback if you need to do something like move your hard disk into another system which for some reason doesn't work on newer kernels. I've been burned by other distros which overwrite the currently running kernel, and i'm glad Ubuntu lets those old ones build up. They come in handy from time to time! Paul I would also second this point! I normally only keep the latest two or three kernels around and have - even in ubuntu - had a minor kernel update kill wireless functionality and had to revert to the previous kernel again. Another point of interest in this case is that if if just the grub boot menu that you want to keep clean, maybe the best way would be to change the 'howmany' option in menu.lst to 2. This will not remove old kernels from the system, but will only display the 2 latest kernels in grub. (After you have installed the package maintainers version of menu.lst again) - Karl -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
On Wed, 2009-01-07 at 11:19 +1030, Karl Goetz wrote: What does it mean? Isn't that fairly obvious? :) Your copy of grubs menu.lst has been changed, and its been changed by something other then the packaging system. I guess so, but I still struggle a bit with some of the jargon. I'm still very nervous about trashing the system by being too hasty. Anyway, what with your gentle push in my back, I accepted the install the package maintainer's version. And Bingo! It fixed the problem. Thank you Karl and Karl. Thank you Paul and Dave. Thank you Andre too. So completes yet another 2 minute tweak that took me several hours accomplish. Dave W -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
Re: Old Kernels . . .(never die!)
On Wed, 07 Jan 2009 12:43:53 +1100 The Wassermans dw...@optusnet.com.au wrote: On Wed, 2009-01-07 at 11:19 +1030, Karl Goetz wrote: What does it mean? Isn't that fairly obvious? :) Your copy of grubs menu.lst has been changed, and its been changed by something other then the packaging system. I guess so, but I still struggle a bit with some of the jargon. I'm still very nervous about trashing the system by being too hasty. Thats understandable. I have a SPARC system running on my network, which uses Silo (based on Lilo). I think I've forgotten to run the silo update after changing its kernel twice now, with the result of not booting. Anyway, what with your gentle push in my back, I accepted the install the package maintainer's version. And Bingo! It fixed the problem. Great to hear! Its odd that you wound up with this problem, as grub handles updates to the file (I've never had to manually run grub-update unless recovering a broken system). Thank you Karl and Karl. Thank you Paul and Dave. Thank you Andre too. So completes yet another 2 minute tweak that took me several hours accomplish. aye, but next time you'll know what to do (and you'll probably be braver about exploring the options). kk Dave W -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian user / gNewSense contributor http://www.kgoetz.id.au No, I won't join your social networking group -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
