-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: segmentation fault upon modification of conkyrc. (Regression?) #1908
Comments
You didn't start gdb with conky executable nor attached it later. Do |
Understood and my mistake. Sorry.
I am unsure I understand. Obviously I will replace the pseudo-path that is within the angle-brackets. I am not on the affected computer right now. But that does all me to add the following. The earlier version of Conky on which I do not have the problem advertises itself (within my Conky itself) as |
Stack trace
|
Caused by PR introducing geometry primitives #1862. The cause is Line that crashes: window.window = XCreateWindow(display, window.root, window.geometry.x,
window.geometry.y, b, b, 0, depth,
InputOutput, visual, flags, &attrs); on My hunch is Reproduced by reloading the config. Currently trying the following to fix this: update those pointers on move and move assignment. |
So the problem is that I tried being too clever with the dark arts of metaprogramming and missed that assignment to nested The previously proposed fix would require additional metadata at which point the So I'm removing |
@LinuxOnTheDesktop I was able to reproduce and can't anymore after fix/geometry-accessors. Can you confirm it's fixed? |
I am afraid that the problem is not fixed. Here are some details. I used git to obtain a version of conky that advertises itself as |
Clone the branch I linked with |
Right. I think I've switched branch. (I'm not great at git.) Conky now advertises itself as I seem to have the same problem as before. For, the terminal reports that the config file was modified, and that consequently it is being reloaded, but then I still get a segementation fault. I can, later, supply another stack trace. |
Alright, do let me know, because I was able to replicate and I believe the changes that got merged fixed the problem. If you're still seeing In any case, paste the new stack trace and I'll check it out. |
The latest iteration of version 1.21.1 (the iteration advertised here) seems to fix this problem. Great! EDITED. |
What happened?
I had Conky running (via the Bash script that I use always) and I modified my conkyrc. I saw this:
108971 Segmentation fault (core dumped) conky -c "${conk_path[conkyRc]}"
I am on Linux Mint Cinnamon.
I compiled from source using the latest code from git.
Previously I was using a Conky that I had compiled from source, from git, approximately a week ago - and I think that then I did not have the problem. I believe also that there was a bug report about this or a similar problem - a closed report - but I cannot find that report at present.
Version
1.21.0-pre-6bf383cf
Which OS/distro are you seeing the problem on?
Linux (other)
Conky config
No response
Stack trace
# Er . . $ gdb (gdb) run -c <full-path-of-my-conkyRC> [. . .] No executable file specified [. . .] (gdb) run conky -c <full-path-of-my-conkyRC> [. . .] No executable file specified
Relevant log output
No response
The text was updated successfully, but these errors were encountered: