On Sun, 15 Feb 2009 15:46:45 - Peter Pugh-Jones
wrote:
>Hi Janitor,
>
>Are you saying we should downgrade the kdebase-workspace version to an
>older version for everything to wrk properly?
>
>Currently I appear to have the following installed:
>
>kdebase-workspace-bin: 4.2.0-0ubuntu1~intrepid
Yes. Separate bug for the crash please.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b..
All of which confirms it works far better than it did before. I think
these new issues now that it works at all should be filed as new bugs.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubunt
The package in intrepid-proposed is missing a depends on
obex-data-server. Install that. A fix upload is pending.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscrib
I've apparently managed to break it already. I was attempting to pair it
with my cellphone when the "kbluetooth4-devicemanager" crashed. It now
refuses to open with the following output:
kbluetooth4-devicemanager(8445)
Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
kblue
This is significantly better than before and IIRC about where we were
before the switch to bluez 4.
On Thu, 22 Jan 2009 18:01:42 - mfabry wrote:
>I've just installed latest Intrepid packages (KDE 4.1.4). I was able to
pair devices (handheld and mobile) with my desktop. Unfortunately that's
On Thursday 22 January 2009 11:56, Michael Marley wrote:
> I just checked, and it is FTBFS for AMD64:
Due to build timing it built against the old version of kdebase-workspace.
I've just retried it.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You receiv
On Thursday 22 January 2009 10:33, Michael Marley wrote:
> The fixed kdeworkspace packages are installed, but kbluetooth is still
> version 0.1, and it will not start. It just crashes complaining about
> DBUS like it always did.
kdebluetooth_0.3-0ubuntu0.1 is in the archive and published.
--
so
I just updated my packaged for intrepid w/ kde 4.2rc1 and got the app
upgrade, seems to be working, I will try to pair it with something later to
see if it's fully functional.
On Thu, Jan 22, 2009 at 10:48 AM, Scott Kitterman
wrote:
> The ones you want are version 4.1.4-0ubuntu1~intrepid3. They
The ones you want are version 4.1.4-0ubuntu1~intrepid3. They are there.
Perhaps not on your mirror yet.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdeba
The fixes are already in Jaunty. It should work.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kubuntu-bugs mailing list
ku
I am guessing these won't make it into kde 4.2 until the official
release?
On Thu, Jan 22, 2009 at 7:54 AM, Scott Kitterman
wrote:
> It's automatically built. The amd64 buildds are just running a bit
> behind.
>
> --
> solid-bluetooth needs update for bluez 4.x
> https://bugs.launchpad.net/bugs/
It's automatically built. The amd64 buildds are just running a bit
behind.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
ku
There are patches needed for kdebase-workspace. We have the patches for
both 4.1 and 4.2 and are working on an update.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
Bugs, which is subsc
Tried compiling it this morning for intrepid + kde 4.2rc1 and came up with
this:
[ 3%] Building CXX object src/CMakeFiles/kbluetooth4.dir/agent/agent.o
/home/srelysian/kbluetooth4/src/agent/agent.cpp: In member function 'void
Agent::Authorize(QDBusObjectPath, const QString&)':
/home/srelysian/kbl
vsuarez ha escrito:
> Jajajaja, no jodas Israel, ¡tú por aquí!
Tio este puñetero bug, clama al cielo, me das ganas de gnome
simplemente por esta chorrada, y otras como que el kmail no ordena
bien los correos y
>
> On Fri, Jan 16, 2009 at 12:58 PM, kamaxeon wrote:
>
>> Me too
>>
>> SRE
Jajajaja, no jodas Israel, ¡tú por aquí!
On Fri, Jan 16, 2009 at 12:58 PM, kamaxeon wrote:
> Me too
>
> SRElysian ha escrito:
>
> > You have my (20) vote(s). Hopefully this will change the priority a
> > little.
> >
> > On Fri, Jan 16, 2009 at 8:40 AM, frapell wrote:
> >
> >> @Niels Ganser:
>
Me too
SRElysian ha escrito:
> You have my (20) vote(s). Hopefully this will change the priority a
> little.
>
> On Fri, Jan 16, 2009 at 8:40 AM, frapell wrote:
>
>> @Niels Ganser:
>> Yes, that was the answer i was referring to... forgot to add a link there,
>> heh...
>> The mail i sent him was
You have my (20) vote(s). Hopefully this will change the priority a
little.
On Fri, Jan 16, 2009 at 8:40 AM, frapell wrote:
> @Niels Ganser:
> Yes, that was the answer i was referring to... forgot to add a link there,
> heh...
> The mail i sent him was asking how to start, if i should read somet
On Fri, 16 Jan 2009 13:00:01 - Niels Ganser wrote:
>frapell: It's great that you want to assist in fixing this! You will
>probably have more success offering your help in
>https://bugs.kde.org/show_bug.cgi?id=172267 though, as this essentially
>is a KDE bug. In https://bugs.kde.org/show_bug.cg
I am actually using KDE 4.2rc1 right now. Unless it sneaks in under the
radar at the last minute official release (which should be due by the end of
this month), it's doubtful it will make it in. I do understand that they are
all working hard, and I was a bit rude about it so I appologize. Just see
The more I think on this, the more it aggravates me. I was scrolling through
the posts earlier to see if any of the dev's have even spoken up about it,
and I came across something to the effect of "not having time to fix it".
This isn't some obscure mouse that for some reason doesn't work, it's an
Less glitter and more stable is available in Hardy if you want it. The
bluetooth issue isn't something any Kubuntu developer could control.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Kubuntu
I've been working directly with Tom Patzig (although the two weeks or so
i've been ill and out of the loop)
On Tue, Nov 11, 2008 at 09:05, Harald Sitter
<[EMAIL PROTECTED]>wrote:
> ** Also affects: kdebase via
> http://bugs.kde.org/show_bug.cgi?id=172267
> Importance: Unknown
> Status:
Perhaps, but not in the time we have until the archive closes. Release notes
is really all we can do.
--
solid-bluetooth needs update for bluez 4.x
https://bugs.launchpad.net/bugs/280997
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kevin Christmas wrote:
> 2. I don't know if there's more configuration settings somewhere else,
> but the gnome bluetooth-applet is painful. I have to constantly remove,
> search, and then re-add my mouse.
I don't think that is bluetooth-applet's fault. It is bug #249448 that
you hit.
--
solid
At this point there really isn't a great answer for bluetooth and
Kubuntu.
Complaints that us developers aren't doing our 'job' - I'm a volunteer and so
are virtually all the developers working on Kubuntu just demotivate me, so no
apologies for the reaction.
For the release, the choices are no
OK. That's good to know.
We really can't put the gnome stuff on the CD and automatically install it
because there would be no way to undo that once we have a working KDE
bluetooth for intrepid-updates. This does, however, seem worthy of a mention
in the release notes.
Would one of you who ha
1. The problem is not that Kubuntu devs were too busy making things shiny
they forgot to do core work. The problem is that bluez 3 was seriously
broken with our current kernel (input devices of any kind would not work)
and yet KDE upstream had not yet updated to work with bluez4. There really
I spoke with the upstream developer, and at this point he does not have the
time to put towards porting to 4.x. I've started to do the port myself, but
the changes are quite large and i'm very familiar with the coding style.
You can see where they're at from revisions 10+ at this br branch:
https:
30 matches
Mail list logo
