What packages are necessary for a computer to have sound?

[Rod J]

OK, you didn't need to install gedit. Gedit is the Gnome/Unity equivalent of our Kate or Kwrite app. You could have used Kate as effectively.

Also, you shouldn't run gui apps using sudo. You should use kdesudo. I guess you probably didn't realise gedit was a gui app?

So, the error messages you got trying to run gedit were more to do with trying to run a Gnome app in Kubuntu (KDE) and maybe because you used sudo instead of kdesudo (I think).

Instead of the line on that page (the Second Alternate Method): sudo gedit /etc/default/speech-dispatcher
you should instead try this: kdesudo kate /etc/default/speech-dispatcher

[Shabakthanai]

You read me like a book, my friend. Thanks

OK, you didn't need to install gedit. Gedit is the Gnome/Unity equivalent of our Kate or Kwrite app. You could have used Kate as effectively.

Also, you shouldn't run gui apps using sudo. You should use kdesudo. I guess you probably didn't realise gedit was a gui app?

So, the error messages you got trying to run gedit were more to do with trying to run a Gnome app in Kubuntu (KDE) and maybe because you used sudo instead of kdesudo (I think).

Instead of the line on that page (the Second Alternate Method): sudo gedit /etc/default/speech-dispatcher
you should instead try this: kdesudo kate /etc/default/speech-dispatcher

I removed gedit, Rod. Thanks

[Shabakthanai]

I opened a terminal and did as you suggested. My computer is pretty fast, and after pressing enter, the cursor moved to the next line and just sits there. Sometimes when this happens, it means the computer is working to resolve a command, so I am sitting here waiting for something to happen. It has been going on for several minutes now, so I am stumped what to do. I have an 8 core processor with 16GB RAM, it seems unreasonable that the computer is still working on a reply, but ...@$#*&^%#(@ you can see why that persistent opening under existing window is such a problem. I finally remembered that and sure enough hidden underneath my current page is the request for password to open Kate. Sorry to ramble, but I think you and others should realize how serious the 'opening under current app problem is'. Aparently SteveRiley has experienced the problem in OpenOffice too, now, so I am no longer alone with that problem. I will finish and get back to you. Thanks for your continued patience.

[Shabakthanai]

My computer is difinately working the problem, finally a long list of can't do's is appearing and the work continues.

When I opened Kate, I didn't know what to enter or open and referred to the original help post I was referred to. I looked for Speach Dispatcher, but it was not in the list of items Kate provided. I did click on Pulseaudio, one of the entries and the following appeared:

# This file is deprecated please edit /etc/init/pulseaudio.conf I read the words but do not understand what I am to do. I think one of my two electrons is taking a nap and putting pressure to perform on the remainder.

[Shabakthanai]

My computer stopped working the problem and here is what it came up with:

steven@Yeshuah-desktop:~$ kdesudo kate /etc/default/speech-dispatcher

Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
kactivitymanagerd(3017)/nepomuk (library): Could not find virtuoso to connect to. Aborting
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
Object::connect: No such signal org::freedesktop::UPower:eviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower:eviceRemoved(QDBusObjectPath)
Disc in /dev/sr0 is a Video DVD
Object::connect: No such signal org::freedesktop::UPower:eviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower:eviceRemoved(QDBusObjectPath)
steven@Yeshuah-desktop:~$
steven@Yeshuah-desktop:~$

Again, this is over my head to understand the implications of the work.

[Shabakthanai]

Also, you shouldn't run gui apps using sudo. You should use kdesudo. I guess you probably didn't realise gedit was a gui app?

When I know it is a KDE application, I do try to run kdesudo, and do so also when an application isn't obvious by its name, but by how it is used, like Dolphin. I have to admit, that comingling Gnome and KDE is a bit confusing. I accept that they both work fine on Kubuntu, but still for one like me it is still confusing when I see an update that always refers to Ubuntu entries and not Kubuntu. It sure would be nice if even in the updates and such, they would use Kubntu entries instead of Ubuntu. One more electron and I might be able to handle the confusion.

[Snowhog]

That's because the file /etc/default/speech-dispatcher doesn't exist.

The URL I cited was a suggestion. Given that this file doesn't exist, then attempting "that solution" isn't viable.

Did you try the initial suggestions?

sudo alsa force-reload

And if that didn't work, then:

sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio

And force reload Alsa again:

sudo alsa force-reload

[Shabakthanai]

Yes, but unfortunately nothing changed for the better. I am not and will never blame anyone who is trying to help me. I was just explaining that success was not achieved. I never know where the solution will come, and appreciate each and every attempt to help. If I ever give the implication that I am complaining about any offered help, I am either misunderstood or stated things I did not intend. You are among those I most appreciate in the forum. I so wish I had your talent and skill, so I too could help others. I just love this stuff.

