Posts by hughparker1

hughparker1 · Installation

Hi rolfie and Dutch_Master, thanks for your replies.

I managed to update sources list and then ran the update, upgrade, dist-upgrade commands as suggested.

rebooted then ran autoremove to clean up

all working great! thanks again for you help

hughparker1 · Installation

Hi, I have been using Devuan for quite a while now and I'm running on following release....

hugh@DELL-INSP-DEVUAN:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 1.0 (jessie)
Release:	1.0
Codename:	jessie
hugh@DELL-INSP-DEVUAN:~$

Is this the lastest stable release, if not how can I upgrade? Any advice would be appreciated.

I have tried $ sudo apt dist-upgrade but says nothing to updgrade

hughparker1 · Other Issues

GNUser wrote:

Bummer. Your issue is not lack of sse2 support. I'm afraid I don't know Firefox well enough to know why recent versions are crashing on your machine. I tested both AppImages (52 and 53) and they run okay on my Devuan Jessie 64bit with the default 3.16 kernel.
All I can say for sure is that lately Firefox has been aggressively breaking compatibility (e.g., 52 and up require pulseaudio, 53 and up require sse2). I'd consider not playing their little game and going with a conservative alternative such as Palemoon.

Thanks @GNUser for you help and taking the time to respond to my issue. I will checkout Palemoon and see how it performs on my hardware.

hughparker1 · Other Issues

GNUser wrote:

3.
ExceptionHandler::GenerateDump cloned child 7624
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
This is the show stopper. It means that Firefox53 is crashing. I'm sure this will happen regardless of how you try to run Firefox53 on your system (AppImage or not). If Firefox from Devuan repository works for you but Firefox53 crashes, my guess is that you are running an older processor that, as of Firefox53, is no longer supported (see https://www.mozilla.org/en-US/firefox/5 … uirements/ and https://www.reddit.com/r/linux/comments … 4_or_amd/).
Specifically, as of Firefox53, Firefox requires sse2 support in the CPU. What is the output of this command:
cat /proc/cpuinfo | grep -i sse2 || echo "no sse2 support"
?
If lack of sse2 is indeed your issue, then Firefox52 is the last version that will run on your machine. When the time comes, see Life after Firefox.

Thanks again @GNUser, here it the output you requested...

hugh@DELL-INSP-DEVUAN:~$ cat /proc/cpuinfo | grep -i sse2 || echo "no sse2 support"
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
hugh@DELL-INSP-DEVUAN:~$

Also here is a brief description of the laptop specification...

DELL Inspiron 5559 laptop
Processor: IntelCore i7-6500U CPU 2 Cores, 4 Logical Processors
Integrated Graphics Processor: Intel HD Graphics 520
Discrete Graphics Processor: AMD Radeon R5 M335
Drive: Crucial CT750MX3 SSD size: 750GB
Memory: 16GB 1600MHz DDR3

GNUser wrote:

If you want to give the Firefox52 AppImage a shot, just follow the steps in my post #9 above, but use this instead of the wget line in that post:
wget https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage -O Firefox52.AppImage
I'd be interested in knowing if it's the sse2 issue that made Firefox53 a no-go for you.

I thought I would try your suggestion to check if the Firefox52 AppImage would work to at least try to narrow down the cause of the problem....

$ mkdir -p Firefox_52

$ cd Firefox_52

$ wget https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage -O Firefox52.AppImage

hugh@DELL-INSP-DEVUAN:~/Firefox_52$ wget https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage -O Firefox52.AppImage
converted 'https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage' (ANSI_X3.4-1968) -> 'https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage' (UTF-8)
--2017-06-09 10:47:11--  https://bintray.com/probono/AppImages/download_file?file_path=Firefox-52.0.1.glibc2.3.4-x86_64.AppImage
Resolving bintray.com (bintray.com)... 75.126.118.184
Connecting to bintray.com (bintray.com)|75.126.118.184|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.bintray.com/probono/AppImages/Firefox-52.0.1.glibc2.3.4-x86_64.AppImage [following]
converted 'https://dl.bintray.com/probono/AppImages/Firefox-52.0.1.glibc2.3.4-x86_64.AppImage' (ANSI_X3.4-1968) -> 'https://dl.bintray.com/probono/AppImages/Firefox-52.0.1.glibc2.3.4-x86_64.AppImage' (UTF-8)
--2017-06-09 10:47:12--  https://dl.bintray.com/probono/AppImages/Firefox-52.0.1.glibc2.3.4-x86_64.AppImage
Resolving dl.bintray.com (dl.bintray.com)... 5.153.35.248
Connecting to dl.bintray.com (dl.bintray.com)|5.153.35.248|:443... connected.
HTTP request sent, awaiting response... 302 
Location: https://akamai.bintray.com/98/987cb1d6439e93786696f1ab9c3b22dd90a981d3e081f96752fcaaa2cc9f5d86?__gda__=exp=1497002353~hmac=beb2c832f98f9932372a0d6dd6d25e683776f25dac7e8242df1e92e793a50599&response-content-disposition=attachment%3Bfilename%3D%22Firefox-52.0.1.glibc2.3.4-x86_64.AppImage%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX18uKkxxKQAxyL-j4VZX3KpW7Aioi2i_K-jvoTQPeqkFtLFDqJ12RMJL0hwxyZ5uVJaqXoh87Vdl6JAHFusmpEHJB0JIIHTKufZb_jvFdQgxFpY7AVWVeTuYWYuQLKFL2syAThICoIn-5w [following]
converted 'https://akamai.bintray.com/98/987cb1d6439e93786696f1ab9c3b22dd90a981d3e081f96752fcaaa2cc9f5d86?__gda__=exp=1497002353~hmac=beb2c832f98f9932372a0d6dd6d25e683776f25dac7e8242df1e92e793a50599&response-content-disposition=attachment%3Bfilename%3D%22Firefox-52.0.1.glibc2.3.4-x86_64.AppImage%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX18uKkxxKQAxyL-j4VZX3KpW7Aioi2i_K-jvoTQPeqkFtLFDqJ12RMJL0hwxyZ5uVJaqXoh87Vdl6JAHFusmpEHJB0JIIHTKufZb_jvFdQgxFpY7AVWVeTuYWYuQLKFL2syAThICoIn-5w' (ANSI_X3.4-1968) -> 'https://akamai.bintray.com/98/987cb1d6439e93786696f1ab9c3b22dd90a981d3e081f96752fcaaa2cc9f5d86?__gda__=exp=1497002353~hmac=beb2c832f98f9932372a0d6dd6d25e683776f25dac7e8242df1e92e793a50599&response-content-disposition=attachment;filename="Firefox-52.0.1.glibc2.3.4-x86_64.AppImage"&response-content-type=application/octet-stream&requestInfo=U2FsdGVkX18uKkxxKQAxyL-j4VZX3KpW7Aioi2i_K-jvoTQPeqkFtLFDqJ12RMJL0hwxyZ5uVJaqXoh87Vdl6JAHFusmpEHJB0JIIHTKufZb_jvFdQgxFpY7AVWVeTuYWYuQLKFL2syAThICoIn-5w' (UTF-8)
--2017-06-09 10:47:13--  https://akamai.bintray.com/98/987cb1d6439e93786696f1ab9c3b22dd90a981d3e081f96752fcaaa2cc9f5d86?__gda__=exp=1497002353~hmac=beb2c832f98f9932372a0d6dd6d25e683776f25dac7e8242df1e92e793a50599&response-content-disposition=attachment;filename=%22Firefox-52.0.1.glibc2.3.4-x86_64.AppImage%22&response-content-type=application/octet-stream&requestInfo=U2FsdGVkX18uKkxxKQAxyL-j4VZX3KpW7Aioi2i_K-jvoTQPeqkFtLFDqJ12RMJL0hwxyZ5uVJaqXoh87Vdl6JAHFusmpEHJB0JIIHTKufZb_jvFdQgxFpY7AVWVeTuYWYuQLKFL2syAThICoIn-5w
Resolving akamai.bintray.com (akamai.bintray.com)... 23.63.90.245
Connecting to akamai.bintray.com (akamai.bintray.com)|23.63.90.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 60582136 (58M) [application/octet-stream]
Saving to: 'Firefox52.AppImage'

