MX-problem or Distrowatch-problem?

Message
Author
User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#61 Post by rijnsma11111 »

Eadwine Rose wrote: Sat Sep 28, 2024 8:23 am Members cannot delete posts.

Solved icon is that V-button on the top right of each post. Click the one in the post that holds the solution.
New tiny problem: searching like hell, but I don't see V-button on the top right of each post. I'm sorry.

User avatar
CharlesV
Global Moderator
Posts: 7059
Joined: Sun Jul 07, 2019 5:11 pm

Re: MX-problem or Distrowatch-problem?

#62 Post by CharlesV »

Before you reply to a post, and your a logged in user, you should a check mark on the top right of the post, right by the Author's name.


Image
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#63 Post by rijnsma11111 »

CharlesV wrote: Sat Sep 28, 2024 1:34 pm Before you reply to a post, and your a logged in user, you should a check mark on the top right of the post, right by the Author's name.


Image
I am logged in.
I only have three icons edit, warning (report) and quote.
Maybe because I renewed my account because of problems after change of email and password?
My number of posts is now 5 .
Last edited by rijnsma11111 on Sat Sep 28, 2024 2:01 pm, edited 1 time in total.

User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#64 Post by rijnsma11111 »

Code: Select all

Snapshot created on: 20240918_1201
System:
  Kernel: 6.1.0-25-amd64 [6.1.106-3] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-amd64 root=UUID=<filter> ro no
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_x64 Libretto October 20  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: H81M-K v: Rev X.0x serial: <superuser required> BIOS: American Megatrends
    v: 1003 date: 10/24/2014
CPU:
  Info: model: Intel Celeron G1840 bits: 64 type: MCP arch: Haswell level: v2 built: 2013-15
    process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1198 high: 1210 min/max: 800/2800 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1210 2: 1187 bogomips: 11174
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: VGA-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0402 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: VGA-1 model: HP LE2002x serial: <filter> built: 2012 res: 1600x900 hz: 60 dpi: 92
    gamma: 1.2 size: 443x249mm (17.44x9.8") diag: 508mm (20") ratio: 16:9 modes: max: 1600x900
    min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (HSW GT1) direct-render: Yes
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK 8
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  API: ALSA v: k6.1.0-25-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off tools: pw-cat,pw-cli,wpctl
  Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK H81M-C
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.96 TiB used: 15.12 GiB (0.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10EZEX-00BN5A0 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A01 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: HD161HJ size: 149.05 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0-19 scheme: MBR
Partition:
  ID-1: / raw-size: 97.66 GiB size: 95.56 GiB (97.86%) used: 15.12 GiB (15.8%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2392 libs: 1219 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 216 Uptime: 6h 15m wakeups: 3 Memory: 7.63 GiB used: 3.45 GiB (45.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

User avatar
CharlesV
Global Moderator
Posts: 7059
Joined: Sun Jul 07, 2019 5:11 pm

Re: MX-problem or Distrowatch-problem?

#65 Post by CharlesV »

Hmm... checking now...
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
CharlesV
Global Moderator
Posts: 7059
Joined: Sun Jul 07, 2019 5:11 pm

Re: MX-problem or Distrowatch-problem?

#66 Post by CharlesV »

It looks like there is a restriction of 5 posts before those other icons show up. Can you see the solved post now that you have 6 posts?
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#67 Post by rijnsma11111 »

Produce even one more post.

User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#68 Post by rijnsma11111 »

No. I don't see the 'v'
Three icons.

User avatar
richb
Administrator
Posts: 10842
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX-problem or Distrowatch-problem?

#69 Post by richb »

Looks like you typed V it is the check mark.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
rijnsma11111
Posts: 54
Joined: Sat Sep 14, 2024 4:36 pm

Re: MX-problem or Distrowatch-problem?

#70 Post by rijnsma11111 »

richb wrote: Sat Sep 28, 2024 2:31 pm Looks like you typed V it is the check mark.
Before I typed something it also did not work. That is why I typed.
Shall I try to delete? Oops. Not possible. 9_9

Post Reply

Return to “General”