gmane.linux.ubuntu.devel.kubuntu

Kubuntu Council Elections 2012

Harald Sitter — 2012-05-25T20:52:06

The Kubuntu Council is a group of 6 Kubuntu Members who get to vote on
membership of Kubuntu Members and occasionally other decisions regarding
Kubuntu.

Half the council is nearing the end of their 2 year appointment so we need
to hold elections for the open positions to the council.  This could be
you! If you are a Kubuntu Member and are willing to turn up to Kubuntu
meetings as much as possible for the next couple of years do consider
putting your name forward.

We are particularly encouraging non-developers to put their name forward,
as we feel that a less development focused council is beneficial for
the Kubuntu community.

To put your name forward make sure you update your wiki page and then post
to this list.

To nominate someone else also write to this list. It might be a good idea
to first have a chat with the affected person. Please note that everyone
who was nominated by someone else will have to verify their nomination.

Closing date for nominations is June 9 at 23:59 UTC.

The poll will start on June 10. Voting instructions will be sent to
members of the kubuntu-members team with public email addresses on
Launchpad directly. If you do not have a public email address in Launchpad
and wish to vote, email me privately with the address you'd like used you
will get a ballot as well.

regards,
Harald for the Kubuntu Council

Kubuntu Council Status/Elections

Scott Kitterman — 2012-05-25T19:46:07

Getting elections set up has taken longer than we thought, so rather than lose 
half the council membership this week, the KC has decided the existing members 
whose terms are about to expire should be extended three weeks to give time to 
prepare an election.

People who've considered running for Kubuntu Council in the past should be 
considering it again.  It is mosts certainly not just for developers.  Any 
Kubuntu member is eligible to run.

Scott K

P.S. On that note, I'd appreciate it if someone who's subscribed to the user 
list would forward this there.

Overview of Jockey replacement; options for Kubuntu?

Martin Pitt — 2012-05-25T09:12:05

Hello all,

Also sending this to kubuntu-devel< at >, but as I'm not a subscriber
someone needs to moderate; CC'ing Scott and Harald directly.

As discussed at UDS and in [1] we want to dramatically simplify the
machinery for installing extra drivers (NVidia, bcmwl, and friends).
Jockey was originally designed to do a lot more than we are using it
for, and be compatible with other distros as well (I had it working on
Fedora 14 back then, when we discussed it in the Linux Foundation
driver backports workgroup). But we don't use it to that extent, other
distros have moved into a different direction, and thus it has way too
much code and bugs. So Ubuntu will drop it and replace with with
something much simpler and robust, and also use upstream friendly APIs
(PackageKit).

The logic of detecting drivers and providing PackageKit/aptdaemon
plugins is now in the ubuntu-drivers-common package (formerly known
as "nvidia-common"). This now mostly makes PackageKit/aptdaemon able
to answer a "WhatProvides(MODALIAS, pci:s0000DEADv0000BEEF...)" query
to map a piece of hardware to a driver package. It also contains a
command line tool "ubuntu-drivers" with a few commands (list,
autoinstall, and debug at the moment) which replaces jockey's usage in
the installer (which called jockey-text --no-dbus ...).

The user interface will be made a lot simpler and less confusing, and
move into software-properties-gtk (or perhaps software-center at some
point).

The question arises what to do with Kubuntu. We have a few obvious
options:

* Kubuntu uses software-properties-kde, so as long as we keep
software-properties, the new design could be implemented there as
well, and jockey-kde be dropped.

* Kubuntu implements a similar (or their own) design using the
ubuntu-drivers-common API in the KDE control center as an embedded
tab. Then we can also drop jockey-kde.

* Kubuntu keeps jockey-kde, and takes over the Jockey maintenance.
ubuntu-drivers-common does not break Jockey, but it would still
need some maintenance to adapt to newer nvidia driver versions,
changing Qt/KDE APIs, and the like.

* Kubuntu keeps the jockey-kde UI, but drops the backend
(jockey-common) and changes the UI to work with the
ubuntu-drivers-common API.

In either case, automatic driver installation by Ubiquity will Just
Work (e. g. for the Broadcom wifi cards) but there should still be an
UI for enabling or changing drivers (like NVidia, which is not
auto-installed) manually.

Opinions?

Thanks,

Martin

[1] https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-third-party-driver-installation

[Blueprint topic-quantal-flavor-kubuntu] Kubuntu Quantal PLans

Kate Stewart — 2012-05-24T22:49:39

Blueprint changed by Kate Stewart:

    Approver: Kate Stewart => Kubuntu Council

SRU xsettings-kde

Harald Sitter — 2012-05-24T20:43:57

Someone please make
https://bugs.launchpad.net/ubuntu/+source/xsettings-kde/+bug/1002811
so that it meets with ludicrous requirements. I will not. Kthxbai.

