home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.mint      Looks pretty on the outside, thats it!      30,566 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 29,011 of 30,566   
   Paul to All   
   Re: dpkg errors following a clean instal   
   28 Aug 25 03:02:01   
   
   From: nospam@needed.invalid   
      
   On Thu, 8/28/2025 12:25 AM, Lawrence D’Oliveiro wrote:   
   > On Wed, 27 Aug 2025 21:12:21 +0100, pinnerite wrote:   
   >   
   >> dpkg: unrecoverable fatal error, aborting:   
   >>  files list file for package 'gnome-accessibility-themes' is missing   
   >>  final newline   
   >>   
   >> $ find . -name gnome-accessibility-themes just returns to the prompt, so   
   >> it is not a file.   
   >   
   > It’s a package. There might be something in /var/lib/dpkg/info/.   
   >   
      
   At some time in the past, the symptoms suggest an installation   
   was done from bad optical media. I can find one bug report, where   
   the people don't reach that conclusion, but apparently during the   
   original install, there was an error message like that, the operator   
   clicked "continue", the system booted OK (operator not curious),   
   the operator was "happy" and no longer interested in the message.   
      
   And then later, the damage gets noticed.   
      
   I checked the four files in this case, in a VM, and all terminate normally.   
   I copied them over and checked them in HxD.   
      
   This is one of the reasons that Ubuntu media includes hashing as part   
   of the startup. So that if major pieces are corrupted, the operator   
   is alerted there is something wrong with the media. It's an expensive   
   way to detect media trouble, but at a time like this, it sounds like   
   a good idea.   
      
   A person could "rip" their old optical media to an .iso, then   
   find the originally released hash for the file, and compare to the   
   current hash. As a means of detecting a media degradation over time.   
   Use your favorite tool, like a K3B or so. You can do a TORAM=yes boot   
   on one piece of media, install K3B, and rip another piece of media.   
      
      # Each folder has hash values you can use to check   
      
      https://mirror.csclub.uwaterloo.ca/linuxmint/stable/   
      
   As for the file corruption, the error message doesn't really tell   
   you what the syndrome actually is. There could be an entire 2048 byte   
   sector missing, for example.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca