- This topic has 23 replies, 9 voices, and was last updated Oct 16-4:13 am by scruffyeagle.
-
Posts
-
scruffyeagle
During the past few days, Conky has seemed as if it’s crashing. I think this problem is the result of doing updates. (Several days ago, I did a massive updating session using Syaptic, and this problem never happened before that.) Conky used to start up and be displayed on the screen at initial boot time, but now it doesn’t get shown at all without direct intervention.
When I use the menu to start it (Menu click/ Desktop/ Conky on/off), the 1st click seemingly does nothing, then the 2nd click puts Conky up on the desktop. My suspicion, is that Conky is actually running, but not visible on the desktop – and the 1st click turns it off. Then, the 2nd click turns it on and it becomes visible – but, for less than a minute. After which, it vanishes again.
Here’s the output of “inxi -Fxxxrz”:
——————–System: Kernel: 4.9.0-264-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM v: 3.0.0 vt: 7 dm: SLiM v: 1.3.6 Distro: antiX-19.4_x64-full Grup Yorum 20 May 2021 base: Debian GNU/Linux 10 (buster) Machine: Type: Portable System: Dell product: Latitude E6400 v: N/A serial: <superuser required> Chassis: type: 8 serial: <superuser required> Mobo: Dell model: 0U692R serial: <superuser required> BIOS: Dell v: A34 date: 06/04/2013 Battery: ID-1: BAT0 charge: 76.4 Wh (102.0%) condition: 74.9/76.4 Wh (98.1%) volts: 12.2 min: 11.1 model: Panasonic DELL FU44196 type: Li-ion serial: <filter> status: full CPU: Info: dual core model: Intel Core2 Duo P8600 bits: 64 type: MCP smt: <unsupported> arch: Penryn Yorkfield rev: A cache: L1: 128 KiB L2: 3 MiB Speed (MHz): avg: 1200 high: 1600 min/max: 800/2401 boost: enabled cores: 1: 1600 2: 800 bogomips: 9576 Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen5 ports: active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300 Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: intel gpu: i915 display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31") s-diag: 398mm (15.69") Monitor-1: LVDS-1 mapped: LVDS1 model: Seiko Epson 0x5441 res: 1280x800 hz: 60 dpi: 107 size: 303x190mm (11.93x7.48") diag: 358mm (14.1") modes: 1280x800 OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403 Sound Server-1: ALSA v: k4.9.0-264-antix.1-amd64-smp running: yes Network: Device-1: Intel 82567LM Gigabit Network vendor: Dell driver: e1000e v: 3.2.6-k port: efe0 bus-ID: 00:19.0 chip-ID: 8086:10f5 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel WiFi Link 5100 driver: iwlwifi v: kernel bus-ID: 0c:00.0 chip-ID: 8086:4232 class-ID: 0280 IF: wlan0 state: down mac: <filter> RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 6ea0 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104 Drives: Local Storage: total: 1.14 TiB used: 288.89 GiB (24.8%) ID-1: /dev/sda vendor: Toshiba model: MK2561GSYN size: 232.89 GiB speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 0C scheme: MBR ID-2: /dev/sdb type: USB vendor: Western Digital model: WD My Passport 0748 size: 931.48 GiB type: N/A serial: <filter> rev: 1019 scheme: MBR Partition: ID-1: / size: 28.71 GiB used: 7.43 GiB (25.9%) fs: ext4 dev: /dev/sda5 Swap: ID-1: swap-1 type: partition size: 9.77 GiB used: 30.9 MiB (0.3%) priority: -1 dev: /dev/sda3 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A sodimm: SODIMM C Fan Speeds (RPM): cpu: 3013 Repos: Packages: apt: 2141 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/buster/ buster main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 1: deb http://deb.debian.org/debian/ buster-backports non-free contrib main Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.us.debian.org/debian/ buster main contrib non-free 2: deb http://security.debian.org/ buster/updates main contrib non-free No active apt repos in: /etc/apt/sources.list.d/onion.list No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 210 Uptime: 13h 13m wakeups: 11 Memory: 3.82 GiB used: 1.52 GiB (40.0%) Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: Bash v: 5.0.3 running-in: roxterm inxi: 3.3.19- This topic was modified 6 months, 2 weeks ago by anticapitalista. Reason: added solved
sybok
Hi, I have no idea, apart from asking the below questions:
1) If you suspect that ‘conky’ is running but not displayed, can you see it in list of processes (‘ps -ef | grep conky’ or ‘pgrep conky’)?
2) Are other desktops affected?
3) Could you try (to backup and) remove your IceWM configuration, replace it with “default” and see how that behaves.
Perhaps, this could be due to update of IceWM to the recently released 3.0.0, e.g. backwards incompatible change in configuration files.Also, the 3.0.0 is known to have issues, see e.g. https://www.antixforum.com/forums/topic/icewm-crash-opening-audacity/#post-90502
1) Here’s the result:
$ ps -ef | grep conky spirit 1325 30148 0 05:39 pts/0 00:00:00 grep conky spirit 29410 1 0 05:09 ? 00:00:07 conky$ pgrep conky 29410This means Conky is actually running without being visible on the desktop, right?
2) I haven’t tried using other desktops. I’d have to shut down all the programs I’m currently using, to try them, including Firefox…
3) I don’t see any alternative version of IceWM in the Synaptic list; just the v3.0.
I agree, that this is probably caused by the IceWM v3.0. The timing of the problem is too perfectly fit with recently updating programs. IMO, this is a NASTY BUG, and v3.0 should be removed from the antiX repo until it’s fixed.
I really would love to roll back to an earlier version of IceWM, but I have no idea how to do that.
- This reply was modified 6 months, 3 weeks ago by rokytnji.
sybok
1) Yes, conky is running.
‘ps -ef | grep <something>’ matches the ‘grep <something>’ command as well, that’s why I sometimes write ‘ps -ef | grep <something> -v grep’.The link in my previous post mentions that 3.0.1 should be in the repositories soon and that you can download the DEB file already.
sybok:
I’ve now tested the other IceWM desktops, and discovered that the only one with Conky malfunctioning is the space-IceWM desktop. The others (Rox-IceWM, min-IceWM, & plain IceWM) all seem to be functioning normally.
I have VeraCrypt being automatically started, along with the start of the space-IceWM desktop. The timing of Conky disappearing off the screen is coincident with the program box of VeraCrypt being displayed, but before the contents of that box are displayed; i.e., the box sits there blank white for several seconds, before getting populated with contents, and Conky disappears the moment that box gets put up.
BobC
If you think IceWM 3.0.0 is the cause try 3.0.1 from testing
anticapitalista
Seems like
VeraCrypt being automatically started, along with the start of the space-IceWM desktop
is the cause, not IceWM
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
sybok
https://github.com/veracrypt/VeraCrypt states that ‘VeraCrypt’ uses/requires ‘wxWidgets’.
anticapitalista
https://github.com/veracrypt/VeraCrypt states that ‘VeraCrypt’ uses/requires ‘wxWidgets’.
Ok, that points to a bug in IceWM3 and is fixed with IceWM 3.0.1. But, poster says it works ok with IceWM, Rox-IceWM and min-IceWM. Strange.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
caprea
Then the OP should definitely try the 3.0.1 version from test repo
https://www.antixforum.com/forums/topic/icewm-crash-opening-audacity/Edit:didn’t see anti’s post.
- This reply was modified 6 months, 3 weeks ago by caprea.
rokytnji
Done
$ apt-cache policy icewm icewm: Installed: 3.0.0-1.0antix1 Candidate: 3.0.0-1.0antix1 Version table: *** 3.0.0-1.0antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye bullseye/main amd64 Packages 100 /var/lib/dpkg/status 2.1.2-1 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages 1.9.0-1.0antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye bullseye/nosystemd amd64 PackagesSometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsanticapitalista
Even with latest 3.0.1 IceWM, zzzFM-IceWM causes the conky issue described.
IIRC this has only started to happen with the IceWM 3 series.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I have 2 laptops, a Dell Latitude E6400 running antiX v19.4, and a Dell Precision M6300 running antiX v21. The Conky problem is happening on the Latitude, so I chose to use the Precision today, That’s what I’m using right now. I found that it’s still using IceWM v2.9.9. To protect the system, I locked the version so it can’t upgrade. I’ll do any testing on the Latitude, which already has the problem. If & when I find a working solution, I’ll upgrade the Precision at that time. So, I’ll need to switch computers, in order to test the IceWM v3.0.1 version. BUT – I see that anticapitalista has posted that the problem still exists in the v3.0.1 – so, I don’t see any point in rushing to go test it.
I’ll need to make a note of it, to dl’ & install wxwidgets in the Latitude. I searched using the Precision, and found only “wx-common” which is described as “wxwidgets Cross-platform”, so my guess is that wx-common is what I need to dl’. I dl’d it into the Precision machine, but this also, will need to wait until I’ve switched back to the Latitude for discovering if it solves the problem.
Re. VeraCrypt: I’ve used it in every OS I’ve installed during the past few years, and never had any problem with it. Other than the difficulty of installing it, of course. But, it’s central, vital, & irreplaceable for my computing, for 2 reasons. One reason, is that there’s no fully functional substitute. By “fully functional”, I include the ability to display the very long passwords while I’m typing them in, so I can catch & correct typos. The second reason is that all my personal files are kept on encrypted external drives, NOT on any internal hard drive – so the encryption/decryption program is absolutely necessary. The external drives are absolutely necessary, so WHEN any given computer’s internal drive crashes, all my files won’t be lost with the machine. Encryption is necessary, because external drives are so easily stolen. This way, they can steal the device, but can’t get at my data.
One small correction: Conky disappeared coincident with the CONTENTS of the VeraCrypt box being displayed, not when the empty white VeraCrypt box gets displayed to screen.
I noticed one other small malfunction involving the display of the VeraCrypt program’s box: The placment of the box isn’t being retained from one startup to the next. I manually move it back to the center of the screen, but the next time I boot up, the VeraCrypt box gets pushed back to top left corner of the desktop.
I will see if I can recreate this on antiX 21 with zzz-icewm desktop.
I have a git account, and will put an issue in for it there.
PS: it didn’t happen with zzz-icewm on antiX 21 64 bit full sysvinit with icewm 3.0.1 so I’ll test from USB.
- This reply was modified 6 months, 3 weeks ago by BobC.
Ok, with freshly updated 19.4 the problem does occur only when running space-icewm (IceWM tested with 3.0.1, SpaceFM version 1.0.6) and with veracrypt installed from the buster version .deb veracrypt-1.25.9-Debian-10-amd64.deb, and it occurs when I click the desktop itself. I did not actually run veracrypt itself. Conky remains running but is not visible. The problem does not occur if I switch to any desktop other than space-icewm.
- You must be logged in to reply to this topic.