Kubuntu and main/universe

Colin Watson — 2012-05-23T11:49:54

Hi Kubuntu folks,

At this UDS, the old "archive reorg" topic came up again
(https://wiki.ubuntu.com/ArchiveReorganisation for those unfamiliar with
it; this page also contains some background for some of the Ubuntu
archive jargon I've inevitably ended up using in this post), and I had a
side discussion with Jonathan about a Kubuntu-related question arising
from it.

Ultimately, I still do plan to move all free software in the archive to
a single consolidated "main" component and express who supports what in
ways that are rather more flexible than (effectively) moving files
around in the pool; but it's clear at this point that I'm only going to
be able to lay the groundwork for that this cycle, not actually do it.
In advance of that, though, my question is as follows: is being in main
actually much more than an obstruction to Kubuntu development these
days?

Up to now, the packages that make up Kubuntu - at least the images you
ship - have been in main at least in part because Canonical was offering
some level of support for them, and thus we wanted to make sure they
passed an explicit review by our security team and the like.  Now that
that isn't the case, though, being in main basically means that
Canonical is requiring main inclusion review for Kubuntu even though we
aren't offering support for it, out of step with all other community
flavours, and thus imposing an extra chunk of work on you that nobody
else has to do.  That seems rather unfair!  When I spoke to him at UDS,
Jonathan seemed to feel the same way, and indicated that you might well
want to consider moving Kubuntu-specific packages to universe.

Now, this is one particular way to look at things, and I realise that
you could cast the question differently.  Since the main component has
that extra level of review associated with it and has a more restricted
uploader group, many people do regard it as having an extra claim of
quality.  I don't want to be the guy "kicking Kubuntu out of main"; if
we make this change in advance of a more sweeping archive
reorganisation, I'd much rather do it with your consent and indeed
enthusiasm.  My conversation with Jonathan suggested that this might
well be forthcoming, but I said I'd mail kubuntu-devel to see what other
people think.

Some other details:

 * What effect would such a change have on upgrades?  update-manager
   shows a "no longer supported by Canonical" message for installed
   packages that have been moved from main to universe between releases;
   does muon have anything like this?  I don't want to scare off Kubuntu
   users.

 * Moving to universe would imply not using language packs any more,
   because uploads to universe don't have translations stripped out and
   sent through the Launchpad translations system.  Jonathan suggested
   that this would be a desirable change for Kubuntu, but I expect that
   at the very least it would be a respectable chunk of work for
   somebody to unwind all of that infrastructure.  (As an aside, we'll
   need to think about how this would work post-archive-reorg if more or
   less everything ends up in main.)

 * A number of Kubuntu-specific packages would need to stay in main for
   transitive-closure reasons: source packages in main that, for
   example, build bindings for both GTKish and Qtish worlds will
   generally build-depend on both, which will cause those
   build-dependencies to stay in main along with all their
   (build-)dependencies.  I don't want to encourage people to start
   splitting source packages for the sake of this, so a number of base
   packages would stay in main regardless.  Still, lots of UI packages
   would be able to drop out to a component with less restrictive
   processes.

   I've attached a file showing a first pass at what the results would
   have been if we'd done this for 12.04.

 * Are there any effects on mirroring that you care about?  Right now,
   it's in principle possible to run an archive mirror useful to Kubuntu
   users with only main (and maybe restricted).  This change would mean
   you'd have to have universe as well.  On the other hand, Xubuntu et
   al have this problem today anyway, and maybe you only care about
   things like the major per-country mirror network which carries
   everything.

 * Would there be any "soft" questions of PR and the like that would
   need to be addressed?

Thanks,

[greenrd< at >gmail.com: Bug report: Mailing list reject message isunfriendly]

Jonathan Riddell — 2012-05-23T11:23:00

----- Forwarded message from Robin Green <greenrd< at >gmail.com> -----

Date: Wed, 23 May 2012 12:19:59 +0100
Subject: Bug report: Mailing list reject message is unfriendly
From: Robin Green <greenrd< at >gmail.com>
To: kubuntu-devel-owner< at >lists.ubuntu.com
Sender: mailman-bounces< at >lists.ubuntu.com

   I am very annoyed because kcrashhandler told me to report a bug in
   apport-kde by email to kubuntu-devel< at >lists.ubuntu.com. But YOU CAN'T
   because YOU GET THE MESSAGE "You are not allowed to post to this mailing
   list, and your message has
   been automatically rejected. "
   This is not at all user-friendly.
   This was the end of a long list of crashes and incorrect behaviours that I
   ran into while trying to report a bug. The user experience needs to be
   improved.

[Blueprint topic-quantal-flavor-kubuntu] Kubuntu Quantal PLans

Kate Stewart — 2012-05-23T02:14:26

Blueprint changed by Kate Stewart:

    Definition Status: Drafting => Approved

[Blueprint topic-quantal-flavor-kubuntu] Kubuntu Quantal PLans

Kate Stewart — 2012-05-23T02:14:15

Blueprint changed by Kate Stewart:

    Definition Status: New => Drafting

[Blueprint topic-quantal-flavor-kubuntu] Kubuntu Quantal PLans

Kate Stewart — 2012-05-23T02:14:02

Blueprint changed by Kate Stewart:

    Priority: Undefined => Medium

Fwd: Automatic crash report generated by DrKonqi for Apport KDE.

2012-05-21T09:30:43

----- Forwarded message from Dennis Schridde <devurandom< at >gmx.net> -----

From: Dennis Schridde <devurandom< at >gmx.net>
To: kubuntu-devel-owner< at >lists.ubuntu.com
Subject: Fwd: Automatic crash report generated by DrKonqi for Apport KDE.
Date: Mon, 14 May 2012 12:58:19 +0200
Sender: mailman-bounces< at >lists.ubuntu.com

Hello Kubuntu developers!

Apport crashed and started DrKonqi, which then wanted me to send an email to 
the kubuntu-devel mailinglist. This was not possible, because the mailinglist 
is write protected.

--Dennis
Content-Description: kubuntu-devel-owner< at >lists.ubuntu.com: Re: Automatic crash report generated by DrKonqi for Apport KDE.
Subject: Re: Automatic crash report generated by DrKonqi for Apport KDE.
From: kubuntu-devel-owner< at >lists.ubuntu.com
To: devurandom< at >gmx.net
Date: Mon, 14 May 2012 10:04:15 +0000
Sender: kubuntu-devel-bounces< at >lists.ubuntu.com

You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
kubuntu-devel-owner< at >lists.ubuntu.com.

From: Dennis Schridde <devurandom< at >gmx.net>
To: kubuntu-devel< at >lists.ubuntu.com
Subject: Re: Automatic crash report generated by DrKonqi for Apport KDE.
Date: Mon, 14 May 2012 12:04:09 +0200

Am Montag, 14. Mai 2012, 12:00:26 schrieben Sie:
Console output was:
python: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
KCrash: Application '' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit

Content-Description: kubuntu-devel-owner< at >lists.ubuntu.com: Automatic crash report generated by DrKonqi for Apport KDE.
Subject: Automatic crash report generated by DrKonqi for Apport KDE.
From: kubuntu-devel-owner< at >lists.ubuntu.com
To: devurandom< at >gmx.net
Date: Mon, 14 May 2012 10:00:51 +0000
Sender: kubuntu-devel-bounces< at >lists.ubuntu.com

You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
kubuntu-devel-owner< at >lists.ubuntu.com.

From: Dennis Schridde <devurandom< at >gmx.net>
To: kubuntu-devel< at >lists.ubuntu.com
Subject: Automatic crash report generated by DrKonqi for Apport KDE.
Date: Mon, 14 May 2012 12:00:26 +0200

Application: python2 (1.0)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic-pae i686
Distribution: Ubuntu 12.04 LTS

libglew1.5

Micah Gersten — 2012-05-20T07:48:03

Would it be possible to transition avogadro, calligra, and kalzium to
glew 1.7?

After the kubuntu packages are transitioned I plan to have the dev
package and source removed again so that we can transition the rest to
glew 1.7 without debian/control changes.

Thanks,
Micah

Some words on Muon Update Manager

Valter Mura — 2012-05-19T07:38:31

Hi

I noticed some things while using MUM:

- every time I click on item to update, a panel for description opens in 
the bottom, appears nothing but the suggestion to visit Launchpad. In 
Muon Package Manager it appears correctly.

- in the right bottom of the window (or where you want) I would like to 
see the calculation how much space will be occupied or saved by the 
installation/update. I remember I can see it in MPM

- I would like to see, while installing, the operations performed by the 
programs. I cannot see them but before I could.

Should I open a bug for these few things?

Thanks and regards,

Looking to contribute

Jayson Rowe — 2012-05-18T03:08:47

Good Evening,
I've been lurking as a Kubuntu user since 5.04 first hit, and I'm
interested in getting involved and contributing back. Looking for any
areas where I may be able to help.

I'm a SysAdmin/NetAdmin by trade, also do some development (Python,
Ruby, and even .NET). I'm willing to learn packaging or anything else.
I've followed the packaging guide, and I think I have everything set
up, including pbuilder setup for Precise, Oneiric, Natty and Lucid.

