Created attachment 1617806 [details]
File: backtrace

Created attachment 1617807 [details]
File: cgroup

Created attachment 1617808 [details]
File: core_backtrace

Created attachment 1617809 [details]
File: cpuinfo

Created attachment 1617810 [details]
File: dso_list

Created attachment 1617811 [details]
File: environ

Created attachment 1617812 [details]
File: limits

Created attachment 1617813 [details]
File: maps

Created attachment 1617814 [details]
File: mountinfo

Created attachment 1617815 [details]
File: open_fds

Created attachment 1617816 [details]
File: proc_pid_status

(In reply to Basil Mohamed Gohar from comment #0)
> Description of problem:
> Anytime I click on Solaar applet and choose to see extended details of a
> component, such as a mouse or keyboard, the app will crash in this fashion.

Thanks for the report. I cannot reproduce it. Which desktop environment are you using? Does `solaar show` work? Please post the output.

Thank you for the prompt reply!

I am use MATE.

This is the output of `solaar show`:

[basilgohar@rummaan-hidayahonline-net ~]$ solaar show
Unifying Receiver
  Device path  : /dev/hidraw2
  USB id       : 046d:c52b
  Serial       : 9D2AACB0
    Firmware   : 24.07.B0030
    Bootloader : 02.09
    Other      : AA.AC
  Has 2 paired device(s) out of a maximum of 6.
  Notifications: wireless, software present (0x000900)
  Device activity counters: 1=81

  1: Wireless Mouse M510
     Codename     : M510v2
     Kind         : mouse
     Wireless PID : 4051
     Protocol     : HID++ 4.5
     Polling rate : 8 ms (125Hz)
     Serial number: 9D2AACB0
          Firmware: RQM 62.01.B0015
     The power switch is located on the base.
     Supports 21 HID++ 2.0 features:
         0: ROOT                   {0000}   
         1: FEATURE SET            {0001}   
         2: DEVICE FW VERSION      {0003}   
         3: DEVICE NAME            {0005}   
         4: RESET                  {0020}   
         5: BATTERY STATUS         {1000}   
         6: unknown:1802           {1802}   internal, hidden
         7: unknown:1810           {1810}   internal, hidden
         8: unknown:1830           {1830}   internal, hidden
         9: unknown:1862           {1862}   internal, hidden
        10: unknown:1890           {1890}   internal, hidden
        11: unknown:18A0           {18A0}   internal, hidden
        12: unknown:18B1           {18B1}   internal, hidden
        13: REPROG CONTROLS V4     {1B04}   
        14: WIRELESS DEVICE STATUS {1D4B}   
        15: unknown:1DF0           {1DF0}   hidden
        16: unknown:1E00           {1E00}   hidden
        17: unknown:1E22           {1E22}   internal, hidden
        18: unknown:1EB0           {1EB0}   internal, hidden
        19: LOWRES WHEEL           {2130}   
            Wheel Reports: HID
        20: POINTER SPEED          {2205}   
            Pointer Speed: 1.0
     Has 7 reprogrammable keys:
         0: LEFT CLICK                , default: LeftClick                   => LEFT CLICK                
             mse, divertable, pos:0, group:1, gmask:1
         1: RIGHT CLICK               , default: RightClick                  => RIGHT CLICK               
             mse, divertable, pos:0, group:1, gmask:1
         2: MIDDLE BUTTON             , default: MiddleMouseButton           => MIDDLE BUTTON             
             mse, reprogrammable, divertable, pos:0, group:2, gmask:3
         3: LEFT SCROLL AS AC PAN     , default: HorzScrollLeftSet           => LEFT SCROLL AS AC PAN     
             mse, reprogrammable, divertable, pos:0, group:2, gmask:3
         4: RIGHT SCROLL AS AC PAN    , default: HorzScrollRightSet          => RIGHT SCROLL AS AC PAN    
             mse, reprogrammable, divertable, pos:0, group:2, gmask:3
         5: BACK AS BUTTON 4          , default: BackEx                      => BACK AS BUTTON 4          
             mse, reprogrammable, divertable, pos:0, group:2, gmask:3
         6: FORWARD AS BUTTON 5       , default: BrowserForwardEx            => FORWARD AS BUTTON 5       
             mse, reprogrammable, divertable, pos:0, group:2, gmask:3
     Battery: 70%, discharging.

  2: Wireless Solar Keyboard K750
     Codename     : K750
     Kind         : keyboard
     Wireless PID : 4002
     Protocol     : HID++ 2.0
     Polling rate : 20 ms (50Hz)
     Serial number: BA988AAB
     The power switch is located on the edge of top right corner.
     Battery: unknown (device is offline).

Similar problem has been detected:

Flip the power switch off on a K520 keyboard connected to the receiver.
Click on any of the items from the drop-down menu of the tray panel.

reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        /usr/bin/python3 -s /usr/bin/solaar
crash_function: gtk_cell_renderer_get_aligned_area
executable:     /usr/bin/python3.7
journald_cursor: s=1273e7e5a1c249bbbe3604a84b4582db;i=95720;b=fcd9fdfb43e44a33999d9bb769211f88;m=81f3e86;t=5962fef99e6d7;x=d91b9725e9b9448f
kernel:         5.3.7-200.fc30.x86_64
package:        solaar-1.0.1-1.fc30
reason:         python3.7 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Ok, so it seems I can reproduce this on one of my machines which has a K520 keyboard and a M310 mouse when the keyboard power switch is off, but it's not reproducible on another machine with K800 and M325. Let's dig into this upstream, then.

Reported upstream.

Reproducible on F31 as well.

We did some debugging upstream and it's likely a GTK bug. What is the desktop theme that you're using? It's crashing for me on BlueMenta theme, but not on TraditionalOk.

You can find it under System->Preferences->Look and Feel->Appearance.

Apparently, this only happens with BlueMenta and Menta themes on MATE, hence reassigning to mate-themes package. It could be a GTK bug, but I have no idea how to debug this further.

I can confirm that solar window crashes when BlueMenta theme is used, but it seems that this application don't like a padding with GtkTreeView or GtkCellGtkCellRenderer inside a GtkTreeView.

Gtk:ERROR:gtkcellrenderer.c:1796:gtk_cell_renderer_get_aligned_area: assertion failed: (aligned_area->x >= cell_area->x && aligned_area->x <= cell_area->x + cell_area->width)

Commenting out those 2 lines in gtkwidget.css avoid this crash.

https://github.com/mate-desktop/mate-themes/blob/master/desktop-themes/BlueMenta/gtk-3.0/gtk-widgets.css#L4631

treeview.view {
/*    padding: 0px 1px;*/
}

https://github.com/mate-desktop/mate-themes/blob/master/desktop-themes/BlueMenta/gtk-3.0/gtk-widgets.css#L4771

.cell {
/*	padding: 2px;*/
	text-shadow: none;
}

But using a padding in treeview.view {} or .cell {} is quite common and not a theme issue. Other applications (eg. gtk3-widget-factory or others) with a treeview don't crash with this setting.
And i am in doubt that this is an bug in GtkCellGtkCellRenderer itself.

As workaround you can create ~/.config/gtk-3.0/gtk.css for the moment with that content:

treeview.view {
    padding: 0px;
}

.cell {
    padding: 0px;
}

Fixed by solaar upstream https://github.com/pwr-Solaar/Solaar/pull/643

(In reply to Dominik 'Rathann' Mierzejewski from comment #18)
> We did some debugging upstream and it's likely a GTK bug. What is the
> desktop theme that you're using? It's crashing for me on BlueMenta theme,
> but not on TraditionalOk.
> 
> You can find it under System->Preferences->Look and Feel->Appearance.

Apologies for the late reply.  I didn't catch the "needinfo" for this specific question and was wondering why BZ kept bugging me...:-p

Yes, I have a BlueMenta-based theme (it says Custom, but I think I just changed something like a font or something similar).

Thanks for the reply. Can you try switching to another theme (without Menta in its name) and see if it's still crashing for you?
Upstream committed a fix and it'll be included in the next release, but for now the work-around is to change the theme.

(In reply to Dominik 'Rathann' Mierzejewski from comment #23)
> Thanks for the reply. Can you try switching to another theme (without Menta
> in its name) and see if it's still crashing for you?
> Upstream committed a fix and it'll be included in the next release, but for
> now the work-around is to change the theme.

Yes.  That worked!  I'm not minding the theme switch at this time, so I think I'll rock "TraditionalOk" for a while longer....just avoiding Menta (which yes, other ones also have the same problem).

Interestingly, I just got some new Logitech peripherals, so I really did need to use Solaar, and it worked perfectly after this.  Forgot how awesome of a utility this really was.  I just couldn't use it much all this time. :-D

FEDORA-2020-5011b62b4b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5011b62b4b

FEDORA-2020-2d902a1576 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d902a1576

FEDORA-2020-d00e89d607 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d00e89d607

FEDORA-2020-5011b62b4b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5011b62b4b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5011b62b4b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-d00e89d607 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d00e89d607`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d00e89d607

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-2d902a1576 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2d902a1576`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d902a1576

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-5011b62b4b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-2d902a1576 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-5011b62b4b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-d00e89d607 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.