search

rockowitz / ddcui

Graphical user interface for ddcutil - control monitor settings
http://www.ddcutil.com
GNU General Public License v2.0
147 stars 2 forks source link

Segment violation on Ubuntu 19.04 #7

Closed ghost closed 4 years ago

ghost commented 5 years ago

Trying to run ddcui (ddcutil runs perfect):

ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (core' generado)`

rockowitz commented 5 years ago

The "(ddc_write_read_with_retry) .. for DDC Null Response" is just an informational message from ddcutil about recovery from an unusual but not impossible response from a monitor.

Can you run ddcui using valgrind?  That should pinpoint the location of the segfault.  Please send the output as a file.

Also, please run "sudo ddcutil interrogate 2>&1" and send the output as a file as well.  That will help me better understand your system.  It's possible that the ddcutil API is returning invalid data that ddcui can't handle.

Thank you, Sanford

On 5/26/19 5:42 AM, mavr76 wrote:

Trying to run ddcui (ddcutil runs perfect):

|ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (|core' generado) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3QEPH4TQKTSDZ3WA53PXJLRTA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GV4JWWA, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMGY3X5R6NEERTEJFCGBBDPXJLRTANCNFSM4HPWJGAA.

ghost commented 5 years ago

Ok, there it goes as attachments.

interrogate_output.txt valgrind_output.txt

I'm running Ubuntu 19.04 on a Toshiba z30 laptop with and external monitor connected by HDMI (Dell P2419HC).

Thank you for your work and support

On Sun, May 26, 2019 at 6:54 PM rockowitz notifications@github.com wrote:

The "(ddc_write_read_with_retry) .. for DDC Null Response" is just an informational message from ddcutil about recovery from an unusual but not impossible response from a monitor.

Can you run ddcui using valgrind? That should pinpoint the location of the segfault. Please send the output as a file.

Also, please run "sudo ddcutil interrogate 2>&1" and send the output as a file as well. That will help me better understand your system. It's possible that the ddcutil API is returning invalid data that ddcui can't handle.

Thank you, Sanford

On 5/26/19 5:42 AM, mavr76 wrote:

Trying to run ddcui (ddcutil runs perfect):

|ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (|core' generado) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3QEPH4TQKTSDZ3WA53PXJLRTA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GV4JWWA>,

or mute the thread < https://github.com/notifications/unsubscribe-auth/ADMGY3X5R6NEERTEJFCGBBDPXJLRTANCNFSM4HPWJGAA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=AKT5SMAYJ3R7CGRRXVQAZV3PXK6EHA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIJO7I#issuecomment-496015229, or mute the thread https://github.com/notifications/unsubscribe-auth/AKT5SMDOSCHFWTEARSRE77TPXK6EHANCNFSM4HPWJGAA .

ghost commented 5 years ago

Sorry,

I just realize that the valgrind_output file is empty. Here is the output attached. valgrind_output2.txt

On Sun, May 26, 2019 at 6:54 PM rockowitz notifications@github.com wrote:

The "(ddc_write_read_with_retry) .. for DDC Null Response" is just an informational message from ddcutil about recovery from an unusual but not impossible response from a monitor.

Can you run ddcui using valgrind? That should pinpoint the location of the segfault. Please send the output as a file.

Also, please run "sudo ddcutil interrogate 2>&1" and send the output as a file as well. That will help me better understand your system. It's possible that the ddcutil API is returning invalid data that ddcui can't handle.

Thank you, Sanford

On 5/26/19 5:42 AM, mavr76 wrote:

Trying to run ddcui (ddcutil runs perfect):

|ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (|core' generado) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3QEPH4TQKTSDZ3WA53PXJLRTA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GV4JWWA>,

or mute the thread < https://github.com/notifications/unsubscribe-auth/ADMGY3X5R6NEERTEJFCGBBDPXJLRTANCNFSM4HPWJGAA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=AKT5SMAYJ3R7CGRRXVQAZV3PXK6EHA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIJO7I#issuecomment-496015229, or mute the thread https://github.com/notifications/unsubscribe-auth/AKT5SMDOSCHFWTEARSRE77TPXK6EHANCNFSM4HPWJGAA .

ghost commented 5 years ago

I also re-run valgrind with extended log. Here it goes, I hope it help. valgrind_log.txt

On Sun, May 26, 2019 at 6:54 PM rockowitz notifications@github.com wrote:

The "(ddc_write_read_with_retry) .. for DDC Null Response" is just an informational message from ddcutil about recovery from an unusual but not impossible response from a monitor.

Can you run ddcui using valgrind? That should pinpoint the location of the segfault. Please send the output as a file.

Also, please run "sudo ddcutil interrogate 2>&1" and send the output as a file as well. That will help me better understand your system. It's possible that the ddcutil API is returning invalid data that ddcui can't handle.

Thank you, Sanford

On 5/26/19 5:42 AM, mavr76 wrote:

Trying to run ddcui (ddcutil runs perfect):

|ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (|core' generado) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3QEPH4TQKTSDZ3WA53PXJLRTA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GV4JWWA>,

or mute the thread < https://github.com/notifications/unsubscribe-auth/ADMGY3X5R6NEERTEJFCGBBDPXJLRTANCNFSM4HPWJGAA .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=AKT5SMAYJ3R7CGRRXVQAZV3PXK6EHA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIJO7I#issuecomment-496015229, or mute the thread https://github.com/notifications/unsubscribe-auth/AKT5SMDOSCHFWTEARSRE77TPXK6EHANCNFSM4HPWJGAA .

rockowitz commented 5 years ago

I suspect the problem has to do with how ddcutil/ddcui are reporting the invalid laptop display.

I have added/enabled tracing code in ddcutil development branch 0.9.6 and ddcui 0.0.5.

Please rebuild, run ddcui under valgrind, and send the output as an attachment.  There is no need for the extended valgrind output.  That just shows memory that is not been released at program shutdown, which is expected.

Thanks for your help in tracking down this bug.

Sanford

On 5/26/19 2:16 PM, mavr76 wrote:

I also re-run valgrind with extended log. Here it goes, I hope it help.

On Sun, May 26, 2019 at 6:54 PM rockowitz notifications@github.com wrote:

The "(ddc_write_read_with_retry) .. for DDC Null Response" is just an informational message from ddcutil about recovery from an unusual but not impossible response from a monitor.

Can you run ddcui using valgrind? That should pinpoint the location of the segfault. Please send the output as a file.

Also, please run "sudo ddcutil interrogate 2>&1" and send the output as a file as well. That will help me better understand your system. It's possible that the ddcutil API is returning invalid data that ddcui can't handle.

Thank you, Sanford

On 5/26/19 5:42 AM, mavr76 wrote:

Trying to run ddcui (ddcutil runs perfect):

|ddcui (0x7f8de5bef780 MainWindow::longRunningTaskStart) Executing (ddc_write_read_with_retry) Display_Handle[i2c: fh=23, busno=3], ddc_write_read() succeeded after 1 sleep and retry for DDC Null Response (0x7f8de5bef780 MainWindow::initMonitors) Processing display 0 (0x7f8de5bef780 MainWindow::initMonitors) Processing display 1 Violación de segmento (|core' generado) `

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <

https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3QEPH4TQKTSDZ3WA53PXJLRTA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GV4JWWA>,

or mute the thread <

https://github.com/notifications/unsubscribe-auth/ADMGY3X5R6NEERTEJFCGBBDPXJLRTANCNFSM4HPWJGAA

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub

https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=AKT5SMAYJ3R7CGRRXVQAZV3PXK6EHA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIJO7I#issuecomment-496015229, or mute the thread

https://github.com/notifications/unsubscribe-auth/AKT5SMDOSCHFWTEARSRE77TPXK6EHANCNFSM4HPWJGAA .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3RVO3JVFYHKCW2RGKLPXLHX5A5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIKYBA#issuecomment-496020484, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMGY3SVPZXMI74IIFBTZ5LPXLHX5ANCNFSM4HPWJGAA.

ghost commented 5 years ago

Hi again,

I built both, ddcutil 0.9.6 and ddcui 0.0.5. Now, ddcui runs perfect without error.

Despite this, I ran again "sudo ddcutil interrogate 2>&1" and ddcui under valgrind so here it is as attachment:

valgrind_log.txt interrogate_log.txt

rockowitz commented 5 years ago

If the segfault has gone away, it probably resulted from a version mismatch between libddcutil and ddcui.  Up until now, as ddcui is alpha level code and the API implemented by libddcutil has been changing rapidly to keep up, I haven't used SONAME versioning for libddcutil.  The time has come to start using library versioning, and that will be implemented in the next release of ddcutil.

I'm surprised that the valgrind log doesn't include any of the ddcui/libddcutil trace output.  I would be curious to see the tracing before turning it off.  Can you run ddcui again without valgrind and send me the console log.  Thanks.

Sanford

On 5/27/19 11:40 AM, mavr76 wrote:

Hi again,

I built both, ddcutil 0.9.6 and ddcui 0.0.5. Now, ddcui runs perfect without error.

Despite this, I ran again "sudo ddcutil interrogate 2>&1" and ddcui under valgrind so here it is as attachment:

valgrind_log.txt https://github.com/rockowitz/ddcui/files/3224355/valgrind_log.txt interrogate_log.txt https://github.com/rockowitz/ddcui/files/3224356/interrogate_log.txt

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockowitz/ddcui/issues/7?email_source=notifications&email_token=ADMGY3TVFDOZCUVTC3LFXN3PXP6GPA5CNFSM4HPWJGAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKC4SQ#issuecomment-496250442, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMGY3RPMOD7FLZMNDTCHTTPXP6GPANCNFSM4HPWJGAA.

ghost commented 5 years ago

Here it is ddcui_log.txt