FF not following theme

Sector11 · 2017-06-17 23:49:10

Anyone have an idea why FireFox isn't following my dark theme anymore?
Or better yet, know why it isn't?

Theme is: S11-NS-brushed
OB Theme: S11-SR-71-Black

EDIT: I am using the stock FF-ESR in "Deuterium" which is: 52.2.0 (64-bit)

Last edited by Sector11 (2017-06-19 17:06:17)

hhh · 2017-06-18 05:09:02

What version Fx?

hhh · 2017-06-18 05:11:01

> Anyone have an idea why FireFox isn't following my dark theme anymore?
Or better yet, know why it isn't?

Ha! Impressive double negative. You may pass The Bridge of Death.

nobody · 2017-06-18 11:02:44

Modern Firefox uses GTK3 and not GTK2, and it does not use it 'correctly' in all places, i.e. it uses some elements incorrectly.

a) Always use the most recent FF version, because things actually improve (FF 54).

b) You need to use a GTK3 theme that has given special consideration to Firefox' twisted GTK3 usage. For example, Arc (Light, Dark, Darker), Breeze-GTK etc.

c) An alternative is to use whole themes for Firefox itself (install them like addons from the addons menu).

d) You get the developer edition's dark/light theme for free in Firefox, check it out, it looks quite good.

Head_on_a_Stick · 2017-06-18 11:06:45

twoion wrote:

a) Always use the most recent FF version, because things actually improve (FF 54).

The OP won't like that because FF v54 has a hard dependency on libpulse

Sector11 · 2017-06-18 18:35:30

Yea, and right now on an almost clean install of BL-D, I copied over ~/.claws-mail and ~/.mozilla then installed claws-mail and thunderbird I have the same FF as before: v52.2.0

I will have to change browsers when FF insists on Pulse.
Pulse has never worked on this machine since my #! days - which means for the moment I have no sound again. And BTW, that theme "S11-NS-Black" was working on my BL pre Deuterium install.

Sorry for the delay in responding I have been reinstalled BL-D for days trying to figure out why things don't work with my pre-Deuterium configs. Think I have it nailed down now.

johnraff · 2017-06-19 01:17:20

Sector11 wrote:

Pulse has never worked on this machine since my #! days...

Pulse has changed a lot. Because it didn't work 5 years ago doesn't necessarily mean it can't be got to work now. /OT

Sector11 · 2017-06-19 02:09:31

You forgot this: [Sovled] No sound with Pulse Audio And now I find that while there was (I had to reinstall again) ALSA sound here, there was nothing on the net - no music, no videos (could see them though). Have to start over.

So HoaS has it right: The OP won't like that because FF v54 has a hard dependency on libpulse

johnraff · 2017-06-19 02:32:02

^No, I didn't forget that. You were asked if you'd be interested in co-operating to get to the bottom of why PA wasn't working for you:

Head_on_a_Stick wrote:

OK, the only difference there is the IRQ number for the non-default card
In the live system, what does PulseAudio say about the available outputs?
pacmd list-sinks
@ector1935's suggestion is worth a try if you happen to have an installed system with PulseAudio still in place; it would be really useful to track down this failing.
In your qasmixer system (s12), have any module options been applied?
grep -R intel /etc/modprobe.d

So the question is still open.

Sector11 · 2017-06-19 03:55:23

Well, lets just say I've been trying to fix other problems I'm having with BL "Deuterium" and at the point that thread was started I was interested in getting sound working. I did, and yes, I am interested in seeing if I can get PA working. For that reason I have three installs here, and I've had to reinstall all three of them multiple times trying to get things working. So it's pretty hard working on finding out why pulse isn't working when the system won't stay up. And according to to the Xorg.0.logs I sent to HoaS everything is OK - but obviously, it's not.

I have gotten to the point before trying anything now - no matter how trivial - I will ask questions. Because what worked in #!, what worked in my old BL install is not working in "Deuterium". Copy some config file from my "backup" ~/.conf and next thing I know I have a "screen with a mouse pointer" - nothing else. I saved one shot!. Have to drop to TTY1 or 2 to 'try and fix things'

So I'm going to ask some really dumb questions in the coming days if it means I can keep this system from going wonkers on me. I have been driving HoaS crazy in PM's because everything I do, every tweak I try, I end up with a blank screen with nothing but a mouse pointer. I have spent the last week - reinstalling more times than I can count. I've been searching and researching stuff all over the web with Startpage, seen more TTY1's and TTY2's in the past 7 days than I have in 7 years of using Linux.

In one of those installs I deleted the symlink directories mentioned in the first post, along with a couple of other tweaks. So I wan't 100% certain it was the fact they were deleted that caused the problem. Of course, I had NO IDEA that there was a change in the wind and things had moved to ~/.local/share - but I ended up with a blank screen and a mouse pointer "again" ...

Now this was a simple question ... about FF (same version as before) not following the 'same themes' I used before.

OpenBox = S11-SR-71-Black & system theme = S11-NS-Brushed that I have been using since #!, Waldorf days and with the BL install before now. It's a tweak of Onyx that comes with Deuterium - so it should work. But I'm not getting the black drop down menus.

johnraff · 2017-06-19 04:50:51

Hmm... it's really bad that you're getting all these problems with the latest release. I don't really think all that much changed with Deuterium - mostly in the way PA and compton were started up in ~/.config/openbox/autostart - but I got the impression that perhaps your previous install came from a much earlier "dev" version, and was updated after that? If so then it might have been a bigger jump for you. Some of those config files you copied in from "backup" might need tweaking before use.

If you want to take a bit of the load off HoaS you could post your problems here in the forum instead of in PMs - that way other people might join in with advice, and other people can benefit from the solutions. And certainly don't be afraid to ask what might seem to be "dumb questions".

Back on topic where are the themes you're using? installed on the system, or in your local ~/.themes folder? If the latter, you might want to try moving them to ~/.local/share/themes.

EDIT: also, what happens if you try another darkish theme, like "Bunsen", or the untweaked Onyx theme? Do the drop-down menus fit in then?

Last edited by johnraff (2017-06-19 05:34:36)

Sector11 · 2017-06-19 05:38:34

Right no they are in
~/.locale/share/themes
~/.locale/share/icons
~/.locale/share/fonts

the symlinked dirs are still there - BUT and this is what HoaS was helping with: NVIDIA it will install quite nicely on some systems but not here probably as I left nouveau as I built things up. Donno try tomorrow.

Tomorrow I'll reinstall - update and then install NVIDIA. (yes, I need it, it's faster, and better graphics and "transparent conkys are actually transparent" IF I can get compton running.

Off to bed - wife is waiting.

johnraff · 2017-06-19 06:08:40

If NVIDIA still doesn't work, maybe start a new thread on that topic?
Does the live system work OK?

Head_on_a_Stick · 2017-06-19 07:01:19

Sector11 wrote:

And now I find that while there was (I had to reinstall again) ALSA sound here, there was nothing on the net - no music, no videos (could see them though). Have to start over.
So HoaS has it right: The OP won't like that because FF v54 has a hard dependency on libpulse

Are you sure you were using FF v54?

Debian has just switched to the v52 ESR branch and that works without PulseAudio.

Sector11 wrote:

Copy some config file from my "backup" ~/.conf

And there is the problem

Please post the *exact* command used and also the full name and content of any files that are copied by that command (use the "-v" flag to get it to list the files copied).

Sector11 · 2017-06-19 17:20:44

I am using the stock FF-ESR in "Deuterium" which is: 52.2.0 (64-bit) - Will put that tidbit in the OP as well.

When I deleted the symlinked directories:
/home/sector11/.fonts
/home/sector11/.icons
/home/sector11/.themes

and recreated them putting my fonts in ~/.fonts; icons in ~/.icons and themes in ~/.themes = OOPS! Broken stuff.

I am using the same themes as I did in my earlier BL - which John has guessed is his BL-ALPHA = Deb Netinstall with the early scripts (I also edited some things in those scripts so Pulse was not installed and no network manager either, etc. etc. Right now in this build, themes, icons and fonts are all in ~/.local/share --> /themes /icons & /fonts

And right now, with that, I still get:

So if anyone has an idea how to fix this I'd appreciate it because it worked like a champ in the earlier version I had of BL.

twoion wrote:

Modern Firefox uses GTK3 and not GTK2, and it does not use it 'correctly' in all places, i.e. it uses some elements incorrectly.
a) Always use the most recent FF version, because things actually improve (FF 54).
b) You need to use a GTK3 theme that has given special consideration to Firefox' twisted GTK3 usage. For example, Arc (Light, Dark, Darker), Breeze-GTK etc.
c) An alternative is to use whole themes for Firefox itself (install them like addons from the addons menu).
d) You get the developer edition's dark/light theme for free in Firefox, check it out, it looks quite good.

Now this is something to look at.
a) I'll stay with the default Debian Stable FF though
b) will go looking and see what they do - These are system wide themes right?
- - although doesn't answer my question: why did FF 52 behave properly in BL pre-Deuterium but not here.
c) more addons to slow things down ... BUT I may have to is there is no answer coming.

I may have no coice.

=== OFF TOPIC === But talked about above ===
=== Read but no further comments please ===
=== I will open new threads on these subjects ===
And: about this:

If so then it might have been a bigger jump for you. Some of those config files you copied in from "backup" might need tweaking before use.

That has been the whole fight ... not knowing about changes how do I know.

mostly in the way PA and compton were started up in ~/.config/openbox/autostart