Firefox52.AppImage      100%[=================================>]  57.78M  1.90MB/s   in 32s    

2017-06-09 10:47:46 (1.81 MB/s) - 'Firefox52.AppImage' saved [60582136/60582136]

hugh@DELL-INSP-DEVUAN:~/Firefox_52$

$ chmod a+x Firefox52.AppImage

$ ./Firefox52.AppImage

hugh@DELL-INSP-DEVUAN:~/Firefox_52$ ./Firefox52.AppImage
zenity, kdialog, Xdialog missing. Skipping ./bin//firefox.wrapper.

(firefox:4023): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed
ExceptionHandler::GenerateDump cloned child 4073
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
hugh@DELL-INSP-DEVUAN:~/Firefox_52$

getting the same "Mozilla Crash Reporter" error message as before.... http://imgur.com/a/NwfhU

I don't have the tech knowledge to understand the results of my tests, is there any clue what is causing Firefox to crash like this?

EDIT: here is the details of the kernel that I am using in case that helps ...

hugh@DELL-INSP-DEVUAN:~$ uname -a
Linux DELL-INSP-DEVUAN 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.18-1~bpo8+1 (2017-04-10) x86_64 GNU/Linux
hugh@DELL-INSP-DEVUAN:~$

hughparker1 · Other Issues

GNUser wrote:

@hughparker1: You don't need sudo to make it executable. Also, for security reasons I recommend not running any web browser as superuser. As to what directory to put the AppImage in, it is completely up to you--an AppImage does not require installation and contains everything it needs inside that one file, which can be run from any directory. It is truly a "portable application".
In case any newbies need a more explicit step-by-step of what to do from the command line:
dest_dir="$HOME/bin" # dest_dir can be anything you want
mkdir -p "$dest_dir"
cd "$dest_dir"
wget https://bintray.com/probono/AppImages/download_file?file_path=Firefox-53.0.2.glibc2.3.4-x86_64.AppImage -O Firefox53.AppImage
chmod a+x Firefox53.AppImage
./Firefox53.AppImage
At that point, you will be asked whether you would like a .desktop file (~/.local/share/applications/appimagekit-firefox.desktop) to be created automatically for you so that you can run the Firefox appimage directly from your applications menu.
That's it At the most, you will be adding a single additional file to your system (either ~/.local/share/applications/appimagekit-firefox.desktop or a little marker file called ~/.local/share/appimagekit/Firefox_no_desktopintegration).
The advantage of using AppImages is the extreme simplicity of one app = one file. The only disadvantage I can think of is not having the convenience of getting security fixes through your package manager.
P.S. In case you'd like to see what's contained inside the AppImage:
./Firefox53.AppImage --appimage-extract

Thanks @GNUser for the clear instructions, I haven't been able to try it till today, but I get the same "Mozilla Crash Reporter" error message as before.... http://imgur.com/a/NwfhU

Here is the steps I did, in case I made some mistake....

hugh@DELL-INSP-DEVUAN:~$ mkdir -p Firefox_New
hugh@DELL-INSP-DEVUAN:~$

hugh@DELL-INSP-DEVUAN:~$ cd Firefox_New
hugh@DELL-INSP-DEVUAN:~/Firefox_New$

hugh@DELL-INSP-DEVUAN:~/Firefox_New$ wget https://bintray.com/probono/AppImages/download_file?file_path=Firefox-53.0.2.glibc2.3.4-x86_64.AppImage -O Firefox53.AppImage
converted 'https://bintray.com/probono/AppImages/download_file?file_path=Firefox-53.0.2.glibc2.3.4-x86_64.AppImage' (ANSI_X3.4-1968) -> 'https://bintray.com/probono/AppImages/download_file?file_path=Firefox-53.0.2.glibc2.3.4-x86_64.AppImage' (UTF-8)
--2017-06-08 11:37:16--  https://bintray.com/probono/AppImages/download_file?file_path=Firefox-53.0.2.glibc2.3.4-x86_64.AppImage
Resolving bintray.com (bintray.com)... 108.168.194.93
Connecting to bintray.com (bintray.com)|108.168.194.93|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.bintray.com/probono/AppImages/Firefox-53.0.2.glibc2.3.4-x86_64.AppImage [following]
converted 'https://dl.bintray.com/probono/AppImages/Firefox-53.0.2.glibc2.3.4-x86_64.AppImage' (ANSI_X3.4-1968) -> 'https://dl.bintray.com/probono/AppImages/Firefox-53.0.2.glibc2.3.4-x86_64.AppImage' (UTF-8)
--2017-06-08 11:37:17--  https://dl.bintray.com/probono/AppImages/Firefox-53.0.2.glibc2.3.4-x86_64.AppImage
Resolving dl.bintray.com (dl.bintray.com)... 5.153.35.248
Connecting to dl.bintray.com (dl.bintray.com)|5.153.35.248|:443... connected.
HTTP request sent, awaiting response... 302 
Location: https://akamai.bintray.com/8d/8d5708398bccb911c793a4d0098c69a0f7a62955df66c8735c9096be73b8dd0b?__gda__=exp=1496918960~hmac=446aea627b038d05d246df20ba037f123ec9e52f9e631b3eb6185a85681f6793&response-content-disposition=attachment%3Bfilename%3D%22Firefox-53.0.2.glibc2.3.4-x86_64.AppImage%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX1-KLVXw7cionUT2yF-SIU9pm-emtZJV5J3cV8znsWYTc6sSFGxP-Mzcrbiiu1ZIDl3sIr3Mr4ESlJCM7Hbyw_eeLFkvZQekUKeevS46SVV6VfTB5h_5m46A4dJJXj-p1jTNssBn1t6Cgg [following]
converted 'https://akamai.bintray.com/8d/8d5708398bccb911c793a4d0098c69a0f7a62955df66c8735c9096be73b8dd0b?__gda__=exp=1496918960~hmac=446aea627b038d05d246df20ba037f123ec9e52f9e631b3eb6185a85681f6793&response-content-disposition=attachment%3Bfilename%3D%22Firefox-53.0.2.glibc2.3.4-x86_64.AppImage%22&response-content-type=application%2Foctet-stream&requestInfo=U2FsdGVkX1-KLVXw7cionUT2yF-SIU9pm-emtZJV5J3cV8znsWYTc6sSFGxP-Mzcrbiiu1ZIDl3sIr3Mr4ESlJCM7Hbyw_eeLFkvZQekUKeevS46SVV6VfTB5h_5m46A4dJJXj-p1jTNssBn1t6Cgg' (ANSI_X3.4-1968) -> 'https://akamai.bintray.com/8d/8d5708398bccb911c793a4d0098c69a0f7a62955df66c8735c9096be73b8dd0b?__gda__=exp=1496918960~hmac=446aea627b038d05d246df20ba037f123ec9e52f9e631b3eb6185a85681f6793&response-content-disposition=attachment;filename="Firefox-53.0.2.glibc2.3.4-x86_64.AppImage"&response-content-type=application/octet-stream&requestInfo=U2FsdGVkX1-KLVXw7cionUT2yF-SIU9pm-emtZJV5J3cV8znsWYTc6sSFGxP-Mzcrbiiu1ZIDl3sIr3Mr4ESlJCM7Hbyw_eeLFkvZQekUKeevS46SVV6VfTB5h_5m46A4dJJXj-p1jTNssBn1t6Cgg' (UTF-8)
--2017-06-08 11:37:18--  https://akamai.bintray.com/8d/8d5708398bccb911c793a4d0098c69a0f7a62955df66c8735c9096be73b8dd0b?__gda__=exp=1496918960~hmac=446aea627b038d05d246df20ba037f123ec9e52f9e631b3eb6185a85681f6793&response-content-disposition=attachment;filename=%22Firefox-53.0.2.glibc2.3.4-x86_64.AppImage%22&response-content-type=application/octet-stream&requestInfo=U2FsdGVkX1-KLVXw7cionUT2yF-SIU9pm-emtZJV5J3cV8znsWYTc6sSFGxP-Mzcrbiiu1ZIDl3sIr3Mr4ESlJCM7Hbyw_eeLFkvZQekUKeevS46SVV6VfTB5h_5m46A4dJJXj-p1jTNssBn1t6Cgg
Resolving akamai.bintray.com (akamai.bintray.com)... 23.63.90.245
Connecting to akamai.bintray.com (akamai.bintray.com)|23.63.90.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 61479160 (59M) [application/octet-stream]
Saving to: 'Firefox53.AppImage'

