Kubuntu 14.04 LTS Schedule, Plans,...

[Rog132]

Linking to https://www.kubuntuforums.net/showth...Schedule-Plans

[MoonRise]

Thanks for the info on Rekonq!

[geoaraujo]

Default browser

The default is the Firefox: https://lists.ubuntu.com/archives/ku...er/007591.html

[wrender]

Hopefully the default firefox install will be the one from the blue shell ppa!

[SteveRiley]

Hopefully the default firefox install will be the one from the blue shell ppa!

It probably won't be. The BlueShell PPA lags official releases by a few days, which is not good for security.

[life0riley]

What are the benefits of having Firefox from the Blue Shell PPA? I installed that in a raring VirtualBox guest and couldn't tell the difference.

[Snowhog]

My (limited) understanding is that Firefox from Blue Shell is better integrated with KDE.

[life0riley]

My (limited) understanding is that Firefox from Blue Shell is better integrated with KDE.

I tried to see that when I installed it. Maybe I didn't know what I was looking for.

[wrender]

There is no point making it the default browser if the blue shell KDE integrated version isn't used. It establishes proper MIME types to be used with the system and also knows to use the kde file browser when viewing/opening/saving files. Everytime you click on an attachment or open something from the internet becomes a hassle and lame. Who cares if your browser takes a few days to update it is better than having a browser that doesn't know how to function with the system.

[SteveRiley]

There is very little choice right now.

Rekonq is too unstable right now. It relies on the Qt 4.x version of QtWebKit, which is unmaintained. The Qt 5 version isn't really any better. The Qt 5 WebKit library based on webkit2 will be discontinued after Qt 5.2. The future is QtWebEngine, based on Blink (Chromium), but won't be ready until Qt 5.4. So, unfortunately, the state of KDE-native web browsers is rather flat at the moment. (More info.)

Konqueror is unmaintained (sadly).

Who cares if your browser takes a few days to update it is better than having a browser that doesn't know how to function with the system.

You would care if a zero-day vulnerability were discovered and the main repository is immediately updated, while Blue Shell's PPA may not compile for a few days.

[claydoh]

As we can't really have 2 Firefox packages in the Ubuntu repos, I wonder if just the mime types could be integrated into a Kubuntu-specific package, say kubuntu-default-settings or similar. I don't think that itself would require a separate compilation of Firefox, like the KDE integration does. Or would it?

Sent from my DNA using Tapatalk, like that really matters

[SteveRiley]

Not sure. Rohan seems to be the caretaker of the PPA, he might have some ideas.

Interestingly, Chromium -- without any modifications -- uses the KDE dialogs. I suppose it also sets the MIME types appropriately; I haven't checked. I wonder if it might make more sense for this to be Kubuntu's default rather than Firefox? I wonder what ScottK would think about that...

Edit: on my machine, Chromium uses the KDE dialogs. Elsewhere on the forum, we have a report of Chromium using the Gtk+ file picker. Not sure what to think about that.

[claydoh]

Not sure. Rohan seems to be the caretaker of the PPA, he might have some ideas.

Interestingly, Chromium -- without any modifications -- uses the KDE dialogs. I suppose it also sets the MIME types appropriately; I haven't checked. I wonder if it might make more sense for this to be Kubuntu's default rather than Firefox? I wonder what ScottK would think about that...

Hah!

I think Chromium would have to be better or rather more regularly maintained in Ubuntu (if it isn't nowadays)

[SteveRiley]

Fully updated Saucy:

steve@t520:~$ [B]apt-cache policy chromium-browser[/B]
chromium-browser:
  Installed: 31.0.1650.63-0ubuntu0.13.10.1~20131204.1
  Candidate: 31.0.1650.63-0ubuntu0.13.10.1~20131204.1
  Version table:
 *** 31.0.1650.63-0ubuntu0.13.10.1~20131204.1 0
        500 http://mirror.pnl.gov/ubuntu/ saucy-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ saucy-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     29.0.1547.65-0ubuntu2 0
        500 http://mirror.pnl.gov/ubuntu/ saucy/universe amd64 Packages

Chromium calendar: http://www.chromium.org/developers/calendar
Looks like v.32 has been out for nearly two months and it hasn't made its way into *buntu yet.

Meanwhile, v.33 and v.34 have been tagged and can be built right now, if you want:
http://src.chromium.org/viewvc/chrome/releases/

Curiously, even Arch is still only at v.31:
https://www.archlinux.org/packages/?sort=&q=chromium

Gentoo, meanwhile, has ebuilds for v.32 and v.33, but they're masked:
http://packages.gentoo.org/package/www-client/chromium

I wonder if maybe it isn't so much that *buntu is behind, but instead there's something wonky with v.32 and v.33?

[MoonRise]

Glad I don't have to make that call so close to RD.