And there lies the crux of my problem. My old BL install did not have PA and compton worked with ~/.config/compton/"with multiple configs" and my OB Menu entry for compton (Stealth) looks like this:

		<menu id="root-menu-5453" label="Stealth Control">
			<item label="Kill">
				<action name="Execute">
					<command>killall compton</command>
				</action>
			</item>
			<separator/>
			<item label="Run NoShadow">
				<action name="Execute">
					<command>compton --config ~/.config/compton/NS11.compton.conf</command>
				</action>
			</item>
			<item label="Edit NoShadow">
				<action name="Execute">
					<command>medit ~/.config/compton/NS11.compton.conf</command>
				</action>
			</item>
			<separator/>
			<item label="Run S11 Shadow">
				<action name="Execute">
					<command>compton --config ~/.config/compton/S11.compton.conf</command>
				</action>
			</item>
			<item label="Edit S11 Shadow">
				<action name="Execute">
					<command>medit ~/.config/compton/S11.compton.conf</command>
				</action>
			</item>
			<separator/>
			<item label="Run Has Fade2">
				<action name="Execute">
					<command>compton --config ~/.config/compton/Has.compton.conf</command>
				</action>
			</item>
			<item label="Edit Has Fade2">
				<action name="Execute">
					<command>medit ~/.config/compton/Has.compton.conf</command>
				</action>
			</item>
			<separator/>
			<item label="brex">
				<action name="Execute">
					<command>compton -cCG --paint-on-overlay -o 0.9 -r 30 -l -9 -t -9 -i 0.8 -e 0.75 -m 0.9</command>
				</action>
			</item>
			<item label="1 more">
				<action name="Execute">
					<command>compton -Gb -i 0.9</command>
				</action>
			</item>
			<item label="2 another">
				<action name="Execute">
					<command>compton -cC -G -b</command>
				</action>
			</item>
			<item label="Complex">
				<action name="Execute">
					<command>compton -cC -fF -I 0.065 -O 0.065 -D 6 -m 0.8 -G -b -i 0.5 -e 0.75</command>
				</action>
			</item>
		</menu>

I would sooner get rid of some things that the Bunsen "scripts" are doing and give the tweaking back to the user.

For example I found that just putting MY ~/.config/compton in Deuterium and calling my config in autostart:

compton --config ~/.config/compton/S11.compton.conf &

and the next reboot left me with a blank screen after logging in with just a mouse cursor. Go figure.

Putting "compton" in "/usr/lib/x86_64-linux-gnu/openbox-xdg-autostart" is a mistake IMHO and then starting it with:

bl-compositor --start

=== OFF TOPIC ===
=== Read but no further comments please ===
=== I will open new threads on these subjects ===

Sector11 · 2017-06-19 20:22:19

johnraff wrote:

If NVIDIA still doesn't work, maybe start a new thread on that topic?
Does the live system work OK?

NVIDIA HowTo coming to a thread near you soon, with all thanks to HoaS!

Live system works except for: no sound.

DeepDayze · 2017-06-19 20:37:18

Sector11 wrote:

johnraff wrote:
If NVIDIA still doesn't work, maybe start a new thread on that topic?
Does the live system work OK?
NVIDIA HowTo coming to a thread near you soon, with all thanks to HoaS!
Live system works except for: no sound.

Something must be flaky about your sound hardware to not make it work correctly even in the live environment.

johnraff · 2017-06-20 02:32:18

@S11 you requested no comments on the "off-topic" zone here, but I do have one or two comments/suggestions if you'd care to start new threads on those various issues.

Last edited by johnraff (2017-06-20 04:53:31)

Sector11 · 2017-06-20 03:53:20

Comments about the subject are welcome of course .. the other stuff is OT and I'll be opening a couple at least tomorrow since I'm off to be now, 00:52 here and a family gathering tomorrow.

#1 2017-06-17 23:49:10

FF not following theme

#2 2017-06-18 05:09:02

Re: FF not following theme

#3 2017-06-18 05:11:01

Re: FF not following theme

#4 2017-06-18 11:02:44

Re: FF not following theme

#5 2017-06-18 11:06:45

Re: FF not following theme

#6 2017-06-18 18:35:30

Re: FF not following theme

#7 2017-06-19 01:17:20

Re: FF not following theme

#8 2017-06-19 02:09:31

Re: FF not following theme

#9 2017-06-19 02:32:02

Re: FF not following theme

#10 2017-06-19 03:55:23

Re: FF not following theme

#11 2017-06-19 04:50:51

Re: FF not following theme

#12 2017-06-19 05:38:34

Re: FF not following theme

#13 2017-06-19 06:08:40

Re: FF not following theme

#14 2017-06-19 07:01:19

Re: FF not following theme

#15 2017-06-19 17:20:44

Re: FF not following theme

#16 2017-06-19 20:22:19

Re: FF not following theme

#17 2017-06-19 20:37:18

Re: FF not following theme

#18 2017-06-20 02:32:18

Re: FF not following theme

#19 2017-06-20 03:53:20

Re: FF not following theme

Board footer