Firefox53.AppImage                100%[============================================================>]  58.63M  1.85MB/s   in 38s    

2017-06-08 11:37:58 (1.53 MB/s) - 'Firefox53.AppImage' saved [61479160/61479160]

hugh@DELL-INSP-DEVUAN:~/Firefox_New$

hugh@DELL-INSP-DEVUAN:~/Firefox_New$ chmod a+x Firefox53.AppImage
hugh@DELL-INSP-DEVUAN:~/Firefox_New$

hugh@DELL-INSP-DEVUAN:~/Firefox_New$ ./Firefox53.AppImage
zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_Cdg7JV/usr/bin//firefox.wrapper.

(firefox:7574): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed
ExceptionHandler::GenerateDump cloned child 7624
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
hugh@DELL-INSP-DEVUAN:~/Firefox_New$

So I'm not sure what went wrong, is there any clue in the output above? any help would be appreciated.

hughparker1 · Other Issues

Spass wrote:

hughparker1, hmm, seems to me that all your steps are correct. I've downloaded that version you mentioned (64-bit) and it works on my machine just fine. Maybe try creating a new profile?
$ cd /home/hugh/Applications/firefox
$ ./firefox -P
Or go with GNUser's advice from post #5.

Thanks @Spass for feedback, I was looking at GNUser's advice from post #5 but I have never used AppImages before, so I had a look online and found some advice here ...

https://askubuntu.com/questions/774490/ … install-it

GNUser wrote:

1. Download the latest Firefox*.AppImage (available here: https://bintray.com/probono/AppImages/F … .3.4#files)
2. Make it executable
3. Run it and enjoy

Hi @GNUser, thanks for the suggestion to use .AppImage, I haven't used this before so I wondered is this the correct way to make it executable, and is it ok to run without sudo in front?

$ chmod a+x Firefox-53.0.2.glibc2.3.4-x86_64.AppImage

And is this the correct way to execute the appImage, do I need sudo and run from the Download folder?

$ ./Firefox-53.0.2.glibc2.3.4-x86_64.AppImage

Also, is there any disadvantage in using this method? Thank you @GNUser and @Spass for your feedback and support.

hughparker1 · Other Issues

Spass wrote:

Unfortunately there's no newer Firefox package in the stable repos at the moment, but I found a way to use newest Firefox ESR (currently 52.1.2) on my Devuan Jessie without a problem. I will explain that later in this post.
(Note: New versions of Firefox (52 and up) require PulseAudio for audio playback, see here.)
Q1. You can check it this way for example:
# apt-get update
$ apt-cache search firefox    << this will show you the list of packages with 'firefox' in their names
$ apt-cache policy firefox-esr    << this will show you installed version (if any) and versions available in the repos
Q2. You should use:
# apt-get install -t jessie-backports package_name
That's probably not the "best way to install latest version of Firefox", but my solution was:
1) I've downloaded Firefox 52 ESR from here > https://www.mozilla.org/en-US/firefox/o … tions/all/
2) I extracted it and copied 'firefox' folder to my home directory (for example /home/my_name/Applications/)
3) I changed default web browser in Preferred Applications settings (exo-preferred-applications), choosing "Other..." The path should be something like this - /home/your_name/Applications/firefox/firefox "%s"
You can also add individual ".desktop" entry for it in the ~/.local/share/applications/ folder (that way it will show in the main menu) or you can just use "Web Browser" entry (exo-open --launch WebBrowser %u) to open it. You can use GUI tool 'menulibre' for adding desktop entries.
And that's it, now I'm on newest ESR branch, it uses my settings from ~/.mozilla/ without a problem, it even auto-updates, everything works fine. Well, almost... Still, from time to time some links want to open in the "older" Firefox 45, because the newer one is not registered as a default browser system-wide (it doesn't show in the update-alternatives --config x-www-browser). I didn't find a way to do it 100% correctly yet. Maybe it should be placed somewhere in the /bin or /lib folders instead of /home?
// EDIT: That issue was solved by smoki one post below. Thanks!
If something is unclear or you have more questions, I'll try to help. Cheers.

Many thanks for your help and clear instructions. I tried to do as you suggested, here are my steps...

https://www.mozilla.org/en-US/firefox/o … tions/all/

downloaded English (British) "firefox-52.1.2esr.tar.bz2"

create new directory /home/hugh/Applications/

extract .tar.bz2 file and then copy extracted "firefox" folder to /home/hugh/Applications/

$ cp -avr /home/hugh/Downloads/firefox /home/hugh/Applications

(N) Settings > Preferred Application > (T) Internet
Web Browser: Debian Sensible Browser (default) change to...
Web Browser: Other...
/home/hugh/Applications/firefox/firefox "%s"

when I open firefox I get error message... http://imgur.com/a/jtBym I even tried clicking the "firefox" executable in my /home/hugh/Applications/firefox folder but get same message.

Not sure if I did something incorrectly, does the error indicate what is wrong?

hughparker1 · Other Issues

I have installed Devuan Xfce and would like to use the latest version of Firefox as the default version 45.9.0 is quite old, not sure if it is ok to do this and if I can use backports. So I have a couple of questions....

Q1. not sure of package name, is there a way to find the correct package name and version before installing?

Q2. would this be the correct syntax to use to install?

$ apt-get -t jessie-backports install package_name

Thanks for any advice as I am still quite new to linux

hughparker1 · Installation

fsmithred wrote:

Maybe you need to install the firmware from backports.
apt-get -t jessie-backports install firmware-iwlwifi

Thanks @fsmithred for your help, guess what, it worked! That was a good call, thank you for your recommendation. Now I can set this topic to resolved.

I have learned a lot over this over the past 4 days , it looks like when you add backports to your sources.list, you have to explicitly install each package from backports using "apt-get -t jessie-backports install package_name" which allows you to control which distribution or release the packages will be retrieved from. I guess it makes sense otherwise you might make you system unstable if you got everything upgraded when you run the usual "apt-get update/upgrade" command, therefore it looks to me that you are in control?

Also learned how to check wireless drivers. But I think I have a lot more still to learn. Thank you to @fsmithred, @lazlo, @golinux and @greenjeans for your excellent instructions and feedback.

hughparker1 · Installation

lazlo wrote:

@hughparker1 The kernel module for the wifi NIC isn't loading. The firmware and the kernel module are two separate things that work together and both have to be running.
No wifi driver is listed in your lspci output:
...
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] (rev 81)
Subsystem: Dell Device 06b2
Kernel driver in use: radeon
02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless AC 3160
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07)
Subsystem: Dell Device 06b2
Kernel driver in use: r8169
...
So if the update-initramfs -u and a reboot doesn't fix it try this:
sudo modprobe iwlwifi
If that works there will be no output from the command. If it doesn't work you'll get a an error and can check the kernel logs for more info.
To see what is keeping it from loading (either with modprobe or on boot) check the kernel log for errors:
dmesg | egrep 'error|iwlwifi'
If you want to keep the latest portion of the kernel log updating in another TTY you can use tail:
tail -f /var/log/dmesg
That would allow you execute a command in one TTY and then switch to the one running tail to see what the kernel just logged into dmesg. That's handy if the grep command is returning information that is not useful for some reason.
If the module loads then check if the WNIC is running with ifconfig:
sudo ifconfig
If needed do:
sudo ifconfig wlan0 up
Once you can see it listed in the output from ifconfig wicd should be able to handle everything else though.
Good luck!
lazlo

Thanks @lazlo for your feedback and suggestions to resolve my problem with wireless network.

I have ran the commands you suggested and the outputs are below...

EDIT2: forgot to include these ...

$ sudo update-initramfs -u

hugh@DELL-INSP-DEVUAN:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.2-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
live-boot: core filesystems devices utils udev wget blockdev.
hugh@DELL-INSP-DEVUAN:~$

REBOOT but still no wi-fi

so run this command...

$ sudo modprobe iwlwifi

hugh@DELL-INSP-DEVUAN:~$ sudo modprobe iwlwifi
[sudo] password for hugh: 
hugh@DELL-INSP-DEVUAN:~$

no output but also no error messages

no wi-fi yet so REBOOT but still no wi-fi

first terminal window........

hugh@DELL-INSP-DEVUAN:~$ sudo dmesg | egrep 'error|iwlwifi'
[sudo] password for hugh: 
[    2.364163] tpm_crb: probe of MSFT0101:00 failed with error -16
[    2.539868] i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1_26.bin failed with error -2
[    2.542515] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[    2.547727] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-3160-17.ucode (-2)
[    2.547731] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2
[    2.633304] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_pfp.bin failed with error -2
[    2.633823] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_me.bin failed with error -2
[    2.635139] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_ce.bin failed with error -2
[    2.635350] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_rlc.bin failed with error -2
[    2.635565] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_mc.bin failed with error -2
[    2.636201] radeon 0000:01:00.0: Direct firmware load for radeon/hainan_k_smc.bin failed with error -2
[    2.683163] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq failed with error -2
hugh@DELL-INSP-DEVUAN:~$

second terminal window....

hugh@DELL-INSP-DEVUAN:~$ sudo tail -f /var/log/dmesg
[sudo] password for hugh: 
[    4.288739] lp: driver loaded but no devices found
[    4.292337] ppdev: user-space parallel port driver
[    4.301771] fuse init (API version 7.26)
[    4.675720] RPC: Registered named UNIX socket transport module.
[    4.675721] RPC: Registered udp transport module.
[    4.675722] RPC: Registered tcp transport module.
[    4.675722] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    4.678942] FS-Cache: Loaded
[    4.687961] FS-Cache: Netfs 'nfs' registered for caching
[    4.697357] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

first terminal window........

hugh@DELL-INSP-DEVUAN:~$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 84:7b:eb:13:91:2f  
          inet addr:192.168.1.8  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::867b:ebff:fe13:912f/64 Scope:Link
          inet6 addr: fd58:1f28:a661:b500:867b:ebff:fe13:912f/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16677 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1531 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1871547 (1.7 MiB)  TX bytes:167785 (163.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:33 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:3466 (3.3 KiB)  TX bytes:3466 (3.3 KiB)

hugh@DELL-INSP-DEVUAN:~$

first terminal window........

hugh@DELL-INSP-DEVUAN:~$ sudo ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device
hugh@DELL-INSP-DEVUAN:~$

Note: no change in second terminal window after the additional commands were run in the first terminal

Wicd Network Manager still says "No wireless networks found"

To be honest I don't know enough about linux to be able to examine the output and diagnose what the problem is so any advice on what I can do would be appreciated. Thanks again for the continued support, very much appreciated.

EDIT: would it help if i uninstalled and then reinstalled "firmware-iwlwifi"

hughparker1 · Installation

greenjeans wrote:

Well i'm not the ninja here obviously, but wondering if maybe you need to run update-initramfs -u?
I would think that would occur as part of the process after installing a new kernel but I could be wrong, thus my suggestion.

Thanks @greenjeans I didn't know if there was any other step required as I haven't done kerknel upgrade in terminal before. I'll try it later today when I get home and let you know how I get on. Cheers.

hughparker1 · Installation

golinux wrote:

hughparker1 wrote:
Would it be worth installing the latest testing kernel on Devuan while I still have ascii in my sources.list?
Disable the ascii repo. Add the Devuan backports repo and try that kernel first. I think it's at least 4.9 something.

fsmithred wrote:

Yes, go with backports. Disable ascii. All the devs have been focused on getting jessie ready, and not much work has been done on ascii.
apt-get -t jessie-backports install linux-image-4.9.0-0.bpo.2-amd64

Thanks @golinux and @fsmithred for advice and continued support

I installed latest kernel ...

$ apt-get -t jessie-backports install linux-image-4.9.0-0.bpo.2-amd64

and now boots to Desktop without 'nomodeset' in linux line. Success!

Also Redshift is working perfectly now at sunset Success!

And my Brightness function keys are working now Success!

Only one small problem, no wi-fi detected which was working before I installed new kernel, very strange.

When I click on Wicd Network Manager is just says 'No wireless network found'

I plugged in a network cable and tried installing the non-free package I normally use for Debian install...

$ sudo apt install firmware-iwlwifi

hugh@DELL-INSP-DEVUAN:~$ sudo apt install firmware-iwlwifi
Reading package lists... Done
Building dependency tree       
Reading state information... Done
firmware-iwlwifi is already the newest version.
The following packages were automatically installed and are no longer required:
  grub-pc-bin libelfg0 libgeoclue0 libnm-glib4 libnm-util2 libuuid-perl
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
hugh@DELL-INSP-DEVUAN:~$

... so it looks like it's already installed but it's not working. Has anyone encountered this before?

this is the output for '$ lspci -k'

hugh@DELL-INSP-DEVUAN:~$ lspci -k
00:00.0 Host bridge: Intel Corporation Device 1904 (rev 08)
	Subsystem: Dell Device 06b2
	Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation Device 1916 (rev 07)
	Subsystem: Dell Device 06b2
	Kernel driver in use: i915
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Device 9d60 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: intel-lpss
00:15.1 Signal processing controller: Intel Corporation Device 9d61 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: intel-lpss
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
	Kernel driver in use: mei_me
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: ahci
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Device 9d14 (rev f1)
	Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation Device 9d15 (rev f1)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)
	Subsystem: Dell Device 06b2
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
	Subsystem: Dell Device 06b2
