How/Do I report these?

[Nasa]

Ok,

requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).

1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?


2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...


3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.


I know, I'm pushing my luck -- so I will stop here.


Nasa

[Clark, Joel]

I suggest report 1) against the music app.

For 2) you are on untested ground working with QT/QML and the mesa drivers. The MeeGo devices that depend on the Mesa drivers have only been tested with a GTK/Clutter based UX. Sounds like either a QT or Mesa issue.

3)?

regards
Joel



-----Original Message-----
From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-***@public.gmane.org] On Behalf Of Nasa
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?

Ok,

requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).

1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?


2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...


3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.


I know, I'm pushing my luck -- so I will stop here.


Nasa

[Nasa]

Joel,

Should I create a bug report for #2? And should it be 2 bugs?
One for the navit issue and one for lack of testing of the mesa
drivers? It would seem that the drivers would need to be good to
go if meego compliance is going to be enforced (ie: if an app is
written against core, it should work with everything, right?).

Nasa

----- Original Message -----

Post by Clark, Joel
I suggest report 1) against the music app.
For 2) you are on untested ground working with QT/QML and the mesa
drivers. The MeeGo devices that depend on the Mesa drivers have only
been tested with a GTK/Clutter based UX. Sounds like either a QT or
Mesa issue.
3)?
regards
Joel
-----Original Message-----
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?
Ok,
requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).
1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?
2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...
3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.
I know, I'm pushing my luck -- so I will stop here.
Nasa
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Clark, Joel]

I doubt there is a Navit issue. My guess is the issue is between QT and the graphics driver you are using. You can file a bug but it may be difficult to find someone willing to debug a stack with all thee components Navit, QT and your graphics. I know from experience the QT guys will ask for a simple test case that reproduces the problem without depending on "MeeGo apps". The project teams that I know of that use the Mesa drivers are not using QT.

Can you just switch to using Navit with GTK?

Regards
Joel

Post by Nasa
Joel,
Should I create a bug report for #2? And should it be 2 bugs?
One for the navit issue and one for lack of testing of the mesa
drivers? It would seem that the drivers would need to be good to
go if meego compliance is going to be enforced (ie: if an app is
written against core, it should work with everything, right?).
Nasa
----- Original Message -----

Post by Clark, Joel
I suggest report 1) against the music app.
For 2) you are on untested ground working with QT/QML and the mesa
drivers. The MeeGo devices that depend on the Mesa drivers have only
been tested with a GTK/Clutter based UX. Sounds like either a QT or
Mesa issue.
3)?
regards
Joel
-----Original Message-----
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?
Ok,
requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).
1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?
2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...
3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.
I know, I'm pushing my luck -- so I will stop here.
Nasa
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Nasa]

As it turns out, the reason I hadn't noted the problem before is
that I have been using some previous configurations that used
GTK. The only reason I was even looking at the qt option was
that I couldn't get the navit menu to show up (see Bug 19742).
Yinmaosen's reply made me look at that...


The reason I was thinking of a writting a bug report was more along
the lines that someone could right an app against the *core* meego
compliance with expectations it would run correctly everywhere, when
infact it may not.

BTW: thanks for indulging little old me.

Nasa

----- Original Message -----

Post by Clark, Joel
I doubt there is a Navit issue. My guess is the issue is between QT
and the graphics driver you are using. You can file a bug but it may
be difficult to find someone willing to debug a stack with all thee
components Navit, QT and your graphics. I know from experience the QT
guys will ask for a simple test case that reproduces the problem
without depending on "MeeGo apps". The project teams that I know of
that use the Mesa drivers are not using QT.
Can you just switch to using Navit with GTK?
Regards
Joel

Joel,
Should I create a bug report for #2? And should it be 2 bugs?
One for the navit issue and one for lack of testing of the mesa
drivers? It would seem that the drivers would need to be good to
go if meego compliance is going to be enforced (ie: if an app is
written against core, it should work with everything, right?).
Nasa
----- Original Message -----

Post by Clark, Joel
I suggest report 1) against the music app.
For 2) you are on untested ground working with QT/QML and the mesa
drivers. The MeeGo devices that depend on the Mesa drivers have only
been tested with a GTK/Clutter based UX. Sounds like either a QT or
Mesa issue.
3)?
regards
Joel
-----Original Message-----
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?
Ok,
requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).
1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?
2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...
3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.
I know, I'm pushing my luck -- so I will stop here.
Nasa
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi

[Clark, Joel]

BTW which devel:kernel version fixed 17618?

regards
Joel


-----Original Message-----
From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-***@public.gmane.org] On Behalf Of Nasa
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?

Ok,

requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).

1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?


2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...


3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.


I know, I'm pushing my luck -- so I will stop here.


Nasa

[Nasa]

Joel,

I'm not at my system right now, but it came from http://download.meego.com/live/devel:/kernel/ and it was a full kernel (ie: something like kernel-2.6.39-392.8.i586.rpm as I needed some of the additional modules/drivers not in the 1.2 image).

Nasa

----- Original Message -----

Post by Clark, Joel
BTW which devel:kernel version fixed 17618?
regards
Joel
-----Original Message-----
Sent: Wednesday, June 29, 2011 3:50 AM
To: meego-ivi
Subject: [MeeGo-ivi] How/Do I report these?
Ok,
requesting a little help with a couple of issues trying
1.2 (with a couple of updates from 1.2.0.90, matching
against reported bug fixes).
1) I'm having trouble identifying what/where I should report
this issue... I have a large (100+ Gig) music collection that
is stored on an external usb drive, which has a bug related to
this -- see 17618 (I resolved this by using an updated kernel
from the kernel devel on download.meego.com). With the updated
tracker (the fix seems to have set off a firestorm, see 19353)
the external drive is *indexed* by tracker as reported by doing
a 'tracker-control -F'. The total time doing the initial scan
was on the order of 10 - 15 minutes, which is cool given the
size of the items by searched. The problem arises when I start
the music app. The app makes it seem that it is rescanning the
collection on every restart of the application (ie: reboot).
At no time have I noticed the music app completly loading my
music collection (ie: Within Temptation album doesn't get
all the songs on it loaded). So what I don't know is if this
is something I would report against tracker or the music app?
2) When I run navit with the provided navit.xml file, navit
locks up with a totally white screen. The provided navit.xml
file uses qpainter, but if I provide one using the gtk painter
the main navit app works, but I can't get into the internal
menu. Yinmaosen in his comment on Bug report 20255 states that
it works fine for him on RV, so I am trying to identify what would
be different. I am using the mesa drivers instead of egmd...
3) An odd ball *issue*, very low on the totem pole - but, when
I install app using rpm on a terminal (either a VT or using the
terminal with meego) I hear "welcome to navit". Strange.
I know, I'm pushing my luck -- so I will stop here.
Nasa
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi