Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. [Bug 1172] cannot hear any sound from dialer in GTA02
      ([EMAIL PROTECTED])
   2. [Bug 1261] munmap_chunk(): invalid pointer: 0x40c984d4 - Can
      not       launch the OpenMoko GUI ([EMAIL PROTECTED])
   3. [Bug 1262] New: X dies just before loading the desktop
      ([EMAIL PROTECTED])
   4. [Bug 1263] New: hald memory leak
      ([EMAIL PROTECTED])
   5. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1172





------- Additional Comments From [EMAIL PROTECTED]  2008-03-11 15:29 -------
Ok, this looks more and more like a software bug. Builds from mickeyl and
buildhost fail. DAMP Handset Spk is controlling Stereo Out for some reason.

Amp is working correctly as I can turn it on/off and note the difference.

I have objdump -d both mickeyl modules and mine and they are identical so its
not a difference in building the main driver module.

I don't understand why my builds work and other peoples fail.




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1261





------- Additional Comments From [EMAIL PROTECTED]  2008-03-11 17:33 -------
O.k, I try to avoid flashing my neo as long as possible. 

I did an ipkg update and then:
ipkg install openmoko-dialer2_0.1.0\+svnr4178-r7_fic-gta01.ipk 

ERROR: Cannot satisfy the following dependencies for openmoko-dialer2:
         libgsmd (>= 0.1+svnr4174) libgcrypt11 (>= 1.4.0) pango (>= 1.18.3)

But I can't solve the dependencys because:

[EMAIL PROTECTED]:/# ipkg install libgsmd libgcrypt11 pango
Package openmoko-dialer2 (1:0.1.0+svnr4176-r7) installed in root is up to date.
Package libgsmd (0.1+svnr4162-r42) installed in root is up to date.
Package libgcrypt11 (1.2.3-r1) installed in root is up to date.
Package pango (1.18.1-r0) installed in root is up to date.
Nothing to be done

And I can't find any newer packages. 

So, I'm sure just flashing the neo again (with a new Snapshot oder the one
that's used at this moment) will solve the problems, but I don't like this
solution. ;)

But many thanks for your time and help!



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1262

           Summary: X dies just before loading the desktop
           Product: Neo1973 Hardware
           Version: GTA01Bv4
          Platform: Neo1973
               URL: http://pastebin.ca/938552
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core System
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


This bug happens in about 1 out 3 bootups. Rootfs flashed with
Snapshot-20080306-fic-gta01 and kernel with 2.6.24+svnr4154-r4165-r3-neo1973.
Current solution is to login through SSH and start xserver-nodm manually, it has
never crashed there so far.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1263

           Summary: hald memory leak
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Applications & Dependencies
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


When I leave my system running for a while, I see the memory usage of 'hald'
climbing. Currently from 'top':

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
 1013 haldaemo  15   0 18680  16m 1372 S  0.0 13.0   0:02.52 hald               

[EMAIL PROTECTED]:~# uptime
 21:06:40 up 15:55,  2 users,  load average: 0.03, 0.03, 0.00

however in the past I have seen its virtual memory usage over 60MB.

Package version is: hal - 0.5.9-r5 - Hardware Abstraction Layer

My system is slightly non-standard - I have my root on the sd card, and for
several months I have updated it with 'ipkg upgrade' from my locally-built tree
(MokoMakefile, monotone.openembedded.org, autorev) rather than doing a clean
re-install. I would appreciate it if someone with a 'clean' system could check
to see if they see the same hald behaviour after the system has been running for
a few days.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1012
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1193
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1212
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1214
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1215
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1216
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1217
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1218



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to