00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)
	Subsystem: Dell Device 06b2
	Kernel driver in use: i801_smbus
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] (rev 81)
	Subsystem: Dell Device 06b2
	Kernel driver in use: radeon
02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless AC 3160
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07)
	Subsystem: Dell Device 06b2
	Kernel driver in use: r8169
hugh@DELL-INSP-DEVUAN:~$

Is there something else I can do to get wi-fi working again? I checked and wi-fi still works with live USB and on other partitions.

Thanks for all the help received so far, it is much appreciated. Just one little hurdle to overcome.

hughparker1 · Installation

fsmithred wrote:

I have this feeling that it might be related to the fact I needed to add nomodeset to linux boot line in grub
Trust the Force, Luke. You are correct.
I just booted with 'nomodeset' and redshift no longer works. Neither does my brightness script that I've been using.

Thanks for feedback. I was wondering if the problem I'm having is something to do with the kernel I am using in Devuan which is a lot older than the other two OS I use on my laptop which I bought just last year ...

....................... Kernel version
Devuan Xfce 3.16.43-2
Linux Mint Xfce 4.10.0-20
Debian Stretch Xfce 4.9.18-1

Would it be worth installing the latest testing kernel on Devuan while I still have ascii in my sources.list? ( EDIT: then maybe I wouldn't need to add nomodeset to linux boot line)

I had a look at what is currently available....

hugh@DELL-INSP-DEVUAN:~$ apt-cache search linux-image
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
linux-image-4.9.0-0.bpo.2-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.2-amd64
linux-image-4.9.0-0.bpo.2-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-0.bpo.2-rt-amd64-dbg - Debugging symbols for Linux 4.9.0-0.bpo.2-rt-amd64
linux-image-4.9.0-0.bpo.2-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-2-grsec-amd64 - Linux 4.9 for 64-bit PCs, Grsecurity protection
linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-image-4.9.0-0.bpo.2-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-0.bpo.2-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-4.9.0-2-amd64-unsigned - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-2-rt-amd64-unsigned - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-2-amd64 - Linux 4.9 for 64-bit PCs (signed)
linux-image-4.9.0-2-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)
hugh@DELL-INSP-DEVUAN:~$

... and I thought Linux 4.9+79 for 64-bit PCs (signed) looks like the latest...

hugh@DELL-INSP-DEVUAN:~$ apt show linux-image-4.9.0-2-amd64
Package: linux-image-4.9.0-2-amd64
Source: linux-signed (4.4)
Version: 4.9.18-1
Installed-Size: 189 MB
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Replaces: linux-image-4.9.0-2-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool
Recommends: firmware-linux-free, irqbalance
Suggests: linux-doc-4.9, debian-kernel-handbook, grub-pc | grub-efi-amd64 | extlinux
Conflicts: linux-image-4.9.0-2-amd64-unsigned
Breaks: initramfs-tools (<< 0.120+deb8u2), xserver-xorg-input-vmmouse (<< 1:13.0.99)
Homepage: https://www.kernel.org/
Built-Using: linux (= 4.9.18-1)
Section: kernel
Priority: optional
Download-Size: 39.1 MB
APT-Sources: http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
Description: Linux 4.9 for 64-bit PCs (signed)

hugh@DELL-INSP-DEVUAN:~$

Would I just need to run following command to install...

$ sudo apt-get install linux-image-4.9.0-2-amd64

.. or is there more steps required? I've never upgraded kernel from the terminal before so don't know if there is more to this than a single command.

the other option I suppose is to do full ascii upgrade except I remember what @golinux said the other day....

golinux wrote:

You probably don't want to upgrade to ascii - it is a bit broken atm. Just enable the ascii repo to get that one package then disable it immediately. Along the way, there may be unresolved dependencies and installing from different releases always has a risk of 'unintended consequences'. Depends how adventurous you are and on your tolerance for breaking things. Of course it may be perfectly fine. Your choice.
Look at the bottom of this page for source information.
Note that I am very conservative while others think nothing of leaping into the unknown.

So I'm wondering if it's worth a try. I could just follow the steps I found in this link https://talk.devuan.org/t/upgrading-dev … -ascii/363 do those instructions looks OK?

Since Devuan isn't my daily driver at the moment (especially with no redshift for late evening work) I wonder if a full upgrade would be worth considering. At the moment I mainly use Debian Stretch and haven't come across any problems since since installing late last year. That's why I was thinking that Devuan testing might be worth considering. I do realise there is always some risk. Any advice/guidance would be appreciated.

hughparker1 · Installation

fsmithred wrote:

Make sure randr is installed. Check in synaptic. You can also see what methods are available to redshift with
redshift -m list
I can start 'redshift-gtk' on the command line if I give it my latitude and longitude. It works, it puts an icon in the system tray, and I can get an information window from that.

thanks for feedback, I opened terminal and ran 'redshift -m list'...

hugh@DELL-INSP-DEVUAN:~$ redshift -m list
Available adjustment methods:
  drm
  randr
  vidmode
  dummy

Specify colon-separated options with `-m METHOD:OPTIONS'.
Try `-m METHOD:help' for help.
hugh@DELL-INSP-DEVUAN:~$

Not sure what the output means to be honest, any advice would be appreciated.

I also tried opening terminal and running command with my my latitude and longitude....

$ redshift-gtk -l 55.82:-4.42 -t 6500:3400

but same happens as before, icon appears and error message window popped up...

Failed to run Redshift
Gamma ramp size too small: 0
Failed to start adjustment method randr.
(B) Close

then icon disappears again when I click OK

This is the same error that appears when I start redshift from the menu

I also opened synaptic package manager and searched for 'randr' and following packages were returned .....

libxcb-randr0
libxrandr2
x11-xserver-utils
xserver-xorg-video-nouv

I didn't see a separate package specifically called 'randr'

Then I checked the same packages/versions in my other two partitions Debian and Linux Mint where redshift is working OK, and compared them with Devuan...

Debian Mint Devuan
libxcb-randr0 1.12-1 1.11.1 1.10-3+b1
libxrandr2 2:1.5.1-1 2:1.5.0-1 2:1.4.2-1+b1
x11-xserver-utils 7.7+7+b 1 7.7+7 7.7+3+b1
xserver-xorg-video-nouv1:1.0.13-3 1:1.0.12 1:1.0.11-1

