I'm glad everything is working now. Without knowing the last thing(s) you did
before your system started working I can't say what fixed it, but as long as
the problem doesn't return I wouldn't worry about it.
signature.asc
Description: PGP signature
OR, you could do, sudo aptitude remove file. file being the thing you want to
remove. If it is a problem it won't let you do it. that's the honest truth.
In my previous experience anyways.
Just for information: I commented here
(https://trisquel.info/en/forum/problems-os-after-upgrade#comment-133612)
that the problem disappeared without any modification on the system.
Situation that I am finding weird...
> rytege have you eliminated the possibility that a hardware problem is
causing Trisquel to fail?
No, actually I am also thinking about a hardware problem but I do not know
how to verify it!
> Things like running a memory test, or checking the integrity of the drive
that holds your OS
I did not comment recently because the system has "magically" been OK.
I've recovered the sound and the latency has disappeared and I do not know
why?
Later I've got the possibility to update the system and still no error came.
It is fine now but I do not understand why the system came back
Actually I have the current version after an update:
$ uname -r
4.4.0-128-lowlatency
Is the "huge" difference between 4.4 and 4.13 / 4.14 normal?
>lose the sound applet in their panel
They can install several different ones and try and see which one suits them
better. I recommend 'volti'
>and volume buttons might not work unless they are specifically mapped to
amixer commands or something.
This was not the case on my system. They
Advice For New Users On Not Breaking Their Debian System
Don't blindly remove software
Sometimes when you remove a package, the package manager needs to remove
other packages too. This is because the additional packages depend on the
package you're trying to remove.
> One could tinker for ever with Trisquel, and never find a solution, if the
> problem is actually dodgy RAM, or a dying hard drive etc ;)
Since the problem was introduced in a recent update, I think that the problem
is likely in Trisquel Also, audio began working again when Totem crashed, so
> My browser is js-less, meaning it is always mute anyway.
Files embedded with the html5 tag can be played back without JavaShit,
if audio is working in the browser. pulseaudio also integrates nicely with the
desktop environment. Without it rytege will probably lose the sound applet in
their
rytege have you eliminated the possibility that a hardware problem is causing
Trisquel to fail? Things like running a memory test, or checking the
integrity of the drive that holds your OS partition, and the integrity of the
file system of your OS partition?
Have you got an other OS dual
>To test this, I ran 'sudo apt remove pulseaudio', looked at the packages
that would have been removed, cancelled, and then ran 'sudo apt purge
pulseaudio' and compared. It's the same packages, none of which are system
breaking when removed.
yep..
>you are probably joking, but i strongly advice against this, for one "purge"
can remove too much and break the system
Absolutely not true. It will purge only pulseaudio.
>but also PulseAudio is required for sound on things like firefox, I don't
know if Abrowser requires it but removing
> Purge removes too much, usually not only the package but things that depend
> on the package so it will break your system by getting rid of too much
> stuff.
'apt remove' also removes things that depend on the package. According to the
apt man page, the only difference between remove and purge
Again please do not do this.
Purge removes too much, usually not only the package but things that depend
on the package so it will break your system by getting rid of too much stuff.
You probably won't be able to boot into your Desktop Environment.
You can remove config files of pulseaudio
> Thank you for this awareness! :-)
happy_gnu is right that you probably want pulseaudio. However, it might be a
worth a shot to temporarily remove it along with any config files that could be
causing the problem, and then adding things back in one at a time.
Try removing pulseaudio with
$
Thank you for this awareness! :-)
you are probably joking, but i strongly advice against this, for one "purge"
can remove too much and break the system, but also PulseAudio is required for
sound on things like firefox, I don't know if Abrowser requires it but
removing pulseaudio can cause even more trouble.
As far as your no sound issue goes try:
sudo apt purge pulseaudio
o/
> What did you do after Totem crashed to get audio back?
Nothing... just starting VLC and checking that it works with VLC now.
> Did it just start working, or did you have to do something in sound
settings?
It just started working.
> Are you able to kill and restart pulseaudio while your
Actually this is happening when I am clicking on the Start Menu with the list
of programs. It takes a few minutes (+/- 3 minutes) to be able to navigate
through the list of programs.
> When I am trying to launch a video file with Totem, the application crashes!
> But then I am able to get **the audio back** ?!!??!
> Then I am able to launch the video file but with VLC
If Totem crashing fixes your audio, I guess you should add Totem to Startup
Applications so that it crashes
Hello everyone,
I am still facing this issue. Does anyone have an idea?
For information: when I am now starting my computer it takes 3 minutes (more
or less) to have a fluid desktop. This is happening since the last upgrade of
Friday. This is strange I think. Can we get a log of what is
When I am trying to launch a video file with Totem, the application crashes!
But then I am able to get **the audio back** ?!!??!
Then I am able to launch the video file but with VLC (as the Totem
application is no more working since a few weeks now).
For information: I have posted the error
I am getting the following result:
$ pulseaudio --kill && pulseaudio
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.
Do you think maybe the kill command is not working are expected?
I've tried to kill the process through the System Monitor
Try 'pulseaudio --kill' instead of 'killall pulseaudio'
signature.asc
Description: PGP signature
> This is the message I get if I try to run pulseaudio *without* killing it
first. Are you sure that you ran 'killall' correctly.
I guess so. At least I have run the killing command first. But I have tried
anyway one more time with this:
$ killall pulseaudio && pulseaudio
E: [pulseaudio]
Does this also work for Intel sound drivers (yes my laptop is dependent on
this) with other free systems like Parabola, Devuan, PureOS, GuixSD, Uruk,
Hyperbola etc? This was before successful that I've migrated to Parabola
against nonfree ArchBang early summer 2017.
But also, adding your
> E: [pulseaudio] pid.c: Daemon already running.
> E: [pulseaudio] main.c: pa_pid_file_create() failed.
This is the message I get if I try to run pulseaudio *without* killing it
first. Are you sure that you ran 'killall' correctly. Paste this into a
terminal exactly:
killall pulseaudio &&
Thank you mason for your feedback.
after running the killall puslseaudio and the pulseaudio in a terminal I got
the following messages:
$ pulseaudio
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.
$
I am unable to launch VLC and when I am
In a terminal, run "killall pulseaudio" and then run pulseaudio in a
terminal. Then, try playing something in VLC, playing something in your
browser, adjusting the sound applet in your panel, and opening and adjusting
values in the volume menu. If any errors or warnings appear in the
For information:
- when I am trying to shut down my computer I am getting the following screen
Any ideas? :-)
I have restarted my computer and I am confirming: the starting of my
environment is very slow after my loggin.
Furthermore, I do not have any sound :-/
When I am trying to access to the "Sound" application from the Control Center
I am getting the printscreen in attachment.
I am unable to
I do not know why but the problem is solved!
This is very strange indeed.
This problem occured and at the same time my computer was taking to much time
to starting: to arrive to the desktop and to have my application launch bar
ready to choose a application.
I am going to test if this
I was unable to open the "Sound" application from the Control Center because
I had launched alsamixer in a terminal.
I am still unable to have sound on my computer, this is problematic to me :-/
Anyone is facing the same problem?
35 matches
Mail list logo
