The Linux.uk Community Forum

Hi,

Does anyone know of any computer supplier in the UK or EU which could configure a desktop/workstation
with 4 x 1 TB hard drives and install Debian Buster as the operating system ?

Thanks.

I am using opera-stable_45.0.2552.888_amd64.deb on a Debian Jessie system to
access my emails from a Microsoft Exchange OWA Light system.

However I am having problems with this version of Opera and
am thinking of upgrading it to the latest version for Linux
(version 62).

Please does anyone know whether Jessie would support this
version. If not, which would be the latest version of Opera
that Jessie supports.

I realise that Jessie is an old stable version of Debian, but
I am not able to upgrade it at the moment.

Chrome has problems with producing dropdown menus.

Has anyone else come across this problem ?

Would the latest version of Chrome solve this problem ?

Chrome has now been installed on a Jessie system as follows :-

(1) Logged into home directory as root.

(2) Downloaded google-chrome-stable_current_amd64.deb from

      https://www.google.co.in/chrome/browser/desktop/index.html

      to the home directory.

(3) In the home directory, tried to install Chrome :-

      apt install  ./google-chrome-stable_current_amd64.deb

(4) This failed, giving lots of error messages such as :-

      E: Release 'google-chrome-stable_current_amd64.deb' for 'firefox-l10n-hr' was not found

(5) The command :-

       dpkg -i google-chrome-stable_current_amd64.deb

       was then run.

(6) This gave the messages :-

      Selecting previously unselected package google-chrome-stable.
(Reading database ... 120380 files and directories currently installed.)
Preparing to unpack google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (63.0.3239.84-1) ...
dpkg: dependency problems prevent configuration of google-chrome-stable:
google-chrome-stable depends on libappindicator1; however:
Package libappindicator1 is not installed.

dpkg: error processing package google-chrome-stable (--install):
dependency problems - leaving unconfigured
Processing triggers for menu (2.1.47) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Processing triggers for man-db (2.7.0.2-5) ...
Errors were encountered while processing:
google-chrome-stable


(7) So the command :-

      apt-get -f install

      and then the command :-

      dpkg -i google-chrome-stable_current_amd64.deb

      were run.

( Then the command :-

      google-chrome-stable

     was run to start Chrome.

(9) This produced the following error messages :-

     libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: nouveau
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[32145:32145:1211/192714.812289:ERROR:sandbox_linux.cc(351)] InitializeSandbox() called with multiple threads in process gpu-process.

     Can anyone please explain what these errors mean and how can they be resolved ?

     Chrome runs to some extent but I would like to clear up the above errors.

      Thanks very much.

I am having problems with Chromium (version 57.0.2987.98 amd64) on
a Jessie desktop system.

Drop down menus on certain websites are not working at all (the menus don't drop down). I understand that Chromium on Jessie is no longer supported.

Rather than going through the whole process of updating from Jessie to Stretch in order to get the latest stable Chromium version (62.0.3202.89),
I was thinking of the possibility of installing the latest version of Chrome on Jessie. I have seen several websites that refer to this process :-

https://askubuntu.com/questions/885973/ ... t-on-16-04

https://www.tecmint.com/install-google- ... linux-mint

My intention would be as follows :-

(1) Click on the following link and download the Google Chrome Browser from Google's website, as appropriate to a Debian 64 bit system :-

https://www.google.co.in/chrome/browser ... index.html

I note that Google's repository will be also be added to my system so that
Chrome can automatically be kept up to date.

(2) Perform an update :-

sudo apt-get update

(3) Install Chrome as follows :-

sudo apt-get install ./google-chrome-stable_current_amd64.deb


(4) Run Chrome :-

$ google-chrome-stable


Would this work okay, with no problems at all ?

 A similar problem with Chromium has been reported before :-

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856573

although the above bug was found in chromium-browser/56.0.2924.76-4 amd64  in a Debian 9.0 system,
whereas I am reporting a problem in chromium 57.0.2987.98 amd64 in a Debian 8.0 (Jessie) system.

The problem I am having has been present since Chromium was installed as part of the installation of Jessie.

I have reported my problem to bugs.debian.org as a follow up to bug 856573, but have not heard back.

Many thanks for your suggestions, Mark.

I am a bit mystified, though, as to why you think these suggestions might help.

So I would be very grateful if you could explain a bit about the reasoning behind your suggestions.

Thanks.

Can anyone please help with the following problem ?
Is there a work around ?

No response when clicking to get a drop down menu on various websites.

System : Jessie
Chromium : 57.0.2987.98 amd64

Problem solved by commenting out the line :-

load-module module-console-kit

in /etc/pulse/default.pa

This allows pulseaudio to start.

(module-console-kit had not been installed on the system. Before the above line
was commented out, pulseaudio was prevented from starting via /etc/pulse/default.pa ).

I'm afraid I can't do the boot you suggest at the moment.

In the ~/.config/vlc/vlcrc file I have found :-

# Left (integer)
#aout-remap-channel-left=0

# Center (integer)
#aout-remap-channel-center=1

# Right (integer)
#aout-remap-channel-right=2

# Rear left (integer)
#aout-remap-channel-rearleft=3

# Rear center (integer)
#aout-remap-channel-rearcenter=4

# Rear right (integer)
#aout-remap-channel-rearright=5

# Side left (integer)
#aout-remap-channel-middleleft=6

# Side right (integer)
#aout-remap-channel-middleright=7

# Low-frequency effects (integer)
#aout-remap-channel-lfe=8

# Normalize channels (boolean)
#aout-remap-normalize=1


# Audio output module (string)
aout=pulse


Would it be a good idea to change aout=pulse to aout=alsa

to see if vlc will work properly ?

Another problem has arisen whereby first thing this morning the monitor was
found to be completely black. Switching the monitor off and then on again
gave a "No Signal" message. The computer was eventually restarted but the intermittent
metallic whooping sounds continue.

This whole problem has become very worrying and distressing.

I appreciate that you must be a very busy person, Mark, but would you possibly
be able to offer support over the phone to quicken the solution of the problems that have arisen ?
If you can't personally provide such support, would you be able to suggest a colleague who might be
able to priovide phone support ?

It would greatly help if this support can be provided this evening.

Any such help would be paid for, of course. Just let me know the cost.

Thanks very much if you or a colleague are able to help in this way.

 There is now also a problem with strange sounds
coming through the speakers from time to time.

It is like a metallic whooping sound.

Could this possibly signify a problem with the soundcard, given
the loss of sound problem ?

% cat ~/.asoundrc
No such file or directory


% cat /etc/asound.conf
pcm.!default {
type hw
card 0
}

ctl.!default {
type hw
card 1
}

The iceweasel browser is the browser needed for most work.

vlc appears to now be working although it still gives the following error
(as before):

[000000000104d608] pulse audio output error: PulseAudio server connection failure: Connection refused


Also, there now appears to be sound with the Chromium browser (although this was off and on before so
we shall see if it lasts), but still no sound with the Iceweasel browser.