Welcome!
Forum users
  • Please read this before asking for help, and don't forget to add Quick System Info to help requests!
  • Please follow the Forum Rules

Current releases
--MX-19.4 release info here
--Migration information to MX-19.4 here
--antiX-19.4 (Grup Yorum) release info here

Important information
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- New Forum Features, Marking Solved and Referencing a User: here

Problem detected while install screenfetch

Post Reply
Message
Author
WynnSmith
Posts: 13
Joined: Thu Dec 31, 2020 8:54 pm

Problem detected while install screenfetch

#1 Post by WynnSmith »

I'm new to Linux. I've selected MS Linux to revive my limited resource Acer Netbook. I installed the 32 bit final, downloaded from OSU. I'm familiar with Windows tools such as MSInfo for looking up a variety of hardware and software tech info. I found a suggestion for 'screenfetch' to collect bios info and tried to install it.

In MX Package Installer, on the 'Stable Repo' tab, I attempted to install screenfetch. After going through its paces, it returned a dialog box:
Error
Problem detected while installing, please inspect the console output.

The console tells me this:
Selecting previously unselected package screenfetch.
dpkg: unrecoverable fatal error, aborting:
loading files list file for package 'linux-headers-4.19.0-12-common': cannot open /var/lib/dpkg/info/
(Reading database ... E: Problem renaming the file /var/lib/apt/extended_states.rkT8B5 to /var/lib/apt/
extended_states - rename (5: Input/output error)
E: Could not open file /var/lib/apt/extended_states - open 5: Input/output error)
E: Failed open StateFile /var/lib/ap/extended_states
E: Sub-process /usr/bin/dpkg returned an error code (2)

I'm comfortable with the command line in MS land, although the Linux version will take some learning. Your suggestions are warmly appreciated.

User avatar
junoluna
Posts: 515
Joined: Sun Sep 29, 2019 11:53 pm

Re: Problem detected while install screenfetch

#2 Post by junoluna »

can you post your quick system info first as per forum rules for troubleshooting?

search quick system info in the menu then copy it between the code tags above the reply area ..... then someone will no doubt be along to help you .... assuming not hungover

User avatar
i_ri
Posts: 607
Joined: Tue Jun 30, 2015 12:26 am

Re: Problem detected while install screenfetch

#3 Post by i_ri »

meanwhile ,, screenfetch aside momentarily,
"System Profiler and Benchmark"

is an entry for launch, in the menu [System]
(alternate to in terminal command <hardinfo>)

<neofetch> is available similar to <screenfetch>
in terminal type: neofetch
or in terminal type: inxi --help
or in terminal type: man neofetch
bios info.? hardware info.
welcome to mx

do the "QSI" " Quick System Info" launch from menu [ MX Tools]

WynnSmith
Posts: 13
Joined: Thu Dec 31, 2020 8:54 pm

Re: Problem detected while install screenfetch

#4 Post by WynnSmith »

Thank you i_ri. That was extremely helpful to me, being new to linux land. BTW, one obvious challenge, becoming new to Linux on a netbook, is that my small screen real estate, lack of basic knowledge of the tools, and lacking any basic customization that one would normally do when familiar with a system, makes it virtually impossible, for the next few weeks or so, that I could use that netbook to collect information and then transmit it to this forum from that notebook. Therefore, I can see from the replies so far, that a lowly person such as I, must be willing and able to overcome a huge learning curve, before posting error messages to this forum. I apologize to those whom I have annoyed.

So thank you. Thank you for the suggestion of pre-installed tools. I wasn't aware they existed and so that will help me up the learning curve.

User avatar
i_ri
Posts: 607
Joined: Tue Jun 30, 2015 12:26 am

Re: Problem detected while install screenfetch

#5 Post by i_ri »

Hello WynnSmith and junoluna
No big curve. short straight path clicking.

You may have uncovered something that needs investigation with screenfetch, i don't know.
meanwhile, check health if screenfetch errors left a scar,
launch from menu "Synaptic Package Manager" [System, Settings]
(root password)
click the Reload button (in the Synaptic toolbar below the menubar)

does it complete? messages? health? quiet?

WynnSmith
Posts: 13
Joined: Thu Dec 31, 2020 8:54 pm

Re: Problem detected while install screenfetch

#6 Post by WynnSmith »

At this stage, my system seems truly broken. I'm going to reinstall from the OSU 386 Final that I've put on a thumb drive with Rufus. I'm installing to an Acer Aspire One D150-1165 with 2GB RAM and an early Atom N270 CPU. The BIOS is v1.13 dated 1/19/2010. I'm using a 32GB thumb drive for my swap drive.

I had used the MX Linux package installer to install a number of apps. However, I didn't check any log files for errors. I suspect my problem could be from choosing a bad app or perhaps choosing too many to install all at once. It was after that, before trying in of the newly installed apps, I attempted to use the 'Stable Repo' tab to install screenfetch. After my next re-install, I'll use the tools you suggested to gather system info.

One of my first goals will be to map a drive to my Windows Server Work share and pick out a text editor that follows traditional CUA interface rules.

thanks again for your help.

User avatar
JayM
Qualified MX Guide
Posts: 10076
Joined: Tue Jan 08, 2019 4:47 am

Re: Problem detected while install screenfetch

#7 Post by JayM »

You may have a bad repo mirror. There have been many since covid-19 quarantines started for some reason. I would need to see your Quick System Info to find out though. See the instructions in the link in my signature.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

WynnSmith
Posts: 13
Joined: Thu Dec 31, 2020 8:54 pm

Re: Problem detected while install screenfetch

#8 Post by WynnSmith »

Here is my QSI after wiping the drives, reinstalling MX Linux, and installing updates. I'm not going to worry about the problem from my original post unless it crops up again. Now I have a new problem and wonder if I should start a new thread?
This problem also appeared in my original install. The screen goes black after returning from the screensaver. I've turned off all the sleep and suspend options, so I believe it's the screensaver that is triggering the problem. The screen goes black with a fully functional mouse pointer... except there's nothing to click on.

In researching on the web, I found this suggestion. I don't know what it is, but it sounded promising after reading through many different web pages. I understand I simply need to type this into a commandline and then reboot. Your advice is appreciated.

sudo echo "options i915 enable_psr=0" >> /etc/modprobe.d/i915.conf

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-12-686-pae i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-686-pae 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.3_386 patito feo November 11  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Other-vm? System: Acer product: Aspire one v: V1.13 serial: <filter> 
           Mobo: Acer model: Aspire one v: V1.13 serial: <filter> BIOS: Acer v: 1.13 
           date: 01/19/2010 
Battery:   ID-1: BAT0 charge: 67.9 Wh condition: 67.9/73.3 Wh (93%) volts: 12.2/11.1 
           model: Simplo UM08A71 type: Li-ion serial: N/A status: Full 
CPU:       Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell 
           family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB 
           flags: nx pae sse sse2 sse3 ssse3 bogomips: 6383 
           Speed: 815 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 815 2: 893 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 status: Not affected 
           Type: spectre_v2 status: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics 
           vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:27ae 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 
           direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 
           Sound Server: ALSA v: k4.19.0-12-686-pae 
Network:   Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Foxconn driver: wl 
           v: kernel port: 5000 bus ID: 01:00.0 chip ID: 14e4:4315 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet 
           vendor: Acer Incorporated ALI driver: ATL1E v: N/A port: 1000 bus ID: 03:00.0 
           chip ID: 1969:1026 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 178.46 GiB used: 5.98 GiB (3.3%) 
           ID-1: /dev/sda vendor: Toshiba model: MK1652GSX size: 149.05 GiB block size: 
           physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0J scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Transcend model: JetFlash Transcend 32GB 
           size: 29.41 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 
           scheme: MBR 
Partition: ID-1: / raw size: 34.18 GiB size: 33.39 GiB (97.70%) used: 5.91 GiB (17.7%) fs: ext4 
           dev: /dev/sda1 
           ID-2: /home raw size: 30.76 GiB size: 30.15 GiB (98.02%) used: 67.1 MiB (0.2%) 
           fs: ext4 dev: /dev/sda2 
           ID-3: swap-1 size: 29.41 GiB used: 520 KiB (0.0%) fs: swap 
           swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sdb1 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 182 Uptime: 19m Memory: 1.96 GiB used: 429.2 MiB (21.4%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36
           
Last edited by WynnSmith on Sun Jan 03, 2021 11:43 am, edited 1 time in total.

User avatar
junoluna
Posts: 515
Joined: Sun Sep 29, 2019 11:53 pm

Re: Problem detected while install screenfetch

#9 Post by junoluna »

think you should do a new thread


btw .. make sure your QSI is properly formatted .... easier for the troubleshooters to read...

should look like this

i don't think you need to put QSI between code tags ... should be automatically formatted when you paste it in

Code: Select all

ystem: Host: <filter> Kernel: 4.19.0-12-686-pae i686 bits: 32 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-686-pae
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19.3_386 patito feo November 11 2020 base: Debian GNU/Linux 10 (buster)
Machine: Type: Other-vm? System: Acer product: Aspire one v: V1.13 serial: <filter>
Mobo: Acer model: Aspire one v: V1.13 serial: <filter> BIOS: Acer v: 1.13
date: 01/19/2010
Battery: ID-1: BAT0 charge: 67.9 Wh condition: 67.9/73.3 Wh (93%) volts: 12.2/11.1
model: Simplo UM08A71 type: Li-ion serial: N/A status: Full
CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell
family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB
flags: nx pae sse sse2 sse3 ssse3 bogomips: 6383
Speed: 815 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 815 2: 893
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 status: Not affected
Type: spectre_v2 status: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics
vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:27ae
Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1024x600~60Hz
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-12-686-pae
Network: Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Foxconn driver: wl
v: kernel port: 5000 bus ID: 01:00.0 chip ID: 14e4:4315
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
vendor: Acer Incorporated ALI driver: ATL1E v: N/A port: 1000 bus ID: 03:00.0
chip ID: 1969:1026
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 178.46 GiB used: 5.98 GiB (3.3%)
ID-1: /dev/sda vendor: Toshiba model: MK1652GSX size: 149.05 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0J scheme: MBR
ID-2: /dev/sdb type: USB vendor: Transcend model: JetFlash Transcend 32GB
size: 29.41 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100
scheme: MBR
Partition: ID-1: / raw size: 34.18 GiB size: 33.39 GiB (97.70%) used: 5.91 GiB (17.7%) fs: ext4
dev: /dev/sda1
ID-2: /home raw size: 30.76 GiB size: 30.15 GiB (98.02%) used: 67.1 MiB (0.2%)
fs: ext4 dev: /dev/sda2
ID-3: swap-1 size: 29.41 GiB used: 520 KiB (0.0%) fs: swap
swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sdb1
Sensors: System Temperatures: cpu: 50.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 182 Uptime: 19m Memory: 1.96 GiB used: 429.2 MiB (21.4%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36

User avatar
JayM
Qualified MX Guide
Posts: 10076
Joined: Tue Jan 08, 2019 4:47 am

Re: Problem detected while install screenfetch

#10 Post by JayM »

@WynnSmith: you should read the [url=viewtopic.php?p=255061#p255061]forum rules[/url, as should everyone from time to time as they're subject to change now and then.
Do not reply to others' existing topics to ask for help nor post multiple issues in one topic. Start a new topic for each issue. This helps to avoid confusion and chaos.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

Post Reply

Return to “MX Repositories”