I also try to lurk in IRC and help out when I have time (I'm jaysonr
on Freenode). Interested in any advice to get me started.

My Launchpad profile is here: https://launchpad.net/~jayson.rowe


Thanks!

--
-jayson

Work Items

Jonathan Riddell — 2012-05-15T12:03:00

I've typed up the work items as discussed at UDS.  Please edit any mistakes or missing items.

David will organise the council elections soon and after we have a new kubuntu council elected we can have a meeting to approve the work items.

https://blueprints.launchpad.net/sprints/uds-q?searchtext=kubuntu

Jonathan

kdesudo and the config problem

Harald Sitter — 2012-05-12T16:15:20

lo'

https://bugs.launchpad.net/ubuntu/+source/kdesudo-kde4/+bug/632503

Let me quickly outline how user (kde) configuration work with kdesudo.
They do not.
The entire idea is that kdesudo makes applications use the target
users home rather than the invokees. otherwise running `kdesudo kate`
would write a config that is only writable/readable by root into the
users home making kate when invoked the regular way unable to save
data.
But! KDE software also stores theming data in config files (widget
style, fonts, colors ...) which then leads to inconsistent appearance
of applications running using kdesudo. Incidentally enough that is why
one is supposed to use gksu/kdesudo with gui apps ;).

This is a long standing complaint with users of kdesudo and AFAIK we
never actually discussed what we want to (not) do about it. Suppose it
is time ;)

