Posts by Ron

Ron · Other Issues

Head_on_a_Stick wrote:

Check

While waiting for your reply, I went ahead and deleted the preferences folder I created with that file in it, and kept the file you recommend in preferences.d, then rebooted. Synaptic is still showing the old version of sudoku I use as the latest version. I also checked apt update and apt policy gnome-sudoku and that checked out good also. So I guess all is well??

Ron · Other Issues

Head_on_a_Stick wrote:

Looks good to me :-)

Great. Just one more thing. Now this is what I get in Synaptic. It shows the old version that I use as the latest version. Does this mean I can undo the first thing I did earlier? Or should I just leave well enough alone?

Ron · Other Issues

I added the file you said. I changed the version from what you wrote to this 1:3.22.2-1 because this is the version I'm using. I ran the commands and this is what happened:

ron@ron:~$ sudo apt update
[sudo] password for ron: 
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Get:2 http://deb.devuan.org/merged chimaera-security InRelease [21.5 kB]
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 21.5 kB in 3s (7,144 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

ron@ron:~$ apt policy gnome-sudoku
gnome-sudoku:
  Installed: 1:3.22.2-1
  Candidate: 1:3.22.2-1
  Version table:
     1:3.38.0-1 500
        500 http://deb.devuan.org/merged chimaera/main amd64 Packages
 *** 1:3.22.2-1 501
        100 /var/lib/dpkg/statu

Is everything now correct?

Ron · Other Issues

Head_on_a_Stick wrote:

There is no pinning for that package. If you run apt update followed by apt list --upgradable I think gnome-sudoku will still be marked for upgrade to the chimaera version.

I only update via Synaptic, and here's what happens in it. It doesn't get updated. But are you saying if I do an update via the terminal it will get updated?

This is what I got from your commands:

ron@ron:~$ sudo apt update
[sudo] password for ron: 
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Get:2 http://deb.devuan.org/merged chimaera-security InRelease [21.5 kB]
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://deb.devuan.org/merged chimaera-backports InRelease
Fetched 21.5 kB in 2s (9,148 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.

ron@ron:~$ apt list --upgradable
Listing... Done
gnome-sudoku/stable 1:3.38.0-1 amd64 [upgradable from: 1:3.22.2-1]
N: There is 1 additional version. Please use the '-a' switch to see it

Ron · Other Issues

Head_on_a_Stick wrote:

Either location should work.
Check the pinning with
apt policy
apt policy gnome-sudoku
I would consider running the program from a chroot because pinning makes me nervous but that would take significantly more disk space.

Here's the output:

$ apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 100 http://deb.devuan.org/merged chimaera-backports/non-free amd64 Packages
     release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=non-free,b=amd64
     origin deb.devuan.org
 100 http://deb.devuan.org/merged chimaera-backports/contrib amd64 Packages
     release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=contrib,b=amd64
     origin deb.devuan.org
 100 http://deb.devuan.org/merged chimaera-backports/main amd64 Packages
     release v=4.0,o=Devuan Backports,a=stable-backports,n=chimaera-backports,l=Devuan Backports,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged chimaera-updates/main amd64 Packages
     release v=4.0.0,o=Devuan,a=stable-updates,n=chimaera-updates,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged chimaera-security/main amd64 Packages
     release v=4.0,o=Devuan,a=stable-security,n=chimaera-security,l=Devuan-Security,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged chimaera/contrib amd64 Packages
     release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=contrib,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged chimaera/non-free amd64 Packages
     release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=non-free,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged chimaera/main amd64 Packages
     release v=4.0,o=Devuan,a=stable,n=chimaera,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
Pinned packages:
     refractainstaller-base -> 9.5.6 with priority 1001
     refractainstaller-gui -> 9.5.6 with priority 1001

and

$ apt policy gnome-sudoku
gnome-sudoku:
  Installed: 1:3.22.2-1
  Candidate: 1:3.38.0-1
  Version table:
     1:3.38.0-1 500
        500 http://deb.devuan.org/merged chimaera/main amd64 Packages
 *** 1:3.22.2-1 100
        100 /var/lib/dpkg/status

Why does pinning make you nervous? My concern is just to be sure that nothing else gets blocked from updating.

Ron · Other Issues

aitor wrote:

I forgot the extension. So, you don't need to create any additional folder, because /etc/apt/preferences.d is the right place to edit the file.

Well everything seems to be working right. I had some updates today, and sudoku was marked as not to be upgraded. Everything else updated okay. Should I just leave well enough alone, or put that file in preferences.d and delete the preferences folder I created?

Ron · Other Issues

It appears to have worked. Thanks, to both of you.

BTW, there was no "preferences" folder in /etc/apt, so I created one. Is that normal? There is a "preferences.d" folder.

Ron · Other Issues

I update via Synaptic, never from the terminal, so I don't see how this applies to me? I want Synaptic to not update sudoku, which is what I thought Lock Version was supposed to do. In Synaptic is there a way to pick and choose from among the list of updates that are presented (when there are updates)?

Ron · Other Issues

I like an older version of gnome-sudoku than the one in chimaera's repo, so I had that particular older one installed via a .deb file, then in Synaptic Package Manager I had it marked as "Lock Version" under Package in the menu. I know it got marked because the icon changed to "Installed (locked to current version)" in the icon legend. However, the last time I did an upgrade gnome-sudoku got updated along with all the rest that had updates [ironically it still has the "Installed (locked to current version)" icon]. Did I miss a step, or am I misunderstanding what Lock Version does? Once I go back to the older version is there a way I can prevent gnome-sudoku from updating again?

Ron · Other Issues

Marked as solved. No doubt it was bad RAM.

Ron · Other Issues

andyprough wrote:

Any luck Ron? I'm thinking with double the memory you'll be getting a better experience all around.

So far, so good.

Ron · Other Issues

I only had one 4 gig stick. Just replaced it with one brand new 8 gig stick. Hopefully my browser crashes are now a thing of the past.

Ron · Other Issues

Head_on_a_Stick wrote:

Ouch. Perhaps I was wrong about that broken POS software...

So the RAM is bad and needs replacing, I presume. I'll see if I can get it done tomorrow. One question, how come the bad RAM is only affecting the browsers and nothing else?

Ron · Other Issues

So I installed memtest86+ and ran it. How long is it supposed to run? I cut it off after 2 hours and 46 minutes. I took three pics as it ran, one at 40 minutes, the second at 65 minutes, and the last at 2 hours and 46 minutes. Here they are. It doesn't look good, but I don't know how to decipher what it means:

Ron · Other Issues

Okay, now we're getting somewhere. There are a lot of failures. Are they meaningless, or are they a problem?

ron@ron:~$ sudo memtester 1800 5
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 1800MB (1887436800 bytes)
got  1800MB (1887436800 bytes), trying mlock ...locked.
Loop 1/5:
  Stuck Address       : testing   2FAILURE: possible bad address line at offset 0x3601ff60.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x81e016f420806686 != 0x81e016f420846686 at offset 0x00ac6f50.
  Compare SUB         :   Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   8FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x14cdcb28.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x2527eb28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x351a9b38.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x168f27e0.
  Bit Spread          : testing 111FAILURE: 0xfffffffffffaffff != 0xfffffffffffeffff at offset 0x027e6b28.
  Bit Flip            : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 2/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x67b5fb38.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x210a71e31169926a != 0x210a71e3116d926a at offset 0x024f8b28.
FAILURE: 0x210a71e31169926a != 0x210a71e3116d926a at offset 0x0e7d4b28.
  Compare SUB         :   Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x027fab28.
  Block Sequential    : testing  16FAILURE: 0x1010101010101010 != 0x1010101010141010 at offset 0x00ac6b28.
  Checkerboard        : testing  17FAILURE: 0xaaaaaaaaaaaaaaaa != 0xaaaaaaaaaaaeaaaa at offset 0x020b6f50.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x0eabcf50.
FAILURE: 0x00000005 != 0x00040005 at offset 0x2f660f50.
  Bit Flip            : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x12856b28.
  Walking Ones        : testing 109FAILURE: 0xfffffffffffbffff != 0xffffffffffffffff at offset 0x14cdcb28.
  Walking Zeroes      : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0eabcb28.
FAILURE: 0x00000001 != 0x00040001 at offset 0x2f642f50.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 3/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x3abe5b38.
Skipping to next test...
  Random Value        : ok
FAILURE: 0x849452d58100b80b != 0x849452d58104b80b at offset 0x027e6b28.
  Compare XOR         : FAILURE: 0xe030724480962f6d != 0xe030724480922f6d at offset 0x323bfb38.
  Compare SUB         :   Compare MUL         : ok
FAILURE: 0x00000001 != 0x00040001 at offset 0x027e6b28.
  Compare DIV         :   Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : testing   1FAILURE: 0x00000000 != 0x00040000 at offset 0x2f660f50.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x073d6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x2f67eb28.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x12856820.
  Bit Spread          : testing  19FAILURE: 0x00280000 != 0x002c0000 at offset 0x2d2f8f50.
  Bit Flip            : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0e7d4b28.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00000001 != 0x00040001 at offset 0x0e814f50.
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 4/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x32509f60.
Skipping to next test...
  Random Value        : ok
  Compare XOR         : ok
FAILURE: 0x58011009044c94b4 != 0x58011009044894b4 at offset 0x351a9b38.
  Compare SUB         : FAILURE: 0xf81ce9a8d028b00f != 0xf81ce9a8d02cb00f at offset 0x12856f50.
FAILURE: 0xf81ce9a8d028b00f != 0xf81ce9a8d02cb00f at offset 0x2f67eb28.
  Compare MUL         :   Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
FAILURE: 0xcefd860afce107b3 != 0xcefd860afce507b3 at offset 0x0d134b28.
FAILURE: 0xcefd860afdd85838 != 0xcefd860afddc5838 at offset 0x14cdcf50.
  Sequential Increment:   Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x0d0f6b28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x351a9b38.
  Block Sequential    : testing   8FAILURE: 0x808080808080808 != 0x8080808080c0808 at offset 0x0e814b28.
  Checkerboard        : testing   4FAILURE: 0x5555555555555555 != 0x5555555555515555 at offset 0x027e6820.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x14cdcf50.
  Bit Flip            : testing   7FAILURE: 0x00040001 != 0x00000001 at offset 0x32661f60.
  Walking Ones        : ok         
  Walking Zeroes      : testing   0FAILURE: 0x00040001 != 0x00000001 at offset 0x351a9b38.
  8-bit Writes        : ok
  16-bit Writes       : -FAILURE: 0x768fbe9efbf3a928 != 0x768fbe9efbf7a928 at offset 0x0eabcf50.

Loop 5/5:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x3abe5b38.
Skipping to next test...
  Random Value        : ok
FAILURE: 0xaa4c2f2dd8405405 != 0xaa4c2f2dd8445405 at offset 0x23486f50.
  Compare XOR         :   Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
FAILURE: 0xdaa76f56fa99a191 != 0xdaa76f56fa9da191 at offset 0x14cdcb28.
  Sequential Increment:   Solid Bits          : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x12856b28.
  Block Sequential    : testing   0FAILURE: 0x00000000 != 0x00040000 at offset 0x00ac6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x027e6b28.
FAILURE: 0x00000000 != 0x00040000 at offset 0x14cdcb28.
FAILURE: 0x00040000 != 0x00000000 at offset 0x352a9b38.
  Checkerboard        : testing   4FAILURE: 0xaaaaaaaaaaaaaaaa != 0xaaaaaaaaaaaeaaaa at offset 0x027e6b28.
  Bit Spread          : testing   0FAILURE: 0x00000005 != 0x00040005 at offset 0x0eabcf50.
FAILURE: 0x00000005 != 0x00040005 at offset 0x1528cf50.
  Bit Flip            : testing   2FAILURE: 0x00000001 != 0x00040001 at offset 0x12856b28.
  Walking Ones        : ok         
  Walking Zeroes      : ok         
  8-bit Writes        : ok
  16-bit Writes       : ok

Done.
ron@ron:~$ echo $?
6

Ron · Other Issues

Is the below correct? From what I've read it should return "0" but I got a "1".

ron@ron:~$ sudo memtester free 5
[sudo] password for ron: 
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000

Usage: memtester [-p physaddrbase [-d device]] <mem>[B|K|M|G] [loops]
ron@ron:~$ echo $?
1

Ron · Other Issues

andyprough wrote:

If Ron is using the .deb packages, he may want to try switching to the tarball from the website.

I was using the tarball, and a few days ago switched to Steve's .deb. It doesn't appear to make a difference. I'm beginning to wonder if I have bad RAM, but I'm not knowledgeable of myself to know whether that's the case or not.

andyprough wrote:

You'll be relieved to hear that "that fat **** Tobin" is gone from the forum by the way. His millions of adoring fans are in mourning.

Actually, that's not true. While his last post was Dec 22, he was in fact active on the forum just today.

And at risk of repeating myself, here's the results of a memory test I did, and of which I don't know how to decipher:

ron@ron:~$ sudo memtester 3700 5
[sudo] password for ron:
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3700MB (3879731200 bytes)
got  3700MB (3879731200 bytes), trying mlock ...Killed
ron@ron:~$ echo $?
137

Ron · Other Issues

Head_on_a_Stick wrote:

Can you share the full error?

That's all the terminal said. Is there a log somewhere that has documented this?

Head_on_a_Stick wrote:

You can generate a stack trace for them by following https://wiki.debian.org/HowToGetABacktrace but I don't know about the relevant debug symbols. Ask on their forums.

I see this link mentions gdb. In my searches about this problem I came across this app being recommended. Honestly though I'm getting tired of this issue.

I should add I also did a memory test (during which I had Pale Moon opened and during the test it crashed). Here's the results, and I have no idea what 137 means:

ron@ron:~$ sudo memtester 3700 5
[sudo] password for ron:
memtester version 4.5.0 (64-bit)
Copyright (C) 2001-2020 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 3700MB (3879731200 bytes)
got  3700MB (3879731200 bytes), trying mlock ...Killed
ron@ron:~$ echo $?
137

Ron · Other Issues

I was able to get a crash after opening Pale Moon in via the terminal. After the crash the terminal said Segmentation Fault. Question: would adding more RAM fix this, or is the problem deeper than merely adding RAM? I have 4gigs RAM.

Ron · Other Issues

golinux wrote:

That needed to be done long before Devuan existed. That doesn't mean that it wasn't intentional but not for reasons you might be imagining . . .

I don't know . . . I have a very vivid (and crazy) imagination at times.

Ron · Other Issues

Question: since this has worked on older versions of Devuan, and since this file did not exist on my current system, does this mean that Devuan or Debian has deliberately made the choice to have this disabled?

Ron · Other Issues

Thanks HoaS (again). It works now on an unfrozen system. Waiting for another freeze to see if it works then (I'm assuming it will).

Ron · Other Issues

Along the lines of my other recent post about browser crashes, I had a computer freeze-up while browsing the web, and for the first time Alt + SysRq then r e i s u b did not reboot the system. It stayed frozen; had to do a hard shut down. This has now happened more than once. Any idea what why the reboot didn't work?

Ron · Other Issues

After playing a handful of youtube videos on Chromium it hasn't crashed at all yet, unlike Vivaldi where I'd get crashes on just about every other video (and sometimes multiple crashes on the same video). FTR, Chromium did crash on me once, but there were no videos playing at the time.

So, I'm guessing there really isn't anything that can be done about this? I'd really prefer using Vivaldi over Chromium for youtube watching.

Ron · Other Issues

golinux wrote:

I thought uBlock Origin did that automatically. Maybe I'm missing something . . .

I think it does. 🤔

The officially official Devuan Forum!

#151 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-26 16:24:13

#152 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-26 15:45:40

#153 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-26 15:34:34

#154 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-26 15:19:26

#155 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-26 14:14:44

#156 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-25 23:43:42

#157 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-24 23:26:45

#158 Re: Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-24 16:57:15

#159 Other Issues » [SOLVED] Getting "Lock Version" in Synaptic to work » 2022-02-24 04:38:35

#160 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-18 03:08:17

#161 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-15 23:38:41

#162 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-14 20:36:35

#163 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-13 21:49:26

#164 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-13 19:11:50

#165 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 23:32:13

#166 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 22:02:18

#167 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 20:06:58

#168 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 17:45:54

#169 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-12 14:29:38

#170 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 18:20:34

#171 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 17:27:37

#172 Re: Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 13:55:24

#173 Other Issues » [SOLVED-PENDING] First time r-e-i-s-u-b didn't work » 2022-02-09 02:56:19

#174 Re: Other Issues » [SOLVED-BAD RAM] Browser crashes on Devuan 3 and 4,... » 2022-02-07 17:41:27

#175 Re: Other Issues » Weird option in Chromium settings » 2022-02-07 17:35:01

Board footer