I noticed there are slightly older versions for the four packages in Devuan

Also noticed there is a slightly different package name in Devuan for package 'xserver-xorg-video-nouveau'

So I upgraded the four packages to latest versions by re-enabling testing suite 'ascii' in /etc/apt/sources.list.d/devuan-ascii.list

reboot but still redshift no different from before.

not sure what else I can try. I have this feeling that it might be related to the fact I needed to add nomodeset to linux boot line in grub, since redshift works in both Debian and Mint partitions so the hardware seems to be OK. And I don't need to have 'nomodeset' in the linux boot line in grub for Debian and Mint partitions. So maybe that's the problem? Just a wild guess as I'm not too technical with linux yet.

hughparker1 · Installation

Just thought I would mention that when I run open terminal and run 'redshift -v' it does seem to pick up details from '~/.config/redshift.conf' OK ....

hugh@DELL-INSP-DEVUAN:~$ redshift -v
Location: 55.83 N, 4.42 W
Temperatures: 6500K at day, 3400K at night
Solar elevations: day above 3.0, night below -6.0
Brightness: 1.00:1.00
Gamma (Daytime): 0.800, 0.800, 0.800
Gamma (Night): 0.800, 0.800, 0.800
Gamma ramp size too small: 0
Failed to start adjustment method randr.
hugh@DELL-INSP-DEVUAN:~$

so redshift.conf file seems to be recognised, but it shows error in the last two lines...

Gamma ramp size too small: 0
Failed to start adjustment method randr.

hughparker1 · Installation

Thanks for feedback.

I created a new file... /etc/apt/sources.list.d/devuan-ascii.list
and added these lines...

# for the testing suite
deb http://auto.mirror.devuan.org/merged ascii main

then run sudo apt update then opened Synaptic Package Manager: search for 'redshift' (select redshift-gtk for install)

then start redshift from menu and icon appears but error message window popped up...

Failed to run Redshift
Gamma ramp size too small: 0
Failed to start adjustment method randr.
(B) Close

then icon disappears again.

There are several computers in my home with redshift installed and working, I checked what also gets installed along with redshift-gtk....

these packages should be installed:

redshift-gtk installed = yes
redshift installed = yes
geoclue-2.0 installed = yes
iio-sensor-proxy installed = no
libgeoclue-2.0 installed = yes

So 'iio-sensor-proxy' is missing in Devuan and perhaps this is significant, but not sure.

but when I try to install 'iio-sensor-proxy' I get following message...

Could not mark all packages for installation or upgrade
The following packages have unresolvable dependencies. Make sure that all required repositories are added and enabled in the preferences
iio-sensor-proxy Depends: systemd but it is not installable

not sure what I can do, I have Debian on another partition on my laptop and redshift is working ok.

Also, I just noticed that my brightness function keys are not working, so not sure if that gives us a clue as to why I am having problems with redshift not working.

hughparker1 · Installation

golinux wrote:

Would be better to get the pkg from Devuan Ascii than Debian Stretch to avoid conflicts down the line. No guarantee that either one won't break jessie though . . .

Thanks again @golinux, I just found this link ... https://talk.devuan.org/t/upgrading-dev … -ascii/363

...the steps look straightforward enough, is there anything I should be careful about? I realise there are no guarantees though.

hughparker1 · Installation

golinux wrote:

Would be better to get the pkg from Devuan Ascii than Debian Stretch to avoid conflicts down the line. No guarantee that either one won't break jessie though . . .

I'll check out your recommendation, haven't heard about Devuan Ascii but I'll have a look for it. Thanks @golinux for your help.

hughparker1 · Installation

I found a "redshift-gtk_1.11-1_all.deb" package on the debian website....

https://packages.debian.org/stretch/redshift-gtk

Looks like this version is for Debian stretch, but I wondered if it was worth trying to install it, or does anyone know if it would NOT be advisable to do this in Devuan as I understand that Devuan RC2 is based on Debian stable.

I haven't installed from a .deb file before but I had a look online and found this can be done by running following command in terminal...

$ sudo dpkg -i redshift-gtk_1.11-1_all.deb

Would it be safe enough to install this package? I'm not very knowledgeable on installing from terminal, as I have only installed via Synaptic Package Manager before now.

Alternatively, is adding a jessie-backports line to my sources.list a viable option...

deb http://ftp.debian.org/debian jessie-backports main

I apologise if is this a stupid idea, but I'm still learning Linux so not sure if these are realistic options. Any advice/guidance would be appreciated.

hughparker1 · Installation

fsmithred wrote:

@FOSSuser: Good call.
@hughparker1: the correct locale to choose is en_GB

Thanks @FOSSuser and @fsmithred for your support

I think I must have selected 'uk_UA.UTF-8 UTF-8' as my locale because I see 'set lang=uk_UA' in my '/boot/grub/grub.cfg'

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=uk_UA
  insmod gettext

when I try to change this it doesn't seem to work....

$ sudo dpkg-reconfigure locales

  
Package configuration                                                           

 ┌──────────────────────────┤ Configuring locales ├──────────────────────────┐  
 │ Locales are a framework to switch between multiple languages and allow    │  
 │ users to use their language, country, characters, collation order, etc.   │  
 │                                                                           │  
 │ Please choose which locales to generate. UTF-8 locales should be chosen   │  
 │ by default, particularly for new installations. Other character sets may  │  
 │ be useful for backwards compatibility with older systems and software.    │  
 │                                                                           │  
 │ Locales to be generated:                                                  │  
 │                                                                           │  
 │    [ ] en_DK.UTF-8 UTF-8                                                  │  
 │    [ ] en_GB ISO-8859-1                                                   │  
 │    [ ] en_GB.ISO-8859-15 ISO-8859-15                                  ▒   │  
 │    [ ] en_GB.UTF-8 UTF-8                                              ▒   │  
 │    [ ] en_HK ISO-8859-1                                                   │  
 │                                                                           │  
 │                                                                           │  
 │                    <Ok>                        <Cancel>                   │  
 │                                                                           │  
 └───────────────────────────────────────────────────────────────────────────┘

when I select 'en_GB.UTF-8 UTF-8' and tab to highlight <Ok> then press enter

I get this screen...

Package configuration                                                           
 ┌──────────────────────────┤ Configuring locales ├──────────────────────────┐  
 │ Many packages in Debian use locales to display text in the correct        │  
 │ language for the user. You can choose a default locale for the system     │  
 │ from the generated locales.                                               │  
 │                                                                           │  
 │ This will select the default language for the entire system. If this      │  
 │ system is a multi-user system where not all users are able to speak the   │  
 │ default language, they will experience difficulties.                      │  
 │                                                                           │  
 │ Default locale for the system environment:                                │  
 │                                                                           │  
 │                                None                                       │  
 │                                C.UTF-8                                    │  
 │                                en_US.UTF-8                                │  
 │                                uk_UA.UTF-8                                │  
 │                                                                           │  
 │                                                                           │  
 │                    <Ok>                        <Cancel>                   │  
 │                                                                           │  
 └───────────────────────────────────────────────────────────────────────────┘

...but 'en_GB.UTF-8 UTF-8' is not on the list so I selected 'en_US.UTF-8' and pressed enter

the output in terminal now shows...

hugh@DELL-INSP-DEVUAN:~$ sudo dpkg-reconfigure locales
Generating locales (this might take a while)...
en_US.UTF-8... done
uk_UA.UTF-8... done
Generation complete.
hugh@DELL-INSP-DEVUAN:~$

... but when I reboot I still see the russian like characters on the grub menu screen, and my keyboard is still showing English (UK) same as before. So maybe this can't be fixed, or is there a step I missed ?

EDIT: the step I missed was

$ sudo update-grub

after reboot, I see english in the GRUB MENU silly me

hughparker1 · Installation

FOSSuser wrote:

Have you seen this before? I chose UK during the install process so not sure why there is russian text showing.
I have a feeling that uk is Ukranian, probably need en or gb.

thanks for feedback, I'm not sure if I chose en or gb or uk to be honest, I'm not sure what was displayed on the list of options, I should have taken a note. but I did have to change the keyboard from US to English (UK) after the install when I rebooted, so not sure if that gives a clue or not.

hughparker1 · Installation

DELL Inspiron 5559
Processor: IntelCore i7-6500U CPU 2 Cores, 4 Logical Processors
Integrated Graphics Processor: Intel HD Graphics 520
Discrete Graphics Processor: AMD Radeon R5 M335
Drive: Crucial CT750MX3 SSD size: 750GB
Memory: 16GB

Hi, I have installed the latest image 'devuan_jessie_1.0.0-RC2_amd64_uefi-live.iso' on my DELL laptop.