You might be able to imagine that since the problem is caused by the
very core idea of kdesudo working around it would be a right pain in
the booty. In particular applications/kdelibs needs to have a runtime
theme override (runtime being data that is already in memory, for
example as envrionment variables). I reckon GTK3 has the very same
thing with theme configs being stored in X11 from what I understand.
Since I don't see Qt/KDE moving to an X11 bound way of defining the
theme (portability and whatnot) the only way to achieve this would be
to define other means for settings transfer (e.g. dbus) coming with
equally invasive code changes. This however also affects kdesu and
thus all that rubbish can be done upstream.

The question is whether that is even worth thinking about.

I for one do not think so, particularly since running most apps using
kdesudo is a bad idea to begin with. Also one would have to define
where to draw the line, because I can totally imagine people asking
for kdesudo kate to use the settings of the user adding a whole new
layer of problems. Should an app really need to run as root the app
developer can probably make theme transfer work individually (e.g.
have a host app that exports the data via dbus and invoke kdesu(do)
from that host app, the rootified app then reads the data from dbus).

Thoughts?

HS

the circle that was no circle

Harald Sitter — 2012-05-12T15:34:00

https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/981898

it turns out our logo is not actually forming a circle (supposedly
because of weird stroke corner handling in inkscape). if someone would
work the inkscape magic and fix that it would be really great :)

HS

re

ΓΙΩΡΓΟΣ ΠΑΤΡΟΥΔΑΚΗΣ — 2012-05-08T13:11:34

firefox-kde-support

Mark Fraser — 2012-05-06T20:13:58

I have just upgraded my first computer to 12.04 and I noticed that the package 
firefox-kde-support is no longer available to install. From what I've read on 
the forums, this seems to be due to Canonical no longer sponsoring Kubuntu.

If this is the case, could it not be moved to universe or multiverse instead?

PPPoE not working in Precise

Ovidiu-Florin Bogdan — 2012-05-04T14:06:38

Hello everybody,

I'm new in Kubuntu Testing, and I don't quite know yet all the steps I have
to take, but I think I've found a bug in Precise (Kubuntu 12.04).
I have a fresh installation on an MSI laptop, and I cannot connect it to a
PPPoE network. All the details are added just like I did on 11.10, but it
fails to connect.

It starts the connection, but after about 2 minutes of waiting it fails to
connect.

The hardware has no problems, neither does the connection; it works
flawlessly on Windows.

How can I generate a report for this issue?

Sincerely,
*Ovidiu - Florin Bogdan*
***mob: +40 743-135.018 _*
***I enjoy the massacre of ads. This sentence will slaughter ads without a
messy bloodbath.*
http://www.google.com/profiles/ovidiu.b13

Making folderview as default for all new users

Flavio Moringa — 2012-05-04T13:15:40

I guys,

maybe you can help me out here.

In Kubuntu 11.10 I managed to configure
/usr/share/kubuntu-default-settings/kde4-profile/default/share/config/plasma-desktop-appletsrc
so that all the users I created had as default the "folderview" layout and
not the upstream "Desktop" layout, as also have the widgets locked by
default...

It was relatively easy to do... I just configured a user the way I liked
it, an then copied it's plasma-desktop-appletsrc (without the geometry
entries) to
/usr/share/kubuntu-default-settings/kde4-profile/default/share/config/...

But in 12.04 it doesn't work... it doesn't do anything... it's like the
file isn't even there....

What changed? Any thoughts or help? Any other way to do this?

Thanks a lot

Your's trully