[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#1272 - Conky Crashes With own_window_transparent yes User who did this - Uli Schlachter (psychon) Reason for closing: Not a bug Additional comments about closing: I am not completely sure, but I think the reporter says that this isn't our fault. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1272 - Conky Crashes With own_window_transparent yes User who did this - AwesomeBug (AwesomeBug) -- Hi, My mistake, didn't realize conky config needs to be changed a little different when using a tiling window manager. I made some changes to my config and it's working now... Sorry about this... :( Cheers -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272#comment4084 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1272 - Conky Crashes With own_window_transparent yes User who did this - Uli Schlachter (psychon) -- I noticed now if I disable compton and use these options below conky runs ok and transparent, but I can't use compton still. So you are now saying this a bug between compton and conky? Awesome has nothing to do with it? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272#comment4077 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - AwesomeBug (AwesomeBug)
Attached to Project - awesome
Summary - Conky Crashes With own_window_transparent yes
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
Specs:
Slackware 14.1 x86_64
xorg-server-1.14.3
Awesome 3.5.5
Nvidia GTX660M - 331.67 drivers
Conky 1.9.0
I've been told this might be a conky bug, but I've never had crashes with conky
ever and this script runs fine in other DE/WM; KDE, Gnome, Xfce, Openbox.
This is my script
-
background yes
use_xft yes
xftfont aller:size=9
xftalpha 0.8
out_to_console no
update_interval 3.0
total_run_times 0
draw_shades no
own_window yes
own_window_type desktop# normal /override /desktop
own_window_transparent yes
own_window_hints undecorate,sticky,skip_taskbar,skip_pager,below,sticky
minimum_size 1920
maximum_width 1920
double_buffer yes
default_color e3412c
color1 DDBBAA
alignment top_middle
gap_y 5 #vertical
#gap_x 0 #horizontal
no_buffers yes
TEXT
${alignc}${color}CPU1: ${color1}${cpu cpu0}% \
${color}CPU2: ${color1}${cpu cpu1}% \
${color}CPU3: ${color1}${cpu cpu2}% \
${color}CPU4: ${color1}${cpu cpu3}% - ${freq}MHz - ${platform coretemp.0 temp
1} °C \
${color}GPU: ${color1}${execi 100 nvidia-settings -q gpucoretemp -t | head -1}
°C \
${color}RAM: ${color1}${mem} - $memperc% \
${color}SSD: ${color1}${fs_free /} free \
${color}LAN: ${color1}${addr eth0} - ${downspeed eth0} kb/s down - ${upspeed
eth0} kb/s up \
${color}POWER: ${color1}${acpiacadapter AC0} - Battery: ${battery_percent
BAT0}% ${battery_time BAT0} \
${color}UP: ${color1}$uptime
#|--Battery-OSD
${execi 70 ~/.conky/scripts/battery_notify.sh}
-
And when I try running conky this is the ouput I'm getting;
Conky: forked to background, pid is 7423
Conky: desktop window (289) is root window
Conky: window type - desktop
Conky: drawing to created window (0xc1)
Conky: drawing to double buffer
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 2 (X_ChangeWindowAttributes)
Serial number of failed request: 237
Current serial number in output stream: 238
I've tried several options and the only thing I can get to work is with
override, but I like using compton and this draws shadows around it.
I've been testing conky without compton running, this is why I didn't list it
for 'specs'
Thank you! :)
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1272 - Conky Crashes With own_window_transparent yes User who did this - AwesomeBug (AwesomeBug) -- I ran for debug; conky -DD -c horizontal.orange Here's ouput; DEBUG(0) [conky.c:5338]: reading contents from config file 'horizontal.orange' DEBUG(1) [core.c:1225]: no templates to replace DEBUG(1) [core.c:354]: Adding $cpu for CPU 0 DEBUG(1) [core.c:354]: Adding $cpu for CPU 1 DEBUG(1) [core.c:354]: Adding $cpu for CPU 2 DEBUG(1) [core.c:354]: Adding $cpu for CPU 3 DEBUG(0) [linux.c:1058]: parsed platform args: 'coretemp.0' 'temp' 1 1.00 0.00 Conky: forked to background, pid is 10053 Conky: desktop window (289) is root window Conky: window type - desktop Conky: drawing to created window (0x121) Conky: drawing to double buffer X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Serial number of failed request: 349 Current serial number in output stream: 350 -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272#comment4075 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1272 - Conky Crashes With own_window_transparent yes
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1272 - Conky Crashes With own_window_transparent yes User who did this - AwesomeBug (AwesomeBug) -- I noticed now if I disable compton and use these options below conky runs ok and transparent, but I can't use compton still. own_window no own_window_class Conky own_window_type normal# normal /override /desktop own_window_transparent yes own_window_hints undecorate,sticky,skip_taskbar,skip_pager,below Again I've been told this might be a conky bug but I've never had a problem ever running Conky under several different desktops and window managers in about five years till now. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1272#comment4076 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
