LinuxMusicians

I'd rather set the associations manually than go messing with different FF PPAs.

Maybe this was already down on F's TODO list? Maybe its already fixed?

danboid wrote:I'd rather set the associations manually than go messing with different FF PPAs.

Than is maybe a good idea to disable "blue shell ppa" as well,because it will probably overwrite your manual settings at the time its version overrides the ubuntu version

falkTX wrote:I think it's awful how an opensource application doesn't support one of the most used DEs (KDE), eeek....
Using the blueshell PPA is the solution, but it doesn't always work. There's a time period when Firefox was just updated overriding the patched one. Forcing the version means we get stuck on an older FF, which kinda is a security issue...

I cannot guarantee the reliability of "ppa:alexey-ivanov/firefox-kde" but those versions successfully overrides the ubuntu ones....

PS:let's hope that Iceweasel doesn't has this issue, if you know what i mean

falkTX wrote:I guess I can add kuser, sure.

Thanks! User management is a pretty regular admin task, even for newbs so including a GUI for user mgmt makes sense for KX, even better if its linked under the KDE System Settings - that's where I'd expect to find it.

falkTX wrote:Regarding firefox, it's just like totalchaos says. I think it's awful how an opensource application doesn't support one of the most used DEs (KDE), eeek....
Using the blueshell PPA is the solution, but it doesn't always work. There's a time period when Firefox was just updated overriding the patched one. Forcing the version means we get stuck on an older FF, which kinda is a security issue...

It is a shame about its lack of KDE support, after all these years! As I understand it, most of the FF devs are Windows users and hence its Windows focused. I'd expect thats not the case for Chromium, as most Google devs run glibc-based, GNU/Linux apparently.

falkTX wrote: I think iceweasel is still on version 10, or close. Is that suppose to be security supported?
Anyway, we'll see about that later...

Actually iceweasel updates on "esr" releases. Right now they are on version 17esr. By the time (hopefully) we have KXStudio-Debian i guess it will be version 24esr

danboid wrote:As I understand it, most of the FF devs are Windows users and hence its Windows focused.

I don't want to start an argument here but Mozilla is the biggest supporter of free (as in freedom) internet. The primary target of Firefox is GNU/Linux and not MSWindows who is famous with not one or two campaigns against Firefox over the years.As for devs, most of the professional devs are windows users. It's just the way things are...

The plan was to release 12.04.2 this month , right F?

Is that still the plan? It'd be nice to have a brief status report. Maybe we're still waiting on the drivers?

Thanks!

EDIT

Have you patched the kernel for the USB audio prob people have been having under 3.8.x+? It got fixed, I heard, so I hope you spotted the patch as I'd have to hunt for it now if not?

