Created attachment 58440 [details] patch that seems to fix the issue for me Version: unspecified (using KDE 4.6.1) OS: FreeBSD I have a dual monitor setup where one monitor is positioned above the other. Resolution of the top monitor is 1680x1050, resolution of the bottom monitor is 1280x998, virtual resolution is 1680 x 2048. Reproducible: Always Steps to Reproduce: Login to KDE with the described monitor setup configured in xorg.conf. Actual Results: No splash screen, ksplashx crashes. Expected Results: Splash screen. The following gdb session shows details of the crash: Starting program: /usr/obj/usr/ports/x11/kdebase4-workspace/work/kdebase-workspace-4.6.1/build/ksplash/ksplashx/ksplashx Default Program received signal SIGBUS, Bus error. 0x000000000041602b in updateSplashImage (img=..., x_pos=0, y_pos=1050) at /usr/obj/usr/ports/x11/kdebase4-workspace/work/kdebase-workspace-4.6.1/ksplash/ksplashx/splash.cpp:833 833 *d = *s; (gdb) p d $1 = (QRgb *) 0xff00080bff000508 (gdb) p s $2 = (QRgb *) 0x8038df8d0 (gdb) x/s 0xff00080bff000508 0xff00080bff000508: <Address 0xff00080bff000508 out of bounds> (gdb) list 828 QRgb* d = (( QRgb* )( splash_image.scanLine( y + y_pos ))) + x_pos; 829 for( int x = 0; 830 x < img.width(); 831 ++x, ++d, ++s ) 832 { 833 *d = *s; 834 } 835 } 836 PixmapData pix = imageToPixmap( img ); 837 GC gc = qt_xget_temp_gc( x11Screen(), false ); (gdb) p y $3 = 998 (gdb) p y_pos $4 = 1050 (gdb) p x_pos $5 = 0 (gdb) p x $6 = 0 (gdb) p splash_image $7 = {data = 0x802404060} (gdb) p splash_image.data $8 = (QImage::QImageData *) 0x802404060 (gdb) p *splash_image.data $9 = {<QShared> = {count = 1}, w = 1680, h = 2048, d = 32, ncols = 0, nbytes = 13762560, bitordr = 0, ctbl = 0x0, bits = 0x802600000, alpha = false, dpmx = 0, dpmy = 0, offset = {xp = 0, yp = 0}, ctbl_mine = false} (gdb) p *img.data $10 = {<QShared> = {count = 1}, w = 1278, h = 1024, d = 32, ncols = 0, nbytes = 5234688, bitordr = 0, ctbl = 0x0, bits = 0x803400000, alpha = false, dpmx = 14173, dpmy = 14173, offset = {xp = 0, yp = 0}, ctbl_mine = false} It looks like the crash happens when y + y_pos goes beyond splash_image height.
Forgot to mention - the top monitor is designated as the primary monitor. With the patch the progress bar is shown in the middle of it while the background is shown on both monitors. The splash theme is the default default one.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
I haven't been using that kind of vertical monitor arrangement for many years. I think that the issue can be easily checked, but right now I do not have two monitors near me.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!