MX-19 Beta 3 Feedback

[Jerry3904]

Whew, so not crazy! It is unpredictable, but I will keep after it.

[SwampRabbit]

I searched through the thread, not sure if it was brought up exactly the same as what I am seeing.

Fresh VBox install, updated, rebooted... the top of the panel where the Log Out and clock is is not transparent with the rest of the panel.

Code: Select all

System:    Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=c5141bcf-7a60-4178-bd02-e04d22d1f0f9 ro quiet video=1280x1024 splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
           Chassis: Oracle Corporation type: 1 serial: <filter> 
           Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
           date: 12/01/2006 
Battery:   ID-1: BAT0 charge: 49.0 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
           model: innotek 1 type: Unknown serial: N/A status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i7-6700HQ bits: 64 type: MCP arch: Skylake-S 
           family: 6 model-id: 5E (94) stepping: 3 microcode: N/A L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 10367 
           Speed: 2592 MHz min/max: N/A Core speeds (MHz): 1: 2592 2: 2592 
           Vulnerabilities: Type: l1tf mitigation: PTE Inversion 
           Type: mds 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
Graphics:  Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter vendor: VMware 
           driver: vboxvideo v: 6.0.12_Debian r132055 bus ID: 00:02.0 chip ID: 80ee:beef 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           alternate: vboxvideo resolution: 1920x975~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel 
           bus ID: 00:05.0 chip ID: 8086:2415 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI port: d010 
           bus ID: 00:03.0 chip ID: 8086:100e 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
           v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:    Local Storage: total: 31.67 GiB used: 5.28 GiB (16.7%) 
           ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 31.67 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR 
Partition: ID-1: / raw size: 29.64 GiB size: 29.05 GiB (98.01%) used: 5.28 GiB (18.2%) fs: ext4 
           dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 175 Uptime: 2m Memory: 3.85 GiB used: 784.7 MiB (19.9%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

[dolphin_oracle]

It's actaully just the clock thats not transparent.

[JayM]

It's actaully just the clock thats not transparent.

So that still hasn't been fixed in the Orage clock panel app, huh?
https://forum.mxlinux.org/viewtopic.php?f=108&t=48641

I always just remove the Orage clock and add the Clock panel app instead. It also has a calendar pop-up when you click the time, but lacks the ability to schedule appointments and things (which I never use anyway.) There's also the Date/Time panel app that does the same thing (simple panel clock and pop-up calendar, no scheduling of appointments.) Those who need Orage's scheduling abilities will just have to match the background color to that of their panel as best they can.

[SwampRabbit]

It's actaully just the clock thats not transparent.

Well I'll be.... yep

The colors are so close its hard to even tell.

I knew I got to the B3 too late

[Buck Fankers]

Desktop right click menu is not scroll-able, if I use my Thunar Custom Actions from MX18.
They scroll OK in Thunar. Since i have them several, I can't access desktop settings and change say wall paper.

[asqwerth]

There were discussions in the Dev team board as to whether to go with Orage or xfce's clock applet for MX19 now that it's on xfce 4.14. It was a toss up between more functionality in orage (and more users being used to it having been MX's default clock app all this while) and various aesthetic niggles it had when placed on the new gtk3 xfce panel.

[JayM]

What's frustrating is that someone wrote a patch in 2017 that fixes the transparency issue but no one's updated Orage since 2015 let alone applied the patch. I did so to the Orage 4.12 source code but am unable to get it to compile. ./configure complains that it can't find gtk2.0. Here's the patch if anyone's interested:

Code: Select all

diff --git a/panel-plugin/xfce4-orageclock-plugin.c b/panel-plugin/xfce4-orageclock-plugin.c
index ae3aa8b..3623d8a 100644
--- a/panel-plugin/xfce4-orageclock-plugin.c
+++ b/panel-plugin/xfce4-orageclock-plugin.c
@@ -735,10 +735,13 @@ void oc_bg_set(Clock *clock)
 {
     GdkColor *bg = NULL;
 
-    if (clock->bg_set)
+    if (clock->bg_set) {
         bg = &clock->bg;
-
-    gtk_widget_modify_bg(clock->ebox, GTK_STATE_NORMAL, bg);
+        gtk_widget_modify_bg(clock->ebox, GTK_STATE_NORMAL, bg);
+        gtk_event_box_set_visible_window(GTK_EVENT_BOX(clock->ebox), TRUE);
+    } else {
+        gtk_event_box_set_visible_window(GTK_EVENT_BOX(clock->ebox), FALSE);
+    }
 }
 
 void oc_timezone_set(Clock *clock)

Edit: I got it to compile (I didn't have the gtk2.0 dev library installed, d'oh!) and installed it but it's not available as a panel app. If I install orage from the repo (I had uninstalled it prior to compiling from patched source and installing that) then do sudo make install again I seem to still have the orage panel app from the package, not the one from the source code. I obviously don't know what I'm doing, but I doubt if the MX packagers would want to maintain a patched version of orage anyway, so I guess it doesn't really matter.

Edit 2: I figured it out. Having a transparent background in Orage only works with a solid color panel background, not when you tell the panel to use "None (use system style)" which is the default. Apparently it assumes that "none" means no color so it uses its own background color. YMMV because I found this out after compiling and installing the patched version, though I did do a sudo make uninstall, then uninstalled and reinstalled Orage from MXPI, logged out/in and I get the same results.

[Eadwine Rose]

Hmm.. how then is it possible that it is transparent for me?

This is from beta2.1:

snapshot.png

[JayM]

Hmm.. how then is it possible that it is transparent for me?

This is from beta2.1:

snapshot.png

See my edit 2 above. You probably selected a solid panel background color (with transparency, it looks like,)