falkTX wrote:I just need to think a bit more of what the structure of the repos should be in the long-term.
(for now there's "libs", "plugins", "apps" and "kxstudio" separate repos)

Maybe a testing/backports repo might be a good idea, so the user can choose if he prefers stability over bleeding edge and vise versa. Just a thought.

falkTX wrote:

danboid wrote:Have you patched the kernel for the USB audio prob people have been having under 3.8.x+? It got fixed, I heard, so I hope you spotted the patch as I'd have to hunt for it now if not?

I'm not sure, and I can't test it cause I don't have the hardware.
If you do, install this:

Code: Select all

sudo apt-get install linux-generic-lts-raring # installs 3.8-generic from raring

Reboot into 3.8-generic and report back
(really please, I have no possibility to check this bug for myself!)

I am having trouble accessing my mobile phone (via USB) with the current 3.8.0.26-lowlatency kernel, so i switch to linux-3.2
If this bug is related to the bug described above, i can test the behavior of the linux-generic-lts-raring right away.

falkTX wrote:

totalchaos wrote:I am having trouble accessing my mobile phone (via USB) with the current 3.8.0.26-lowlatency kernel, so i switch to linux-3.2
If this bug is related to the bug described above, i can test the behavior of the linux-generic-lts-raring right away.

Any testing is welcome. The lowlatency kernel used in kxstudio is exactly the same as the generic besides the timer config.

Nope, still not working on linux-3.8.0.27-generic
Maybe a 3.10 kernel might be a good idea, at some point in time? (although besides this problem in particular the 3.8 is acting great)

totalchaos wrote:(although besides this problem in particular the 3.8 is acting great)

Well, as I said in my other thread, I'm having trouble on new machine with alsa_in snd-aloop and a little glitchy with the zita option, and these troubles might be 3.8 related, I'm not sure. But I'll confirm that lots of things about 3.8 are excellent.

falkTX wrote: I think I'll have to switch back to the alsa-jack plugin option.
I got a kernel segfault while I was in debian 2 days ago, I had almost forgot how bad the 3.2 kernel handled it.

I'll try to see if I can make firefox work with it. Is youtube a case of audio not working with alsa-jack plugin?

I linked to a firefox bug in the other thread. It is an issue of HTML5. So YouTube has an opt-in for html5 via youtube.com/html5 and then sound won't work, opt-out again and use Flash, it will work, but other sites use html5, and html5 is great and is the future…

I think this is a case where kernel has issues with snd-aloop (not even certain there) and Firefox with HTML5 has issues with alsa-jack plugin, and it is hard to know where the blame lies.

wolftune wrote:

falkTX wrote: I think I'll have to switch back to the alsa-jack plugin option.
I got a kernel segfault while I was in debian 2 days ago, I had almost forgot how bad the 3.2 kernel handled it.

I'll try to see if I can make firefox work with it. Is youtube a case of audio not working with alsa-jack plugin?

I linked to a firefox bug in the other thread. It is an issue of HTML5. So YouTube has an opt-in for html5 via youtube.com/html5 and then sound won't work, opt-out again and use Flash, it will work, but other sites use html5, and html5 is great and is the future…

I think this is a case where kernel has issues with snd-aloop (not even certain there) and Firefox with HTML5 has issues with alsa-jack plugin, and it is hard to know where the blame lies.

I don't have any trouble with snd-aloop but i noticed that Linux-3.8 treats my soundcard differently comparing to Linux-3.2. 3.8 sees 2 output channels by default, while Linux 3.2 sees 6 output channels by default. In both cases i can switch the number of channels from the alsamixer. The difference is that when i'm using 2 channels i cannot use buffer size below 128, but the gui's looks cleaner and there is no danger some programs (like Yoshimi) to auto-connect to all 6 channels. But when using 6 channels i can successfully use buffer size of 32. Note that this is not KXStudio specific behavior, but a general one.
As for Firefox html5 issue it is exactly like Wolfune said above

(Hate to admit it, but) Chromium deserves more than Firefox to be the default KXStudio browser. I haven't used Chromium from long time ago but in the past hours i discovered 4 powerful reasons for Chromium to become KXStudio default:

0. Doesn't have this issue with html5 and jack (it seems that Firefox is the only web browser that has it)
1. If using chromium-codecs-ffmpeg-extra there is less need of using adobe-flashplugin, if not at all
2. Chromium has no problem with dark skin themes
3. no KDE compatibility issues (that i have seen)

I think those points are compelling, but I still am invested in Firefox more and strongly support Mozilla as a true ethical and honorable organization compared to Google. It is easy enough to install Chromium, of course. And both are under heavy ongoing development. Of course, we do need a functional system out of the box which works for audio especially… I'm hoping this all gets solved one way or another. I am optimistic.

Given the valid points about Chromium, I won't complain too loudly if it were made the default in KXStudio for now.

falkTX wrote:Is there any true solid reason to keep relying on firefox instead of chromium?

I think that some of the issues raised about Ubuntu/Canonical apply to Chromium/Google. Firefox is more like Debian. Ubuntu's polish and benefits are not unlike Chromium's and yet Debian and Firefox are the more community-oriented, more ethical, and perhaps the better long-term allies. In both cases it is a tough decision, and not all aspects are comparable. I'm sure you could find some technical reasons to favor Firefox also. But it's not the same upstream/downstream simple solution… I'll let others add their thoughts about the advantages to Firefox (and hope they do), but I'm open to being convinced otherwise although I deeply respect Mozilla in general sense.

i also tried Midori (from ppa:midori) and even Epiphany (Web - the gnome browser). They are both working fine, both connecting with alsa->jack plugin and both have html5/h264 support. So now i'm really questioning mozilla's user oriented policy??????

F:

OK - I'll try that kernel soon if not today. Will let you know.

As for Chromium VS FF - there is no real comparison in my mind. Chromium/Chrome always has been a buggy wreck of an an app - I cannot rely on it. Yes, I appreciate it loads and may render some pages faster than FF and that FF has a few flaws but I always prefer stability over speed and thats why I use FF.

FF is of course the original browser as it can be traced back to Mosaic / Netscape Navigator. Google have this obsession with trying to add as many features into their browser as fast as possible and thats why its so buggy. I was annoyed that Mozilla started copying them to a degree by starting to release a new version every month or so but thankfully it hasn't had the effect of making FF as unreliable as chromium/chrome.

Chromium = "Your browser has crashed" icon, for me! I also hate that its so easy to accidentally close a Chromium window containing multiple tabs. Confirmation would be nice before I lose all my work!

The other browser alternatives really aren't worth bothering with - none have the same extensive plugin library available under FF nor the dev. manpower to compete with FF.