Then I installed 'gtk-redshift' via synaptic package manager (couldn't find usual redshift-gtk package)

I have also copied my config file as I would normally do....

sudo cp redshift.conf ~/.config/

here is contents of redshift.conf

; Global settings for redshift
[redshift]
; Set the day and night screen temperatures
temp-day=6500
temp-night=3400

; Enable/Disable a smooth transition between day and night
; 0 will cause a direct change from day to night screen temperature.
; 1 will gradually increase or decrease the screen temperature.
transition=1

; Set the screen brightness. Default is 1.0.
;brightness=0.9

; It is also possible to use different settings for day and night
; since version 1.8.
;brightness-day=0.7
;brightness-night=0.4

; Set the screen gamma (for all colors, or each color channel
; individually)
gamma=0.8
;gamma=0.8:0.7:0.8
; This can also be set individually for day and night since
; version 1.10.
;gamma-day=0.8:0.7:0.8
;gamma-night=0.6

; Set the location-provider: 'geoclue', 'geoclue2', 'manual'
; type 'redshift -l list' to see possible values.
; The location provider settings are in a different section.
location-provider=manual

; Set the adjustment-method: 'randr', 'vidmode'
; type 'redshift -m list' to see all possible values.
; 'randr' is the preferred method, 'vidmode' is an older API.
; but works in some cases when 'randr' does not.
; The adjustment method settings are in a different section.
adjustment-method=randr

; Configuration of the location-provider:
; type 'redshift -l PROVIDER:help' to see the settings.
; ex: 'redshift -l manual:help'
; Keep in mind that longitudes west of Greenwich (e.g. the Americas)
; are negative numbers.
[manual]
lat=55.825
lon=-4.417

; Configuration of the adjustment-method
; type 'redshift -m METHOD:help' to see the settings.
; ex: 'redshift -m randr:help'
; In this example, randr is configured to adjust screen 1.
; Note that the numbering starts from 0, so this is actually the
; second screen. If this option is not specified, Redshift will try
; to adjust _all_ screens.
[randr]
screen=0

I have used this config file many times in the past and it usually works ok.

...but redshift fails to start via the applications menu (this also happens with Synaptic Package Manager, not sure why this is happening) so I need to start via terminal but I get following error message...

hugh@DELL-INSP-DEVUAN:~$ sudo redshift
[sudo] password for hugh: 
Trying location provider `geoclue'...
Unable to obtain master client: The name org.freedesktop.Geoclue.Master was not provided by any .service files
Failed to start provider geoclue.
Trying next provider...
Trying location provider `manual'...
Latitude and longitude must be set.
hugh@DELL-INSP-DEVUAN:~$

I tried installing 'geoclue' then 'geoclue-2.0' but made no difference.

I have installed redshift several times in the past and normally have no problems.

I'm not sure if there is something wrong with my configuration so I was wondering if anyone had experienced this same error on Devuan and how I can fix it. I have limited technical skills but can use terminal if I know the correct syntax. Any help/advice would be appreciated.

EDIT: I just noticed my ~/.config/redshift.conf file had [redshift] on second line so I tried changing this to [redshift-gtk] to see if this makes a difference

$ sudo nano ~/.config/redshift.conf

; Global settings for redshift
[redshift]

change to ...

; Global settings for redshift
[redshift-gtk]

Now I can start Redshift from the menu where I couldn't before. I can also now start from the termininal as well by entering ...

hugh@DELL-INSP-DEVUAN:~$ redshift-gtk

The '~/.config/redshift.conf' file that I used is normally used for the newer 'redshift-gtk' v1.11-1 package and not the older 'gtk-redshift' v1.9.1-4 which was all that was available in Synaptic Package Manager. I think the name change adds a bit of confusion as well.

I will wait till this evening to see if the screen does change colour to indicate it is working as intended, and will update this post with results.

EDIT2: I checked Redshift again tonight but although it starts and icon is displayed in the app indicator panel along the top, the screen colour doesn't change as expected. So there must be something wrong with my ~/.config/redshift.conf file. I know it does work with the the newer 'redshift-gtk' v1.11-1 but looks like it won't work with older 'gtk-redshift' v1.9.1-4 which is the only version in the stable repositories.

I will need to investigate how to make changes in my sources.list to see if I can get the newer version installed. Is it possible to do this on the Devuan system?

Is it ok to just add following line?

deb http://ftp.debian.org/debian jessie-backports main

~~Or will there be any conflict with Devuan by doing this?~~
~~Is there a devuan equivalent to this line?~~

I had a look at the sources.list ....

hugh@DELL-INSP-DEVUAN:~$ cat /etc/apt/sources.list
## package repositories
deb [url]http://auto.mirror.devuan.org/merged[/url] jessie main contrib non-free
deb [url]http://auto.mirror.devuan.org/merged[/url] jessie-updates main contrib non-free
deb [url]http://auto.mirror.devuan.org/merged[/url] jessie-security main contrib non-free
#deb [url]http://auto.mirror.devuan.org/merged[/url] jessie-backports main contrib non-free

and I see there is a line for jessie-backports so I will try to enable that line and see if can install the newer 'redshift-gtk' v1.11-1

EDIT3: I enabled devuan jessie-backports and ran apt update but couldn't find the newer 'redshift-gtk' v1.11-1 package to install. I wonder is there any other way to install this package?

hughparker1 · Installation

golinux wrote:

@hughparker1 . . . I'm pretty sure you won't have to reinstall. Just an update/upgrade should get you to the stable release. That looks like Russian to me also. Locales must be confused . . .

Thanks for feedback. is there an easy way for me to check/modify Locales you mentioned?

hughparker1 · Installation

fsmithred wrote:

When you start synaptic from the menu, you should get a window that asks for a password. If you set up the system to use a root account, use the root password, and if you set it up for sudo, use your password. If you're not getting the pop-up window for authentication, then start it from a terminal like you did until that issue is solved.

I did set it up for sudo but I'm not getting the pop-up window for authentication, not sure why.

fsmithred wrote:

For the grub problem. You're right. Editing the config on devuan won't help if debian is in charge of boot. I can think of three ways to fix it.
1. Boot into Devuan and reinstall grub-efi-amd64
2. Boot into Devuan and run 'sudo grub-install' in a terminal. (no device name needed with uefi)
- optional for 2: run 'sudo grub-install --bootloader-id=some-name'
In either of those cases above, grub will create a bootloader and I expect it will put itself first in the list of bootloaders. Then you'll need to run update-grub to get debian in the boot menu. WARNING: I don't know this for a fact. UEFI implementations vary from manufacturer to manufacturer, so your system might not act like mine. COMMENT: I would try #2 with the bootloader-id first, and use an id name that is something other than debian, devuan or boot. Then you will know for sure that it's the one you just made.

I booted into Devuan and opened synaptic package manager and installed 'grub-efi-amd64'

I took your recommendation and went with 'bootloader-id' method first, so opened terminal and ran...

$ sudo grub-install --bootloader-id=devuan-hp

hugh@DELL-INSP-DEVUAN:~$ sudo grub-install --bootloader-id=devuan-hp
Installing for x86_64-efi platform.
Installation finished. No error reported.
hugh@DELL-INSP-DEVUAN:~$

$ sudo update-grub

hugh@DELL-INSP-DEVUAN:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Found Debian GNU/Linux (9.0) on /dev/sda11
Found Linux Lite 3.4 (16.04) on /dev/sda12
Found Linux Mint 18.1 Serena (18.1) on /dev/sda13
Found MX-16 Metamorphosis (16) on /dev/sda14
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
hugh@DELL-INSP-DEVUAN:~$

So far so good, then rebooted and checked UEFI boot settings and 'devuan-hp' was shown as a new entry first on list and is now in charge of grub menu as you predicted it would be.

Also when I pressed 'e' on the Devuan entry of the grub menu. I noticed the 'nomodeset' was already there in the Linux line, I added this the other day.

fsmithred wrote:

In my system, Debian's bootloader is in /boot/efi/EFI/debian and Devuan's is in /boot/efi/EFI/devuan. There is a /boot/efi/EFI/boot/, too.

My system has a /boot/efi/EFI/boot/ as well. I'm not sure what it does.

fsmithred wrote:

Read this if you haven't, re-read it if you have: http://www.rodsbooks.com/efi-bootloaders/index.html

I hadn't read this to be honest but I had a quick look and found the second link "How to install an EFI boot loader, in general terms" explained very clearly so thanks for the link. I now know a little bit more than I did yesterday.

Thanks for all your help I really appreciated it. I'm very happy with the final result.

Quick question, when Devuan stable is finally released, with the uefi install be a bit more automated than the current rc2 release? Following your instructions it was quite easy to install the boot loader post install. I thought the steps to do this during the install were a bit too difficult for a linux newbie like myself to follow.

PS. I noticed when I pressed 'e' to enter the setparams screen to look at Linux line, there were what looked like russian characters along the bottom of the screen. see screenshot... http://i.imgur.com/UyWTi5E.jpg
Similar characters were also visible along the bottom of the GRUB MENU... http://i.imgur.com/RrpgG4V.jpg
Have you seen this before? I chose UK during the install process so not sure why there is russian text showing.

hughparker1 · Installation

fsmithred wrote:

1. Graphics card or driver. Whichever one you want to blame. You could try the proprietary driver, but if it's working ok, there's no need.
2. Yes. Add nomodeset to /etc/default/grub and then run update-grub to generate a new menu. Then you don't have to edit at boot every time.
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"

thanks for your continued support. I managed to install Devuan successfully,

I chose the default option to not install the uefi boot loader as I wasn't confident enought to perform the steps described to do this manually.

I then logged into my other linux OS and ran update-grub to add Devuan to the grub menu.

Then reboot to show new grub menu and selected Devuan and pressed 'e' to edit the boot entry and add the word nomodeset to the Linux line.

Now I am logged into the Devuan Xfce desktop.

I now realise that when I modify /etc/default/grub to add nomodeset ....

GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"

... and try to update-grub I get error....

hugh@DELL-INSP-DEVUAN:~$ sudo update-grub
/usr/sbin/grub-mkconfig: 250: /usr/sbin/grub-mkconfig: cannot create /boot/grub/grub.cfg.new: Directory nonexistent
hugh@DELL-INSP-DEVUAN:~$

This must be because I chose not to install the uefi boot loader.

Is there an easy way to do this now after the event? (without damaging my other Debian or Windows installation) If I knew the correct syntax to use I can use the terminal. Thanks again for all your help so far it has been great.

EDIT: will there be any problems since I already have Debian installed previously, I was thinking of the path for boot loader \EFI\boot\bootx64.efi might be the same for both Debian and Devuan ?

EDIT2: I notice there is a package called grub-efi in Synaptic Package Manager and wondered if I just need to install that?

Also, is there any other required steps after that? bearing in mind that I already have Debian Stretch and Windows 10 on my laptop.

PS. I found that Synaptic Package Manager didn't start from the normal menu path, but I managed to run it via terminal using

$ sudo synaptic

not sure if this is a known problem or something I did wrong during the install.

The officially official Devuan Forum!

#1 Re: Installation » [SOLVED] Is "Devuan GNU/Linux 1.0 (jessie)" lastest stable version? » 2019-10-28 17:20:58

#2 Installation » [SOLVED] Is "Devuan GNU/Linux 1.0 (jessie)" lastest stable version? » 2019-10-27 21:35:33

#3 Re: Other Issues » What is best way to install latest version of Firefox? » 2017-06-09 16:26:14

#4 Re: Other Issues » What is best way to install latest version of Firefox? » 2017-06-09 09:58:48

#5 Re: Other Issues » What is best way to install latest version of Firefox? » 2017-06-08 10:54:20

#6 Re: Other Issues » What is best way to install latest version of Firefox? » 2017-06-02 15:59:26

#7 Re: Other Issues » What is best way to install latest version of Firefox? » 2017-06-01 23:32:13

#8 Other Issues » What is best way to install latest version of Firefox? » 2017-05-29 14:35:22

#9 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-19 22:56:57

#10 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-19 15:45:23

#11 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-19 08:50:53

#12 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-18 20:46:45

#13 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-18 14:42:08

#14 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-17 14:08:11

#15 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-16 23:07:31

#16 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-16 22:50:31

#17 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-16 17:27:45

#18 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-16 17:23:03

#19 Re: Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-16 16:40:04

#20 Re: Installation » [SOLVED] can't get splash screen UEFI install (only scrolling text) » 2017-05-15 11:13:33

#21 Re: Installation » [SOLVED] can't get splash screen UEFI install (only scrolling text) » 2017-05-15 09:43:36

#22 Installation » [SOLVED] Redshift fails to start - .service files missing? » 2017-05-15 09:14:12

#23 Re: Installation » [SOLVED] can't get splash screen UEFI install (only scrolling text) » 2017-05-14 19:04:38

#24 Re: Installation » [SOLVED] can't get splash screen UEFI install (only scrolling text) » 2017-05-14 18:46:07

#25 Re: Installation » [SOLVED] can't get splash screen UEFI install (only scrolling text) » 2017-05-13 11:34:04

Board footer