That's because the file /etc/default/speech-dispatcher doesn't exist.

The URL I cited was a suggestion. Given that this file doesn't exist, then attempting "that solution" isn't viable.

Did you try the initial suggestions?

sudo alsa force-reload

And if that didn't work, then:

sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio

And force reload Alsa again:

sudo alsa force-reload

[Snowhog]

If I ever give the implication that I am complaining about any offered help, I am either misunderstood or stated things I did not intend.

Never. I hope any comments I make aren't similarly construed.

You are among those I most appreciate in the forum. I so wish I had your talent and skill, so I too could help others. I just love this stuff.

Kind words. Thank you.

I can imagine that this situation is frustrating the heck out of you; I'm sure it would if I were experiencing it.

Do you have a LiveDVD or LiveUSB of this version of Kubuntu? If you do, do you have system sound using it?

[Shabakthanai]

What a great idea. I am not sure. I actually installed Kubuntu 13.10 and while doing the work that must be done post-installation, I made a mistake and while thinking I was just upgrading packages actually upgraded the distribution to 14.04. I used a USB 3.0 stick for the install; it was very fast and appeared perfect.

Should I try to use that USB to see if sound is present on the try Kubuntu option or assume this happened in the upgrade.

You are right about the frustration, I have two persistent problems which both make the OS pretty much useless. You probably noticed, but the other is when I open most applications or click on links, etc. the existing screen remains and the selected screens appear under the existing screen.

My computer is quite fast, so many times I will click the same selection several times before I remember the problem. Each click was successful; each page opened under the preceding. This problem is driving me nuts, yet I don't want to solve every difficult problem by reinstalling the OS again, even though my impatience keeps screaming at me. It was either Steve or Vince, they both are so good at this stuff, but one of them got a similar result using OpenOffice. It showed me that the problem, although more severe in my computer, is experienced by at least one other. Of course I am not happy that he is also affected, but it is nice to know that it probably isn't another of my classic screw-ups gone unnoticed. I am hanging in there, because whatever cause the problem may be rare, but will probably affect others, so a solution is pretty important in my thinking. With every breath you take, I hope your day gets better, friend. Another way to say and mean Have a Good Day

Never. I hope any comments I make aren't similarly construed.
Kind words. Thank you.

I can imagine that this situation is frustrating the heck out of you; I'm sure it would if I were experiencing it.

Do you have a LiveDVD or LiveUSB of this version of Kubuntu? If you do, do you have system sound using it?

[Snowhog]

Yes, use the Try Kubuntu option on the USB. IF you have working sound there, we know that your current issue is a configuration one, and that can be resolved.

[Shabakthanai]

Dear Snowhog,

Just to be clear, I am answering this post in my Windows 7 OS. System Sounds are working fine, and the DVD player includes sound too.

When I attempted to open the Kubuntu 13.10 USB 3.0, I got some error messages; the first part I did not get all the message, because it changed screens faster than I could get a pen and copy all. It started I believe with Invalid Cluster Error.... Next screen is as follows:

[1.893753] Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block (0,0)

I restarted twice with the same result, so something is amiss with the USB 3.0 Thumb, I guess.

Next, I downloaded the most recent Kubuntu 14.04 LTS and made a successful USB 3.0 ISO stick.

It opened and selected 'Try Kubuntu'. There were NO system sounds. When I attempted to open System Settings to further check sound, System Settings opened in the other Screen, and the mouse would not move to the other screen to select the application. Frustration abounds. New and never before experienced problems seem to occur almost every time anymore. Do you have any suggestions now?

Since sounds work fine when I open the alternate OS, Windows 7, doesn't it seem probably that the problem is a Kubuntu problem?

Can the problem on the USB 3.0 stick be repaired, or should I just format the stick and use for other things. I have a good fresh ISO install on a 4GB Transcend 3.0 USB thumb drive anyway. I was just thinking there might be something to learn from the repair.

Yes, use the Try Kubuntu option on the USB. IF you have working sound there, we know that your current issue is a configuration one, and that can be resolved.

[Shabakthanai]

Could this be a glitch in the kernel?

[Shabakthanai]

I have attempted all solutions that are provided in this post. I re-installed the 14.04 version of Kubuntu yesterday. Help has pretty much ceased. I am not getting anything that calls for a bug report. I purchased and installed a new sound card which seems to be recognized and installed properly. And finally, sound works fine int he Windows 7 version, so the motherboard must still be OK. Please don't tell me I have to use Windows 7 forever

[ubuntuku]

still no sound with your new sound card?