linuxmint / mint19.2-beta

BETA Bug Squah Rush
4 stars 4 forks source link

Cinnamon - stock theme - lack of padding for modal dialogs with buttons & run dialog #76

Closed smurphos closed 5 years ago

smurphos commented 5 years ago

Describe the bug The stock Cinnamon theme modal dialog confirmation for removing applets lacks padding between the buttons and text and looks poor The run dialog could also do with a little padding between the prompt and the entry.

To Reproduce Steps to reproduce the behavior:

Set Desktop theme to Cinnamon in Themes module. Right clock on menu applet and click remove. Note the lack of padding between the buttons and text

Press Alt-F2 to bring up the run dialog - not the lack of padding between the entry and text.

Expected behavior Nicer looking dialogs

Frequency Does the issue happen:

Edition (Desktop environment): In which edition is this happening?

Live or post-install: Indicate if this is happening after the installation, or during the live session:

Screenshots If applicable, add screenshots to help explain your problem. screenshot-screen-2019-07-28-072952

Screenshot from 2019-07-28 07-52-00

Locale: Paste the output of locale.

steve@steve-HP-Pavilion-g6-Notebook-PC:~$ locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL

Drivers: Paste the output of inxi -Gxx.

steve@steve-HP-Pavilion-g6-Notebook-PC:~$ inxi -Gxx
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0116 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2 
  compat-v: 3.0 direct render: Yes 

Crash report:

''Stack trace'' If you are reporting a crash. Go to "Software Sources" and enable the debug symbols. Then go to "System Reports" and extract the stack trace for your crash and paste it here.

''Dmesg'' If you type dmesg in a terminal, you should see a line corresponding to the crash. Paste it here.

Additional context Add any other context about the problem here.