You are not logged in.
Before the March 12th's update, conky worked very well. And when I edited the config file with conky running, it refreshed to update its appereance very soon.
However, after I updated conky, when saving ~/.conkyrc, conky just disappeared. And I had to restart X then conky would show again.
I use openbox, and here's my ~./conkyrc (partial):
conky.config = {
alignment = 'top_left',
background = true,
border_width = 1,
cpu_avg_samples = 2,
default_color = 'white',
default_outline_color = 'white',
default_shade_color = 'grey',
draw_borders = false,
draw_graph_borders = true,
draw_outline = false,
draw_shades = false,
use_xft = true,
font = 'DejaVu Sans Mono:size=9',
gap_x = 5,
gap_y = 60,
minimum_height = 5,
minimum_width = 5,
net_avg_samples = 2,
no_buffers = true,
out_to_console = false,
out_to_stderr = false,
extra_newline = false,
own_window = true,
own_window_class = 'Conky',
own_window_type = 'override',
stippled_borders = 0,
update_interval = 1.0,
uppercase = false,
use_spacer = 'none',
show_graph_scale = false,
show_graph_range = false,
own_window_transparent = true,
double_buffer = true
}
Last edited by shake (2018-03-16 11:36:25)
Offline
Before the March 12th's update
This is meaningless. We have no way fo knowing what was in that update; so don't know what has changed. Now do we know anything about your graphics stack.
Moving to NC...
Offline
Sorry, I don't know why it's crashing... I know in the past that when I change my configuration files, sometimes conky updates and sometimes it crashes. But I change my configuration file so infrequently that I don't care.
Is changing the conky configuration files something you do on a regular basis?
FYI, when conky crashes, you don't need to log out and log in... Just run "conky &" in a terminal window. It does the same thing.
Offline
Sorry, I don't know why it's crashing... I know in the past that when I change my configuration files, sometimes conky updates and sometimes it crashes. But I change my configuration file so infrequently that I don't care.
Is changing the conky configuration files something you do on a regular basis?
FYI, when conky crashes, you don't need to log out and log in... Just run "conky &" in a terminal window. It does the same thing.
:)Thank you! To be honest, I'm a new conky user. So, changing conky config recently is inevitable cause I want it looks good.
By the way, I tried to run "conky &" after conky crashed today. And the terminal put:
shakehost% conky &
[1] 933
shakehost% conky: desktop window (4005ed) is subwindow of root window (4c7)
conky: window type - override
conky: drawing to created window (0x1000001)
conky: drawing to double buffer
conky: forked to background, pid is 934
[1] + done conky
shakehost%
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 2 (X_ChangeWindowAttributes)
Serial number of failed request: 169
Current serial number in output stream: 170
Conky didn't show. Something wrong but I don't know...
Offline
Hmmm, that's strange...
How do you automatically start conky in Openbox?
What is the output of "uname -a"?
Offline
This may sound silly - but it's the only explanation I can imagine that fits the symptoms: when conky is started with X starting up (where/how is it started exactly) is it perhaps given a specific configuration file other than the default?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Then editing the default config should™ not have any impact at all.
1. does only the conky window or also the conky process disappear
2. got a coredump? (man coredumpctl)
3. Your actual complete conkyrc - and does it matter *what* you edit or does merely saving the file trigger this?
4. "Before the March 12th's update" - please provide your pacman log, otherwise nobody can know what "the March 12th's update" means.
Online
Ah, yes. For some reason I was thinking this was the original symptom (changes had no effect). Nevermind my suspicion - but still knowing exactly how conky is launched would be good.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
All right! Guys. I found the reason. Conky crashes just when I save the .conkyrc, even without changing anything. So I rm .conkyrc today, and conky used its default config file, and everything was fine. The problem lies in my .conkyrc file. Then I noted that the difference between default and mine was "own_window_type". So I changed mine:
own_window_type = override
to
own_window_type = desktop
The problem haven't shown again.
By the way, I started conky in openbox's config file "autostart". Conky didn't crash when startx, but crashed if I started it manually in terminal. Weird!
Offline