From trac at haiku-os.org Fri Aug 1 00:59:54 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 31 Jul 2008 22:59:54 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.0ad9aff4fd554a1b2ff342063148c69e@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by bonefish): Since r26692 pretty much all I/O goes through the very new (and likely still buggy) I/O request framework. Can you please check whether r26691 still works OK. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 07:51:56 2008 From: trac at haiku-os.org (umccullough) Date: Fri, 01 Aug 2008 05:51:56 -0000 Subject: [Haiku-bugs] [Haiku] #2078: Add stdio_ext.h header In-Reply-To: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> References: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> Message-ID: <052.9697299506b17aa8795d6e5c9454ff23@haiku-os.org> #2078: Add stdio_ext.h header --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by umccullough): I have attached a new patch that supplies a stdio_ext.h that contains only __fsetlocking() (with associated constants) and _flushlbf() as these appear to be the only methods currently implemented in Haiku. Should allow gettext and others to compile that rely on __fsetlocking() at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 12:46:53 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 01 Aug 2008 10:46:53 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.126ee78bf14b993824a4631a5f1d2ebf@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): I've encountered a similar behavior last night after running a configure. KDL shows that the thread running most of the time was the page writer, althuogh not in low memory situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 13:01:06 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 01 Aug 2008 11:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.336a28fde0fbef6e340c981bf433fd52@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): Replying to [comment:4 bonefish]: > Can you please check whether r26691 still works OK. r26691 appears to work okay. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 14:50:33 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 01 Aug 2008 12:50:33 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.806023c3155c27e2ffbc9d39b68217ad@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): I encountered the hang on r26691 as well, should we move that to a new ticket? It seems unrelated to the corruption. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 18:39:46 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 01 Aug 2008 16:39:46 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.b296f8259a0d665ceae90ed6447cfd7f@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): Could you provide some more debug information when the hang happens? Although, you should retry it with a latest rev, as in http://dev.haiku-os.org/changeset/26710 Ingo fixed a busy loop in the vm_page_allocate_page(). If it re-happens, and you can take some serial output debug, or some screeshots, it'd be nice to know which thread is running, and it's stack trace (bt command). And if your application is waiting (thread ), like your configure, what is waiting for (check the "waiting for" field in the output of the thread KDL command). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 18:42:07 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 01 Aug 2008 16:42:07 -0000 Subject: [Haiku-bugs] [Haiku] #2559: [pthreads] Define PTHREAD_STACK_MIN Message-ID: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> #2559: [pthreads] Define PTHREAD_STACK_MIN -------------------------+-------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- I encountered the following code snippet in Mono: {{{ ret = pthread_attr_setstacksize(&attr, PTHREAD_STACK_MIN); }}} FreeBSD and NetBSD were special-cased to use 65536 instead. No idea how standard this is, but maybe we should define it to something sensible? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 18:42:07 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 01 Aug 2008 16:42:07 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 In-Reply-To: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> References: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> Message-ID: <051.81fe2529695dbea84a65b92f7dc5bb04@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): @scottmc: Partially. The sem.h has been implemented but not heavely tested. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 18:57:56 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 01 Aug 2008 16:57:56 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.ad75985b58b7777c734905f96f136e91@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): A busy loop fix does not sound as if the file corruption were fixed...? In that case I'd be hesitant to shoot my source files. I have not yet encountered such a hang again, still on r26691. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 1 20:59:00 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 01 Aug 2008 18:59:00 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.346c65bd2a21484a76aff45b7d329bdd@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by andreasf): Replying to [comment:18 axeld]: > FYI OS X does not have any other way to kill an app besides the team monitor. Actually it does detect that an app has become unresponsive and then offers "Sofort beenden" from its dock menu. I had to use it quite often for Mail when I lost my 802.11 connection at university. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 01:55:09 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 01 Aug 2008 23:55:09 -0000 Subject: [Haiku-bugs] [Haiku] #2559: [pthreads] Define PTHREAD_STACK_MIN In-Reply-To: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> References: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> Message-ID: <052.1135604ff4f096080652867e086c6de4@haiku-os.org> #2559: [pthreads] Define PTHREAD_STACK_MIN --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * priority: normal => low Comment: {{{PTHREAD_STACK_MIN}}} is not part of the POSIX standard (at least it's not supposed to be defined in or ), and I wouldn't even know what kind of value it is supposed to have. The minimal stack is one page (4 KB), which is probably even sufficient for all libroot functions (that is ATM I can't think of any that would use more). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 02:10:03 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 02 Aug 2008 00:10:03 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.e1196d19edbd1f2c31ff1a4e39c50981@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Replying to [comment:9 andreasf]: > A busy loop fix does not sound as if the file corruption were fixed...? In that case I'd be hesitant to shoot my source files. If r26692 shreds your data, the current revision still will. r26710 only fixes a system hang when the kernel heap needs to grow while all potentially usable pages are bound in caches. It doesn't even fix this completely (i.e. the system will still hang, but a few more threads will continue to run) as documented in r26711. So, if you like your data, don't use any revision newer than r26691 for the moment. I'll try to track the problems down, but that might take a few days. If you have any more hints how to easily reproduce it, that would be much appreciated. > I have not yet encountered such a hang again, still on r26691. If it is the problem fixed by r26710 it should be relatively old and rare, I think. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 10:15:10 2008 From: trac at haiku-os.org (mrsunshine) Date: Sat, 02 Aug 2008 08:15:10 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.9fc3e2966addf564b7784697ef6c2c00@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mrsunshine): Still not working even after the timer split and APIC timer removed from sTimers... =) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 12:42:05 2008 From: trac at haiku-os.org (mrsunshine) Date: Sat, 02 Aug 2008 10:42:05 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.764a3fd65211e2265bd16401a56f7ebd@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mrsunshine): Well, removed the whole kernel tree, updated it and now haiku boots, just takes some time for it to do it but it actualy boots without trouble, no more outb 0x4d0 1 etc =) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 13:57:20 2008 From: trac at haiku-os.org (mmu_man) Date: Sat, 02 Aug 2008 11:57:20 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.d639f1d4870e6401755f99ab543c2391@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmu_man): Maybe APIC timers actually work on IXP ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 14:11:42 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 02 Aug 2008 12:11:42 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.1303928bd7c52dc521594498cba62aeb@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): Could #2522 be related to this one? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 15:16:37 2008 From: trac at haiku-os.org (euan) Date: Sat, 02 Aug 2008 13:16:37 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.289e21035517279777a1ee1897207dee@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by euan): I would suspect that the timer is still broken, it's just that other hardware devices are regularly generating interrupts. At least that's how my system seemed to respond about 6 months ago. It was only with other kernel changes, and IDE changes that it stopped booting. The main clue was that when you say clicked shutdown the dialog box would only appear after the mouse was moved, or a key pressed. I might try rebuilding the tree anyways. After hope, there's always desperation... :D -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 17:32:07 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 02 Aug 2008 15:32:07 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.5e11cbbc957847522cefee59fd3bb6ea@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by bonefish): Replying to [comment:11 emitrax]: > Could #2522 be related to this one? No, #2522 predates r26692, which Andreas has confirmed has introduced this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 2 20:03:12 2008 From: trac at haiku-os.org (andreasf) Date: Sat, 02 Aug 2008 18:03:12 -0000 Subject: [Haiku-bugs] [Haiku] #2560: ALLPERMS uses undefined S_ISTXT Message-ID: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> #2560: ALLPERMS uses undefined S_ISTXT -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The public {{{posix/sys/stat.h}}} header defines {{{ALLPERMS}}} as follows: {{{ #define ALLPERMS (S_ISUID | S_ISGID | S_ISTXT | S_IRWXU | S_IRWXG | S_IRWXO) }}} Yet I don't see a definition for {{{S_ISTXT}}}. Should it be defined or removed from {{{ALLPERMS}}}? Same issue for {{{fssh_stat.h}}} probably. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 03:56:42 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 01:56:42 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.6960f158840f3c7d92e5ed6c954bf9df@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26751. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 04:59:46 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 02:59:46 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.d88efcb2b3f5efbd3144bce34d663511@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Unfortunately I haven't seen this one yet. The stack trace looks like something went wrong on the stack. The eip at which the exception occurred is a location on the stack. And the 0xffff0104, which is the address through which syscalls are routed is displayed as a stack frame address. Either the stack is corrupted by something or the stack/stack frame pointers are offset. It might give some more insight, if you could enable kernel tracing for syscalls and signals and also do a "traced 0" when it happens the next time. Maybe it even stops happing then with syscall tracing enabled, which would indicate a bug in the syscall handler code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 05:06:03 2008 From: trac at haiku-os.org (umccullough) Date: Sun, 03 Aug 2008 03:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.710247ff48f69f3431616b3ad8a36ac5@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by umccullough): Aha! I didn't see this ticket (i searched for "Invalid Opencode Exception" and this bug didn't come up). I am also seeing this when running ./configure on some libs and packages while messing with Haiku. I'm currently running r26688 and have seen at least one or two of these in the last 24 hours. Perhaps I'll add some tracing myself and see if I can provide extra detail. These weren't happening two weeks ago when I was compiling all the same libs/packages before. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 05:06:45 2008 From: trac at haiku-os.org (umccullough) Date: Sun, 03 Aug 2008 03:06:45 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.6bba95e1375b31495dfd1b2302819123@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by umccullough): That was "Invalid Opcode Exception" of course (my fingers had a mind of their own). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 07:27:45 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 03 Aug 2008 05:27:45 -0000 Subject: [Haiku-bugs] [Haiku] #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked In-Reply-To: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> References: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> Message-ID: <051.5b0129a14efe78ebbe80de8ef8a226c9@haiku-os.org> #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * component: - General => System/Kernel Comment: I can confirm this one on 26751 also: {{{ stack trace for thread 5 "page writer" kernel stack: 0x80157000 to 0x8015b000 frame caller :function + offset 0 8015a568 (+ 48) 80056fd5 :invoke_debugger_command + 0x00ed 1 8015a598 (+ 64) 80056dcd :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 8015a5d8 (+ 64) 80057115 :invoke_debugger_command_pipe + 0x009d 3 8015a618 (+ 48) 80057ff0 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 8015a648 (+ 48) 800579a6 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 8015a678 (+ 224) 800593bc :evaluate_debug_command + 0x0088 6 8015a758 (+ 64) 8005544e :kernel_debugger_loop__Fv + 0x01ae 7 8015a798 (+ 48) 80055fe3 :kernel_debugger + 0x0117 8 8015a7c8 (+ 192) 80055ec1 :panic + 0x0029 9 8015a888 (+ 48) 8003896c :rw_lock_read_unlock + 0x0074 10 8015a8b8 (+ 48) 807a07c6 :iterative_io_finished_hook__FPvP9IORequestlbUl + 0x0022 11 8015a8e8 (+ 64) 800953e6 :do_iterative_fd_io_finish__FPvP9IORequestlbUl + 0x0032 12 8015a928 (+ 96) 8006d126 :NotifyFinished__9IORequest + 0x016a 13 8015a988 (+ 48) 8006d220 :SetStatusAndNotify__9IORequestl + 0x006c 14 8015a9b8 (+ 64) 80095ca9 :do_iterative_fd_io + 0x0191 15 8015a9f8 (+ 80) 807a154f :bfs_io__FP9fs_volumeP8fs_vnodePvP9IORequest + 0x008f 16 8015aa48 (+ 64) 80095a15 :vfs_vnode_io + 0x0029 17 8015aa88 (+ 192) 8008ce9f :vfs_write_pages + 0x0063 18 8015ab48 (+ 64) 800311a7 :Write__12VMVnodeCachexPC5iovecUlPUl + 0x002b 19 8015ab88 (+ 80) 800b1db8 :write_page__FP7vm_page + 0x0074 20 8015abd8 (+1024) 800b22a3 :page_writer__FPv + 0x0307 21 8015afd8 (+ 32) 8004d0cf :_create_kernel_thread_kentry__Fv + 0x001b 22 8015aff8 (+2146062344) 8004d06c :thread_kthread_exit__Fv + 0x0000 mutex 0xc2e8e554: name: bfs inode 40.38 flags: 0x0 holder: 307 waiting threads: thread 307: THREAD: 0x916d9000 id: 307 (0x133) name: "jam" all_next: 0x916bf800 team_next: 0x00000000 q_next: 0x80102fe0 priority: 10 (next 10) state: ready next_state: ready cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 fault_handler: 0x00000000 args: 0x910d47f8 0x00000000 entry: 0x80049d48 team: 0x90e37ba0, "jam" exit.sem: 23892 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 7721 kernel_stack_base: 0xa10da000 user_stack_area: 7723 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 46873355 user_time: 13489276 flags: 0x200 architecture dependant section: esp: 0xa10ddcb8 ss: 0x00000010 fpu_state at 0x916d9380 }}} This was during the patience... section of jam -aq. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 12:43:44 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 10:43:44 -0000 Subject: [Haiku-bugs] [Haiku] #2560: ALLPERMS uses undefined S_ISTXT In-Reply-To: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> References: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> Message-ID: <052.c361e5e8173e9c378844f7e98a73ce57@haiku-os.org> #2560: ALLPERMS uses undefined S_ISTXT ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): The attached patch removes {{{S_ISTXT}}} from {{{ALLPERMS}}}, fixing compilation of software using it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 12:48:27 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 10:48:27 -0000 Subject: [Haiku-bugs] [Haiku] #2560: [PATCH] ALLPERMS uses undefined S_ISTXT (was: ALLPERMS uses undefined S_ISTXT) In-Reply-To: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> References: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> Message-ID: <052.63dea3e7f26739d61c898bf1f19411bd@haiku-os.org> #2560: [PATCH] ALLPERMS uses undefined S_ISTXT ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 13:27:31 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 11:27:31 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.eadabdac9e842b523e7c5c6b7465024c@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): Works for me, too, at r26751. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 14:52:21 2008 From: trac at haiku-os.org (axeld) Date: Sun, 03 Aug 2008 12:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #2560: [PATCH] ALLPERMS uses undefined S_ISTXT In-Reply-To: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> References: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> Message-ID: <052.294236cec49f10595cf366a4cb9546c8@haiku-os.org> #2560: [PATCH] ALLPERMS uses undefined S_ISTXT ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Applied in r26754, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 15:22:00 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 13:22:00 -0000 Subject: [Haiku-bugs] [Haiku] #650: [build system] packages are broken for target bone In-Reply-To: <040.12f6dea91cb857b68640441f77ffe151@haiku-os.org> References: <040.12f6dea91cb857b68640441f77ffe151@haiku-os.org> Message-ID: <049.a48b2242dc6cd7697963f7c2f1c07c72@haiku-os.org> #650: [build system] packages are broken for target bone ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: low | Milestone: Unscheduled Component: Build System | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * priority: normal => low * platform: => All * milestone: R1 => Unscheduled Old description: > The following packages doesn't compile when i > ./configure--target=bone > jam packages > > cannaIM > emuxki > inputkit > networkingkit > pdf_writer > printingkit > radeon > screensaverkit > translationkit > usb_vision > > Also note that packages have cvs in it's names e.g. > haiku_networkingkit_cvs, > but should be haiku_networkingkit_svn > > cvs New description: The following packages doesn't compile when i ./configure--target=bone jam packages cannaIM emuxki inputkit networkingkit pdf_writer printingkit radeon screensaverkit translationkit usb_vision Also note that packages have cvs in it's names e.g. haiku_networkingkit_cvs, but should be haiku_networkingkit_svn cvs -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 15:26:06 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 13:26:06 -0000 Subject: [Haiku-bugs] [Haiku] #1990: subversion is not part of the build optional packages In-Reply-To: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> References: <043.8ef46ae040081ccdf00d670ce2d35349@haiku-os.org> Message-ID: <052.dc45fe9c70eab50f6b0a69e69b3dce09@haiku-os.org> #1990: subversion is not part of the build optional packages ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 15:29:51 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 13:29:51 -0000 Subject: [Haiku-bugs] [Haiku] #1290: Problem compiling on MacOS X In-Reply-To: <045.e9ebe2b9a12b8ee2f4aa24b41478eeed@haiku-os.org> References: <045.e9ebe2b9a12b8ee2f4aa24b41478eeed@haiku-os.org> Message-ID: <054.4854b98d3b4487a2f4399eee769791ef@haiku-os.org> #1290: Problem compiling on MacOS X ---------------------------+------------------------------------------------ Reporter: jimmiejams | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should have been fixed quite a while ago. Please reopen, if any problem still persists. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 15:35:18 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 13:35:18 -0000 Subject: [Haiku-bugs] [Haiku] #2527: PANIC: vm_page_fault: unhandled page fault in kernel space at 0x1001004, ip 0x8004fafb In-Reply-To: <044.09dcb199e85b7f2328bd68e6916dc739@haiku-os.org> References: <044.09dcb199e85b7f2328bd68e6916dc739@haiku-os.org> Message-ID: <053.be78143c71cf2f60a83fcfee1eb872f5@haiku-os.org> #2527: PANIC: vm_page_fault: unhandled page fault in kernel space at 0x1001004, ip 0x8004fafb --------------------------+------------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: high | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2223. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 15:36:57 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 03 Aug 2008 13:36:57 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.fd7cad79ae13300e07a62715493d3e0b@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * priority: normal => high Old description: > {{{ > vm_soft_fault: va 0xdeadbef3 not covered by area in address space > vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at > 0xdeadbef3, ip 0x80045773, write 0, user 0, thread 0x24f5 > PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbef3, > ip 0x80045773 > > Welcome to Kernel Debugging Land... > Running on CPU 0 > kdebug> > kdebug> bt > stack trace for thread 9461 "w>Terminal 1" > kernel stack: 0x977b4000 to 0x977b8000 > user stack: 0x70082000 to 0x700c2000 > frame caller :function + offset > 977b7730 (+ 48) 80048dab :invoke_debugger_command + 0x00cf > 977b7760 (+ 64) 80049b54 :_ParseCommand__16ExpressionParserRi > + 0x01f8 > 977b77a0 (+ 48) 80049546 > :EvaluateCommand__16ExpressionParserPCcRi + 0x01de > 977b77d0 (+ 224) 8004ac68 :evaluate_debug_command + 0x0088 > 977b78b0 (+ 64) 800478e6 :kernel_debugger_loop__Fv + 0x017a > 977b78f0 (+ 48) 80048599 :kernel_debugger + 0x010d > 977b7920 (+ 192) 80048481 :panic + 0x0029 > 977b79e0 (+ 64) 800935a7 :vm_page_fault + 0x00ab > 977b7a20 (+ 64) 8009d675 :page_fault_exception + 0x00b1 > 977b7a60 (+ 12) 800a0d4d :int_bottom + 0x001d (nearest) > iframe at 0x977b7a6c (end = 0x977b7ac4) > eax 0xdeadbeef ebx 0x90c8d880 ecx 0x0 edx 0x90c8d880 > esi 0x1 edi 0x801cc0a8 ebp 0x977b7ad4 esp 0x977b7aa0 > eip 0x80045773 eflags 0x10282 > vector: 0xe, error code: 0x0 > 977b7a6c (+ 104) 80045773 :notify_select_events + 0x001b > 977b7ad4 (+ 32) 8004581b :notify_select_event + 0x0027 > 977b7af4 (+ 64) 80045c40 :notify_select_event_pool + 0x005c > 977b7b34 (+ 48) 801c5f45 ons/kernel/drivers/dev/tty>:tty_notify_select_event__FP3ttyUc + 0x0031 > 977b7b64 (+ 48) 801c5fd1 ons/kernel/drivers/dev/tty>:tty_notify_if_available__FP3ttyT0b + 0x0085 > 977b7b94 (+ 48) 801c4ef3 ons/kernel/drivers/dev/tty>:_._12WriterLocker + 0x0067 > 977b7bc4 (+ 208) 801c7a1d ons/kernel/drivers/dev/tty>:tty_write_to_tty_master_unsafe__FP10tty_cookiePCcPUl > + 0x0469 > 977b7c94 (+ 320) 801c7b5d ons/kernel/drivers/dev/tty>:tty_write_to_tty_master__FP10tty_cookiePCvPUl > + 0x0089 > 977b7dd4 (+ 48) 801c9093 ons/kernel/drivers/dev/tty>:master_write__FPvxPCvPUl + 0x0027 > 977b7e04 (+ 128) 80067b20 > :devfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x0178 > 977b7e84 (+ 64) 8007955a > :file_write__FP15file_descriptorxPCvPUl + 0x0036 > 977b7ec4 (+ 80) 80069fe9 :common_user_io__FixPvUlb + 0x017d > 977b7f14 (+ 48) 8006a4dc :_user_write + 0x0028 > 977b7f44 (+ 100) 800a0ec2 :pre_syscall_debug_done + 0x0002 > (nearest) > iframe at 0x977b7fa8 (end = 0x977b8000) > eax 0x78 ebx 0x81aaec ecx 0x700c1c90 edx 0xffff0104 > esi 0x22740b edi 0x22740d ebp 0x700c1ccc esp 0x977b7fdc > eip 0xffff0104 eflags 0x203 > vector: 0x63, error code: 0x0 > 977b7fa8 (+ 0) ffff0104 > 700c1ccc (+ 48) 00216e7a <_APP_>:Write__5ShellPCvUl + 0x002e > 700c1cfc (+ 80) 0021fa1a <_APP_>:KeyDown__8TermViewPCcl + 0x03b2 > 700c1d4c (+ 464) 00385ceb > :DispatchMessage__7BWindowP8BMessageP8BHandler + 0x0aef > 700c1f1c (+ 96) 00389fc4 :task_looper__7BWindow + 0x0270 > 700c1f7c (+ 48) 002e2ed3 :_task0___7BLooperPv + 0x003f > 700c1fac (+ 48) 00795030 :_get_next_team_info + 0x005c > (nearest) > 700c1fdc (+ 0) 700c1fec 196701:w>Terminal 1_9461_stack at 0x70082000 + > 0x3ffec > kdebug> > }}} New description: {{{ vm_soft_fault: va 0xdeadbef3 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xdeadbef3, ip 0x80045773, write 0, user 0, thread 0x24f5 PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbef3, ip 0x80045773 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> kdebug> bt stack trace for thread 9461 "w>Terminal 1" kernel stack: 0x977b4000 to 0x977b8000 user stack: 0x70082000 to 0x700c2000 frame caller :function + offset 977b7730 (+ 48) 80048dab :invoke_debugger_command + 0x00cf 977b7760 (+ 64) 80049b54 :_ParseCommand__16ExpressionParserRi + 0x01f8 977b77a0 (+ 48) 80049546 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 977b77d0 (+ 224) 8004ac68 :evaluate_debug_command + 0x0088 977b78b0 (+ 64) 800478e6 :kernel_debugger_loop__Fv + 0x017a 977b78f0 (+ 48) 80048599 :kernel_debugger + 0x010d 977b7920 (+ 192) 80048481 :panic + 0x0029 977b79e0 (+ 64) 800935a7 :vm_page_fault + 0x00ab 977b7a20 (+ 64) 8009d675 :page_fault_exception + 0x00b1 977b7a60 (+ 12) 800a0d4d :int_bottom + 0x001d (nearest) iframe at 0x977b7a6c (end = 0x977b7ac4) eax 0xdeadbeef ebx 0x90c8d880 ecx 0x0 edx 0x90c8d880 esi 0x1 edi 0x801cc0a8 ebp 0x977b7ad4 esp 0x977b7aa0 eip 0x80045773 eflags 0x10282 vector: 0xe, error code: 0x0 977b7a6c (+ 104) 80045773 :notify_select_events + 0x001b 977b7ad4 (+ 32) 8004581b :notify_select_event + 0x0027 977b7af4 (+ 64) 80045c40 :notify_select_event_pool + 0x005c 977b7b34 (+ 48) 801c5f45 :tty_notify_select_event__FP3ttyUc + 0x0031 977b7b64 (+ 48) 801c5fd1 :tty_notify_if_available__FP3ttyT0b + 0x0085 977b7b94 (+ 48) 801c4ef3 :_._12WriterLocker + 0x0067 977b7bc4 (+ 208) 801c7a1d :tty_write_to_tty_master_unsafe__FP10tty_cookiePCcPUl + 0x0469 977b7c94 (+ 320) 801c7b5d :tty_write_to_tty_master__FP10tty_cookiePCvPUl + 0x0089 977b7dd4 (+ 48) 801c9093 :master_write__FPvxPCvPUl + 0x0027 977b7e04 (+ 128) 80067b20 :devfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x0178 977b7e84 (+ 64) 8007955a :file_write__FP15file_descriptorxPCvPUl + 0x0036 977b7ec4 (+ 80) 80069fe9 :common_user_io__FixPvUlb + 0x017d 977b7f14 (+ 48) 8006a4dc :_user_write + 0x0028 977b7f44 (+ 100) 800a0ec2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x977b7fa8 (end = 0x977b8000) eax 0x78 ebx 0x81aaec ecx 0x700c1c90 edx 0xffff0104 esi 0x22740b edi 0x22740d ebp 0x700c1ccc esp 0x977b7fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 977b7fa8 (+ 0) ffff0104 700c1ccc (+ 48) 00216e7a <_APP_>:Write__5ShellPCvUl + 0x002e 700c1cfc (+ 80) 0021fa1a <_APP_>:KeyDown__8TermViewPCcl + 0x03b2 700c1d4c (+ 464) 00385ceb :DispatchMessage__7BWindowP8BMessageP8BHandler + 0x0aef 700c1f1c (+ 96) 00389fc4 :task_looper__7BWindow + 0x0270 700c1f7c (+ 48) 002e2ed3 :_task0___7BLooperPv + 0x003f 700c1fac (+ 48) 00795030 :_get_next_team_info + 0x005c (nearest) 700c1fdc (+ 0) 700c1fec 196701:w>Terminal 1_9461_stack at 0x70082000 + 0x3ffec kdebug> }}} -- Comment: #2557 is a duplicate of this one. The bug apparently still persists. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 17:07:26 2008 From: trac at haiku-os.org (mrsunshine) Date: Sun, 03 Aug 2008 15:07:26 -0000 Subject: [Haiku-bugs] [Haiku] #2561: bfs_shell no more sems Message-ID: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> #2561: bfs_shell no more sems ------------------------+--------------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------+--------------------------------------------------- bfs_shell when copying lots of files crashes with no more sems error (tested by printf) backtrace: #0 0x0806d0e6 in fssh_panic ()[[BR]] #1 0x0806dcd5 in fssh_mutex_init ()[[BR]] #2 0x0806c7ce in fssh_file_cache_create ()[[BR]] #3 0x0805c6f6 in Inode::Create ()[[BR]] #4 0x0806922c in bfs_create ()[[BR]] #5 0x08072b36 in FSShell::create_vnode ()[[BR]] #6 0x08074fb7 in FSShell::_kern_open ()[[BR]] #7 0x0807c54f in FSShell::GuestFSDomain::CreateFile ()[[BR]] #8 0x0807a4ea in FSShell::copy_entry ()[[BR]] #9 0x0807abe7 in FSShell::copy_dir_contents ()[[BR]] #10 0x0807a973 in FSShell::copy_entry ()[[BR]] #11 0x0807abe7 in FSShell::copy_dir_contents ()[[BR]] #12 0x0807a973 in FSShell::copy_entry ()[[BR]] #13 0x0807abe7 in FSShell::copy_dir_contents ()[[BR]] #14 0x0807a973 in FSShell::copy_entry ()[[BR]] #15 0x0807abe7 in FSShell::copy_dir_contents ()[[BR]] #16 0x0807a973 in FSShell::copy_entry ()[[BR]] #17 0x0807abe7 in FSShell::copy_dir_contents ()[[BR]] #18 0x0807a973 in FSShell::copy_entry ()[[BR]] #19 0x0807b4ba in FSShell::command_cp ()[[BR]] #20 0x08075a5f in FSShell::Command::Do ()[[BR]] #21 0x080788a5 in main ()[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 17:42:44 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 15:42:44 -0000 Subject: [Haiku-bugs] [Haiku] #2560: [PATCH] ALLPERMS uses undefined S_ISTXT In-Reply-To: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> References: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> Message-ID: <052.9a847d9ca2f9eb63ed9044745da2327b@haiku-os.org> #2560: [PATCH] ALLPERMS uses undefined S_ISTXT ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by andreasf): * status: closed => reopened * resolution: fixed => Comment: Shouldn't a fix be applied for {{{fssh_stat.h}}} as well then? Anyhow, I'm now wondering whether my patch above might be wrong: Could it've been a typo meaning {{{S_ISVTX}}} ("save swapped text even after use")? On Darwin {{{S_ISTXT}}} gets defined to {{{S_ISVTX}}} (quote: "sticky bit: not supported" ;)), and {{{ALLPERMS}}} does use {{{S_ISTXT}}} there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 18:32:14 2008 From: trac at haiku-os.org (axeld) Date: Sun, 03 Aug 2008 16:32:14 -0000 Subject: [Haiku-bugs] [Haiku] #2560: [PATCH] ALLPERMS uses undefined S_ISTXT In-Reply-To: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> References: <043.0d4d0118250588606cd0db5941741dc7@haiku-os.org> Message-ID: <052.1591cec418045aa58a6432f3bdfe5e1e@haiku-os.org> #2560: [PATCH] ALLPERMS uses undefined S_ISTXT ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: You're right; ALLPERMS should contain all permission bits. I've changed stat.h now to contain S_ISVTX instead. I also changed the fs_shell's header this time :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 18:55:48 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 16:55:48 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang Message-ID: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> #2562: Occasional hang -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- As reported in #2558, I'm experiencing occasional hangs with high CPU activity on both HT "cores" while compiling software on gcc2 Haiku on real hardware. Here's serial output from r26754: {{{ Welcome to Kernel Debugging Land... Thread 37881 "sh" running on CPU 0 kdebug> teams team id parent name 0x90c0c000 94 0x90b80000 Terminal 0x90b80000 1 0x00000000 kernel_team 0x90c0c174 95 0x90b80000 media_server 0x90c0c45c 97 0x90b80000 midi_server 0x90c0c5d0 98 0x90b80000 print_server 0x90fa1000 21675 0x90b80a2c pe 0x90fa1174 37460 0x90fa145c sh 0x90b80e88 24502 0x90c0cba0 sh 0x90fa1744 37461 0x90fa1174 make 0x90fa12e8 33557 0x90c0ce88 make 0x90b808b8 77 0x90b80000 syslog_daemon 0x90fa145c 33558 0x90fa12e8 sh 0x90b80174 33434 0x90b80e88 make 0x90c0c744 33436 0x90b80174 make 0x90c0c2e8 33437 0x90c0c744 sh 0x90b80ba0 81 0x90b80744 input_server 0x90c0cba0 144 0x90c0c000 sh 0x90b802e8 53 0x90b80000 registrar 0x90c0ca2c 33441 0x90c0c2e8 sh 0x90c0ce88 33442 0x90c0ca2c make 0x90c0c8b8 117 0x90c0c174 media_addon_server 0x90b8045c 58 0x90b80000 debug_server 0x90b805d0 59 0x90b80000 net_server 0x90b80a2c 91 0x90b80000 Tracker 0x90b80744 60 0x90b80000 app_server 0x90fa15d0 37881 0x90fa1744 sh 0x90b80d14 92 0x90b80000 Deskbar kdebug> threads 37460 thread id state wait for object cpu pri stack team name 0x914dd000 37460 waiting cvar 0x90b818a8 - 10 0x957ea00037460 sh kdebug> threads 37881 thread id state wait for object cpu pri stack team name 0x914ab800 37881 running - 0 10 0x957f200037881 sh kdebug> sc 37881 stack trace for thread 37881 "sh" kernel stack: 0x957f2000 to 0x957f6000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 957f5584 (+ 48) 80053e0d :invoke_debugger_command + 0x00ed 1 957f55b4 (+ 64) 80053c05 :invoke_pipe_segment__FP21debugger_comma9 2 957f55f4 (+ 64) 80053f4d :invoke_debugger_command_pipe + 0x009d 3 957f5634 (+ 48) 80054e28 :_ParseCommandPipe__16ExpressionParserRi4 4 957f5664 (+ 48) 800547de :EvaluateCommand__16ExpressionParserPCcRe 5 957f5694 (+ 224) 800561f4 :evaluate_debug_command + 0x0088 6 957f5774 (+ 64) 80052286 :kernel_debugger_loop__Fv + 0x01ae 7 957f57b4 (+ 48) 80052e1b :kernel_debugger + 0x0117 8 957f57e4 (+ 192) 80052cf9 :panic + 0x0029 9 957f58a4 (+ 48) 807a4df5 :int_io_interrupt_handler + 0x00e0 11 957f5914 (+ 48) 800b2950 :hardware_interrupt + 0x006c 12 957f5944 (+ 12) 800b5df6 :int_bottom + 0x0036 (nearest) iframe at 0x957f5950 (end = 0x957f59a8) eax 0x200 ebx 0x90b71030 ecx 0x0 edx 0x246 esi 0x1 edi 0x91bada10 ebp 0x957f59a0 esp 0x957f5984 eip 0x800b25bc eflags 0x246 vector: 0x21, error code: 0x0 13 957f5950 (+ 80) 800b25bc :arch_int_restore_interrupts + 0x0020 14 957f59a0 (+ 32) 80035d32 :restore_interrupts + 0x0012 15 957f59c0 (+ 48) 800b5384 :flush_tmap__FP18vm_translation_map + 0x0 16 957f59f0 (+ 48) 800b4b0b :unlock_tmap__FP18vm_translation_map + 07 17 957f5a20 (+ 64) 800a5640 :vm_map_page + 0x0078 18 957f5a60 (+ 256) 800a7f07 :vm_soft_fault__FP16vm_address_spaceUlbTf 19 957f5b60 (+ 64) 800a7028 :vm_page_fault + 0x0080 20 957f5ba0 (+ 64) 800b28cd :page_fault_exception + 0x00b1 21 957f5be0 (+ 12) 800b5df6 :int_bottom + 0x0036 (nearest) iframe at 0x957f5bec (end = 0x957f5c44) eax 0x0 ebx 0xffff00d6 ecx 0x1 edx 0x914abaec esi 0x957f5ca4 edi 0xffff00d6 ebp 0x957f5c70 esp 0x957f5c20 eip 0x800b5a94 eflags 0x10202 vector: 0xe, error code: 0x3 22 957f5bec (+ 132) 800b5a94 :arch_cpu_user_memcpy + 0x001e (nearest) 23 957f5c70 (+ 640) 800b3b83 :arch_setup_signal_frame + 0x004f 24 957f5ef0 (+ 96) 800427d2 :handle_signals + 0x03ce 25 957f5f50 (+ 64) 8004c9e6 :thread_at_kernel_exit + 0x0076 26 957f5f90 (+ 12) 800b60fb :kernel_exit_handle_signals + 0x0006 (ne) iframe at 0x957f5f9c (end = 0x957f5ff4) eax 0x0 ebx 0x341ac8 ecx 0x1 edx 0x4 esi 0x18030188 edi 0x18000000 ebp 0x7ffecc9c esp 0x957f5fd0 eip 0x800b5f50 eflags 0x212 vector: 0xfd, error code: 0x0 27 957f5f9c (+ 0) 800b5f50 :trap99 + 0x0000 (nearest) 28 7ffecc9c (+ 32) 002c92a4 :malloc + 0x01a4 29 7ffeccbc (+ 48) 00248ab5 <_APP_>:xrealloc + 0x0035 30 7ffeccec (+ 192) 00233729 <_APP_>:unlink_fifo_list + 0x0459 (nearest) 31 7ffecdac (+ 80) 00233b6d <_APP_>:command_substitute + 0x0345 32 7ffecdfc (+ 112) 002368c7 <_APP_>:pat_subst + 0x1bd7 (nearest) 33 7ffece6c (+ 64) 00231e79 <_APP_>:cond_expand_word + 0x0129 (nearest) 34 7ffeceac (+ 96) 00231f47 <_APP_>:cond_expand_word + 0x01f7 (nearest) 35 7ffecf0c (+ 48) 00231fa7 <_APP_>:expand_string_unsplit + 0x003b 36 7ffecf3c (+ 48) 00231ba5 <_APP_>:string_rest_of_args + 0x01d5 (nearest) 37 7ffecf6c (+ 64) 0023163a <_APP_>:strip_trailing_ifs_whitespace + 0x01f6 () 38 7ffecfac (+ 48) 002317f1 <_APP_>:do_assignment + 0x0021 39 7ffecfdc (+ 48) 00237896 <_APP_>:expand_words_shellexp + 0x05da (nearest) 40 7ffed00c (+ 48) 0023728d <_APP_>:expand_words + 0x0021 41 7ffed03c (+ 112) 00226d09 <_APP_>:execute_command_internal + 0x2f65 (neare) 42 7ffed0ac (+ 96) 00224262 <_APP_>:execute_command_internal + 0x04be 43 7ffed10c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 44 7ffed15c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 45 7ffed18c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 46 7ffed1ec (+ 80) 00223bed <_APP_>:execute_command + 0x0065 47 7ffed23c (+ 80) 0022632a <_APP_>:execute_command_internal + 0x2586 (neare) 48 7ffed28c (+ 80) 002243ec <_APP_>:execute_command_internal + 0x0648 49 7ffed2dc (+ 64) 002253df <_APP_>:execute_command_internal + 0x163b (neare) 50 7ffed31c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 51 7ffed37c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 52 7ffed3cc (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 53 7ffed3fc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 54 7ffed45c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 55 7ffed4ac (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 56 7ffed4dc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 57 7ffed53c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 58 7ffed58c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 59 7ffed5bc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 60 7ffed61c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 61 7ffed66c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 62 7ffed69c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 63 7ffed6fc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 64 7ffed74c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 65 7ffed77c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 66 7ffed7dc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 67 7ffed82c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 68 7ffed85c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 69 7ffed8bc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 70 7ffed90c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 71 7ffed93c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 72 7ffed99c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 73 7ffed9ec (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 74 7ffeda1c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 75 7ffeda7c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 76 7ffedacc (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 77 7ffedafc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 78 7ffedb5c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 79 7ffedbac (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 80 7ffedbdc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 81 7ffedc3c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 82 7ffedc8c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 83 7ffedcbc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 84 7ffedd1c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 85 7ffedd6c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 86 7ffedd9c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 87 7ffeddfc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 88 7ffede4c (+ 64) 00225614 <_APP_>:execute_command_internal + 0x1870 (neare) 89 7ffede8c (+ 80) 00224380 <_APP_>:execute_command_internal + 0x05dc 90 7ffededc (+ 64) 002253df <_APP_>:execute_command_internal + 0x163b (neare) 91 7ffedf1c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 92 7ffedf7c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 93 7ffedfcc (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 94 7ffedffc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 95 7ffee05c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 96 7ffee0ac (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 97 7ffee0dc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 98 7ffee13c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 99 7ffee18c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (neare) 100 7ffee1bc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 101 7ffee21c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 102 7ffee26c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 103 7ffee29c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 104 7ffee2fc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 105 7ffee34c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 106 7ffee37c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 107 7ffee3dc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 108 7ffee42c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 109 7ffee45c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 110 7ffee4bc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 111 7ffee50c (+ 64) 00225614 <_APP_>:execute_command_internal + 0x1870 (near) 112 7ffee54c (+ 80) 00224380 <_APP_>:execute_command_internal + 0x05dc 113 7ffee59c (+ 64) 002253df <_APP_>:execute_command_internal + 0x163b (near) 114 7ffee5dc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 115 7ffee63c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 116 7ffee68c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 117 7ffee6bc (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 118 7ffee71c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 119 7ffee76c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 120 7ffee79c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 121 7ffee7fc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 122 7ffee84c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 123 7ffee87c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 124 7ffee8dc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 125 7ffee92c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 126 7ffee95c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 127 7ffee9bc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 128 7ffeea0c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 129 7ffeea3c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 130 7ffeea9c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 131 7ffeeaec (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 132 7ffeeb1c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 133 7ffeeb7c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 134 7ffeebcc (+ 80) 0022632a <_APP_>:execute_command_internal + 0x2586 (near) 135 7ffeec1c (+ 80) 002243ec <_APP_>:execute_command_internal + 0x0648 136 7ffeec6c (+ 64) 002253df <_APP_>:execute_command_internal + 0x163b (near) 137 7ffeecac (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 138 7ffeed0c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 139 7ffeed5c (+ 48) 00225362 <_APP_>:execute_command_internal + 0x15be (near) 140 7ffeed8c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 141 7ffeedec (+ 80) 00223bed <_APP_>:execute_command + 0x0065 142 7ffeee3c (+ 48) 00226556 <_APP_>:execute_command_internal + 0x27b2 (near) 143 7ffeee6c (+ 80) 00224458 <_APP_>:execute_command_internal + 0x06b4 144 7ffeeebc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 145 7ffeef0c (+ 48) 0021f8a5 <_APP_>:reader_loop + 0x01d1 146 7ffeef3c (+ 64) 0021dae2 <_APP_>:main + 0x07b2 147 7ffeef7c (+ 48) 0021679f <_APP_>:_start + 0x005b 148 7ffeefac (+ 48) 001008ea 839631:runtime_loader_seg0ro at 0x00100000 + 0x8ea 149 7ffeefdc (+ 0) 7ffeefec 839630:sh_main_stack at 0x7efef000 + 0xffffec kdebug> }}} This is while executing {{{ /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -D_REENTRANT -o node- test node-test.o ../libglib.la }}} as part of pkg-config 0.23's {{{make}}}. Ctrl+C is unable to kill the running application, neither does {{{kill -9 }}}. Restarting the system works without problems though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 19:19:38 2008 From: trac at haiku-os.org (oco) Date: Sun, 03 Aug 2008 17:19:38 -0000 Subject: [Haiku-bugs] [Haiku] #2563: Strength of colours should use a BSlider to help fine tune the setting Message-ID: <038.f8a9e81a18c5edb892b35bd86c004fae@haiku-os.org> #2563: Strength of colours should use a BSlider to help fine tune the setting ------------------------------------+--------------------------------------- Reporter: oco | Owner: darkwyrm Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- I think it is not easy to fine tune the strength of colours setting using a TextBox. Except if there is a clear rule to calculate the best setting on a specific machine, i think a better interface is needed : - a slider - some keyboard shorcuts - something else... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 19:34:08 2008 From: trac at haiku-os.org (stippi) Date: Sun, 03 Aug 2008 17:34:08 -0000 Subject: [Haiku-bugs] [Haiku] #2563: Strength of colours should use a BSlider to help fine tune the setting In-Reply-To: <038.f8a9e81a18c5edb892b35bd86c004fae@haiku-os.org> References: <038.f8a9e81a18c5edb892b35bd86c004fae@haiku-os.org> Message-ID: <047.0146a6dda09e5672d86bfab2a143127d@haiku-os.org> #2563: Strength of colours should use a BSlider to help fine tune the setting -------------------------------------+-------------------------------------- Reporter: oco | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * owner: darkwyrm => stippi * status: new => assigned Comment: Absolutely agreed! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 21:38:46 2008 From: trac at haiku-os.org (hunnia) Date: Sun, 03 Aug 2008 19:38:46 -0000 Subject: [Haiku-bugs] [Haiku] #1723: Booting stops somehere in the bootscript In-Reply-To: <041.b6d95fd8a59fa2c2dae24538377e72fc@haiku-os.org> References: <041.b6d95fd8a59fa2c2dae24538377e72fc@haiku-os.org> Message-ID: <050.7158abc0a4108a6be78ed5d74e9806db@haiku-os.org> #1723: Booting stops somehere in the bootscript ------------------------+--------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by hunnia): Using the 2008 Aug 2 image on a Haiku partition boot up end executing the tracker is now successfull. So as far as I (hunnia) is concerned the problem get solved and if all agrees, the ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 21:47:42 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 19:47:42 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang In-Reply-To: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> References: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> Message-ID: <052.d54eca9d289cd33a94f6e4e43192040e@haiku-os.org> #2562: Occasional hang ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Next hang: {{{ Welcome to Kernel Debugging Land... Thread 171 "sh" running on CPU 0 kdebug> teams team id parent name 0x90b80744 62 0x90b80000 app_server 0x90c0c000 94 0x90b80000 Terminal 0x90b80000 1 0x00000000 kernel_team 0x90c0c2e8 96 0x90b80000 media_server 0x90c0c45c 99 0x90b80000 midi_server 0x90c0c5d0 100 0x90b80000 print_server 0x90b80e88 170 0x90c0c744 sh 0x90b808b8 77 0x90b80000 syslog_daemon 0x90c0c174 171 0x90b80e88 sh 0x90c0c744 142 0x90c0c000 sh 0x90b80ba0 81 0x90b80744 input_server 0x90b802e8 53 0x90b80000 registrar 0x90b80174 116 0x90c0c2e8 media_addon_server 0x90b8045c 58 0x90b80000 debug_server 0x90b805d0 59 0x90b80000 net_server 0x90b80a2c 91 0x90b80000 Tracker 0x90b80d14 92 0x90b80000 Deskbar kdebug> threads 171 thread id state wait for object cpu pri stack team name 0x91488000 171 running - 0 10 0x80777000 171 sh kdebug> sc 171 stack trace for thread 171 "sh" kernel stack: 0x80777000 to 0x8077b000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 8077a584 (+ 48) 80053e0d :invoke_debugger_command + 0x00ed 1 8077a5b4 (+ 64) 80053c05 :invoke_pipe_segment__FP21debugger_comma9 2 8077a5f4 (+ 64) 80053f4d :invoke_debugger_command_pipe + 0x009d 3 8077a634 (+ 48) 80054e28 :_ParseCommandPipe__16ExpressionParserRi4 4 8077a664 (+ 48) 800547de :EvaluateCommand__16ExpressionParserPCcRe 5 8077a694 (+ 224) 800561f4 :evaluate_debug_command + 0x0088 6 8077a774 (+ 64) 80052286 :kernel_debugger_loop__Fv + 0x01ae 7 8077a7b4 (+ 48) 80052e1b :kernel_debugger + 0x0117 8 8077a7e4 (+ 192) 80052cf9 :panic + 0x0029 9 8077a8a4 (+ 48) 8079edf5 :int_io_interrupt_handler + 0x00e0 11 8077a914 (+ 48) 800b2950 :hardware_interrupt + 0x006c 12 8077a944 (+ 12) 800b5df6 :int_bottom + 0x0036 (nearest) iframe at 0x8077a950 (end = 0x8077a9a8) eax 0x200 ebx 0x90b71030 ecx 0x0 edx 0x246 esi 0x1 edi 0x91bada10 ebp 0x8077a9a0 esp 0x8077a984 eip 0x800b25bc eflags 0x246 vector: 0x21, error code: 0x0 13 8077a950 (+ 80) 800b25bc :arch_int_restore_interrupts + 0x0020 14 8077a9a0 (+ 32) 80035d32 :restore_interrupts + 0x0012 15 8077a9c0 (+ 48) 800b5384 :flush_tmap__FP18vm_translation_map + 0x0 16 8077a9f0 (+ 48) 800b4b0b :unlock_tmap__FP18vm_translation_map + 07 17 8077aa20 (+ 64) 800a5640 :vm_map_page + 0x0078 18 8077aa60 (+ 256) 800a7f07 :vm_soft_fault__FP16vm_address_spaceUlbTf 19 8077ab60 (+ 64) 800a7028 :vm_page_fault + 0x0080 20 8077aba0 (+ 64) 800b28cd :page_fault_exception + 0x00b1 21 8077abe0 (+ 12) 800b5df6 :int_bottom + 0x0036 (nearest) iframe at 0x8077abec (end = 0x8077ac44) eax 0x0 ebx 0xffff00d6 ecx 0x1 edx 0x914882ec esi 0x8077aca4 edi 0xffff00d6 ebp 0x8077ac70 esp 0x8077ac20 eip 0x800b5a94 eflags 0x10202 vector: 0xe, error code: 0x3 22 8077abec (+ 132) 800b5a94 :arch_cpu_user_memcpy + 0x001e (nearest) 23 8077ac70 (+ 640) 800b3b83 :arch_setup_signal_frame + 0x004f 24 8077aef0 (+ 96) 800427d2 :handle_signals + 0x03ce 25 8077af50 (+ 64) 8004c9e6 :thread_at_kernel_exit + 0x0076 26 8077af90 (+ 12) 800b60fb :kernel_exit_handle_signals + 0x0006 (ne) iframe at 0x8077af9c (end = 0x8077aff4) eax 0x0 ebx 0x341ac8 ecx 0x1 edx 0x4 esi 0x18150698 edi 0x18000000 ebp 0x7ffee91c esp 0x8077afd0 eip 0x800b5f50 eflags 0x212 vector: 0xfd, error code: 0x0 27 8077af9c (+ 0) 800b5f50 :trap99 + 0x0000 (nearest) 28 7ffee91c (+ 32) 002c92a4 :malloc + 0x01a4 29 7ffee93c (+ 48) 00248ab5 <_APP_>:xrealloc + 0x0035 30 7ffee96c (+ 192) 00233729 <_APP_>:unlink_fifo_list + 0x0459 (nearest) 31 7ffeea2c (+ 80) 00233b6d <_APP_>:command_substitute + 0x0345 32 7ffeea7c (+ 112) 002368c7 <_APP_>:pat_subst + 0x1bd7 (nearest) 33 7ffeeaec (+ 80) 002376dc <_APP_>:expand_words_shellexp + 0x0420 (nearest) 34 7ffeeb3c (+ 48) 0023792c <_APP_>:expand_words_shellexp + 0x0670 (nearest) 35 7ffeeb6c (+ 48) 0023728d <_APP_>:expand_words + 0x0021 36 7ffeeb9c (+ 112) 00226d09 <_APP_>:execute_command_internal + 0x2f65 (neare) 37 7ffeec0c (+ 96) 00224262 <_APP_>:execute_command_internal + 0x04be 38 7ffeec6c (+ 80) 00223bed <_APP_>:execute_command + 0x0065 39 7ffeecbc (+ 48) 002264f6 <_APP_>:execute_command_internal + 0x2752 (neare) 40 7ffeecec (+ 80) 00224458 <_APP_>:execute_command_internal + 0x06b4 41 7ffeed3c (+ 64) 002253df <_APP_>:execute_command_internal + 0x163b (neare) 42 7ffeed7c (+ 96) 002244e4 <_APP_>:execute_command_internal + 0x0740 43 7ffeeddc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 44 7ffeee2c (+ 64) 00225614 <_APP_>:execute_command_internal + 0x1870 (neare) 45 7ffeee6c (+ 80) 00224380 <_APP_>:execute_command_internal + 0x05dc 46 7ffeeebc (+ 80) 00223bed <_APP_>:execute_command + 0x0065 47 7ffeef0c (+ 48) 0021f8a5 <_APP_>:reader_loop + 0x01d1 48 7ffeef3c (+ 64) 0021dae2 <_APP_>:main + 0x07b2 49 7ffeef7c (+ 48) 0021679f <_APP_>:_start + 0x005b 50 7ffeefac (+ 48) 001008ea 3562:runtime_loader_seg0ro at 0x00100000 + 0x8ea 51 7ffeefdc (+ 0) 7ffeefec 3561:sh_main_stack at 0x7efef000 + 0xffffec }}} (This time, stack trace was taken after trying to Ctrl+C.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 21:49:35 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 19:49:35 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang In-Reply-To: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> References: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> Message-ID: <052.4b756ebcf23cf20a0d58a992476d5e0c@haiku-os.org> #2562: Occasional hang ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Forgot to mention that this was after libiconv 1.12's configure printing: {{{ checking for stdlib.h... (cached) yes }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 3 23:30:57 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 03 Aug 2008 21:30:57 -0000 Subject: [Haiku-bugs] [Haiku] #2564: signbit macro uses __signbitf function although not compiled in? Message-ID: <043.c0f6b67130dd2ce95d09a4a26a21c0e8@haiku-os.org> #2564: signbit macro uses __signbitf function although not compiled in? -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The public header {{{posix/math.h}}} defines a {{{signbit}}} macro to call functions {{{__signbitf}}} et al. However these cannot be resolved at runtime. The implementation for this function seems to be in {{{libroot/posix/glibc/arch/generic/s_signbitf.c}}} but that directory does not seem to be compiled in - there's no {{{./Jamfile}}}, and {{{../Jamfile}}} only includes the specific architecture. Mono's configure for instance detects {{{signbit}}} but later fails to link. (It ''can'' work without, but gets confused by the current situation.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 05:01:03 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 04 Aug 2008 03:01:03 -0000 Subject: [Haiku-bugs] [Haiku] #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked In-Reply-To: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> References: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> Message-ID: <051.d6988093ea0f120f13aec5377e8f658d@haiku-os.org> #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should be fixed in r26776. I couldn't reproduce the exact problem, but in certain error situations the request finished hook was invoked twice, which would perfectly explain this situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 07:27:34 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 Aug 2008 05:27:34 -0000 Subject: [Haiku-bugs] [Haiku] #2511: MediaPlayer will not play .wav files from an Audio CD In-Reply-To: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> References: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> Message-ID: <051.94131a70909c05428c4171383d0da5d5@haiku-os.org> #2511: MediaPlayer will not play .wav files from an Audio CD ---------------------------------------+------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by anevilyak): * owner: axeld => marcusoverhagen * component: - General => Applications/MediaPlayer Comment: I can confirm this one as well on the latest revs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 07:31:00 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 Aug 2008 05:31:00 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs Message-ID: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs -------------------------------+-------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- If I try to copy the last track of a CD mounted via cdda-fs to the hard disk, it copies around 99% of the file and then fails with General OS error. Perhaps some calculation error in the size of the disc? This only seems to happen with some discs though, what information can I gather for this case? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 07:42:10 2008 From: trac at haiku-os.org (umccullough) Date: Mon, 04 Aug 2008 05:42:10 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.bc75a4a6e32ad85c38656e97991f7946@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by umccullough): I thought it had worked in my case, but I simply missed the error message when it popped up and closed it by mistake. So, I can confirm the issue here on r26767 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 12:10:10 2008 From: trac at haiku-os.org (axeld) Date: Mon, 04 Aug 2008 10:10:10 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.ba99f0d1db90e9d42c625f9fd1bba4a3@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by axeld): Can you name some example CDs, preferably in the alternative/rock genre? :-)) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 12:25:56 2008 From: trac at haiku-os.org (axeld) Date: Mon, 04 Aug 2008 10:25:56 -0000 Subject: [Haiku-bugs] [Haiku] #2511: MediaPlayer will not play .wav files from an Audio CD In-Reply-To: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> References: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> Message-ID: <051.d17df426c04a0f7fa5adadcc42db878e@haiku-os.org> #2511: MediaPlayer will not play .wav files from an Audio CD --------------------------------+------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * owner: marcusoverhagen => axeld * component: Applications/MediaPlayer => File Systems/cdda Comment: That's more likely the reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 14:36:15 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 Aug 2008 12:36:15 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.bc83d87460c22822d8e7ef349c4c7d8d@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): I'll need to check...any preferred bands? The one I saw it with was a relatively obscure Japanese import CD which I doubt you'd have in your collection anyways, because it happened to be in the drive at the time and was auto-mounted so I played around (I'm not used to having CD support since I usually use the ata bus manager, but reverted that and forgot to set it back when making an image for koki). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 14:37:15 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 Aug 2008 12:37:15 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.9e098fcbf1427a3d2d15e3e8755d57f4@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): Also if it helps, of the last track it was only missing around 9KB or so, that was copying with Tracker though which iirc uses variable size buffers as the copy goes on, if you want I can try it with DD and a small block size to see if it's just the very last block that fails or what. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 16:21:50 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 04 Aug 2008 14:21:50 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang In-Reply-To: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> References: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> Message-ID: <052.524304b19a0a9ed54557d88fdcb49a86@haiku-os.org> #2562: Occasional hang ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 16:33:22 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 14:33:22 -0000 Subject: [Haiku-bugs] [Haiku] #2559: [pthreads] Define PTHREAD_STACK_MIN In-Reply-To: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> References: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> Message-ID: <052.a7597b55108c1ad0c25f68f9cabccdd3@haiku-os.org> #2559: [pthreads] Define PTHREAD_STACK_MIN --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): FYI in this particular case, using 4096 in place of {{{PTHREAD_STACK_MIN}}} badly freezes the system. Same for 8192 (seen on OSX in {{{limits.h}}}). Using 65536 doesn't. {{{ vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x70002007 create_thread: unable to create proper user stack! CPU 0 halted! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 16:39:47 2008 From: trac at haiku-os.org (kaliber) Date: Mon, 04 Aug 2008 14:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #2561: bfs_shell no more sems In-Reply-To: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> References: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> Message-ID: <054.7bf88627a0ba369f649d3c27783ba459@haiku-os.org> #2561: bfs_shell no more sems -------------------------+-------------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by kaliber): Duplicate of bug #2520 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 17:14:01 2008 From: trac at haiku-os.org (umccullough) Date: Mon, 04 Aug 2008 15:14:01 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.86d5c599b2baec362634e4bcf9e880b1@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by umccullough): Replying to [comment:2 axeld]: > Can you name some example CDs, preferably in the alternative/rock genre? :-)) Oh come on now, this is just a ploy to find out what our musical preferences are :D In my case, it was one of the only CDs I found sitting in a pile on the shelf: Weird Al Yankovic's Straight Outta Lynnwood (DualDisc format) Yeah, slightly embarrassing ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 17:37:20 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 04 Aug 2008 15:37:20 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang In-Reply-To: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> References: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> Message-ID: <052.de20e7c1f8df5d2298880756c9504676@haiku-os.org> #2562: Occasional hang ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Fortunately I'm able to reproduce the problem with a test program, so it should just be a matter of enough poking to understand it. So far I've only found out that in arch_setup_signal_frame() the address of the iframe is already broken. It gets the same one we see in the stack trace, which is off by 12 bytes (its end should be aligned with the kernel stack). The user stack pointer in this iframe points to the kernel stack, which causes data to be overwritten when the functions tries to set up the signal stack. #2522 might very well be related. Will continue looking into it later tonight. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 20:23:00 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 Aug 2008 18:23:00 -0000 Subject: [Haiku-bugs] [Haiku] #2511: MediaPlayer will not play .wav files from an Audio CD In-Reply-To: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> References: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> Message-ID: <051.ec317e69abab789b9ae2b2f953186f16@haiku-os.org> #2511: MediaPlayer will not play .wav files from an Audio CD --------------------------------+------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): I'm trying to understand how cdda-fs would cause that problem though, unless it's failing block reads from the decoder sniffers. Otherwise it seems as if the file being on BFS is giving MediaPlayer some extra information that it's used in lieu of the sniffers and it's not falling back gracefully in the absence of said info, or something along those lines. Would need to investigate exactly what call is failing in MediaPlayer in this case to be sure though. I also need to check what mime type cdda reports for those files as opposed to what they get identified as once copied to BFS. This problem is at least 100% reproducible though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 20:56:40 2008 From: trac at haiku-os.org (un_spacyar) Date: Mon, 04 Aug 2008 18:56:40 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.9b999d1000c8d845341527440c4b2907@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Changes (by un_spacyar): * cc: un_spacyar at yahoo.com.ar (added) * status: closed => reopened * resolution: fixed => Comment: There are some issues not fixed. Please, see the following files: AdvancedSettings.png SavePDF.png PD: sorry for the delay retesting this issue. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 21:09:16 2008 From: trac at haiku-os.org (un_spacyar) Date: Mon, 04 Aug 2008 19:09:16 -0000 Subject: [Haiku-bugs] [Haiku] #2566: Workspaces replicant - active window lost focus Message-ID: <045.2b87057b23bf5bdc9f90fd1f2dee89bf@haiku-os.org> #2566: Workspaces replicant - active window lost focus -------------------------------------+-------------------------------------- Reporter: un_spacyar | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- When create a "Workspaces" replicant, the system lost the focus on active window. In the attached screenshot the active window still shows the grey color in the tab, and the close / resize buttons doesn't work. If I click on the diferent apps windows (Terminal, StyleEdit, Clock), the system not active the window. If delete the replicant, the system works fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 21:11:41 2008 From: trac at haiku-os.org (un_spacyar) Date: Mon, 04 Aug 2008 19:11:41 -0000 Subject: [Haiku-bugs] [Haiku] #2566: Workspaces replicant - active window lost focus In-Reply-To: <045.2b87057b23bf5bdc9f90fd1f2dee89bf@haiku-os.org> References: <045.2b87057b23bf5bdc9f90fd1f2dee89bf@haiku-os.org> Message-ID: <054.6561135784eb5a95b21a77cd85348887@haiku-os.org> #2566: Workspaces replicant - active window lost focus --------------------------------------+------------------------------------- Reporter: un_spacyar | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by un_spacyar): * cc: un_spacyar at yahoo.com.ar (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 21:15:40 2008 From: trac at haiku-os.org (julun) Date: Mon, 04 Aug 2008 19:15:40 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.a8d83d1d2b04013ac9f6b50f75426662@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by julun): Hmmm, the last one looks really strange and i can't reproduce it here. What font settings are in use? Did you rebuild the complete image? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 22:26:32 2008 From: trac at haiku-os.org (diver) Date: Mon, 04 Aug 2008 20:26:32 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.acb5942c6121c7674e463bbaab378788@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by diver): Also if one set font size to 18 pt there will be even more layout issues. So I think this bug should be reopened indeed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 23:02:06 2008 From: trac at haiku-os.org (un_spacyar) Date: Mon, 04 Aug 2008 21:02:06 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.56eac7064b62bd9f3a66d195914f93ec@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by un_spacyar): Response to julun: I'm using the default font settings (12 pt). I attach a new screenshot of my Font settings. I didn't rebuild the image. I retested using this image: vmhaiku.r26477.zip -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 4 22:58:19 2008 From: trac at haiku-os.org (schmedly) Date: Mon, 04 Aug 2008 20:58:19 -0000 Subject: [Haiku-bugs] [Haiku] #2567: System reboots just after splash screen Message-ID: <043.31dda0a8636af016c0b979f4447f4d65@haiku-os.org> #2567: System reboots just after splash screen -----------------------+---------------------------------------------------- Reporter: schmedly | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- While booting Haiku rev 26769 the system consistently reboots just after the splash icons and before the default blue background appears. System is an Intel P35 chipset, Xeon E3110 (Core2Duo) Disabling SMP in the boot menu allows the system to boot up without issue. Debug log from failed boot is attached -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 00:03:31 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 04 Aug 2008 22:03:31 -0000 Subject: [Haiku-bugs] [Haiku] #2562: Occasional hang In-Reply-To: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> References: <043.25830970a02c582c2a9cb7076cd123f5@haiku-os.org> Message-ID: <052.2d67e8786dccd428c05a601981c1a9cc@haiku-os.org> #2562: Occasional hang ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26810. It's always interesting when actually all the information where already there. The stack trace is actually quite correct. A timer interrupt (or another hardware exception) happened right when having entered the kernel via an int 99, hence the trap99 + 0x000 return address. The 12 bytes the iframe seemed to be off, are actually 20 bytes (a kernel iframe is 8 bytes shorter), and those are what the int 99 already put on the kernel stack. So this much is correct. The only thing that must not happen in such a situation is kernel exit work, like setting up a signal handler, since we don't even have a userland iframe and thus overwrite kernel stack. Interestingly this resulted in a busy loop in this case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 00:08:21 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 04 Aug 2008 22:08:21 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.83e666cfba4a16dead8c2af89e0e0cc2@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): This bug has a good chance of having been fixed in r26810. Since I've been able to reproduce it (actually haven't even seen it), I can't say that for sure, though. So I'm leaving it open for the time being. Please update, if you encounter it again, or if you don't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 00:09:36 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 22:09:36 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield Message-ID: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> #2568: Implement sched_yield -------------------------+-------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Haiku does not have a {{{sched.h}}} header and the {{{sched_yield}}} function. It appears to be an optional POSIX feature. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 00:10:20 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 22:10:20 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.2c8ea53f985b6b99f799f71ac66bc6f8@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): I'd be interested to help implementing it. Would {{{libroot/os/scheduler.c}}} be a suitable place for it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 01:04:30 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 23:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #2569: [PATCH] vregs does not store EBX Message-ID: <043.402b59bb09d9f37683cfda769b50f229@haiku-os.org> #2569: [PATCH] vregs does not store EBX -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- The x86 {{{vregs}}} structure passed to {{{sigaction}}} signal handlers does not store EBP in the {{{ebp}}} field but in {{{_reserved_2[2]}}}. EBX is not stored at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 01:11:57 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 23:11:57 -0000 Subject: [Haiku-bugs] [Haiku] #2569: [PATCH] vregs does not store EBX In-Reply-To: <043.402b59bb09d9f37683cfda769b50f229@haiku-os.org> References: <043.402b59bb09d9f37683cfda769b50f229@haiku-os.org> Message-ID: <052.d1d4e1edcf16d0f388b3bb18ee5aa404@haiku-os.org> #2569: [PATCH] vregs does not store EBX ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): The attached patch changes {{{arch_setup_signal_frame}}} and {{{arch_restore_signal_frame}}} to store EBP in the {{{ebp}}} field and EBX in {{{_reserved_2[2]}}}, EBP's previous field. This was checked against real-world applications (make, sleep, vim, ftp) and helped with the ongoing port of Mono's JIT. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 01:20:38 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 23:20:38 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.6f3021fe64d59d081903bd8dbd8c3958@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Attached is a first shot at implementing it. It compiles but is still untested. I have no idea if the syscall does the correct thing... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 01:22:02 2008 From: trac at haiku-os.org (julun) Date: Mon, 04 Aug 2008 23:22:02 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.d96d6a14ff3d644cdb3967ec91254654@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by julun): @un_spacyar: I tested against vmhaiku.r26770 and it works there. There where some changes done on BSlider and the layout code depends on that. The popup bug still exists. Can you verify please? @diver: I probably won't change that much on those handcrafted layout stuff, I would wait until we finally can drop R5 support and go with layouts. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 01:43:17 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 04 Aug 2008 23:43:17 -0000 Subject: [Haiku-bugs] [Haiku] #2570: GET_STATS undefined Message-ID: <043.9f195e207d12098216180c13a34c635f@haiku-os.org> #2570: GET_STATS undefined -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- The undefined symbol {{{GET_STATS}}} in {{{h2generic.c}}} currently breaks the build (r26810). Disabling that case works around it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 03:59:05 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 01:59:05 -0000 Subject: [Haiku-bugs] [Haiku] #2570: GET_STATS undefined In-Reply-To: <043.9f195e207d12098216180c13a34c635f@haiku-os.org> References: <043.9f195e207d12098216180c13a34c635f@haiku-os.org> Message-ID: <052.95c15b2189f9ce618a2b23108aca0a58@haiku-os.org> #2570: GET_STATS undefined --------------------------------+------------------------------------------- Reporter: andreasf | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by anevilyak): * owner: oruizdorantes => anevilyak Comment: Fixed in r26811. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 03:59:19 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 01:59:19 -0000 Subject: [Haiku-bugs] [Haiku] #2570: GET_STATS undefined In-Reply-To: <043.9f195e207d12098216180c13a34c635f@haiku-os.org> References: <043.9f195e207d12098216180c13a34c635f@haiku-os.org> Message-ID: <052.8c6980f13717e2dcc78db3d1df20e667@haiku-os.org> #2570: GET_STATS undefined --------------------------------+------------------------------------------- Reporter: andreasf | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 04:15:42 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 05 Aug 2008 02:15:42 -0000 Subject: [Haiku-bugs] [Haiku] #2571: [Tracker] Crash when quiting via reboot/shutdown or processcontroller Message-ID: <041.75f9d0ebe408217c7f41b0d927ccc123@haiku-os.org> #2571: [Tracker] Crash when quiting via reboot/shutdown or processcontroller ----------------------------------+----------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Tracker will crash reliably if you leave an USB disk tracker window open when quiting via reboot/shutdown or processController->quit->Tracker r26812 vmware and real hardware, i think i already saw the bug around r266xx. see attached gdb session -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 04:18:20 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 02:18:20 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.600f9345b2c902308a388b606a23e29e@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): Some more observations that might be relevant to both this and #2511: 1) trying cd /Audio\ CD and typing ls results in an infinite loop of "ls: cannot access : No such file or directory 2) Trying to cp the files from the CD to someplace else results in every track being 7.8KB on the destination for some reason (no errors reported). Tracker however manages to copy all but the last track correctly. In any case, the reported mimetype on the CD for the files is audio/x-wav, the same as on the hard disk. 3) If I try to copy the file via dd if=/Audio\ CD/10.wav of=/boot/home/10.wav bs=2048, I oddly wind up with a *larger* file than the CD reports (CD reports 54.0MB, the file on the hard disk winds up at 54.87). dd does fail with: dd: reading `10.wav': General system error 28093+1 records in 28093+1 records out 57536468 bytes (58MB) copied, 89.8797 s, 640 kB/s 4) When the dd or Tracker copy fails, I see: "KERN: check_sense: Illegal request" in syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 04:19:07 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 02:19:07 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.0343009ac4ba8ef9d744175abd757f49@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): Bah, apologies for that last comment getting mangled. Unfortunately I can't reformat it :( Hope it helps in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 04:22:01 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 02:22:01 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.25d7e104f6fad6daf0beac64adbd81ea@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): Sorry, I was looking at the wrong Tracker window, 54.0MB is the size that was copied by Tracker, the file on the CD is in fact reported as 54.94MB. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 13:22:25 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 11:22:25 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.84e0be6869853fed6c90f565a9cc85e8@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): "os" always means OS APIs, not POSIX APIs. So os/scheduler.c and os/kernel/schduler.h is not where this would be added. Since this is a POSIX feature, it should be put into libroot/posix/sched.c[pp] and headers/posix/sched.h. The syscall looks good. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 13:23:31 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 11:23:31 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.ca0a9d80323e2db3d0a141a15fdf1ad0@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): Oh, BTW, our coding style wants two blank lines between functions (ie. in scheduler.c of your patch). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 14:15:20 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 12:15:20 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted Message-ID: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- For some time, I am occasionally seeing Haiku freeze completely, i.e. it does not react to mouse movements or F12. Serial output says {{{ CPU 0 halted }}} (or {{{CPU 1 halted}}}). There is however no indication what actually leads to this, i.e. the messages before differ, e.g., BFS warnings or "last message repeated two times" or runtime_loader unable to load {{{_APP_}}} or some non-existing file. In all instances this happened under load, running configure or make, last at r26810. (And it happened already before my local signal handler changes.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 15:32:21 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 13:32:21 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.bde6252ae669a9925cedc1144186afca@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Okay, I just didn't want to mix my code into GPL'ed glibc files. A {{{headers/posix/sched.h}}} file was already part of the patch. Actually I didn't yet read the coding guidelines at all... The existing {{{scheduler.c}}} file is wrong then. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 15:43:58 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 13:43:58 -0000 Subject: [Haiku-bugs] [Haiku] #2568: Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.1ddde5cc8590f4f286da786f78d76946@haiku-os.org> #2568: Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Patch updated to use a new {{{libroot/posix/scheduler.cpp}}} file. Compiles okay, untested. With the previous version (and my workarounds reverted), Mono did link okay. No noticable behavioral change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 15:51:43 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 05 Aug 2008 13:51:43 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.718bd0db7e322babd9782ecaa98dc372@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): This is what you get when entering KDL. The usual procedure is that one CPU gets a panic, sends the other CPUs a message to stop them, these acknowledge and go into a loop (that's when the line "CPU x halted" is printed), and then the CPU where panic occured proceeds into the debugger. There are apparently still some race conditions in this, as it can happen that the original CPU doesn't wake up after stopping the others. I reworked those codepaths once, but I can confirm that it sometimes still happens. Though it could also be the code directly after that, as I've also seen a few times that the debugger starts, but then hangs after printing initial output when having the auto_stack_trace debugger module installed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 16:02:45 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 14:02:45 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.4792db03df1c65197820dcd9680dfbd5@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Thanks for these explanations. I believe I have no special settings or modules installed, so it would seem like the initial race condition. Anything I should do to confirm? Is there debug output to enable somewhere? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 16:46:03 2008 From: trac at haiku-os.org (bga) Date: Tue, 05 Aug 2008 14:46:03 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. Message-ID: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- One of the tests I always do under Haiku is to download the source inside itself with svn. Right now I am using a 2 Gb VMWare image. Haiku itself takes around 200 Mb on this image and the 1.8 Gb left was usually enough to hold the source tree but with the latest revision (26815), it says device is full. "df" actually shows that 0 bytes are available but if I run "du -h ." inside the directory where I downloaded Haiku, it says the files themselves take only 511 Mb. I am pretty sure the problem is not space wasted due to block sizes as it used to work before and, also, it seems it is taking almost 4 times the actual required space which does not seem usual. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 16:55:54 2008 From: trac at haiku-os.org (bga) Date: Tue, 05 Aug 2008 14:55:54 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.9db305d9dbac9595e5a36bf3c8711f72@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): FYI, after erasing the directory that contains the Haiku sources with "rm -rf", all the space is reclaimed and I am back at 1.8 Gb free. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 17:01:58 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 05 Aug 2008 15:01:58 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.367c7db39152fcaae19be33c22ca1ba2@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): You could take a look at src/system/kernel/debug/debug.cpp and there kernel_debugger() and kernel_debugger_loop(). The messaging and halting is done in src/system/kernel/smp.c. There's no specific debug output, but you can add to it. The problem is that this kind of stuff is hard to reproduce in general and adding debug output usually has the nasty side effect of hiding the problem because it delays/changes locking/scheduling and such. A good code review is probably the better approach here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 17:02:54 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 15:02:54 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.8a92ffadd9f3484a13225238ea631053@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by anevilyak): I would guess this is related to r26794. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 17:59:26 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 15:59:26 -0000 Subject: [Haiku-bugs] [Haiku] #2568: [PATCH] Implement sched_yield (was: Implement sched_yield) In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.76e62fb953a4c3f795315e59e1d83900@haiku-os.org> #2568: [PATCH] Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Still links and runs as before. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 18:00:59 2008 From: trac at haiku-os.org (bga) Date: Tue, 05 Aug 2008 16:00:59 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.a51a90a5c663b138c541fb934f8f135f@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): Makes sense but only if we are not trimming down the files on close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 18:12:34 2008 From: trac at haiku-os.org (bga) Date: Tue, 05 Aug 2008 16:12:34 -0000 Subject: [Haiku-bugs] [Haiku] #2574: Something wrong with memory calculation. Message-ID: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> #2574: Something wrong with memory calculation. ---------------------------+------------------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ This bug becomes evident when allocating a big chunk of memory in one go. Activity Monitor will report a negative amount of used memory. This does not seem to be an Activity Monitor problem as even sysinfo acts in a weird way. This is what I got before allocating 500 Mb in one go (snippet form sysinfo output): 2013855744 bytes free (used/max 133627904 / 2147483648) (cached 17035264) And with the memory allocated: 1397829632 bytes free (used/max 749654016 / 2147483648) (cached 3696230400) The values for used memory and cache do not look right. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 18:30:31 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 Aug 2008 16:30:31 -0000 Subject: [Haiku-bugs] [Haiku] #2574: Something wrong with memory calculation. In-Reply-To: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> References: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> Message-ID: <047.10ae74f1a763e5023672e4fc90530ddc@haiku-os.org> #2574: Something wrong with memory calculation. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Used memory actually looks like it's in the correct ballpark for an additional 500MB alloc. The fact that the numbers there look more or less sane though makes me suspect vm_page_num_free_pages() is returning the wrong value here, but that implies several possible variables as suspects. Possibly sInactivePageQueue? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 18:48:48 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 05 Aug 2008 16:48:48 -0000 Subject: [Haiku-bugs] [Haiku] #2453: [Tracker] Dragging items in the same window leaves some folders selected In-Reply-To: <041.371104b097b366fb52697ee8144f9ba9@haiku-os.org> References: <041.371104b097b366fb52697ee8144f9ba9@haiku-os.org> Message-ID: <050.97acc761982752648caf322259afb386@haiku-os.org> #2453: [Tracker] Dragging items in the same window leaves some folders selected -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: closed => reopened * resolution: fixed => Comment: It seems it's not completely fixed after all! If you were over a folder and exits the view it belongs (if the icon is near the border of a tracker window or, on the desktop, if it is near the boundaries of an overlapping window. In this case hiliteDropTarget(false) isn't even called. The view doesn't get B_EXITED/ENTERED_VIEW messages since B_POINTER_EVENTS isn't set. It has been deactivated apparently because of the way mouse tracking is done and especially for the selection rect. It will probably need a mouse tracking rewrite for it to be cleanly fixed. Please fix if you're inspired, i won't have time until next week :-) note: contrary to the description, this can happen in any view mode (list,icon etc...) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 18:53:55 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 05 Aug 2008 16:53:55 -0000 Subject: [Haiku-bugs] [Haiku] #2561: bfs_shell no more sems In-Reply-To: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> References: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> Message-ID: <054.5827501ec354f8bee2d93ee89d81b39b@haiku-os.org> #2561: bfs_shell no more sems -------------------------+-------------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: I increase the maximal number of semaphores in r26816. This should at least last a little bit longer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 19:13:26 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 17:13:26 -0000 Subject: [Haiku-bugs] [Haiku] #2569: [PATCH] vregs does not store EBX In-Reply-To: <043.402b59bb09d9f37683cfda769b50f229@haiku-os.org> References: <043.402b59bb09d9f37683cfda769b50f229@haiku-os.org> Message-ID: <052.4099cc5251be437367ab6e7870900c65@haiku-os.org> #2569: [PATCH] vregs does not store EBX ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Applied in r26818. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 19:17:35 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 17:17:35 -0000 Subject: [Haiku-bugs] [Haiku] #2568: [PATCH] Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.e1f588f93f085166aca74bfc72007353@haiku-os.org> #2568: [PATCH] Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): Looks good, do you mind if I remove the /X11 license part? It looks a bit pointless to me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 19:23:23 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 05 Aug 2008 17:23:23 -0000 Subject: [Haiku-bugs] [Haiku] #2568: [PATCH] Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.8955eda566862be70c7b633981065e9f@haiku-os.org> #2568: [PATCH] Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Go ahead, I'm just used to it from other projects. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 19:29:24 2008 From: trac at haiku-os.org (bga) Date: Tue, 05 Aug 2008 17:29:24 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.c4db7830ec0447988f04b695b104cd8f@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): I reverted to r26793 and the same happens, so it was not r26794 that resulted in this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 19:54:47 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 17:54:47 -0000 Subject: [Haiku-bugs] [Haiku] #2568: [PATCH] Implement sched_yield In-Reply-To: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> References: <043.e44c6ff7398f76f0747a5ba326758ca1@haiku-os.org> Message-ID: <052.d3ae39921459f8f913c959df1a1ddd41@haiku-os.org> #2568: [PATCH] Implement sched_yield --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks! I've applied it in r26820. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 20:04:41 2008 From: trac at haiku-os.org (kaliber) Date: Tue, 05 Aug 2008 18:04:41 -0000 Subject: [Haiku-bugs] [Haiku] #2561: bfs_shell no more sems In-Reply-To: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> References: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> Message-ID: <054.574c0e8c9e5a42d25467b46e857d38f1@haiku-os.org> #2561: bfs_shell no more sems -------------------------+-------------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by kaliber): Please close also bug #2520 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 20:42:56 2008 From: trac at haiku-os.org (kaliber) Date: Tue, 05 Aug 2008 18:42:56 -0000 Subject: [Haiku-bugs] [Haiku] #2346: Some of headers are not self containing In-Reply-To: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> References: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> Message-ID: <051.e6b37d7d6b6a946690c0fb328e134cae@haiku-os.org> #2346: Some of headers are not self containing ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kaliber): I've created a complete patch. I skip regex.h fix due to the comment: /* POSIX says that must be included (by the caller) before . */ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 20:49:50 2008 From: trac at haiku-os.org (tqh) Date: Tue, 05 Aug 2008 18:49:50 -0000 Subject: [Haiku-bugs] [Haiku] #1050: implement a WiFi stack In-Reply-To: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> References: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> Message-ID: <054.b79b88dc5d77368faf39d0b417315ae7@haiku-os.org> #1050: implement a WiFi stack ------------------------------------------+--------------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Network & Internet/Wireless | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------------+--------------------------------- Comment(by tqh): Added a basic port of FreeBSD's libcrypto, asm not enabled and some algos disabled. Enough needed to be able to work on net80211 which is WIP. No tests other than that it compiles. (I may have some changes to existing Haiku BSD headers, so contact me if something is fishy). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 20:56:18 2008 From: trac at haiku-os.org (tqh) Date: Tue, 05 Aug 2008 18:56:18 -0000 Subject: [Haiku-bugs] [Haiku] #1050: implement a WiFi stack In-Reply-To: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> References: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> Message-ID: <054.972b88bb0b0baeb24f32784e664858a1@haiku-os.org> #1050: implement a WiFi stack ------------------------------------------+--------------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Network & Internet/Wireless | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------------+--------------------------------- Comment(by tqh): net80211 just added if someone wants to take a look at the code. It does not compile and is nowhere near finished, but I'm working on it when I have the time. Right now I just to fill in missing headers / functions where possible without changing FreeBSD code. Hence the strange code structure. Also an equivalent to ieee80211_freebsd.c is needed for Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 21:13:04 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 19:13:04 -0000 Subject: [Haiku-bugs] [Haiku] #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes In-Reply-To: <042.049c3dcb127418abcb089c84f77dedd2@haiku-os.org> References: <042.049c3dcb127418abcb089c84f77dedd2@haiku-os.org> Message-ID: <051.af8c969cf44e276d8e917fea8f090fb4@haiku-os.org> #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26816; bug #2561 is actually a duplicate of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 21:13:25 2008 From: trac at haiku-os.org (axeld) Date: Tue, 05 Aug 2008 19:13:25 -0000 Subject: [Haiku-bugs] [Haiku] #2561: bfs_shell no more sems In-Reply-To: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> References: <045.3557b3b17b603c1b60a45189587231f3@haiku-os.org> Message-ID: <054.ca830b0849b383963c91909fef3bd52a@haiku-os.org> #2561: bfs_shell no more sems -------------------------+-------------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Comment(by axeld): Thanks for the note! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 21:29:51 2008 From: trac at haiku-os.org (Hubert) Date: Tue, 05 Aug 2008 19:29:51 -0000 Subject: [Haiku-bugs] [Haiku] #2575: The KDL during mount of partition FAT Message-ID: <041.e6805a8c98cad18b17b3fe9ca30e6fbb@haiku-os.org> #2575: The KDL during mount of partition FAT --------------------------+------------------------------------------------- Reporter: Hubert | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- When I want mount FAT partition I have screen of KDL. Haiku rev. 26804 Athlon64 X2 4600+ 1GB RAM GF6150 HDD ATA 160 GB - partition with Haiku is here HDD SATA 250 GB - FAT(102GB) partition is here DVDRW SATA -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 21:33:55 2008 From: trac at haiku-os.org (Hubert) Date: Tue, 05 Aug 2008 19:33:55 -0000 Subject: [Haiku-bugs] [Haiku] #2575: The KDL during mount of partition FAT In-Reply-To: <041.e6805a8c98cad18b17b3fe9ca30e6fbb@haiku-os.org> References: <041.e6805a8c98cad18b17b3fe9ca30e6fbb@haiku-os.org> Message-ID: <050.7980255d8c3765bc9b91095f15ca3bb5@haiku-os.org> #2575: The KDL during mount of partition FAT ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by Hubert): rev. 26744 too -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 22:08:43 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 05 Aug 2008 20:08:43 -0000 Subject: [Haiku-bugs] [Haiku] #757: [app_server] deadlock on workspace switching In-Reply-To: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> References: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> Message-ID: <049.b3a8b46de1b8ad563b778eb2bbf75dda@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by scottmc): Can anyone other than diver reproduce this? I wasn't able to... If this stays open I think it should be moved from R1/alpha to R1, that is unless someone else is able to reproduce it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 5 20:42:56 2008 From: trac at haiku-os.org (kaliber) Date: Tue, 05 Aug 2008 18:42:56 -0000 Subject: [Haiku-bugs] [Haiku] #2346: Some of headers are not self containing In-Reply-To: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> References: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> Message-ID: <051.e6b37d7d6b6a946690c0fb328e134cae@haiku-os.org> #2346: Some of headers are not self containing ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kaliber): I've created a complete patch. I skip regex.h fix due to the comment: /* POSIX says that must be included (by the caller) before . */ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 00:18:13 2008 From: trac at haiku-os.org (korli) Date: Tue, 05 Aug 2008 22:18:13 -0000 Subject: [Haiku-bugs] [Haiku] #2559: [pthreads] Define PTHREAD_STACK_MIN In-Reply-To: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> References: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> Message-ID: <052.d52a0d5fcda51b27d634fee4dd5760cf@haiku-os.org> #2559: [pthreads] Define PTHREAD_STACK_MIN --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Comment(by korli): Replying to [comment:1 bonefish]: > {{{PTHREAD_STACK_MIN}}} is not part of the POSIX standard (at least it's not supposed to be defined in or ), and I wouldn't even know what kind of value it is supposed to PTHREAD_STACK_MIN should be defined in limits.h. Our pthread_attr_setstacksize() checks against MIN_USER_STACK_SIZE whereas it should be PTHREAD_STACK_MIN. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 02:26:46 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 00:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.282ce01b856a02531cadc5f0a4be87b5@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): I can almost reliably reproduce it at r26820. It seems related to the new XSI semaphores. At commit {{{5de9faef96e4d575a62a8525429c701eaf8cd7c6}}} of my Git branch of Mono, executing {{{mono}}} with either some copied-over hello.exe or the monolite {{{mcs.exe}}} (e.g., as part of bootstrapping with `make`) appears to make heavy use of them, according to serial output, and halts the CPU while aborting. If I configure with {{{--disable-shared- handles}}}, it shows no such XSI activity and aborts okay, without halting the CPU. Still not really suited for debugging though. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 02:33:04 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 00:33:04 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.3b37d39b5f10c64737b67dc45c293d7f@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): {{{ runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mscorlib.dll.so xsi_semget: key = 3, numberOfSemaphores = 8, flags = 384 xsi_semget: key 3 does not exist, but the caller did not ask for creation xsi_semget: key = 1292045439, numberOfSemaphores = 8, flags = 1920 xsi_semctl: semaphoreID = 1, semaphoreNumber = 0, command = 9 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 0 Last message repeated 7 times. xsi_semop: semaphoreID = 1, ops = 0x7ffedbd4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffedbd4, numOps = 1 xsi_semop: semaphoreNumber = 7, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 7, value = 1 xsi_semop: semaphoreID = 1, ops = 0x7ffedbc4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mcs.exe.so runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mcs.exe.so xsi_semop: semaphoreID = 1, ops = 0x7ffed0c8, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffed0c8, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffecbc8, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffecbc8, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed0e8, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 86564, semaphoreSetID = 1, semaphoreNumber = 6, value = 0 xsi_semctl: semaphoreID = 1, semaphoreNumber = 7, command = 4 xsi_semctl: semaphoreID = 1, semaphoreNumber = 0, command = 0 XsiSemaphoreSet::~XsiSemaphoreSet(): removing semaphore set XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 0 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 1 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 2 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 3 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 4 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 5 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 6 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 7 CPU 0 halted! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 02:38:38 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 06 Aug 2008 00:38:38 -0000 Subject: [Haiku-bugs] [Haiku] #2574: Something wrong with memory calculation. In-Reply-To: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> References: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> Message-ID: <047.6da861410447e4ad48e33de6eceaf9f2@haiku-os.org> #2574: Something wrong with memory calculation. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should be fixed in r26837. Note that a huge allocation won't show up, unless it is fully locked or until the memory is touched. The values now reported by get_system_info() reflect the actual page usage instead of the memory commitment. It wouldn't be too difficult to change that, if the general preference is otherwise. I haven't tested what BeOS does. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 08:28:25 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 06 Aug 2008 06:28:25 -0000 Subject: [Haiku-bugs] [Haiku] #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call Message-ID: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- On a fresh vmware development image, r26837, I downloaded a tarball of a port I was going to try, and when I tried to use expander to open it got dropped into KDL. PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call Welcome to Kernel Debugging Land... Thread 193 "tar" running on CPU 0 {{{ PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call Welcome to Kernel Debugging Land... Thread 193 "tar" running on CPU 0 kdebug> bt stack trace for thread 193 "tar" kernel stack: 0x929a0000 to 0x929a4000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 929a35f4 (+ 48) 800544ed :invoke_debugger_command + 0x00ed 1 929a3624 (+ 64) 800542e5 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 929a3664 (+ 64) 8005462d :invoke_debugger_command_pipe + 0x009d 3 929a36a4 (+ 48) 80055508 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 929a36d4 (+ 48) 80054ebe :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 929a3704 (+ 224) 800568d4 :evaluate_debug_command + 0x0088 6 929a37e4 (+ 64) 80052962 :kernel_debugger_loop__Fv + 0x01ae 7 929a3824 (+ 48) 800534fb :kernel_debugger + 0x0117 8 929a3854 (+ 192) 800533d9 :panic + 0x0029 9 929a3914 (+ 96) 80029c40 :get_cached_block__FP11block_cachexPbb + 0x015c 10 929a3974 (+ 80) 8002ca42 :block_cache_get_etc + 0x004e 11 929a39c4 (+ 48) 8002caf4 :block_cache_get + 0x0020 12 929a39f4 (+ 96) 80586d39 :InternalSetTo__10CachedNodeP11Transactionx + 0x014d 13 929a3a54 (+ 48) 805867c9 :SetTo__10CachedNodexb + 0x00d1 14 929a3a84 (+ 64) 80587ff3 :_FindFreeDuplicateFragment__9BPlusTreeR11TransactionPC14bplustree_nodeR10CachedNodePxPP14bplustree_nodePUl + 0x008b 15 929a3ac4 (+ 176) 80588548 :_InsertDuplicate__9BPlusTreeR11TransactionR10CachedNodePC14bplustree_nodeUsx + 0x0494 16 929a3b74 (+ 480) 80589400 :Insert__9BPlusTreeR11TransactionPCUcUsx + 0x0460 17 929a3d54 (+ 80) 8058df05 :Update__5IndexR11TransactionPCclPCUcUsT4UsP5Inode + 0x0245 18 929a3da4 (+ 96) 8058e245 :UpdateSize__5IndexR11TransactionP5Inode + 0x00a1 19 929a3e04 (+ 96) 8059e9bd :bfs_free_cookie__FP9fs_volumeP8fs_vnodePv + 0x020d 20 929a3e64 (+ 48) 80089d44 :file_free_fd__FP15file_descriptor + 0x0028 21 929a3e94 (+ 48) 80079a4c :put_fd + 0x0038 22 929a3ec4 (+ 64) 80079b36 :close_fd_index + 0x0032 23 929a3f04 (+ 32) 8007a631 :common_close__Fib + 0x0031 24 929a3f24 (+ 32) 8007af08 :_user_close + 0x0018 25 929a3f44 (+ 100) 800b6d42 :pre_syscall_debug_done + 0x0002 (nearest) user iframe at 0x929a3fa8 (end = 0x929a4000) eax 0x85 ebx 0x2f0b18 ecx 0x7ffeee10 edx 0xffff0104 esi 0xf62 edi 0x1802e400 ebp 0x7ffeee3c esp 0x929a3fdc eip 0xffff0104 eflags 0x207 user esp 0x7ffeee10 vector: 0x63, error code: 0x0 26 929a3fa8 (+ 0) ffff0104 27 7ffeee3c (+ 80) 00211f20 <_APP_>:extr_init + 0x0f58 (nearest) 28 7ffeee8c (+ 48) 00212c16 <_APP_>:extract_archive + 0x0176 29 7ffeeebc (+ 144) 0021851d <_APP_>:read_and + 0x01a1 30 7ffeef4c (+ 48) 002238c8 <_APP_>:main + 0x0178 31 7ffeef7c (+ 48) 00208df7 <_APP_>:_start + 0x005b 32 7ffeefac (+ 48) 001008ea 4421:runtime_loader_seg0ro at 0x00100000 + 0x8ea 33 7ffeefdc (+ 0) 7ffeefec 4420:tar_main_stack at 0x7efef000 + 0xffffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 08:40:56 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 06 Aug 2008 06:40:56 -0000 Subject: [Haiku-bugs] [Haiku] #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call In-Reply-To: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> References: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> Message-ID: <051.09661e169176bede7013787deb6370e1@haiku-os.org> #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Ok, so it's not just Tar that triggers this. I gunzipped and tar -xf'd it on the command line and then tried running ./configure and got the same panic but in "sh" just a few lines into the configure. Attaching a second serial log file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 10:50:30 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 06 Aug 2008 08:50:30 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.949566ff70a115c16cc9911044de6c6d@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): xsi semaphore debug output looks fine to me. I don't think it's related. Although they might lead to KDL, they have nothing to do with halting the CPU. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:22:55 2008 From: trac at haiku-os.org (nielx) Date: Wed, 06 Aug 2008 09:22:55 -0000 Subject: [Haiku-bugs] [Haiku] #2456: bugs.haiku-os.org doesn't work anymore In-Reply-To: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> References: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> Message-ID: <054.536b539102542a90ff2ce50ce02e4f2e@haiku-os.org> #2456: bugs.haiku-os.org doesn't work anymore -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------+-------------------------------------------------- Changes (by nielx): * status: assigned => closed * resolution: => fixed Comment: bugs.haiku-os.org will now redirect to dev.haiku-os.org. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:28:01 2008 From: trac at haiku-os.org (nielx) Date: Wed, 06 Aug 2008 09:28:01 -0000 Subject: [Haiku-bugs] [Haiku] #2204: Missing or invalid form token. Do you have cookies enabled? In-Reply-To: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> References: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> Message-ID: <059.99fa49979bc8d50c78b2aa5917535029@haiku-os.org> #2204: Missing or invalid form token. Do you have cookies enabled? ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by nielx): Was this before or after the move to Trac 0.11? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:48:38 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 09:48:38 -0000 Subject: [Haiku-bugs] [Haiku] #2574: Something wrong with memory calculation. In-Reply-To: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> References: <038.e3789ba576e8a5eb7113f60ca48882ea@haiku-os.org> Message-ID: <047.c6614b7c0281034797cd56d79d4ec51a@haiku-os.org> #2574: Something wrong with memory calculation. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): I like it as is; that just makes more sense to me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:52:43 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 09:52:43 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.9d6a029d0cfb157f5e0dd0ead1455e0b@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): I wouldn't be so sure about that, though :-) Maybe you could add debug output at the beginning and end of every XSI sem function, and see if it's inside it or not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:53:00 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 09:53:00 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.1a199d47cc7eaf4c2a12753ac5573a94@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:53:20 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 09:53:20 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.c76030064b6d5193db8529108eafbd26@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => critical -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 11:59:18 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 09:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.153f4a01a57e94df269ffcc19f2dbbc0@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Entering KDL is what halts the CPUs, so when there is a panic from XSI sems then it indirectly does halt the CPUs. It would be interesting which panic is triggered as it might be in a situation that leads to this situation reliably. Maybe there is interrupt disabling or spinlocking involved? I could certainly imagine that a spinlock could lead to such a situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:01:21 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 10:01:21 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.0e3549e0f7ad44abd2e570188640c332@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): My wording was unfortunate, I regret; I'm not saying XSI semaphores are the ''cause'' of this, they just seem a way to ''trigger'' it. As Michael said earlier, halting the CPU is part of KDL, so if the semaphores not only lead to KDL but also happen to lead to this deadlock, for whatever reason, we'd have a way to reproduce this bug. For me it is 100% reproducible this way (and apart from that, "occasionally" referred to multiple times a day). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:03:28 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 06 Aug 2008 10:03:28 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.0d43dae47d1199afcfd2dafd4f784b70@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Currently the only spinlock used is the global team one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:04:05 2008 From: trac at haiku-os.org (nielx) Date: Wed, 06 Aug 2008 10:04:05 -0000 Subject: [Haiku-bugs] [Haiku] #2204: Missing or invalid form token. Do you have cookies enabled? In-Reply-To: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> References: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> Message-ID: <059.0d69cf3080788aa066419656174208b9@haiku-os.org> #2204: Missing or invalid form token. Do you have cookies enabled? ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by nielx): * status: new => closed * resolution: => invalid Comment: I see: before. In that case I'm closing this ticket. Please reopen if it occurs again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:14:14 2008 From: trac at haiku-os.org (nielx) Date: Wed, 06 Aug 2008 10:14:14 -0000 Subject: [Haiku-bugs] [Haiku] #2423: New Trac shortens Timeline feed messages In-Reply-To: <043.b625a93d9db6fb6b5da9fa49b64308a3@haiku-os.org> References: <043.b625a93d9db6fb6b5da9fa49b64308a3@haiku-os.org> Message-ID: <052.7e8c80a64105b45b32f72991049074c7@haiku-os.org> #2423: New Trac shortens Timeline feed messages ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: nielx Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: Resolution: | Blockedby: 2449 Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by nielx): * owner: haiku-web => nielx * status: new => assigned Comment: Upstream ticket: [http://trac.edgewall.org/ticket/7316 #7136] Since this is now an official ticket (and even scheduled), I'm going to assign the ticket to me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:15:28 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 10:15:28 -0000 Subject: [Haiku-bugs] [Haiku] #2346: Some of headers are not self containing In-Reply-To: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> References: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> Message-ID: <051.ca10933139371f213ce2f8ebb97204ac@haiku-os.org> #2346: Some of headers are not self containing ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): Patch applied in r26841. I guess this is only a part of this ticket? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 12:28:49 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 06 Aug 2008 10:28:49 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.40ad3eaf063dca9cd246ad88ae4256b7@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Then don't update, because I'm currently in the process of reworking the way undo requests are handled and I'm removing the global spinlock in favour of a private mutex. I'm glad my bugs help to find other bugs. :-). Anyway, from the debug output it seems to be in the semctl function, and it seems that it happens when it tries to remove the last undo request. Functions involved is http://dev.haiku- os.org/browser/haiku/trunk/src/system/kernel/posix/xsi_semaphore.cpp#L513 That's what might trigger the panic, but not the cause of your problem as you said. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:24:44 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 11:24:44 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.aa864ed940422033133239aabbb8561b@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Andreas, you could disable SMP from the bootmenu and then retest that. Without SMP the original panic should run through so you can get a stacktrace. If you could attach that here that'd be most helpful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:30:32 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 11:30:32 -0000 Subject: [Haiku-bugs] [Haiku] #757: [app_server] deadlock on workspace switching In-Reply-To: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> References: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> Message-ID: <049.0e93b3581a324bddd5b55ca0d73ac2e9@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1/alpha1 => R1 Comment: I completely agree. While deadlocking the app_server is truly unfortunate, if one has to try that hard to do it (I didn't manage to do so), it shouldn't stop the alpha. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:30:53 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 11:30:53 -0000 Subject: [Haiku-bugs] [Haiku] #757: [app_server] deadlock on workspace switching In-Reply-To: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> References: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> Message-ID: <049.983b8be8acb0f235b712ceff16fb1f40@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * priority: blocker => critical -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:34:11 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 11:34:11 -0000 Subject: [Haiku-bugs] [Haiku] #1830: Tracker Desktop windows sometimes stops drawing In-Reply-To: <040.9671640cb5c88b8e9fb09caed6da1373@haiku-os.org> References: <040.9671640cb5c88b8e9fb09caed6da1373@haiku-os.org> Message-ID: <049.029cb7e1ecdd4adfcb9c819395ed4ae7@haiku-os.org> #1830: Tracker Desktop windows sometimes stops drawing ---------------------------------+------------------------------------------ Reporter: axeld | Owner: stippi Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: IIRC this has been fixed a long time ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:36:44 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 11:36:44 -0000 Subject: [Haiku-bugs] [Haiku] #2155: get_writable_cached_block: invalid block number 132376871987246 (max 6902263) In-Reply-To: <041.42a4bea31a3988966a76597fdbbb46f7@haiku-os.org> References: <041.42a4bea31a3988966a76597fdbbb46f7@haiku-os.org> Message-ID: <050.b7bf29b01d0c3916d17c7f6a1d33972a@haiku-os.org> #2155: get_writable_cached_block: invalid block number 132376871987246 (max 6902263) ----------------------------+----------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: I would guess this was caused by some corruption that is likely to have been fixed by now. Please reopen if it happens again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:39:01 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 11:39:01 -0000 Subject: [Haiku-bugs] [Haiku] #2367: Media checker blocks in USB when booting from USB In-Reply-To: <040.071b43b6611ddf637fa7f5a2c6cebc5e@haiku-os.org> References: <040.071b43b6611ddf637fa7f5a2c6cebc5e@haiku-os.org> Message-ID: <049.da05f7cc534d12de3c0cfe44026c4caa@haiku-os.org> #2367: Media checker blocks in USB when booting from USB --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by axeld): * priority: high => normal * milestone: R1/alpha1 => R1 Comment: Since the lockup is gone, I'm changing the milestone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 13:47:10 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 11:47:10 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.bb56e70fa8ac92e07a48b1c056a57bb9@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Is this the same as #2574 and could now be closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:05:43 2008 From: trac at haiku-os.org (kaliber) Date: Wed, 06 Aug 2008 12:05:43 -0000 Subject: [Haiku-bugs] [Haiku] #2346: Some of headers are not self containing In-Reply-To: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> References: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> Message-ID: <051.697f32027ab1e0ad0592d323489af571@haiku-os.org> #2346: Some of headers are not self containing ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kaliber): In my opinion the patch is a complete. To be sure check it using simple script included in the first comment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:07:22 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 12:07:22 -0000 Subject: [Haiku-bugs] [Haiku] #2143: KDL in net timer. In-Reply-To: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> References: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> Message-ID: <047.1bc2764be0ad7d3a4870e8ea68f73ddd@haiku-os.org> #2143: KDL in net timer. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by bga): I never got this anymore. Is this still an issue to anyone? If not, maybe it can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:08:40 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 12:08:40 -0000 Subject: [Haiku-bugs] [Haiku] #2178: svn hangs during checkout. In-Reply-To: <038.94bedc511106776468d63f07f7343e0f@haiku-os.org> References: <038.94bedc511106776468d63f07f7343e0f@haiku-os.org> Message-ID: <047.2716f2364753cf02569643842ad684a3@haiku-os.org> #2178: svn hangs during checkout. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by bga): * status: new => closed * resolution: => fixed Comment: Somehow, this seems to have cured itself. Closing it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:11:34 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 12:11:34 -0000 Subject: [Haiku-bugs] [Haiku] #2390: Can't switch resolution in VESA mode. In-Reply-To: <038.8dbd5e29174cc8e1bc5d34ca103c4658@haiku-os.org> References: <038.8dbd5e29174cc8e1bc5d34ca103c4658@haiku-os.org> Message-ID: <047.bc3e99c366e0f7a453c86453ceafae0b@haiku-os.org> #2390: Can't switch resolution in VESA mode. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: fixed | Blockedby: Platform: x64 | Blocking: -------------------------------+-------------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: This has been fixed. Closing it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:13:09 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 12:13:09 -0000 Subject: [Haiku-bugs] [Haiku] #2141: Weird cache behaviour. In-Reply-To: <038.ee5ad1e490c844c0320bbccddc14a7f2@haiku-os.org> References: <038.ee5ad1e490c844c0320bbccddc14a7f2@haiku-os.org> Message-ID: <047.c84ff94d3118e225ffe245955b9c8fff@haiku-os.org> #2141: Weird cache behaviour. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: low | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: This seems to be a moot point now with recent fixes from Ingo. Closing this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:19:44 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 12:19:44 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.c1a6d5161f92807d30c29d54fe63e143@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): I tried disabling CPU 1 in ProcessController (i.e., only CPU 0 left). In that case funnily it ends in {{{ CPU 1 halted! }}} Will try the bootmenu next. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:24:55 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 06 Aug 2008 12:24:55 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.e570c674586625f7312f26c627ff022d@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): I think this one might actually have been fixed by Ingo's changes to the low memory handler ... iirc he did double check about this and was seeing it correctly balancing. In any case it's a somewhat different issue from #2574 since the latter purely had to do with the statistics reported in get_system_info(), and wasn't really tied to the reservation mechanism that I'm aware of. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:25:40 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 06 Aug 2008 12:25:40 -0000 Subject: [Haiku-bugs] [Haiku] #2204: Missing or invalid form token. Do you have cookies enabled? In-Reply-To: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> References: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> Message-ID: <059.d2f80393c552a851d0f747bd54afac14@haiku-os.org> #2204: Missing or invalid form token. Do you have cookies enabled? ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by marcusoverhagen): Yes that was before switching to 0.11. I haven't seen the problem recently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:26:54 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 12:26:54 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.a0f329bc28be35affe3a05b4874a44b2@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Yeah, that's expected. Disabling the CPU only instructs the scheduler not to schedule any threads on that CPU, but the CPU keeps running and entering KDL still requires halting it. That you get "CPU 1 halted" is therefore correct, as the thread that enters KDL must run on CPU 0 and therefore it's CPU 0 sending CPU 1 the halt message, hence the "CPU 1 halted" output (CPU 0 is not halted, it's running the kernel debugger loop). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:29:20 2008 From: trac at haiku-os.org (VinDuv) Date: Wed, 06 Aug 2008 12:29:20 -0000 Subject: [Haiku-bugs] [Haiku] #1708: Select Play from Sounds prefs freezes system In-Reply-To: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> References: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> Message-ID: <049.69e6db1b29ea6b5548e6a0996dcb88cc@haiku-os.org> #1708: Select Play from Sounds prefs freezes system ----------------------------+----------------------------------------------- Reporter: el-al | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by VinDuv): It seems r26827 fixed this (tested Sounds prefpane and MediaPlayer in r26841 on real hardware with Auich ICH). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 14:56:15 2008 From: trac at haiku-os.org (tqh) Date: Wed, 06 Aug 2008 12:56:15 -0000 Subject: [Haiku-bugs] [Haiku] #2143: KDL in net timer. In-Reply-To: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> References: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> Message-ID: <047.fed094d7f00ad5c2c65b5d99390d0617@haiku-os.org> #2143: KDL in net timer. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by tqh): I'm the only cc, and I've never seen it. I just watch for Firefox related problems. So I think it can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 15:00:37 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 13:00:37 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.c5ac4958d35619b9680aa87e69823428@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): Ha, no KDL without SMP! Instead this: {{{ runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mscorlib.dll.so xsi_semget: key = 1176174592, numberOfSemaphores = 8, flags = 384 xsi_semget: key 1176174592 does not exist, but the caller did not ask for creation xsi_semget: key = 1292045451, numberOfSemaphores = 8, flags = 1920 xsi_semctl: semaphoreID = 1, semaphoreNumber = 0, command = 9 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 0 Last message repeated 7 times. xsi_semop: semaphoreID = 1, ops = 0x7ffedbd4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffedbd4, numOps = 1 xsi_semop: semaphoreNumber = 7, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 7, value = 1 xsi_semop: semaphoreID = 1, ops = 0x7ffedbc4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mcs.exe.so runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mcs.exe.so xsi_semop: semaphoreID = 1, ops = 0x7ffed1d4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed1c4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed1d4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffed1c4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffed1d4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffed1c4, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 bfs: bfs_read_link:1368: Invalid Argument runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/System.Xml.dll.so bfs: bfs_read_link:1368: Invalid Argument runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/System.dll.so xsi_semop: semaphoreID = 1, ops = 0x7ffed8b0, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 3, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffed8b0, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 48549, semaphoreSetID = 1, semaphoreNumber = 2, value = 0 xsi_semop: semaphoreID = 1, ops = 0x70013ed8, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 XsiSemaphore::Add: potentially going to sleep XsiSemaphore::Wait: going to sleep vm_soft_fault: va 0xeea000 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xeea01c, ip 0x31bd15, write 0, user 1, thread 0xbda5 vm_page_fault: sending team "mono" 0xbda5 SIGSEGV, ip 0x31bd15 ("mono_seg0ro" +0x11bd15) stack trace: 0x0031d6ec (mono_seg0ro + 0x11d6ec) 0x0031d8ae (mono_seg0ro + 0x11d8ae) 0x0031da99 (mono_seg0ro + 0x11da99) 0x00415d06 (mono_seg0ro + 0x215d06) 0x180711b1 (heap + 0x711b1) 0x180706c1 (heap + 0x706c1) 0x18070478 (heap + 0x70478) 0x18070432 (heap + 0x70432) 0x180703cd (heap + 0x703cd) 0x18070258 (heap + 0x70258) 0x1806fabb (heap + 0x6fabb) 0x1806ee3a (heap + 0x6ee3a) 0x18067983 (heap + 0x67983) 0x180640a5 (heap + 0x640a5) 0x00398691 (mono_seg0ro + 0x198691) 0x002d9f0c (mono_seg0ro + 0xd9f0c) 0x002db3af (mono_seg0ro + 0xdb3af) 0x002dae9a (mono_seg0ro + 0xdae9a) 0x0022d725 (mono_seg0ro + 0x2d725) 0x0022d7f0 (mono_seg0ro + 0x2d7f0) 0x0022e9c3 (mono_seg0ro + 0x2e9c3) 0x0022c9b7 (mono_seg0ro + 0x2c9b7) 0x0022c86f (mono_seg0ro + 0x2c86f) 0x001008ea (runtime_loader_seg0ro + 0x8ea) 0x7ffedfec (mono_main_stack + 0xffffec) vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x800b6364, write 0, user 0, thread 0xbda5 xsi_semop: back to life xsi_semop: semaphore set id 1 got destroyed xsi_sem_undo: TeamID = 48549, SemaphoreSetID = 1, SemaphoreNumber = 6, undo value = 0 xsi_sem_undo: TeamID = 48549, SemaphoreSetID = 1, SemaphoreNumber = 7, undo value = 1 xsi_sem_undo: TeamID = 48549, SemaphoreSetID = 1, SemaphoreNumber = 3, undo value = -1 xsi_sem_undo: TeamID = 48549, SemaphoreSetID = 1, SemaphoreNumber = 2, undo value = -1 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 15:05:01 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 06 Aug 2008 13:05:01 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization In-Reply-To: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> References: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> Message-ID: <051.9cbfed3f85f58067a282de5b19b2bf23@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization --------------------------------------+------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by scottmc): Give me some more time to try this again, been having trouble getting it to where I can boot off of one drive and try to install to the other dual partitioned drive reliably in recent builds. I'll try it again next week I hope. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 15:07:36 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 06 Aug 2008 13:07:36 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization In-Reply-To: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> References: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> Message-ID: <051.e9be96027e78e7e59ae0253a0c2b35ca@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization --------------------------------------+------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by anevilyak): r26828 did warn that things would probably be unstable for a bit as the I/O scheduler / DMA work is more thoroughly integrated, so you might want to keep a watch on the commits list for further work on that before trying again, as that's likely the cause of your current issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 15:52:45 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 13:52:45 -0000 Subject: [Haiku-bugs] [Haiku] #2143: KDL in net timer. In-Reply-To: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> References: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> Message-ID: <047.8a1e41b0b9f7aa8b666f999a8548c366@haiku-os.org> #2143: KDL in net timer. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by axeld): The original problem is still persistent, and is waiting for a fix, I just didn't get around doing it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 16:13:01 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 14:13:01 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.d767379beeecaa169dd3b408f1b902da@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): That output looks more like a "normal" application bug in mono though. A stack trace from the user debugger would be a bit more readable, but what you see there shouldn't be a kernel bug. Well, then it's "unfortunate" that you don't get KDL without SMP, as this makes it trickier to pinpoint. As suggested originally a code review of the SMP code that does the halting and the KDL entry codepath would likely be a good idea. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 16:22:48 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 14:22:48 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock Message-ID: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> #2577: Panic: _mutex_lock(): double lock -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- The following panic was reproducible by executing a Hello World with mono (with shared handles not deactivated) with SMP disabled in the boot menu. {{{ runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mscorlib.dll.so xsi_semget: key = 1292045451, numberOfSemaphores = 8, flags = 384 xsi_semop: semaphoreID = 1, ops = 0x7ffeebd4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffeebd4, numOps = 1 xsi_semop: semaphoreNumber = 7, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 7, value = 1 xsi_semop: semaphoreID = 1, ops = 0x7ffeebc4, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 6, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee844, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 runtime_loader: cannot open file /ToBe/Mono/hello.exe.so runtime_loader: cannot open file /ToBe/Mono/hello.exe.so runtime_loader: cannot open file /ToBe/Mono/mcs/class/lib/monolite/mscorlib.dll.so xsi_semop: semaphoreID = 1, ops = 0x7ffee800, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: new record added. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee7f0, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee800, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffee7f0, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee800, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffee7f0, numOps = 1 xsi_semop: semaphoreNumber = 2, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 2, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee85c, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffee85c, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee35c, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = 0 xsi_semop: semaphoreID = 1, ops = 0x7ffee35c, numOps = 1 xsi_semop: semaphoreNumber = 3, value = 0 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 3, value = -1 xsi_semop: semaphoreID = 1, ops = 0x7ffee87c, numOps = 1 xsi_semop: semaphoreNumber = 6, value = 1 xsi_semop: semaphore acquired succesfully XsiSemaphore::RecordUndo: found record. Team = 49333, semaphoreSetID = 1, semaphoreNumber = 6, value = 0 xsi_semctl: semaphoreID = 1, semaphoreNumber = 7, command = 4 xsi_semctl: semaphoreID = 1, semaphoreNumber = 0, command = 0 XsiSemaphoreSet::~XsiSemaphoreSet(): removing semaphore set XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 0 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 1 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 2 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 3 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 4 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 5 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 6 XsiSemaphore::ClearUndos: semaphoreSetID = 1, semaphoreNumber = 7 PANIC: _mutex_lock(): double lock of 0x90eb7318 by thread 49333 Welcome to Kernel Debugging Land... Thread 49333 "mono" running on CPU 0 kdebug> bt stack trace for thread 49333 "mono" kernel stack: 0x93f30000 to 0x93f34000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 93f336f4 (+ 48) 80054379 :invoke_debugger_command + 0x00ed 1 93f33724 (+ 64) 80054171 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 93f33764 (+ 64) 800544b9 :invoke_debugger_command_pipe + 0x009d 3 93f337a4 (+ 48) 80055394 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 93f337d4 (+ 48) 80054d4a :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 93f33804 (+ 224) 80056760 :evaluate_debug_command + 0x0088 6 93f338e4 (+ 64) 800527ee :kernel_debugger_loop__Fv + 0x01ae 7 93f33924 (+ 48) 80053387 :kernel_debugger + 0x0117 8 93f33954 (+ 192) 80053265 :panic + 0x0029 9 93f33a14 (+ 64) 8003765c :_mutex_lock + 0x00e0 10 93f33a54 (+ 64) 8002e58f :file_cache_set_size + 0x003b 11 93f33a94 (+ 48) 80593878 :SetFileSize__5InodeR11Transactionx + 0x00bc 12 93f33ac4 (+ 352) 80593a5d :Free__5InodeR11Transaction + 0x0029 13 93f33c24 (+ 80) 8059c343 :bfs_remove_vnode__FP9fs_volumeP8fs_vnodeb + 0x00b3 14 93f33c74 (+ 48) 80083b5f :free_vnode__FP5vnodeb + 0x00af 15 93f33ca4 (+ 48) 80083cf5 :dec_vnode_ref_count__FP5vnodebT1 + 0x0119 16 93f33cd4 (+ 32) 800883ea :vfs_put_vnode + 0x001e 17 93f33cf4 (+ 32) 8002f899 :ReleaseStoreRef__12VMVnodeCache + 0x0015 18 93f33d14 (+ 48) 800abaf7 :RemoveArea__7VMCacheP7vm_area + 0x006f 19 93f33d44 (+ 64) 800a4cbb :delete_area__FP16vm_address_spaceP7vm_area + 0x009b 20 93f33d84 (+ 48) 800a6ba9 :vm_delete_areas + 0x0079 21 93f33db4 (+ 48) 800aa6bb :vm_delete_address_space + 0x0033 22 93f33de4 (+ 96) 80049531 :team_delete_team + 0x0245 23 93f33e44 (+ 128) 8004cb4c :thread_exit + 0x0364 24 93f33ec4 (+ 64) 80042d00 :handle_signals + 0x0384 25 93f33f04 (+ 64) 8004cf4e :thread_at_kernel_exit + 0x0076 26 93f33f44 (+ 100) 800b69cb :kernel_exit_handle_signals + 0x0006 (nearest) user iframe at 0x93f33fa8 (end = 0x93f34000) eax 0x0 ebx 0x6beb38 ecx 0x7ffee928 edx 0x200246 esi 0x6c2760 edi 0x1 ebp 0x7ffee954 esp 0x93f33fdc eip 0xffff0104 eflags 0x200217 user esp 0x7ffee928 vector: 0x63, error code: 0x0 27 93f33fa8 (+ 0) ffff0104 7ffee954 -- read fault kdebug> continue }}} Trying to `continue` results in a freeze, without any further serial output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 16:35:40 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 06 Aug 2008 14:35:40 -0000 Subject: [Haiku-bugs] [Haiku] #1970: VM's sAvailableMemory counter is possibly inaccurate In-Reply-To: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> References: <044.e921a4a64e1421d6e6a9995b312a64a9@haiku-os.org> Message-ID: <053.388014ce5b2a813bd772cf897d90b423@haiku-os.org> #1970: VM's sAvailableMemory counter is possibly inaccurate ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: reopened => closed * resolution: => fixed Comment: I think the original problem this ticket was about was already fixed by Axel in r24742. After that kernel memory leaks remained, which have been fixed, and the running low on available (i.e. non-committed) memory didn't trigger the low memory handler (only when running low on free pages that happened), but this has also been fixed in the meantime. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 17:25:35 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 15:25:35 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.bc4667aa09505a0b87a2ef3c52bcab0c@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): Possible that there's a bug in my port that's triggering other things, but I'm not complaining about Mono issues here. Those I'm tracking over at: http://ports.haiku-files.org/wiki/dev-lang/mono/2.x/1 Vanilla Mono does run fine on OpenSolaris and other platforms. The only vaguely related change of mine that comes to mind is that Haiku did not have {{{madvise}}}, {{{mprotect}}} and the POSIX {{{sigaction}}} with {{{SA_SIGINFO}}} yet. I just cross-checked with shared handles disabled and SMP disabled, aborts fine, no {{{vm_soft_fault}}} or freeze. Anyhow, if it's a bug in a userland app such as mono, I'd expect an error (message / crash) in userland. If it's a bug in the kernel, I'd expect a KDL (to investigate), never just a freeze without info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 17:34:49 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 15:34:49 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.d9ecd029b0a9c029bca7ca6d4196e748@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Sure, I'm not saying the original issue is not a bug in Haiku. Just the vm_soft_fault in the output you get without SMP is probably caused by mono and not the same issue seen with SMP enabled. Obviously something happens with SMP enabled that doesn't with SMP disabled that leads to a panic() in the kernel with some other factors that cause the hang. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 17:51:44 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 06 Aug 2008 15:51:44 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.eda3e87d754facc44c0fd3202de184e4@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Ingo, as your branch is merged now, this should be closed I guess? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 18:36:20 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 16:36:20 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. In-Reply-To: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> References: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> Message-ID: <047.f5a2e590ea2f214e02d20e22008b392b@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. ---------------------------+------------------------------------------------ Reporter: bga | Owner: bga Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bga): * owner: marcusoverhagen => bga Comment: Working on it... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 19:45:29 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 17:45:29 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.66d12f1ab8fc01c834d979f52ca39824@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * component: - General => System/Kernel Comment: Can you use the "mutex" command with the lock mentioned in the KDL message? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 19:53:52 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 17:53:52 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.3b4a286777035b9f5caf4f2d2e438ab5@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): There you go: {{{ PANIC: _mutex_lock(): double lock of 0x9125b660 by thread 48517 Welcome to Kernel Debugging Land... Thread 48517 "mono" running on CPU 0 kdebug> mutex 0x9125b660 mutex 0x9125b660: name: vm_cache flags: 0x0 holder: 48517 waiting threads: kdebug> }}} Anything else? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 20:02:36 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 18:02:36 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.302fe925a13c9592253e2c50814ff3cd@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): As requested: {{{ kdebug> thread 48517 THREAD: 0x914b5000 id: 48517 (0xbd85) name: "mono" all_next: 0x914a4800 team_next: 0x913ef800 q_next: 0x9143c000 priority: 20 (next 20) state: running next_state: ready cpu: 0x80113480 (0) sig_pending: 0x100020 (blocked: 0x20) in_kernel: 1 fault_handler: 0x80054394 args: 0x912d8f00 0x00000000 entry: 0x80047df8 team: 0x90b7d000, "kernel_team" exit.sem: 464406 exit.status: 0x1 (No Error (1)) exit.reason: 0x1 exit.signal: 0x0 exit.waiters: 0x95ffbe3c (group -1778401660, thread -1866996320) kernel_stack_area: 1039902 kernel_stack_base: 0x95ffc000 user_stack_area: -1 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 553867 user_time: 38783 flags: 0x1 architecture dependant section: esp: 0x95fffc3c ss: 0x95ff0010 fpu_state at 0x914b5380 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 20:27:58 2008 From: trac at haiku-os.org (axeld) Date: Wed, 06 Aug 2008 18:27:58 -0000 Subject: [Haiku-bugs] [Haiku] #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call In-Reply-To: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> References: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> Message-ID: <051.ccbe03c8fe75530404c5571f43d5a58d@haiku-os.org> #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => blocker * component: - General => System/Kernel * milestone: R1 => R1/alpha1 Comment: This might be a problem with how the I/O scheduler handles the OperationCompleted() method. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 20:28:53 2008 From: trac at haiku-os.org (tonestone57) Date: Wed, 06 Aug 2008 18:28:53 -0000 Subject: [Haiku-bugs] [Haiku] #2578: Running bonnie++ 1.03d on Haiku - crashes system Message-ID: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> #2578: Running bonnie++ 1.03d on Haiku - crashes system --------------------------+------------------------------------------------- Reporter: tonestone57 | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Ran bonnie++, single process, on Haiku r26829. System crashed to KDL. bonnie++ should have worked without crashing. Jpeg image of stack trace attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 20:54:19 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 06 Aug 2008 18:54:19 -0000 Subject: [Haiku-bugs] [Haiku] #2578: Running bonnie++ 1.03d on Haiku - crashes system In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.1ebc49a83e926c292f6db6c9aa48cee1@haiku-os.org> #2578: Running bonnie++ 1.03d on Haiku - crashes system ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * owner: marcusoverhagen => axeld * component: Drivers/Disk => System/Kernel Comment: Actually, 26828 just introduced some major (known to not be entirely stable) changes to handling of disk I/O and such, so right now it's not surprising that this doesn't complete. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 21:00:08 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 19:00:08 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. In-Reply-To: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> References: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> Message-ID: <047.515cc6fb59ba5063633bd43766ab39f7@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. ---------------------------+------------------------------------------------ Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bga): * owner: bga => marcusoverhagen Comment: As of r26844, the PATA controller works and devices are detected as long as it is configured in IDE MODE. Moving this ticket back to Marcus as I don't know when I will have time to look at it again and, more than that, I have no documentation for the JMicron controllers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 21:08:07 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 19:08:07 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. In-Reply-To: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> References: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> Message-ID: <047.4d78f5da224f5c199fa10c8963b861aa@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. ---------------------------+------------------------------------------------ Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by bga): Marcus, just as a refernce, Linux does the following when this controller is found: pci_read_config_dword(pdev, 0x40, &conf1); /* Enable dual function mode, AHCI on fn 0, IDE fn1 */ /* Set the class codes correctly and then direct IDE 0 */ conf1 |= 0x00C2A1B3; /* Set 0, 1, 4, 5, 7, 8, 13, 15, 17, 22, 23 */ pci_write_config_dword(pdev, 0x40, conf1); /* Update pdev accordingly */ pci_read_config_byte(pdev, PCI_HEADER_TYPE, &hdr); pdev->hdr_type = hdr & 0x7f; pdev->multifunction = !!(hdr & 0x80); pci_read_config_dword(pdev, PCI_CLASS_REVISION, &class); pdev->class = class >> 8; What you did originally in the code was pretty similar to this but it seme sthe mask you used was different from the one Linux uses for updating the device configuration and, also, there ios the class updating that you did not do. I tried using the same mask as in Linux but it did not work (although without updating the class). What is more interesting is that it seems linux does that without checking the mode the controller is in, which leads me to believe that it simply ignores the BIOS set mode and force it to be the mixed SATA/PATA mode always. Maybe we should do the same? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 23:02:11 2008 From: trac at haiku-os.org (bga) Date: Wed, 06 Aug 2008 21:02:11 -0000 Subject: [Haiku-bugs] [Haiku] #2579: File cache failure with read-only volumes. Message-ID: <038.b2be7edfb46c3a0320af11ded9b8d5c2@haiku-os.org> #2579: File cache failure with read-only volumes. -----------------------+---------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I finally managed to get my IDE controller to work and mounted my Zeta partition under Haiku. Just to be safe, I mounted it read-only. To my surprise, I can not read any file on the volume. Here is what I get: /Zeta 1.2/home> cat readat_test.cpp cat: readat_test.cpp: Read-only file system Syslog shows: KERN: file_cache: read pages failed: Read-only file system And strace: /Zeta 1.2/home> strace cat readat_test [ 728] _kern_image_relocated(0x681) (215 us) [ 728] --- SIGCONT (Continued) --- [ 728] _kern_create_sem(0x0, "exit stack lock") = 0x00003856 (15 us) [ 728] _kern_create_sem(0x1, "fork lock") = 0x00003857 (15 us) [ 728] _kern_get_system_info(0x7ffeecb4, 0x1fc) = 0x00000000 No error (7 us) [ 728] _kern_reserve_heap_address_range([0x18000000], 0x1, 0x48000000) = 0x00000000 No error (7 us) [ 728] _kern_create_area("heap", 0x2c29f0, 0x1, 0x32000, 0x0, 0x33) = 0x00001d6a (22 us) [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (1 us) [ 728] _kern_create_sem(0x1, "env lock") = 0x00003858 (1 us) [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_create_sem(0x0, "user group") = 0x00003859 (15 us) [ 728] _kern_set_area_protection(0x1d64, 0x15) = 0x00000000 No error (14 us) [ 728] _kern_set_area_protection(0x1d66, 0x15) = 0x00000000 No error (23 us) [ 728] _kern_release_sem(0x3849) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) [ 728] _kern_acquire_sem(0x3858) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3858) = 0x00000000 No error (0 us) [ 728] _kern_read_stat(0x1, (nil), false, 0x7ffeef3c, 0x3c) = 0x00000000 No error (1 us) [ 728] _kern_open(0xffffffff, "readat_test", 0x0, 0x0) = 0x00000003 (19 us) [ 728] _kern_read_stat(0x3, (nil), false, 0x7ffeef3c, 0x3c) = 0x00000000 No error (1 us) [ 728] _kern_read(0x3, 0xffffffffffffffff, 0x1802d000, 0x1000) = 0x80006008 (159 us) /bin/cat: [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xa) = 0x0000000a (4 us) readat_test[ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xb) = 0x0000000b (3 us) : Read-only file system[ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec3fc, 0x17) = 0x00000017 (8 us) [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x2b518b, 0x1) = 0x00000001 (3 us) [ 728] _kern_close(0x3) = 0x00000000 No error (2 us) [ 728] _kern_close(0x1) = 0x00000000 No error (0 us) [ 728] _kern_close(0x2) = 0x00000000 No error (1 us) [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) [ 728] _kern_exit_team(0x1) (2 us) It seems the problem is the _kern_write() calls in a read-only volume. But why does reading a file result in a write operation? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 6 23:26:45 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 06 Aug 2008 21:26:45 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.f13d79cda09a7e96f67fafaa01f2f48c@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 00:05:13 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 06 Aug 2008 22:05:13 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.f60862c8297ca2345a99234440db7412@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks for the reminder. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 01:04:47 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 06 Aug 2008 23:04:47 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.5c335623ce3007406595806cf2f18e4f@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Should be fixed in r26849. I don't have the test case, so please reopen if you encounter it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 01:40:32 2008 From: trac at haiku-os.org (tonestone57) Date: Wed, 06 Aug 2008 23:40:32 -0000 Subject: [Haiku-bugs] [Haiku] #2578: Running bonnie++ 1.03d on Haiku - crashes system In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.9194954da88c99625a3e99eb5903d4da@haiku-os.org> #2578: Running bonnie++ 1.03d on Haiku - crashes system ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by tonestone57): Yes, once the new I/O scheduler is working right then this bug ( and some other new ones ) should disappear. I ran bonnie++ on r26804 without any issues or errors - completed successfully. Once the changes to the disk I/O are complete; I can test again and report back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 01:49:46 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 06 Aug 2008 23:49:46 -0000 Subject: [Haiku-bugs] [Haiku] #2572: Haiku occasionally freezes with CPU halted In-Reply-To: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> References: <043.a03eb8af0bc1f6a98200f234e85e6c6f@haiku-os.org> Message-ID: <052.a96b7d10c48f06f1033af41dfeb980b2@haiku-os.org> #2572: Haiku occasionally freezes with CPU halted ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): I've found a hint ... when compiling with {{{-D_REENTRANT -D_THREAD_SAFE}}} I only get the {{{vm_page_fault}}}, no KDL or freeze, like with SMP disabled. So I'd assume the problem leading to the freeze is triggered somewhere in libroot (or the headers) where a differentiation based on one of those defines is made. If that were true and there were no easy way to prevent the freeze, we could close this bug as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 02:20:23 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 07 Aug 2008 00:20:23 -0000 Subject: [Haiku-bugs] [Haiku] #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call In-Reply-To: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> References: <042.acae1cdcea1e50d72abd197692e17338@haiku-os.org> Message-ID: <051.4a08373678ef2640c32ab11d7367fe28@haiku-os.org> #2576: [Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r26850. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 09:30:20 2008 From: trac at haiku-os.org (axeld) Date: Thu, 07 Aug 2008 07:30:20 -0000 Subject: [Haiku-bugs] [Haiku] #2511: MediaPlayer will not play .wav files from an Audio CD In-Reply-To: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> References: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> Message-ID: <051.d117b16cb09a1d1ee5a50a30f367a49f@haiku-os.org> #2511: MediaPlayer will not play .wav files from an Audio CD --------------------------------+------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26853. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 09:30:41 2008 From: trac at haiku-os.org (axeld) Date: Thu, 07 Aug 2008 07:30:41 -0000 Subject: [Haiku-bugs] [Haiku] #2565: cdda-fs fails to copy the last track off some audio CDs In-Reply-To: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> References: <044.f0fcd69391691cba221461e22c791ee4@haiku-os.org> Message-ID: <053.29cccd0ef9262bfcb2a322d97ce035ba@haiku-os.org> #2565: cdda-fs fails to copy the last track off some audio CDs --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26853. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 09:39:15 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 07 Aug 2008 07:39:15 -0000 Subject: [Haiku-bugs] [Haiku] #2578: Running bonnie++ 1.03d on Haiku - crashes system In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.1d3f9e5e95322f90720ded7c9164b04e@haiku-os.org> #2578: Running bonnie++ 1.03d on Haiku - crashes system ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Actually, running the test, and reporting bugs with as much as information as possible will help speed things up. Anyway, if you test it again and encounter the same crash, please also report the stack trace of the running application (bonnie++ in this case). It might help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 11:26:00 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Thu, 07 Aug 2008 09:26:00 -0000 Subject: [Haiku-bugs] [Haiku] #2579: File cache failure with read-only volumes. In-Reply-To: <038.b2be7edfb46c3a0320af11ded9b8d5c2@haiku-os.org> References: <038.b2be7edfb46c3a0320af11ded9b8d5c2@haiku-os.org> Message-ID: <047.3d65c1ae7fcca94af84c72058d730933@haiku-os.org> #2579: File cache failure with read-only volumes. ------------------------+--------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Old description: > I finally managed to get my IDE controller to work and mounted my Zeta > partition under Haiku. Just to be safe, I mounted it read-only. To my > surprise, I can not read any file on the volume. Here is what I get: > > /Zeta 1.2/home> cat readat_test.cpp > cat: readat_test.cpp: Read-only file system > > Syslog shows: > > KERN: file_cache: read pages failed: Read-only file system > > And strace: > > /Zeta 1.2/home> strace cat readat_test > [ 728] _kern_image_relocated(0x681) (215 us) > [ 728] --- SIGCONT (Continued) --- > [ 728] _kern_create_sem(0x0, "exit stack lock") = 0x00003856 (15 us) > [ 728] _kern_create_sem(0x1, "fork lock") = 0x00003857 (15 us) > [ 728] _kern_get_system_info(0x7ffeecb4, 0x1fc) = 0x00000000 No error > (7 us) > [ 728] _kern_reserve_heap_address_range([0x18000000], 0x1, 0x48000000) > = 0x00000000 No error (7 us) > [ 728] _kern_create_area("heap", 0x2c29f0, 0x1, 0x32000, 0x0, 0x33) = > 0x00001d6a (22 us) > [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) > [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (1 us) > [ 728] _kern_create_sem(0x1, "env lock") = 0x00003858 (1 us) > [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) > [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (0 us) > [ 728] _kern_create_sem(0x0, "user group") = 0x00003859 (15 us) > [ 728] _kern_set_area_protection(0x1d64, 0x15) = 0x00000000 No error > (14 us) > [ 728] _kern_set_area_protection(0x1d66, 0x15) = 0x00000000 No error > (23 us) > [ 728] _kern_release_sem(0x3849) = 0x00000000 No error (0 us) > [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) > [ 728] _kern_acquire_sem(0x3858) = 0x00000000 No error (0 us) > [ 728] _kern_release_sem(0x3858) = 0x00000000 No error (0 us) > [ 728] _kern_read_stat(0x1, (nil), false, 0x7ffeef3c, 0x3c) = > 0x00000000 No error (1 us) > [ 728] _kern_open(0xffffffff, "readat_test", 0x0, 0x0) = 0x00000003 (19 > us) > [ 728] _kern_read_stat(0x3, (nil), false, 0x7ffeef3c, 0x3c) = > 0x00000000 No error (1 us) > [ 728] _kern_read(0x3, 0xffffffffffffffff, 0x1802d000, 0x1000) = > 0x80006008 (159 us) > /bin/cat: [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xa) > = 0x0000000a (4 us) > readat_test[ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xb) > = 0x0000000b (3 us) > : Read-only file system[ 728] _kern_write(0x2, 0xffffffffffffffff, > 0x7ffec3fc, 0x17) = 0x00000017 (8 us) > > [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x2b518b, 0x1) = 0x00000001 > (3 us) > [ 728] _kern_close(0x3) = 0x00000000 No error (2 us) > [ 728] _kern_close(0x1) = 0x00000000 No error (0 us) > [ 728] _kern_close(0x2) = 0x00000000 No error (1 us) > [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) > [ 728] _kern_exit_team(0x1) (2 us) > > It seems the problem is the _kern_write() calls in a read-only volume. > But why does reading a file result in a write operation? New description: I finally managed to get my IDE controller to work and mounted my Zeta partition under Haiku. Just to be safe, I mounted it read-only. To my surprise, I can not read any file on the volume. Here is what I get: /Zeta 1.2/home> cat readat_test.cpp cat: readat_test.cpp: Read-only file system Syslog shows: KERN: file_cache: read pages failed: Read-only file system And strace: {{{ /Zeta 1.2/home> strace cat readat_test [ 728] _kern_image_relocated(0x681) (215 us) [ 728] --- SIGCONT (Continued) --- [ 728] _kern_create_sem(0x0, "exit stack lock") = 0x00003856 (15 us) [ 728] _kern_create_sem(0x1, "fork lock") = 0x00003857 (15 us) [ 728] _kern_get_system_info(0x7ffeecb4, 0x1fc) = 0x00000000 No error (7 us) [ 728] _kern_reserve_heap_address_range([0x18000000], 0x1, 0x48000000) = 0x00000000 No error (7 us) [ 728] _kern_create_area("heap", 0x2c29f0, 0x1, 0x32000, 0x0, 0x33) = 0x00001d6a (22 us) [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (1 us) [ 728] _kern_create_sem(0x1, "env lock") = 0x00003858 (1 us) [ 728] _kern_acquire_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3857) = 0x00000000 No error (0 us) [ 728] _kern_create_sem(0x0, "user group") = 0x00003859 (15 us) [ 728] _kern_set_area_protection(0x1d64, 0x15) = 0x00000000 No error (14 us) [ 728] _kern_set_area_protection(0x1d66, 0x15) = 0x00000000 No error (23 us) [ 728] _kern_release_sem(0x3849) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) [ 728] _kern_acquire_sem(0x3858) = 0x00000000 No error (0 us) [ 728] _kern_release_sem(0x3858) = 0x00000000 No error (0 us) [ 728] _kern_read_stat(0x1, (nil), false, 0x7ffeef3c, 0x3c) = 0x00000000 No error (1 us) [ 728] _kern_open(0xffffffff, "readat_test", 0x0, 0x0) = 0x00000003 (19 us) [ 728] _kern_read_stat(0x3, (nil), false, 0x7ffeef3c, 0x3c) = 0x00000000 No error (1 us) [ 728] _kern_read(0x3, 0xffffffffffffffff, 0x1802d000, 0x1000) = 0x80006008 (159 us) /bin/cat: [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xa) = 0x0000000a (4 us) readat_test[ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec85c, 0xb) = 0x0000000b (3 us) : Read-only file system[ 728] _kern_write(0x2, 0xffffffffffffffff, 0x7ffec3fc, 0x17) = 0x00000017 (8 us) [ 728] _kern_write(0x2, 0xffffffffffffffff, 0x2b518b, 0x1) = 0x00000001 (3 us) [ 728] _kern_close(0x3) = 0x00000000 No error (2 us) [ 728] _kern_close(0x1) = 0x00000000 No error (0 us) [ 728] _kern_close(0x2) = 0x00000000 No error (1 us) [ 728] _kern_release_sem(0x3856) = 0x00000000 No error (0 us) [ 728] _kern_exit_team(0x1) (2 us) }}} It seems the problem is the _kern_write() calls in a read-only volume. But why does reading a file result in a write operation? -- Comment(by marcusoverhagen): I think _kern_write(0x2, ...) is a write to stdout. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 13:41:08 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 11:41:08 -0000 Subject: [Haiku-bugs] [Haiku] #2579: File cache failure with read-only volumes. In-Reply-To: <038.b2be7edfb46c3a0320af11ded9b8d5c2@haiku-os.org> References: <038.b2be7edfb46c3a0320af11ded9b8d5c2@haiku-os.org> Message-ID: <047.af03c685834654a8ef20ae9e64eda221@haiku-os.org> #2579: File cache failure with read-only volumes. ------------------------+--------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bga): Makes sense. Still, I do not understand why I am getting a read-only error when reading a file (more specifically, reading pages from the file system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 15:00:42 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 13:00:42 -0000 Subject: [Haiku-bugs] [Haiku] #2580: Error in BFS when trying to initialize a partition with DriveSetup. Message-ID: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> #2580: Error in BFS when trying to initialize a partition with DriveSetup. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I added a second virtual HD to my VMWare configuration by simply duplicating the Haiku disk image and assigned it as a slave IDE device on the first IDE controller. I then booted Haiku in VMWare and, as expected it saw the 2 devices and a "Haiku" BFS partition in each. I tried to use DriveSetup to initialize the second partition (it was not mounted, of course) and got the error in the attached KDL screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 15:14:13 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 13:14:13 -0000 Subject: [Haiku-bugs] [Haiku] #2580: Error in BFS when trying to initialize a partition with DriveSetup. In-Reply-To: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> References: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> Message-ID: <047.6a7338d6870c5e04c13f829a2ff59ac5@haiku-os.org> #2580: Error in BFS when trying to initialize a partition with DriveSetup. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): I went ahead and tried with mkfs just in case. As I expected, the same error happens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 15:43:29 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 13:43:29 -0000 Subject: [Haiku-bugs] [Haiku] #2581: Position slider does not match position in the song with MediaPlayer. Message-ID: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> #2581: Position slider does not match position in the song with MediaPlayer. --------------------------------------+------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- When playing this MP3 file: http://www.bug-br.org.br/virtual-void.mp3 The position slider in MediaPlayer does not match the actual position in the song. In fact, when the music ends, the position slider is at around 1/4 of the bar. The funny thing is that when the music ends, it starts playing again form the start and the position indicator just continues moving. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 16:36:55 2008 From: trac at haiku-os.org (korli) Date: Thu, 07 Aug 2008 14:36:55 -0000 Subject: [Haiku-bugs] [Haiku] #1217: AUICH looping media_server In-Reply-To: <044.4a2404a68a24a4221ce265dab4360f38@haiku-os.org> References: <044.4a2404a68a24a4221ce265dab4360f38@haiku-os.org> Message-ID: <053.bb991aa50b5546299c9cc1398f3a564d@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Closing. Please reopen if needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 18:11:34 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 07 Aug 2008 16:11:34 -0000 Subject: [Haiku-bugs] [Haiku] #2582: scsi scheduler page fault with interrupts disabled Message-ID: <043.37e59dd7f85990a04c69a3b2f4fcfaa1@haiku-os.org> #2582: scsi scheduler page fault with interrupts disabled ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Got the following KDL on ca. r26856 while launching Firefox (SMP enabled, gcc2 hybrid build). {{{ PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbf03 from eip 0x800631d3 Welcome to Kernel Debugging Land... Thread 32 "scsi scheduler" running on CPU 0 kdebug> sc stack trace for thread 32 "scsi scheduler" kernel stack: 0x936ba000 to 0x936be000 frame caller :function + offset 0 936bdb44 (+ 48) 8005460d :invoke_debugger_command + 0x00ed 1 936bdb74 (+ 64) 80054405 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 936bdbb4 (+ 64) 8005474d :invoke_debugger_command_pipe + 0x009d 3 936bdbf4 (+ 48) 80055628 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 936bdc24 (+ 48) 80054fde :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 936bdc54 (+ 224) 800569f4 :evaluate_debug_command + 0x0088 6 936bdd34 (+ 64) 80052a82 :kernel_debugger_loop__Fv + 0x01ae 7 936bdd74 (+ 48) 8005361b :kernel_debugger + 0x0117 8 936bdda4 (+ 192) 800534f9 :panic + 0x0029 9 936bde64 (+ 48) 800b3e74 :page_fault_exception + 0x0060 10 936bde94 (+ 12) 800b7426 :int_bottom + 0x0036 (nearest) kernel iframe at 0x936bdea0 (end = 0x936bdef0) eax 0xdeadbeef ebx 0x90bc2104 ecx 0x90c073d4 edx 0xdeadbeef esi 0x90c073c0 edi 0x90bc2088 ebp 0x936bdf28 esp 0x936bded4 eip 0x800631d3 eflags 0x210082 vector: 0xe, error code: 0x2 11 936bdea0 (+ 136) 800631d3 :_Finisher__11IOScheduler + 0x008f 12 936bdf28 (+ 96) 8006363b :_GetOperation__11IOScheduler + 0x0177 13 936bdf88 (+ 48) 80063a3e :_Scheduler__11IOScheduler + 0x0032 14 936bdfb8 (+ 32) 80063ace :_SchedulerThread__11IOSchedulerPv + 0x0012 15 936bdfd8 (+ 32) 8004b2af :_create_kernel_thread_kentry__Fv + 0x001b 16 936bdff8 (+1821646856) 8004b24c :thread_kthread_exit__Fv + 0x0000 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 18:13:20 2008 From: trac at haiku-os.org (axeld) Date: Thu, 07 Aug 2008 16:13:20 -0000 Subject: [Haiku-bugs] [Haiku] #2580: Error in BFS when trying to initialize a partition with DriveSetup. In-Reply-To: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> References: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> Message-ID: <047.42dab529c9d7d03937984e626bad9a32@haiku-os.org> #2580: Error in BFS when trying to initialize a partition with DriveSetup. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => assigned * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 18:17:00 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 07 Aug 2008 16:17:00 -0000 Subject: [Haiku-bugs] [Haiku] #2582: scsi scheduler page fault with interrupts disabled In-Reply-To: <043.37e59dd7f85990a04c69a3b2f4fcfaa1@haiku-os.org> References: <043.37e59dd7f85990a04c69a3b2f4fcfaa1@haiku-os.org> Message-ID: <052.dfecd8acebbb8ffaae796ed9c156d084@haiku-os.org> #2582: scsi scheduler page fault with interrupts disabled ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): It was in fact r26856, but on second thoughts SMP was disabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 18:17:38 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 07 Aug 2008 16:17:38 -0000 Subject: [Haiku-bugs] [Haiku] #1767: UHCI legacy support In-Reply-To: <050.c974a7a6754792455eb3ad1d6bd33093@haiku-os.org> References: <050.c974a7a6754792455eb3ad1d6bd33093@haiku-os.org> Message-ID: <059.2ce73076edbf0e085b3a9dcf4b5c12fc@haiku-os.org> #1767: UHCI legacy support ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by emitrax): Any updates on this one? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 19:37:55 2008 From: trac at haiku-os.org (axeld) Date: Thu, 07 Aug 2008 17:37:55 -0000 Subject: [Haiku-bugs] [Haiku] #2580: Error in BFS when trying to initialize a partition with DriveSetup. In-Reply-To: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> References: <038.030abd907f6078ab1d1b0127c8bbe1f0@haiku-os.org> Message-ID: <047.60f429918d1acffe156d838c9ac42277@haiku-os.org> #2580: Error in BFS when trying to initialize a partition with DriveSetup. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26865. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 19:50:52 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 17:50:52 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. Message-ID: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Not sure if this is intentional or not, but I expected other mounted partitions to get the disk icon (without the leaf in the boot disk) but they show the cabinet icon instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 20:17:50 2008 From: trac at haiku-os.org (stippi) Date: Thu, 07 Aug 2008 18:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.e92612870d26517ae9599e3eb70698cf@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by stippi): The problem is that drivers currently don't return HVIF icons. Either we introduce a new ioctl API for drivers to return HVIF icons and enable the code that reads those icons from drivers (BPartition and/or BVolume), or we decide to handle this differently altogether, for example by using built-in icons in Tracker based on volume properties. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 20:24:46 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 18:24:46 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.7f970d28d38e002e73759eab765e68de@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by bga): By drivers you mean the fs add-ons, right? What we ended up doing in Zeta was to include the icons in Tracker itself (although they were loaded from external files). We went as far as having different icons (actually an icon plus a badge) for different file systems. i guess we could simply change the cabinet icon to be a disk icon? This looks more consistent to me. OTOH, it would be cool if the file systems would export their icons (so they could have customized icons) and we only used the default one when no icon was exported. of course someone would have to implement this although it would probably be easier than actually designing the icons :). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 20:29:10 2008 From: trac at haiku-os.org (stippi) Date: Thu, 07 Aug 2008 18:29:10 -0000 Subject: [Haiku-bugs] [Haiku] #2581: Position slider does not match position in the song with MediaPlayer. In-Reply-To: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> References: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> Message-ID: <047.d1ebb508a12b3b85aa8a3bd60cc3b1d0@haiku-os.org> #2581: Position slider does not match position in the song with MediaPlayer. ----------------------+----------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Changes (by stippi): * owner: marcusoverhagen => axeld * component: Applications/MediaPlayer => Add-Ons Comment: Looks like the MP3 decoder/reader reports a wrong total duration for this file. It's not really a problem in the MediaPlayer itself. BTW, when you let it play to the "end", it will crash in III_antialias() in the mp3_decoder with a corrupt stack. In any case, we need to be able to play back this particular song in Haiku! :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 20:37:12 2008 From: trac at haiku-os.org (bga) Date: Thu, 07 Aug 2008 18:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #2581: Position slider does not match position in the song with MediaPlayer. In-Reply-To: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> References: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> Message-ID: <047.504ea2569c927e1fe304c1149253e458@haiku-os.org> #2581: Position slider does not match position in the song with MediaPlayer. ----------------------+----------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Comment(by bga): I just played it to the end using whatever media player is the default one in Ubuntu and it reported an error at the end (no crash, just said "stream error" or something). Still, the time was correct. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 20:45:07 2008 From: trac at haiku-os.org (stippi) Date: Thu, 07 Aug 2008 18:45:07 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.ec5416d5562c1c12dc291988074be797@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by stippi): It is the device drivers actually, like the floppy or scsi_cd drivers. The custom icon trick is still possible (I just checked). In case of BFS, I believe the root folder of the volume gets an icon attribute. This was even still possible in ZETA, I used this trick to give the WonderBrush CD a custom SVG icon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 21:04:07 2008 From: trac at haiku-os.org (stippi) Date: Thu, 07 Aug 2008 19:04:07 -0000 Subject: [Haiku-bugs] [Haiku] #1470: Mouse Speed and Acceleration have limited positions In-Reply-To: <044.f111214fb6540143725ea3a998be0174@haiku-os.org> References: <044.f111214fb6540143725ea3a998be0174@haiku-os.org> Message-ID: <053.461dd39104e3e5eef939875b1d0fde73@haiku-os.org> #1470: Mouse Speed and Acceleration have limited positions ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): Applied in r26866. Thanks a lot for looking into it! Going to test soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 23:26:03 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 Aug 2008 21:26:03 -0000 Subject: [Haiku-bugs] [Haiku] #2581: Position slider does not match position in the song with MediaPlayer. In-Reply-To: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> References: <038.663ce7174880c3c01b9247c901eca2dd@haiku-os.org> Message-ID: <047.84e6f80762f128001146f35d65dd5d80@haiku-os.org> #2581: Position slider does not match position in the song with MediaPlayer. ----------------------+----------------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Comment(by anevilyak): Don't forget to check that 5038.mp3 also plays properly ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 7 23:30:34 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 07 Aug 2008 21:30:34 -0000 Subject: [Haiku-bugs] [Haiku] #2584: File corruption Message-ID: <043.f3f3ddfc5863955f5bc5c9765fae1490@haiku-os.org> #2584: File corruption -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- At r26856 and r26863 I get file corruption when extracting, configuring and make'ing [http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.12.tar.gz libiconv-1.12.tar]. The (first) affected file is {{{lib/cp862.h}}}, which is either truncated or contains garbage at slightly varying offsets. This does not happen back at r26820 for the same tar archive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 00:32:32 2008 From: trac at haiku-os.org (Bouncer) Date: Thu, 07 Aug 2008 22:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #2585: Reporting negative values for Memory Used. Message-ID: <042.01f311a458942da0a4af0ad8abfa9ddf@haiku-os.org> #2585: Reporting negative values for Memory Used. -----------------------+---------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Possibly related to ticket 2574. On real hardware - I was using 'svn' to download the entire haiku source tree. The 'Mb used' display in 'About This System' was continuously decrementing the Memory counter as the download progressed. The download completed successfully - but left my system displaying -2176 Mb used. Funny thing - the negative Memory count was was always approximatly -2 x the size of the "haiku" directory where the download was being written to. According to 'get_info'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 00:37:38 2008 From: trac at haiku-os.org (Bouncer) Date: Thu, 07 Aug 2008 22:37:38 -0000 Subject: [Haiku-bugs] [Haiku] #2585: Reporting negative values for Memory Used. In-Reply-To: <042.01f311a458942da0a4af0ad8abfa9ddf@haiku-os.org> References: <042.01f311a458942da0a4af0ad8abfa9ddf@haiku-os.org> Message-ID: <051.b528405234f5a8ac0c94a3ecb1978c01@haiku-os.org> #2585: Reporting negative values for Memory Used. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by Bouncer): Additional Info: The build used was r26868. My machine has 2047 MB total memory. Final Size of "haiku" directory: 796.2 MB. Attempting to launch FireFox after the download - resulted in a KDL. No details captured. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 01:05:33 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 07 Aug 2008 23:05:33 -0000 Subject: [Haiku-bugs] [Haiku] #2577: Panic: _mutex_lock(): double lock In-Reply-To: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> References: <043.11de65034628ee3601cfc1915fab0afe@haiku-os.org> Message-ID: <052.d65dd166108b4cfc589599ebe436afc1@haiku-os.org> #2577: Panic: _mutex_lock(): double lock ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by andreasf): Gone after applying your patch to r26820. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 01:16:26 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 07 Aug 2008 23:16:26 -0000 Subject: [Haiku-bugs] [Haiku] #2078: [PATCH] Add stdio_ext.h header (was: Add stdio_ext.h header) In-Reply-To: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> References: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> Message-ID: <052.7f082e1c419018228903686dda241823@haiku-os.org> #2078: [PATCH] Add stdio_ext.h header --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by andreasf): Header looks okay afaict, except that it's not strictly POSIX. We might put it into {{{3rdparty}}} instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 04:55:25 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 02:55:25 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 Message-ID: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 --------------------------+------------------------------------------------- Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- While jamming Haiku within Haiku (after having done an svn up on the copy of the tree stored on the disk), I hit this kdl. Backtrace as follows: {{{ stack trace for thread 37 "scsi scheduler" kernel stack: 0xa017b000 to 0xa017f000 frame caller :function + offset 0 a017eb08 (+ 48) 800577d5 :invoke_debugger_command + 0x00ed 1 a017eb38 (+ 64) 800575cd :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 a017eb78 (+ 64) 80057915 :invoke_debugger_command_pipe + 0x009d 3 a017ebb8 (+ 48) 800587f0 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 a017ebe8 (+ 48) 800581a6 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 a017ec18 (+ 224) 80059bbc :evaluate_debug_command + 0x0088 6 a017ecf8 (+ 64) 80055c4a :kernel_debugger_loop__Fv + 0x01ae 7 a017ed38 (+ 48) 800567e3 :kernel_debugger + 0x0117 8 a017ed68 (+ 192) 800566c1 :panic + 0x0029 9 a017ee28 (+ 48) 807cdde5 :ata_request_set_status + 0x003d 10 a017ee58 (+ 48) 807d083e :ata_exec_io + 0x0402 11 a017ee88 (+ 48) 807cec42 :sim_scsi_io + 0x006a 12 a017eeb8 (+ 64) 808cd99b :scsi_async_io + 0x02f3 13 a017eef8 (+ 96) 808e0678 :periph_io__FP23scsi_periph_device_infoP11IOOperationPUl + 0x025c 14 a017ef58 (+ 48) 808dbcfe :do_io__FPvP11IOOperation + 0x0032 15 a017ef88 (+ 48) 80068829 :_Scheduler__11IOScheduler + 0x0055 16 a017efb8 (+ 32) 80068896 :_SchedulerThread__11IOSchedulerPv + 0x0012 17 a017efd8 (+ 32) 8004d8c3 :_create_kernel_thread_kentry__Fv + 0x001b 18 a017eff8 (+1609043976) 8004d860 :thread_kthread_exit__Fv + 0x0000 }}} I don't know what else would be useful to look up at this point though, so I'm going to leave the box in KDL so you can let me know if there's anything else you want me to pull out of the kernel debugger. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 06:53:07 2008 From: trac at haiku-os.org (psudobuddha) Date: Fri, 08 Aug 2008 04:53:07 -0000 Subject: [Haiku-bugs] [Haiku] #2587: USB Boot Panic: could not mount boot device Message-ID: <046.6f0f36d4911d6e6f95a84cadd03c87eb@haiku-os.org> #2587: USB Boot Panic: could not mount boot device -------------------------+-------------------------------------------------- Reporter: psudobuddha | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Experienced on a D520 Dell Latitude Laptop. It at first panics with a NMI interupt, then panics when makes it to the disk icon. Cant get debug output but will provide pictures of screen output as well as bt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 06:54:07 2008 From: trac at haiku-os.org (psudobuddha) Date: Fri, 08 Aug 2008 04:54:07 -0000 Subject: [Haiku-bugs] [Haiku] #2587: USB Boot Panic: could not mount boot device In-Reply-To: <046.6f0f36d4911d6e6f95a84cadd03c87eb@haiku-os.org> References: <046.6f0f36d4911d6e6f95a84cadd03c87eb@haiku-os.org> Message-ID: <055.910036da6465e4c143c25368b4a15d1f@haiku-os.org> #2587: USB Boot Panic: could not mount boot device --------------------------+------------------------------------------------- Reporter: psudobuddha | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by psudobuddha): * cc: briandabrain at gmail.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 10:43:49 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 08 Aug 2008 08:43:49 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.38fd24d869391067bce8048e0137c574@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by mmlr): Just a notice that a patch was attached to this bug. E-Mail notifications for attachments are still not there. Would apply it myself, but I'm at work right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 11:31:25 2008 From: trac at haiku-os.org (axeld) Date: Fri, 08 Aug 2008 09:31:25 -0000 Subject: [Haiku-bugs] [Haiku] #2566: Workspaces replicant - active window lost focus In-Reply-To: <045.2b87057b23bf5bdc9f90fd1f2dee89bf@haiku-os.org> References: <045.2b87057b23bf5bdc9f90fd1f2dee89bf@haiku-os.org> Message-ID: <054.5e9cbb7f5f8fc51e5a7a75462bfe282e@haiku-os.org> #2566: Workspaces replicant - active window lost focus ---------------------------------+------------------------------------------ Reporter: un_spacyar | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * component: Applications/Workspaces => Servers/app_server Comment: I can't reproduce this. Did you do anything special before, or can you reproduce this at will? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 11:43:36 2008 From: trac at haiku-os.org (kaliber) Date: Fri, 08 Aug 2008 09:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #2584: File corruption In-Reply-To: <043.f3f3ddfc5863955f5bc5c9765fae1490@haiku-os.org> References: <043.f3f3ddfc5863955f5bc5c9765fae1490@haiku-os.org> Message-ID: <052.a2a8375c47c1ae662f3a23beafa47ef4@haiku-os.org> #2584: File corruption ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by kaliber): * cc: grzegorz.dabrowski at gmail.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 12:44:06 2008 From: trac at haiku-os.org (stippi) Date: Fri, 08 Aug 2008 10:44:06 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.8dd54f57433c030eef7c4a4ab31957aa@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by stippi): Thanks a lot for the patch, I applied it in r26873! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 12:45:09 2008 From: trac at haiku-os.org (stippi) Date: Fri, 08 Aug 2008 10:45:09 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.14af97f21f4fb6b95c69b6fb932ccff7@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by stippi): Oh, I meant to say... can more people with that NIC report if it is working now, or was working before and isn't anymore? If there are no issues, then we can close this bug I guess. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 13:38:39 2008 From: trac at haiku-os.org (axeld) Date: Fri, 08 Aug 2008 11:38:39 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.1a7cf2a97e73fbbed795c23b5f43cda2@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * priority: high => critical Comment: I had the same problem before r26839. AFAICT this is only triggered by the "ata" driver when a zero length request comes in. If it's reproducible, you might want to print the request, and, more importantly, the io_operation in scsi2ata.c, line 567, right before this: {{{ata_request_set_status(request, SCSI_REQ_CMP);}}} Something like: {{{dprintf("request %p, ccb %p, io_operation %p\n", request, ccb, ccb->io_operation);}}} Alternatively, you should also be able to see this io_operation pointer in the second argument of call 14 in this stack trace (you could see this with "call 14 -2"). Then, when in KDL, you can use the "io_operation" command with this pointer, and print your findings here :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 13:44:23 2008 From: trac at haiku-os.org (dancso.robert) Date: Fri, 08 Aug 2008 11:44:23 -0000 Subject: [Haiku-bugs] [Haiku] #2588: Boot error on Gigabyte N211U notebook Message-ID: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> #2588: Boot error on Gigabyte N211U notebook --------------------------------+------------------------------------------- Reporter: dancso.robert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- After the BIOS boot process the system hangs up. No boot logo, no error messages, no nothing. This is the same on the Zeta. Only BeOS can boot up with the original zbeos. If it want to change the screen to bigger than 640x480x8 (if I use a custom boot logo), or I want to enter the boot menu (using space or the ALT) it hangs up too during boot. So, I cannot try the Haiku on my notebook. On my desktop PC (Shuttle SK21G, 384 MB RAM, SATA HDD, AMD Sempron 2800+) it is works as design. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 13:50:08 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 08 Aug 2008 11:50:08 -0000 Subject: [Haiku-bugs] [Haiku] #2588: Boot error on Gigabyte N211U notebook In-Reply-To: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> References: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> Message-ID: <057.b2f38931ef26eb9f30b3164aa96df7c4@haiku-os.org> #2588: Boot error on Gigabyte N211U notebook ---------------------------------+------------------------------------------ Reporter: dancso.robert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by mmlr): How have you installed Haiku and what boot manager are you using? Are there other operating systems installed and do they boot as expected? You can take a look at http://www.haiku- os.org/documents/user/how_to_get_haiku_booted and see if this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 14:27:02 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 12:27:02 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.ece81d9f71fbafb593a37425b5e9613d@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): Will see what I can find this evening :) Also I feel dumb for not mentioning the revision number of that build, but it was r26872 in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 16:01:55 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 08 Aug 2008 14:01:55 -0000 Subject: [Haiku-bugs] [Haiku] #2585: Reporting negative values for Memory Used. In-Reply-To: <042.01f311a458942da0a4af0ad8abfa9ddf@haiku-os.org> References: <042.01f311a458942da0a4af0ad8abfa9ddf@haiku-os.org> Message-ID: <051.e092c36730ef3cf599fc714e22a91d54@haiku-os.org> #2585: Reporting negative values for Memory Used. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r26876. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 17:21:58 2008 From: trac at haiku-os.org (umccullough) Date: Fri, 08 Aug 2008 15:21:58 -0000 Subject: [Haiku-bugs] [Haiku] #2266: Notifications not send when attachment added to ticket In-Reply-To: <050.17dfb7c464ad7da6a748337b1ae2ee5b@haiku-os.org> References: <050.17dfb7c464ad7da6a748337b1ae2ee5b@haiku-os.org> Message-ID: <059.858f795b924e11b5ad271672c0173b91@haiku-os.org> #2266: Notifications not send when attachment added to ticket ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by umccullough): This is a duplicate of #1740 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 17:23:04 2008 From: trac at haiku-os.org (umccullough) Date: Fri, 08 Aug 2008 15:23:04 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.1b7f356f0dda31ae83f101af8fbb54f0@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by umccullough): Aha! I have this chipset in my core 2 duo box IIRC (and it didn't work before) - will give it another shot in the next couple days and report back. RE: the attachment notification issue with trac, it's logged as #1740 (explanation of why it's still broken there) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 17:29:14 2008 From: trac at haiku-os.org (stippi) Date: Fri, 08 Aug 2008 15:29:14 -0000 Subject: [Haiku-bugs] [Haiku] #2266: Notifications not send when attachment added to ticket In-Reply-To: <050.17dfb7c464ad7da6a748337b1ae2ee5b@haiku-os.org> References: <050.17dfb7c464ad7da6a748337b1ae2ee5b@haiku-os.org> Message-ID: <059.48dbda924c7079b63a72b32bc29d8e0a@haiku-os.org> #2266: Notifications not send when attachment added to ticket ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: Unscheduled Component: Website/Trac | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => duplicate -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 17:38:58 2008 From: trac at haiku-os.org (bga) Date: Fri, 08 Aug 2008 15:38:58 -0000 Subject: [Haiku-bugs] [Haiku] #2589: Renaming a volume should rename de mount menu entry. Message-ID: <038.5e662ff28c221f983fb0e0bcfae86cb2@haiku-os.org> #2589: Renaming a volume should rename de mount menu entry. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- When you rename a volume, the Mount menu in Tracker will still list it with its old name, which is confusing. On a related note, if the mount point was automatically created by mountvolume or Tracker, it should also rename itself to match the new volume name. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 17:48:34 2008 From: trac at haiku-os.org (bga) Date: Fri, 08 Aug 2008 15:48:34 -0000 Subject: [Haiku-bugs] [Haiku] #2590: Haiku gets confused with 2 volumes with the same name. Message-ID: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> #2590: Haiku gets confused with 2 volumes with the same name. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I have two partitions called "Haiku" I mounted both and changed the name of the second partition to "Empty" and rebooted immediately. After boot both partitions had been renamed empty. I then proceeded to rename the first partition (boot) back to Haiku and rebooted. The partitions didn't change names (it reset to "Empty") and now the two partition icosn were overlapping which indicates that it also got confused when saving the partition attributes. I tried yet again and renamed the second partition to "Test". After boot, again both partitions have been renamed "Test". So it seems that (considering 2 BFS partitions, 1 the boot partition): 1 - Renaming the second partition also renames the boot one (only visible after rebooting). 2 - Renaming the boot partition has no effect and then position attributes on the second partition seeing to be copied to the first partition (also after boot). This may or may not be related, but I noticed that working with files on the second partition affected files with the same path in the first partition which lead me to believe that there is a general confusion about Volume objects. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 18:03:46 2008 From: trac at haiku-os.org (scottmc) Date: Fri, 08 Aug 2008 16:03:46 -0000 Subject: [Haiku-bugs] [Haiku] #2589: Renaming a volume should rename de mount menu entry. In-Reply-To: <038.5e662ff28c221f983fb0e0bcfae86cb2@haiku-os.org> References: <038.5e662ff28c221f983fb0e0bcfae86cb2@haiku-os.org> Message-ID: <047.704d1068c2215df18e279602a0bab8f0@haiku-os.org> #2589: Renaming a volume should rename de mount menu entry. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by scottmc): Sounds like a dupe of #2149 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 18:05:49 2008 From: trac at haiku-os.org (stippi) Date: Fri, 08 Aug 2008 16:05:49 -0000 Subject: [Haiku-bugs] [Haiku] #2589: Renaming a volume should rename de mount menu entry. In-Reply-To: <038.5e662ff28c221f983fb0e0bcfae86cb2@haiku-os.org> References: <038.5e662ff28c221f983fb0e0bcfae86cb2@haiku-os.org> Message-ID: <047.4c3a8bfcc5655560fd6b8ae360b83584@haiku-os.org> #2589: Renaming a volume should rename de mount menu entry. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: Yes it's a duplicate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 18:11:18 2008 From: trac at haiku-os.org (bga) Date: Fri, 08 Aug 2008 16:11:18 -0000 Subject: [Haiku-bugs] [Haiku] #2149: Haiku does not update name of a renamed volume until after a reboot In-Reply-To: <042.ba900f626b5e000c5241c29031329e9b@haiku-os.org> References: <042.ba900f626b5e000c5241c29031329e9b@haiku-os.org> Message-ID: <051.442ac870684ca6b1af8c23c60fff03b4@haiku-os.org> #2149: Haiku does not update name of a renamed volume until after a reboot ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bga): As the other bug was marked a duplicate of this one, Haiku should also update the mount point (when the mount point is automatically created by, say, Tracker) as a user usually will expect to find the mount point at /VolumeName. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 18:26:39 2008 From: trac at haiku-os.org (bga) Date: Fri, 08 Aug 2008 16:26:39 -0000 Subject: [Haiku-bugs] [Haiku] #2590: Haiku gets confused with 2 volumes with the same name. In-Reply-To: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> References: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> Message-ID: <047.52c01fa37228dccf3c8e7acad21f0d5c@haiku-os.org> #2590: Haiku gets confused with 2 volumes with the same name. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): The KDL capture I just attached was obtained after initializing the second volume and trying to reboot. typing reboot resulted in the "Failed to load OS" message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 19:05:12 2008 From: trac at haiku-os.org (dancso.robert) Date: Fri, 08 Aug 2008 17:05:12 -0000 Subject: [Haiku-bugs] [Haiku] #2588: Boot error on Gigabyte N211U notebook In-Reply-To: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> References: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> Message-ID: <057.f10f036b509f62110564045db3a40c9e@haiku-os.org> #2588: Boot error on Gigabyte N211U notebook ---------------------------------+------------------------------------------ Reporter: dancso.robert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by dancso.robert): Hello! I have BeOS R5 Pro and Windows XP Home on my notebook. I installed Haiku from an image-file from the BeOS to a blank partition: mount haiku-image, and copy everything to the blank bfs volume, made bootable the Haiku, and I tried to use the BeOS boot manager, and without that. Nothing.[[BR]] I tried this: with QEMU I booted the raw disk, and it worked (~as design)! [[BR]] I tried to use any other (not BeOS like) OS (SuSe, Gentoo, QNX, Windows) and they worked well.[[BR]] I think maybe the the notebook's (VGA)BIOS is different than the others, so maybe we need jut a little modify for the zbeos.[[BR]] I'm sorry, but I cannot send any other detail, because I don't get any (no error message, just a black screen, no disk usage, no voice, nothing). If (on R5 / Dano boot) I use the original zbeos, it is booting up, all icons lights up, and the GUI... But during boot if I press any key the system halted.[[BR]] I think it is not (only) a Haiku error, because I've got this in other BeOS versions what have graficaly modified zbeos (like Zeta).[[BR]] So; when trying to change the boot screen (other than the BIOS screen), or hit any key, than only the reset helps. And on Haiku before the boot logo I've got only a blinking cursor in the top-left corner on the screen.[[BR]] Thanks! R?bert -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 19:30:31 2008 From: trac at haiku-os.org (axeld) Date: Fri, 08 Aug 2008 17:30:31 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.3bdb139a02bcc58d32ead65254d72a13@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by axeld): I reverted that change again, but only because I misread the commit message (I thought anxiety didn't have the hardware, not me). In any case, I do have this chip: {{{device 8167: RTL-8110SC/8169SC Gigabit Ethernet}}} and it doesn't work anymore after the change. 0x14 is just a part of the standard config space that declares the base addresses (and a different than 0x18). Dunno why this seem to work this way on Linux. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 19:46:07 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 08 Aug 2008 17:46:07 -0000 Subject: [Haiku-bugs] [Haiku] #2588: Boot error on Gigabyte N211U notebook In-Reply-To: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> References: <048.8d45af5323c5aae851f6eb07bfd7990e@haiku-os.org> Message-ID: <057.8ad581c5fd26b1dc9a7dbcc484529976@haiku-os.org> #2588: Boot error on Gigabyte N211U notebook ---------------------------------+------------------------------------------ Reporter: dancso.robert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by mmlr): I don't quite understand yet what your configuration is when you attempt that boot. What I gather is that you have a partitions like that: 1: Windows XP 2: BeOS R5 Pro 3: Haiku Now what boot manager are you using to choose between them? Have you added the Haiku to that boot manager? How did you make the Haiku partition bootable? When you say you tried booting the raw disk with QEMU you mean that you did like "qemu -snapshot /dev/disk/ide/ata/0/master/0/raw" and it worked? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 22:02:44 2008 From: trac at haiku-os.org (rvndrk32) Date: Fri, 08 Aug 2008 20:02:44 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load Message-ID: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> #2591: haiku fail to boot load -----------------------+---------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- 'Either you use a version of BeOS to do the setup with DriveSetup or mkbfs or you use Haiku itself with the Installer or DriveSetup. Once you've created and initialized the target partition you can mount the image (using tools like Mount Image or through the Terminal) and copy over all the files. If you are under Haiku, you can just as well use the Installer to make a duplicate of your currently booted installation.' no.try again.doesn't work.formats okay.not bootable. 'If you for example copy such an image directly to a USB drive starting from 0, overwriting the MBR (destoying all partitions already there), then this will boot.' like the dd command or the russian software that does this? dont think so, tried and failed. ' To make sure a partition boot record is there and it contains the right partition offset, you can use the tool "makebootable". Makebootable will do both, write the partition boot code to the beginning of the partition and detect and write the partition offset to where it is needed. You can use the makebootable from BeOS if you have a BeOS installation that has access to the partition in question.' not quite.its SUPPOSED to do this.it doesn't. ive used VBox and qemu, no luck. i believe the images (JPEGs)i still have of the process, may have taken them down from the net. you have to use grub and/or makebootable from within linux. its the only way i haven't tried yet. ----- Michael Lotz wrote: > Hi Richard > >> only issue with that is it doesnt boot.thus the need for grub >> loader. > > I think you are missing some bits and pieces here. Haiku can very well > be booted on real hardware since a long time. I have it seen running on > many machines, rest assured, and configured booted through various > means (BeOS bootman, GRUB, directly from the partition boot code). It > also boots fine from USB sticks. In fact I have written an article > about this topic this very day to explain parts involved and what is > compatible with what. You can find it at http://www.haiku- os.org/documents/user/how_to_get_haiku_booted. > Hope this helps. > > Regards > Michael > > -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 22:19:37 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 08 Aug 2008 20:19:37 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load In-Reply-To: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> References: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> Message-ID: <052.971555e60fc7b28430231084217b4845@haiku-os.org> #2591: haiku fail to boot load ------------------------+--------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Ok, now this is not helpful. The article describes how everything works together. It's the sum of all the steps that gets it bootable, not each single step alone. If you only format and copy you're obviously still missing the part about the partition... Please describe the exact steps you take here. What drives/partitions are involved? When you boot through emulation, what drives do you map/what commands do you use? What method of installation and what bootloader are you using? How is the bootloader configured? For most of us makebootable works just fine, if it doesn't in your case please provide more details. What does it output? What should it output (i.e. what offset does the partition in fact have)? Otherwise this is really very hard to pinpoint. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 22:42:19 2008 From: trac at haiku-os.org (rvndrk32) Date: Fri, 08 Aug 2008 20:42:19 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load In-Reply-To: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> References: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> Message-ID: <052.a0b86a04adb6fd5cc30ff476cdff2c96@haiku-os.org> #2591: haiku fail to boot load ------------------------+--------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rvndrk32): my bad.lemme explain: made a new image (qcow) with qemu.i think 250mb. used haiku to format with driveUtil.formats fine, show as 250mb drive. do the same on a hard disk attached as emu disk with -hdb=/dev/yyy and the size is misreported.(2TB on a 112GB drive as i recall...) Not only that, makebootable, when run from within Haiku at this point, does work on both. [zero offset for emu drive, non-zero for actual drive.you have to give makebootable the partition number on the phys. disk, as trying it normally hangs the process.(or either leave the disk still unbootable, i forget its been over a few weeks.)] during this process you must use: makebootable /dev/ata/0/disk/ (pulled from DiskUtil)for the phys. disk to be 'made' bootable, else returns the offset of zero, but wont work. you cant 'makebootable' the phys. disk as a whole drive, nor can you 'format' it that way.it has to be done as a partition.this is what haiku already does if you use a cleared hard disk thru qemu and try to format it or 'make' it 'BEOS'. the emu disk does not have this limitation. NOTE: copying the FS over is not necessary to reproduce this error, however it still occurs after a full copy with 'cp -R / '. However, the only BOOTABLE volume is the emulated one.(the file you made) hence the bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 22:45:59 2008 From: trac at haiku-os.org (rvndrk32) Date: Fri, 08 Aug 2008 20:45:59 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load In-Reply-To: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> References: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> Message-ID: <052.7969ab62ed1b06914b2bd1683b19854c@haiku-os.org> #2591: haiku fail to boot load ------------------------+--------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rvndrk32): the 'null' utility and haiku image put on the usb stick doesn't work either.only clone i have gotten successful to boot is ZETA cd.uses simlar method to what a boot image and haiku image put on disc would do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 23:29:17 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 21:29:17 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.4f05ff27795f9202411a8e7265740c02@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): {{{ call 14 -2 thread 37, scsi scheduler a017ef58 808dbcfe :do_io__FPvP11IOOperation(0x90d84de8, 0x90dcfbe0) kdebug> io_operation 0x90dcfbe0 io_operation at 0x90dcfbe0 parent: 0x90dd78c4 status: No Error (1) dma buffer: 0x90da8660 offset: 50769447424 (original: 50769447424) length: 0 (original: 0) transferred: 0 block size: 512 saved vec index: 1 saved vec length: 512 r/w: read phase: do all partial begin: no partial end: no bounce buffer: no }}} Hope that helps :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 23:44:55 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 21:44:55 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.4e8352b2c9a70d56dd302f09cfd006b3@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): And just in case, the io buffer: {{{ IOBuffer at 0x90d94780 origin: user kind: physical length: 131072 capacity: 23 vecs: 23 [0] 0x291ee000, 8192 [1] 0x291f1000, 4096 [2] 0x291f0000, 4096 [3] 0x291f2000, 24576 [4] 0x20d4c000, 8192 [5] 0x20d5c000, 8192 [6] 0x2c332000, 4096 [7] 0x2c331000, 4096 [8] 0x2c330000, 4096 [9] 0x2c2b7000, 4096 [10] 0x2c2b6000, 4096 [11] 0x2bd6f000, 4096 [12] 0x2bd5e000, 4096 [13] 0x2bd5d000, 4096 [14] 0x2bd5c000, 4096 [15] 0x2bd16000, 4096 [16] 0x2bd05000, 4096 [17] 0x2bcec000, 4096 [18] 0x2bceb000, 4096 [19] 0x2bce8000, 4096 [20] 0x2bcd7000, 4096 [21] 0x293d2000, 8192 [22] 0x294c0000, 4096 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 00:17:02 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 08 Aug 2008 22:17:02 -0000 Subject: [Haiku-bugs] [Haiku] #2592: Solaris does not define NAME_MAX Message-ID: <043.9e51f9de9efbc6ab79f39eba089364cf@haiku-os.org> #2592: Solaris does not define NAME_MAX --------------------------+------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- {{{B_FILE_NAME_LENGTH}}} is defined to {{{NAME_MAX}}} in {{{headers/build/os/storage/StorageDefs.h}}}, leading to compilation failure in {{{OS.h}}}. Apparently this symbol is not mandatory in POSIX and may vary. The {{{pathconf}}} function would in theory be used to retrieve that value from file name or file descriptor. We should probably define {{{B_FILE_NAME_LENGTH}}} to some sensible constant value in that case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 00:21:16 2008 From: trac at haiku-os.org (scottmc) Date: Fri, 08 Aug 2008 22:21:16 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization In-Reply-To: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> References: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> Message-ID: <051.2bfe0a1d83ee18d4624cb3d1cf232400@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization --------------------------------------+------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by scottmc): Using r26876 I was able to check this and it is in fact working as it's supposed to be, so this one can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 01:16:33 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 08 Aug 2008 23:16:33 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.c547a38581970d84b13e7f5b0aff6434@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks, excellent info! The problem should be fixed in r26881. Please reopen, if it isn't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 01:18:50 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 23:18:50 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.0f044d871eeb720bc7d50e849f4c5fdc@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): Thank Axel for the nice io_* kdebug commands :) And will give it a try in a bit, might need to reinit that partition depending on what happened to it there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 02:23:07 2008 From: trac at haiku-os.org (andreasf) Date: Sat, 09 Aug 2008 00:23:07 -0000 Subject: [Haiku-bugs] [Haiku] #2593: Solaris does not define __progname Message-ID: <043.ab7cadc6c9e64b8b0e9c9ddb16a235a7@haiku-os.org> #2593: Solaris does not define __progname --------------------------+------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- On a Solaris host, {{{__progname}}} is not defined. It is used by some of the tools, e.g. {{{rc}}} and {{{mimeset}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 02:23:53 2008 From: trac at haiku-os.org (rvndrk32) Date: Sat, 09 Aug 2008 00:23:53 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load In-Reply-To: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> References: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> Message-ID: <052.1950bf85029b045905e9084e6e1c0421@haiku-os.org> #2591: haiku fail to boot load ------------------------+--------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rvndrk32): gotya so far, but everything I read says: Haiku must write to the root of the drive to boot.(boot sector) bootman from Haiku wont work, as clearly dictated in german in ZETA.'there is no room near begining of drive', even on a blank drive.same responce in Haiku. isnt the latter the whole reason we need grub? yet you refuse to endorse it,saying you want your own. :-P. I used DiskUtil on the blank drive followed by 'makebootable ' I pulled the info for the drive from Haiku's DiskUtil under qemu, as it was the phys.disk.even with three hard drives, it still showed up. drive 1 was base image(vmware image) drive 2 was phys. drive(over usb) drive 3 was new haiku drive (empty file) followed by a 'cp -R / ' to copy over the contents. *** use the info for the bigger of the drives listed.i used a 120gb external, YMMV.It could not be attached to my IDE bus as my optical drive was taking up the other connection. i think it was atttached as /dev/disk4, as I was using (Kalyway Intel) Leopard at the time. disks 2 and 3 were part of a sata raid system. even such, ubuntu should yield similar.qemu's options are the same.qemu's responce is the same. mount commands are the same.i didnt do anything out of the ordinary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 23:14:18 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 08 Aug 2008 21:14:18 -0000 Subject: [Haiku-bugs] [Haiku] #2591: haiku fail to boot load In-Reply-To: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> References: <043.a83b713aec893fb875c0382761bb86cf@haiku-os.org> Message-ID: <052.20c16fe1ea85ded8a81033a215e1dc03@haiku-os.org> #2591: haiku fail to boot load ------------------------+--------------------------------------------------- Reporter: rvndrk32 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): > made a new image (qcow) with qemu.i think 250mb. > used haiku to format with driveUtil.formats fine, show as 250mb drive. > > do the same on a hard disk attached as emu disk with -hdb=/dev/yyy and the size is misreported.(2TB on a 112GB drive as i recall...) That's a strong indication of something really not working with the disk drivers / controller drivers / partitioning modules / filesystem modules. It's not surprising that after this it doesn't boot. Please include detailed information as to what command you used to do that so we can look further. > [zero offset for emu drive, non-zero for actual drive.you have to give makebootable the partition number on the phys. disk, as trying it normally hangs the process.(or either leave the disk still unbootable, i forget its been over a few weeks.)] If you have an empty emulated image without partition, a zero offset is expected as your filesystem actually starts at 0. > during this process you must use: > makebootable /dev/ata/0/disk/ (pulled from DiskUtil)for the phys. disk to be 'made' bootable, else returns the offset of zero, but wont work. > > you cant 'makebootable' the phys. disk as a whole drive, nor can you 'format' it that way.it has to be done as a partition.this is what haiku already does if you use a cleared hard disk thru qemu and try to format it or 'make' it 'BEOS'. Yes you can't and you shouldn't. Makebootable is not supposed to install a boot manager. It is installing a partition boot record to the start of the target partition. So you have to instruct it what partition is the target. If you need a boot manager, you have to install a boot manager. If you don't need a boot manager, you still need a boot manager, because you always need some kind of boot manager, even if it is only chainloading the partition boot record of the "active" partition afterwards. That's what an fdisk does install for example. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 8 23:38:02 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 Aug 2008 21:38:02 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.331a6a652850a36adc60c69ab1ef1a9a@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): A few more things (thanks to mmlr for tips): {{{ DMABuffer at 0x90da8660 bounce buffer: 0x90ca4000 (physical 0xf768000) bounce buffer size: 16384 vecs: 0 io_request at 0x90dd78c4 parent: 0xa18977e8 status: No Error (1) mutex: 0x90dd78e0 IOBuffer: 0x90d94780 offset: 50769349120 length: 131072 transfer size: 98304 relative offset: 0 pending children: 2 flags: 0x1 team: 472 r/w: read partial transfer: no finished cvar: 0x90dd7930 iteration: vec index: 16 vec offset: 0 remaining bytes: 32768 callbacks: finished 0x00000000, cookie 0x00000000 iteration 0x00000000, cookie 0x00000000 children: 0x90dcfb40 0x90dcfbe0 Going off of that, the other child op: io_operation at 0x90dcfb40 parent: 0x90dd78c4 status: No error dma buffer: 0x90da84c8 offset: 50769349120 (original: 50769349120) length: 98304 (original: 98304) transferred: 98304 block size: 512 saved vec index: 1 saved vec length: 512 r/w: read phase: do all partial begin: no partial end: no bounce buffer: no And its DMA buffer: DMABuffer at 0x90da84c8 bounce buffer: 0x90c9c000 (physical 0xf760000) bounce buffer size: 16384 vecs: 16 [0] 0x291ee000, 8192 [1] 0x291f1000, 4096 [2] 0x291f0000, 4096 [3] 0x291f2000, 24576 [4] 0x20d4c000, 8192 [5] 0x20d5c000, 8192 [6] 0x2c332000, 4096 [7] 0x2c331000, 4096 [8] 0x2c330000, 4096 [9] 0x2c2b7000, 4096 [10] 0x2c2b6000, 4096 [11] 0x2bd6f000, 4096 [12] 0x2bd5e000, 4096 [13] 0x2bd5d000, 4096 [14] 0x2bd5c000, 4096 [15] 0x2bd16000, 4096 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 06:20:56 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 09 Aug 2008 04:20:56 -0000 Subject: [Haiku-bugs] [Haiku] #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add-ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 In-Reply-To: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> References: <044.51c8246685016e22ecbb1c767b88c509@haiku-os.org> Message-ID: <053.fb3745a5ee5c337db230cfc2c305a763@haiku-os.org> #2586: PANIC: ASSERT FAILED (/usr/home/rene/devel/src/add- ons/kernel/bus_managers/ata/ata_request.c:83): status != 0x01 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: marcusoverhagen Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): Doesn't seem to KDL any more, but the issue mentioned in ticket #2584 still seems to be present after this fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 02:40:51 2008 From: trac at haiku-os.org (anxiety) Date: Sat, 09 Aug 2008 00:40:51 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.3013b5d87a8fc11afbca424d72396148@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Changes (by anxiety): * cc: codeanxiety at gmail.com (added) Comment: I've downloaded a few more linux drivers for different cards. I was wrong, there was a difference between the two... 8169 uses PCI_BASE_ADDRESS_1 (0x14) and 8168 uses PCI_BASE_ADDRESS_2 (0x18). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 07:53:35 2008 From: trac at haiku-os.org (meanwhile) Date: Sat, 09 Aug 2008 05:53:35 -0000 Subject: [Haiku-bugs] [Haiku] #1470: Mouse Speed and Acceleration have limited positions In-Reply-To: <044.f111214fb6540143725ea3a998be0174@haiku-os.org> References: <044.f111214fb6540143725ea3a998be0174@haiku-os.org> Message-ID: <053.aa8d2b33b1ff1e8b2d2aeb1c9b02e928@haiku-os.org> #1470: Mouse Speed and Acceleration have limited positions ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Works very well...Thank You Very Much ! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 07:58:04 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 09 Aug 2008 05:58:04 -0000 Subject: [Haiku-bugs] [Haiku] #2584: File corruption In-Reply-To: <043.f3f3ddfc5863955f5bc5c9765fae1490@haiku-os.org> References: <043.f3f3ddfc5863955f5bc5c9765fae1490@haiku-os.org> Message-ID: <052.a0f986995edf049f0f3f2599fa929be9@haiku-os.org> #2584: File corruption ----------------------------+----------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * cc: rgollent at cs.arizona.edu (added) * priority: normal => critical * component: - General => System/Kernel * milestone: R1 => R1/alpha1 Comment: I've been trying to find a way to duplicate this one consistently but thus far I haven't succeeded. A subset of the files from an svn checkout seem to wind up with garbage data towards the end, but the attached test driver for instance does not manage to trigger the problem, even with several hundred concurrent threads. Does svn use the normal stdio calls to write files or is it perhaps using some other syscall that might have fancier semantics that are triggering the bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 10:30:14 2008 From: trac at haiku-os.org (axeld) Date: Sat, 09 Aug 2008 08:30:14 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.f69ab707d301ddaadedeb8048397d3ff@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by axeld): I just take a look at the linux r8169.c driver, and it does indeed use different base addresses. I'll just implement this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 11:45:54 2008 From: trac at haiku-os.org (axeld) Date: Sat, 09 Aug 2008 09:45:54 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.abeac457d953e9c4e1d634e98b635381@haiku-os.org> #1853: RTL8168 recognized but not working ------------------------------+--------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26886. Test reports welcome :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 9 13:07:33 2008 From: trac at haiku-os.org (stippi) Date: Sat, 09 Aug 2008 11:07:33 -0000 Subject: [Haiku-bugs] [Haiku] #2594: [TPC] PANIC: ASSERT FAILED (src/add-ons/kernel/network/protocols/tcp/BufferQueue.cpp:304): buffer != __null Message-ID: <041.58eaa22527266faa6a960baff4dca659@haiku-os.org> #2594: [TPC] PANIC: ASSERT FAILED (src/add- ons/kernel/network/protocols/tcp/BufferQueue.cpp:304): buffer != __null ------------------------------------+--------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Revision is r26680, no patches from newer revision applied to kernel stuff. I left the system running over night with a Transmission download (0.70 for BONE version). Returning to it in the morning, it showed the above panic. Here is the backtrace: {{{ stack trace for thread 2681 "torrent 0x18084e10" ... :panic :Get__11BufferQueueUlbPP10net_buffer + 0x0069 :ReadData__11TCPEndpointUlUlPP10net_buffer + 0x0307 :tcp_read_data__FP12net_protocolUlUlPP10net_buffer + 0x0029 :socket_receive__FP10net_socketP6msghdrPvUli + 0x0087 < :stack_interface_recvfrp__FP10net_socketPvUliP8sockaddrPUi + 0x008c :common_recvfrom__FiPvUliP8sockaddrPUib + 0x0055 :_user_recvfrom + 0x0091 syscall stuff ... }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 15:15:08 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 14 Aug 2008 13:15:08 -0000 Subject: [Haiku-bugs] [Haiku] #2605: PANIC: remove page 0x91d43ae8 from cache 0x976e5f78: page still has mappings! Message-ID: <042.0d362ba6cfe14179bd7ec16b42fc6f9c@haiku-os.org> #2605: PANIC: remove page 0x91d43ae8 from cache 0x976e5f78: page still has mappings! -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- {{{ runtime_loader: cannot open file pe heap_add_area: area 6468 added to small heap 0x90b62000 - usable range 0x99c07000 - 0x9a000000 PANIC: remove page 0x91d43ae8 from cache 0x976e5f78: page still has mappings! Welcome to Kernel Debugging Land... Thread 463 "execvp" running on CPU 0 kdebug> bt stack trace for thread 463 "execvp" kernel stack: 0x99650000 to 0x99654000 user stack: 0x78186000 to 0x781c6000 frame caller :function + offset 0 99653584 (+ 48) 800556fd :invoke_debugger_command + 0x00f5 1 996535b4 (+ 64) 800554ed :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 996535f4 (+ 64) 80055875 :invoke_debugger_command_pipe + 0x009d 3 99653634 (+ 48) 80056750 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 99653664 (+ 48) 80056106 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 99653694 (+ 224) 80057b1c :evaluate_debug_command + 0x0088 6 99653774 (+ 64) 80053b3a :kernel_debugger_loop__Fv + 0x01ae 7 996537b4 (+ 48) 80054703 :kernel_debugger + 0x0117 8 996537e4 (+ 192) 800545e1 :panic + 0x0029 9 996538a4 (+ 96) 800aedf3 :Delete__7VMCache + 0x0077 10 99653904 (+ 64) 800af278 :Unlock__7VMCache + 0x0124 11 99653944 (+ 64) 800b07bf :_RemoveConsumer__7VMCacheP7VMCache + 0x008f 12 99653984 (+ 96) 800af0ea :Delete__7VMCache + 0x036e 13 996539e4 (+ 64) 800af278 :Unlock__7VMCache + 0x0124 14 99653a24 (+ 48) 800af37f :ReleaseRef__7VMCache + 0x002b 15 99653a54 (+ 48) 800a8aa6 :delete_area__FP16vm_address_spaceP7vm_area + 0x00aa 16 99653a84 (+ 48) 800aaa41 :vm_delete_areas + 0x0079 17 99653ab4 (+ 80) 80048f8d :exec_team__FPCcRPPcUlll + 0x0129 18 99653b04 (+1088) 8004b5d4 :_user_exec + 0x0084 19 99653f44 (+ 100) 800bad72 :pre_syscall_debug_done + 0x0002 (nearest) user iframe at 0x99653fa8 (end = 0x99654000) eax 0x22 ebx 0xa1bce0 ecx 0x781c4840 edx 0xffff0104 esi 0x781c6008 edi 0x15 ebp 0x781c498c esp 0x99653fdc eip 0xffff0104 eflags 0x203 user esp 0x781c4840 vector: 0x63, error code: 0x0 20 99653fa8 (+ 0) ffff0104 21 781c498c (+1152) 009fbadb :unknown + 0x8cadb 22 781c4e0c (+4464) 002eefe3 :unknown + 0xeefe3 23 781c5f7c (+ 48) 00362dc6 :unknown + 0x30dc6 24 781c5fac (+ 48) 00993bc0 :unknown + 0x24bc0 25 781c5fdc (+ 0) 781c5fec 6629:execvp_462_stack at 0x78186000 + 0x3ffec kdebug> cache 0x976e5f78 CACHE 0x976e5f78: ref_count: 0 source: 0x00000000 type: RAM virtual_base: 0x0 virtual_end: 0x1e8000 temporary: 1 scan_skip: 0 lock: 0x976e5fc0 lock.holder: 463 areas: consumers: pages: 101 in cache kdebug> page 0x91d43a90 PAGE: 0x91d43a90 queue_next,prev: 0x91d43c1c, 0x91d43a38 physical_number: ae6c cache: 0x976e5f78 cache_offset: 292 cache_next: 0x00000000 type: 0 state: modified wired_count: 0 usage_count: 3 busy_writing: 0 area mappings: 0x976b7af0 (0x1912) kdebug> area 0x976b7af0 AREA: 0x80303000 name: 'additional heap' owner: 0x1 id: 0x171f base: 0x97400000 size: 0x400000 protection: 0x30 wiring: 0x2 memory_type: 0x0 cache: 0x80302000 cache_type: RAM cache_offset: 0x0 cache_next: 0x00000000 cache_prev: 0x00000000 page mappings: 0 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 16:35:24 2008 From: trac at haiku-os.org (bga) Date: Thu, 14 Aug 2008 14:35:24 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.13ca8330078309bdda3243e84cf74d36@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): I just noticed the KDL I get in bug #2590 is exactly the one reported here. Do you guys happen to have 2 mounted partitions with the same name? See the other bug for more information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 17:48:10 2008 From: trac at haiku-os.org (axeld) Date: Thu, 14 Aug 2008 15:48:10 -0000 Subject: [Haiku-bugs] [Haiku] #2346: Some of headers are not self containing In-Reply-To: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> References: <042.e55a33ce082f1a29876a6af37364a93e@haiku-os.org> Message-ID: <051.5e80118e2b2661209680a289652ba236@haiku-os.org> #2346: Some of headers are not self containing ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: I left resolv.h as is, and the rest looks fine, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 17:52:57 2008 From: trac at haiku-os.org (un_spacyar) Date: Thu, 14 Aug 2008 15:52:57 -0000 Subject: [Haiku-bugs] [Haiku] #2606: Activity Monitor replicant - don't have option to delete the replicant Message-ID: <045.15950e718dbd98f7a12829983c31d541@haiku-os.org> #2606: Activity Monitor replicant - don't have option to delete the replicant ------------------------------------------+--------------------------------- Reporter: un_spacyar | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------------+--------------------------------- When I set the Activity Monitor app as a replicant, there are no option in the contextual menu to close/delete the replicant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 17:57:26 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 14 Aug 2008 15:57:26 -0000 Subject: [Haiku-bugs] [Haiku] #2606: Activity Monitor replicant - don't have option to delete the replicant In-Reply-To: <045.15950e718dbd98f7a12829983c31d541@haiku-os.org> References: <045.15950e718dbd98f7a12829983c31d541@haiku-os.org> Message-ID: <054.f941856df47d81ab2411f2f574aa837b@haiku-os.org> #2606: Activity Monitor replicant - don't have option to delete the replicant -------------------------------------------+-------------------------------- Reporter: un_spacyar | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2092 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 17:00:55 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 15:00:55 -0000 Subject: [Haiku-bugs] [Haiku] #2616: parsedate() with an invalid time value seesm to create stack corruption. In-Reply-To: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> References: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> Message-ID: <047.85d370ea576082854fd99ba81ccf9dad@haiku-os.org> #2616: parsedate() with an invalid time value seesm to create stack corruption. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Thanks for the nice test case! Fixed in r27006. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 22:49:21 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 16 Aug 2008 20:49:21 -0000 Subject: [Haiku-bugs] [Haiku] #2618: bfs: *** invalid run(0,0,0) Message-ID: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> #2618: bfs: *** invalid run(0,0,0) -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- {{{ Last message repeated 2 times. bfs: Insert:1307: Name in use bfs: Insert:1307: Name in use Last message repeated 3 times. bfs: Insert:1307: Name in use bfs: we have to panic... switch to read-only mode! bfs: *** invalid run(0,0,0) bfs: bfs_open:1131: Read-only file system Last message repeated 19 times. }}} I don't really know how to reproduce it. I was downloading an iso with firefox while using the system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 13:27:47 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 11:27:47 -0000 Subject: [Haiku-bugs] [Haiku] #1391: [Tracker] don't show icons for volumes in mount menu (easy) In-Reply-To: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> References: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> Message-ID: <049.2a15f534c60b1d46ceffc8957f4a9e09@haiku-os.org> #1391: [Tracker] don't show icons for volumes in mount menu (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks for the patch, I've applied it (among other stuff) in r27001. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 15:37:06 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 13:37:06 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. Message-ID: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. ----------------------------------+----------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I installed the R5 version of SpicyKeys (source and binaries can be found here: http://www.bebits.com/app/385) and the mouse event generator is not working (you were supposed to be able to move the mouse with the keyboard). The keyboard capture code works ok as I can launch applications assigned to hot-keys so I guess it is probably some compatibility issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 12:33:29 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Fri, 15 Aug 2008 10:33:29 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.ec2abf834c8dbb8fe1887fb203f29e46@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by marcusoverhagen): Hi, Axel is correct, you can't simply remove a copyright and replace it with a different one. Adding an author list will not heal this error. Regarding the 3 posix headers with copyright attribution to me, I'll clear those up for sake of conformity myself (this afternoon). But I still see a problem. The Copyright headers usually mention a year for example in wchar.t it's 2002. Looking at http://svn.berlios.de/viewcvs/haiku/haiku/trunk/headers/posix/wchar.h?rev=25433&view=log I see that this file has been worked on in 2002, 2003, 2005, 2006, 2007 and 2008. Thus, instead of doing - Copyright (C) 2002 Marcus Overhagen + Copyright 2002 Haiku Inc. All Rights Reserved. I think I'll have to add + Copyright 2002-2003, 2005-2008 Haiku Inc. All Rights Reserved. or + Copyright 2002, 2003, 2005-2008 Haiku Inc. All Rights Reserved. what do you guys think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 23:05:16 2008 From: trac at haiku-os.org (scottmc) Date: Sat, 16 Aug 2008 21:05:16 -0000 Subject: [Haiku-bugs] [Haiku] #1869: Mediaplayer errors out instead of displaying a dialog box explaining missing codec In-Reply-To: <042.3cf96e9162eca251bd5001c5e96990e4@haiku-os.org> References: <042.3cf96e9162eca251bd5001c5e96990e4@haiku-os.org> Message-ID: <051.6404f08dc6746ac2fb0210917ad83ed9@haiku-os.org> #1869: Mediaplayer errors out instead of displaying a dialog box explaining missing codec ---------------------------------------+------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by scottmc): This seems to be fixed, just need to close out the ticket. I tried playing an unsupported video on r26990 and it gave me a dialog box warning about a missing codec, instead of dropping me to a debug dialog box. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 01:47:45 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 14 Aug 2008 23:47:45 -0000 Subject: [Haiku-bugs] [Haiku] #2523: Invalid Argument while trying to configure and/or make packages in Haiku In-Reply-To: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> References: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> Message-ID: <051.43460f80f84b4612584c4f199b3ac747@haiku-os.org> #2523: Invalid Argument while trying to configure and/or make packages in Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): With r26943 I have not yet seen this one show up, and that's after some heavy building/compiling sessions. So I think this one is ok to close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 01:49:18 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 14 Aug 2008 23:49:18 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.a5bc5dbd145ab85e035bfd690270d29f@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Go ahead and close this. I've been kicking r26943 and have yet to see this one show up, so it's probably been fixed as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 08:53:24 2008 From: trac at haiku-os.org (ekdahl) Date: Fri, 15 Aug 2008 06:53:24 -0000 Subject: [Haiku-bugs] [Haiku] #2608: Changing date & time preferences in Tracker doesn't invalidate concerned views Message-ID: <041.6d6a802b1de9ca55b09616d51f9db5d1@haiku-os.org> #2608: Changing date & time preferences in Tracker doesn't invalidate concerned views ----------------------------------+----------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- It draws over the old text instead. See attached screenshot. I'm using VESA graphics, if that matters. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 11:13:27 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 17 Aug 2008 09:13:27 -0000 Subject: [Haiku-bugs] [Haiku] #2618: bfs: *** invalid run(0,0,0) In-Reply-To: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> References: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> Message-ID: <051.ed727467f6da50c443598a99881bf176@haiku-os.org> #2618: bfs: *** invalid run(0,0,0) ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): I actually managed to reproduced it three times while downloading an iso, and selecting Open with Tracker instead of saving it on disk, but I don't think that's relevant anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 09:11:06 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 07:11:06 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal as replicant doesn't respect settings In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.10d7019f39d6a3581ad4e988aeb9f779@haiku-os.org> #2215: Terminal as replicant doesn't respect settings ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Thanks for the note. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 16:48:16 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 14:48:16 -0000 Subject: [Haiku-bugs] [Haiku] #2143: KDL in net timer. In-Reply-To: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> References: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> Message-ID: <047.ecd1f2bac2f572b8b409f8ba400e6983@haiku-os.org> #2143: KDL in net timer. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: The issue should be fixed with r26981 (the uninit_timer() problem in r26980). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 00:06:10 2008 From: trac at haiku-os.org (mmlr) Date: Sat, 16 Aug 2008 22:06:10 -0000 Subject: [Haiku-bugs] [Haiku] #1869: Mediaplayer errors out instead of displaying a dialog box explaining missing codec In-Reply-To: <042.3cf96e9162eca251bd5001c5e96990e4@haiku-os.org> References: <042.3cf96e9162eca251bd5001c5e96990e4@haiku-os.org> Message-ID: <051.a4e5549efe77cd6b813d74986efe5e14@haiku-os.org> #1869: Mediaplayer errors out instead of displaying a dialog box explaining missing codec ---------------------------------------+------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Closing as requested. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 11:30:11 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 09:30:11 -0000 Subject: [Haiku-bugs] [Haiku] #2619: SOB17 is not work In-Reply-To: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> References: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> Message-ID: <050.fa745a7c49177f2cead32fe5245830c8@haiku-os.org> #2619: SOB17 is not work ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: x64 | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Sorry, but what is "SB17", and where can I get an Haiku version of it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 13:43:15 2008 From: trac at haiku-os.org (bga) Date: Sat, 16 Aug 2008 11:43:15 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.9e4bf0c5cd02fb0b0c1f6d0955b0398c@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by bga): * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 19:23:48 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 17:23:48 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' does not work In-Reply-To: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> References: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> Message-ID: <052.4cf09bd188d37f78a34d0c818454b755@haiku-os.org> #2612: 'Save as' does not work --------------------------------------+------------------------------------- Reporter: andreasf | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/StyledEdit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * owner: axeld => korli * component: - General => Applications/StyledEdit * milestone: R1 => R1/alpha1 Comment: As far as Pe is concerned, it doesn't like to save an unchanged file, and it doesn't do so even in the "Save As" case; if you have any pending changes, "Save As" should work just fine. I don't know what's the issue is in StyledEdit, but maybe it's something similar. In any case, Pe bugs should be reported at the proper place: http://developer.berlios.de/bugs/?group_id=5154 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 15:28:37 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 13:28:37 -0000 Subject: [Haiku-bugs] [Haiku] #2609: /boot/beos/apps/* should have symlinks inside /boot/apps Message-ID: <038.e660129db0a4d6632a1aff15a275a06f@haiku-os.org> #2609: /boot/beos/apps/* should have symlinks inside /boot/apps ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- In BeOS, all aplications inside /boot/beos/apps were symlinked inside /boot/apps. The reason was because /boot/apps was supposed to be a place where the user finds all applications available. Other than that, some R5 programs (like SpicyKeys) launch programs like the Terminal by path and tries to launch it as /boot/apps/Terminal, which obviously fails. I guess this is part of the R5 compatibility goal. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 18:51:36 2008 From: trac at haiku-os.org (bga) Date: Sat, 16 Aug 2008 16:51:36 -0000 Subject: [Haiku-bugs] [Haiku] #2616: parsedate() with an invalid time value seesm to create stack corruption. Message-ID: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> #2616: parsedate() with an invalid time value seesm to create stack corruption. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- I have this email on my account that when parsed by MDR crashes it. More specifically, it crashes in parsedate(). I was able to determine that preparseDate() errors out (more specifically here: {{{ // if we're reached our maximum number of elements, bail out if (index >= MAX_ELEMENTS) return B_ERROR; }}} Then parsedate_etc() catched the error and return it to parsedate(): {{{ if (preparseDate(dateString, elements) < B_OK) { *_flags = PARSEDATE_INVALID_DATE; return B_ERROR; } }}} This was supposed to return to parsedate() which would in turn return the error but it never actually returns. To be sure I changed parsedate() to: {{{ time_t parsedate(const char *dateString, time_t now) { int flags = 0; printf("calling parsedate_etc()\n"); time_t result = parsedate_etc(dateString, now, &flags); printf("returned from parsedate_etc()\n"); return result; } }}} The second printf is never printed. I get a segfault and the following useless stack crawl on gdb: {{{ [Switching to team /system/servers/mail_daemon (5651) thread BGA(BUG-Br) (5659)] 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () (gdb) }}} The emails that causes this is attached. Note the problem is its "Date" header line. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 14:43:05 2008 From: trac at haiku-os.org (mmlr) Date: Sat, 16 Aug 2008 12:43:05 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.093134a3376912ed30acd239380054dd@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Description changed by mmlr: Old description: > I have been doing experiments on a real Haiku installation and playing > with emails I just noticed the indexes are not being correctly > maintained. > > Here is what I mean: > > ~> query MAIL:subject=\* > > /boot/home/development/mdr/AGMSBayesianSpamServer/SoundUncertain > /boot/home/development/mdr/outbound_filters > /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpamServer\ > Settings > /boot/home/development/mdr/bemail/ObjectList.h > /boot/home/development/mdr/bemail > /boot/home/development/mdr/daemon/.cvsignore > /boot/home/development/mdr/bemail/Enclosures.cpp > /boot/home/development/mdr/lib/crypt.cpp > /boot/home/development/spam_server/CVS/Entries > /boot/home/development/mdr/config/ConfigWindow.cpp > /boot/home/development/mdr/bemail/QueryMenu.cpp > /boot/home/development/mdr/CVSROOT/verifymsg > /boot/home/development/mdr/CVSROOT/modules > /boot/home/development/mdr/inbound_protocols > /boot/home/development/mdr/CVSROOT/notify > /boot/home/development/mdr/bemail/Content.h > /boot/home/development/mdr/bemail/Content.cpp > /boot/home/development/mdr/lib/numailkit.cpp > /boot/home/development/mdr/lib/status.cp > /boot/home/development/mdr/config/ConfigWindow.h > /boot/home/development/mdr/bemail/FindWindow.h > /boot/home/development/mdr/bemail/Header.cpp > /boot/home/development/mdr/bemail/LICENSE > /boot/home/development/mdr/bemail/Mail.cpp > /boot/home/development/mdr/bemail/Prefs.h > /boot/home/development/mdr/inbound_protocols/makefile > /boot/home/development/mdr/lib > /boot/home/development/mdr/bemail/Signature.h > /boot/home/development/mdr/bemail/BeMail.rsrc > /boot/home/development/mdr/bemail/Signature.cpp > /boot/home/development/mdr/bemail/QueryMenu.h > /boot/home/development/mdr/daemon/SlowMenu.h > /boot/home/development/mdr/AGMSBayesianSpamServer/BuyLogoLayers.image.x-becasso > /boot/home/development/mdr/bemail/Utilities.cpp > /boot/home/development/mdr/bemail/WIndex.cpp > /boot/home/development/mdr/bemail/Words.cpp > /boot/home/development/mdr/bemail/WIndex.h > /boot/home/development/mdr/bemail/Words.h > /boot/home/development/mdr/bemail/geekspeak > /boot/home/development/mdr/bemail/Utilities.h > /boot/home/development/mdr/config/E-mail.rsrc > /boot/home/development/mdr/daemon/NavMenu.h > /boot/home/development/mdr/bemail/BmapButton.h > /boot/home/development/mdr/daemon/main.cp > > And, just to confirm in one file: > > ~> listattr /boot/home/development/mdr/daemon/main.cp > File: /boot/home/development/mdr/daemon/main.cp > Type Size Name > ----------- --------- ------------------------------- > > 0 bytes total in attributes. > > I was working with those files before I checked the email so it looks a > lot like BFS getting confused about the inodes that it puts on the > indexes. New description: I have been doing experiments on a real Haiku installation and playing with emails I just noticed the indexes are not being correctly maintained. Here is what I mean: {{{ ~> query MAIL:subject=\* /boot/home/development/mdr/AGMSBayesianSpamServer/SoundUncertain /boot/home/development/mdr/outbound_filters /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpamServer\ Settings /boot/home/development/mdr/bemail/ObjectList.h /boot/home/development/mdr/bemail /boot/home/development/mdr/daemon/.cvsignore /boot/home/development/mdr/bemail/Enclosures.cpp /boot/home/development/mdr/lib/crypt.cpp /boot/home/development/spam_server/CVS/Entries /boot/home/development/mdr/config/ConfigWindow.cpp /boot/home/development/mdr/bemail/QueryMenu.cpp /boot/home/development/mdr/CVSROOT/verifymsg /boot/home/development/mdr/CVSROOT/modules /boot/home/development/mdr/inbound_protocols /boot/home/development/mdr/CVSROOT/notify /boot/home/development/mdr/bemail/Content.h /boot/home/development/mdr/bemail/Content.cpp /boot/home/development/mdr/lib/numailkit.cpp /boot/home/development/mdr/lib/status.cp /boot/home/development/mdr/config/ConfigWindow.h /boot/home/development/mdr/bemail/FindWindow.h /boot/home/development/mdr/bemail/Header.cpp /boot/home/development/mdr/bemail/LICENSE /boot/home/development/mdr/bemail/Mail.cpp /boot/home/development/mdr/bemail/Prefs.h /boot/home/development/mdr/inbound_protocols/makefile /boot/home/development/mdr/lib /boot/home/development/mdr/bemail/Signature.h /boot/home/development/mdr/bemail/BeMail.rsrc /boot/home/development/mdr/bemail/Signature.cpp /boot/home/development/mdr/bemail/QueryMenu.h /boot/home/development/mdr/daemon/SlowMenu.h /boot/home/development/mdr/AGMSBayesianSpamServer/BuyLogoLayers.image.x-becasso /boot/home/development/mdr/bemail/Utilities.cpp /boot/home/development/mdr/bemail/WIndex.cpp /boot/home/development/mdr/bemail/Words.cpp /boot/home/development/mdr/bemail/WIndex.h /boot/home/development/mdr/bemail/Words.h /boot/home/development/mdr/bemail/geekspeak /boot/home/development/mdr/bemail/Utilities.h /boot/home/development/mdr/config/E-mail.rsrc /boot/home/development/mdr/daemon/NavMenu.h /boot/home/development/mdr/bemail/BmapButton.h /boot/home/development/mdr/daemon/main.cp }}} And, just to confirm in one file: {{{ ~> listattr /boot/home/development/mdr/daemon/main.cp File: /boot/home/development/mdr/daemon/main.cp Type Size Name ----------- --------- ------------------------------- 0 bytes total in attributes. }}} I was working with those files before I checked the email so it looks a lot like BFS getting confused about the inodes that it puts on the indexes. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 08:26:33 2008 From: trac at haiku-os.org (ekdahl) Date: Fri, 15 Aug 2008 06:26:33 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers (was: Updated posix license headers) In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.29920de7a586c9273a5d1d24cd47f33e@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by ekdahl): I've updated the patches to the current revision. Is there any interest in them or should I just drop them? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 09:24:50 2008 From: trac at haiku-os.org (ekdahl) Date: Fri, 15 Aug 2008 07:24:50 -0000 Subject: [Haiku-bugs] [Haiku] #1816: Tracker doesn't properly redraw modified date column when date&time format changed (seems easy) In-Reply-To: <038.2f568491c4d0c08de3126845fafd75e7@haiku-os.org> References: <038.2f568491c4d0c08de3126845fafd75e7@haiku-os.org> Message-ID: <047.61be637ad690ce83a2044a4f8c51dabb@haiku-os.org> #1816: Tracker doesn't properly redraw modified date column when date&time format changed (seems easy) -----------------------------+---------------------------------------------- Reporter: hma | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: 2608 -----------------------------+---------------------------------------------- Comment(by ekdahl): It applies to the other columns as well. You can see that the text edges get darker in the name column after the change, ie it draws over the old text. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 23:39:39 2008 From: trac at haiku-os.org (diver) Date: Thu, 14 Aug 2008 21:39:39 -0000 Subject: [Haiku-bugs] [Haiku] #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) In-Reply-To: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> References: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> Message-ID: <049.a2eedda9aa0da1273965e2d8616cbda5@haiku-os.org> #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): Could someone take a look at this patch please? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 20:32:34 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 18:32:34 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.3a00327233440d9c22544b53948f493d@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bga): I tried it again with "input_server -q" and got a crash. Funny thiunk is that I was sent to the userland debugger but them it filled the entire screen just like if it was KDL. Anyway, here is what I got on syslog: KERN: vm_soft_fault: va 0xe418a000 not covered by area in address space KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xe418a400, ip 0x3db602, write 0, user 1, thread 0x6c KERN: vm_page_fault: thread "input_server" (108) in team "input_server" (108) tried to read address 0xe418a400, ip 0x3db602 ("???" +0x3db602) KERN: debug_server: Thread 108 entered the debugger: Segment violation KERN: stack trace, current PC 0x3db602 ItemAt__C5BListl + 0x16: KERN: (0x7ffeea1c) 0x21bc82 StopMonitoringDevice__13DeviceManagerP14_BDeviceAddOn_PCc + 0xfe KERN: (0x7ffeeadc) 0x2163b0 StopMonitoringDevice__18BInputServerDevicePCc + 0x2c KERN: (0x7ffeeb0c) 0x5d8529 _._16MouseInputDevice + 0x31 KERN: (0x7ffeeb3c) 0x218945 UnregisterAddOns__12AddOnManager + 0x145 KERN: (0x7ffeebcc) 0x21768b SaveState__12AddOnManager + 0x1f KERN: (0x7ffeebfc) 0x211c79 QuitRequested__11InputServer + 0x71 KERN: (0x7ffeec2c) 0x2dba80 _QuitRequested__7BLooperP8BMessage + 0x30 KERN: (0x7ffeecac) 0x2da052 DispatchMessage__7BLooperP8BMessageP8BHandler + 0x46 KERN: (0x7ffeecdc) 0x2d13bd DispatchMessage__12BApplicationP8BMessageP8BHandler + 0x401 KERN: (0x7ffeeecc) 0x2db9d5 task_looper__7BLooper + 0x211 KERN: (0x7ffeef0c) 0x2cfb2d Run__12BApplication + 0x75 KERN: (0x7ffeef4c) 0x215c0e main + 0x6e KERN: (0x7ffeef7c) 0x210837 _start + 0x5b KERN: (0x7ffeefac) 0x1008ea (runtime_loader_seg0ro + 0x8ea) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 15:34:24 2008 From: trac at haiku-os.org (monni) Date: Fri, 15 Aug 2008 13:34:24 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.cbb6b45a99e8200e73f4470b0e00b09c@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by monni): I think mentioning current year (the day copyright holder(s) were altered) as first year in range would be legal-wise clearest case. This is from previous experience on similar case. As far as law goes copyright doesn't end even though years mentioned in the copyright statement don't include current year... I partly agree in what axeld said about current practice being to include the last year of change, but I think better wording would be to change/add "end" year when file is modified next time (excluding changes to copyright statement), if and only if it already includes Haiku Inc. (or OpenBeOS) in copyright statement. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 23:36:35 2008 From: trac at haiku-os.org (diver) Date: Thu, 14 Aug 2008 21:36:35 -0000 Subject: [Haiku-bugs] [Haiku] #1391: [Tracker] don't show icons for volumes in mount menu (easy) In-Reply-To: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> References: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> Message-ID: <049.929832724d438ffbf06edc176cb77a45@haiku-os.org> #1391: [Tracker] don't show icons for volumes in mount menu (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by diver): Could someone take a look at this patch? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 13:42:00 2008 From: trac at haiku-os.org (bga) Date: Sat, 16 Aug 2008 11:42:00 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.afbbbbcd5459cc1f1da6c207361d967e@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Description changed by bga: Old description: > I have been doing experiments on a real Haiku installation and playing > with emails I just noticed the indexes are not being correctly > maintained. > > Here is what I mean: > > ~> query MAIL:subject=\* > /boot/home/development/mdr/AGMSBayesianSpamServer/SoundUncertain > /boot/home/development/mdr/outbound_filters > /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpamServer\ > Settings > /boot/home/development/mdr/bemail/ObjectList.h > /boot/home/development/mdr/bemail > /boot/home/development/mdr/daemon/.cvsignore > /boot/home/development/mdr/bemail/Enclosures.cpp > /boot/home/development/mdr/lib/crypt.cpp > /boot/home/development/spam_server/CVS/Entries > /boot/home/development/mdr/config/ConfigWindow.cpp > /boot/home/development/mdr/bemail/QueryMenu.cpp > /boot/home/development/mdr/CVSROOT/verifymsg > /boot/home/development/mdr/CVSROOT/modules > /boot/home/development/mdr/inbound_protocols > /boot/home/development/mdr/CVSROOT/notify > /boot/home/development/mdr/bemail/Content.h > /boot/home/development/mdr/bemail/Content.cpp > /boot/home/development/mdr/lib/numailkit.cpp > /boot/home/development/mdr/lib/status.cp > /boot/home/development/mdr/config/ConfigWindow.h > /boot/home/development/mdr/bemail/FindWindow.h > /boot/home/development/mdr/bemail/Header.cpp > /boot/home/development/mdr/bemail/LICENSE > /boot/home/development/mdr/bemail/Mail.cpp > /boot/home/development/mdr/bemail/Prefs.h > /boot/home/development/mdr/inbound_protocols/makefile > /boot/home/development/mdr/lib > /boot/home/development/mdr/bemail/Signature.h > /boot/home/development/mdr/bemail/BeMail.rsrc > /boot/home/development/mdr/bemail/Signature.cpp > /boot/home/development/mdr/bemail/QueryMenu.h > /boot/home/development/mdr/daemon/SlowMenu.h > /boot/home/development/mdr/AGMSBayesianSpamServer/BuyLogoLayers.image.x-becasso > /boot/home/development/mdr/bemail/Utilities.cpp > /boot/home/development/mdr/bemail/WIndex.cpp > /boot/home/development/mdr/bemail/Words.cpp > /boot/home/development/mdr/bemail/WIndex.h > /boot/home/development/mdr/bemail/Words.h > /boot/home/development/mdr/bemail/geekspeak > /boot/home/development/mdr/bemail/Utilities.h > /boot/home/development/mdr/config/E-mail.rsrc > /boot/home/development/mdr/daemon/NavMenu.h > /boot/home/development/mdr/bemail/BmapButton.h > /boot/home/development/mdr/daemon/main.cp > > And, just to confirm in one file: > > ~> listattr /boot/home/development/mdr/daemon/main.cp > File: /boot/home/development/mdr/daemon/main.cp > Type Size Name > ----------- --------- ------------------------------- > > 0 bytes total in attributes. > > I was working with those files before I checked the email so it looks a > lot like BFS getting confused about the inodes that it puts on the > indexes. New description: I have been doing experiments on a real Haiku installation and playing with emails I just noticed the indexes are not being correctly maintained. Here is what I mean: ~> query MAIL:subject=\* /boot/home/development/mdr/AGMSBayesianSpamServer/SoundUncertain /boot/home/development/mdr/outbound_filters /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpamServer\ Settings /boot/home/development/mdr/bemail/ObjectList.h /boot/home/development/mdr/bemail /boot/home/development/mdr/daemon/.cvsignore /boot/home/development/mdr/bemail/Enclosures.cpp /boot/home/development/mdr/lib/crypt.cpp /boot/home/development/spam_server/CVS/Entries /boot/home/development/mdr/config/ConfigWindow.cpp /boot/home/development/mdr/bemail/QueryMenu.cpp /boot/home/development/mdr/CVSROOT/verifymsg /boot/home/development/mdr/CVSROOT/modules /boot/home/development/mdr/inbound_protocols /boot/home/development/mdr/CVSROOT/notify /boot/home/development/mdr/bemail/Content.h /boot/home/development/mdr/bemail/Content.cpp /boot/home/development/mdr/lib/numailkit.cpp /boot/home/development/mdr/lib/status.cp /boot/home/development/mdr/config/ConfigWindow.h /boot/home/development/mdr/bemail/FindWindow.h /boot/home/development/mdr/bemail/Header.cpp /boot/home/development/mdr/bemail/LICENSE /boot/home/development/mdr/bemail/Mail.cpp /boot/home/development/mdr/bemail/Prefs.h /boot/home/development/mdr/inbound_protocols/makefile /boot/home/development/mdr/lib /boot/home/development/mdr/bemail/Signature.h /boot/home/development/mdr/bemail/BeMail.rsrc /boot/home/development/mdr/bemail/Signature.cpp /boot/home/development/mdr/bemail/QueryMenu.h /boot/home/development/mdr/daemon/SlowMenu.h /boot/home/development/mdr/AGMSBayesianSpamServer/BuyLogoLayers.image.x-becasso /boot/home/development/mdr/bemail/Utilities.cpp /boot/home/development/mdr/bemail/WIndex.cpp /boot/home/development/mdr/bemail/Words.cpp /boot/home/development/mdr/bemail/WIndex.h /boot/home/development/mdr/bemail/Words.h /boot/home/development/mdr/bemail/geekspeak /boot/home/development/mdr/bemail/Utilities.h /boot/home/development/mdr/config/E-mail.rsrc /boot/home/development/mdr/daemon/NavMenu.h /boot/home/development/mdr/bemail/BmapButton.h /boot/home/development/mdr/daemon/main.cp And, just to confirm in one file: ~> listattr /boot/home/development/mdr/daemon/main.cp File: /boot/home/development/mdr/daemon/main.cp Type Size Name ----------- --------- ------------------------------- 0 bytes total in attributes. I was working with those files before I checked the email so it looks a lot like BFS getting confused about the inodes that it puts on the indexes. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 16:35:58 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 14:35:58 -0000 Subject: [Haiku-bugs] [Haiku] #2616: parsedate() with an invalid time value seesm to create stack corruption. In-Reply-To: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> References: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> Message-ID: <047.77e7d740d76639a6523b5fa433ede2f7@haiku-os.org> #2616: parsedate() with an invalid time value seesm to create stack corruption. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => assigned * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 09:08:45 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 07:08:45 -0000 Subject: [Haiku-bugs] [Haiku] #2608: Changing date & time preferences in Tracker doesn't invalidate concerned views In-Reply-To: <041.6d6a802b1de9ca55b09616d51f9db5d1@haiku-os.org> References: <041.6d6a802b1de9ca55b09616d51f9db5d1@haiku-os.org> Message-ID: <050.bba378d50716aaabd671ec6482cba5e1@haiku-os.org> #2608: Changing date & time preferences in Tracker doesn't invalidate concerned views -----------------------------------+---------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: 1816 Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 1816 Comment: Duplicate of #1816. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 15:21:46 2008 From: trac at haiku-os.org (ekdahl) Date: Sat, 16 Aug 2008 13:21:46 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.11158b5e55cba69478a5379b7b341c92@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by ekdahl): I've now added a new patch that doesn't touch the files which were copyrighted to Marcus. This is hopefully the last version :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 10:12:22 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 08:12:22 -0000 Subject: [Haiku-bugs] [Haiku] #2523: Invalid Argument while trying to configure and/or make packages in Haiku In-Reply-To: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> References: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> Message-ID: <051.df7ea36f5f9f6236f2c252f9027fa2d0@haiku-os.org> #2523: Invalid Argument while trying to configure and/or make packages in Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Just reopen it if it occurs again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 13:22:26 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 11:22:26 -0000 Subject: [Haiku-bugs] [Haiku] #1391: [Tracker] don't show icons for volumes in mount menu (easy) In-Reply-To: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> References: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> Message-ID: <049.174ef1c91c8225c7df47900afe0a1c09@haiku-os.org> #1391: [Tracker] don't show icons for volumes in mount menu (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): The patch looks good - the problem of this code is just that we currently have no way for a device to get a new style icon, and no icon looks better than the wrong one, IMO. I'll see what I can do about changing this, and then we can apply this patch, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 16:04:25 2008 From: trac at haiku-os.org (bga) Date: Sun, 17 Aug 2008 14:04:25 -0000 Subject: [Haiku-bugs] [Haiku] #2621: Screen update problems. Message-ID: <038.e8d138314d5ea6a0bfdab5f0ffb9c512@haiku-os.org> #2621: Screen update problems. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- I am running Haiku with the VESA driver and I noticed that some windows fail to update in a timely fashion form time to time. One glaring example is the mail_daemon status window. When downloading emails, I see that emails are arriving but, sometime even for 2 or 3 seconds, the Window does not update and suddenly catches up. I know for a fact that it is receiving the update requests so I wonder if this is not related to double buffering? Another example is DriveSetup. If you expand or collapse one of the disks you will notice that it does not react immediately but, instead, sits there until some time passes or you click the window. At which point it does update. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 11:32:34 2008 From: trac at haiku-os.org (luroh) Date: Sun, 17 Aug 2008 09:32:34 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" Message-ID: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Boot process panics after the 4th boot splash icon has lit up, when trying to boot from a USB stick. Stack crawl attached. Interestingly enough, the problem doesn't trigger if I have my bootable Haiku IDE HDD attached while booting from the USB stick. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 14:13:36 2008 From: trac at haiku-os.org (Hubert) Date: Sun, 17 Aug 2008 12:13:36 -0000 Subject: [Haiku-bugs] [Haiku] #2619: SOB17 is not work In-Reply-To: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> References: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> Message-ID: <050.837e13c96ab323f97ec0eca0f24b7431@haiku-os.org> #2619: SOB17 is not work ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: x64 | Blocking: ---------------------------+------------------------------------------------ Comment(by Hubert): Seventeen Or Bust http://www.seventeenorbust.com/download/ version for R5 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 13:41:19 2008 From: trac at haiku-os.org (bga) Date: Sat, 16 Aug 2008 11:41:19 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. Message-ID: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> #2614: Indexes not being correctly maintained. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I have been doing experiments on a real Haiku installation and playing with emails I just noticed the indexes are not being correctly maintained. Here is what I mean: ~> query MAIL:subject=\* /boot/home/development/mdr/AGMSBayesianSpamServer/SoundUncertain /boot/home/development/mdr/outbound_filters /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpamServer\ Settings /boot/home/development/mdr/bemail/ObjectList.h /boot/home/development/mdr/bemail /boot/home/development/mdr/daemon/.cvsignore /boot/home/development/mdr/bemail/Enclosures.cpp /boot/home/development/mdr/lib/crypt.cpp /boot/home/development/spam_server/CVS/Entries /boot/home/development/mdr/config/ConfigWindow.cpp /boot/home/development/mdr/bemail/QueryMenu.cpp /boot/home/development/mdr/CVSROOT/verifymsg /boot/home/development/mdr/CVSROOT/modules /boot/home/development/mdr/inbound_protocols /boot/home/development/mdr/CVSROOT/notify /boot/home/development/mdr/bemail/Content.h /boot/home/development/mdr/bemail/Content.cpp /boot/home/development/mdr/lib/numailkit.cpp /boot/home/development/mdr/lib/status.cp /boot/home/development/mdr/config/ConfigWindow.h /boot/home/development/mdr/bemail/FindWindow.h /boot/home/development/mdr/bemail/Header.cpp /boot/home/development/mdr/bemail/LICENSE /boot/home/development/mdr/bemail/Mail.cpp /boot/home/development/mdr/bemail/Prefs.h /boot/home/development/mdr/inbound_protocols/makefile /boot/home/development/mdr/lib /boot/home/development/mdr/bemail/Signature.h /boot/home/development/mdr/bemail/BeMail.rsrc /boot/home/development/mdr/bemail/Signature.cpp /boot/home/development/mdr/bemail/QueryMenu.h /boot/home/development/mdr/daemon/SlowMenu.h /boot/home/development/mdr/AGMSBayesianSpamServer/BuyLogoLayers.image.x-becasso /boot/home/development/mdr/bemail/Utilities.cpp /boot/home/development/mdr/bemail/WIndex.cpp /boot/home/development/mdr/bemail/Words.cpp /boot/home/development/mdr/bemail/WIndex.h /boot/home/development/mdr/bemail/Words.h /boot/home/development/mdr/bemail/geekspeak /boot/home/development/mdr/bemail/Utilities.h /boot/home/development/mdr/config/E-mail.rsrc /boot/home/development/mdr/daemon/NavMenu.h /boot/home/development/mdr/bemail/BmapButton.h /boot/home/development/mdr/daemon/main.cp And, just to confirm in one file: ~> listattr /boot/home/development/mdr/daemon/main.cp File: /boot/home/development/mdr/daemon/main.cp Type Size Name ----------- --------- ------------------------------- 0 bytes total in attributes. I was working with those files before I checked the email so it looks a lot like BFS getting confused about the inodes that it puts on the indexes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 13:44:09 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 11:44:09 -0000 Subject: [Haiku-bugs] [Haiku] #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) In-Reply-To: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> References: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> Message-ID: <049.a2536a773d0872cddca2c1375be9d2e1@haiku-os.org> #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 22:27:07 2008 From: trac at haiku-os.org (kaliber) Date: Sat, 16 Aug 2008 20:27:07 -0000 Subject: [Haiku-bugs] [Haiku] #2617: seekdir and telldir not implemented Message-ID: <042.e342356d7a278e7db074f37a72463850@haiku-os.org> #2617: seekdir and telldir not implemented -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- seekdir and telldir is defined in posix/dirent.h, but isn't implemented. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 10:09:13 2008 From: trac at haiku-os.org (ekdahl) Date: Fri, 15 Aug 2008 08:09:13 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.dc98a2a9402598b3d69e35c7ddf5917e@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by ekdahl): Replying to [comment:3 ekdahl]: > > Should there be any indenting for preprocessor code? > > #ifndef NULL > #define NULL 0 > #endif > or > #ifndef NULL > # define NULL 0 > #endif > or > #ifndef NULL > #define NULL 0 > #endif > (but with tabs)? Hmm, seems all my newlines disappeared on the trac page, but it looks alright in the email at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 16:21:03 2008 From: trac at haiku-os.org (tqh) Date: Fri, 15 Aug 2008 14:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #2523: Invalid Argument while trying to configure and/or make packages in Haiku In-Reply-To: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> References: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> Message-ID: <051.66a9384d9a8733e2a2ae01d4a65d60ed@haiku-os.org> #2523: Invalid Argument while trying to configure and/or make packages in Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by tqh): * cc: fredrik.holmqvist at gmail.com (added) Comment: I need to check this on my machine, always when I've crashed in Haiku thru Firefox I've seen that Invalid Argument. I just assumed that was normal. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 01:14:56 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 23:14:56 -0000 Subject: [Haiku-bugs] [Haiku] #2613: Calling Minimize() in Window constructor does not work. Message-ID: <038.a1a7dd0860f90f5052cf4bd111637b17@haiku-os.org> #2613: Calling Minimize() in Window constructor does not work. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- If Minimize() is called in the Window constructor it will not work as expected. The Window will not be minimized (it will still show on screen) but IsMinimized() will return true. In BeOS R5, minimizing a Window on its constructor is a valid operation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 00:35:41 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 14 Aug 2008 22:35:41 -0000 Subject: [Haiku-bugs] [Haiku] #2605: PANIC: remove page 0x91d43ae8 from cache 0x976e5f78: page still has mappings! In-Reply-To: <042.0d362ba6cfe14179bd7ec16b42fc6f9c@haiku-os.org> References: <042.0d362ba6cfe14179bd7ec16b42fc6f9c@haiku-os.org> Message-ID: <051.08d181d6f35acb7208fdf26848436bf6@haiku-os.org> #2605: PANIC: remove page 0x91d43ae8 from cache 0x976e5f78: page still has mappings! ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Unfortunately you printed the wrong area. Somewhat inconsistently the parameter to "area" is not the address of the vm_area structure, but any address in the area. Or an area ID. It would also be interesting what's the parameters of the delete_area() call (particularly the area). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 21:32:21 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 16 Aug 2008 19:32:21 -0000 Subject: [Haiku-bugs] [Haiku] #1412: Haiku doesn't have the sys/ipc.h sys/sem.h and sys/mman.h files. In-Reply-To: <043.7a34c974ccd5686395f8a6ca893e2f3d@haiku-os.org> References: <043.7a34c974ccd5686395f8a6ca893e2f3d@haiku-os.org> Message-ID: <052.df84c0acf9e2a9674b7d92503d41d4bb@haiku-os.org> #1412: Haiku doesn't have the sys/ipc.h sys/sem.h and sys/mman.h files. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: emitrax Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by emitrax): sys/sem.h has been added along with ipc.h. Although the latest theorically would imply sys/shm.h and sys/msg, which are not yet implemented, I think this ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 17:00:59 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 15:00:59 -0000 Subject: [Haiku-bugs] [Haiku] #2559: [pthreads] Define PTHREAD_STACK_MIN In-Reply-To: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> References: <043.efbb9ab837a45c93d4cd9ec3ca6f96f2@haiku-os.org> Message-ID: <052.8bc5ecfa51bd43221d5368149b7be1b3@haiku-os.org> #2559: [pthreads] Define PTHREAD_STACK_MIN --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26982. If the value of PTHREAD_STACK_MIN is problematic, please yell :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 06:59:23 2008 From: trac at haiku-os.org (shinta) Date: Sat, 16 Aug 2008 04:59:23 -0000 Subject: [Haiku-bugs] [Haiku] #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect In-Reply-To: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> References: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> Message-ID: <050.5143cae0e903539d5222a6b4d69d6e57@haiku-os.org> #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by shinta): Above patch is another idea. LineHeight(0) calls _FindLineBreaks() eventually. I don't know whether removing check of fStyles->IsValidNullStyle() is OK or not. But, at leaset, it seems strange that ascent and descent aren't set when fStyles->IsValidNullStyle() is false. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 11:14:16 2008 From: trac at haiku-os.org (Hubert) Date: Sun, 17 Aug 2008 09:14:16 -0000 Subject: [Haiku-bugs] [Haiku] #2619: SOB17 is not work In-Reply-To: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> References: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> Message-ID: <050.ffcc2aaffe3cb1809e4ecc8842dee7f1@haiku-os.org> #2619: SOB17 is not work ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: x64 | Blocking: ---------------------------+------------------------------------------------ Comment(by Hubert): Ah, this is rev. 26999 and many earliest from last three months -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 02:30:24 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 15 Aug 2008 00:30:24 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.fae38c3dbfd607c1ed34b790ffb06d2a@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 19:01:42 2008 From: trac at haiku-os.org (andreasf) Date: Fri, 15 Aug 2008 17:01:42 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' does not work Message-ID: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> #2612: 'Save as' does not work -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- At r26941 The "Save as" menu items of StyledEdit and Pe do not work - the title bar displays the new file name but neither Tracker nor `ls` show the new file (i.e., it does not exist). If created via `touch` they are there right away and can be opened, modified and saved in both apps. I assume this bug is two-part - a) both applications do not recognize the error while saving (d?j?-vu... #2148), and b) the fault itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 15:39:41 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 13:39:41 -0000 Subject: [Haiku-bugs] [Haiku] #2609: /boot/beos/apps/* should have symlinks inside /boot/apps In-Reply-To: <038.e660129db0a4d6632a1aff15a275a06f@haiku-os.org> References: <038.e660129db0a4d6632a1aff15a275a06f@haiku-os.org> Message-ID: <047.bd18459767e76795753da34b8d87cd00@haiku-os.org> #2609: /boot/beos/apps/* should have symlinks inside /boot/apps -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by axeld): I don't know, using this path inside of applications isn't a good idea, as /boot/apps/ is user territory - ie. they can and will change it to their needs. Besides that, I don't see much point in providing those links, at least not just for compatibility. Isn't SpicyKeys completely configurable, anyway? What do others think about this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 23:06:59 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 21:06:59 -0000 Subject: [Haiku-bugs] [Haiku] #2607: Unable to check emails using MDR In-Reply-To: <039.083aec540b4a569021b25cbf3ffe5457@haiku-os.org> References: <039.083aec540b4a569021b25cbf3ffe5457@haiku-os.org> Message-ID: <048.dfcfad1a9bb3e30875d495be3894c852@haiku-os.org> #2607: Unable to check emails using MDR ----------------------------+----------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Mail Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: Fixed on r26984. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 17:05:08 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 15:05:08 -0000 Subject: [Haiku-bugs] [Haiku] #2609: /boot/beos/apps/* should have symlinks inside /boot/apps In-Reply-To: <038.e660129db0a4d6632a1aff15a275a06f@haiku-os.org> References: <038.e660129db0a4d6632a1aff15a275a06f@haiku-os.org> Message-ID: <047.ed6243eede764f15c482e0095b040f0c@haiku-os.org> #2609: /boot/beos/apps/* should have symlinks inside /boot/apps -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by bga): I am not arguing it is a good idea, I am just pointing out that Be decided bootapps would hold all applications. The ones shipped with BeOS wpuld be symlinked there and the user could also install other applications. This looks like a nice approach to me as the user just need to go to one single place to find his applications (unless he/she intentionally deletes links from there or install things in other places, of course). SpicyKeys was just an example as it comes pre-configured with those paths. There could be other applications that rely on this behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 14 21:34:51 2008 From: trac at haiku-os.org (koki) Date: Thu, 14 Aug 2008 19:34:51 -0000 Subject: [Haiku-bugs] [Haiku] #2607: Unable to check emails using MDR Message-ID: <039.083aec540b4a569021b25cbf3ffe5457@haiku-os.org> #2607: Unable to check emails using MDR ---------------------------+------------------------------------------------ Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Mail Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Running r26970, trying to check mail using MDR gives the following error message... ***** demo at myhaiku.org: Error while getting a message: Name not found ***** ...and no messages are retrieved from the server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 16:33:54 2008 From: trac at haiku-os.org (luroh) Date: Sun, 17 Aug 2008 14:33:54 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" In-Reply-To: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> References: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> Message-ID: <049.136a468d741707e8a80f36cbcb6352ee@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by luroh): Thank you for the instructions. There were about 15 pages of debug output of which I have attached the latter half. I believe the USB stick itself is OK, it's a USB 2.0 1GB stick onto which I copy a 200MB image, containing nothing extra but Firefox, using the command: sudo dd if=./generated/haiku.image of=/dev/sdb The same stick can boot another computer (my laptop) without any problems. The problematic computer above is a desktop machine with an Asus A8V-E Deluxe motherboard (based on the VIA K8T890 chipset). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 10:05:12 2008 From: trac at haiku-os.org (ekdahl) Date: Fri, 15 Aug 2008 08:05:12 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.43adc58e87185e9bc483c612733f17e8@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by ekdahl): Replying to [comment:2 axeld]: > Thanks for your work! There is just a minor problem; while our coding style guide mentions "Public headers should always be copyrighted to "Haiku Inc." and don't list any authors.", this does not mean that you can deliberately change such headers. > Especially "Copyright Marcus Overhagen" is not the same as "Copyright Haiku, Authors Marcus Overhagen". > > Maybe you can just ask him if he is okay to be removed from that header (and such make it look like the others). If not, I would at least volunteer to rewrite the null.h header :-)) Ok, so here's a new version with a rewritten null.h header then. But its hard to rewrite a such small header without getting a strong resemblance to the old one :) BTW, some coding style questions struck me: Whats the preferred header guard style, _NULL_H_, _NULL_H or NULL_H? I've seen all variants but no mention in the guidelines. Should there be any indenting for preprocessor code? #ifndef NULL #define NULL 0 #endif or #ifndef NULL # define NULL 0 #endif or #ifndef NULL #define NULL 0 #endif (but with tabs)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 14:42:51 2008 From: trac at haiku-os.org (denisw) Date: Sat, 16 Aug 2008 12:42:51 -0000 Subject: [Haiku-bugs] [Haiku] #2615: Improved keyboard navigation with triggers Message-ID: <041.bfa285969fbe4acaf329c06c203e20ca@haiku-os.org> #2615: Improved keyboard navigation with triggers -------------------------+-------------------------------------------------- Reporter: denisw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- While many Haiku apps use shortcuts for several menu items, I realized that there is no functionality to quickly navigate through Haiku UIs with the keyboard. Many toolkits in other OS's have "mnemonics" for this purpose, which are displayed as underlined letters in menu or button labels. Pressing this letter key (in combination with a certain modifier) focuses and activates the control. For instance, if you have a "Cancel" button with an underlined "C", you can press e.g. Ctrl+C to activate the button. Looking into the Be Book, BMenuItem has a SetTrigger() method which seems to be just like that (except that you don't have to press a modifier, which makes sense because the menu is already focused). It would be nice if this feature could be useable in more controls though, such as buttons, tabs, and the menus of a menu bar. My proposal is # the addition of a SetUseTrigger(bool useTrigger) method to BControl. If true is passed (the default might have to be false for compatibility reasons), the first character of the control's label with a leading "_" will be made the trigger character of that control and underlined in appearance (the "_" itself will not be shown). The advantage of this API in comparison to BMenuItem's current SetTrigger() is easier translation (when support for translation is added later on): as the trigger key will likely be different from language to language, it is easier to have the string and the trigger in one string instead of being spread in a string and a separate character. I hope this would be a valid API addition for R1. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 23:45:34 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 Aug 2008 21:45:34 -0000 Subject: [Haiku-bugs] [Haiku] #2598: sshd occasionally segfaults on connect (possibly when forking) In-Reply-To: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> References: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> Message-ID: <053.b6f940013ebd677df55b83cabf03ed04@haiku-os.org> #2598: sshd occasionally segfaults on connect (possibly when forking) ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Hi Ingo, I tried this test again but using sshd -ddd, and got slightly different but still interesting behavior. This time it didn't actually segfault, but sshd did somehow completely exit after I logged out the session: last few lines of debugging output from sshd: {{{ debug2: channel 0: rcvd adjust 32778 debug1: server_input_channel_req: channel 0 request window-change reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req window-change debug1: server_input_channel_req: channel 0 request window-change reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req window-change debug1: Received SIGCHLD. debug1: session_by_pid: pid 231 debug1: session_exit_message: session 0 channel 0 pid 231 debug2: channel 0: request exit-status confirm 0 debug1: session_exit_message: release channel 0 debug2: channel 0: write failed debug2: channel 0: close_write debug2: channel 0: output open -> closed debug1: session_pty_cleanup: session 0 release /dev/tt/p1 debug2: channel 0: read<=0 rfd 7 len 0 debug2: channel 0: read failed debug2: channel 0: close_read debug2: channel 0: input open -> drain debug2: channel 0: ibuf empty debug2: channel 0: send eof debug2: channel 0: input drain -> closed debug2: channel 0: send close debug2: notify_done: reading debug3: channel 0: will not send data after close debug2: channel 0: rcvd close debug3: channel 0: will not send data after close debug2: channel 0: is dead debug2: channel 0: gc: notify user debug1: session_by_channel: session 0 channel 0 debug1: session_close_by_channel: channel 0 child 0 debug1: session_close: session 0 pid 0 debug2: channel 0: gc: user detached debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: server-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 server-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1) debug3: channel 0: close_fds r -1 w -1 e -1 c -1 Connection closed by 192.168.1.126 debug1: do_cleanup Closing connection to 192.168.1.126 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 13:48:39 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 11:48:39 -0000 Subject: [Haiku-bugs] [Haiku] #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) In-Reply-To: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> References: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> Message-ID: <049.7291bc644f08ebc4e70478b0510933ce@haiku-os.org> #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Thanks, I've applied your patch in r26978. I just made a few changes: use B_RGBA32 for icons instead of B_CMAP8, and honour the 80 column line limit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 01:52:27 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 14 Aug 2008 23:52:27 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal as replicant doesn't respect settings In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.f805619ce0b5e6f4910aa08aa58a456e@haiku-os.org> #2215: Terminal as replicant doesn't respect settings ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): Seeing as the replicant feature has been removed from terminal, this ticket can also be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 10:57:53 2008 From: trac at haiku-os.org (Hubert) Date: Sun, 17 Aug 2008 08:57:53 -0000 Subject: [Haiku-bugs] [Haiku] #2619: SOB17 is not work Message-ID: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> #2619: SOB17 is not work --------------------------+------------------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x64 Blocking: | --------------------------+------------------------------------------------- SB17 is doesn't run from certain time, despite, that it run on Haiku image from February / March -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 17:55:11 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 15 Aug 2008 15:55:11 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.4af822415921e126550926b74162ebb8@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by mmlr): Do you have any debug output from that? Does it work to unplug and replug the mouse? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 09:18:10 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 07:18:10 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.0e1b96ca09f51de5f0e7e94193d7375f@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): Thanks for your work! There is just a minor problem; while our coding style guide mentions "Public headers should always be copyrighted to "Haiku Inc." and don't list any authors.", this does not mean that you can deliberately change such headers. Especially "Copyright Marcus Overhagen" is not the same as "Copyright Haiku, Authors Marcus Overhagen". Maybe you can just ask him if he is okay to be removed from that header (and such make it look like the others). If not, I would at least volunteer to rewrite the null.h header :-)) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 11:17:52 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 09:17:52 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.2731edeae759831af32c0e5d42756563@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): It wasn't just null.h, though. You can use \{\{\{/\}\}\} to have correct newlines :-) In any case, I usually do it this way, and that's also what you'll find in 95% our sources: {{{ #ifndef NULL # define NULL 0 #endif }}} The header guards follow at least one rule: local/(very) private headers use NAME_H, public or shared system headers use at least _NAME_H (as the underscore is generally a reserved namespace for the operating system, not just Haiku). If it's _NAME_H_ or _NAME_H I don't really care, I would just follow what the majority of the other POSIX headers does. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 16 20:23:37 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 16 Aug 2008 18:23:37 -0000 Subject: [Haiku-bugs] [Haiku] #2615: Improved keyboard navigation with triggers In-Reply-To: <041.bfa285969fbe4acaf329c06c203e20ca@haiku-os.org> References: <041.bfa285969fbe4acaf329c06c203e20ca@haiku-os.org> Message-ID: <050.af962fd1e0fe97a67dba51cb004a3130@haiku-os.org> #2615: Improved keyboard navigation with triggers ---------------------------------+------------------------------------------ Reporter: denisw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * component: - General => Kits/Interface Kit Comment: Switching components. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 12:43:19 2008 From: trac at haiku-os.org (korli) Date: Sun, 17 Aug 2008 10:43:19 -0000 Subject: [Haiku-bugs] [Haiku] #2616: parsedate() with an invalid time value seesm to create stack corruption. In-Reply-To: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> References: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> Message-ID: <047.2f216f70fff05692ed74b9b299e03300@haiku-os.org> #2616: parsedate() with an invalid time value seesm to create stack corruption. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by korli): You might want to add your testcase in src/tests/system/libroot/os/ParseDateTest.cpp. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 13:59:33 2008 From: trac at haiku-os.org (axeld) Date: Fri, 15 Aug 2008 11:59:33 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.c2191a42daef680aa227037023b50175@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): I think while it's legally more correct, I also think that this can be pretty much neglected in practice. Having the first and the last year is at least the most interesting part of it, else we could probably also only mention the current year - earlier versions will carry the earlier copyright, and the document as is is clearly not copyrighted in a previous year. So much for the logic, but I'm not a lawyer :-) I would suggest we just keep the current practice of mentioning the first and the last year of changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 15:33:30 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 13:33:30 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. Message-ID: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> #2610: USB mouse dies when input_server is restarted. ----------------------------------+----------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Restarting the input_server results in my USB mouse not coming back to life. Maybe it is not being correctly reset? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 15 20:36:19 2008 From: trac at haiku-os.org (bga) Date: Fri, 15 Aug 2008 18:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.762e49f7fdad082dad63a56219921a35@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bga): Tried another time. This time without a crash. Nothing relevant on syslog (except for the message that the keyboard was found. Nothing about mouse). Unplugging the mouse and plugging it again makes it start working. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 17:09:59 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 17 Aug 2008 15:09:59 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' does not work In-Reply-To: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> References: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> Message-ID: <052.a90fa0e3b27b39360f238f82d7dc1915@haiku-os.org> #2612: 'Save as' does not work --------------------------------------+------------------------------------- Reporter: andreasf | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/StyledEdit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by andreasf): At r26991 I have not yet encountered this in StyledEdit again (without pending changes). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 14:43:02 2008 From: trac at haiku-os.org (mmlr) Date: Sun, 17 Aug 2008 12:43:02 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" In-Reply-To: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> References: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> Message-ID: <049.a92ce54ccbf6e07d2f624932747e97a9@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): A stack trace in that case is not very helpful, as it is not where the problem happens. What is interesting instead is the debug output from boot either through serial debugging or per screenshots of on-screen debug output. What size is that USB stick and are you sure the whole image actually did fit on it? Bug #2602 documents the issue where a image didn't actually fit on the device. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 14:44:54 2008 From: trac at haiku-os.org (mmlr) Date: Sun, 17 Aug 2008 12:44:54 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" In-Reply-To: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> References: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> Message-ID: <049.7bbd6a8c5217a99591348131df05f3c5@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Scratch that, in fact it's bug #2587 that documents the non-fitting image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 15:39:08 2008 From: trac at haiku-os.org (bga) Date: Sun, 17 Aug 2008 13:39:08 -0000 Subject: [Haiku-bugs] [Haiku] #2616: parsedate() with an invalid time value seesm to create stack corruption. In-Reply-To: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> References: <038.7cf4ac4dbcf65f2b553a08ade788a469@haiku-os.org> Message-ID: <047.fe566951674bf814db8258a1c0d4daf7@haiku-os.org> #2616: parsedate() with an invalid time value seesm to create stack corruption. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by bga): Added the test case with r27003. Again, gdb is useless to debug this due to the stack corruption. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 17:42:57 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 15:42:57 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.f8fbb848f525552ea39e19a02dd22df6@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): libpng 1.2.30 has now been released. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 18:17:32 2008 From: trac at haiku-os.org (Coldfirex) Date: Sun, 17 Aug 2008 16:17:32 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.6ce95706ec61bcc96e1bb08c32219575@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by Coldfirex): Unable to reproduce in r26984 under vmware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 18:46:37 2008 From: trac at haiku-os.org (luroh) Date: Sun, 17 Aug 2008 16:46:37 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.4624b60c8213d5e4d0fc30e2af489805@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by luroh): I can reproduce it in Vmware, r27006. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 18:50:44 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 17 Aug 2008 16:50:44 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.f655d185d1080258072aabe09636c399@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * component: - General => Applications/Tracker Comment: That one might actually be an original Tracker bug, I think I remember that one being there in BeOS 5 too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 18:57:43 2008 From: trac at haiku-os.org (umccullough) Date: Sun, 17 Aug 2008 16:57:43 -0000 Subject: [Haiku-bugs] [Haiku] #2619: SOB17 is not work In-Reply-To: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> References: <041.bfd32157392a4bddb5511c86bb14ec98@haiku-os.org> Message-ID: <050.7b96cd347d0c14cfce46fe42bb3188d0@haiku-os.org> #2619: SOB17 is not work ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: x64 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): Last time I ran SB17 on Haiku was over 2 years ago on a PIII and it ran fine (albeit slower than expected). http://flickr.com/photos/umccullough/130597452/sizes/o/ and http://flickr.com/photos/umccullough/130597453/sizes/o/ Unfortunately SB17 is closed source and the version available for BeOS is actually older and doesn't support some newer processors properly. Newer versions required proper pthread support, and so they had dropped the BeOS port entirely. I recently tried to establish interest in an updated Haiku port, but their developers are pretty busy and not terribly interested it seems: http://www.free-dc.org/forum/showthread.php?t=13777 I will test it on a P4 2.8ghz here shortly and report my findings as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:28:17 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 17:28:17 -0000 Subject: [Haiku-bugs] [Haiku] #2622: [StyledEdit] moves focus back to home if you change window size Message-ID: <042.41ea4a36dec75fae5b7e2ca319def522@haiku-os.org> #2622: [StyledEdit] moves focus back to home if you change window size -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- In StyledEdit if you change the size of the window, the focus of your work is moved to the top of the document. You can get it back by moving the cursor key, as long as you had placed it where you were. Expected behavior is that when you resize the window, the current view is preserved. Very annoying if you were looking at line 22000. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:30:58 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 17:30:58 -0000 Subject: [Haiku-bugs] [Haiku] #2623: [StyledEdit] Add current line number display Message-ID: <042.ae98f5c56db92b908bae72f2391fdbbd@haiku-os.org> #2623: [StyledEdit] Add current line number display -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- It would be nice if StyledEdit showed the current line number, like Pe does, in the lower left hand side. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:34:37 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 17:34:37 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.6ef978a14c58edca3270ee31fd45331a@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): If a GUI server crashes, the console mode is used as a fallback (because if the input_server is missing, it can't be used for keyboard input, obviously). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:35:48 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 17:35:48 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.d95757fe59569b72644e5c3033a589c2@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): BTW, please use \{{{ and \}}} for preformatted text, that's a lot better to read :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:38:46 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 17:38:46 -0000 Subject: [Haiku-bugs] [Haiku] #1412: Haiku doesn't have the sys/ipc.h sys/sem.h and sys/mman.h files. In-Reply-To: <043.7a34c974ccd5686395f8a6ca893e2f3d@haiku-os.org> References: <043.7a34c974ccd5686395f8a6ca893e2f3d@haiku-os.org> Message-ID: <052.f349a52b67260872a4b4111f5b126881@haiku-os.org> #1412: Haiku doesn't have the sys/ipc.h sys/sem.h and sys/mman.h files. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: emitrax Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 19:55:36 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 17:55:36 -0000 Subject: [Haiku-bugs] [Haiku] #2622: [StyledEdit] moves focus back to home if you change window size In-Reply-To: <042.41ea4a36dec75fae5b7e2ca319def522@haiku-os.org> References: <042.41ea4a36dec75fae5b7e2ca319def522@haiku-os.org> Message-ID: <051.2a64353476a1a853f4fec4c7336d4df9@haiku-os.org> #2622: [StyledEdit] moves focus back to home if you change window size --------------------------------------+------------------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * type: enhancement => bug -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 20:04:01 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 18:04:01 -0000 Subject: [Haiku-bugs] [Haiku] #2514: Enlarged Terminal wraps input line overwriting beginning In-Reply-To: <041.0709cde09fcc236684912295319f2232@haiku-os.org> References: <041.0709cde09fcc236684912295319f2232@haiku-os.org> Message-ID: <050.dccd26adda51f0ef0b0edb84733d2e2f@haiku-os.org> #2514: Enlarged Terminal wraps input line overwriting beginning ------------------------+--------------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): This can also be seen if you type really long commands and then recall them later by using the cursor up/down keys. See attached screenshot. Note that the command should read: {{{ ./configure --prefix=/boot/common LDFLAGS=-L/boot/common/lib CPPFLAGS=-I/boot/common/include }}} as is actually executed as it should be, just that it's being displayed wrong. This is on r26990. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 20:07:46 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 18:07:46 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.5ebdd17049bb9ae7de8a9355e61bcd20@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r27001. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 21:23:11 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 19:23:11 -0000 Subject: [Haiku-bugs] [Haiku] #2624: Screen Saver doesn't work Message-ID: <040.13d4ed2cadfb6c9cb4514e6071cdd6ee@haiku-os.org> #2624: Screen Saver doesn't work -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Screen Savers (none of them) don't work (neither using the test button) nor in real life. This happens on r27010 (hybrid build (gcc2 with gcc4 libs)), but was already present before. The system uses the intel_extreme driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 21:29:42 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 19:29:42 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work Message-ID: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> #2625: ZipOMatic doesn't work -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- ZipOMatic doesn't work, when invoked via context menu. This happen on r27010. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 21:47:54 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 19:47:54 -0000 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work Message-ID: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> #2626: p4 (perforce client) doesn't work -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- p4 (perforce client) build for BeOS R5 doesn't work. Fails with the following message: rossi at wayreth home> p4 runtime_loader: elf_resolve_symbol: could not resolve symbol '_kunlock_node_' resolve symbol "_kunlock_node_" returned: -2147478780 runtime_loader: troubles relocating: 0x80001304 (image: p4) rossi at wayreth home> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 21:52:36 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 17 Aug 2008 19:52:36 -0000 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> Message-ID: <049.0da9f08cd427cd8688e9ed3771fa6707@haiku-os.org> #2626: p4 (perforce client) doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): Looks like p4 is using an undocumented syscall... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 21:56:02 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 19:56:02 -0000 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> Message-ID: <049.9591815981e72ebdc232e947b013211c@haiku-os.org> #2626: p4 (perforce client) doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Btw, the client is still available using the archived releases on the Perforce site: http://www.perforce.com/perforce/downloads/otherlist.html#beos5x86 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:04:25 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 20:04:25 -0000 Subject: [Haiku-bugs] [Haiku] #2627: Mail-It doesn't work (undefined symbol) Message-ID: <040.bae413d733044da6b598f792d366dd76@haiku-os.org> #2627: Mail-It doesn't work (undefined symbol) -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Mail-It 3.0 (BeOS R5) doesn't work. Undefined symbol: rossi at wayreth home> /boot/apps/BeatWare/Mail-It/Mail-It runtime_loader: elf_resolve_symbol: could not resolve symbol 'DS_EventReceived__16BWDataSubscriberUl' resolve symbol "DS_EventReceived__16BWDataSubscriberUl" returned: -2147478780 runtime_loader: troubles relocating: 0x80001304 (image: libfreestyle.so) rossi at wayreth home> libfreestyle.so is correctly installed in home/config/libs Package has been installed using the PackageInstaller -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:14:54 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 20:14:54 -0000 Subject: [Haiku-bugs] [Haiku] #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility Message-ID: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- TIFF translator doesn't handle files created by MacOS screenshot utility. Sample file attached. Happens or r27010. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:18:58 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 20:18:58 -0000 Subject: [Haiku-bugs] [Haiku] #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility In-Reply-To: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> References: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> Message-ID: <049.e394dba2b12e00e1e5aa521a78430bbe@haiku-os.org> #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Sample file available upon request rossi webpositive.org, couldn't attach the sample to this ticket, due to file size limitations. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:24:21 2008 From: trac at haiku-os.org (luroh) Date: Sun, 17 Aug 2008 20:24:21 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> Message-ID: <049.a42681903cb25186d7bf3c98c7738751@haiku-os.org> #2625: ZipOMatic doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by luroh): Works here in Vmware with r27010, any particular steps to reproduce? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:30:48 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 20:30:48 -0000 Subject: [Haiku-bugs] [Haiku] #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility In-Reply-To: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> References: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> Message-ID: <049.8804a118680bb253d2d94a2172b4c148@haiku-os.org> #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility ----------------------------------+----------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by axeld): * component: - General => Add-Ons/Translators Comment: Not even zipped? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:32:23 2008 From: trac at haiku-os.org (bga) Date: Sun, 17 Aug 2008 20:32:23 -0000 Subject: [Haiku-bugs] [Haiku] #2629: Automatic disk mounting not working. Message-ID: <038.a69687c7fc33e3e0b9d21ea4fc8dfaba@haiku-os.org> #2629: Automatic disk mounting not working. ----------------------------------+----------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- CDs are not being auto-mounted by Tracker even when Automatic Disk Mounting is set to all disks. Tried with a BFS cd, a ISO9660 CD and an Audio CD (cdda-fs). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:35:30 2008 From: trac at haiku-os.org (axeld) Date: Sun, 17 Aug 2008 20:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> Message-ID: <049.95daf90a88921dead2be3b582fe56554@haiku-os.org> #2626: p4 (perforce client) doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Should be fixed by r27011. -- Ticket URL: Haiku The Haiku operating system. From rossi at webpositive.org Sun Aug 17 22:33:16 2008 From: rossi at webpositive.org (Marcus Jacob) Date: Sun, 17 Aug 2008 22:33:16 +0200 Subject: [Haiku-bugs] [Haiku] #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility In-Reply-To: <049.8804a118680bb253d2d94a2172b4c148@haiku-os.org> References: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> <049.8804a118680bb253d2d94a2172b4c148@haiku-os.org> Message-ID: Nope, its a 2Mb file ;-( even zipped. Rossi -- Marcus Jacob eMail:m.jacob at mac.com iChat:m.jacob at mac.com Sent from my iPhone On 17.08.2008, at 22:30, "axeld" wrote: > #2628: TIFF translator doesn't handle TIFF files created by MacOS > screenshot > utility > ---------------------------------- > +----------------------------------------- > Reporter: rossi | Owner: axeld > Type: bug | Status: new > Priority: normal | Milestone: R1 > Component: Add-Ons/Translators | Version: R1 development > Resolution: | Blockedby: > Platform: All | Blocking: > ---------------------------------- > +----------------------------------------- > Changes (by axeld): > > * component: - General => Add-Ons/Translators > > > Comment: > > Not even zipped? > > -- > Ticket URL: > Haiku > The Haiku operating system. > _______________________________________________ > Haiku-bugs mailing list > Haiku-bugs at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/haiku-bugs From trac at haiku-os.org Sun Aug 17 22:42:49 2008 From: trac at haiku-os.org (bga) Date: Sun, 17 Aug 2008 20:42:49 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.b832110e9bdd5dc930608275e91c857b@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by bga): * status: closed => reopened * resolution: fixed => Comment: Actually, it is not. Just tried with an Audio CD and although the Mount menu now shows the CD icon, the icon in the Desktop is still the cabinet one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 22:47:12 2008 From: trac at haiku-os.org (bga) Date: Sun, 17 Aug 2008 20:47:12 -0000 Subject: [Haiku-bugs] [Haiku] #2630: Eject when unmounting not working. Message-ID: <038.60f769d53494f12643b23e42342745a0@haiku-os.org> #2630: Eject when unmounting not working. ----------------------------------+----------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- When a CD is unmounted it does not eject even when eject when unmounting is enabled in the Mount settings. -- Ticket URL: Haiku The Haiku operating system. From rossi at webpositive.org Sun Aug 17 23:03:53 2008 From: rossi at webpositive.org (Marcus Jacob) Date: Sun, 17 Aug 2008 23:03:53 +0200 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <049.95daf90a88921dead2be3b582fe56554@haiku-os.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> <049.95daf90a88921dead2be3b582fe56554@haiku-os.org> Message-ID: <0AFB2449-AD5C-4755-97FB-8B535109C556@webpositive.org> Yupp ;-) Thanks, Rossi -- Marcus Jacob eMail:m.jacob at mac.com iChat:m.jacob at mac.com Sent from my iPhone On 17.08.2008, at 22:35, "axeld" wrote: > #2626: p4 (perforce client) doesn't work > ------------------------ > +--------------------------------------------------- > Reporter: rossi | Owner: axeld > Type: bug | Status: closed > Priority: normal | Milestone: R1 > Component: - General | Version: R1 development > Resolution: fixed | Blockedby: > Platform: All | Blocking: > ------------------------ > +--------------------------------------------------- > Changes (by axeld): > > * status: new => closed > * resolution: => fixed > > > Comment: > > Should be fixed by r27011. > > -- > Ticket URL: > Haiku > The Haiku operating system. From rossi at webpositive.org Sun Aug 17 23:05:00 2008 From: rossi at webpositive.org (Marcus Jacob) Date: Sun, 17 Aug 2008 23:05:00 +0200 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> <049.a42681903cb25186d7bf3c98c7738751@haiku-os.org> Message-ID: <6B14CD77-248D-40A9-AB53-140B58C714D4@webpositive.org> > On 17.08.2008, at 22:24, "luroh" wrote: > >> #2625: ZipOMatic doesn't work >> ------------------------ >> +--------------------------------------------------- >> Reporter: rossi | Owner: axeld >> Type: bug | Status: new >> Priority: normal | Milestone: R1 >> Component: - General | Version: R1 development >> Resolution: | Blockedby: >> Platform: x86 | Blocking: >> ------------------------ >> +--------------------------------------------------- >> >> Comment(by luroh): >> >> Works here in Vmware with r27010, any particular steps to reproduce? > > Strange. I tried to invoke ZipOMatic from the Tracker context menu > with a single file, multiple files and a directory selected. All > basically gave the same none result, Nothing happened. > > This is on a hybrid build, gcc2 with gcc4 libs installed. > > But it also happened before on a non hybrid gcc2 build. Actually it > never worked on my system. > > Rossi > >> >> >> -- >> Ticket URL: >> Haiku >> The Haiku operating system. From umccullough at gmail.com Sun Aug 17 23:08:52 2008 From: umccullough at gmail.com (Urias McCullough) Date: Sun, 17 Aug 2008 14:08:52 -0700 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <0AFB2449-AD5C-4755-97FB-8B535109C556@webpositive.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> <049.95daf90a88921dead2be3b582fe56554@haiku-os.org> <0AFB2449-AD5C-4755-97FB-8B535109C556@webpositive.org> Message-ID: <1e80d8750808171408p13eae535h927bdf72c986b9a3@mail.gmail.com> 2008/8/17 Marcus Jacob : > Yupp ;-) > > Thanks, > Rossi I think it's generally a bad idea to respond via the bugs mailing list - you should be adding comments to the trac tickets. From trac at haiku-os.org Sun Aug 17 23:13:42 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 21:13:42 -0000 Subject: [Haiku-bugs] [Haiku] #2626: p4 (perforce client) doesn't work In-Reply-To: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> References: <040.e331d94fd03fdfba95553d8b4fb58721@haiku-os.org> Message-ID: <049.66072289f0851c91d5d670c68abfaaa6@haiku-os.org> #2626: p4 (perforce client) doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Yupp ;-) works now ... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 23:15:19 2008 From: trac at haiku-os.org (mmlr) Date: Sun, 17 Aug 2008 21:15:19 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" In-Reply-To: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> References: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> Message-ID: <049.0198bae1bcabfab4b50202ac8eb7bb3f@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 5 Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 5 Comment: The cause can be seen in the first screenshot at the top. Both the UHCI and EHCI controllers present have invalid IRQ assignments, which means that the BIOS didn't initialize interrupt routing for them. That means, this is in fact a duplicate of bug #5. If it works when you have a IDE disk connected this probably causes the BIOS to do some additional setup that it doesn't do when that's not the case. Maybe there are some USB legacy settings in the BIOS that you can try changing, otherwise there's not much you can currently do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 23:17:15 2008 From: trac at haiku-os.org (rossi) Date: Sun, 17 Aug 2008 21:17:15 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> Message-ID: <049.9b2cd238ef407f71c82e974ea96d03d4@haiku-os.org> #2625: ZipOMatic doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): I just invoked the Tracker add-on using the context menu. tried it on an individual files, multiple files and a single directory. No success with an of these nothing happens at all ... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 23:38:40 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 17 Aug 2008 21:38:40 -0000 Subject: [Haiku-bugs] [Haiku] #2631: Panic during boot with file_cache debug on Message-ID: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> #2631: Panic during boot with file_cache debug on -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Beside slowing down drastically the boot time, having file cache debug on, causes the following panic. {{{ lookup page from offset 282624: 0x91cf8ea8, size = 12, pageOffset = 248 file_cache_read(ref = 0x90c4e500, offset = 286066, buffer = 0x18106120, size = 151) cache_io(ref = 0x90c4e500, offset = 286066, buffer = 0x18106120, size = 151, read) lookup page from offset 282624: 0x91cf8ea8, size = 151, pageOffset = 3442 cache_io(ref = 0x90bfa2d0, offset = 79434, buffer = 0x7003be80, size = 79, write) lookup page from offset 77824: 0x91cfa088, size = 79, pageOffset = 1610 file_cache_write(ref = 0x90bfa2d0, offset = 79434, buffer = 0x7003be80, size = 79) = 0 PANIC: page fault, but interrupts were disabled. Touching address 0xccccccfc from eip 0x80038b0b Welcome to Kernel Debugging Land... Thread 146 "w>Deskbar" running on CPU 0 kdebug> bt stack trace for thread 146 "w>Deskbar" kernel stack: 0x91fd6000 to 0x91fda000 user stack: 0x700c3000 to 0x70103000 frame caller :function + offset 0 91fd9880 (+ 48) 8005598d :invoke_debugger_command + 0x00f5 1 91fd98b0 (+ 64) 8005577d :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 91fd98f0 (+ 64) 80055b05 :invoke_debugger_command_pipe + 0x009d 3 91fd9930 (+ 48) 800569e0 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 91fd9960 (+ 48) 80056396 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 91fd9990 (+ 224) 80057dac :evaluate_debug_command + 0x0088 6 91fd9a70 (+ 64) 80053dca :kernel_debugger_loop__Fv + 0x01ae 7 91fd9ab0 (+ 48) 80054993 :kernel_debugger + 0x0117 8 91fd9ae0 (+ 192) 80054871 :panic + 0x0029 9 91fd9ba0 (+ 48) 800b7950 :page_fault_exception + 0x0078 10 91fd9bd0 (+ 12) 800baf46 :int_bottom + 0x0036 (nearest) kernel iframe at 0x91fd9bdc (end = 0x91fd9c2c) eax 0x80038b04 ebx 0xcccccc00 ecx 0x800f969c edx 0x20 esi 0xccccccf4 edi 0x1fc ebp 0x91fd9c54 esp 0x91fd9c10 eip 0x80038b0b eflags 0x10082 vector: 0xe, error code: 0x0 11 91fd9bdc (+ 120) 80038b0b :_mutex_lock + 0x0067 12 91fd9c54 (+ 48) 800a2a0b :object_cache_get_usage + 0x0027 13 91fd9c84 (+ 64) 8002c2fa :block_cache_used_memory + 0x007e 14 91fd9cc4 (+ 32) 800b3f83 :vm_page_get_stats + 0x002f 15 91fd9ce4 (+ 48) 8004509f :_get_system_info + 0x0073 16 91fd9d14 (+ 560) 800451cf :_user_get_system_info + 0x0027 17 91fd9f44 (+ 100) 800bb172 :pre_syscall_debug_done + 0x0002 (nearest) user iframe at 0x91fd9fa8 (end = 0x91fda000) eax 0xce ebx 0x725d40 ecx 0x70102190 edx 0xffff0104 esi 0x1800ec90 edi 0x1804ee20 ebp 0x701021bc esp 0x91fd9fdc eip 0xffff0104 eflags 0x207 user esp 0x70102190 vector: 0x63, error code: 0x0 18 91fd9fa8 (+ 0) ffff0104 19 701021bc (+ 640) 008eaca8 <_APP_>:Update__17ProcessController + 0x002c 20 7010243c (+2208) 008e9309 <_APP_>:MessageReceived__17ProcessControllerP8BMessage + 0x00b9 21 70102cdc (+ 48) 002f9377 :DispatchMessage__7BLooperP8BMessageP8BHandler + 0x005b 22 70102d0c (+ 480) 003a069d :DispatchMessage__7BWindowP8BMessageP8BHandler + 0x174d 23 70102eec (+ 48) 002221e8 <_APP_>:DispatchMessage__10TBarWindowP8BMessageP8BHandler + 0x0054 24 70102f1c (+ 96) 003a3e60 :task_looper__7BWindow + 0x0270 25 70102f7c (+ 48) 002fa8d3 :_task0___7BLooperPv + 0x003f 26 70102fac (+ 48) 0069dbd8 :_get_next_team_info + 0x005c (nearest) 27 70102fdc (+ 0) 70102fec 3487:w>Deskbar_146_stack at 0x700c3000 + 0x3ffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 23:43:37 2008 From: trac at haiku-os.org (mmlr) Date: Sun, 17 Aug 2008 21:43:37 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> Message-ID: <049.77afea64e31d14a0ba26028e31c81f5a@haiku-os.org> #2625: ZipOMatic doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): I have seen that as well, though not sure how to reproduce it. I invoked Zip-O-Matic through navigating to the Tracker Add-Ons folder and running it from there. Maybe this is another instance of unregistered MIME-Type and doesn't get picked up by the mime_update.sh during post_install operation as these Add-Ons reside outside the normal apps/preferences folder? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 17 23:56:01 2008 From: trac at haiku-os.org (luroh) Date: Sun, 17 Aug 2008 21:56:01 -0000 Subject: [Haiku-bugs] [Haiku] #2620: USB boot problem: "PANIC: did not find any boot partitions!" In-Reply-To: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> References: <040.4bec29405d3838f4d509141380eca42a@haiku-os.org> Message-ID: <049.a68d35fbb953fed3608e5219d761bb64@haiku-os.org> #2620: USB boot problem: "PANIC: did not find any boot partitions!" ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 5 Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by luroh): Ah, makes sense, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:05:15 2008 From: trac at haiku-os.org (korli) Date: Sun, 17 Aug 2008 22:05:15 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.d9fa111e9555a607522899def4cadc7f@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by korli): * status: reopened => closed * resolution: => fixed Comment: Updated in r27012. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:25:27 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 17 Aug 2008 22:25:27 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h Message-ID: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The POSIX headers {{{netinet/in.h}}} and {{{netinet/NetAdress.h}}} appear to duplicate some definitions. This somehow leads to a redefinition error for {{{struct sockaddr_in}}} when compiling Git with IPv6 support. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:30:53 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 22:30:53 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.eefe05d041f514cf3269e5ba710f6359@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by scottmc): This is a dupe of #1867 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:36:14 2008 From: trac at haiku-os.org (korli) Date: Sun, 17 Aug 2008 22:36:14 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.f97064e536d835e8e468fb8bd627e18b@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by korli): Could it be fixed in r27014 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:36:56 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 17 Aug 2008 22:36:56 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.b9f3c6f1a2b81021139b65146edf9ad2@haiku-os.org> #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Sorry. The error does occur, with the headers I'm a little wrong: {{{netinet/in.h}}} is not in posix but in legacy, {{{in6.h}}} is in posix though, complicated... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:47:15 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 22:47:15 -0000 Subject: [Haiku-bugs] [Haiku] #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility In-Reply-To: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> References: <040.c232950afe8f630d7c1d09b812d62808@haiku-os.org> Message-ID: <049.576508c8577eb26fea0a67fdaef59764@haiku-os.org> #2628: TIFF translator doesn't handle TIFF files created by MacOS screenshot utility ----------------------------------+----------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Comment(by scottmc): Haiku (as of r26990) is using tiff 3.6.1, current released version of libtiff is 3.8.2: http://ports.haiku-files.org/wiki/media-libs/tiff/3.8.2/1 This may or may not fix this issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 00:56:16 2008 From: trac at haiku-os.org (bbjimmy) Date: Sun, 17 Aug 2008 22:56:16 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory Message-ID: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> #2633: JAM vfork: Out of memory --------------------------+------------------------------------------------- Reporter: bbjimmy | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- jam on r27011 real hardware install with 448 MB of memory .... patience... patience... found 66238 target(s) updating 8855 target(s) InitScript1 generated/haiku.image-init-vars vfork: Out of memory -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 01:52:48 2008 From: trac at haiku-os.org (scottmc) Date: Sun, 17 Aug 2008 23:52:48 -0000 Subject: [Haiku-bugs] [Haiku] #2193: Gzip needs 1.2.4b patch applied (easy one) (was: Gzip needs 1.2.4b patch applied) In-Reply-To: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> References: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> Message-ID: <051.6a8c68a80b72b941ec745ede11f20815@haiku-os.org> #2193: Gzip needs 1.2.4b patch applied (easy one) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by scottmc): Just need to apply the patch... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 02:09:12 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 18 Aug 2008 00:09:12 -0000 Subject: [Haiku-bugs] [Haiku] #2193: Gzip needs 1.2.4b patch applied (easy one) In-Reply-To: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> References: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> Message-ID: <051.51fd2cf3106638947b0e20a74db1abcb@haiku-os.org> #2193: Gzip needs 1.2.4b patch applied (easy one) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by scottmc): There is a 1.3.12 which is used by FreeBSD among others: http://ports.haiku-files.org/wiki/app-arch/gzip/1.3.12/1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 02:34:14 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 18 Aug 2008 00:34:14 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.3d0701e7ba64be2bed3f61322a655d49@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by anevilyak): * status: new => closed * resolution: => invalid Comment: This won't work until swap support is complete. jam on its own needs around 550MB to do its build calculations and fork, ignoring the rest of the OS, cache, etc, as a result of which this currently won't be doable with less than ~800MB-1GB of RAM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:13:12 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 18 Aug 2008 01:13:12 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.245cc8aa8677348ee99c00010100e380@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by bbjimmy): This may be true, but it still needs to be fixed before Alpha 1 release -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:17:38 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 18 Aug 2008 01:17:38 -0000 Subject: [Haiku-bugs] [Haiku] #1972: Implement paging (swap file) support In-Reply-To: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> References: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> Message-ID: <049.2aae5778cf2526df2dcd31ab55e5e344@haiku-os.org> #1972: Implement paging (swap file) support ----------------------------+----------------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bbjimmy): * cc: black.belt.jimmy at gmail.com (added) Comment: #2633: JAM vfork: Out of memory apparently these are related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:20:37 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 18 Aug 2008 01:20:37 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.0c9044bb17454a7581e6e4867c17602c@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): Yes, but it's already a well known issue with other bugs tracking it in the system. It may have been more accurate to close this as a duplicate but I couldn't find the ticket number offhand. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:23:42 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 18 Aug 2008 01:23:42 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.7c02a6dfcad6da2ae8bc39724cd207cb@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by bbjimmy): ticked #1972 perhaps -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:26:39 2008 From: trac at haiku-os.org (umccullough) Date: Mon, 18 Aug 2008 01:26:39 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.a59f520701563f01d1802eef915d7757@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): Replying to [comment:2 bbjimmy]: > This may be true, but it still needs to be fixed before Alpha 1 release It's already present on the proposals page (Prop #8): http://dev.haiku- os.org/wiki/R1/Alpha1Proposals#Prop8:FinishandIncludeSwapFileSupport Currently there is a GSoC student working on it under the mentorship of Ingo I believe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:29:47 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 18 Aug 2008 01:29:47 -0000 Subject: [Haiku-bugs] [Haiku] #2633: JAM vfork: Out of memory In-Reply-To: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> References: <042.c80f9f157a3918bcce01effa9115311e@haiku-os.org> Message-ID: <051.ff5e162db861180202c75876531f5a0e@haiku-os.org> #2633: JAM vfork: Out of memory ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): Correct and it's getting relatively close to being able to be turned on from what I've seen. Hopefully in the next few weeks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 03:41:23 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 18 Aug 2008 01:41:23 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.15660c26cae6bc92d238872dbbd5f7b0@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by bbjimmy): Not only is it not fixed, after running the installer one is left with an unbootable partition. Now running makebootable from the command line no has the same result. I can no longer install haiku and make the new partition boot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 04:04:15 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 18 Aug 2008 02:04:15 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.c391eaa849b636ac40e36c1400890ff3@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by bbjimmy): I ran "makebootable /dev/disk/ata/0/raw" instead of "makebootable /TEST" and I could then boot the new partition ... haiku r27015 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 08:36:09 2008 From: trac at haiku-os.org (axeld) Date: Mon, 18 Aug 2008 06:36:09 -0000 Subject: [Haiku-bugs] [Haiku] #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. In-Reply-To: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> References: <038.cdecad3a55c5fd81b5c9068b60362661@haiku-os.org> Message-ID: <047.b985611b4fd4dde6ed0453774c1fee95@haiku-os.org> #2583: Mounted partitions other than boot get a cabinet icon instead of the disk icon. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: low | Milestone: R1 Component: User Interface | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => duplicate -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 09:13:18 2008 From: trac at haiku-os.org (axeld) Date: Mon, 18 Aug 2008 07:13:18 -0000 Subject: [Haiku-bugs] [Haiku] #1867: Icons for other volumes default to the file cabinet icon In-Reply-To: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> References: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> Message-ID: <051.4e89d00c60b8bdfcb24af4a566b7c11d@haiku-os.org> #1867: Icons for other volumes default to the file cabinet icon ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: I am not sure what Bruno tested, but it works fine over here on different machines. Fixed in r27001. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 10:50:56 2008 From: trac at haiku-os.org (stippi) Date: Mon, 18 Aug 2008 08:50:56 -0000 Subject: [Haiku-bugs] [Haiku] #1867: Icons for other volumes default to the file cabinet icon In-Reply-To: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> References: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> Message-ID: <051.bf32113386fcf427aab0ec007f4bb6ee@haiku-os.org> #1867: Icons for other volumes default to the file cabinet icon ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): I would estimate that he set is Desktop icon size to something else than 16x16 or 32x32. If I read your patch correctly, you bail out early if the icon size is not one of those. This is different from the rest of the icon functions, where I check the color space of the icon. If it's 32 bit, it ignores the given icon_size and just uses the bitmap size. I can work on this today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 11:02:25 2008 From: trac at haiku-os.org (emitrax) Date: Mon, 18 Aug 2008 09:02:25 -0000 Subject: [Haiku-bugs] [Haiku] #2634: Panic during boot on hash_next Message-ID: <042.ec724f9fcdc6a907e1e0aab12ab8d7de@haiku-os.org> #2634: Panic during boot on hash_next -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This happened as well with file cache debug on. {{{ lookup page from offset 32768: 0x91cfb790, size = 169, pageOffset = 1667 file_cache_read(ref = 0x90c5cd48, offset = 34280, buffer = 0x7ffed46c, size = 155) cache_io(ref = 0x90c5cd48, offset = 34280, buffer = 0x7ffed46c, size = 155, read) lookup page from offset 32768: 0x91cfb790, size = 155, pageOffset = 1512 vm_page_fault: kernel thread accessing invalid user memory! vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x8, ip 0x800a59c9, write 0, user 0, thread 0x9 PANIC: vm_page_fault: unhandled page fault in kernel space at 0x8, ip 0x800a59c9 Welcome to Kernel Debugging Land... Thread 9 "block notifier/writer" running on CPU 0 kdebug> bt stack trace for thread 9 "block notifier/writer" kernel stack: 0x80169000 to 0x8016d000 frame caller :function + offset 0 8016ca68 (+ 48) 8005598d :invoke_debugger_command + 0x00f5 1 8016ca98 (+ 64) 8005577d :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 8016cad8 (+ 64) 80055b05 :invoke_debugger_command_pipe + 0x009d 3 8016cb18 (+ 48) 800569e0 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 8016cb48 (+ 48) 80056396 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 8016cb78 (+ 224) 80057dac :evaluate_debug_command + 0x0088 6 8016cc58 (+ 64) 80053dca :kernel_debugger_loop__Fv + 0x01ae 7 8016cc98 (+ 48) 80054993 :kernel_debugger + 0x0117 8 8016ccc8 (+ 192) 80054871 :panic + 0x0029 9 8016cd88 (+ 80) 800ab9f5 :vm_page_fault + 0x0111 10 8016cdd8 (+ 64) 800b79a1 :page_fault_exception + 0x00c9 11 8016ce18 (+ 12) 800baf46 :int_bottom + 0x0036 (nearest) kernel iframe at 0x8016ce24 (end = 0x8016ce74) eax 0x0 ebx 0x8016cebc ecx 0x0 edx 0x0 esi 0x0 edi 0x0 ebp 0x8016ce78 esp 0x8016ce58 eip 0x800a59c9 eflags 0x10256 vector: 0xe, error code: 0x0 12 8016ce24 (+ 84) 800a59c9 :hash_next + 0x0015 13 8016ce78 (+ 352) 8002bfed :block_notifier_and_writer__FPv + 0x01e5 14 8016cfd8 (+ 32) 8004c5f7 :_create_kernel_thread_kentry__Fv + 0x001b 15 8016cff8 (+2145988616) 8004c594 :thread_kthread_exit__Fv + 0x0000 kdebug> reboot }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 11:33:18 2008 From: trac at haiku-os.org (axeld) Date: Mon, 18 Aug 2008 09:33:18 -0000 Subject: [Haiku-bugs] [Haiku] #1867: Icons for other volumes default to the file cabinet icon In-Reply-To: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> References: <042.af4133f370f5b33b2b2236d3de53e450@haiku-os.org> Message-ID: <051.b715db501223c905d03b37bf1bba1322@haiku-os.org> #1867: Icons for other volumes default to the file cabinet icon ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): Actually, I just copied what was already there. But please remove that check; I would be all in favour of getting rid of that icon_which parameter everywhere, but for R1, I thought consistency would be the preferred way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 14:09:18 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 12:09:18 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.ddd4f4d758626f6d2fc3c51d5e8825c4@haiku-os.org> #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Really sorry for the confusion, but my original report was right. Spotlight just managed to delete some files while I was looking at them. There are two files in {{{headers/posix/netinet/in/}}}, {{{in.h}}} and {{{NetAddress.h}}}, for which a diff shows no difference at all. opengroup.org has no mention of a {{{NetAddress.h}}}, so I suggest we move or drop it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 14:28:15 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 12:28:15 -0000 Subject: [Haiku-bugs] [Haiku] #2636: UserBuildConfig.ReadMe documents unimplemented HAIKU_ADD_POSIX_TEST_SUITE_TO_IMAGE variable Message-ID: <043.45725cfe1f5268acf886a89756ec0b74@haiku-os.org> #2636: UserBuildConfig.ReadMe documents unimplemented HAIKU_ADD_POSIX_TEST_SUITE_TO_IMAGE variable --------------------------+------------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- {{{UserBuildConfig.ReadMe}}} has an example {{{ HAIKU_ADD_POSIX_TEST_SUITE_TO_IMAGE = 1 ; }}} which supposedly copies the POSIX test suite to {{{home/posixtestsuite}}}, but it doesn't, and `grep -r` finds no mention of it elsewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 15:02:42 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 13:02:42 -0000 Subject: [Haiku-bugs] [Haiku] #2637: [PATCH] Signal tests do not compile with gcc4 Message-ID: <043.6e60b69ac343e5f85d95dad042109e5f@haiku-os.org> #2637: [PATCH] Signal tests do not compile with gcc4 -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- {{{signal_test}}} does not compile due to lack of {{{stdlib.h}}} for {{{exit}}}. {{{syscall_restart}}} does not compile due to ISO-forbidden C++ array initialization. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 15:03:51 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 13:03:51 -0000 Subject: [Haiku-bugs] [Haiku] #2637: [PATCH] Signal tests do not compile with gcc4 In-Reply-To: <043.6e60b69ac343e5f85d95dad042109e5f@haiku-os.org> References: <043.6e60b69ac343e5f85d95dad042109e5f@haiku-os.org> Message-ID: <052.e42efca94b4a9907f3e2de2ac288085d@haiku-os.org> #2637: [PATCH] Signal tests do not compile with gcc4 --------------------------------+------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by andreasf): The attached patch fixes compilation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 16:46:25 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 18 Aug 2008 14:46:25 -0000 Subject: [Haiku-bugs] [Haiku] #2636: UserBuildConfig.ReadMe documents unimplemented HAIKU_ADD_POSIX_TEST_SUITE_TO_IMAGE variable In-Reply-To: <043.45725cfe1f5268acf886a89756ec0b74@haiku-os.org> References: <043.45725cfe1f5268acf886a89756ec0b74@haiku-os.org> Message-ID: <052.e2675672b5dc197e6b2038bf8ddac8e6@haiku-os.org> #2636: UserBuildConfig.ReadMe documents unimplemented HAIKU_ADD_POSIX_TEST_SUITE_TO_IMAGE variable ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Removed in r27039. It had been replaced by an option (test) package. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 17:55:43 2008 From: trac at haiku-os.org (korli) Date: Mon, 18 Aug 2008 15:55:43 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.1d5e5c635a8e40e18b6c5c82a70055fd@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by korli): Could you check again with r27042 please ? The I/O kernel backend could be at fault, at least I don't see why it wouldn't work as expected now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 18:06:41 2008 From: trac at haiku-os.org (korli) Date: Mon, 18 Aug 2008 16:06:41 -0000 Subject: [Haiku-bugs] [Haiku] #2435: [Media] volume slider is flickering when moving In-Reply-To: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> References: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> Message-ID: <049.33f147fbca40a95985fe0058ca25fd2c@haiku-os.org> #2435: [Media] volume slider is flickering when moving --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by korli): You mean the one in the Deskbar ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 21:19:27 2008 From: trac at haiku-os.org (diver) Date: Mon, 18 Aug 2008 19:19:27 -0000 Subject: [Haiku-bugs] [Haiku] #2435: [Media] volume slider is flickering when moving In-Reply-To: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> References: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> Message-ID: <049.40db4bbff218787fbb812f8dc4707ce2@haiku-os.org> #2435: [Media] volume slider is flickering when moving --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by diver): Exactly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 22:28:47 2008 From: trac at haiku-os.org (axeld) Date: Mon, 18 Aug 2008 20:28:47 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.62919f885766cc0a423219310aec8982@haiku-os.org> #2632: Duplicate definitions in netinet/in.h and netinet/NetAddress.h ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Not sure what your system messed up there, but NetAddress.h is in headers/os/net/, and not in posix/netinet. Also, it has completely different contents than in.h, it just happens to include it. If you still find something wrong with the current setup, feel free to reopen this bug, though; maybe I just didn't understand you correctly :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 22:35:11 2008 From: trac at haiku-os.org (axeld) Date: Mon, 18 Aug 2008 20:35:11 -0000 Subject: [Haiku-bugs] [Haiku] #2638: input_server's screen_saver filter crash in ScreenSaverFilter::Filter() Message-ID: <040.3f99bcf9dcc23175aa1a09d21b160a81@haiku-os.org> #2638: input_server's screen_saver filter crash in ScreenSaverFilter::Filter() -----------------------------------+---------------------------------------- Reporter: axeld | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Add-Ons/Input Filters | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- I turned off the screen saver, and closed the ScreenSaver preferences app, then the input_server crashed obviously while trying to update a BMessageRunner. Image attached, happened with or around r27015. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:09:04 2008 From: trac at haiku-os.org (korli) Date: Mon, 18 Aug 2008 21:09:04 -0000 Subject: [Haiku-bugs] [Haiku] #2638: input_server's screen_saver filter crash in ScreenSaverFilter::Filter() In-Reply-To: <040.3f99bcf9dcc23175aa1a09d21b160a81@haiku-os.org> References: <040.3f99bcf9dcc23175aa1a09d21b160a81@haiku-os.org> Message-ID: <049.88ec815e5f5e922eae1fbec3dc2f133c@haiku-os.org> #2638: input_server's screen_saver filter crash in ScreenSaverFilter::Filter() ------------------------------------+--------------------------------------- Reporter: axeld | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by korli): Hopefully r27049 should help to avoid the crash. Maybe better locking is needed though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:12:15 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 21:12:15 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Possible redefinition for struct sockaddr_in, related to IPv6 (was: Duplicate definitions in netinet/in.h and netinet/NetAddress.h) In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.bcb4db9383afc53b3278b7e9a4297f3f@haiku-os.org> #2632: Possible redefinition for struct sockaddr_in, related to IPv6 ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by andreasf): * status: closed => reopened * resolution: invalid => Comment: Git confirms that some files have been wrongly moved around somehow on my Mac, yeah. But that's the wrong explanation only. The problem of {{{struct sockaddr_in}}} being redefined occurs while compiling on a Haiku system, so that is ''still'' a problem. Unfortunately in this case I have absolutely no explanation at hand. I checked the header guards, and they looked okay. I am aware that IPv6 is not or not fully supported yet, but in that case I'd expect to either find that out at runtime, or at compile-time by missing IPv6 structs, functions etc. Not by conflicts with otherwise fine IPv4 stuff. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:17:04 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 18 Aug 2008 21:17:04 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Possible redefinition for struct sockaddr_in, related to IPv6 In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.a873bfc1318e8c4cee261ddde48001f8@haiku-os.org> #2632: Possible redefinition for struct sockaddr_in, related to IPv6 ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): Just curious, what's the testcase that's causing it to fail? I've compiled various other pieces of network code without issues on Haiku itself, so it'd be helpful to have some more specifics here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:17:58 2008 From: trac at haiku-os.org (korli) Date: Mon, 18 Aug 2008 21:17:58 -0000 Subject: [Haiku-bugs] [Haiku] #2193: Gzip needs 1.2.4b patch applied (easy one) In-Reply-To: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> References: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> Message-ID: <051.651fd21096966b6432515f42e85f577c@haiku-os.org> #2193: Gzip needs 1.2.4b patch applied (easy one) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r27050. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:35:08 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 18 Aug 2008 21:35:08 -0000 Subject: [Haiku-bugs] [Haiku] #2632: Possible redefinition for struct sockaddr_in, related to IPv6 In-Reply-To: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> References: <043.9ffec829e65b63304f0426a80485003a@haiku-os.org> Message-ID: <052.778cda0d71d13b660504f137c82611d8@haiku-os.org> #2632: Possible redefinition for struct sockaddr_in, related to IPv6 ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Compiling Git (git.git master, post 1.6.0-rc3) without setting {{{NO_IPV6=YesPlease}}} in the {{{Makefile}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:48:28 2008 From: trac at haiku-os.org (korli) Date: Mon, 18 Aug 2008 21:48:28 -0000 Subject: [Haiku-bugs] [Haiku] #2403: [Installer] Shows install aborted if you click begin without first selecting an "onto" volume In-Reply-To: <042.1c4ad7f77b6f4e78625db79d6441264c@haiku-os.org> References: <042.1c4ad7f77b6f4e78625db79d6441264c@haiku-os.org> Message-ID: <051.81b7109b0c286f48735c390fb95cd818@haiku-os.org> #2403: [Installer] Shows install aborted if you click begin without first selecting an "onto" volume -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r27051. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 23:52:28 2008 From: trac at haiku-os.org (emitrax) Date: Mon, 18 Aug 2008 21:52:28 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount Message-ID: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> #2639: [usb_disk]: unable to mount -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Here is what I get when I try to mount my usb stick. {{{ usb_disk: unhandled ioctl 22 usb_disk: unhandled ioctl 23 usb_disk: unhandled ioctl 13 usb_disk: unhandled ioctl 22 usb_disk: unhandled ioctl 23 file_cache: read pages failed: Is a directory }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 00:45:35 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 18 Aug 2008 22:45:35 -0000 Subject: [Haiku-bugs] [Haiku] #2640: [OpenSSL] Needs updating to 0.9.8h Message-ID: <042.a18939ac428e40cf4140fae003d36aa1@haiku-os.org> #2640: [OpenSSL] Needs updating to 0.9.8h ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ I tested using the 0.9.8g patch to build OpenSSL 0.9.8h and the patch appears to work on it, so this should be an easy one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 00:56:25 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 18 Aug 2008 22:56:25 -0000 Subject: [Haiku-bugs] [Haiku] #2283: less needs updating (easy) (was: less needs updating) In-Reply-To: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> References: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> Message-ID: <051.211acbd9373ade5ffb0a296f06196a72@haiku-os.org> #2283: less needs updating (easy) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by scottmc): Perhaps needs tagging rather than a diff? Anyways should be fairly easy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 01:16:57 2008 From: trac at haiku-os.org (emitrax) Date: Mon, 18 Aug 2008 23:16:57 -0000 Subject: [Haiku-bugs] [Haiku] #2631: Panic during boot with file_cache debug on In-Reply-To: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> References: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> Message-ID: <051.8dca1b4932d2515531ef82cc6ccd002b@haiku-os.org> #2631: Panic during boot with file_cache debug on ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): The problem seems to be in the block_cache constructor. The object gets added to the sCaches list, which is unlocked right away. However, the mutex of the cache is only initialized right before exit the constructor. What happens here is that another thread gets to the object from the sCacheList before it gets fully constructed. In fact, I don't understand why the objet is added right away to the sCacheList. What happens if the constructor fails? Does the invalid object still hangs around? I'd move the sCaches.Add(this); from the beginning to the end of the constructor, right after the mutex is initialized. This way the objet is only added if correctly constructed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 02:18:37 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 00:18:37 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.bdad3e35c34cd4d1fc7afea780fd3a19@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Even more easily reproducible if you move the mouse while fast-clicking (within the icon off-course). Not moving at all (turn your mouse upsidedown) makes it really hard to reproduce (if not unreproducible). Can't provide a backtrace right know, sorry, but it calls the debuger in _AddChild: AddChild failed - the view already has a parent. Might be unrelated, but while testing this, i noticed another strange thing: If you move really slowly (like 1 pixel beetween two clicks [doesn't need to be fast clicks]) it can toggle the focus of a tracker window, specifically the last focused one. (easily reproducible too, and on any desktop icon) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 02:29:50 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 00:29:50 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.104b878568a59dce2ac0b9d3b5e153a3@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): i couldn't reproduce on it r5 (max v4.1), maybe it's not tracker's fault after all... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 04:52:02 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 02:52:02 -0000 Subject: [Haiku-bugs] [Haiku] #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) In-Reply-To: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> References: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> Message-ID: <052.326ae70aa575bee98038f47464932992@haiku-os.org> #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): I'm all for it too, i get bitten everyday by this one! I've got the simple patch ready, does everyone agree on this change? By the way Shift+DownArrow/UpArrow and Shift+Home/End are already good. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 05:05:58 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 19 Aug 2008 03:05:58 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.4f631b4aec108a46b611fc2df0a50d9e@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by anevilyak): Was that R5 with the stock Tracker or with OpenTracker? I specifically remember patching a few race conditions in OT to try and reduce that problem, though I don't remember managing to eliminate it completely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 06:14:51 2008 From: trac at haiku-os.org (bbjimmy) Date: Tue, 19 Aug 2008 04:14:51 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.90308d61330ab913b54783b9406b056a@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by bbjimmy): I tried again with r27057. The issue is the same. This time I ran the installer from a terminal and it said it was installing the boot code to /dev/disk/ata/0/slave/raw but it would not boot. Running makebootable /TEST stated that it was also installing the boot code to /dev/disk/ata/0/slave/raw but left the partition unbootable. Running makebootable /dev/disk/ata/0/slave/raw worked. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 09:18:25 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 19 Aug 2008 07:18:25 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.b64f7283487a850ef9f9638b173e6254@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Any more details on that? What kind of device is it? Did it work previously? What filesystem do you try to mount? I guess the ioctl's are for the device icons which are not implemented in usb_disk, they shouldn't be fatal at all though. Some days ago it was reported to me by aldeck on IRC that mounting did work, but the filesystem was empty after that. That's a regression with FAT it seems though and not related to usb_disk, as the device can be accessed correctly still. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 09:26:49 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 07:26:49 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.d0d839e580f0514357f23bc40cae6d72@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Replying to [comment:1 mmlr]: > Any more details on that? What kind of device is it? Did it work previously? What filesystem do you try to mount? I can turn debug output on if there is one. It definitely used to work. It's an ext3 partition and it is detected during scanning. It's a normal usb stick. > > I guess the ioctl's are for the device icons which are not implemented in usb_disk, they shouldn't be fatal at all though. Some days ago it was reported to me by aldeck on IRC that mounting did work, but the filesystem was empty after that. That's a regression with FAT it seems though and not related to usb_disk, as the device can be accessed correctly still. About the ioctls I thought that too, but I thought they could be the cause. When I mount it from the tracker, no icons appear on the desktop, but an "unnamed volume" entry is added to the root directory. Although an ls of it result in "Is a directory" error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:09:00 2008 From: trac at haiku-os.org (VinDuv) Date: Tue, 19 Aug 2008 08:09:00 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems Message-ID: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Configuration : real hardware, laptop with an (old) NVIDIA Geforce2 Go and a 1400x1050 internal LCD screen. I tested with r27057. After the boot, the screen goes completely unreadable (see the attached screenshot). It works fine in fail-safe video mode. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:32:39 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 08:32:39 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.51d8b0dc4b4d62b3ed73fbcc6dd58a83@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): {{{ usb_disk: open(disk/usb/0/0/raw) usb_disk: opening raw device disk/usb/0/0/raw for disk/usb/0/0/raw usb_disk: unhandled ioctl 22 usb_disk: unhandled ioctl 23 usb_disk: close() usb_disk: free() usb_disk: open(disk/usb/0/0/raw) usb_disk: opening raw device disk/usb/0/0/raw for disk/usb/0/0/raw usb_disk: unhandled ioctl 13 usb_disk: close() usb_disk: free() usb_disk: open(disk/usb/0/0/raw) usb_disk: opening raw device disk/usb/0/0/raw for disk/usb/0/0/raw usb_disk: unhandled ioctl 22 usb_disk: unhandled ioctl 23 usb_disk: close() usb_disk: free() usb_disk: B_GET_MEDIA_STATUS: 0x00000000 usb_disk: B_GET_MEDIA_STATUS: 0x00000000 usb_disk: open(disk/usb/0/0/0) usb_disk: opening raw device disk/usb/0/0/raw for disk/usb/0/0/0 usb_disk: read(32768, 1024) usb_disk: read successful with 1024 bytes usb_disk: B_GET_GEOMETRY: 3963904 sectors at 512 bytes per sector usb_disk: read(35840, 4096) usb_disk: read successful with 4096 bytes usb_disk: read(539648, 4096) usb_disk: read successful with 4096 bytes file_cache: read pages failed: Is a directory file_cache: read pages failed: Is a directory usb_disk: B_GET_MEDIA_STATUS: 0x00000000 Last message repeated 4 times. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:42:58 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 08:42:58 -0000 Subject: [Haiku-bugs] [Haiku] #2631: Panic during boot with file_cache debug on In-Reply-To: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> References: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> Message-ID: <051.58096afb3ddd1a15e79ea1f3b6ff3589@haiku-os.org> #2631: Panic during boot with file_cache debug on ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks, the patch looks good! I just moved the registration of the low resource hook out of the mutex, and changed the order in the destructor as well. The list was originally used for debugging purposes only, and there the order didn't matter. Fixed in r27058. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:43:20 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 08:43:20 -0000 Subject: [Haiku-bugs] [Haiku] #2631: Panic during boot with file_cache debug on In-Reply-To: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> References: <042.feb67f2b681b07d3e6be91fefe843c48@haiku-os.org> Message-ID: <051.8087691ff51292f3357c353853812342@haiku-os.org> #2631: Panic during boot with file_cache debug on ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => high * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 18 13:54:25 2008 From: trac at haiku-os.org (xspager) Date: Mon, 18 Aug 2008 11:54:25 -0000 Subject: [Haiku-bugs] [Haiku] #2635: GCC can't allocate more memory: virtual memory exhausted Message-ID: <042.5eca8373536526be5cbaefc280fbda40@haiku-os.org> #2635: GCC can't allocate more memory: virtual memory exhausted -----------------------+---------------------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x64 Blocking: | -----------------------+---------------------------------------------------- When I call make to build the GBA emulator VBA and everything goes fine, until it reach the file GBA.cpp. The build end with this error: source='../GBA.cpp' object='GBA.o' libtool=no \ depfile='.deps/GBA.Po' tmpdepfile='.deps/GBA.TPo' \ depmode=gcc /bin/sh ../../depcomp \ g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"VisualBoyAdvance\" -DVERSION=\"1.7.2\" -DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_MALLOC_H=1 -DHAVE_STRINGS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_NETINET_IN_H=1 -I. -I. -I../../src -DSDL -DSYSCONFDIR=\"/usr/local/etc\" -fno-exceptions -I/boot/home/config/include/SDL -D_GNU_SOURCE=1 -g -O2 -DPROFILING -DMMX -DDEV_VERSION -c -o GBA.o `test -f '../GBA.cpp' || echo './'`../GBA.cpp /boot/home/src/VisualBoyAdvance-1.7.2/src/GBA.cpp: In function `void CPULoop(int)': /boot/home/src/VisualBoyAdvance-1.7.2/src/GBA.cpp:3919: virtual memory exhausted make[2]: *** [GBA.o] Error 1 make[2]: Leaving directory `/boot/home/src/VisualBoyAdvance-1.7.2/src/sdl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/boot/home/src/VisualBoyAdvance-1.7.2/src' make: *** [all-recursive] Error 1 I'm running Haiku on a real x86_64(AMD Athlon X2) machine with 2GB of memory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:49:34 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 08:49:34 -0000 Subject: [Haiku-bugs] [Haiku] #2618: bfs: *** invalid run(0,0,0) In-Reply-To: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> References: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> Message-ID: <051.30ce5628c9be3d4fd8c18b2e4a513acf@haiku-os.org> #2618: bfs: *** invalid run(0,0,0) -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => critical * component: - General => File Systems/BFS * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 10:49:48 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 08:49:48 -0000 Subject: [Haiku-bugs] [Haiku] #2634: Panic during boot on hash_next In-Reply-To: <042.ec724f9fcdc6a907e1e0aab12ab8d7de@haiku-os.org> References: <042.ec724f9fcdc6a907e1e0aab12ab8d7de@haiku-os.org> Message-ID: <051.3fd9b92a9be057834bb77b374c530303@haiku-os.org> #2634: Panic during boot on hash_next ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => high * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:00:19 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 09:00:19 -0000 Subject: [Haiku-bugs] [Haiku] #2642: bfs: mkdir creates invalid directory Message-ID: <042.0a0eb7fe2bd7d8e9792f3794a7092aa8@haiku-os.org> #2642: bfs: mkdir creates invalid directory -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Sorry, I couldn't find a better summary {{{ for i in `seq -w 1 1000` ; do mkdir $i ; cd $i ; done }}} By running the above in bash, you'll see that onced reached the absolute deepth of 204 levels, the script continues to create directory in the last level, but it is unable to cd'in, and returns an error of "no such file or directory". While not critical, it shouldn't create invalid directory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:01:42 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 09:01:42 -0000 Subject: [Haiku-bugs] [Haiku] #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) In-Reply-To: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> References: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> Message-ID: <052.1968554fcb77b29066a11d7a1db22d08@haiku-os.org> #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): Since there is no real logic but only habituation behind all this, I think there is nothing wrong with either way of doing it. Since everyone else does it differently, though, I would think it would be smartest to switch as long as there aren't more Haiku users around ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:17:15 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 19 Aug 2008 09:17:15 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected Message-ID: <043.0786930e484a2f240575b79901142eea@haiku-os.org> #2643: Black screen when DVI connected -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- When I connect either both VGA and DVI, or just DVI to the following graphics card: {{{ device Unclassified device (Non-VGA unclassified device) [0|0|0] vendor 10de: nVidia Corporation device 0343: NV36 [GeForce FX 5700LE] }}} the initial splash screen is displayed nicely on the screen(s) but I then get a black screen (on both screens if both connected). This appears to be a problem with the Nvidia driver. With VESA (fail-safe mode in boot menu) I get the desktop displayed on both screens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:29:47 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 19 Aug 2008 09:29:47 -0000 Subject: [Haiku-bugs] [Haiku] #2618: bfs: *** invalid run(0,0,0) In-Reply-To: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> References: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> Message-ID: <051.4c8638492792ecd5feee71c72bb95e15@haiku-os.org> #2618: bfs: *** invalid run(0,0,0) -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by mmlr): I've actually seen that on my laptop as well. I investigated it a bit without result at first but then dropped it because I couldn't reproduce it on another system (I assumed the filesystem on the laptop was just a bit corrupted). If you can reproduce it like that, you should also be able to reproduce it by generating a large file through dd. It did that for me with {{{dd if=/dev/zero of=/the/file bs=2M}}} always around 3.8GB written. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:36:24 2008 From: trac at haiku-os.org (stippi) Date: Tue, 19 Aug 2008 09:36:24 -0000 Subject: [Haiku-bugs] [Haiku] #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) In-Reply-To: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> References: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> Message-ID: <052.74e0c6720da27a668533bcf65ea100c1@haiku-os.org> #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by stippi): +1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 11:46:19 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 09:46:19 -0000 Subject: [Haiku-bugs] [Haiku] #2644: Panic on Scheduler::_Finisher Message-ID: <042.dd1510cedfb1e76e3c5d793ae3673b8a@haiku-os.org> #2644: Panic on Scheduler::_Finisher -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Happened with latest rev while doing the following {{{ dd if=/dev/zero of=/the/file bs=2M }}} Serial debug output {{{ PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbf03 from eip 0x80066337 Welcome to Kernel Debugging Land... Thread 25 "scsi scheduler" running on CPU 0 kdebug> bt stack trace for thread 25 "scsi scheduler" kernel stack: 0x80266000 to 0x8026a000 frame caller :function + offset 0 80269b44 (+ 48) 80055dd1 :invoke_debugger_command + 0x00f5 1 80269b74 (+ 64) 80055bc1 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 80269bb4 (+ 64) 80055f49 :invoke_debugger_command_pipe + 0x009d 3 80269bf4 (+ 48) 80056e24 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 80269c24 (+ 48) 800567da :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 80269c54 (+ 224) 800581f0 :evaluate_debug_command + 0x0088 6 80269d34 (+ 64) 8005420e :kernel_debugger_loop__Fv + 0x01ae 7 80269d74 (+ 48) 80054dd7 :kernel_debugger + 0x0117 8 80269da4 (+ 192) 80054cb5 :panic + 0x0029 9 80269e64 (+ 48) 800b8180 :page_fault_exception + 0x0078 10 80269e94 (+ 12) 800bb776 :int_bottom + 0x0036 (nearest) kernel iframe at 0x80269ea0 (end = 0x80269ef0) eax 0x90b92870 ebx 0x90b9407c ecx 0x90b927e4 edx 0xdeadbeef esi 0x90b927d0 edi 0x90b94000 ebp 0x80269f28 esp 0x80269ed4 eip 0x80066337 eflags 0x210082 vector: 0xe, error code: 0x2 11 80269ea0 (+ 136) 80066337 :_Finisher__11IOScheduler + 0x008f 12 80269f28 (+ 96) 80066a43 :_GetNextUnscheduledRequest__11IOScheduler + 0x0177 13 80269f88 (+ 48) 80066b85 :_Scheduler__11IOScheduler + 0x0015 14 80269fb8 (+ 32) 80066c32 :_SchedulerThread__11IOSchedulerPv + 0x0012 15 80269fd8 (+ 32) 8004ca3b :_create_kernel_thread_kentry__Fv + 0x001b 16 80269ff8 (+2144952328) 8004c9d8 :thread_kthread_exit__Fv + 0x0000 kdebug> teams team id parent name 0x90b7e000 1 0x00000000 kernel_team 0x90b7e8b8 69 0x90b7e000 syslog_daemon 0x90c10ba0 134 0x90c102e8 sh 0x90b7ee88 73 0x90b7e744 input_server 0x90b7e2e8 43 0x90b7e000 registrar 0x90c10e88 138 0x90c1045c media_addon_server 0x90b7e45c 48 0x90b7e000 debug_server 0x90b7e5d0 49 0x90b7e000 net_server 0x90b7e174 174 0x90c10ba0 dd 0x90b7e744 50 0x90b7e000 app_server 0x90b7ed14 85 0x90b7e000 Tracker 0x90c10000 86 0x90b7e000 Deskbar 0x90c102e8 88 0x90b7e000 Terminal 0x90c1045c 89 0x90b7e000 media_server 0x90c10744 91 0x90b7e000 midi_server 0x90c108b8 92 0x90b7e000 print_server kdebug> bt 174 stack trace for thread 174 "dd" kernel stack: 0x80209000 to 0x8020d000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 8020c780 (+ 32) 80041d42 :context_switch__FP6threadT0 + 0x0026 1 8020c7a0 (+ 64) 80041fac :scheduler_reschedule + 0x0248 2 8020c7e0 (+ 48) 800b828e :hardware_interrupt + 0x00a6 3 8020c810 (+ 12) 800bb776 :int_bottom + 0x0036 (nearest) kernel iframe at 0x8020c81c (end = 0x8020c86c) eax 0x0 ebx 0x0 ecx 0x800f969c edx 0x246 esi 0x90d24a80 edi 0x1820d000 ebp 0x8020c8b4 esp 0x8020c850 eip 0x800ada07 eflags 0x246 vector: 0xfb, error code: 0x0 4 8020c81c (+ 152) 800ada07 :lock_memory_etc + 0x00ff 5 8020c8b4 (+ 48) 8006aff9 :LockMemory__8IOBufferlb + 0x003d 6 8020c8e4 (+ 64) 80065fed :ScheduleRequest__11IOSchedulerP9IORequest + 0x002d 7 8020c924 (+ 48) 806db109 :das_io__FPvP9IORequest + 0x0029 8 8020c954 (+ 64) 80064ba4 :devfs_io__FP9fs_volumeP8fs_vnodePvP9IORequest + 0x0144 9 8020c994 (+ 64) 800952e9 :vfs_vnode_io + 0x0029 10 8020c9d4 (+ 224) 80094c5d :do_iterative_fd_io_iterate__FPvP9IORequestPb + 0x024d 11 8020cab4 (+ 64) 8009562f :do_iterative_fd_io + 0x015b 12 8020caf4 (+ 80) 8059e7e3 :bfs_io__FP9fs_volumeP8fs_vnodePvP9IORequest + 0x009b 13 8020cb44 (+ 64) 800952e9 :vfs_vnode_io + 0x0029 14 8020cb84 (+ 192) 8008c5eb :vfs_write_pages + 0x0063 15 8020cc44 (+ 96) 8002f217 :write_to_file__FP14file_cache_refPvxlUlUlbUlUl + 0x01ab 16 8020cca4 (+ 208) 8002f895 :cache_io__FPvT0xUlPUlb + 0x063d 17 8020cd74 (+ 96) 8003004d :file_cache_write + 0x00e1 18 8020cdd4 (+ 80) 80593c15 :WriteAt__5InodeR11TransactionxPCUcPUl + 0x031d 19 8020ce24 (+ 96) 805a0667 :bfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x00d3 20 8020ce84 (+ 64) 8008db70 :file_write__FP15file_descriptorxPCvPUl + 0x0044 21 8020cec4 (+ 80) 8007e459 :common_user_io__FixPvUlb + 0x017d 22 8020cf14 (+ 48) 8007e94c :_user_write + 0x0028 23 8020cf44 (+ 100) 800bb9a2 :pre_syscall_debug_done + 0x0002 (nearest) user iframe at 0x8020cfa8 (end = 0x8020d000) eax 0x7e ebx 0x2b7d40 ecx 0x7ffeee50 edx 0xffff0104 esi 0x0 edi 0x200000 ebp 0x7ffeee8c esp 0x8020cfdc eip 0xffff0104 eflags 0x203 user esp 0x7ffeee50 vector: 0x63, error code: 0x0 24 8020cfa8 (+ 0) ffff0104 25 7ffeee8c (+ 48) 0020250a :unknown + 0x250a 26 7ffeeebc (+ 64) 00203919 :unknown + 0x3919 27 7ffeeefc (+ 128) 00204078 :unknown + 0x4078 28 7ffeef7c (+ 48) 00201c7b :unknown + 0x1c7b 29 7ffeefac (+ 48) 001008ea 3867:runtime_loader_seg0ro at 0x00100000 + 0x8ea 30 7ffeefdc (+ 0) 7ffeefec 3866:dd_main_stack at 0x7efef000 + 0xffffec kdebug> thread 174 THREAD: 0x914e0000 id: 174 (0xae) name: "dd" all_next: 0x9150d000 team_next: 0x00000000 q_next: 0x9151b800 priority: 10 (next 10) state: ready next_state: ready cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 fault_handler: 0x00000000 args: 0x90d249d8 0x00000000 entry: 0x80049774 team: 0x90b7e174, "dd" exit.sem: 2124 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 3864 kernel_stack_base: 0x80209000 user_stack_area: 3866 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 5297401 user_time: 84371 flags: 0x200 architecture dependant section: esp: 0x8020c724 ss: 0x00000010 fpu_state at 0x914e0380 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 12:10:10 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 10:10:10 -0000 Subject: [Haiku-bugs] [Haiku] #2618: bfs: *** invalid run(0,0,0) In-Reply-To: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> References: <042.46d396d5b6a2d3fdc248e77a63409ba3@haiku-os.org> Message-ID: <051.bdfc02e05aebcf22b7f550d96c29afe2@haiku-os.org> #2618: bfs: *** invalid run(0,0,0) -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): Replying to [comment:3 mmlr]: > I've actually seen that on my laptop as well. I investigated it a bit without result at first but then dropped it because I couldn't reproduce it on another system (I assumed the filesystem on the laptop was just a bit corrupted). If you can reproduce it like that, you should also be able to reproduce it by generating a large file through dd. It did that for me with {{{dd if=/dev/zero of=/the/file bs=2M}}} always around 3.8GB written. That actually produced bug #2644, which is easy to reproduce over here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 12:45:51 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 19 Aug 2008 10:45:51 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.2a0926c5bed71dfecf7bad61cdc51751@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): So it looks like it's not a usb_disk problem. Reads seem to work fine from a device standpoint of view. You can verify that by using DiskProbe to directly read from the device. If that works, it must be some upper layer that fails, as usb_disk solely provides the raw I/O. You should try to find the exact location where this "Is a directory" comes from by tracking it from where the file cache output is generated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 12:53:22 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 10:53:22 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.d0a855eef79229c5eb82264d33ea1f94@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Replying to [comment:4 mmlr]: > So it looks like it's not a usb_disk problem. Reads seem to work fine from a device standpoint of view. You can verify that by using DiskProbe to directly read from the device. If that works, it must be some upper layer that fails, as usb_disk solely provides the raw I/O. > Yep, disk probes works. > You should try to find the exact location where this "Is a directory" comes from by tracking it from where the file cache output is generated. I'll try that. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:16:16 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 11:16:16 -0000 Subject: [Haiku-bugs] [Haiku] #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) In-Reply-To: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> References: <043.85bf60c1cc67156741a9df7cc46b9da9@haiku-os.org> Message-ID: <052.e624f19b4c0d3cf6d9d59562419105f7@haiku-os.org> #1255: Make Multi-Selection Modifier Semantics in Tracker Consistent with Standard List Selection (easy) -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: fixed in r27059 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:23:15 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 11:23:15 -0000 Subject: [Haiku-bugs] [Haiku] #1263: Tracker scrollbar confusion In-Reply-To: <048.3a59e14c7ab6530a67389d93cf5484a0@haiku-os.org> References: <048.3a59e14c7ab6530a67389d93cf5484a0@haiku-os.org> Message-ID: <057.73afb6361c94904f7ea0efc56ea1facb@haiku-os.org> #1263: Tracker scrollbar confusion -----------------------------------+---------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Closing this one, this is a multi-issue ticket and all seem to have been fixed. Please open a new more specific ticket (and check existing ones off-course) if there's a remaining issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:38:29 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 11:38:29 -0000 Subject: [Haiku-bugs] [Haiku] #2642: bfs: mkdir creates invalid directory In-Reply-To: <042.0a0eb7fe2bd7d8e9792f3794a7092aa8@haiku-os.org> References: <042.0a0eb7fe2bd7d8e9792f3794a7092aa8@haiku-os.org> Message-ID: <051.65784c516f444d2f199349d553090dcb@haiku-os.org> #2642: bfs: mkdir creates invalid directory ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): This sounds very much like you get beyond B_PATH_NAME_LENGTH; it will cut the path after 1024 bytes, and therefore isn't able to create the directory with the name you intended. What exactly happens? Have you tried to manually enter the deepest level to see how it looks like? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:42:16 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 11:42:16 -0000 Subject: [Haiku-bugs] [Haiku] #2642: bfs: mkdir creates invalid directory In-Reply-To: <042.0a0eb7fe2bd7d8e9792f3794a7092aa8@haiku-os.org> References: <042.0a0eb7fe2bd7d8e9792f3794a7092aa8@haiku-os.org> Message-ID: <051.7831f095cb120caddfc9ca660681d0d1@haiku-os.org> #2642: bfs: mkdir creates invalid directory ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Replying to [comment:1 axeld]: > This sounds very much like you get beyond B_PATH_NAME_LENGTH; it will cut the path after 1024 bytes, and therefore isn't able to create the directory with the name you intended. > If so, it should be handled differently, as in linux I get an path name too long or alike. > What exactly happens? Have you tried to manually enter the deepest level to see how it looks like? Yes I did. I get a no such file or directory. Actually, now that I think of, it shoulnd't be the B_PATH_NAME_LENGHT, because I always use the relative path, not the absolute. With the script, I create the directory and cd'in right away, then create another one, cd'in and so on. Thus the name is at most always 4 bytes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 14:20:31 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 12:20:31 -0000 Subject: [Haiku-bugs] [Haiku] #1951: Tracker Crashes on replicant drag from Pulse to desktop In-Reply-To: <043.0b669dc478b15c06168feedb35872480@haiku-os.org> References: <043.0b669dc478b15c06168feedb35872480@haiku-os.org> Message-ID: <052.97ddeaaa18555317e572772f776acf71@haiku-os.org> #1951: Tracker Crashes on replicant drag from Pulse to desktop -----------------------------------+---------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Can't reproduce here, but looking at the backtrace, this could happen if the label of the button was null because it wasn't properly set/archived... Oh, just found something! It has surely been fixed by this: http://dev .haiku-os.org/ticket/2097 closing... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 14:45:21 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 12:45:21 -0000 Subject: [Haiku-bugs] [Haiku] #2639: [usb_disk]: unable to mount In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.94c14d7fdd5b8a01759362a710efdf4b@haiku-os.org> #2639: [usb_disk]: unable to mount ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by aldeck): Yep, have had problems with a FAT usb disk since a few (~hundreds) revisions. The disk was mountable, but the content was empty, after unmounting i couldn't mount it again. It has even regressed a little more since a few revisions, now clicking on the disk icon makes it disapear and unmount immediately. After that the disk isn't available for mounting. See the attached serial log. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:31:24 2008 From: trac at haiku-os.org (xspager) Date: Tue, 19 Aug 2008 13:31:24 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error Message-ID: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> #2647: runtime_loader error -----------------------------------+---------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Blockedby: | Platform: x64 Blocking: | -----------------------------------+---------------------------------------- I got this errot in runtime loader, calling a program compiled by me: ~/src/VisualBoyAdvance-1.7.2/src/sdl> ./VisualBoyAdvance[[br]] runtime_loader: unhandled pheader type 0x68003300[[br]] runtime_loader: Troubles parsing Program headers, numRegions = -2147483632 i had a lot of trouble to get VisualBoyAdvande to compile, but the link process don't emit any warning, so i suppose that the binnary is ok. As sugested by DeadYak i put here the output of objdump -x VisualBoyAdvance VisualBoyAdvance: file format elf32-i386 VisualBoyAdvance architecture: i386, flags 0x00000150: HAS_SYMS, DYNAMIC, D_PAGED start address 0x000128d4 Program Header: LOAD off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 2**12 filesz 0x000f5684 memsz 0x000f5684 flags r-x LOAD off 0x000f5684 vaddr 0x000f6684 paddr 0x000f6684 align 2**12 filesz 0x0000701c memsz 0x0010999c flags rw- DYNAMIC off 0x000f6f60 vaddr 0x000f7f60 paddr 0x000f7f60 align 2**2 filesz 0x00000100 memsz 0x00000100 flags rw- Dynamic Section: NEEDED libSDL.so NEEDED libpng.so NEEDED libgame.so NEEDED libmedia.so NEEDED libGL.so NEEDED libbe.so NEEDED libdevice.so NEEDED libtextencoding.so NEEDED libz.so NEEDED libnetwork.so NEEDED libroot.so SYMBOLIC 0x0 INIT 0x1204c FINI 0xedb10 HASH 0x94 STRTAB 0x81c4 SYMTAB 0x2754 STRSZ 0x6217 SYMENT 0x10 PLTGOT 0xf8060 PLTRELSZ 0x3c0 PLTREL 0x11 JMPREL 0x11c8c REL 0xe3dc RELSZ 0x38b0 RELENT 0x8 RELCOUNT 0x70c Sections: Idx Name Size VMA LMA File off Algn 0 .hash 000026c0 00000094 00000094 00000094 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .dynsym 00005a70 00002754 00002754 00002754 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .dynstr 00006217 000081c4 000081c4 000081c4 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .rel.dyn 000038b0 0000e3dc 0000e3dc 0000e3dc 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .rel.plt 000003c0 00011c8c 00011c8c 00011c8c 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 5 .init 0000001e 0001204c 0001204c 0001204c 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE 6 .plt 00000790 0001206c 0001206c 0001206c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 7 .text 000db310 00012800 00012800 00012800 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE 8 .fini 00000019 000edb10 000edb10 000edb10 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE 9 .rodata 00007b44 000edb40 000edb40 000edb40 2**5 CONTENTS, ALLOC, LOAD, READONLY, DATA 10 .eh_frame 000018c4 000f6684 000f6684 000f5684 2**2 CONTENTS, ALLOC, LOAD, DATA 11 .ctors 00000010 000f7f48 000f7f48 000f6f48 2**2 CONTENTS, ALLOC, LOAD, DATA 12 .dtors 00000008 000f7f58 000f7f58 000f6f58 2**2 CONTENTS, ALLOC, LOAD, DATA 13 .dynamic 00000100 000f7f60 000f7f60 000f6f60 2**2 CONTENTS, ALLOC, LOAD, DATA 14 .got 00000d8c 000f8060 000f8060 000f7060 2**2 CONTENTS, ALLOC, LOAD, DATA 15 .data 000048a0 000f8e00 000f8e00 000f7e00 2**5 CONTENTS, ALLOC, LOAD, DATA 16 .bss 00102980 000fd6a0 000fd6a0 000fc6a0 2**5 ALLOC 17 .comment 000006c0 00000000 00000000 000fc6a0 2**0 CONTENTS, READONLY 18 .debug_aranges 00000060 00000000 00000000 000fcd60 2**0 CONTENTS, READONLY, DEBUGGING 19 .debug_pubnames 00000106 00000000 00000000 000fcdc0 2**0 CONTENTS, READONLY, DEBUGGING 20 .debug_info 00002e0d 00000000 00000000 000fcec6 2**0 CONTENTS, READONLY, DEBUGGING 21 .debug_abbrev 0000044c 00000000 00000000 000ffcd3 2**0 CONTENTS, READONLY, DEBUGGING 22 .debug_line 00001932 00000000 00000000 0010011f 2**0 CONTENTS, READONLY, DEBUGGING -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:33:31 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 19 Aug 2008 13:33:31 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.900383deecdc5197ca05846f923c4ba8@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Changes (by anevilyak): * platform: x64 => x86 Comment: Update platform, we don't have an x64 rev at the moment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:41:36 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 19 Aug 2008 13:41:36 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.3ce096251053da8a49be7facfd640024@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Old description: > I got this errot in runtime loader, calling a program compiled by me: > > ~/src/VisualBoyAdvance-1.7.2/src/sdl> ./VisualBoyAdvance[[br]] > runtime_loader: unhandled pheader type 0x68003300[[br]] > runtime_loader: Troubles parsing Program headers, numRegions = > -2147483632 > > i had a lot of trouble to get VisualBoyAdvande to compile, but the link > process don't emit any warning, so i suppose that the binnary is ok. As > sugested by DeadYak i put here the output of > > objdump -x VisualBoyAdvance > > VisualBoyAdvance: file format elf32-i386 > VisualBoyAdvance > architecture: i386, flags 0x00000150: > HAS_SYMS, DYNAMIC, D_PAGED > start address 0x000128d4 > > Program Header: > LOAD off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 2**12 > filesz 0x000f5684 memsz 0x000f5684 flags r-x > LOAD off 0x000f5684 vaddr 0x000f6684 paddr 0x000f6684 align 2**12 > filesz 0x0000701c memsz 0x0010999c flags rw- > DYNAMIC off 0x000f6f60 vaddr 0x000f7f60 paddr 0x000f7f60 align 2**2 > filesz 0x00000100 memsz 0x00000100 flags rw- > > Dynamic Section: > NEEDED libSDL.so > NEEDED libpng.so > NEEDED libgame.so > NEEDED libmedia.so > NEEDED libGL.so > NEEDED libbe.so > NEEDED libdevice.so > NEEDED libtextencoding.so > NEEDED libz.so > NEEDED libnetwork.so > NEEDED libroot.so > SYMBOLIC 0x0 > INIT 0x1204c > FINI 0xedb10 > HASH 0x94 > STRTAB 0x81c4 > SYMTAB 0x2754 > STRSZ 0x6217 > SYMENT 0x10 > PLTGOT 0xf8060 > PLTRELSZ 0x3c0 > PLTREL 0x11 > JMPREL 0x11c8c > REL 0xe3dc > RELSZ 0x38b0 > RELENT 0x8 > RELCOUNT 0x70c > > Sections: > Idx Name Size VMA LMA File off Algn > 0 .hash 000026c0 00000094 00000094 00000094 2**2 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 1 .dynsym 00005a70 00002754 00002754 00002754 2**2 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 2 .dynstr 00006217 000081c4 000081c4 000081c4 2**0 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 3 .rel.dyn 000038b0 0000e3dc 0000e3dc 0000e3dc 2**2 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 4 .rel.plt 000003c0 00011c8c 00011c8c 00011c8c 2**2 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 5 .init 0000001e 0001204c 0001204c 0001204c 2**0 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 6 .plt 00000790 0001206c 0001206c 0001206c 2**2 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 7 .text 000db310 00012800 00012800 00012800 2**4 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 8 .fini 00000019 000edb10 000edb10 000edb10 2**0 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 9 .rodata 00007b44 000edb40 000edb40 000edb40 2**5 > CONTENTS, ALLOC, LOAD, READONLY, DATA > 10 .eh_frame 000018c4 000f6684 000f6684 000f5684 2**2 > CONTENTS, ALLOC, LOAD, DATA > 11 .ctors 00000010 000f7f48 000f7f48 000f6f48 2**2 > CONTENTS, ALLOC, LOAD, DATA > 12 .dtors 00000008 000f7f58 000f7f58 000f6f58 2**2 > CONTENTS, ALLOC, LOAD, DATA > 13 .dynamic 00000100 000f7f60 000f7f60 000f6f60 2**2 > CONTENTS, ALLOC, LOAD, DATA > 14 .got 00000d8c 000f8060 000f8060 000f7060 2**2 > CONTENTS, ALLOC, LOAD, DATA > 15 .data 000048a0 000f8e00 000f8e00 000f7e00 2**5 > CONTENTS, ALLOC, LOAD, DATA > 16 .bss 00102980 000fd6a0 000fd6a0 000fc6a0 2**5 > ALLOC > 17 .comment 000006c0 00000000 00000000 000fc6a0 2**0 > CONTENTS, READONLY > 18 .debug_aranges 00000060 00000000 00000000 000fcd60 2**0 > CONTENTS, READONLY, DEBUGGING > 19 .debug_pubnames 00000106 00000000 00000000 000fcdc0 2**0 > CONTENTS, READONLY, DEBUGGING > 20 .debug_info 00002e0d 00000000 00000000 000fcec6 2**0 > CONTENTS, READONLY, DEBUGGING > 21 .debug_abbrev 0000044c 00000000 00000000 000ffcd3 2**0 > CONTENTS, READONLY, DEBUGGING > 22 .debug_line 00001932 00000000 00000000 0010011f 2**0 > CONTENTS, READONLY, DEBUGGING New description: I got this errot in runtime loader, calling a program compiled by me: {{{ ~/src/VisualBoyAdvance-1.7.2/src/sdl> ./VisualBoyAdvance runtime_loader: unhandled pheader type 0x68003300 runtime_loader: Troubles parsing Program headers, numRegions = -2147483632 }}} i had a lot of trouble to get VisualBoyAdvande to compile, but the link process don't emit any warning, so i suppose that the binnary is ok. As sugested by DeadYak i put here the output of {{{ objdump -x VisualBoyAdvance }}} {{{ VisualBoyAdvance: file format elf32-i386 VisualBoyAdvance architecture: i386, flags 0x00000150: HAS_SYMS, DYNAMIC, D_PAGED start address 0x000128d4 Program Header: LOAD off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 2**12 filesz 0x000f5684 memsz 0x000f5684 flags r-x LOAD off 0x000f5684 vaddr 0x000f6684 paddr 0x000f6684 align 2**12 filesz 0x0000701c memsz 0x0010999c flags rw- DYNAMIC off 0x000f6f60 vaddr 0x000f7f60 paddr 0x000f7f60 align 2**2 filesz 0x00000100 memsz 0x00000100 flags rw- Dynamic Section: NEEDED libSDL.so NEEDED libpng.so NEEDED libgame.so NEEDED libmedia.so NEEDED libGL.so NEEDED libbe.so NEEDED libdevice.so NEEDED libtextencoding.so NEEDED libz.so NEEDED libnetwork.so NEEDED libroot.so SYMBOLIC 0x0 INIT 0x1204c FINI 0xedb10 HASH 0x94 STRTAB 0x81c4 SYMTAB 0x2754 STRSZ 0x6217 SYMENT 0x10 PLTGOT 0xf8060 PLTRELSZ 0x3c0 PLTREL 0x11 JMPREL 0x11c8c REL 0xe3dc RELSZ 0x38b0 RELENT 0x8 RELCOUNT 0x70c Sections: Idx Name Size VMA LMA File off Algn 0 .hash 000026c0 00000094 00000094 00000094 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .dynsym 00005a70 00002754 00002754 00002754 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .dynstr 00006217 000081c4 000081c4 000081c4 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .rel.dyn 000038b0 0000e3dc 0000e3dc 0000e3dc 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .rel.plt 000003c0 00011c8c 00011c8c 00011c8c 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 5 .init 0000001e 0001204c 0001204c 0001204c 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE 6 .plt 00000790 0001206c 0001206c 0001206c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 7 .text 000db310 00012800 00012800 00012800 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE 8 .fini 00000019 000edb10 000edb10 000edb10 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE 9 .rodata 00007b44 000edb40 000edb40 000edb40 2**5 CONTENTS, ALLOC, LOAD, READONLY, DATA 10 .eh_frame 000018c4 000f6684 000f6684 000f5684 2**2 CONTENTS, ALLOC, LOAD, DATA 11 .ctors 00000010 000f7f48 000f7f48 000f6f48 2**2 CONTENTS, ALLOC, LOAD, DATA 12 .dtors 00000008 000f7f58 000f7f58 000f6f58 2**2 CONTENTS, ALLOC, LOAD, DATA 13 .dynamic 00000100 000f7f60 000f7f60 000f6f60 2**2 CONTENTS, ALLOC, LOAD, DATA 14 .got 00000d8c 000f8060 000f8060 000f7060 2**2 CONTENTS, ALLOC, LOAD, DATA 15 .data 000048a0 000f8e00 000f8e00 000f7e00 2**5 CONTENTS, ALLOC, LOAD, DATA 16 .bss 00102980 000fd6a0 000fd6a0 000fc6a0 2**5 ALLOC 17 .comment 000006c0 00000000 00000000 000fc6a0 2**0 CONTENTS, READONLY 18 .debug_aranges 00000060 00000000 00000000 000fcd60 2**0 CONTENTS, READONLY, DEBUGGING 19 .debug_pubnames 00000106 00000000 00000000 000fcdc0 2**0 CONTENTS, READONLY, DEBUGGING 20 .debug_info 00002e0d 00000000 00000000 000fcec6 2**0 CONTENTS, READONLY, DEBUGGING 21 .debug_abbrev 0000044c 00000000 00000000 000ffcd3 2**0 CONTENTS, READONLY, DEBUGGING 22 .debug_line 00001932 00000000 00000000 0010011f 2**0 CONTENTS, READONLY, DEBUGGING }}} -- Comment(by mmlr): How did you compile the binary? What compiler were you using? When you say you had a lot of trouble compiling, what kind of trouble do you mean? This rather looks like an incorrectly built binary and not like a runtime loader issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:49:42 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 19 Aug 2008 13:49:42 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.4fafe15bac564e326e920536b19917a7@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by anevilyak): That's why I had him objdump it, I would've assumed if it was incorrectly built somehow then objdump would've complained also, but it seems to have parsed all the program headers without any problems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:53:06 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 19 Aug 2008 13:53:06 -0000 Subject: [Haiku-bugs] [Haiku] #2637: [PATCH] Signal tests do not compile with gcc4 In-Reply-To: <043.6e60b69ac343e5f85d95dad042109e5f@haiku-os.org> References: <043.6e60b69ac343e5f85d95dad042109e5f@haiku-os.org> Message-ID: <052.ebfb85f798e3727e7b997934e9ca630e@haiku-os.org> #2637: [PATCH] Signal tests do not compile with gcc4 --------------------------------+------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r27061 and r27062. I also fixed a couple of other tests. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:55:08 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 13:55:08 -0000 Subject: [Haiku-bugs] [Haiku] #2410: [Tracker] navigation arrows are always active In-Reply-To: <040.c0e33242e512b5a6787d6928174e93dd@haiku-os.org> References: <040.c0e33242e512b5a6787d6928174e93dd@haiku-os.org> Message-ID: <049.bf361c7bda64bff289c0112333945cc1@haiku-os.org> #2410: [Tracker] navigation arrows are always active -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Fixed in r27063 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 15:58:10 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 13:58:10 -0000 Subject: [Haiku-bugs] [Haiku] #353: [Tracker] crash after several fast right clicks on trash icon In-Reply-To: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> References: <040.ec6142bf5502705bc98578da3c1b75c4@haiku-os.org> Message-ID: <049.5b28294a532266c3e404bc0d65ee4e78@haiku-os.org> #353: [Tracker] crash after several fast right clicks on trash icon -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Replying to [comment:20 anevilyak]: > Was that R5 with the stock Tracker or with OpenTracker? Thats opentracker for sure, i don't know how to find the version though.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:05:45 2008 From: trac at haiku-os.org (bga) Date: Tue, 19 Aug 2008 14:05:45 -0000 Subject: [Haiku-bugs] [Haiku] #2648: Using TAB to switch fields should ignore disabled fields. Message-ID: <038.f62fd7278258c71267aaacc318962c09@haiku-os.org> #2648: Using TAB to switch fields should ignore disabled fields. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- When using TAB to switch fields, disabled fields are being taken into account and switched to. I don't remember how it was in R5, but considering the user can not do anything in a disabled field, they should probably be ignored. As an example, check the E-mail preferences app. When creating an account including an outbound chain, when configuring the outbound chain the fields username/password are disabled unless ESMTP is set but using TAB will switch to those fields. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:06:56 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 19 Aug 2008 14:06:56 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.2e4de61dea8f2744d9bffe79f4f33db2@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by mmlr): That depends. The problem reported is that a certain program header was not understood (the negative value there translates to B_BAD_DATA and is returned in that case). So it is possible that there is a header that our runtime_loader doesn't support but objdump does. That's why I ask about the compiler version, as using our standard compilers this shouldn't happen. Checking elf specs the range 0x60000000 to 0x6fffffff where the indicated header (0x68003300) falls into are "reserved for OS specific semantics". So it seems that this is a header that was put there intentionally when generating the binary. Probably this is specific to another OS but was not disabled when compiling for Haiku. Objdump either does not understand and therefore skip it or it ignores it as OS specific. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:15:58 2008 From: trac at haiku-os.org (korli) Date: Tue, 19 Aug 2008 14:15:58 -0000 Subject: [Haiku-bugs] [Haiku] #1223: Media perflet crashed on Intel/Realtek HDA hardware (8086:2668) In-Reply-To: <043.9e4879d6e758234f4e586431bce5f7c9@haiku-os.org> References: <043.9e4879d6e758234f4e586431bce5f7c9@haiku-os.org> Message-ID: <052.e8476465d3f73ab1d071ed6d2e13160c@haiku-os.org> #1223: Media perflet crashed on Intel/Realtek HDA hardware (8086:2668) ----------------------------+----------------------------------------------- Reporter: siarzhuk | Owner: ithamar Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): Could you check please if this bug is still valid as is (does the preflet crash) ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:16:57 2008 From: trac at haiku-os.org (xspager) Date: Tue, 19 Aug 2008 14:16:57 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.f7d6d3bd3934eec01e1865625a0f1396@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by xspager): Replying to [comment:4 mmlr]: > That depends. The problem reported is that a certain program header was not understood (the negative value there translates to B_BAD_DATA and is returned in that case). So it is possible that there is a header that our runtime_loader doesn't support but objdump does. That's why I ask about the compiler version, as using our standard compilers this shouldn't happen. > > Checking elf specs the range 0x60000000 to 0x6fffffff where the indicated header (0x68003300) falls into are "reserved for OS specific semantics". So it seems that this is a header that was put there intentionally when generating the binary. Probably this is specific to another OS but was not disabled when compiling for Haiku. Objdump either does not understand and therefore skip it or it ignores it as OS specific. mmlr, i use the default that is installed by the haiku build process (gcc version 2.95.3-haiku-080323) i build the VisualBoyAdvance-1.7.2 using: {{{ CXXFLAGS='-O0 -lnetwork' ./configure --build=i586-pc-beos --enable-c-core --without-mmx --disable-rpath --disable-sdltest --disable-profilings make }}} i also build pkg-config and SDL myself, but i don't know if has something to do with -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:25:24 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 14:25:24 -0000 Subject: [Haiku-bugs] [Haiku] #2442: [Tracker]: it should not be possible to create a directory in / In-Reply-To: <042.a70ecd44fb82554b699b8220b1d4325b@haiku-os.org> References: <042.a70ecd44fb82554b699b8220b1d4325b@haiku-os.org> Message-ID: <051.383dcdc73ba5ae7db3a4e95f01aab196@haiku-os.org> #2442: [Tracker]: it should not be possible to create a directory in / -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): So to summarize what we should/could do: Issue1: Fix1: Disable the "new..." menu item and Command+N when in Disks. Fix2: Show an alert with "You cannot (/are not allowed to) create a folder/file here..." Issue2: Fix "open parent" so that it works just like the Up navigator arrow. Issue3: Dropping a file/folder in the Disks "folder" gives a "Not enough space" alert, the message could be more specific, like in Issue1/Fix2. Right? I'd personnaly go with Fix2 for the Issue1. What do you think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:41:17 2008 From: trac at haiku-os.org (korli) Date: Tue, 19 Aug 2008 14:41:17 -0000 Subject: [Haiku-bugs] [Haiku] #1856: Port UDF file system to Haiku FS API In-Reply-To: <040.cf5ef7891b86bfbc7ad92095308544fb@haiku-os.org> References: <040.cf5ef7891b86bfbc7ad92095308544fb@haiku-os.org> Message-ID: <049.f7d5365d7ab04ad67054416d94f816b0@haiku-os.org> #1856: Port UDF file system to Haiku FS API -------------------------------+-------------------------------------------- Reporter: korli | Owner: emitrax Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/UDF | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by korli): * owner: => emitrax -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:43:08 2008 From: trac at haiku-os.org (korli) Date: Tue, 19 Aug 2008 14:43:08 -0000 Subject: [Haiku-bugs] [Haiku] #1873: GLTeapot causes system hang on real hardware In-Reply-To: <042.63ffd726eafcd3fae4f92ead4ae12027@haiku-os.org> References: <042.63ffd726eafcd3fae4f92ead4ae12027@haiku-os.org> Message-ID: <051.7db81326931c6ca334f38cb8d02e412c@haiku-os.org> #1873: GLTeapot causes system hang on real hardware ---------------------------+------------------------------------------------ Reporter: qyellow | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:46:39 2008 From: trac at haiku-os.org (korli) Date: Tue, 19 Aug 2008 14:46:39 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.8117d5fa5fb6236fe95eda8c44b1abdb@haiku-os.org> #1910: Page fault with hda --------------------------------+------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by korli): Does it still crash ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 16:58:55 2008 From: trac at haiku-os.org (korli) Date: Tue, 19 Aug 2008 14:58:55 -0000 Subject: [Haiku-bugs] [Haiku] #2283: less needs updating (easy) In-Reply-To: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> References: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> Message-ID: <051.d68cc73d3ec976759241824fd35eed40@haiku-os.org> #2283: less needs updating (easy) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by korli): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 18:38:22 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 16:38:22 -0000 Subject: [Haiku-bugs] [Haiku] #2442: [Tracker]: it should not be possible to create a directory in / In-Reply-To: <042.a70ecd44fb82554b699b8220b1d4325b@haiku-os.org> References: <042.a70ecd44fb82554b699b8220b1d4325b@haiku-os.org> Message-ID: <051.afa80c8c6886a1c9b95f054e733a8a08@haiku-os.org> #2442: [Tracker]: it should not be possible to create a directory in / -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): I would do a mix: remove the "new" menu item, but show the alert when the user presses Command-N. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 19:52:14 2008 From: trac at haiku-os.org (xspager) Date: Tue, 19 Aug 2008 17:52:14 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.6d77eeec8d0a7a6d477011bd21815bbe@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by xspager): Replying to [comment:6 axeld]: > Can you provide the executable, or a link to it? (upload limit is 500K) yes -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 20:37:58 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 19 Aug 2008 18:37:58 -0000 Subject: [Haiku-bugs] [Haiku] #1489: Add Icon in File Type gives General system error in Icon-O-Matic In-Reply-To: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> References: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> Message-ID: <051.e02ca2afec5c91aa48ff3a430e0b42a3@haiku-os.org> #1489: Add Icon in File Type gives General system error in Icon-O-Matic ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Comment(by scottmc): Did this just get fixed, or is there still more to happen? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 20:44:47 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 19 Aug 2008 18:44:47 -0000 Subject: [Haiku-bugs] [Haiku] #1868: Icon changing using the File Type Icon drop doesn't update in dialog box In-Reply-To: <042.845f1057073c3c71af3588341d9fa6e3@haiku-os.org> References: <042.845f1057073c3c71af3588341d9fa6e3@haiku-os.org> Message-ID: <051.e23918243f50b79ff61450614c2b779b@haiku-os.org> #1868: Icon changing using the File Type Icon drop doesn't update in dialog box ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/FileTypes | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): This seems to have changed on recent builds? Now if I try dropping a different icon for a file it updates the files icon right away, but the icon drop box instead of not updating the icon box is it just left empty. I'd expect to see the new icon there. I only have a single volume here so I wasn't able to check to see if non-boot volume icons are still acting as they were when this ticket was filed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 21:05:04 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 19 Aug 2008 19:05:04 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.c51701779beb353b8592e8ebeb6649d7@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): If you need libsdl and pkg-config to test this out there's binaries of each posted at: http://ports.haiku-files.org/downloads -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 22:08:29 2008 From: trac at haiku-os.org (mmu_man) Date: Tue, 19 Aug 2008 20:08:29 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix & bsd license headers In-Reply-To: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> References: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> Message-ID: <050.2d8fdf4d5faeb213863861b499e4ed48@haiku-os.org> #2191: Updated posix & bsd license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmu_man): Actually, the licence name also should be fixed. I discussed this with Richard M Stallman at RMLL, and as he said, "MIT Licence" is misleading. See: http://www.gnu.org/licenses/license-list.html#X11License We should really check this, decide which we use, either X11 or BSD- revised, and use the correct name. Hmm that should likely be a separate ticket I suppose. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 23:08:17 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 19 Aug 2008 21:08:17 -0000 Subject: [Haiku-bugs] [Haiku] #2649: Licence name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.ce8bde26b8a8d8097f69b1deca1acdca@haiku-os.org> #2649: Licence name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Axel recently changed my "MIT/X11" to "MIT", saying it was redundant. My view is that [http://en.wikipedia.org/wiki/MIT MIT| is an institution, so it is as accurate as saying FSF license (instead of GPLv2, ...). I guess that's what the GNU link above is trying to say. The OSI lists it as [http://www.opensource.org/licenses/mit-license.php MIT License] though, so it can't be totally wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 23:37:40 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 19 Aug 2008 21:37:40 -0000 Subject: [Haiku-bugs] [Haiku] #2644: Panic on Scheduler::_Finisher In-Reply-To: <042.dd1510cedfb1e76e3c5d793ae3673b8a@haiku-os.org> References: <042.dd1510cedfb1e76e3c5d793ae3673b8a@haiku-os.org> Message-ID: <051.7d932bffc9a16a2ff24b72d5b044a38f@haiku-os.org> #2644: Panic on Scheduler::_Finisher ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r27070. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 23:42:48 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 19 Aug 2008 21:42:48 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.9f71f64880b864cc6ad562fbeee66c79@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by andreasf): I don't remember seeing recent commits in this area, so what seemed to do the trick for me was to set the timezone in {{{UserBuildConfig}}} (Europe/Paris in my case). Haiku's clock is off by two hours then, as before. But if I choose GMT in Haiku's time settings, I get the correct time now. Five months ago, choosing that option changed it to something odd. Is there a settings file or Jam rule to automate setting the display to GMT? In QEMU using {{{-localtime}}} is an easy option, but on a real machine the clock offset can easily get one's biorhythm shifted... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 23:44:00 2008 From: trac at haiku-os.org (stippi) Date: Tue, 19 Aug 2008 21:44:00 -0000 Subject: [Haiku-bugs] [Haiku] #1489: Add Icon in File Type gives General system error in Icon-O-Matic In-Reply-To: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> References: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> Message-ID: <051.33b959cd2b8968a71d30b408fa85d4fd@haiku-os.org> #1489: Add Icon in File Type gives General system error in Icon-O-Matic ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Oh yeah, thanks a lot for helping me stay on top of trac! Really. Fixed in r27065. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 23:53:35 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 19 Aug 2008 21:53:35 -0000 Subject: [Haiku-bugs] [Haiku] #2649: Licence name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.cd0063afcc4c35dbc49114286f023444@haiku-os.org> #2649: Licence name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Wikipedia knows the term [http://en.wikipedia.org/wiki/MIT_license MIT license], too. Given the name of our OS, it would be consequent to switch to the basically equivalent [http://en.wikipedia.org/wiki/Poetic_License Poetic License], BTW. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 00:11:54 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 19 Aug 2008 22:11:54 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.791ac86cb1ae804560c9d5244b75c69f@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by anevilyak): That's determined by ~/config/settings/RTC_time_settings as on R5. Writing the value 'gmt' to that file suffices. It's one of several things I include in a zip full of pre-configured settings files I have in my UserBuildConfig. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 00:33:47 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 22:33:47 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.9a8869cb65ad8172c9d830630bcc091a@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by aldeck): You must not trust Menu preflet when it says you are in CTRL mode. It only compares key codes of the left command key and the right command key, and theres a bug in the keymaps (most non english). I'll fix the keymaps shortly. Concerning the Italian keymap, i could produce the @ symbol, the problem is that ALT-GR becomes RightControl when you're in ALT mode, sure looks odd, but let's keep that for another ticket :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 03:24:01 2008 From: trac at haiku-os.org (koki) Date: Wed, 20 Aug 2008 01:24:01 -0000 Subject: [Haiku-bugs] [Haiku] #1208: Adding a "Query"-icon (easy) In-Reply-To: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> References: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> Message-ID: <053.f136321f1cdf8bf20be9a7279358df3d@haiku-os.org> #1208: Adding a "Query"-icon (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Mail | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by koki): * cc: kokitomare at gmail.com (added) Comment: Is the queries icon supposed to be present in the Mail app? I ask because I am running r27056 and I don't see it (I do see there is a Queries menu though, though I am not sure if it was there before or not). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 03:37:47 2008 From: trac at haiku-os.org (anxiety) Date: Wed, 20 Aug 2008 01:37:47 -0000 Subject: [Haiku-bugs] [Haiku] #1208: Adding a "Query"-icon (easy) In-Reply-To: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> References: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> Message-ID: <053.e93557a891d26e11e87f2e62069dfa14@haiku-os.org> #1208: Adding a "Query"-icon (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Mail | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anxiety): I don't believe the patch to add the icon to the toolbar has been reviewed and committed yet... you should still be able to access the same functionality through the menu if you're interested. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 03:41:59 2008 From: trac at haiku-os.org (koki) Date: Wed, 20 Aug 2008 01:41:59 -0000 Subject: [Haiku-bugs] [Haiku] #1208: Adding a "Query"-icon (easy) In-Reply-To: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> References: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> Message-ID: <053.a874e5aadcbe6d242e5f31528f504d05@haiku-os.org> #1208: Adding a "Query"-icon (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Mail | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by koki): Replying to [comment:11 anxiety]: > you should still be able to access the same functionality through the menu if you're interested. I just noticed that. However, accessing queries from the Queries menu doesn't work. Is this feature not implemented yet, or is this a bug and should I file a separate bug report in that case? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 03:56:28 2008 From: trac at haiku-os.org (anxiety) Date: Wed, 20 Aug 2008 01:56:28 -0000 Subject: [Haiku-bugs] [Haiku] #1208: Adding a "Query"-icon (easy) In-Reply-To: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> References: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> Message-ID: <053.5aa5431dda8a07fb45c1990ead70e679@haiku-os.org> #1208: Adding a "Query"-icon (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Mail | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anxiety): Replying to [comment:12 koki]: > I just noticed that. However, accessing queries from the Queries menu doesn't work. Is this feature not implemented yet, or is this a bug and should I file a separate bug report in that case? My guess is that, by default, you don't have mail/queries folder and/or any queries in it. This feature still needs to be developed more, such as finishing humdinger's suggestions and creating a few sample queries. Hmm, maybe I have time to do that right now. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 04:02:39 2008 From: trac at haiku-os.org (koki) Date: Wed, 20 Aug 2008 02:02:39 -0000 Subject: [Haiku-bugs] [Haiku] #1208: Adding a "Query"-icon (easy) In-Reply-To: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> References: <044.89fbfd717a67e8f57d61abad1606e34d@haiku-os.org> Message-ID: <053.6e24a5039d87808ffba0bcb6a2b38049@haiku-os.org> #1208: Adding a "Query"-icon (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Mail | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by koki): Replying to [comment:13 anxiety]: > My guess is that, by default, you don't have mail/queries folder and/or any queries in it. I do; I placed an email query (known to run from Tracker) in the... /boot/home/mail/queries ...folder to test this. > This feature still needs to be developed more, such as finishing humdinger's suggestions and creating a few sample queries. Hmm, maybe I have time to do that right now. :) That would be nice. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:18:53 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 19 Aug 2008 11:18:53 -0000 Subject: [Haiku-bugs] [Haiku] #2644: Panic on Scheduler::_Finisher In-Reply-To: <042.dd1510cedfb1e76e3c5d793ae3673b8a@haiku-os.org> References: <042.dd1510cedfb1e76e3c5d793ae3673b8a@haiku-os.org> Message-ID: <051.fdd8448cdc7e52ae80f6860bee931277@haiku-os.org> #2644: Panic on Scheduler::_Finisher ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 14:07:57 2008 From: trac at haiku-os.org (andreasf) Date: Tue, 19 Aug 2008 12:07:57 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read Message-ID: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> #2646: [read] Too much data read ---------------------------------------------+------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ {{{ ls * | (read x && echo $x) }}} outputs the first entry of the first column concatenated by single whitespace with the first entry of the second column. Git expects to only get one file name from `read`. Ingo said this was a problem with Haiku's `read`. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 22:15:13 2008 From: trac at haiku-os.org (mmu_man) Date: Tue, 19 Aug 2008 20:15:13 -0000 Subject: [Haiku-bugs] [Haiku] #2649: Licence name is misleading Message-ID: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> #2649: Licence name is misleading -----------------------+---------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The "MIT" licence does not actually exist. It's a nickname to the X11 licence, which is close to the revised BSD one. But the MIT has used many licences over time. Even though it's a known fact and might legally work, naming which we mean is much better. We should choose either X11 or BSD-revised, and use the correct name everywhere. See http://www.gnu.org/licenses/license-list.html#X11License -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 14:08:51 2008 From: trac at haiku-os.org (xspager) Date: Tue, 19 Aug 2008 12:08:51 -0000 Subject: [Haiku-bugs] [Haiku] #2635: GCC can't allocate more memory: virtual memory exhausted In-Reply-To: <042.5eca8373536526be5cbaefc280fbda40@haiku-os.org> References: <042.5eca8373536526be5cbaefc280fbda40@haiku-os.org> Message-ID: <051.c0f83273515a91868583617ff89c8119@haiku-os.org> #2635: GCC can't allocate more memory: virtual memory exhausted ------------------------+--------------------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x64 | Blocking: ------------------------+--------------------------------------------------- Comment(by xspager): The author of VisualBoyAdvance warns about the gcc and the -O flags on the README. Using -O0 the build of the file GBA.cpp ends without errors. Please close this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:47:21 2008 From: trac at haiku-os.org (cebif) Date: Tue, 19 Aug 2008 11:47:21 -0000 Subject: [Haiku-bugs] [Haiku] #2645: Play any sound with Preferences, Sounds and system freezes Message-ID: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> #2645: Play any sound with Preferences, Sounds and system freezes --------------------------------+------------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Sounds | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I copied some wav sounds into /boot/beos/etc/sounds and playing any one of them with the Sounds application causes my system to freeze. If I play those same sounds using MediaPlayer there is no freeze. I was testing with r27011 on real hardware. The steps to reproduce: 1 put some wav type sound files in the /boot/beos/etc/sounds folder. 2 Open Preferences, Sounds. 3 Select any one of these wav sounds with the Sounds app 4 Click play button The result is the system begins to freeze. It is still possible to move the mouse pointer but cannot use it to activate anything by clicking. The sound plays right to the end properly but then the freeze happens. I also got a stack trace after pressing F12. I will upload that soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 08:48:17 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 20 Aug 2008 06:48:17 -0000 Subject: [Haiku-bugs] [Haiku] #2645: Play any sound with Preferences, Sounds and system freezes In-Reply-To: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> References: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> Message-ID: <049.a82ad401363fdb1ef07ffe7d90386579@haiku-os.org> #2645: Play any sound with Preferences, Sounds and system freezes ---------------------------------+------------------------------------------ Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Sounds | Version: R1 development Resolution: duplicate | Blockedby: 1708 Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 1708 Comment: Duplicate of #1708. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 09:34:48 2008 From: trac at haiku-os.org (stippi) Date: Wed, 20 Aug 2008 07:34:48 -0000 Subject: [Haiku-bugs] [Haiku] #2635: GCC can't allocate more memory: virtual memory exhausted In-Reply-To: <042.5eca8373536526be5cbaefc280fbda40@haiku-os.org> References: <042.5eca8373536526be5cbaefc280fbda40@haiku-os.org> Message-ID: <051.0be1571ce24e7cda271b8f5dfc900db4@haiku-os.org> #2635: GCC can't allocate more memory: virtual memory exhausted ------------------------+--------------------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: x64 | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: Ok, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:48:35 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 08:48:35 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.bbb78378ba96a59c7909db7e3b11a7be@haiku-os.org> #1910: Page fault with hda --------------------------------+------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by PieterPanman): Ah, forgot about this ticket. No it does not crash, I suppose this ticket can be closed. However HDA does not work on my laptop yet. It does show up at the Media panel, but without any controls. I can try to play files, but I get no output. I will move this to #1072. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:50:01 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 08:50:01 -0000 Subject: [Haiku-bugs] [Haiku] #1072: Write an HDA audio driver and add-on In-Reply-To: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> References: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> Message-ID: <049.cd29c87294c88ebb0f4c519fa0bc4edb@haiku-os.org> #1072: Write an HDA audio driver and add-on ----------------------------+----------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by PieterPanman): HDA does not work on my laptop yet. It does show up as recognized at the Media panel, but without any controls on its control page. I can try to play files, but I get no output. Attached the syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:53:23 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 08:53:23 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.156fc29bec5f2b5684918f03752f0fdf@haiku-os.org> #1910: Page fault with hda --------------------------------+------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: I close this bug then. The driver is not finished btw. Also do you have sound with Linux ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:54:51 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 08:54:51 -0000 Subject: [Haiku-bugs] [Haiku] #1072: Write an HDA audio driver and add-on In-Reply-To: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> References: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> Message-ID: <049.dc2a2e75ea225fad6a1a4a1645d50275@haiku-os.org> #1072: Write an HDA audio driver and add-on ----------------------------+----------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by PieterPanman): * cc: pieter at panman.eu (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:56:03 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 08:56:03 -0000 Subject: [Haiku-bugs] [Haiku] #1910: Page fault with hda In-Reply-To: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> References: <044.4be623d20aa6f058c673c3283a04a314@haiku-os.org> Message-ID: <053.be671c78fb4ce9cf886bb0d37525e67b@haiku-os.org> #1910: Page fault with hda --------------------------------+------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by PieterPanman): Yes, and I have had sound with the oss for Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:58:11 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 08:58:11 -0000 Subject: [Haiku-bugs] [Haiku] #1072: Write an HDA audio driver and add-on In-Reply-To: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> References: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> Message-ID: <049.6234b0ba341d11e862d637153c41e2a0@haiku-os.org> #1072: Write an HDA audio driver and add-on ----------------------------+----------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): FWIW I don't have sound either at 192khz/24 bits. I'll probably stick the driver to 48khz/16bits for the time being until fixed. The problem might be related to Haiku media kit/addons. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 10:59:17 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 08:59:17 -0000 Subject: [Haiku-bugs] [Haiku] #2639: unable to mount ext3 partition with usb_disk In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.bcd6de4ddce851066572d697829dcdc2@haiku-os.org> #2639: unable to mount ext3 partition with usb_disk --------------------------------+------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ext2 | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by PieterPanman): My Fat stick does mount, but appears empty. Same ioctl output in syslog. Latest revision. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 11:00:54 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 20 Aug 2008 09:00:54 -0000 Subject: [Haiku-bugs] [Haiku] #1072: Write an HDA audio driver and add-on In-Reply-To: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> References: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> Message-ID: <049.4e5e3ee1bbd561917e48a79ab2aa0e62@haiku-os.org> #1072: Write an HDA audio driver and add-on ----------------------------+----------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by PieterPanman): Thanks, when something might work again, let me know I'll try it. I can also test things if you need. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 11:03:22 2008 From: trac at haiku-os.org (siarzhuk) Date: Wed, 20 Aug 2008 09:03:22 -0000 Subject: [Haiku-bugs] [Haiku] #1223: Media perflet crashed on Intel/Realtek HDA hardware (8086:2668) In-Reply-To: <043.9e4879d6e758234f4e586431bce5f7c9@haiku-os.org> References: <043.9e4879d6e758234f4e586431bce5f7c9@haiku-os.org> Message-ID: <052.986522deb6dc38f4442f751975935a72@haiku-os.org> #1223: Media perflet crashed on Intel/Realtek HDA hardware (8086:2668) ----------------------------+----------------------------------------------- Reporter: siarzhuk | Owner: ithamar Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by siarzhuk): * status: assigned => closed * resolution: => fixed Comment: No crashes more. But no sound too from my Realtek hardware. ;-) And it is hang my system on start. I'll investigate it and notify the Trac later. This one can be close, I think. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:39:22 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 11:39:22 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.4940dbb2a443f03fe322e9b25f702428@haiku-os.org> #2641: [nvidia] Video problems --------------------------------------+------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 17:04:33 2008 From: trac at haiku-os.org (bga) Date: Tue, 19 Aug 2008 15:04:33 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.d607433b26b26ededc11a0b1beea4a74@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): Forget the last comment about the name and size index, as the name index includes directories while the size index does not. This does not change the problem, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 12:21:25 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 20 Aug 2008 10:21:25 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.3cf9cd40e4543010f31aa6004ef9de1b@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by emitrax): Any chance this can be related to our bash version? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 12:24:22 2008 From: trac at haiku-os.org (cebif) Date: Wed, 20 Aug 2008 10:24:22 -0000 Subject: [Haiku-bugs] [Haiku] #2645: Play any sound with Preferences, Sounds and system freezes In-Reply-To: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> References: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> Message-ID: <049.d5a6154afce556927e98b5f4fb6c732b@haiku-os.org> #2645: Play any sound with Preferences, Sounds and system freezes ---------------------------------+------------------------------------------ Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Sounds | Version: R1 development Resolution: duplicate | Blockedby: 1708 Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by cebif): Replying to [comment:1 mmlr]: > Duplicate of #1708. With bug #1708 aiff type sounds are been used. Preferences, Sounds was able to play wav typs before but not when I tested with r20711. The bug is different in this respect unless wav files were also tested in #1708. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 13:16:20 2008 From: trac at haiku-os.org (farvardin) Date: Wed, 20 Aug 2008 11:16:20 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.61eb7bfb431c88e3035c0b5cfad51321@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by farvardin): * cc: eforgeot at yahoo.fr (added) * platform: All => x86 Comment: I've copied the latest nightly build (19 Aug. 2008) to a SD card (using dd). It starts booting haiku, but at the end of the booting process, there is a kernel panic. Probably this is related to the USB support of haiku, but it would be nice to be able to boot haiku this way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 18:10:55 2008 From: trac at haiku-os.org (axeld) Date: Tue, 19 Aug 2008 16:10:55 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.c2cec4dc1d5b94bd81f6800fa8190b42@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by axeld): Can you provide the executable, or a link to it? (upload limit is 500K) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 20:12:05 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 19 Aug 2008 18:12:05 -0000 Subject: [Haiku-bugs] [Haiku] #2639: unable to mount ext3 partition with usb_disk (was: [usb_disk]: unable to mount) In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.e9718d9d5ce37476c4c0913bbecac958@haiku-os.org> #2639: unable to mount ext3 partition with usb_disk --------------------------------+------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ext2 | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by emitrax): * component: - General => File Systems/ext2 Comment: Actually, it does mount another stick with a fat partition. The one that does not mount has an ext3 partition, which, IIRC, did mount previously. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:40:05 2008 From: trac at haiku-os.org (aldeck) Date: Tue, 19 Aug 2008 11:40:05 -0000 Subject: [Haiku-bugs] [Haiku] #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders In-Reply-To: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> References: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> Message-ID: <051.5c3269bf2646576124475db840af8941@haiku-os.org> #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): I'd call that one a bug! At least it will be a bad joke for most users :) I mean, 99% of the time you want the folders to merge, i don't really see why replacing is the default. Also it would be more consistent with other operating systems. And guys, it's even the first issue addressed by Sikosis's Haiku Tips, and feels really embarassing (see Haiku Down Under video at the end) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 13:51:02 2008 From: trac at haiku-os.org (tqh) Date: Wed, 20 Aug 2008 11:51:02 -0000 Subject: [Haiku-bugs] [Haiku] #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) Message-ID: <038.cc379f3e9fd1a7d907414312c6418dc4@haiku-os.org> #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) --------------------------------------------+------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------------+------------------------------- New laptop with Intel GM965 crashes on boot in Painter::FillRectNoClipping. Booting with Vesa fallback works as expected. Backtrace attached. This is a gcc4 build (from yesterday). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 13:53:33 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 20 Aug 2008 11:53:33 -0000 Subject: [Haiku-bugs] [Haiku] #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) In-Reply-To: <038.cc379f3e9fd1a7d907414312c6418dc4@haiku-os.org> References: <038.cc379f3e9fd1a7d907414312c6418dc4@haiku-os.org> Message-ID: <047.2a528efb74a93b3daa4b845010690e85@haiku-os.org> #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) ---------------------------------------------+------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: duplicate | Blockedby: 2350 Platform: All | Blocking: ---------------------------------------------+------------------------------ Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 2350 Comment: Another duplicate of #2350. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 16:33:23 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 20 Aug 2008 14:33:23 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.9cefc68c5c1f85141a6fb83a47df9c7b@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by andreasf): Possibly. We have GNU bash 2.05b.0(1) whereas some other OSes have 3.2.x. I also noticed our `bash --version` says {{{i586-pc-beos}}}, not {{{i586 -pc-haiku}}}. No idea if it's easy to upgrade. I had checked our bash's {{{read.def}}} but didn't spot anything obvious. Due to some comments in the code I checked whether `ls * | (read && echo $REPLY)` is any better, but it wasn't. I noticed that in the home directory it's different for directories, in {{{/boot/home/config}}} I get {{{Desktop:}}} despite the second column reading {{{apr-util}}}. So maybe the string is just not correctly terminated? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 16:39:35 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 20 Aug 2008 14:39:35 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.d11927302237ec2fca031ce452f640f2@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by anevilyak): I noticed some other anomalies with our bash that may or may not be related...tab-completion of a relative path is broken, it completes the directory name and then puts a space (i.e. if I want to tab complete the path to an executable to run it).. it works correctly if you're tab completing after having typed cd first though, oddly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 16:44:43 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 20 Aug 2008 14:44:43 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.394105d6409053a0dfba95b21ec92095@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by emitrax): You can try and compile bash-3.2 within haiku and check the output of the above command. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 18:55:06 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 20 Aug 2008 16:55:06 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading (was: Licence name is misleading) In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.fdf2f4423f762df0196b22e351da85d5@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Description changed by mmlr: Old description: > The "MIT" licence does not actually exist. > It's a nickname to the X11 licence, which is close to the revised BSD > one. But the MIT has used many licences over time. Even though it's a > known fact and might legally work, naming which we mean is much better. > We should choose either X11 or BSD-revised, and use the correct name > everywhere. > See http://www.gnu.org/licenses/license-list.html#X11License New description: The "MIT" license does not actually exist. It's a nickname to the X11 license, which is close to the revised BSD one. But the MIT has used many license over time. Even though it's a known fact and might legally work, naming which we mean is much better. We should choose either X11 or BSD-revised, and use the correct name everywhere. See http://www.gnu.org/licenses/license-list.html#X11License -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 19:28:45 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 17:28:45 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.c12728bab51309e3f89ab412ce5c4724@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Fixed in r27086 -- Ticket URL: Haiku The Haiku operating system. From kokitomare at gmail.com Wed Aug 20 20:02:47 2008 From: kokitomare at gmail.com (Jorge Mare) Date: Wed, 20 Aug 2008 11:02:47 -0700 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading (was: Licence name is misleading) In-Reply-To: <051.fdf2f4423f762df0196b22e351da85d5@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> <051.fdf2f4423f762df0196b22e351da85d5@haiku-os.org> Message-ID: On Wed, Aug 20, 2008 at 9:55 AM, mmlr wrote: > #2649: License name is misleading > New description: > > The "MIT" license does not actually exist. > It's a nickname to the X11 license, which is close to the revised BSD one. > But the MIT has used many license over time. Even though it's a known fact > and might legally work, naming which we mean is much better. > We should choose either X11 or BSD-revised, and use the correct name > everywhere. > See http://www.gnu.org/licenses/license-list.html#X11License The OSI seems to disagree: http://www.opensource.org/licenses/mit-license.php Not an expert, but it does seem that it is not that clear cut. When BGA said in our interview with the SCaLE folks back in February that Haiku used a BSD license, I recall Michael Phipps pointing out that it was not BSD but MIT the license that was chosen for Haiku. A quick search of the OpenBeos mailing list archive also reveals at least one message from Phipps that coincides with this: http://www.freelists.org/archives/openbeos/04-2002/msg00342.html I am note advocating one license name over another; but I do think it would be a good idea to (try to) get feedback Michael Phipps on this one, as he (at least) seemed very clear on the choice and he may be able to throw some light into why that choice was made. FWIW. Jorge From trac at haiku-os.org Wed Aug 20 20:18:18 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 18:18:18 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.206e3bb024e63fb455240a8504507629@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by korli): Replying to [comment:6 aldeck]: > Fixed in r27086 Please revert this: with this change I can't use the standard right option key on French keyboards, ie to type the euro symbol. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 20:57:29 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 18:57:29 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.e797579f02e21139b497975a4ea2e0e5@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by aldeck): * status: closed => reopened * resolution: fixed => Comment: Reverted in r27087 Advices welcomed :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:12:48 2008 From: trac at haiku-os.org (stippi) Date: Wed, 20 Aug 2008 19:12:48 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.3314a3b665ad4b00d0b60028b4af0a25@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by stippi): Can't the Menu preflet be fixed to not touch the right side of the keyboard? And then apply the patch to the keymaps with the same change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:15:15 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 20 Aug 2008 19:15:15 -0000 Subject: [Haiku-bugs] [Haiku] #1923: Time Date inaccurate after booting up Haiku In-Reply-To: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> References: <040.8caab11846b17dc28cf60f9f5c70fda6@haiku-os.org> Message-ID: <049.0ec57335b934f0408b75f678f43fb99b@haiku-os.org> #1923: Time Date inaccurate after booting up Haiku --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by andreasf): Thanks, that works great! I suggest we document this in {{{UserBuildConfig.ReadMe}}}. Even better would be if we could have a Jam rule to write that value into the file so that the user does not need to be instructed how to create the file and then to have it added (e.g., {{{SetHaikuImageToUseGMT ;}}}). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:16:55 2008 From: trac at haiku-os.org (j_freeman) Date: Wed, 20 Aug 2008 19:16:55 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup Message-ID: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> #2651: KDL during startup -----------------------+---------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The system goes into KDL just before the processor chip icon illuminates. I'll attach photos of a stack crawl, as well as the last page while on- screen debug output is enabled. The computer is my friend's, so I'm not familiar with the hardware but he says this is it: http://www.tigerdirect.com/applications/SearchTools/item- details.asp?EdpNo=3758921&body=MAIN -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:18:29 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 20 Aug 2008 19:18:29 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.db1ca76f3bc7d29888c389591ae3bc63@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by andreasf): It seems like the menu checks the right-hand key to choose the displayed modifier, so messes it up for those keymaps - if that were the case, we could update it to check the left key instead and leave the keymaps as they are? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:32:42 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 19:32:42 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.6e0be717c4893438675b0b8546202cf7@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by aldeck): Good ideas, let's hope it doesn't break something else :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:50:16 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 20 Aug 2008 19:50:16 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup In-Reply-To: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> References: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> Message-ID: <053.3aafe74edcc298008d1746e4268dc96e@haiku-os.org> #2651: KDL during startup ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Unfortunately KDL does not yet mention the revision... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 22:24:36 2008 From: trac at haiku-os.org (axeld) Date: Wed, 20 Aug 2008 20:24:36 -0000 Subject: [Haiku-bugs] [Haiku] #2639: unable to mount ext3 partition with usb_disk In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.808194a36f6d90d8e830007755b46f5e@haiku-os.org> #2639: unable to mount ext3 partition with usb_disk --------------------------------+------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/ext2 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r27088. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 22:24:59 2008 From: trac at haiku-os.org (axeld) Date: Wed, 20 Aug 2008 20:24:59 -0000 Subject: [Haiku-bugs] [Haiku] #2639: unable to mount ext3 partition with usb_disk In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.65b213cc4e15f1892d0343001609aa46@haiku-os.org> #2639: unable to mount ext3 partition with usb_disk ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => high * component: File Systems/ext2 => System/Kernel * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 22:26:44 2008 From: trac at haiku-os.org (j_freeman) Date: Wed, 20 Aug 2008 20:26:44 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup In-Reply-To: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> References: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> Message-ID: <053.8443f91a64f89e0182ac660b4a6d1bde@haiku-os.org> #2651: KDL during startup ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by j_freeman): Whoops, I suppose that's kinda important. ;) Revision is r27059. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 23:08:01 2008 From: trac at haiku-os.org (axeld) Date: Wed, 20 Aug 2008 21:08:01 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.6ae59eb7e535fe424ecb7f09bdcdcc00@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by axeld): With the archive posted I get a different error, though: {{{ runtime_loader: elf_resolve_symbol: found symbol 'debugger' in shared image but wrong type }}} I used libSDL.so from HaikuPorts above, but also the BeOS one doesn't change this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 23:49:49 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 21:49:49 -0000 Subject: [Haiku-bugs] [Haiku] #2639: unable to mount ext3 partition with usb_disk In-Reply-To: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> References: <042.cc90f6ae325260c0468b67536ba412f8@haiku-os.org> Message-ID: <051.196813b310ca8e1dfa9eed38d7b819eb@haiku-os.org> #2639: unable to mount ext3 partition with usb_disk ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by aldeck): I've still got the problem with my fat usb disk (can't try ext3 right now). I guess it's a different bug then? I've got the same syslog as in my previous comment. Note for mmlr: Diskprobe shows only like 60 bytes of repetitive pattern and the rest is filled with zeroes. I can't access further blocks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 00:11:09 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 20 Aug 2008 22:11:09 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.7621e59c103e21fe92df240dcbeec095@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by andreasf): I tried, and I've come further than Scott had, but I do not get to a prompt due to issues with {{{/etc/termcap}}}: http://ports.haiku-files.org/wiki/app-shells/bash/3.2/2 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:08:47 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 23:08:47 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.a49ae1e128dbda3a67d26e409635d6fe@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Should be fixed in r27092. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:28:26 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 23:28:26 -0000 Subject: [Haiku-bugs] [Haiku] #2283: less needs updating (easy) In-Reply-To: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> References: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> Message-ID: <051.eacdf17267e6a10f830b95e08dba5e8e@haiku-os.org> #2283: less needs updating (easy) ----------------------------------------------+----------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: I added missing files in your patch (charset.h). Seems good in r27094 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:34:22 2008 From: trac at haiku-os.org (korli) Date: Wed, 20 Aug 2008 23:34:22 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' does not work In-Reply-To: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> References: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> Message-ID: <052.ff5b9b6abce81dd36a4294cdc32a129c@haiku-os.org> #2612: 'Save as' does not work --------------------------------------+------------------------------------- Reporter: andreasf | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/StyledEdit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by korli): Can't reproduce here also. Was this on real hardware ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:34:14 2008 From: trac at haiku-os.org (xspager) Date: Wed, 20 Aug 2008 23:34:14 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.7a4faa9ec755b2e4e09b61bb6f2c02f6@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by xspager): Replying to [comment:9 axeld]: > With the archive posted I get a different error, though: > {{{ > runtime_loader: elf_resolve_symbol: found symbol 'debugger' in shared image but wrong type > }}} > > I used libSDL.so from HaikuPorts above, but also the BeOS one doesn't change this. axeld, it is why i build SDL myself. In the Haiku gcc4+gcc2 i got a litlle diferent error message, runtime loader also say that had trouble realloking libbe.so too. In gcc2 i use SDL that i build myself, but in the gcc4+gcc2('cause of the lack of gcc. it is right?) i use the same SDL, from haikuports, too, and i get the unresovable symbol as with you, in Haiku gcc2 and in the mixed gcc4 using the Haikuport or bebits prebuid libSDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:38:42 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 23:38:42 -0000 Subject: [Haiku-bugs] [Haiku] #2074: Time Preferences window doesn't show up. In-Reply-To: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> References: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> Message-ID: <053.29340014a32450f6cd4f1e25b3a7d17c@haiku-os.org> #2074: Time Preferences window doesn't show up. ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Yep, i can confirm it is fixed! (Tested on r27094) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 01:41:11 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 20 Aug 2008 23:41:11 -0000 Subject: [Haiku-bugs] [Haiku] #2057: 'IFS' screensaver crash In-Reply-To: <044.7b1b6ec7b89eaa223334a4d86ad3aebb@haiku-os.org> References: <044.7b1b6ec7b89eaa223334a4d86ad3aebb@haiku-os.org> Message-ID: <053.55ca38ce7f26df266d3db1b6200c90e8@haiku-os.org> #2057: 'IFS' screensaver crash ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Forgot to close that one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 02:59:53 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 21 Aug 2008 00:59:53 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.12aeb329ec9f1a0bb5bc3e36c3094bcc@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by aldeck): * status: reopened => closed * resolution: => fixed Comment: Applied in r27095 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 03:11:04 2008 From: trac at haiku-os.org (dustin howett) Date: Thu, 21 Aug 2008 01:11:04 -0000 Subject: [Haiku-bugs] [Haiku] #2652: Default Preferences folder display & Preflet Description attribute Message-ID: <048.722a6a01669b493b18c47c4ae7d1bb76@haiku-os.org> #2652: Default Preferences folder display & Preflet Description attribute ---------------------------+------------------------------------------------ Reporter: dustin howett | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Idea partly by Koki in #haiku Add preflet descriptions to a Description attribute and display them in the Tracker window. Set the default view for the preferences folder to detailed list view, hide every column except Name and Description (of course, the user can change this), as size and date &c. are not as important for preflets. This provides quick, easy access to the preflets and what they all do without having the user do any extra work (just open the Preferences folder) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 13:59:34 2008 From: trac at haiku-os.org (tqh) Date: Wed, 20 Aug 2008 11:59:34 -0000 Subject: [Haiku-bugs] [Haiku] #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) In-Reply-To: <038.cc379f3e9fd1a7d907414312c6418dc4@haiku-os.org> References: <038.cc379f3e9fd1a7d907414312c6418dc4@haiku-os.org> Message-ID: <047.51336ad4ea067439387e9f9e13bbf54d@haiku-os.org> #2650: Intel Extreme crash on boot (Painter::FillRectNoClipping) ---------------------------------------------+------------------------------ Reporter: tqh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: duplicate | Blockedby: 2350 Platform: All | Blocking: ---------------------------------------------+------------------------------ Comment(by tqh): Ah I only looked for intel extreme driver bugs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 18:16:39 2008 From: trac at haiku-os.org (axeld) Date: Wed, 20 Aug 2008 16:16:39 -0000 Subject: [Haiku-bugs] [Haiku] #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders In-Reply-To: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> References: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> Message-ID: <051.26ebebffa3f881e25c62ba741b9dd7e0@haiku-os.org> #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): Well, BeOS survived long years with this "feature", so I wouldn't go as far to call it a bug. But in any case, changing this would be very welcome :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 19 13:06:51 2008 From: trac at haiku-os.org (bga) Date: Tue, 19 Aug 2008 11:06:51 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.2bf170b453c7076479bb82b113c9ae8a@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): More index problems: {{{ ~/mail/BGA(BUG-Br)/in> query MAIL:subject=\* | wc -l query: could not get path for entry query: could not get path for entry 152 }}} BTW, there are only 110 emails in my system right now and it seems the MAIL:subject index have 152 entries. Here is what I see on syslog when running the command above: {{{ KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623466 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623466 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623397 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623397 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623494 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623494 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623377 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623377 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623526 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623526 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623462 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623462 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623489 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623489 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623513 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623513 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623487 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623487 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623482 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623482 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623486 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623486 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623492 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623492 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623381 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623381 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623400 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623400 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623405 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623405 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623377 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623377 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623387 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623387 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623418 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623418 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623550 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623550 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623686 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623686 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623463 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623463 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623441 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623441 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623430 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623430 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623382 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623382 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623400 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623400 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623453 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623453 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623460 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623460 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623454 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623454 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623456 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623456 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623531 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623531 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623419 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623419 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623420 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623420 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623421 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623421 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623427 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623427 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623426 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623426 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623425 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623425 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623388 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623388 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623381 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623381 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623398 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623398 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623424 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623424 in index "MAIL:subject"! KERN: bfs: inode 2623354 in query has no name! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623398 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623398 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623367 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623367 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623369 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623369 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623462 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623462 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623461 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623461 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623463 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623463 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623467 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623467 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623434 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623434 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623460 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623460 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623367 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623367 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623379 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623379 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623419 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623419 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623355 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623355 in index "MAIL:subject"! KERN: bfs: KERN: inode 2623356 in query has no name! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623666 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623666 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623585 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623585 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623612 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623612 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623384 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623384 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623369 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623369 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623485 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623485 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623566 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623566 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623571 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623571 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623572 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623572 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623407 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623407 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623426 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623426 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623427 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623427 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623414 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623414 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623479 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623479 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623397 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623397 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623399 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623399 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623431 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623431 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623388 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623388 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623380 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623380 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623630 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623630 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623451 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623451 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623410 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623410 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623421 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623421 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623383 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623383 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623369 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623369 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623379 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623379 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623380 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623380 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623381 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623381 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623408 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623408 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623444 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623444 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623367 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623367 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623405 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623405 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623422 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623422 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623604 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623604 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623456 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623456 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623412 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623412 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623407 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623407 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623404 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623404 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623588 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623588 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623377 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623377 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623422 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623422 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623423 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623423 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623401 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623401 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623493 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623493 in index "MAIL:subject"! KERN: bfs: inode 2623354 in query has no name! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623495 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623495 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623376 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623376 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623400 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623400 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623390 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623390 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623399 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623399 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623410 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623410 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623432 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623432 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623450 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623450 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623456 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623456 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623457 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623457 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623461 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623461 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623464 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623464 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623469 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623469 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623416 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623416 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623649 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623649 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623457 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623457 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623699 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623699 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623355 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623355 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623367 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623367 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623391 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623391 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623430 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623430 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623434 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623434 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623445 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623445 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623458 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623458 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623388 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623388 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623466 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623466 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623509 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623509 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623510 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623510 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623511 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623511 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623387 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623387 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623419 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623419 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623420 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623420 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623398 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623398 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623712 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623712 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623713 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623713 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623376 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623376 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623379 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623379 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623382 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623382 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623383 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623383 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623383 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623383 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623383 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623383 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623383 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623383 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623384 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623384 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623389 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623389 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623389 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623389 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623390 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623390 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623391 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623391 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623392 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623392 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623393 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623393 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623397 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623397 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623399 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623399 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623399 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623399 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623405 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623405 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623410 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623410 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623412 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623412 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623413 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623413 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623417 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623417 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623419 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623419 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623422 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623422 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623430 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623430 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623445 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623445 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623455 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623455 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623458 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623458 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623615 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623615 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623440 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623440 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623441 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623441 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623423 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623423 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623377 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623377 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623414 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623414 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623464 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623464 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623391 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623391 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623464 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623464 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623541 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623541 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623384 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623384 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623387 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623387 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623398 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623398 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623441 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623441 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623446 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623446 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623449 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623449 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623379 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623379 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623416 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623416 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623425 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623425 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623428 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623428 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623446 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623446 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623448 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623448 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623475 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623475 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623477 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623477 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623528 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623528 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623396 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623396 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623414 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623414 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623393 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623393 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623384 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623384 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623462 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623462 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623400 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623400 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623404 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623404 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623409 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623409 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623413 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623413 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623442 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623442 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623451 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623451 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623460 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623460 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623387 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623387 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623367 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623367 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623382 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623382 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623384 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623384 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623385 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623385 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623386 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623386 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623386 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623386 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623387 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623387 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623391 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623391 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623396 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623396 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623396 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623396 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623428 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623428 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623431 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623431 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623443 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623443 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623447 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623447 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623459 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623459 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623463 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623463 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623466 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623466 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623467 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623467 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623468 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623468 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623470 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623470 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623474 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623474 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623377 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623377 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623408 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623408 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623389 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623389 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623392 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623392 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623401 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623401 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623455 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623455 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623369 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623369 in index "MAIL:subject"! KERN: bfs: inode 2623356 in query has no name! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623454 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623454 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623382 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623382 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623671 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623671 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623381 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623381 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623408 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623408 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623717 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623717 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623646 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623646 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623506 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623506 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623650 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623650 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623529 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623529 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623445 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623445 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623501 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623501 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623405 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623405 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623393 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623393 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623702 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623702 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623378 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623378 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623425 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623425 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623637 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623637 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623449 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: KERN: could not get inode 2623449 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623411 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623411 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623689 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623689 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623396 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623396 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623479 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623479 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623407 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623407 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623565 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623565 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623407 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623407 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623414 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623414 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623392 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623392 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623386 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623386 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: KERN: inode at 2623555 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623555 in index "MAIL:subject"! KERN: bfs: InitCheck:301: Bad data KERN: bfs: inode at 2623447 is corrupt! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 2623447 in index "MAIL:subject"! }}} The system has only been running for a few hours (after installing r27057) and I checked for emails (and downloaded then) around 10 times in this period. No unexpected reboot, crash or anything else that would have a bigger chance of corrupting data. And. just as reported originally (and considering all my email files are inside the mail directory: {{{ ~/mail/BGA(BUG-Br)/in> query MAIL:subject=\* | grep -v mail query: could not get path for entry /boot/home/development/haiku/generated/Jamfile /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 9 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 1 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 8 /boot/home/config/settings/Media/MDefaultManager /boot/home/config/settings/Media/multi_audio_settings /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 1 /boot/home/config/settings/Mail/BeMail\ Settings /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 0 /boot/home/config/settings/Media/multi_audio_settings /boot/home/config/settings/Mail/BeMail\ Settings query: could not get path for entry /boot/home/development/haiku/generated/haiku.image /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 7 /boot/home/development/haiku/data /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 0 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 0 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 2 /boot/home/development/haiku/generated/haiku.image /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 7 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 3 /boot/home/development/haiku/headers /boot/home/development/haiku/generated/haiku.image /boot/home/development/haiku/3rdparty /boot/home/development/haiku/3rdparty /boot/home/development/haiku/docs /boot/home/development/haiku/headers /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 9 /boot/home/config/settings/Media/multi_audio_settings /boot/home/config/settings/Media/multi_audio_settings /boot/home/development/haiku/docs /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 9 /boot/home/development/haiku/data /boot/home/config/settings/Media/multi_audio_settings /boot/home/config/settings/Media/MDefaultManager /boot/home/development/haiku/generated/Jamfile /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 5 /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 4 /boot/home/config/settings/Media/MDefaultManager /boot/home/config/settings/AGMSBayesianSpam/AGMSBayesianSpam\ Database.backup\ 0 }}} So this is definitely the case that files that have nothing to do with a specific index but were accessed (in some cases, even read-only, it seems), were incorrectly added to it. Note that my example involves MAIL:* indexes, but It is probably also affecting BEOS:APP_SIG, for example, and maybe even last_modified, name and size indexes. In fact: {{{ ~/mail/BGA(BUG-Br)/in> query name=\* | wc -l 116415 ~/mail/BGA(BUG-Br)/in> query size\<1000000000 | wc -l 93916 }}} Considering I have no files that are equal or bigger to the size I used, those numbers shoulkd match, right? Not that I another thing I also see from time to time is the same file added twice to one index so it could be that name has more files than it should, size has less files than it should or even both. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 10:02:15 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 21 Aug 2008 08:02:15 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.b21b1b63d7ed5917fe50787fdd9ee5bd@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by emitrax): Last time I tried I did get a prompt. I'll try and builing it again today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 10:30:02 2008 From: trac at haiku-os.org (axeld) Date: Thu, 21 Aug 2008 08:30:02 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup In-Reply-To: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> References: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> Message-ID: <053.131bb2612e846eac251d5322dc58081a@haiku-os.org> #2651: KDL during startup ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): How did you try to boot Haiku? How large is the disk, what partitions are on it? The problem is just that Haiku doesn't find a boot partition - this can have many reasons, and can largely depend on how you tried to boot it. Can you enable on-screen debug output in the boot loader and take photos from each page? Most interesting would be those with the drive/partition recognition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 10:32:41 2008 From: trac at haiku-os.org (axeld) Date: Thu, 21 Aug 2008 08:32:41 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.e6b270c7ab2e6f32af21c6b9b6f145b3@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): The MIT license as found on OSI is our license. We could add a link to it somewhere in our tree (and/or AboutSystem), and also put it in there completely, for reference, once. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 21:07:59 2008 From: trac at haiku-os.org (koki) Date: Wed, 20 Aug 2008 19:07:59 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.c8acc9111ded3f62a85ef7903c419a6d@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by koki): * cc: kokitomare at gmail.com (added) Comment: Copy and paste of what I posted to the haiku-bugs list (not knowing that it was bad etiquette to reply to the list; my apologies). The OSI seems to disagree (with the view that the MIT license does not exist): http://www.opensource.org/licenses/mit-license.php Not an expert, but it does seem that it is not that clear cut. When BGA said in our interview with the SCaLE folks back in February that Haiku used a BSD license, I recall Michael Phipps pointing out that it was not BSD but MIT the license that was chosen for Haiku. A quick search of the OpenBeos mailing list archive also reveals at least one message from Phipps that coincides with this: http://www.freelists.org/archives/openbeos/04-2002/msg00342.html I am note advocating one license name over another; but I do think it would be a good idea to (at least try to) get feedback from Michael Phipps on this one, as he (at least) seemed very clear on the choice and he may be able to throw some light into why that choice was made. FWIW. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 20 13:56:12 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 20 Aug 2008 11:56:12 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.b0fd8a34c80b0ab971792a80d45ecf2b@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Please open a new bug report for your issue as it is not related to this bug and this bug has been closed already. Can you also provide a stack trace of the KDL using the "sc" command and include some details to the SD card used? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 11:36:30 2008 From: trac at haiku-os.org (cebif) Date: Thu, 21 Aug 2008 09:36:30 -0000 Subject: [Haiku-bugs] [Haiku] #2645: Play any wav sound with Preferences, Sounds and system freezes (was: Play any sound with Preferences, Sounds and system freezes) In-Reply-To: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> References: <040.ae888d7ab44d10d9da65ddff8eedee28@haiku-os.org> Message-ID: <049.1f1a4e8123d438e4e1ba1cbec4a104cf@haiku-os.org> #2645: Play any wav sound with Preferences, Sounds and system freezes ---------------------------------+------------------------------------------ Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Sounds | Version: R1 development Resolution: duplicate | Blockedby: 1708 Platform: All | Blocking: ---------------------------------+------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 11:44:03 2008 From: trac at haiku-os.org (axeld) Date: Thu, 21 Aug 2008 09:44:03 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.3106d2fae3eec27f18f88fc03e39225b@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by axeld): Since you already had to compile SDL yourself, I think there is just something wrong with your setup. I just have no idea what this could be. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 12:02:14 2008 From: trac at haiku-os.org (cebif) Date: Thu, 21 Aug 2008 10:02:14 -0000 Subject: [Haiku-bugs] [Haiku] #1708: Select Play from Sounds prefs freezes system In-Reply-To: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> References: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> Message-ID: <049.ab9b523017fa1591c8a6f640a2cba400@haiku-os.org> #1708: Select Play from Sounds prefs freezes system ----------------------------+----------------------------------------------- Reporter: el-al | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: 2645 ----------------------------+----------------------------------------------- Comment(by cebif): Replying to [comment:4 mmlr]: > (In #2645) Duplicate of #1708. I don't think #2646 is a duplicate because before I tested with r27011, wav types could be played in Sounds. I should probably have made it clear when I reported #2645 that not only aiff types but now wav sounds caused a freeze. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 12:48:58 2008 From: trac at haiku-os.org (xspager) Date: Thu, 21 Aug 2008 10:48:58 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.19a38624424bd01c588cd77f8eb73eaf@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by xspager): Replying to [comment:11 axeld]: > Since you already had to compile SDL yourself, I think there is just something wrong with your setup. I just have no idea what this could be. may be, but i don't believe so, at least to SDL and pkg-config. I use this to both: {{{ ./configure --build=i586-pc-beos --prefix=/boot/home/config && make install }}} to VBA i got a lot of compilation error, so i try many configure flags options, until i found one that build. {{{ CXXFLAGS='-O1 -lnetwork' ./configure --build=i586-pc-beos --disable- sdltest --enable-c-core --disable-profiling --without-mmx && make }}} thanks for helping axeld! ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 13:16:32 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 21 Aug 2008 11:16:32 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' sometimes behaves unexpected (was: 'Save as' does not work) In-Reply-To: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> References: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> Message-ID: <052.2e6d97ca045e4ae7dcf6cb9789cc343b@haiku-os.org> #2612: 'Save as' sometimes behaves unexpected --------------------------------------+------------------------------------- Reporter: andreasf | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/StyledEdit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by andreasf): Yes, it was. The earlier problem I referred to (#2148) was that due to a BFS issue the volume became read-only, but StyledEdit did not complain when trying to save on it, as described above. (At that time, `touch` etc. didn't work either.) Not sure if the problem is in StyledEdit itself or in libbe/whatever, but as an observation, in some corner cases the app behaves unexpected... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 13:44:55 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 11:44:55 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.8d28860b77e24e0ae221012006e85ef7@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by bonefish): Replying to [comment:5 andreasf]: > I tried, and I've come further than Scott had, but I do not get to a prompt due to issues with {{{/etc/termcap}}}: > > http://ports.haiku-files.org/wiki/app-shells/bash/3.2/2 These are only warnings -- the same printed when starting the ftp client -- and shouldn't have anything to do with why you don't get a prompt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 14:12:55 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 12:12:55 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.d89c0510298653701d0bf666f723c619@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by bonefish): I'm no longer sure that Haiku's "read" is broken. Here's what "help read" says: {{{ read: read [-ers] [-u fd] [-t timeout] [-p prompt] [-a array] [-n nchars] [-d delim] [name ...] One line is read from the standard input, or from file descriptor FD if the -u option is supplied, and the first word is assigned to the first NAME, the second word to the second NAME, and so on, with leftover words assigned to the last NAME. Only the characters found in $IFS are recognized as word delimiters. If no NAMEs are supplied, the line read is stored in the REPLY variable. If the -r option is given, this signifies `raw' input, and backslash escaping is disabled. The -d option causes read to continue until the first character of DELIM is read, rather than newline. If the -p option is supplied, the string PROMPT is output without a trailing newline before attempting to read. If -a is supplied, the words read are assigned to sequential indices of ARRAY, starting at zero. If -e is supplied and the shell is interactive, readline is used to obtain the line. If -n is supplied with a non-zero NCHARS argument, read returns after NCHARS characters have been read. The -s option causes input coming from a terminal to not be echoed. The -t option causes read to time out and return failure if a complete line of input is not read within TIMEOUT seconds. If the TMOUT variable is set, its value is the default timeout. The return code is zero, unless end-of-file is encountered, read times out, or an invalid file descriptor is supplied as the argument to -u. }}} "With leftover words assigned to the last NAME" is exactly what happens in Haiku. BeOS's bash 2.03 bevaves the same, while all bash 3.* versions I've tested read only the first word. So I guess updating our bash will indeed make our "read" behave the same. I suppose filing a bug report with the bash folks (that either their documentation or their implementation is wrong) would be in order. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 14:16:14 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 12:16:14 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.80a0b1cf0621e98cc87a43d8b60a0e60@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by bonefish): Replying to [comment:12 xspager]: > > may be, but i don't believe so, at least to SDL and pkg-config. I use this to both: > > {{{ > ./configure --build=i586-pc-beos --prefix=/boot/home/config && make install > }}} While it might usually work {{{--build=i586-pc-beos}}} is not correct. > to VBA i got a lot of compilation error, so i try many configure flags options, until i found one that build. > > {{{ > CXXFLAGS='-O1 -lnetwork' ./configure --build=i586-pc-beos --disable- sdltest --enable-c-core --disable-profiling --without-mmx && make > }}} Unless I'm much mistaken CXXFLAGS are the C++ compilation flags. "-lnetwork" is a linker flag (LDFLAGS), though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 15:06:58 2008 From: trac at haiku-os.org (xspager) Date: Thu, 21 Aug 2008 13:06:58 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.e18d96cf2cc0684976a2cb3d7bffe0f8@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by xspager): Replying to [comment:13 bonefish]: > Replying to [comment:12 xspager]: > > > > may be, but i don't believe so, at least to SDL and pkg-config. I use this to both: > > > > {{{ > > ./configure --build=i586-pc-beos --prefix=/boot/home/config && make install > > }}} > > While it might usually work {{{--build=i586-pc-beos}}} is not correct. > someone on the #haiku give me this "cheat code" :D . what is the right bonefish? > > to VBA i got a lot of compilation error, so i try many configure flags options, until i found one that build. > > > > {{{ > > CXXFLAGS='-O1 -lnetwork' ./configure --build=i586-pc-beos --disable- sdltest --enable-c-core --disable-profiling --without-mmx && make > > }}} > > Unless I'm much mistaken CXXFLAGS are the C++ compilation flags. "-lnetwork" is a linker flag (LDFLAGS), though. yes, this could be the error... hum... but i did that 'cause ld warns about the lack of symbols, that i judge to be from this lib. when i include that there no warns. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 15:41:50 2008 From: trac at haiku-os.org (xspager) Date: Thu, 21 Aug 2008 13:41:50 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.eef2ec2ed469717fdaff87887ffd9320@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by xspager): it sill broke. on rev. 27095 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 16:17:09 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 21 Aug 2008 14:17:09 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.c6024740afc5fd1c40446b7a4294eb9d@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by aldeck): * cc: alex at zappotek.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 16:41:58 2008 From: trac at haiku-os.org (julun) Date: Thu, 21 Aug 2008 14:41:58 -0000 Subject: [Haiku-bugs] [Haiku] #2534: BPicture somehow broken due to change 26665 (was: Menu background issues with R5 Apps) In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.eb8ee20a04792b224d496fe6558ebd05@haiku-os.org> #2534: BPicture somehow broken due to change 26665 ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by julun): * cc: host.haiku at gmx.de (added) * milestone: R1 => R1/alpha1 Comment: Hi, r26665 broke code like this: src/kits/print/BeUtilsTranslation.cpp:75 BPicture *BitmapToGrayedPicture(BView* view, BBitmap *bitmap) { if (bitmap) { BRect rect(bitmap->Bounds()); view->BeginPicture(new BPicture()); view->DrawBitmap(bitmap); view->SetHighColor(255, 255, 255, 128); view->SetDrawingMode(B_OP_ALPHA); view->FillRect(rect); return view->EndPicture(); } return NULL; } If i change it like this it is working again: BPicture *BitmapToGrayedPicture(BView* view, BBitmap *bitmap) { if (bitmap) { BRect rect(bitmap->Bounds()); BView* tmp = new BView(rect, "", B_FOLLOW_NONE, B_WILL_DRAW); view->AddChild(tmp); tmp->BeginPicture(new BPicture()); tmp->DrawBitmap(bitmap); tmp->SetHighColor(255, 255, 255, 128); tmp->SetDrawingMode(B_OP_ALPHA); tmp->FillRect(rect); BPicture* result = tmp->EndPicture(); view->RemoveChild(tmp); delete tmp; return result; } return NULL; } The above function is called from src/servers/print/ConfigWindow.cpp:310 To see the broken behavior apply the attached patch to StyledEdit, set 'Preview' as system default printer and use 'Print' directly from the File menu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 17:08:57 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 21 Aug 2008 15:08:57 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.bb98cfa2113deebd0c18c879bef75555@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): I have fixed the SDL patch on HaikuPorts: http://ports.haiku-files.org/browser/haikuports/trunk/media- libs/libsdl/SDL-1.2.13-haiku.diff To build SDL, grab the source, patch it then: * cp /boot/home/config/share/libtool/config.guess build-scripts * cp /boot/home/config/share/libtool/config.sub build-scripts * cat $(aclocal --print-ac-dir)/libtool.m4 >> acinclude.m4 * libtoolize --force --copy * aclocal * automake * autoconf * ./configure --prefix=/boot/common * make * make install To build the tests, cd test, then: * autoconf * ./configure * make Still might be an issue with opengl support, need to look into that further. See Haiku ticket #2196. From: http://ports.haiku-files.org/wiki/media-libs/libsdl/1.2.13/1 Sounds like xspager is using a mixed gcc2-gcc4 haiku? I have not tested that out, so your mileage may vary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 17:46:55 2008 From: trac at haiku-os.org (j_freeman) Date: Thu, 21 Aug 2008 15:46:55 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup In-Reply-To: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> References: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> Message-ID: <053.4a513f97de048a891df0abd0f06be08c@haiku-os.org> #2651: KDL during startup ------------------------+--------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by j_freeman): I was booting from a 4GB OCZ USB thumbdrive with only one partition, that being Haiku. The same thumbdrive works on my computer. I'll post back with the on-screen debug output when I get a chance to try it on his PC again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 18:26:34 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 21 Aug 2008 16:26:34 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.04d700c8ee43ef0603ae06bec545d273@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by aldeck): * status: closed => reopened * resolution: fixed => Comment: There is a problem with this new libpng version. The image in Vision's setup/(first startup) window is not loaded anymore. Here's what i get on terminal output: libpng error: x[9C]b[60]: invalid chunk type -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 18:27:51 2008 From: trac at haiku-os.org (korli) Date: Thu, 21 Aug 2008 16:27:51 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.0c450dd963589e2d15f6520fdc4484fb@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by korli): Will update with 1.2.31 ASAP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 18:29:43 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 21 Aug 2008 16:29:43 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.d6ea3d4eeede7a6c6895cb64a59d33b4@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by andreasf): That might explain the concatenation of the two filename columns in Git's {{{templates}}} subdir but not the colon after {{{Desktop}}} in the home dir... Couldn't this be an issue with our POSIX (e.g., wide char) implementation? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 21:14:32 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 21 Aug 2008 19:14:32 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.1594843dc0173aa759c49008acb687e4@haiku-os.org> #2327: Please add langinfo.h as a public header --------------------------+------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): This is needed for link-grammar, which is one of the dependencies of AbiWord. Kaliber, what did you run into so far that this is holding up? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 21:17:50 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 21 Aug 2008 19:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.5ef3d1713ab16294bd1111e6796d0b4c@haiku-os.org> #2327: Please add langinfo.h as a public header --------------------------+------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by scottmc): * cc: haiku at scottmc.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 21:21:24 2008 From: trac at haiku-os.org (luroh) Date: Thu, 21 Aug 2008 19:21:24 -0000 Subject: [Haiku-bugs] [Haiku] #2653: Ghost links in Haiku source tree (easy) Message-ID: <040.6861f215648a82f8703ba017ee845422@haiku-os.org> #2653: Ghost links in Haiku source tree (easy) ---------------------+------------------------------------------------------ Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ src/add-ons/kernel/file_systems/googlefs/_APP_ src/add-ons/input_server/methods/pen/_APP_ src/add-ons/input_server/methods/t9/_APP_ Some archive programs run into problems when hitting these links. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 22:01:03 2008 From: trac at haiku-os.org (kaliber) Date: Thu, 21 Aug 2008 20:01:03 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.7c421efc94bf06f6c9b009c0ec6a3854@haiku-os.org> #2327: Please add langinfo.h as a public header --------------------------+------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by kaliber): Replying to [comment:2 scottmc]: > This is needed for link-grammar, which is one of the dependencies of AbiWord. > Kaliber, what did you run into so far that this is holding up? I cannot remember. Man or groff require that header. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 22:06:22 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 21 Aug 2008 20:06:22 -0000 Subject: [Haiku-bugs] [Haiku] #2653: Ghost links in Haiku source tree (easy) In-Reply-To: <040.6861f215648a82f8703ba017ee845422@haiku-os.org> References: <040.6861f215648a82f8703ba017ee845422@haiku-os.org> Message-ID: <049.3a7651afae2ac38fe4a7979df590c591@haiku-os.org> #2653: Ghost links in Haiku source tree (easy) ----------------------+----------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Changes (by andreasf): * cc: andreas.faerber at web.de (added) Comment: `grep -r` complained about them, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 22:13:53 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 20:13:53 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.67893b933701f760cb3b4b95df5e01c6@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by bonefish): Replying to [comment:9 andreasf]: > That might explain the concatenation of the two filename columns in Git's {{{templates}}} subdir but not the colon after {{{Desktop}}} in the home dir... Well, try and run an {{{ls *}}} in the home directory and you'll see. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 22:18:56 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 20:18:56 -0000 Subject: [Haiku-bugs] [Haiku] #2647: runtime_loader error In-Reply-To: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> References: <042.5d52a8924829730e3fecc64db896f740@haiku-os.org> Message-ID: <051.0d828982bbc37d4daa632744b144ee9f@haiku-os.org> #2647: runtime_loader error ------------------------------------+--------------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Comment(by bonefish): Replying to [comment:14 xspager]: > Replying to [comment:13 bonefish]: > > Replying to [comment:12 xspager]: > > > > > > may be, but i don't believe so, at least to SDL and pkg-config. I use this to both: > > > > > > {{{ > > > ./configure --build=i586-pc-beos --prefix=/boot/home/config && make install > > > }}} > > > > While it might usually work {{{--build=i586-pc-beos}}} is not correct. > > someone on the #haiku give me this "cheat code" :D . what is the right bonefish? i586-pc-haiku describes our platform. Usually one should use the auto tools to replace config.{guess,sub}, so that one wouldn't even need to specify the platform. Aside from that there might be actual porting effort necessary to get the program working correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 23:08:01 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 21 Aug 2008 21:08:01 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.5e0cbca5a1b7d25ef489be2efda29a9b@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by andreasf): Seems like I just did `ls` there for checking then, sorry. The Makefile does `ls *--*`, therefore `ls *` as simplification that appeared to work elsewhere. If I run `ls | (read x y; echo $x:$y)` it separates the first and second column entries by the specified colon and then concatenates the remaining ones with whitespace, which would back your interpretation. I checked on Solaris 10 but even that has bash 3.0 already; the only other system to cross-check I found was BeOS R5, which has {{{2.03.0(1)}}}, both do '''not''' expose this issue. If it's a problem with our specific version, the question is, should we just silently upgrade to a more recent bash asap, or should we fix software like Git to handle this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 21 23:54:24 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 21 Aug 2008 21:54:24 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.3097da997a570df9c62862674c69772d@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by bonefish): After some more checking, it turns out {{{read}}} actually behaves the same on all platforms and bash versions and according to the documentation. What does behave differently is {{{ls}}}. Apparently it uses a different output format when its stdout is not a tty (you can check with {{{ls | cat}}}), but it doesn't under Haiku. There's probably something wrong with the tty recognition, or something is misconfigured. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 00:35:10 2008 From: trac at haiku-os.org (korli) Date: Thu, 21 Aug 2008 22:35:10 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.1fb3cc06f435c38958324db663f19917@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by korli): * status: reopened => closed * resolution: => fixed Comment: Updated in r27115. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 01:33:52 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 21 Aug 2008 23:33:52 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.a2cf67e3bbc6862d384608b81e46a6cd@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by andreasf): Confirmed, `ls | cat` is one-column elsewhere, including BeOS, but multi- column at r27117. Unfortunately I don't see the {{{ls}}} source - it's neither in {{{bash/builtins}}} nor in {{{bin}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 01:42:33 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 21 Aug 2008 23:42:33 -0000 Subject: [Haiku-bugs] [Haiku] #2646: [read] Too much data read In-Reply-To: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> References: <043.f0e688d7ee5d6163d7f35b16ce35c9b5@haiku-os.org> Message-ID: <052.6a0bb57e90d85fddea073ed5a2965476@haiku-os.org> #2646: [read] Too much data read ----------------------------------------------+----------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by emitrax): you mean {{{src/bin/coreutils/src/ls.c}}} ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 08:13:17 2008 From: trac at haiku-os.org (laplace) Date: Fri, 22 Aug 2008 06:13:17 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.a5e954e973815e09f29b6ddcce7cc402@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by laplace): * owner: laplace => jackburton * priority: normal => blocker Comment: This is a quite serious bug for printing, I propose to change its milestone to R1/alpha1. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 10:31:14 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 22 Aug 2008 08:31:14 -0000 Subject: [Haiku-bugs] [Haiku] #2652: Default Preferences folder display & Preflet Description attribute In-Reply-To: <048.722a6a01669b493b18c47c4ae7d1bb76@haiku-os.org> References: <048.722a6a01669b493b18c47c4ae7d1bb76@haiku-os.org> Message-ID: <057.d9be5e0a8bd1eaeb76cf7606ac606e2e@haiku-os.org> #2652: Default Preferences folder display & Preflet Description attribute ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): It's actually a very nice idea IMHO. Hope to see this implemented soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 10:38:35 2008 From: trac at haiku-os.org (diver) Date: Fri, 22 Aug 2008 08:38:35 -0000 Subject: [Haiku-bugs] [Haiku] #2652: Default Preferences folder display & Preflet Description attribute In-Reply-To: <048.722a6a01669b493b18c47c4ae7d1bb76@haiku-os.org> References: <048.722a6a01669b493b18c47c4ae7d1bb76@haiku-os.org> Message-ID: <057.92e461b1a595fb17fe5419f1e8b40cc7@haiku-os.org> #2652: Default Preferences folder display & Preflet Description attribute ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): It could even be extended to system folder describing drivers/add- ons/servers, maybe their versions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 11:23:03 2008 From: trac at haiku-os.org (jackburton) Date: Fri, 22 Aug 2008 09:23:03 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.c1176d2646c4315398651bccbda68efe@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Replying to [comment:7 laplace]: > This is a quite serious bug for printing, I propose to change its milestone to R1/alpha1. I agree, but I don't think I have the time to work on this, sorry. So someone else will have to fix it. Currently, except for what I wrote in comment 6, I don't have a good idea on how to solve this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 12:21:26 2008 From: trac at haiku-os.org (laplace) Date: Fri, 22 Aug 2008 10:21:26 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.25d1c535279068786ac9da534596e44f@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by laplace): * cc: host.haiku at gmx.de (added) Comment: CCed Karsten as he brought up this topic on printing mailing list. In R5 BView seems to support a kind of "disk mode" SetDiskMode(filename, offset) according to the comment in our View.cpp the picture is flattened to the file while the drawing commands are recorded, maybe that could be utilized, if SetDiskMode(...) would be implemented ;)? On the other hand this might be an optimization only and un-/flattening of large bitmaps must be supported anyway? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 12:32:46 2008 From: trac at haiku-os.org (laplace) Date: Fri, 22 Aug 2008 10:32:46 -0000 Subject: [Haiku-bugs] [Haiku] #2477: Haiku's bootman doesn't show the same partitions as BeOS's In-Reply-To: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> References: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> Message-ID: <050.383b32df5269b9777366a255435c0d96@haiku-os.org> #2477: Haiku's bootman doesn't show the same partitions as BeOS's ---------------------------+------------------------------------------------ Reporter: idefix | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by laplace): * owner: axeld => laplace * milestone: R1 => R1/alpha1 Comment: When I asked on the development mailing list, Axel outlined the necessary steps for B_GET_BIOS_DRIVE_ID: > It's even a bit of work, but I can outline it a bit: > 1) the boot loader needs to make a connection between drive ID and disk > in a way that the OS can recognize it again. IIRC BeOS uses a sum/hash > of the contents of a few blocks until it has enough to differentiate > all (BIOS) drives. The name, or serial number is probably not reliably > available from the BIOS, but I haven't really tried that yet. > 2) it would need to store that information in the kernel_args > structure. > 3) when the OS detects the drives, it would see in that structure how > it can recognize the drive again, and can then store the BIOS ID of > that drive internally, so that B_GET_BIOS_DRIVE_ID can work as > expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 13:09:31 2008 From: trac at haiku-os.org (VinDuv) Date: Fri, 22 Aug 2008 11:09:31 -0000 Subject: [Haiku-bugs] [Haiku] #2654: The Boot Menu doesn't work on Intel Macs Message-ID: <041.5c74fb71b4501ca58b7a0b9c116ecdf9@haiku-os.org> #2654: The Boot Menu doesn't work on Intel Macs --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- When I start Haiku on my Mac mini (with a USB keyboard), I can press the spacebar to enter the boot menu, but after that nothing happens if I press the arrows or the Enter keys. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 14:13:56 2008 From: trac at haiku-os.org (julun) Date: Fri, 22 Aug 2008 12:13:56 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.8e131b5948b1d3c35f981054088c5ee1@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, can we do a partial upload in _Upload(), like splitting the data in a defined size and use link.Attach and link.Read as long all data are up in the app_server? Same for download? Would that work? This would effect both _Upload()/ _Download in BPicture and ImportData/ExportData in ServerPicture, right? If that could work i can give it a try next week, I'm off over the weekend. Regards, Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 14:25:43 2008 From: trac at haiku-os.org (julun) Date: Fri, 22 Aug 2008 12:25:43 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.f71808ccca74aa903f6c360906ee49b1@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Forget what i wrote, i had a short look at ServerLink.Attach/ Read. Need to think about it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 14:29:16 2008 From: trac at haiku-os.org (axeld) Date: Fri, 22 Aug 2008 12:29:16 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.fdf761f2f5d63850840b82added5aac0@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: I'm closing this as invalid, have a look at the recent discussion on haiku-development. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 15:19:08 2008 From: trac at haiku-os.org (laplace) Date: Fri, 22 Aug 2008 13:19:08 -0000 Subject: [Haiku-bugs] [Haiku] #2477: Haiku's bootman doesn't show the same partitions as BeOS's In-Reply-To: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> References: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> Message-ID: <050.2aceb6fe2079e421efa2f1d06108a12a@haiku-os.org> #2477: Haiku's bootman doesn't show the same partitions as BeOS's ---------------------------+------------------------------------------------ Reporter: idefix | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by laplace): Part two of this ticket is fixed in r27149. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:03:05 2008 From: trac at haiku-os.org (bga) Date: Fri, 22 Aug 2008 15:03:05 -0000 Subject: [Haiku-bugs] [Haiku] #1128: Backgrounds desktop rightclick menu crash In-Reply-To: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> References: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> Message-ID: <049.8033028a5b13f498b3e2d3bf97a3fca8@haiku-os.org> #1128: Backgrounds desktop rightclick menu crash --------------------------------------+------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by bga): * status: closed => reopened * resolution: invalid => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:03:49 2008 From: trac at haiku-os.org (bga) Date: Fri, 22 Aug 2008 15:03:49 -0000 Subject: [Haiku-bugs] [Haiku] #1128: Backgrounds desktop rightclick menu crash In-Reply-To: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> References: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> Message-ID: <049.6e17e554e393b9dab418bf46f25f0933@haiku-os.org> #1128: Backgrounds desktop rightclick menu crash --------------------------------------+------------------------------------- Reporter: cebif | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by bga): * owner: korli => bga * status: reopened => new Comment: I can reproduce this at will. I am on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:06:03 2008 From: trac at haiku-os.org (bga) Date: Fri, 22 Aug 2008 15:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #1128: Backgrounds desktop rightclick menu crash In-Reply-To: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> References: <040.ef6d6490fa4565e85cc6e18ad04fd591@haiku-os.org> Message-ID: <049.7f6d3624a74fea8483ff7d6f1df151c6@haiku-os.org> #1128: Backgrounds desktop rightclick menu crash --------------------------------------+------------------------------------- Reporter: cebif | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: Fixed on r27153. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:24:03 2008 From: trac at haiku-os.org (diver) Date: Fri, 22 Aug 2008 15:24:03 -0000 Subject: [Haiku-bugs] [Haiku] #2655: [NTFS] Port NTFS file system to Haiku FS API Message-ID: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> #2655: [NTFS] Port NTFS file system to Haiku FS API -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Also ntfs-3g should be updated to the latest version as it contains lots of stablity and security fixes. I would even vote to move it to the Alpha1 as ability to mount ntfs partitions will surely be useful to new users. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:53:40 2008 From: trac at haiku-os.org (diver) Date: Fri, 22 Aug 2008 15:53:40 -0000 Subject: [Haiku-bugs] [Haiku] #2656: [Deskbar] looper must be locked Message-ID: <040.b6d3f8864932ab3c0c20c6292fe69eae@haiku-os.org> #2656: [Deskbar] looper must be locked ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Type in terminal {{{hey application/x-vnd.Be-TSKB 'TmMn'}}} and press Enter. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 18:29:50 2008 From: trac at haiku-os.org (allenb) Date: Fri, 22 Aug 2008 16:29:50 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.7b4065dd4d41d9e87ed339dc04eeb44f@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by allenb): * cc: ben.allen at gmail.com (added) Comment: Replying to [comment:2 bonefish]: > Wikipedia knows the term [http://en.wikipedia.org/wiki/MIT_license MIT license], too. Given the name of our OS, it would be consequent to switch to the basically equivalent [http://en.wikipedia.org/wiki/Poetic_License Poetic License], BTW. :-) Perhaps a more appropriate incarnation might be: Permission granted,[[BR]] Free of charge, to all persons[[BR]] Obtaining these files[[BR]] To use as you like:[[BR]] Copy, share, or modify,[[BR]] Free or for profit[[BR]] Just one condition:[[BR]] All copies must include these[[BR]] License notices.[[BR]] Software provided[[BR]] "As-is", with no warranty[[BR]] Express or implied[[BR]] We have done our best;[[BR]] Damages, problems: we will[[BR]] Not be liable -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 22:16:46 2008 From: trac at haiku-os.org (luroh) Date: Fri, 22 Aug 2008 20:16:46 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.9e632b48bbe5c50f22e7d39e295bcd43@haiku-os.org> #2643: Black screen when DVI connected --------------------------------------+------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by luroh): I have the exact same symptom (the card has 2 x DVI, no VGA). $ lspci -nn | grep VGA 02:00.0 VGA compatible controller [0300]: nVidia Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 22:22:41 2008 From: trac at haiku-os.org (luroh) Date: Fri, 22 Aug 2008 20:22:41 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.448e6acc42c9d76a55fc9d9d051886a1@haiku-os.org> #2643: Black screen when DVI connected --------------------------------------+------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by luroh): Ugh, formatting error, should be: {{{ 02:00.0 VGA compatible controller [0300]: nVidia Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 23:30:16 2008 From: trac at haiku-os.org (aldeck) Date: Fri, 22 Aug 2008 21:30:16 -0000 Subject: [Haiku-bugs] [Haiku] #591: [Deskbar] doesn't redraw it's shelf In-Reply-To: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> References: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> Message-ID: <049.14bd155a6e189598798799d23585a653@haiku-os.org> #591: [Deskbar] doesn't redraw it's shelf -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): I can still reproduce here, r27160, i'll have a look -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 00:30:31 2008 From: trac at haiku-os.org (korli) Date: Fri, 22 Aug 2008 22:30:31 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.6639ce1599247df86a14167b8465f9c2@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r27162 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 02:05:05 2008 From: trac at haiku-os.org (korli) Date: Sat, 23 Aug 2008 00:05:05 -0000 Subject: [Haiku-bugs] [Haiku] #1633: KDL when accessing a file on a CD-ROM In-Reply-To: <041.9ce519cbbcb7dea64f8186cbc8dcd238@haiku-os.org> References: <041.9ce519cbbcb7dea64f8186cbc8dcd238@haiku-os.org> Message-ID: <050.f2da69d2c0de8d9f9a42a34715d320f3@haiku-os.org> #1633: KDL when accessing a file on a CD-ROM ------------------------------------+--------------------------------------- Reporter: vzsolt | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by korli): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 02:14:15 2008 From: trac at haiku-os.org (aldeck) Date: Sat, 23 Aug 2008 00:14:15 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.b9f01394e5c5f25a2fadca20051b88af@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by aldeck): There has been some changes in r27095, is it better? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 02:37:32 2008 From: trac at haiku-os.org (korli) Date: Sat, 23 Aug 2008 00:37:32 -0000 Subject: [Haiku-bugs] [Haiku] #1155: Screen Saver Pref -- Settings aren't detected on-the-fly (easy) In-Reply-To: <041.0f5f080b8434dc83b25c3c28f1fd1622@haiku-os.org> References: <041.0f5f080b8434dc83b25c3c28f1fd1622@haiku-os.org> Message-ID: <050.a7e528ecaef8b2c3f0e6a0f4ea40d59e@haiku-os.org> #1155: Screen Saver Pref -- Settings aren't detected on-the-fly (easy) --------------------------------------+------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by korli): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 04:32:07 2008 From: trac at haiku-os.org (bga) Date: Sat, 23 Aug 2008 02:32:07 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.c51568b67ded37d056ede012dbbc9caf@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): I just confirmed that this also makes the same file be added twice to one index. This messes up the BEOS:APP_SIG index, for example, which makes the Open With menu in Tracker show full paths because it gets the same exacutable twice or more in the index (note it is not 2 exacutables with the same signature, it is the exact same executable twice in the index). Based on all of the above I guess MDR is just doing thing is a way that triggers one of these (in Inode:WritteAttribute): // TODO: we actually depend on that the contents of "buffer" are constant. // If they get changed during the write (hey, user programs), we may mess // up our index trees! // TODO: for attribute files, we need to log the first // BPLUSTREE_MAX_KEY_LENGTH bytes of the data stream, or the same as above // might happen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 10:12:19 2008 From: trac at haiku-os.org (kaliber) Date: Sat, 23 Aug 2008 08:12:19 -0000 Subject: [Haiku-bugs] [Haiku] #2657: Implement XSI shared memory Message-ID: <042.63e95c7db1e6012ade856ec8ab9f688b@haiku-os.org> #2657: Implement XSI shared memory -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- sys/shm.h is missing and not implemented in Haiku. It would be nice to have it. http://www.opengroup.org/onlinepubs/009695399/basedefs/sys/shm.h.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 10:26:53 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 23 Aug 2008 08:26:53 -0000 Subject: [Haiku-bugs] [Haiku] #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest (was: Running bonnie++ 1.03d on Haiku - crashes system) In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.6a0e4899d98f3183c998be1d7300404f@haiku-os.org> #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by emitrax): * owner: axeld => bonefish * milestone: R1 => R1/alpha1 Comment: Ingo, has this been fixed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 10:36:08 2008 From: trac at haiku-os.org (scottmc) Date: Sat, 23 Aug 2008 08:36:08 -0000 Subject: [Haiku-bugs] [Haiku] #2658: Deskbar floating where it should after resolution change Message-ID: <042.71b5142596fc67fa61f04043a3169bc3@haiku-os.org> #2658: Deskbar floating where it should after resolution change -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This happened with r26168. I changed the screen resolution from 1024x768 to 1280x800 and the deskbar stay where it was, instead of moving to the upper right corner like usual. I can move it there manually and it then stays. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 10:48:56 2008 From: trac at haiku-os.org (3dEyes) Date: Sat, 23 Aug 2008 08:48:56 -0000 Subject: [Haiku-bugs] [Haiku] #2655: [NTFS] Port NTFS file system to Haiku FS API In-Reply-To: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> References: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> Message-ID: <049.935fa4fecfc724214cae008fcbd7fc4c@haiku-os.org> #2655: [NTFS] Port NTFS file system to Haiku FS API --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by 3dEyes): I have partially made code on the working computer. Soon I will commit it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:31:36 2008 From: trac at haiku-os.org (diver) Date: Fri, 22 Aug 2008 15:31:36 -0000 Subject: [Haiku-bugs] [Haiku] #2655: [NTFS] Port NTFS file system to Haiku FS API In-Reply-To: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> References: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> Message-ID: <049.261f4556d82d94986ff88e04f20bcff9@haiku-os.org> #2655: [NTFS] Port NTFS file system to Haiku FS API --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by diver): But how about bash and other GPL stuff in /boot/beos/bin folder? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 22 17:27:43 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 22 Aug 2008 15:27:43 -0000 Subject: [Haiku-bugs] [Haiku] #2655: [NTFS] Port NTFS file system to Haiku FS API In-Reply-To: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> References: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> Message-ID: <049.5a66ad3a16d0317cb6c942efa00eff77@haiku-os.org> #2655: [NTFS] Port NTFS file system to Haiku FS API --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): The only problem with that idea is that we can't include it in a default distribution as it's based on GPL licensed code. Ergo you'd still have to build it yourself by enabling GPL add-ons in the build system configuration if you wanted it, but we definitely can't include it out of the box. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 11:44:49 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 09:44:49 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.d0b1ebf02d108bd94911f0f36f3a9e0f@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by diver): Nope, nothing changed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 12:34:42 2008 From: trac at haiku-os.org (rossi) Date: Sat, 23 Aug 2008 10:34:42 -0000 Subject: [Haiku-bugs] [Haiku] #2624: Screen Saver doesn't work In-Reply-To: <040.13d4ed2cadfb6c9cb4514e6071cdd6ee@haiku-os.org> References: <040.13d4ed2cadfb6c9cb4514e6071cdd6ee@haiku-os.org> Message-ID: <049.7b32d8f114e801c6d56863155d564d20@haiku-os.org> #2624: Screen Saver doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Did some further investigation of the issue. The original image create by the build system works fine. This problem only happens on installations done from the original imigae using Installer (booting from the build create haiku-image dd'ed to an usb stick, installing to harddisk). Running mimeset after the Installer quits solves this problem and also fixes the ZipOMatic problem (Ticket 2625). Apperently there seems to be an issue in the Installer, needs further investigation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 12:36:43 2008 From: trac at haiku-os.org (rossi) Date: Sat, 23 Aug 2008 10:36:43 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> Message-ID: <049.f8501f5af0a4ca0ef8e8b7cbc49b3788@haiku-os.org> #2625: ZipOMatic doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Same root cause as Ticket 2624. Suggest to close this ticket, which I cannot do myself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 13:31:35 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 11:31:35 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () Message-ID: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () ----------------------------------+----------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Happens when I clicked Revert button in Keymap preflet (before it was set to Russian. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 13:34:04 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 11:34:04 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files Message-ID: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> #2660: [Trac] can't attach files --------------------------+------------------------------------------------- Reporter: diver | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- I tried to add png image to the #2659 Oops? Trac detected an internal error: Exception: Failed to create unique name: /var/trac/dev.haiku- os.org/attachments/ticket/2659/input_server_bt.100.png There was an internal error in Trac. It is recommended that you inform your local Trac administrator and give him all the information he needs to reproduce the issue. To that end, you could a ticket at this site. The action that triggered the error was: POST: /attachment/ticket/2659/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 13:36:34 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 11:36:34 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () In-Reply-To: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> References: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> Message-ID: <049.7c2c87591c9344bb9cb620d29613798e@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () -----------------------------------+---------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by diver): Can't attach back trace yet, see #2660. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 14:20:12 2008 From: trac at haiku-os.org (korli) Date: Sat, 23 Aug 2008 12:20:12 -0000 Subject: [Haiku-bugs] [Haiku] #1155: Screen Saver Pref -- Settings aren't detected on-the-fly (easy) In-Reply-To: <041.0f5f080b8434dc83b25c3c28f1fd1622@haiku-os.org> References: <041.0f5f080b8434dc83b25c3c28f1fd1622@haiku-os.org> Message-ID: <050.59bd5008643ab7efaf0ac2f21879c41b@haiku-os.org> #1155: Screen Saver Pref -- Settings aren't detected on-the-fly (easy) --------------------------------------+------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r27173. Tested OK. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 14:54:07 2008 From: trac at haiku-os.org (aldeck) Date: Sat, 23 Aug 2008 12:54:07 -0000 Subject: [Haiku-bugs] [Haiku] #591: [Deskbar] doesn't redraw it's shelf In-Reply-To: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> References: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> Message-ID: <049.78813e458c5281da8add56501ab4def4@haiku-os.org> #591: [Deskbar] doesn't redraw it's shelf -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Well i looked at the code, and there's a (~0.5sec) waiting loop in MouseDown to detect the long click. So i would say it is expected that the deskbar can't do anything during that time, or am i missing something? I did a quick rewrite of the long click detection using a separate class/thread that sends "long click" messages to the view, it's cool and working but, before i cleanup and commit, i wonder if there wasn't a simpler solution or if i'm not working around a problem that should get fixed in the first place :-) regards -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 15:59:18 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 23 Aug 2008 13:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.53281052c2e27ea40db6a23b04a71ca3@haiku-os.org> #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:4 emitrax]: > Ingo, has this been fixed? You tell me. :-) I've never run bonnie++ (BTW, how about adding an optional test package?). I've never seen such a crash and Trac doesn't seem to want me to show the stack trace. It may already have been fixed; at least some I/O scheduler related problems have been addressed in the meantime. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 16:14:42 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 23 Aug 2008 14:14:42 -0000 Subject: [Haiku-bugs] [Haiku] #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.c5cb1450e11c032b8b09d9b776314505@haiku-os.org> #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Replying to [comment:5 bonefish]: > Replying to [comment:4 emitrax]: > > Ingo, has this been fixed? > > You tell me. :-) I've never run bonnie++ (BTW, how about adding an optional test package?). I'm not the one working on I/O scheduler. :-) If about "optional test package" you mean bonnie++, it's already included since r26920. >I've never seen such a crash and Trac doesn't seem to want me to show the stack trace. It may >already have been fixed; at least some I/O scheduler related problems have been addressed in >the meantime. Yes, that's why I'm asking. The stack trace shows that it fails in _GetNextUnscheduledRequest with a page fault on 0xdeadbf03, and since some other related ticket have been fixed, I thought this one was fixed too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 16:17:11 2008 From: trac at haiku-os.org (bga) Date: Sat, 23 Aug 2008 14:17:11 -0000 Subject: [Haiku-bugs] [Haiku] #2661: bfs : 1397 : Name in use. Message-ID: <038.20257fe967171de9046defe5319dc750@haiku-os.org> #2661: bfs : 1397 : Name in use. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- These seem to be harmless messages that show on syslog but I guess I manage to track it to what I think is a bug (completely by chance, as I was investigating bug #2614. All the times I am getting this message it is happening when writting the last_modified attribute to files. The reason it does that is because it seems this index does not allow duplicates. This is kinda weird because I see no reason for it not to accept duplicates (a duplicate here is 2 files with the same modification date, which can happen (and, in fact, does) all the time. So I went to check how this is set and I noticed it uses the following code in BPlusTree.cpp to figure if the index allows duplicates or not: BPlusTree.cpp : BPlusTree::SetTo(). {{{ fAllowDuplicates = ((stream->Mode() & S_INDEX_DIR) == S_INDEX_DIR && stream->BlockRun() != stream->Parent()) || (stream->Mode() & S_ALLOW_DUPS) != 0; }}} fAllowDuplicates is initialized by default as being true and is only changed when SetTo() is called. S_ALLOW_DUPS is not set anywhere in the BFS code, stream->Mode() must have S_INDEX_DIR set (either this or the bug is in this point) so it seems the problem is the stream->BlockRun() != stream->Parent() check. What is its intent exactly? And why does it seem it has a different behaviour for last_modified when compared to the behavious in, say, size or name indexes? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 17:49:56 2008 From: trac at haiku-os.org (VinDuv) Date: Sat, 23 Aug 2008 15:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #2489: No boot when HyperThreading is activated In-Reply-To: <041.b2aecae886747a7c51d2dc551386ed43@haiku-os.org> References: <041.b2aecae886747a7c51d2dc551386ed43@haiku-os.org> Message-ID: <050.8cdfabaaef5ac09d9204b4619ddf82c4@haiku-os.org> #2489: No boot when HyperThreading is activated ---------------------------------+------------------------------------------ Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by VinDuv): I used a serial cable to get the serial log. Before rebooting, it just prints : {{{ No APM available. smp: using ACPI to detect MP configuration. }}} (tested with r27178) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 18:46:29 2008 From: trac at haiku-os.org (bga) Date: Sat, 23 Aug 2008 16:46:29 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.98add4d471a5e9a09dd082153762c6f9@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): Just found a reliable way to reproduce at least part of the problem I am seeing. The script attached to this bug will trigger the "Bad data" error problem all the time here in my computer. I was able to track this error down to the fact that there are still entries in the index that point to files that were deleted. Although this is doing that by creating copies of all applications in the apps folder and checking the BEOS:APP_SIG index, it looks like it would happoen even with 7 apps being copied (but not less) and the index problem happens to all indexes (except for name, size, last_modified, which are handled as a special case). If someone else could confirm this bug, that would be much appreciated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 18:48:16 2008 From: trac at haiku-os.org (bga) Date: Sat, 23 Aug 2008 16:48:16 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.369e5447b395de98c6daca7abb52042a@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): Attaching files is not working, so here is the script: {{{ #!/bin/sh APP_SIG_NUM_FILES=`query BEOS:APP_SIG=\* | wc -l` echo "Number of readable files in BEOS:APP_SIG index : $APP_SIG_NUM_FILES" echo -n "Copying /boot/beos/apps/* to ./test ... " mkdir test copyattr -d /boot/beos/apps/* test/. echo "Ok." APP_SIG_NUM_FILES=`query BEOS:APP_SIG=\* | wc -l` echo "Number of readable files in BEOS:APP_SIG index : $APP_SIG_NUM_FILES" APP_SIG_NUM_FILES=`query BEOS:APP_SIG=\* | sort -u | wc -l` echo "Number of unique readable files in BEOS:APP_SIG index : $APP_SIG_NUM_FILES" echo -n "Erasing test dir ... " rm -rf test echo "Ok." # This will generate errors in syslog. The index still contains references to # files that were deleted. The funny thing is that not all files resukts in # errors, whcih means that at least some are correctly removed from the index. APP_SIG_NUM_FILES=`query BEOS:APP_SIG=\* | xargs catattr BEOS:APP_SIG | wc -l` echo "Number of readable files in BEOS:APP_SIG index : $APP_SIG_NUM_FILES" APP_SIG_NUM_FILES=`query BEOS:APP_SIG=\* | xargs catattr BEOS:APP_SIG | sort -u | wc -l` echo "Number of unique readable files in BEOS:APP_SIG index : $APP_SIG_NUM_FILES" }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 18:54:53 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 23 Aug 2008 16:54:53 -0000 Subject: [Haiku-bugs] [Haiku] #2655: [NTFS] Port NTFS file system to Haiku FS API In-Reply-To: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> References: <040.430fa7d0f8e07711a03c56aafd67fcc6@haiku-os.org> Message-ID: <049.e9796a2445165d6c3db3446b9678d007@haiku-os.org> #2655: [NTFS] Port NTFS file system to Haiku FS API --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by anevilyak): Replying to [comment:2 diver]: > But how about bash and other GPL stuff in /boot/beos/bin folder? bash is a little bit different since it links to libroot, which is ok since that lib is LGPL'd anyways (since it draws its heritage from glibc). The ntfs add-on links to the kernel directly, so it's a bit more problematic there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 19:04:18 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 23 Aug 2008 17:04:18 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.a7fc7fe20b832ee71936b1c2580baca4@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): Replying to [comment:7 bga]: > If someone else could confirm this bug, that would be much appreciated. Script tested. I confirm the behavior. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 19:05:49 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 23 Aug 2008 17:05:49 -0000 Subject: [Haiku-bugs] [Haiku] #591: [Deskbar] doesn't redraw it's shelf In-Reply-To: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> References: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> Message-ID: <049.8270664ac8a9d82f9bf3511c2651a9f5@haiku-os.org> #591: [Deskbar] doesn't redraw it's shelf -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by anevilyak): You could also just set up a half second BMessageRunner :) Busy waiting in MouseDown would definitely be an issue though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 20:17:53 2008 From: trac at haiku-os.org (nielx) Date: Sat, 23 Aug 2008 18:17:53 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files In-Reply-To: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> References: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> Message-ID: <049.89a21c44e67559ec77c0ae0dd6dfe49d@haiku-os.org> #2660: [Trac] can't attach files ---------------------------+------------------------------------------------ Reporter: diver | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by nielx): * owner: haiku-web => nielx * status: new => assigned Comment: Please try again now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 21:19:56 2008 From: trac at haiku-os.org (andreasf) Date: Sat, 23 Aug 2008 19:19:56 -0000 Subject: [Haiku-bugs] [Haiku] #2661: bfs : 1397 : Name in use. In-Reply-To: <038.20257fe967171de9046defe5319dc750@haiku-os.org> References: <038.20257fe967171de9046defe5319dc750@haiku-os.org> Message-ID: <047.a8b2e3cd414e7487ef22e67ff709e0c1@haiku-os.org> #2661: bfs : 1397 : Name in use. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by andreasf): * cc: andreas.faerber at web.de (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 21:21:12 2008 From: trac at haiku-os.org (luroh) Date: Sat, 23 Aug 2008 19:21:12 -0000 Subject: [Haiku-bugs] [Haiku] #2662: FAT USB stick problem: "PANIC: could not write back block 7908 (General system error)" Message-ID: <040.e3a242713b471c2c7e20480cfb94f8f3@haiku-os.org> #2662: FAT USB stick problem: "PANIC: could not write back block 7908 (General system error)" -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When double clicking a USB disk (FAT formatted) icon, Haiku panics. cd'ing to the USB stick in the Terminal and then running ls works fine. Running on real hardware (Lenovo T60 laptop), booted from a USB stick, r27178. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 21:32:40 2008 From: trac at haiku-os.org (andreasf) Date: Sat, 23 Aug 2008 19:32:40 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.62bf841d7e2ef778d86a5e7fa31d8ed3@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Warranty disclaimers need to be uppercase to be legally valid in the US, I once read. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 21:35:36 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 19:35:36 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files In-Reply-To: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> References: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> Message-ID: <049.29fa0b772cfa21ae0447f4f8401ec54e@haiku-os.org> #2660: [Trac] can't attach files ---------------------------+------------------------------------------------ Reporter: diver | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): Still same problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 21:36:22 2008 From: trac at haiku-os.org (diver) Date: Sat, 23 Aug 2008 19:36:22 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files In-Reply-To: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> References: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> Message-ID: <049.e3d4f40b6c69d5af4e009e33d249b4b5@haiku-os.org> #2660: [Trac] can't attach files ---------------------------+------------------------------------------------ Reporter: diver | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): Hmm, but attachment with another name works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 23 22:27:30 2008 From: trac at haiku-os.org (andreasf) Date: Sat, 23 Aug 2008 20:27:30 -0000 Subject: [Haiku-bugs] [Haiku] #2649: License name is misleading In-Reply-To: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> References: <042.33c659eca2a11ff5914de20358b44d83@haiku-os.org> Message-ID: <051.cdb6ebdccbc2a7d72aa69ffc183ffa45@haiku-os.org> #2649: License name is misleading ------------------------+--------------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by andreasf): Replying to [comment:4 koki]: > it would be a good idea to (at least try to) get feedback from Michael Phipps on this one, as he (at least) seemed very clear on the choice and he may be able to throw some light into why that choice was made. The BSD License requires the copyrights to be acknowledged in the documentation, whereas the MIT/X11 License does not require them to be mentioned outside the source code. MIT/X11 is therefore regarded as the most liberal open-source license, making it very easy to adopt code in both copylefted and closed-source projects. As an example, with the MIT license someone might adopt Haiku as basis of an in-flight entertainment system without obligation to mention this on-screen or in the manual; BSD would require this but not GPL, while GPL would require them to provide their derived sources whereas BSD and MIT/X11 do not. The Poetic License may be nice to read but I have strong doubts whether its creation involved any lawyer. Creating our own license text would provide the same challenge. Sticking with a widely established license would be easiest and best for new potential users to recognize. If we stated that Haiku was under the Haiku Public License "HPL" then no one would know what that means even if it's text were identical to MIT/X11 License. Anyway, changing {{{MIT}}} to {{{MIT/X11}}} would've been an unproblematic clarification change to apply (non-contential). Changing Haiku's license however should be discussed on the mailing list, not silently decided in a bug ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 00:07:58 2008 From: trac at haiku-os.org (scottmc) Date: Sat, 23 Aug 2008 22:07:58 -0000 Subject: [Haiku-bugs] [Haiku] #2658: Deskbar floating where it should after resolution change In-Reply-To: <042.71b5142596fc67fa61f04043a3169bc3@haiku-os.org> References: <042.71b5142596fc67fa61f04043a3169bc3@haiku-os.org> Message-ID: <051.26e52270f3252e2048ea4dedd42e432a@haiku-os.org> #2658: Deskbar floating where it should after resolution change ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): strange, saw it happen twice with fresh installs of r26168, but not now on r26178. guess this can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 03:24:56 2008 From: trac at haiku-os.org (bga) Date: Sun, 24 Aug 2008 01:24:56 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.bff6cb5f93618caba9e54f732c8cbfce@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): r27180 fixes at least part of this bug (although it can be just hiding a different bug). Will do some more test to see if it fixes the other problems too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 03:44:37 2008 From: trac at haiku-os.org (aldeck) Date: Sun, 24 Aug 2008 01:44:37 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () In-Reply-To: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> References: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> Message-ID: <049.918b917e7159a8e8300a005120940568@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () -----------------------------------+---------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): I could reproduce. With any keymap, just start Keymaps preflet and hit revert. The problem is that revert should be disabled in the first place (i fixed that a few months ago). Clicking revert apparently loads a corrupted keymap, that probably cause the crash. Will have a look. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 04:04:43 2008 From: trac at haiku-os.org (aldeck) Date: Sun, 24 Aug 2008 02:04:43 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () In-Reply-To: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> References: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> Message-ID: <049.8dcd9381c94c1489fd9515d1b1523d44@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () -----------------------------------+---------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): There seem to be a regression, don't know wich revision broke it precisely, but at least r24184 didn't have the bug. r24924 is probably the one but i couldn't verify for sure. I'll check that with Ren?. Crash in Keymap::IsDeadYak()? :-D regards -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 04:33:46 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 24 Aug 2008 02:33:46 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () In-Reply-To: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> References: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> Message-ID: <049.16a89a894b038f619bd5891e720ad00d@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () ---------------------------------+------------------------------------------ Reporter: diver | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * owner: korli => anevilyak * component: Servers/input_server => Preferences/Keymap Comment: On it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 06:13:29 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 24 Aug 2008 04:13:29 -0000 Subject: [Haiku-bugs] [Haiku] #2598: sshd occasionally segfaults on connect (possibly when forking) In-Reply-To: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> References: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> Message-ID: <053.c02dfe4352ef8f815362068e759ade0f@haiku-os.org> #2598: sshd occasionally segfaults on connect (possibly when forking) ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Possibly related, possibly a different bug, but in revisions of the last week or so I've been seeing some new behavior: on large data transfers (read: > 1GB or so), sshd keeps spontaneously terminating itself with the following error message: Disconnecting: Corrupted MAC on input. I haven't seen any changes to the network stack that would influence something like this, and I didn't think the I/O scheduler framework was in any way involved so this one confuses me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 14:05:48 2008 From: trac at haiku-os.org (bga) Date: Sun, 24 Aug 2008 12:05:48 -0000 Subject: [Haiku-bugs] [Haiku] #2663: Telnet seems to be broken. Message-ID: <038.f0945836320eaf6a2a302f6940b3436a@haiku-os.org> #2663: Telnet seems to be broken. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I was trying to use telnet to test my POP3 server. I got connected to it, got the banner but at the first command I tried to send, it got stuck. I am not sure if it sent the command or if it got stuck just after I pressed enter and before sending it. Debugging the main (and only) telnet thread shows this backtrace: (gdb) bt #0 0xffff0102 in ?? () #1 0x00301e95 in select () from /boot/beos/system/lib/libroot.so #2 0x002113c5 in process_rings () #3 0x002147a3 in Scheduler () #4 0x002148eb in telnet () #5 0x0020f270 in tn () #6 0x00210145 in main () (gdb) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 14:06:45 2008 From: trac at haiku-os.org (bga) Date: Sun, 24 Aug 2008 12:06:45 -0000 Subject: [Haiku-bugs] [Haiku] #2663: Telnet seems to be broken. In-Reply-To: <038.f0945836320eaf6a2a302f6940b3436a@haiku-os.org> References: <038.f0945836320eaf6a2a302f6940b3436a@haiku-os.org> Message-ID: <047.c55bb08c08ae33b15be48cd4e97cc8db@haiku-os.org> #2663: Telnet seems to be broken. ---------------------------------+------------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Description changed by bga: Old description: > I was trying to use telnet to test my POP3 server. I got connected to it, > got the banner but at the first command I tried to send, it got stuck. I > am not sure if it sent the command or if it got stuck just after I > pressed enter and before sending it. Debugging the main (and only) telnet > thread shows this backtrace: > (gdb) bt > #0 0xffff0102 in ?? () > #1 0x00301e95 in select () from /boot/beos/system/lib/libroot.so > #2 0x002113c5 in process_rings () > #3 0x002147a3 in Scheduler () > #4 0x002148eb in telnet () > #5 0x0020f270 in tn () > #6 0x00210145 in main () > (gdb) New description: I was trying to use telnet to test my POP3 server. I got connected to it, got the banner but at the first command I tried to send, it got stuck. I am not sure if it sent the command or if it got stuck just after I pressed enter and before sending it. Debugging the main (and only) telnet thread shows this backtrace: {{{ (gdb) bt #0 0xffff0102 in ?? () #1 0x00301e95 in select () from /boot/beos/system/lib/libroot.so #2 0x002113c5 in process_rings () #3 0x002147a3 in Scheduler () #4 0x002148eb in telnet () #5 0x0020f270 in tn () #6 0x00210145 in main () (gdb) }}} -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 14:07:39 2008 From: trac at haiku-os.org (bga) Date: Sun, 24 Aug 2008 12:07:39 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.d528a9ace9b3f2a49ef3a50abcf7633a@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by bga): * owner: axeld => bga * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 14:42:08 2008 From: trac at haiku-os.org (korli) Date: Sun, 24 Aug 2008 12:42:08 -0000 Subject: [Haiku-bugs] [Haiku] #2659: [input_server] crash in Keymap::IsDeadKey () In-Reply-To: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> References: <040.f018426ca2c1821c2986bdf67f1a9b64@haiku-os.org> Message-ID: <049.ec736a515928014b858254388cf04fd8@haiku-os.org> #2659: [input_server] crash in Keymap::IsDeadKey () ---------------------------------+------------------------------------------ Reporter: diver | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by korli): the keymap file seems invalid. I added a check in r27183 to avoid loading this invalid keymap. The invalid keymap could be related to the VM or I/O subsystem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 15:19:30 2008 From: trac at haiku-os.org (bga) Date: Sun, 24 Aug 2008 13:19:30 -0000 Subject: [Haiku-bugs] [Haiku] #2614: Indexes not being correctly maintained. In-Reply-To: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> References: <038.4528d507cf963c22755a70b534347c8a@haiku-os.org> Message-ID: <047.bb4bb21c822c8c7e17609c61d989b088@haiku-os.org> #2614: Indexes not being correctly maintained. -------------------------------+-------------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by bga): * status: assigned => closed * resolution: => fixed Comment: After some extensive testing (who would know downloading emails was a good way to stress-test a file system? :) ) it seems that this is really fixed. Fixed in r27180. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 24 20:12:57 2008 From: trac at haiku-os.org (aldeck) Date: Sun, 24 Aug 2008 18:12:57 -0000 Subject: [Haiku-bugs] [Haiku] #2156: [Keymap] Selecting a user keymap, the Use button is disabled In-Reply-To: <043.218c94ee15f7d0b733c1d01eeae2ba70@haiku-os.org> References: <043.218c94ee15f7d0b733c1d01eeae2ba70@haiku-os.org> Message-ID: <052.a388845b1a8c8ce2c2bf8f747ee4c490@haiku-os.org> #2156: [Keymap] Selecting a user keymap, the Use button is disabled ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by aldeck): * cc: alex at zappotek.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 00:29:02 2008 From: trac at haiku-os.org (julun) Date: Sun, 24 Aug 2008 22:29:02 -0000 Subject: [Haiku-bugs] [Haiku] #2664: Mediaplayer crash after pressing SPACE Message-ID: <040.be7c17e08b2ea820ea1f6c7e8a51888d@haiku-os.org> #2664: Mediaplayer crash after pressing SPACE -----------------------+---------------------------------------------------- Reporter: julun | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- * open Mediaplayer without any files * press SPACE, MediaPlayer will crash It happens most likely in PlaybackManager::_StateAt(...) while called with invalid index. See attached screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 02:40:55 2008 From: trac at haiku-os.org (anevilyak) Date: Mon, 25 Aug 2008 00:40:55 -0000 Subject: [Haiku-bugs] [Haiku] #2664: Mediaplayer crash after pressing SPACE In-Reply-To: <040.be7c17e08b2ea820ea1f6c7e8a51888d@haiku-os.org> References: <040.be7c17e08b2ea820ea1f6c7e8a51888d@haiku-os.org> Message-ID: <049.a25c7a5b2a09ad0bbc06b2a9ac566f00@haiku-os.org> #2664: Mediaplayer crash after pressing SPACE ---------------------------------------+------------------------------------ Reporter: julun | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by anevilyak): * status: new => closed * resolution: => fixed * component: - General => Applications/MediaPlayer Comment: Fixed in r27194. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 07:13:29 2008 From: trac at haiku-os.org (tonestone57) Date: Mon, 25 Aug 2008 05:13:29 -0000 Subject: [Haiku-bugs] [Haiku] #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.d1a5a85e350dfa6fd449c6e7b850cdae@haiku-os.org> #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by tonestone57): Just finished testing bonnie++ on revision 27189 The test finished without any errors. Ran both single and multi-process tests. Looks like Haiku is stable once again. Well done. This bug seems to have been fixed with one of the revisions and can now be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 09:46:03 2008 From: trac at haiku-os.org (jackburton) Date: Mon, 25 Aug 2008 07:46:03 -0000 Subject: [Haiku-bugs] [Haiku] #2625: ZipOMatic doesn't work In-Reply-To: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> References: <040.a8072caa0ac7ee1529c74cde754f74be@haiku-os.org> Message-ID: <049.440c68f9acd4c1b8a2061e46e0ce80b5@haiku-os.org> #2625: ZipOMatic doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: Closing as dup of #2624. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 12:01:21 2008 From: trac at haiku-os.org (jackburton) Date: Mon, 25 Aug 2008 10:01:21 -0000 Subject: [Haiku-bugs] [Haiku] #1319: [Tracker] desktop icons selection is shifted 1px to the left In-Reply-To: <040.bef90aba15345c94303c110fc6ac4fcf@haiku-os.org> References: <040.bef90aba15345c94303c110fc6ac4fcf@haiku-os.org> Message-ID: <049.a9c8ad23ddd309c19820c0072295cdcb@haiku-os.org> #1319: [Tracker] desktop icons selection is shifted 1px to the left ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): I had a look at this. Removing the + 1 in the following code: BPoint loc; loc.y = textRect.bottom - view->FontInfo().descent; loc.x = textRect.left + 1; in TextWidget.cpp, BTextWidget::Draw(), fixes the problem. But again, since the selection isn't as shifted in beos as it is on haiku, I think the problem could be more what I wrote in comment 6. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 12:37:42 2008 From: trac at haiku-os.org (PieterPanman) Date: Mon, 25 Aug 2008 10:37:42 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) Message-ID: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ---------------------------------------------+------------------------------ Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Attached is a patch that fixes the problem with the device type in the listdev output. See this line: {{{ device Unclassified device (Non-VGA unclassified device) [0|0|0] }}} For some reason the relevant attributes are now B_UINT16_TYPE instead of B_UINT8_TYPE. It checked for the attribute name and type, so when the type did not match, the true value was not used, but the default 0 was used. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 13:11:47 2008 From: trac at haiku-os.org (andreasf) Date: Mon, 25 Aug 2008 11:11:47 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) In-Reply-To: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> References: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> Message-ID: <056.c2bae212a0a46b5fc1ed69c9b8d34333@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ----------------------------------------------+----------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by andreasf): * cc: andreas.faerber at web.de (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 14:03:43 2008 From: trac at haiku-os.org (jackburton) Date: Mon, 25 Aug 2008 12:03:43 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) In-Reply-To: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> References: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> Message-ID: <056.48c572bb90c080c78cd25c95b5114ab9@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ----------------------------------------------+----------------------------- Reporter: PieterPanman | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by jackburton): * owner: axeld => jackburton Comment: Tested ok. Committing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 14:05:41 2008 From: trac at haiku-os.org (jackburton) Date: Mon, 25 Aug 2008 12:05:41 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) In-Reply-To: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> References: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> Message-ID: <056.b2cd7a01f90bc04bc8aa194ab62cbfee@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ----------------------------------------------+----------------------------- Reporter: PieterPanman | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by jackburton): On second thought... how come the types are B_UINT16_TYPE but the code reads pci_class_api_id = attr.value.ui8 ? Shouldn't we change it to attr.value.ui16 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 14:10:35 2008 From: trac at haiku-os.org (PieterPanman) Date: Mon, 25 Aug 2008 12:10:35 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) In-Reply-To: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> References: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> Message-ID: <056.17eccac37d4e094700357239198aa232@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ----------------------------------------------+----------------------------- Reporter: PieterPanman | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by PieterPanman): I was just typing a message about this, yes, that doesn't make sense at all! If we do that, we should also change their declarations to '''uint16''': {{{ uint8 pci_class_base_id = 0; uint8 pci_class_sub_id = 0; uint8 pci_class_api_id = 0; }}} I'm not sure about the underlying reason for the change of uint8 to uint16, but we should change all 3 properly. Sorry about that :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 14:21:41 2008 From: trac at haiku-os.org (jackburton) Date: Mon, 25 Aug 2008 12:21:41 -0000 Subject: [Haiku-bugs] [Haiku] #2666: listdev does not list the device types anymore (patch) In-Reply-To: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> References: <047.fa59fd35ea6debce3482b4dde308d9c4@haiku-os.org> Message-ID: <056.d43cd346054436f078f7db148e08da0a@haiku-os.org> #2666: listdev does not list the device types anymore (patch) ----------------------------------------------+----------------------------- Reporter: PieterPanman | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Applied (with the above changes) in r27195. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 16:46:17 2008 From: trac at haiku-os.org (bga) Date: Mon, 25 Aug 2008 14:46:17 -0000 Subject: [Haiku-bugs] [Haiku] #2624: Screen Saver doesn't work In-Reply-To: <040.13d4ed2cadfb6c9cb4514e6071cdd6ee@haiku-os.org> References: <040.13d4ed2cadfb6c9cb4514e6071cdd6ee@haiku-os.org> Message-ID: <049.91eab487cafe834345d3577fbdf88e9f@haiku-os.org> #2624: Screen Saver doesn't work ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by bga): Didn't look at the installer code, but it is possible that it is not creating required indexes (like BEOS:APP_SIG) on the target partition before starting copying the files. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 18:33:14 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 16:33:14 -0000 Subject: [Haiku-bugs] [Haiku] #2131: AMD Geode Video controller needs a driver In-Reply-To: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> References: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> Message-ID: <051.e15778cf939a242080d0d59c0439665b@haiku-os.org> #2131: AMD Geode Video controller needs a driver -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by scottmc): This can be moved to low priority and dropped from R1 milestone as it's not a requirement, just a "would be nice to have". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 18:33:08 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 16:33:08 -0000 Subject: [Haiku-bugs] [Haiku] #2474: Serial port driver needed for Oxford Semi UART 16950 In-Reply-To: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> References: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> Message-ID: <051.e675b922dfc160ef571e3f5bf6bc8939@haiku-os.org> #2474: Serial port driver needed for Oxford Semi UART 16950 --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): This can be moved to low priority and dropped from R1 milestone as it's not a requirement, just a "would be nice to have". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 18:35:54 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 16:35:54 -0000 Subject: [Haiku-bugs] [Haiku] #1504: Enable USB -> RS-232 Serial port adapter on startup to allow for serial debugging In-Reply-To: <042.7c70faf4ac1b2ffaff4b5e0d484a792f@haiku-os.org> References: <042.7c70faf4ac1b2ffaff4b5e0d484a792f@haiku-os.org> Message-ID: <051.804142dde7b2f97d3b6e7b0699a7ffb3@haiku-os.org> #1504: Enable USB -> RS-232 Serial port adapter on startup to allow for serial debugging --------------------------+------------------------------------------------- Reporter: scottmc | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): This can be moved to low priority and dropped from R1 milestone as it's not a requirement, just a "would be nice to have". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 18:54:04 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 16:54:04 -0000 Subject: [Haiku-bugs] [Haiku] #2132: AMD Geode Audio controller needs a driver In-Reply-To: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> References: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> Message-ID: <051.2107a22ad6a3457accce89177e688eb7@haiku-os.org> #2132: AMD Geode Audio controller needs a driver ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by scottmc): Here's a link to the datasheet for the CS5536 chip that contains the audio device for the Geode platform: http://www.amd.com/files/connectivitysolutions/geode/geode_lx/33238G_cs5536_db.pdf My guess is that it isn't much different than the CS5530. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 18:57:12 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 16:57:12 -0000 Subject: [Haiku-bugs] [Haiku] #2131: AMD Geode Video controller needs a driver In-Reply-To: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> References: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> Message-ID: <051.92c7ddd395fc222e0f5464f2bb76cc16@haiku-os.org> #2131: AMD Geode Video controller needs a driver -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by scottmc): For future reference, here's a link to the AMD datasheet for the Geode, which has the video built into the processor. http://www.amd.com/files/connectivitysolutions/geode/geode_lx/33234G_LX_databook.pdf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:06:56 2008 From: trac at haiku-os.org (julun) Date: Mon, 25 Aug 2008 17:06:56 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.d700e7686ea6dde650a8e757af7055a0@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, I've created an version of LinkSender/Receiver using an area to pass data arround the exceeds the max buffer size. I'm not sure if i leak the area in LinkSender. If someone has the time, please review. Thanks Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:07:09 2008 From: trac at haiku-os.org (stippi) Date: Mon, 25 Aug 2008 17:07:09 -0000 Subject: [Haiku-bugs] [Haiku] #1504: Enable USB -> RS-232 Serial port adapter on startup to allow for serial debugging In-Reply-To: <042.7c70faf4ac1b2ffaff4b5e0d484a792f@haiku-os.org> References: <042.7c70faf4ac1b2ffaff4b5e0d484a792f@haiku-os.org> Message-ID: <051.58bec4a200e55fa3f22e6b7893e44a65@haiku-os.org> #1504: Enable USB -> RS-232 Serial port adapter on startup to allow for serial debugging --------------------------+------------------------------------------------- Reporter: scottmc | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by stippi): * milestone: R1 => Unscheduled -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:21:37 2008 From: trac at haiku-os.org (stippi) Date: Mon, 25 Aug 2008 17:21:37 -0000 Subject: [Haiku-bugs] [Haiku] #2474: Serial port driver needed for Oxford Semi UART 16950 In-Reply-To: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> References: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> Message-ID: <051.14d5bd85c553c5284ae1137a7d2e2347@haiku-os.org> #2474: Serial port driver needed for Oxford Semi UART 16950 --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by stippi): * milestone: R1 => Unscheduled -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:41:16 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 17:41:16 -0000 Subject: [Haiku-bugs] [Haiku] #1400: Add nasm as an available buildsystem tool. In-Reply-To: <041.012af30dc4cbc5d5273ddc4fef877a32@haiku-os.org> References: <041.012af30dc4cbc5d5273ddc4fef877a32@haiku-os.org> Message-ID: <050.3a58c7b875de6b9eea3de826523a2155@haiku-os.org> #1400: Add nasm as an available buildsystem tool. ---------------------------+------------------------------------------------ Reporter: stippi | Owner: bonefish Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by scottmc): Might yasm fit the need here? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:42:42 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 17:42:42 -0000 Subject: [Haiku-bugs] [Haiku] #2132: AMD Geode Audio controller needs a driver In-Reply-To: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> References: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> Message-ID: <051.4231df10bff357398c82a28eb266ead3@haiku-os.org> #2132: AMD Geode Audio controller needs a driver ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by scottmc): This can also be removed from the R1 milestone. I'll check into getting hardware, but no promises. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 20:16:53 2008 From: trac at haiku-os.org (laplace) Date: Mon, 25 Aug 2008 18:16:53 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.7ef845db82f3b2036e314d1595ee4ed4@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by laplace): In line 126 and 131 of your patch you have removed the space after "for" statement, and inside the space after each semicolon is also missing. Why have you removed "new (std::nothrow)" in line 123, 124. This will leak opList, if an exception is thrown when allocation of ptList fails? Either that or if exceptions are disabled, a null pointer access could happen, if memory allocation did fail. Maybe you could use class AutoDeleter (or whatever it is called) to delete the buffers automatically that are for example allocated in line 976 or 1014. Otherwise it looks good as far as I can tell, besides in rare cases the area could be leaked on receiver side, if the receiver dies before it can delete the area. In order to fix that, the sender side somehow needs to keep track of the opened areas and delete them after the receiver has died. BTW is the sender == app_server? The sender also has to be notified, when the receiver deletes the area, so that the sender does not delete it twice. Could be a problem, if the area_id has be reused for a new area. I don't know how likely that is. In case of bad performance an area cache might be necessary too? Does printing from ShowImage work now, BTW? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 20:29:36 2008 From: trac at haiku-os.org (korli) Date: Mon, 25 Aug 2008 18:29:36 -0000 Subject: [Haiku-bugs] [Haiku] #2132: AMD Geode Audio controller needs a driver In-Reply-To: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> References: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> Message-ID: <051.25b56bf371488bcb35f12d4da1042b7f@haiku-os.org> #2132: AMD Geode Audio controller needs a driver ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: Component: Drivers/Audio | Version: Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * version: R1 development => * milestone: R1 => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 20:34:32 2008 From: trac at haiku-os.org (korli) Date: Mon, 25 Aug 2008 18:34:32 -0000 Subject: [Haiku-bugs] [Haiku] #2132: AMD Geode Audio controller needs a driver In-Reply-To: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> References: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> Message-ID: <051.7cb420f4044f8eed39549a5f4fc9fdc1@haiku-os.org> #2132: AMD Geode Audio controller needs a driver ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: Component: Drivers/Audio | Version: Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): http://alumni.cse.ucsc.edu/~brucem/gx_audio/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 20:56:02 2008 From: trac at haiku-os.org (julun) Date: Mon, 25 Aug 2008 18:56:02 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.34fd26e601b39c81ccf0e6a293ae2dd0@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, I'm sorry for the confusing patch. i made the diff with an not up to date version of my tree. I will add a new one ASAP, also without those whitespaces for easyer review. With this patch printing works fine from ShowImage. Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 21:32:18 2008 From: trac at haiku-os.org (Begasus) Date: Mon, 25 Aug 2008 19:32:18 -0000 Subject: [Haiku-bugs] [Haiku] #2667: Loading graphic files in SDL games Message-ID: <042.438657afebea7038bcc56955fa483155@haiku-os.org> #2667: Loading graphic files in SDL games -----------------------+---------------------------------------------------- Reporter: Begasus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- With the latest Haiku builds I'm not able to play games like TuxPaint, blobwars freeciv etc. Problem I get is that it can't open/load a graphic file. This is been done with freshly compiled Haiku from svn, SDL libs etc compiled myself in Haiku, the ones from haikuports etc .. all with no luck loading the graphic file (or in case of xrick a zip container). Games are compiled in Haiku itself also (and used zips that worked before). I'll add a file with the crash info over Terminal and a debug output from tuxpaint. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 21:42:22 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 19:42:22 -0000 Subject: [Haiku-bugs] [Haiku] #2667: Loading graphic files in SDL games In-Reply-To: <042.438657afebea7038bcc56955fa483155@haiku-os.org> References: <042.438657afebea7038bcc56955fa483155@haiku-os.org> Message-ID: <051.4c2b7a9d13060070457c686c5626d0b0@haiku-os.org> #2667: Loading graphic files in SDL games ------------------------+--------------------------------------------------- Reporter: Begasus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): I was able to compile and run pipepanic a few days ago and didn't have any issues with it. Looking at the output for the can't locate file errors, you'll see the path has a // in it, that would be your problem right there. Trick is figuring out why it's coming out like that. {{{ /boot/apps/Games/TuxMath//share/tuxmath/images/status/standby.png 121 The Simple DirectMedia error that occured was: 122 No such file or directory }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 21:43:28 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 19:43:28 -0000 Subject: [Haiku-bugs] [Haiku] #2667: Loading graphic files in SDL games In-Reply-To: <042.438657afebea7038bcc56955fa483155@haiku-os.org> References: <042.438657afebea7038bcc56955fa483155@haiku-os.org> Message-ID: <051.92436a95e7900cbf97f4ea65c9a74a94@haiku-os.org> #2667: Loading graphic files in SDL games ------------------------+--------------------------------------------------- Reporter: Begasus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by scottmc): * cc: haiku at scottmc.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 22:36:49 2008 From: trac at haiku-os.org (tigerdog) Date: Mon, 25 Aug 2008 20:36:49 -0000 Subject: [Haiku-bugs] [Haiku] #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly In-Reply-To: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> References: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> Message-ID: <050.5baa4a1f1cc9e543cdc2019add1081b5@haiku-os.org> #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Comment(by tigerdog): I have the same issue with a Logitech S510 wireless keyboard feeding UHCI USB on ECS KN1 Lite motherboard, nVidia nForce4 ultra chipset. A second wireless receiver for a logitech G7 mouse is also attached. Mainboard has "USB keyboard" emulation set to "Y" so KB is active during bootup. If I type more than 3 characters per second, one of two things happens: - characters are dropped (not shown when typed) - characters repeat until another key is pressed. Happens both in the middle of words or after typing ceases. The problem happens when wireless receiver is directly attached to the computer. Problem is worse when connected to KVM and USB extension. I use this same hardware setup KB, receiver, KVM, cable) for R5, R5+BONE, Zeta 1.21 and 1.5, Xubuntu 8.10 and Win2K (Be Bootman) with no trouble. Only Haiku has issues. This is the main thing keeping me from using Haiku as my main OS at this time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 23:28:21 2008 From: trac at haiku-os.org (julun) Date: Mon, 25 Aug 2008 21:28:21 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.39c11c71e3c4671f3ad3e6bcb1161f5a@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, here is an updated one, I don't know why the first one showed all those strange removal stuff. Hope this one is easyer to review. Thanks for the comments so far. :) Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 01:02:03 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 25 Aug 2008 23:02:03 -0000 Subject: [Haiku-bugs] [Haiku] #1527: Selecting an area on the desktop leaves ghostlines In-Reply-To: <042.707491492d3c5dfcbc5a423133096d6e@haiku-os.org> References: <042.707491492d3c5dfcbc5a423133096d6e@haiku-os.org> Message-ID: <051.044a65aedb6697fd2c4983a48933da9f@haiku-os.org> #1527: Selecting an area on the desktop leaves ghostlines ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by scottmc): I suspect what we are seeing here is caused by being off grid? That perhaps where the click-drag window was started from isn't exactly on an integer coordinate, but off by some fractional number. Maybe only dragging this click drag box using integers, (or floats without a decimal if you will) would take care of it? That might explain why we only see it happen in certain directions, could be a subtraction error on the undraw part of the code? By by keeping it on an interger(-like) grid you might be able to fix it? Just a thought. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 03:25:14 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 26 Aug 2008 01:25:14 -0000 Subject: [Haiku-bugs] [Haiku] #2658: Deskbar floating where it should after resolution change In-Reply-To: <042.71b5142596fc67fa61f04043a3169bc3@haiku-os.org> References: <042.71b5142596fc67fa61f04043a3169bc3@haiku-os.org> Message-ID: <051.30b873f7e33034a1bba3bc82b7d3e113@haiku-os.org> #2658: Deskbar floating where it should after resolution change ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): This bug is still there. I compiled an SDL demo program and when I run it, it changes the screen resolution ( 800x600 i think) and when I press ESC to exit that program the screen resolution switches back to 1280x800 and leaves the deskbar in about the middle top of the screen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 04:52:33 2008 From: trac at haiku-os.org (katisu) Date: Tue, 26 Aug 2008 02:52:33 -0000 Subject: [Haiku-bugs] [Haiku] #2532: Video/Audio on Dell Latitude LS :( In-Reply-To: <042.083503791c860b07774e8d36dacea3a0@haiku-os.org> References: <042.083503791c860b07774e8d36dacea3a0@haiku-os.org> Message-ID: <051.c02f278e871a7c2c3d93757961bc06e3@haiku-os.org> #2532: Video/Audio on Dell Latitude LS :( ----------------------------------------+----------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------------------+----------------------------------- Changes (by katisu): * cc: katisu at comcast.net (added) Comment: I had this problem some time ago when testing opensound on my Dell Latitude CPiA. From discussing with Francois this is an issue of the memory layout in this chipset. Opensound is not written with the Haiku Neomagic driver in mind. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 08:14:28 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 26 Aug 2008 06:14:28 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.f6d1049e9a5c2f5e511b5d7b995b6139@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Ah, yes! That looks very nice, indeed! Moreover, done this way, it will also solve other problems related to big transfers between app_server and libbe (just check Window.cpp). Good work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 08:21:49 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 26 Aug 2008 06:21:49 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.32be213e4f0d18e91fdac50385918d80@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): One more comment, besides what Michael already wrote: since resize_area() can fail, you should check its return value too. And in case it happens, I guess you could try to delete and re-create the area. Thanks for your work, btw! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 08:28:35 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 26 Aug 2008 06:28:35 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.dce9334225e1c25ba8110ecee65fd0fb@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Replying to [comment:16 jackburton]: > Ah, yes! That looks very nice, indeed! > Moreover, done this way, it will also solve other problems related to big transfers between app_server and libbe (just check Window.cpp). Sorry, it's in View.cpp (for example, BView::FillShape()) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 09:49:52 2008 From: trac at haiku-os.org (stippi) Date: Tue, 26 Aug 2008 07:49:52 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.8794831bfa64810a4f6e82372339da0b@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): The new patch looks good to me, only you need to use new (std::nothrow) in the first part of the patch (two places) and check the returned pointer. Return B_NO_MEMORY if it's NULL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 10:58:34 2008 From: trac at haiku-os.org (stippi) Date: Tue, 26 Aug 2008 08:58:34 -0000 Subject: [Haiku-bugs] [Haiku] #1527: Selecting an area on the desktop leaves ghostlines In-Reply-To: <042.707491492d3c5dfcbc5a423133096d6e@haiku-os.org> References: <042.707491492d3c5dfcbc5a423133096d6e@haiku-os.org> Message-ID: <051.3479a871b145dd6c32613ee09655202d@haiku-os.org> #1527: Selecting an area on the desktop leaves ghostlines ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): Unfortunately, that's not it. The scary part is that if you only keep dragging many times enough, the bug will "go away" by itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 12:55:45 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 10:55:45 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. Message-ID: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> #2668: Haiku's partition map representation looks weird. ---------------------------+------------------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ This is more obvious when looking at DriveSetup but I think the problem is in our disk manager. For example, I have this 500 Gb disk it has one single primary partition created (465.8 Gb of usable size). But due to what is probably some kind of block alignment, there is a bit of free space before the partition (around 5 kb) and this is reported as a different partition in Haiku. So I have: /dev/disk/ata/1/slave/raw /dev/disk/ata/1/slave/0 /dev/disk/ata/1/slave/0_0 The 0_0 one is the 5 Kb partition. Although it is there, it is not reported by any other OS (not Linux nor Windows) that I have in the same machine. With DriveSetup it even looks a bit weirder as it markes the partition exactly like it would mark a extended/logical partition so the /0 partition (the real 465.8 Gb one) looks like it is a logical partition and it is not. Is this intended; This can get things confusing I guess. What if when DriveSetup can create partitions people try to remove that 0_0 partition? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 13:57:41 2008 From: trac at haiku-os.org (julun) Date: Tue, 26 Aug 2008 11:57:41 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.42134a043f3cb1f209451081c34987c0@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi all, thanks for the comments. I have integrated them so far and reduced a bit of the code also. If you agree on that patch i will commit it later today. Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 16:27:53 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 14:27:53 -0000 Subject: [Haiku-bugs] [Haiku] #2667: Loading graphic files in SDL games In-Reply-To: <042.438657afebea7038bcc56955fa483155@haiku-os.org> References: <042.438657afebea7038bcc56955fa483155@haiku-os.org> Message-ID: <051.4b2ab6a7e8caf6e2137924b32be21696@haiku-os.org> #2667: Loading graphic files in SDL games ------------------------+--------------------------------------------------- Reporter: Begasus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by bga): Actually, that works in terminal at least: mkdir -p xxx/yyy/zzz touch xxx/yyy/zzz/file echo "Test" >> xxx/yyy/zzz/file cat xxx/yyy//zzz/file Test -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 19:52:06 2008 From: trac at haiku-os.org (rossi) Date: Tue, 26 Aug 2008 17:52:06 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load Message-ID: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> #2669: scsi scheduler takes 100% cpu load -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The scsi scheduler threads suddenly sucks all cpu cycles (100% cpu usage) and in 30% of all cases causes a complete system freeze sooner or later, however never recovers from the 100% load. This happens on r27208 during installation from an usb stick (from which the system has been booted). It does take different amounts of time with each install trial, before the effect takes place. In 1 out of roughly 15 tries I actually managed a complete install before the system went bananas. This behaviour was not present with the previous builds (from before Sunday). Rossi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 19:57:27 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 26 Aug 2008 17:57:27 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.9a571ad33df079fe73c322d3d3d34c4c@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * component: - General => System/Kernel Comment: This looks like a duplicate of ticket #2604. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 20:07:15 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 26 Aug 2008 18:07:15 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.217e62a2866e0181be70e0c87e5180ce@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): It's actually a different bug and I was just going to open a bug about this. It seems it has been introduced lately. The CPU in this case goes to 100% and the scsi scheduler is the only thread eating up the CPU. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 20:33:20 2008 From: trac at haiku-os.org (rossi) Date: Tue, 26 Aug 2008 18:33:20 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.3da2b6f76ae609b946023c1c0124f1da@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by rossi): Actually I'm pretty sure that this issue didn't exist with my previous build (was done on sunday based on sundays repository head revision) don't remember the revision number. Besides the installation, the svn update caused this to happen as well and to my bad luck trashed the source tree beyond cleanup's capabilities ;-( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 22:30:56 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 20:30:56 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.a8e3c3c0e906c819f512995092e09e6c@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): I actually got that too when checking out the sources under VMWare. System became completely unusable and eventually completely locked up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 23:04:30 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 26 Aug 2008 21:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.15b0769547e584bdde322a13a490c464@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Please attach the sector 0 of your HD and the first sector of the extended partition (the ".../0"). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Aug 26 23:11:41 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 26 Aug 2008 21:11:41 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.8d227ef1a81fdd3a16550b742a8e4495@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish Comment: I'm in the process of implementing an actual I/O scheduling algorithm. That might also fix this issue. If not, I'll look into afterwards. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:01:25 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 26 Aug 2008 22:01:25 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.f1a04531fbaff1fc171a30ee5e9fba82@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): I actually get a somewhat strange list of partitions from Installer here as well, though I'm not certain if that's a matter of Installer not filtering what it gets back from the disk system properly, or the disk manager weirdly interpreting the partition map. Specifically, I get: {{{ (null) - 186.3GB (Intel Partition Map) [(null) partition: 0] null (0B) [(null)] [/dev/disk/ata/3/master/raw partition: 2] Haiku - 18.6GB [Be File System] [/dev/disk/ata/3/master/raw partition: 3] HaikuData - 148.2GB [Be File System] [/dev/disk/ata/3/master/raw partition: 4] }}} On the command line, Installer presents the following output: {{{ SourceVisitor::Visit(BPartition *) : /dev/disk/ata/3/master/1 SourceVisitor::Visit(BPartition *) : (null) ScanDisksPartitions partitions begin TargetVisitor::Visit(BDiskDevice *) : /dev/disk/ata/3/master/raw TargetVisitor::Visit(BPartition *) : /dev/disk/ata/3/master/0 TargetVisitor::Visit(BPartition *) : (null) TargetVisitor::Visit(BPartition *) : /dev/disk/ata/3/master/1 TargetVisitor::Visit(BPartition *) : (null) TargetVisitor::Visit(BPartition *) : /dev/disk/ata/3/master/2 TargetVisitor::Visit(BPartition *) : (null) }}} According to FreeBSD's fdisk, the partition map is: {{{ ******* Working on device /dev/ad6 ******* parameters extracted from in-core disklabel are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 40949622 (19994 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 235 (0xeb),(BeOS file system) start 40949685, size 39070080 (19077 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 235 (0xeb),(BeOS file system) start 80019765, size 310697100 (151707 Meg), flag 0 beg: cyl 1023/ head 254/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: }}} Is this related to Bruno's issue, or should I file a separate bug against Installer for this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:06:36 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 22:06:36 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.ec44246422ceab904addc46480feab50@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): Added the requested data. There are 3 files in the zip file: raw.bin (HD's sector 0). 0.bin (First sector of partition identified as /0) 0_0.bin (Just added this for completeness. First sector of partition identified as /0_0). Let me know if you need anything else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:19:05 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 22:19:05 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.055d02f770dc7bc2d82e38385501e571@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by bga): * status: closed => reopened * resolution: fixed => Comment: Sorry for taking this long to check this but it is still not working. when the input_server restarts the mouse is dead. Again, unplugging and pluging it again make it start working. No messages in syslog whatsoever. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:22:17 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 22:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #2670: Directories created using Tracker have wrong permissions. Message-ID: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> #2670: Directories created using Tracker have wrong permissions. ----------------------------------+----------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- When a directory is created through Tracker, its permissions bits are set to 777. Maybe it is not respecting the default umask? Anyway, creating a directory through the terminal creates it with permissions 644, which are more like it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:27:18 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 26 Aug 2008 22:27:18 -0000 Subject: [Haiku-bugs] [Haiku] #2670: Directories created using Tracker have wrong permissions. In-Reply-To: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> References: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> Message-ID: <047.c1b8f7d2f80ccfee1be2519c198e2a6d@haiku-os.org> #2670: Directories created using Tracker have wrong permissions. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by anevilyak): How is that incorrect? Directories use the execute bit to indicate that traversal is allowed. If anything, 755 or 777 would be correct, 644 is definitely not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:29:01 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 22:29:01 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.2e4548ab844283e3465aa7900bbf8a5a@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: reopened Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by bga): * status: closed => reopened * resolution: fixed => Comment: I am reopening this just because I think this fix broke something else. Now the key combos inside SpicyKeys are not wqorking. Left-Windows + G, for example, was supposed to open the home dir but it is not doing that (it was before). Instead, it seems it is generating a diferent keycode because if the Terminal has the focus, for example, the cursor will move as if space was hit). In fact, I am pretty sure it is generating the space scan code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:38:39 2008 From: trac at haiku-os.org (bga) Date: Tue, 26 Aug 2008 22:38:39 -0000 Subject: [Haiku-bugs] [Haiku] #2670: Directories created using Tracker have wrong permissions. In-Reply-To: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> References: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> Message-ID: <047.aba21ba1a24fc0de0e2bd1c270a53bc8@haiku-os.org> #2670: Directories created using Tracker have wrong permissions. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bga): Yes, I meant to say 755 and they are created with 777. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 00:50:05 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 26 Aug 2008 22:50:05 -0000 Subject: [Haiku-bugs] [Haiku] #2670: Directories created using Tracker have wrong permissions. In-Reply-To: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> References: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> Message-ID: <047.7e0a59ee0ca0d30996800bb9bd486ca3@haiku-os.org> #2670: Directories created using Tracker have wrong permissions. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by anevilyak): From a quick glance, FSCreateNewFolder just uses BDirectory::CreateDirectory(), which does indeed hardcode the permissions: {{{ // create the dir status_t error = _kern_create_dir(fDirFd, path, S_IRWXU | S_IRWXG | S_IRWXO); }}} Where are you expecting it to pick up the permissions from? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 01:15:49 2008 From: trac at haiku-os.org (stippi) Date: Tue, 26 Aug 2008 23:15:49 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.aa574de495a6bb6ddc034f913a109ba5@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: new Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): You are leaking the first buffer in the error case. Looks fine otherwise, but I kind of looked in a hurry... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 02:31:42 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 00:31:42 -0000 Subject: [Haiku-bugs] [Haiku] #2670: Directories created using Tracker have wrong permissions. In-Reply-To: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> References: <038.c68a5ebbb76247627c9709c68a2f8b6c@haiku-os.org> Message-ID: <047.1facd3fe57da8187707a871a97a4130f@haiku-os.org> #2670: Directories created using Tracker have wrong permissions. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bga): How about doing the same as mkdir? http://dev.haiku-os.org/browser/haiku/trunk/src/bin/coreutils/src/mkdir.c -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 03:20:03 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 27 Aug 2008 01:20:03 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.80eb419b50c35a3735ab11331e98d109@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): I doubt that's the thread scheduler's fault...I've had 100% CPU usage in plenty of things and the sys was still responsive on one CPU. More likely some locks are being held while that thread loops that result in everything else blocking eventually. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 10:24:23 2008 From: trac at haiku-os.org (nielx) Date: Wed, 27 Aug 2008 08:24:23 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files In-Reply-To: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> References: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> Message-ID: <049.e901543d1f23c109c0fc61c319d25b3b@haiku-os.org> #2660: [Trac] can't attach files ---------------------------+------------------------------------------------ Reporter: diver | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by nielx): * status: assigned => closed * resolution: => fixed Comment: I'll close this ticket now. I have deleted the old file with the name that was taken, and I know how this happened. The fix is still in the works (albeit currently not yet done). N. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 10:44:07 2008 From: trac at haiku-os.org (denisw) Date: Wed, 27 Aug 2008 08:44:07 -0000 Subject: [Haiku-bugs] [Haiku] #1874: VIA Rhine-II not working In-Reply-To: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> References: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> Message-ID: <051.3cc61f1378c7cc7817d6cf9b47ed9f1f@haiku-os.org> #1874: VIA Rhine-II not working ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by denisw): I can confirm this too. Because many VIA-based motherboards ship with this chipset on-board (I have an AsRock board, for instance), I think this problem is quite important. Maybe make it a blocker for a second Alpha (if not Alpha 1)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 13:21:58 2008 From: trac at haiku-os.org (mmu_man) Date: Wed, 27 Aug 2008 11:21:58 -0000 Subject: [Haiku-bugs] [Haiku] #2671: Bug on comment in style.css Message-ID: <042.3badf8192c087bca6e8e0449fb5a59f6@haiku-os.org> #2671: Bug on comment in style.css ---------------------+------------------------------------------------------ Reporter: mmu_man | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Component: Website | Version: Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ The CSS misses a start of comment on medium icons rule. NetSurf is very picky about it and just ignores the whole rule. See http://vlists.pepperfish.net/pipermail/netsurf-dev-netsurf- browser.org/2008-August/000614.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 14:37:14 2008 From: trac at haiku-os.org (julun) Date: Wed, 27 Aug 2008 12:37:14 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps (was: BPicture somehow broken due to change 26665) In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.b4168d38a09d2155460d1eb877d6dee5@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by julun): * cc: host.haiku at gmx.de (removed) Comment: Hi, i change this back to it's original topic, today i took the time and synced back step by step and r26665 did not introduce the mentioned breakage in my posted code nor does it introduce any regression at all here. Sorry for the noise. The posted code might not have worked since the first time implemented, but starting with change r27063 the broken behavoir was shown because of the correct diabled state handling in BPictureButton. BTW, i synced back down to r25000 and even there Gobe and AbiWord show the black/ red background thiny. Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:24:47 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 27 Aug 2008 13:24:47 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. Message-ID: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. ------------------------------+--------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Although not dangerous, this should behave differently. {{{ mkdir temp cd temp rm -rf ../temp cd .. }}} expected behavior: last command should correctly cd'us to the parent directory actual behavior: cd ../: no such file or directory error returned. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:24:45 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 27 Aug 2008 13:24:45 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.06b702f8300bebeff8e057ef5c5979a2@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: OK, confirmed, the partition map contains only a single descriptor for a primary partition with type 0x7 starting at 1 MB with a size of about 465 GB. The problem is that we support nesting partition maps and that this partition contains a sector that has a valid partition table sector signature. Since we are relatively lenient evaluating the partition map and it contains at least one descriptor describing a valid child, and since no file system claims to recognize the partition, the partitioning system is allowed to scan the partition and publish child partitions. I guess I'll disable the feature of nested partition maps for the time being. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:30:00 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 27 Aug 2008 13:30:00 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.79f26511cca95a4534de69df6ed3da30@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by anevilyak): That doesn't appear to be BFS-specific, more likely the VFS. In any case, I see the same behavior on FreeBSD here, though not on Linux. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:33:57 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 27 Aug 2008 13:33:57 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.981ad7749134900c958453d4d143e068@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): I could only tested it in linux, and the behavior was like the one (I) expected. How BeOS behaves? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:40:38 2008 From: trac at haiku-os.org (julun) Date: Wed, 27 Aug 2008 13:40:38 -0000 Subject: [Haiku-bugs] [Haiku] #1067: Printing doesn't work in ShowImage In-Reply-To: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> References: <045.d8ec8ab2277b9b7084c4ff993866524a@haiku-os.org> Message-ID: <054.8a69450e122b688e6375109df853e5f0@haiku-os.org> #1067: Printing doesn't work in ShowImage ---------------------------------+------------------------------------------ Reporter: jackburton | Owner: jackburton Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by julun): * status: new => closed * resolution: => fixed Comment: Hi, thanks, i fixed it and commited in r27214. Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:44:00 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 13:44:00 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.ca543f7603250001bd4ad813a4f96e8a@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): Cool. I take it you will remove support for nested partitions *EXCEPT* if it is a extended partition, right? As it will have logical partitions inside it). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 15:44:00 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 27 Aug 2008 13:44:00 -0000 Subject: [Haiku-bugs] [Haiku] #2590: Haiku gets confused with 2 volumes with the same name. In-Reply-To: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> References: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> Message-ID: <047.44846bd3d3756f8b23fe4eeb0852c4de@haiku-os.org> #2590: Haiku gets confused with 2 volumes with the same name. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): The question actually is, are two volumes with the same name allowed? Since the VFS layer contains a few function based on path value, like vnode_path_to_vnode and fd_and_path_to_vnode, having two volume with the same name can perhaps confuse those function. A little note though: in the rootfs partition, the volume is actually called Haiku1 and not Haiku like it is under the desktop directory. Beside, you can't rename a volume to Haiku as it result in "name already in use" error, which looks like an inconsistency. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:09:11 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 14:09:11 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.beb1442c65bf97c1ee9abc80b9247c70@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by bga): * status: reopened => closed * resolution: => fixed Comment: Mea culpa. Due to a bug in the SpicyKeys installer, the input filter was not being installed. So yeah, the bug is gone. Sorry. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:11:26 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 14:11:26 -0000 Subject: [Haiku-bugs] [Haiku] #2610: USB mouse dies when input_server is restarted. In-Reply-To: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> References: <038.f54d5dad79e04cbedeb83f3372c458ff@haiku-os.org> Message-ID: <047.a6bd6f13688825de86f66d46daecbf2c@haiku-os.org> #2610: USB mouse dies when input_server is restarted. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bga): Onw think I noticed is that when I have a PS/2 mouse, restarting the input_serve shows a message saying that a PS/2 mouse was found. When I have the USB mouse instead, no message to that effect shows in syslog. Maybe the input_server is not even trying to use the USB mouse when it is restarted for some reason? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:12:06 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 27 Aug 2008 14:12:06 -0000 Subject: [Haiku-bugs] [Haiku] #1874: VIA Rhine-II not working In-Reply-To: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> References: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> Message-ID: <051.ada9f717b15bf8126329ab8d6a773f73@haiku-os.org> #1874: VIA Rhine-II not working ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by scottmc): @denisw Can you post the output of listdev run from your terminal? Also where Haiku revision? Listdev was fixed again in r27195 The laptop I had with the VIA RhineII is now dead, so hopefully between denisw and sklp we will have some hardware to try out possible fixes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:15:35 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 14:15:35 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.18e937ce55e6d8e18441be2bb9d69694@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): I just tried this under Linux on an nfs mounted disk: bga at librarian:~/x$ cd .. bash: cd: ..: No such file or directory Behaves exactly like Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:17:54 2008 From: trac at haiku-os.org (koki) Date: Wed, 27 Aug 2008 14:17:54 -0000 Subject: [Haiku-bugs] [Haiku] #2671: Bug on comment in style.css In-Reply-To: <042.3badf8192c087bca6e8e0449fb5a59f6@haiku-os.org> References: <042.3badf8192c087bca6e8e0449fb5a59f6@haiku-os.org> Message-ID: <051.287b2239ab25cd1f557c7bb598cc4403@haiku-os.org> #2671: Bug on comment in style.css ----------------------+----------------------------------------------------- Reporter: mmu_man | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Component: Website | Version: Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Comment(by koki): Should be fixed. Please check. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:18:45 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 27 Aug 2008 14:18:45 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.9303ef7ae6245ae4cdae0239b41b37fb@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by anevilyak): Hm..at least on Ubuntu with ReiserFS (all I have to test with Linux-wise) it works. FreeBSD concurs with your NFS experience though. It makes sense though, if you remove the directory then in theory the special files . and .. don't exist any more either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:21:07 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 14:21:07 -0000 Subject: [Haiku-bugs] [Haiku] #2590: Haiku gets confused with 2 volumes with the same name. In-Reply-To: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> References: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> Message-ID: <047.b4fb3c80b38c0352677ccba8c79e39ae@haiku-os.org> #2590: Haiku gets confused with 2 volumes with the same name. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bga): Yes, you can have 2 volumes with the same name. Otherwise you would have serious problems with removable media. Yes, the mount point is not related to the disk label at all. The only relationship is that Tracker tries to create a directory with the same name to mount it and then append numbers if the name is already taken. Anyway, I was only able to reproduce this with VMWare. This may be a VMWare specific bug or it may just be the fact that when trying on real hardware, the partitions are not exactly equal while, with VMWare, they are (I created the second partition as a copy of the first). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:37:12 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 27 Aug 2008 14:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #2590: Haiku gets confused with 2 volumes with the same name. In-Reply-To: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> References: <038.ddaffba438e88bae80668618ae55f0af@haiku-os.org> Message-ID: <047.344e94efba2ee3ab224b6b119798878d@haiku-os.org> #2590: Haiku gets confused with 2 volumes with the same name. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): Replying to [comment:4 bga]: > Yes, you can have 2 volumes with the same name. Otherwise you would have serious problems with removable media. What I meant was if it was allowed to mount the volume with the same name already taken by another volume. > > Yes, the mount point is not related to the disk label at all. The only relationship is that Tracker tries to create a directory with the same name to mount it and then append numbers if the name is already taken. In rootfs numbers are appended as you said, but in the Desktop directory they are not. > > Anyway, I was only able to reproduce this with VMWare. This may be a VMWare specific bug or it may just be the fact that when trying on real hardware, the partitions are not exactly equal while, with VMWare, they are (I created the second partition as a copy of the first). I'll see if I can try with a volume with the same name formatted with DriveSetup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 16:39:13 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 27 Aug 2008 14:39:13 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.98ef481dc4ab14d5bc9b59c49392a325@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): I have gentoo with ext3. This might then be fs specific, unless linux VFS have changed lately (kernel 2.6.20 over here). I can't try this on BeOS unfortuntely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 17:32:07 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 27 Aug 2008 15:32:07 -0000 Subject: [Haiku-bugs] [Haiku] #2673: [Terminal] Text Encoding not working? Message-ID: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> #2673: [Terminal] Text Encoding not working? -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I'm not sure but I think the text encoding menu option does nothing. This was on r27178. When I built jed (text editor) the menus have letters in their border instead of the expected lines. It might be that terminal isn't using the same mode as jed expects? The jed maintainer suggested trying "xterm" mode? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 17:35:32 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 27 Aug 2008 15:35:32 -0000 Subject: [Haiku-bugs] [Haiku] #2673: [Terminal] Text Encoding not working? In-Reply-To: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> References: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> Message-ID: <051.c4d5c203e3283b3ed095127356727371@haiku-os.org> #2673: [Terminal] Text Encoding not working? ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Here's what the expected output should look like: http://www.jedsoft.org/jed/images.html I've attached a screenshot of what terminal shows. Changing the text encoding to any of the menu selections has no effect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 17:39:51 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 27 Aug 2008 15:39:51 -0000 Subject: [Haiku-bugs] [Haiku] #2673: [Terminal] Text Encoding not working? In-Reply-To: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> References: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> Message-ID: <051.1eddac14ccc116d166dff6c826c1d281@haiku-os.org> #2673: [Terminal] Text Encoding not working? ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): I'd assume you already tried export TERM=xterm ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 18:07:18 2008 From: trac at haiku-os.org (kvdman) Date: Wed, 27 Aug 2008 16:07:18 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.e0772f907b22490675055d86db7353f1@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by kvdman): I've tested r27151. The red backgrounds on AbiWord's menu items are gone. The colour picker icon still doesn't appear correct or work properly in Gobe Productive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 19:55:19 2008 From: trac at haiku-os.org (kev) Date: Wed, 27 Aug 2008 17:55:19 -0000 Subject: [Haiku-bugs] [Haiku] #2177: boot screen does not show, but desktop does appear correctly afterwards In-Reply-To: <038.d1bd554a50c472377b631d3cad48fc0e@haiku-os.org> References: <038.d1bd554a50c472377b631d3cad48fc0e@haiku-os.org> Message-ID: <047.696e7ba77fb358561d1e537c6f261945@haiku-os.org> #2177: boot screen does not show, but desktop does appear correctly afterwards ---------------------+------------------------------------------------------ Reporter: kev | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------+------------------------------------------------------ Comment(by kev): Still having no boot screen on r27210. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 19:57:59 2008 From: trac at haiku-os.org (kev) Date: Wed, 27 Aug 2008 17:57:59 -0000 Subject: [Haiku-bugs] [Haiku] #2439: boot process stalls (around mime_update.sh/emuxki: init_hardware()?) In-Reply-To: <038.f78b13c2744771eb62cdc040745d297c@haiku-os.org> References: <038.f78b13c2744771eb62cdc040745d297c@haiku-os.org> Message-ID: <047.f6a47a215dd46dee0e6b9637c83bc1de@haiku-os.org> #2439: boot process stalls (around mime_update.sh/emuxki: init_hardware()?) ---------------------+------------------------------------------------------ Reporter: kev | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------+------------------------------------------------------ Comment(by kev): No longer having this problem. At least, booting from the HD directly works, but I haven't tried QEMU lately. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 23:55:55 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 27 Aug 2008 21:55:55 -0000 Subject: [Haiku-bugs] [Haiku] #2672: [bfs]: cd .. does not work in deleted directory. In-Reply-To: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> References: <042.ad3cbe34202def099df3653cc89fe399@haiku-os.org> Message-ID: <051.5a3118bb14ffe728f335ce4276940886@haiku-os.org> #2672: [bfs]: cd .. does not work in deleted directory. -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: low | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: BeOS reports the same error. Interestingly on Solaris (SunOS 5.10) I get: {{{ bolero bonefish 5 (~/tt): rmdir ~/tt rmdir: directory "/home/tfs/bonefish/tt": Can't remove current directory or .. }}} Though it can easily be tricked: {{{ bolero bonefish 7 (~/tt): (cd ..; rmdir tt) bolero bonefish 8 (~/tt): cd .. -bash: cd: ..: No such file or directory }}} Haiku's behavior seem OK. Closing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 00:12:20 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 27 Aug 2008 22:12:20 -0000 Subject: [Haiku-bugs] [Haiku] #2673: [Terminal] Text Encoding not working? In-Reply-To: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> References: <042.8a596394d3e0e5dba0f1da5b28e9025a@haiku-os.org> Message-ID: <051.8f8686822424dbd799eca6644c197251@haiku-os.org> #2673: [Terminal] Text Encoding not working? ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Replying to [comment:2 anevilyak]: > I'd assume you already tried export TERM=xterm ? That's set by default. Anyway, this has nothing to do with text encoding. We simply don't support all xterm escape sequences yet. E.g. we don't support the graphics character set, which is why there are "q", "x", "l", "j" instead of lines. So the open "Windows" menu looks at good as it gets ATM. I don't see what the box to the left is supposed to be, but I guess the remainders of some menu. So maybe some positioning escape sequences are used, that we don't support yet. If you can find out which ones, it's probably not so hard to add them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 00:39:47 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 27 Aug 2008 22:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #2668: Haiku's partition map representation looks weird. In-Reply-To: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> References: <038.d5592efdd4b9e2c386305b18cef737a1@haiku-os.org> Message-ID: <047.b906f9ac891aad01afb0ebdfbaa9b53a@haiku-os.org> #2668: Haiku's partition map representation looks weird. ----------------------------+----------------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:5 bga]: > Cool. I take it you will remove support for nested partitions *EXCEPT* if it is a extended partition, right? As it will have logical partitions inside it). Yep, I meant only a nested partition map (which describes the primary partitions). Done in r27215. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 01:29:12 2008 From: trac at haiku-os.org (aldeck) Date: Wed, 27 Aug 2008 23:29:12 -0000 Subject: [Haiku-bugs] [Haiku] #2453: [Tracker] Dragging items leaves some folders hilited/selected (was: [Tracker] Dragging items in the same window leaves some folders selected) In-Reply-To: <041.371104b097b366fb52697ee8144f9ba9@haiku-os.org> References: <041.371104b097b366fb52697ee8144f9ba9@haiku-os.org> Message-ID: <050.b36b41de18c8bee408b5f3c95476e312@haiku-os.org> #2453: [Tracker] Dragging items leaves some folders hilited/selected -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 02:03:20 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 28 Aug 2008 00:03:20 -0000 Subject: [Haiku-bugs] [Haiku] #2441: [Tracker] Wrong offset when changing dir in single window navigation & icon mode. (was: [Tracker] Wrong offset when switching from mini-icon to icon mode.) In-Reply-To: <041.44d42d5cfbe99ee47b0bb48185487b71@haiku-os.org> References: <041.44d42d5cfbe99ee47b0bb48185487b71@haiku-os.org> Message-ID: <050.b150d728389036c8163db429a0348feb@haiku-os.org> #2441: [Tracker] Wrong offset when changing dir in single window navigation & icon mode. -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Adjusted summary Can't edit the description though, replace step 3) by: 3) change dir using the navigation arrows. --------- I did find some inconsistency in BPoseView::SwitchDir(). If the passed AttributeStreamNode *node isn't NULL, the origin is correctly restored but it is (likely wrongly) again reseted before returning. I tried to do the reset only when "not restoring" but it gave strange/inconsistent results. So there's either another bug or something i don't understand. To summarize, i'm stuck. Also, i don't understand the following comment in BPoseView::SwitchDir(), what does "this" refer to? And besides, we actually set the origin before and after so it doesn't help understand the comment: // be sure this happens after origin is set and window is sized // properly for proper icon caching! See also commit list discussion of r26121. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 02:26:01 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 28 Aug 2008 00:26:01 -0000 Subject: [Haiku-bugs] [Haiku] #2372: [Tracker] unneeded offset in icon mode In-Reply-To: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> References: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> Message-ID: <050.a4633b24de4f65c820f26f9d9c7c4fd4@haiku-os.org> #2372: [Tracker] unneeded offset in icon mode -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Well, i didn't commit anything yet because it needed a bit of refactoring in BPoseView to do it cleanly. I started refactoring what i needed but it's not a simple patch anymore and could introduce a few new bugs, well maybe i'd need a branch so that i can benefit from version control and avoid the pressure of touching a (IMO) core component thats quite stable. Well i don't promise anything, but what's our policy regarding branches, it seems it's not a big deal, what should i do? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 03:57:50 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 28 Aug 2008 01:57:50 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.6bd362919e97f4f325e2418b8d287dbf@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): In r27216 the new I/O scheduling algorithm is in place. I tried "svn co" and "svn up" in VMware and things worked without problems (not very fast, though -- 31 min for the checkout with 256 MB RAM). I haven't tried an installation. Please report how that goes, now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 04:22:44 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 28 Aug 2008 02:22:44 -0000 Subject: [Haiku-bugs] [Haiku] #2372: [Tracker] unneeded offset in icon mode In-Reply-To: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> References: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> Message-ID: <050.66e482d4bd8bc04a15644429e7b02ced@haiku-os.org> #2372: [Tracker] unneeded offset in icon mode -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by bonefish): Replying to [comment:1 aldeck]: > Well i don't promise anything, but what's our policy regarding branches, it seems it's not a big deal, what should i do? Just create a directory with your developer name in [http://dev.haiku- os.org/browser/haiku/branches/developer haiku/branches/developer] and feel free to do in it whatever you like. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 04:27:54 2008 From: trac at haiku-os.org (aldeck) Date: Thu, 28 Aug 2008 02:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #2372: [Tracker] unneeded offset in icon mode In-Reply-To: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> References: <041.fe5a0932b6c039326d7a14a126528192@haiku-os.org> Message-ID: <050.00eea2a82d42800f88cf9c1a84febf26@haiku-os.org> #2372: [Tracker] unneeded offset in icon mode -----------------------------------+---------------------------------------- Reporter: aldeck | Owner: aldeck Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): Perfect, will do! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 04:30:42 2008 From: trac at haiku-os.org (bga) Date: Thu, 28 Aug 2008 02:30:42 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.237cfe62517c3f188d785c9ec7b4c83a@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): Thanks. worked perfectly here. AFAIK, this bug can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 06:24:49 2008 From: trac at haiku-os.org (katisu) Date: Thu, 28 Aug 2008 04:24:49 -0000 Subject: [Haiku-bugs] [Haiku] #2674: Add Intel Atom 230 to OS.h Message-ID: <041.5a2d6661782bdcc95a2d17fa30224c58@haiku-os.org> #2674: Add Intel Atom 230 to OS.h ---------------------------+------------------------------------------------ Reporter: katisu | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Tested Haiku working on a Intel Atom 230 (under fail-safe vesa mode). Processor is identified as Intel but model is listed as unknown in Pulse. Will be attaching sysinfo.txt and a screenshot. Additional reference: http://download.intel.com/design/processor/specupdt/319978.pdf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 07:26:09 2008 From: trac at haiku-os.org (leavengood) Date: Thu, 28 Aug 2008 05:26:09 -0000 Subject: [Haiku-bugs] [Haiku] #2675: Backlight turned off on Radeon Mobility X600 Message-ID: <045.d912a97153de74f92a0d1b1e46357ef7@haiku-os.org> #2675: Backlight turned off on Radeon Mobility X600 -------------------------------------+-------------------------------------- Reporter: leavengood | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- This may be a known problem on some ATI chipsets since I saw euan mention it on another bug, but nonetheless: When I boot up my IBM ThinkPad Z60m I get a very dark screen. Graphics are there but barely visible so the problem seems to be the backlight. The output from listdev for my display controller is: {{{ device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 1002: ATI Technologies Inc device 3150: M24 1P [Radeon Mobility X600] }}} Attached is my syslog from two boots, with the first boot using the radeon driver and the second using forced VESA mode, which works. If there is any simple fix or way for me to correct this myself, let me know. I am a developer but certainly not any driver expert, but I'm willing to try. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 19:20:35 2008 From: trac at haiku-os.org (stippi) Date: Mon, 25 Aug 2008 17:20:35 -0000 Subject: [Haiku-bugs] [Haiku] #2131: AMD Geode Video controller needs a driver In-Reply-To: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> References: <042.a51ea134382c4e7d5cc06c9902a684c2@haiku-os.org> Message-ID: <051.f416b156de3d84892b41a0a8e2cc7fc2@haiku-os.org> #2131: AMD Geode Video controller needs a driver -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers/Graphics | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by stippi): * milestone: R1 => Unscheduled -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 09:42:43 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 28 Aug 2008 07:42:43 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.d2ede62a9b2d716bce81f65b099ace0e@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): So it's related to BPicture ? Then it might be that we don't sync correctly the graphic state in some cases, when drawing a BPicture. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 16:10:35 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 25 Aug 2008 14:10:35 -0000 Subject: [Haiku-bugs] [Haiku] #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest In-Reply-To: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> References: <046.03be6246b18395e66632e26e893e269c@haiku-os.org> Message-ID: <055.df46d795549e4f46fd32bd3665195623@haiku-os.org> #2578: [scsi scheduler]: crash in _GetNextUnscheduledRequest ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 09:57:33 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 07:57:33 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.d3b8435e26b0c0dd373e0255765210b7@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, it's not an problem of BPicture at all, moreover it is the combination of how it is implemented client/ server side. Imagin the following: create view, add view to window pass view to function, call BeginPicture on it set view high color for example the call will succeed and go to app server, but won't recorded in the current drawing state as it's handled in _DispatchPictureMessage on the client side(libbe) the B_VIEW_HIGH_COLOR_BIT is set and the color cached call end picture on that view now reuse the same view to draw a second picture pass view to function, call BeginPicture on it set view high color the call will not succeed(go to app_server and added to BPicture) since the view B_VIEW_HIGH_COLOR_BIT is set and the color is the same this is where ServerPicture::SyncState should come into the game, but it will sync the unmodified drawstate into the picture, because the first function call did not modify the drawing state so basically nothing happens, except that the view highcolor is now the default, black while playing the picture call end picture on that view R5 shows that calls to a given view, e.g SetHighColor will modify the current drawing state even after BeginPicture was called. Note also, that the above applies to SetDrawingMode etc. as well. So i'm on it, will attach a diff later today. Regards, Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 09:57:52 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 07:57:52 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.5b1a2924de685299a8364081ef24487f@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by julun): * cc: host.haiku at gmx.de (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 10:20:55 2008 From: trac at haiku-os.org (shinta) Date: Mon, 25 Aug 2008 08:20:55 -0000 Subject: [Haiku-bugs] [Haiku] #2665: Donating codes: APE reader Message-ID: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> #2665: Donating codes: APE reader ----------------------------------+----------------------------------------- Reporter: shinta | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- I donate my APE reader codec's source codes to Haiku. This post is based on http://www.freelists.org/archives/haiku- development/06-2008/msg00049.html Haiku: r26161[[BR]] [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (enhancement No.5) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Aug 25 10:26:52 2008 From: trac at haiku-os.org (shinta) Date: Mon, 25 Aug 2008 08:26:52 -0000 Subject: [Haiku-bugs] [Haiku] #2665: Donating codes: APE reader In-Reply-To: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> References: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> Message-ID: <050.5f5c9aa5e263a1b7b8bdcbbfa45988fd@haiku-os.org> #2665: Donating codes: APE reader -----------------------------------+---------------------------------------- Reporter: shinta | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Comment(by shinta): Above files are APE reader and static libs. Please build these files to Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Aug 27 02:52:14 2008 From: trac at haiku-os.org (bga) Date: Wed, 27 Aug 2008 00:52:14 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.b1cf734b5abf4b0245cefeaae32df068@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): Hi Ingo. Just to clarify, this was introduced with one of the recent changes to the IO scheduiler stuff. Not long ago I could download the tree under Haiku without problems, no I can not anymore as this will happen. This also shows how our scheduler bahaves *REALLY* badly. I hace 4 cores on this machine and I can see in process controller one being used at 100%. But the system grinds to a halt and I can?t do anything (like moving windows, opening menus). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 10:24:57 2008 From: trac at haiku-os.org (stippi) Date: Thu, 28 Aug 2008 08:24:57 -0000 Subject: [Haiku-bugs] [Haiku] #2665: Donating codes: APE reader In-Reply-To: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> References: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> Message-ID: <050.55e30949e065705d3c902e0dfae969d2@haiku-os.org> #2665: Donating codes: APE reader -----------------------------------+---------------------------------------- Reporter: shinta | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Comment(by stippi): I wanted to take care of this, but still have not taken the time to do so... sorry! Anyone else, please feel free to beat me to it, otherwise I still plan on doing it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 10:44:32 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 08:44:32 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.249f2be704bea5b8482bd64f42dfbdad@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, and by the way, this bug is basically invalid if the red label is gone in AbiWord. I have installed Gobe in R5 now and what, the black squares are there on purpose! These are the color indicators, also the 'Edit color' window looks on R5 exactly like the one in the attached screenshot! Nevertheless find attached a fix for the problem i described, which will fix the black BPicture drawing in the 'Print Setup' panel. Regards, Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 11:40:52 2008 From: trac at haiku-os.org (stippi) Date: Thu, 28 Aug 2008 09:40:52 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.b1695abb24c663bef87c3ccaf2faa53a@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): Ah, ok - I get it! Please commit! Nice catch. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 12:06:22 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 28 Aug 2008 10:06:22 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.abd2a4fa443d3bf709ec749117d3001f@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): I think that the best way to handle this, we should modify SyncState() to actually sync the client and the server states. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 12:12:43 2008 From: trac at haiku-os.org (mmu_man) Date: Thu, 28 Aug 2008 10:12:43 -0000 Subject: [Haiku-bugs] [Haiku] #2671: Bug on comment in style.css In-Reply-To: <042.3badf8192c087bca6e8e0449fb5a59f6@haiku-os.org> References: <042.3badf8192c087bca6e8e0449fb5a59f6@haiku-os.org> Message-ID: <051.c380797a421710df1c29844f5cb55fa4@haiku-os.org> #2671: Bug on comment in style.css ----------------------+----------------------------------------------------- Reporter: mmu_man | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: Component: Website | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Changes (by mmu_man): * status: new => closed * resolution: => fixed Comment: Seems to work now, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 12:15:00 2008 From: trac at haiku-os.org (stippi) Date: Thu, 28 Aug 2008 10:15:00 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.020ed4e833e80323742fe6c6a4d65def@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): But we may need to be compatible with BeOS behavior here. In theory, it should be enough to handle this on the View.cpp side of things (don't modify state if recording a BPicture), but if some BeOS app relies on the fact that the view state is modified even when recording a BPicture, this app would be broken. For example, it could continue to use a BView and rely on the final state after recording a BPicture. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 14:08:35 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 12:08:35 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.95e8c6fd6e7499d4fbdc56cfa16189b6@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by julun): * status: new => closed * resolution: => invalid Comment: Close this as invalid, Gobe does look like as in the screenshot.[[BR]] [[BR]] The last part (comment 9)should be fixed in r27218. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 14:22:28 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 28 Aug 2008 12:22:28 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.ace2bb650133eb38ce5dbd15f24ff186@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): I think we could simplify the code by just returning false in the ops which also needs to set the drawing state. If you have a look at the function calling _DispatchPictureMessage(), it passes the message to the BView if that function returns false. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 14:37:46 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 12:37:46 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.7680aee5a7bc3cf4829c5f394473173f@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Wouldn't LinkReceiver::Read have bumped the position up about the size of the read data? If not, i can go and change it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 14:44:47 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 28 Aug 2008 12:44:47 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.88dc473966a9479dcd388c67ab13daaf@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Replying to [comment:17 julun]: > Wouldn't LinkReceiver::Read have bumped the position up about the size of the read data? If not, i can go and change it. Yes, you're right. That wouldn't work, then. Unless we rewind the position, of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 16:00:55 2008 From: trac at haiku-os.org (kvdman) Date: Thu, 28 Aug 2008 14:00:55 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.42bf1d6f095c16890ec0c02ffa364f34@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by kvdman): re: "and by the way, this bug is basically invalid if the red label is gone in AbiWord. I have installed Gobe in R5 now and what, the black squares are there on purpose! These are the color indicators, also the 'Edit color' window looks on R5 exactly like the one in the attached screenshot!" and: "Close this as invalid, Gobe does look like as in the screenshot." The icon does indeed look as in GoBE Productive for the colour selector, sorry about that. The colour picker doesn't behave as it does in BeOS. Changing the values of RGB will not change the wheel palette correctly.. (only between black and white and in between). See the attached pictures please. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 16:33:55 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 14:33:55 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.ec766f1d07bce9e6556fe452633bf270@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by julun): Hi, i didn't want to offend you by what i wrote, I apologize if i did. I can reproduce it here too, so would you please so kind and open a new ticket for this. Currently I'm not sure if it is releated to BPicture, BView or something. Thanks, Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 17:43:16 2008 From: trac at haiku-os.org (kvdman) Date: Thu, 28 Aug 2008 15:43:16 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.886ff4d13c5f5e58bf88a1ef490ee7e1@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by kvdman): No offense taken! I just thought that the situation was related. I'll open a new bug report for the colour wheel. Thanks, Karl -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 17:44:35 2008 From: trac at haiku-os.org (kvdman) Date: Thu, 28 Aug 2008 15:44:35 -0000 Subject: [Haiku-bugs] [Haiku] #2676: Colour picker in GoBE Productive is monochrome Message-ID: <041.26b2d11d43dbb18920e2d8f6fe7188fa@haiku-os.org> #2676: Colour picker in GoBE Productive is monochrome -----------------------+---------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The colour picker for GoBE Productive doesn't behave as it does in BeOS. Changing the values of RGB will not change the wheel palette correctly.. (only between black and white and in between). See the attached pictures please. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 17:49:04 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 28 Aug 2008 15:49:04 -0000 Subject: [Haiku-bugs] [Haiku] #2676: Colour picker in GoBE Productive is monochrome In-Reply-To: <041.26b2d11d43dbb18920e2d8f6fe7188fa@haiku-os.org> References: <041.26b2d11d43dbb18920e2d8f6fe7188fa@haiku-os.org> Message-ID: <050.6a517da44f5a3fe257754383a2485d6c@haiku-os.org> #2676: Colour picker in GoBE Productive is monochrome ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * component: - General => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 17:49:25 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 28 Aug 2008 15:49:25 -0000 Subject: [Haiku-bugs] [Haiku] #2676: Colour picker in GoBE Productive is monochrome In-Reply-To: <041.26b2d11d43dbb18920e2d8f6fe7188fa@haiku-os.org> References: <041.26b2d11d43dbb18920e2d8f6fe7188fa@haiku-os.org> Message-ID: <050.1f859e7d3c1b544504edf594d8d3cfce@haiku-os.org> #2676: Colour picker in GoBE Productive is monochrome ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: julun Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * owner: axeld => julun -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 17:58:54 2008 From: trac at haiku-os.org (rossi) Date: Thu, 28 Aug 2008 15:58:54 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.ba3986287c00eb3b53c5adafc6e5deaf@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by rossi): I can only second that. Both issues (installer and svn) have been solved. May someone with the appropiate rights please close this bug. Thanks, Rossi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 18:07:25 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 28 Aug 2008 16:07:25 -0000 Subject: [Haiku-bugs] [Haiku] #2669: scsi scheduler takes 100% cpu load In-Reply-To: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> References: <040.75d6c6e1d4907d02ed8cb512c62df82a@haiku-os.org> Message-ID: <049.29d85649f7acd65fab8bf32e4f3c29d8@haiku-os.org> #2669: scsi scheduler takes 100% cpu load ----------------------------+----------------------------------------------- Reporter: rossi | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Aug 28 20:03:30 2008 From: trac at haiku-os.org (julun) Date: Thu, 28 Aug 2008 18:03:30 -0000 Subject: [Haiku-bugs] [Haiku] #2612: 'Save as' sometimes behaves unexpected In-Reply-To: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> References: <043.faa45b77899080acf1a8def900301c5a@haiku-os.org> Message-ID: <052.89cda7e1d6c634cf462975dc3f40a6b2@haiku-os.org> #2612: 'Save as' sometimes behaves unexpected --------------------------------------+------------------------------------- Reporter: andreasf | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Applications/StyledEdit | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed Comment: fixed in r27225 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 12:23:34 2008 From: trac at haiku-os.org (nutela) Date: Fri, 29 Aug 2008 10:23:34 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.aeac2a67e002eef920e9698ef0201610@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by nutela): A link would have been nice... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 12:38:10 2008 From: trac at haiku-os.org (nutela) Date: Fri, 29 Aug 2008 10:38:10 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.288a858329ffc0a128f124d2453f4e54@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by nutela): I could not find anything in the recent discussion on haiku-development other besides the "Haiku Alpha 1 desktop logo proposal" where there was no discussion about the Desk Bar at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 12:56:06 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 29 Aug 2008 10:56:06 -0000 Subject: [Haiku-bugs] [Haiku] #2400: [vfs]: vnode is not becoming unbusy In-Reply-To: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> References: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> Message-ID: <051.1d5e22384eed892935ad585b21014f2a@haiku-os.org> #2400: [vfs]: vnode is not becoming unbusy ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: emitrax Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by emitrax): * component: File Systems/BFS => System/Kernel Comment: Although the situation has improved since the introduction of the I/O scheduler, this still happens under heavy I/O operations. The problem may be related to the ide/scsi module as Ingo(or Axel, don't really remember) suggested. Quoting Axel from the haiku-gsoc mailing list, since this happens on low memory situation: "Codepaths necessary to recover from extreme memory shortage should have some preallocated buffers around they can use then". (Marcus?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 13:41:46 2008 From: trac at haiku-os.org (rossi) Date: Fri, 29 Aug 2008 11:41:46 -0000 Subject: [Haiku-bugs] [Haiku] #2677: Tracker doesn't show name of symbolic link correct on first display Message-ID: <040.32589a7aa212b3c0b9493e5ac7d52c56@haiku-os.org> #2677: Tracker doesn't show name of symbolic link correct on first display -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- There seems to be an issue with symbolic links not being displayed correctly, when a Tracker window is first opened. Instead of the link a blank line/entry is displayed, once the window contents have been scrolled, the link is displayed right. See also the two screenshots attached. Rossi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 13:49:09 2008 From: trac at haiku-os.org (rossi) Date: Fri, 29 Aug 2008 11:49:09 -0000 Subject: [Haiku-bugs] [Haiku] #2677: Tracker doesn't show name of symbolic link correct on first display In-Reply-To: <040.32589a7aa212b3c0b9493e5ac7d52c56@haiku-os.org> References: <040.32589a7aa212b3c0b9493e5ac7d52c56@haiku-os.org> Message-ID: <049.a82a5089d2ab5fed4ebdb303fe68b738@haiku-os.org> #2677: Tracker doesn't show name of symbolic link correct on first display ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by rossi): Addendum: apperently the blank line is only displayed the first time the window is opened. On successive reopenings of the window some other file name is shown instead of the link name. Scrolling still corrects the issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 13:58:27 2008 From: trac at haiku-os.org (rossi) Date: Fri, 29 Aug 2008 11:58:27 -0000 Subject: [Haiku-bugs] [Haiku] #2678: "profiles" for screen settings Message-ID: <040.05a6cd91bc8082a42461821e14edf67f@haiku-os.org> #2678: "profiles" for screen settings -------------------------+-------------------------------------------------- Reporter: rossi | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- When working with a laptop, which is used standalone and together with an attached external display, it would be highly appreciated, if there would be "profiles" for the relevant settings (screen resolution, background) in order to have two sets of settings for working with either the internal or the external screen, without always manually setting these settings. The current state should be detected by the vga driver and the appropiated settings should be activated automagically ;-) Rossi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 15:53:49 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 29 Aug 2008 13:53:49 -0000 Subject: [Haiku-bugs] [Haiku] #1972: Implement paging (swap file) support In-Reply-To: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> References: <040.6a0030783dc98530450a11a28a320ca9@haiku-os.org> Message-ID: <049.2d35864d57d42929b0063f8432528332@haiku-os.org> #1972: Implement paging (swap file) support ----------------------------+----------------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Enabled swap support by default in r27233. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 15:58:19 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 29 Aug 2008 13:58:19 -0000 Subject: [Haiku-bugs] [Haiku] #2239: kernel doesn't free memory that was requested from userspace programs In-Reply-To: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> References: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> Message-ID: <052.ea09241c1092ceb71007fed215a613d2@haiku-os.org> #2239: kernel doesn't free memory that was requested from userspace programs ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Several kernel memory leaks have been fixed in the meantime and the low memory management has been improved. Furthermore swap support is enabled now. This should be fixed. If it isn't, please re-open. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:12:49 2008 From: trac at haiku-os.org (kev) Date: Fri, 29 Aug 2008 14:12:49 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.ceab39b9241e40cda80af7c553e3216d@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: reopened Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by kev): * status: closed => reopened * resolution: fixed => Comment: Actually, I was still having this problem, even on the latest build. All that needed to be done was create the directories ~/config/add_ons/input_server and filters/ underneath that. (That also allows UniversalScroller to install properly, BTW.) Are these empty directories automatically stripped from the distro or something? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:14:35 2008 From: trac at haiku-os.org (korli) Date: Fri, 29 Aug 2008 14:14:35 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.2449218063192f109312f6629d322897@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by korli): * status: reopened => closed * resolution: => fixed Comment: Replying to [comment:4 kev]: > Actually, I was still having this problem, even on the latest build. All that needed to be done was create the directories ~/config/add_ons/input_server and filters/ underneath that. (That also allows UniversalScroller to install properly, BTW.) Are these empty directories automatically stripped from the distro or something? Please, please don't hijack tickets. Just open new ones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:22:46 2008 From: trac at haiku-os.org (kev) Date: Fri, 29 Aug 2008 14:22:46 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.cef901da8d75067433ad7b6655cdab98@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: reopened Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by kev): * status: closed => reopened * resolution: fixed => Comment: Uh...the start page says, "Before reporting a bug please make sure that it does not yet exist. You can also use the search function for this." bga's description fit what had happened to me exactly, and even his follow-up (about the input filter not being installed) is still the case for me... If you really think these two bugs aren't the same, please show me how this is the case (maybe provide more detail?), or if Haiku's tracking policy has changed, maybe the start page ought to be updated. As of now, the current build still has this exact bug, as far as the information on this page indicates to me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:27:53 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 29 Aug 2008 14:27:53 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.b88c6fa57fecd44be612d29309e922e4@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: reopened => closed * resolution: => fixed Comment: The initial bug had nothing to do with the missing subdirectories, that's another issue, hence new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:45:28 2008 From: trac at haiku-os.org (kev) Date: Fri, 29 Aug 2008 14:45:28 -0000 Subject: [Haiku-bugs] [Haiku] #2611: SpicyKeys input_server add-on mouse event generator does not work. In-Reply-To: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> References: <038.45d6ffc1b18cc3c62d480ca20c5d96b2@haiku-os.org> Message-ID: <047.46efea5a0a7d2665a9db1bc28b35b49b@haiku-os.org> #2611: SpicyKeys input_server add-on mouse event generator does not work. -----------------------------------+---------------------------------------- Reporter: bga | Owner: korli Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by kev): Oh, sorry, I had misinterpreted what bga had said, thinking he had done something to affect the installers, but had known what he was talking about to keep it in the same ticket. That's why I was all confused, I was just following bga, who hadn't been accused of hijacking :P Anyway, will do, I don't see a ticket on this yet, so I'll open one. Thanks for your patience. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 18:11:33 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 29 Aug 2008 16:11:33 -0000 Subject: [Haiku-bugs] [Haiku] #2400: [vfs]: vnode is not becoming unbusy In-Reply-To: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> References: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> Message-ID: <051.957dffbea9375cfb27dfca393c8e7ae6@haiku-os.org> #2400: [vfs]: vnode is not becoming unbusy ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: emitrax Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): I believe I have already mentioned that on the mailing list, this doesn't need to be any kind of deadlock due to memory problems. The "low memory handler" stack trace even suggests that it is still running (but was preempted). I still think it's possible that syncing the file in question simply took longer than the 10 seconds get_vnode() waits. IIRC you've already tried to increase the timeout without success, which could mean that the low memory handler was starved for some reason. Enabling scheduler tracing would help to verify this. If you have a test case that allows to reproduce the problem more or less reliably, I could have a look. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 18:15:12 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 29 Aug 2008 16:15:12 -0000 Subject: [Haiku-bugs] [Haiku] #2400: [vfs]: vnode is not becoming unbusy In-Reply-To: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> References: <042.22c8f58394bb04153c0fcba1ff949dd4@haiku-os.org> Message-ID: <051.c2f6e7f90761bb75bac035ddc4c90348@haiku-os.org> #2400: [vfs]: vnode is not becoming unbusy ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: emitrax Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Replying to [comment:4 bonefish]: > > If you have a test case that allows to reproduce the problem more or less reliably, I could have a look. I used to trigger this by unpacking the haiku source tree from a usb stick, but I don't know if that's still the case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 16:47:33 2008 From: trac at haiku-os.org (kev) Date: Fri, 29 Aug 2008 14:47:33 -0000 Subject: [Haiku-bugs] [Haiku] #2679: ~/config/add_ons/input_server/ and .../filters/ missing Message-ID: <038.2ed0bf8229fe6fa6663da249a3d5f12f@haiku-os.org> #2679: ~/config/add_ons/input_server/ and .../filters/ missing --------------------------+------------------------------------------------- Reporter: kev | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Not having these directories around breaks the installers of both SpicyKeys and UniversalScroller. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 22:18:19 2008 From: trac at haiku-os.org (clebin) Date: Fri, 29 Aug 2008 20:18:19 -0000 Subject: [Haiku-bugs] [Haiku] #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! Message-ID: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! -----------------------+---------------------------------------------------- Reporter: clebin | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Haiku gives me a kernel panic as it boots, even with all the safe mode options selected. I'm building directly to a partition from Ubuntu, which worked up until around 4 months ago. I can build to a raw image and boot it in Qemu ok. My hardware is a Fujitsu-Siemens Amilo PI 1505 - Core Duo, Intel GMA 950 graphics, Intel HDA sound, SATA, Firewire... (technical spec attached) I've attached a back-trace. Let me know if you need anything else (hope I didn't duplicate any bug here...) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Aug 29 22:52:23 2008 From: trac at haiku-os.org (koki) Date: Fri, 29 Aug 2008 20:52:23 -0000 Subject: [Haiku-bugs] [Haiku] #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! In-Reply-To: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> References: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> Message-ID: <050.3d26a4d21f4d107a135abcbe68e68b1a@haiku-os.org> #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! ------------------------+--------------------------------------------------- Reporter: clebin | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by koki): * cc: kokitomare at gmail.com (added) Comment: This sounds similar to bug #2243. (A workaround for #2243 is to remove the Firewire driver; you may want to try that). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 00:15:51 2008 From: trac at haiku-os.org (clebin) Date: Fri, 29 Aug 2008 22:15:51 -0000 Subject: [Haiku-bugs] [Haiku] #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! In-Reply-To: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> References: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> Message-ID: <050.618fc30ba3d9e94c551066b4def8943c@haiku-os.org> #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! ------------------------+--------------------------------------------------- Reporter: clebin | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by clebin): Replying to [comment:1 koki]: > This sounds similar to bug #2243. > > (A workaround for #2243 is to remove the Firewire driver; you may want to try that). Doesn't seem to work for me. Pardon my ignorance - I deleted the firewire folder containing fw_raw from the src and generated folders and ran 'jam -q', then 'sudo jam -q' again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 01:05:57 2008 From: trac at haiku-os.org (Adek336) Date: Fri, 29 Aug 2008 23:05:57 -0000 Subject: [Haiku-bugs] [Haiku] #2681: webpage: wrong links Message-ID: <042.1217c7a4e49efa97bbe46833d2023697@haiku-os.org> #2681: webpage: wrong links ---------------------+------------------------------------------------------ Reporter: Adek336 | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ I've checked http://factory.haiku- os.org/documentation/Haiku_Book_doxygen/html/ and the navigation bar in the top right points to sites like http://factory.haiku-os.org/about instead of http://www.haiku-os.org/about . -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 01:09:46 2008 From: trac at haiku-os.org (umccullough) Date: Fri, 29 Aug 2008 23:09:46 -0000 Subject: [Haiku-bugs] [Haiku] #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! In-Reply-To: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> References: <041.b1e1a636e5586c00995589be32d111a2@haiku-os.org> Message-ID: <050.061a3cf05bf23e8c7c815b4454a313e3@haiku-os.org> #2680: Panic on boot: Fatal exception "NMI Interrupt" occurred! ----------------------+----------------------------------------------------- Reporter: clebin | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------+----------------------------------------------------- Changes (by umccullough): * component: - General => Drivers Comment: I'm pretty sure just deleting the source directory would just end up causing the jam to fail (and not write a new image to the partition at all). The proper way to remove a target from the image is to edit build/jam/HaikuImage and remove the targets there. Line's 140 and 181 it appears http://dev.haiku-os.org/browser/haiku/trunk/build/jam/HaikuImage#L140 and http://dev.haiku-os.org/browser/haiku/trunk/build/jam/HaikuImage#L181 That said, it may still not be firewire related even if it demonstrates the same bug - AFAICT, the firewire issue reported in the other ticket exposes some kind of flaky hardware issue that isn't that common. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 01:14:30 2008 From: trac at haiku-os.org (Adek336) Date: Fri, 29 Aug 2008 23:14:30 -0000 Subject: [Haiku-bugs] [Haiku] #1874: VIA Rhine-II not working In-Reply-To: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> References: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> Message-ID: <051.76c7c78f88b2d34277d4746286515d0d@haiku-os.org> #1874: VIA Rhine-II not working ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by Adek336): confirmed on r27217, grep via_rhine /var/log/syslog says KERN: KDiskDeviceManager::_AddDiskSK[via_rhine] (vr) restarting KERN: /dev/net/via_rhine/0: media change, media 0x900026 quality 1000 speed 10000 KERN: [via_rhine] (vr) tx shutdown timeout KERN: [via_rhine] (vr) restarting KERN: [via_rhine] (vr) tx shutdown timeout KERN: [via_rhine] (vr) restarting [many more copies of tx shutdown timeout / restarting messages] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 01:17:20 2008 From: trac at haiku-os.org (Adek336) Date: Fri, 29 Aug 2008 23:17:20 -0000 Subject: [Haiku-bugs] [Haiku] #1874: VIA Rhine-II not working In-Reply-To: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> References: <042.c155ce63a12fc64e267e9a6ad4e99da7@haiku-os.org> Message-ID: <051.7f3015986556a923fafa77d92b034d3f@haiku-os.org> #1874: VIA Rhine-II not working ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by Adek336): reposted for better formatting: {{{ KERN: KDiskDeviceManager::_AddDiskSK[via_rhine] (vr) restarting KERN: /dev/net/via_rhine/0: media change, media 0x900026 quality 1000 speed 10000 KERN: [via_rhine] (vr) tx shutdown timeout KERN: [via_rhine] (vr) restarting KERN: [via_rhine] (vr) tx shutdown timeout KERN: [via_rhine] (vr) restarting [many more copies of tx shutdown timeout / restarting messages] }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 02:29:53 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 00:29:53 -0000 Subject: [Haiku-bugs] [Haiku] #1512: deadlock after clicking on Deskbar In-Reply-To: <050.70652cbc7cad0548d42aa7be3175e7b3@haiku-os.org> References: <050.70652cbc7cad0548d42aa7be3175e7b3@haiku-os.org> Message-ID: <059.b3b2f335dcc949a2ca326ea8341bbe24@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by anevilyak): I just had this bug happen to me on gcc2 with a single non-HT CPU, fyi. Though the rw_lock seems to have been renamed in the meantime. If I see it again I'll try and gather more detailed data on it, at first I thought it might be related to swap and just rebooted to try disabling swap and seeing if it worked, and I haven't been able to duplicate it again since, with or without. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 07:33:00 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 05:33:00 -0000 Subject: [Haiku-bugs] [Haiku] #2598: sshd occasionally segfaults on connect (possibly when forking) In-Reply-To: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> References: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> Message-ID: <053.39d6b23d843242702346233e1c8067c9@haiku-os.org> #2598: sshd occasionally segfaults on connect (possibly when forking) ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Confirmed, that appears to have been caused by 26980/26981. Will file a new bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 07:34:35 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 05:34:35 -0000 Subject: [Haiku-bugs] [Haiku] #2598: sshd occasionally segfaults on connect (possibly when forking) In-Reply-To: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> References: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> Message-ID: <053.a433d43a5afcb9af8564018d865e2225@haiku-os.org> #2598: sshd occasionally segfaults on connect (possibly when forking) ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Since the segfault problem still remains though...have the patches for OpenSSH to build/work with Haiku been submitted upstream? If so I could pull the source and run the testsuites and such myself to see if I can help track this down. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 07:38:50 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 05:38:50 -0000 Subject: [Haiku-bugs] [Haiku] #2682: Network instability issues since net_timer changes Message-ID: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> #2682: Network instability issues since net_timer changes --------------------------------------+------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Since the rewrites in 26980/26981, I've been noticing some instability issues with the network stack, especially when larger amounts of data are involved. For instance, copying a few hundred megabytes of data via scp is guaranteed to at some point terminate the connection with the following message from sshd: {{{ Disconnecting: Corrupted MAC on input. }}} After something along those lines has happened at least once, connections seem to destabilize much more quickly afterwards, for instance I see Vision's network threads randomly go dead. I'm not sure what information would be most useful with respect to debugging at this point though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 07:39:13 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 05:39:13 -0000 Subject: [Haiku-bugs] [Haiku] #2682: Network instability issues since net_timer changes In-Reply-To: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> References: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> Message-ID: <053.e6bd136fba7914f9bff58c3924006e99@haiku-os.org> #2682: Network instability issues since net_timer changes ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by anevilyak): * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 13:04:01 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 30 Aug 2008 11:04:01 -0000 Subject: [Haiku-bugs] [Haiku] #2598: sshd occasionally segfaults on connect (possibly when forking) In-Reply-To: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> References: <044.8190f7167b1a7129ed18c1d985fdb3d9@haiku-os.org> Message-ID: <053.bed2a4853e646d42f021a108b8841ebd@haiku-os.org> #2598: sshd occasionally segfaults on connect (possibly when forking) ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:17 anevilyak]: > Since the segfault problem still remains though...have the patches for OpenSSH to build/work with Haiku been submitted upstream? If so I could pull the source and run the testsuites and such myself to see if I can help track this down. Nope, the patches are available in our repository in buildtools/patches/openssh/, though. BTW, weird, I definitely wrote a reply to your comment 6 days ago. I wonder what happened. Anyway, I was only saying that I don't think the problems are related -- but it seems you found the causing revision already -- and that the SSH sources don't really look helpful at the place where the error message is emitted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 15:42:44 2008 From: trac at haiku-os.org (Hubert) Date: Sat, 30 Aug 2008 13:42:44 -0000 Subject: [Haiku-bugs] [Haiku] #2575: The KDL during mount of partition FAT In-Reply-To: <041.e6805a8c98cad18b17b3fe9ca30e6fbb@haiku-os.org> References: <041.e6805a8c98cad18b17b3fe9ca30e6fbb@haiku-os.org> Message-ID: <050.31d190fa95545116a586ed0f324f7380@haiku-os.org> #2575: The KDL during mount of partition FAT ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by Hubert): I tested r27234 and I can FAT32 partition mount with success. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 15:47:33 2008 From: trac at haiku-os.org (Hubert) Date: Sat, 30 Aug 2008 13:47:33 -0000 Subject: [Haiku-bugs] [Haiku] #2683: I can't connect SE K800i Message-ID: <041.911a5073e3bb945f0ef5e4b9ec399432@haiku-os.org> #2683: I can't connect SE K800i -------------------------+-------------------------------------------------- Reporter: Hubert | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- I can't connect cell phone Sony Ericson K800i by USB -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 15:56:54 2008 From: trac at haiku-os.org (Hubert) Date: Sat, 30 Aug 2008 13:56:54 -0000 Subject: [Haiku-bugs] [Haiku] #2684: I can't connect SE K800i Message-ID: <041.61df93acce0db50788487af7f9d753b3@haiku-os.org> #2684: I can't connect SE K800i -------------------------+-------------------------------------------------- Reporter: Hubert | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- I can't connect cell phone Sony Ericson K800i by USB screen: [[Image(http://www.wrzuta.pl/obraz/7fKo0OKCJl/)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 17:31:59 2008 From: trac at haiku-os.org (emitrax) Date: Sat, 30 Aug 2008 15:31:59 -0000 Subject: [Haiku-bugs] [Haiku] #2685: vfork: out of memory Message-ID: <042.558d764e7fe0ea4e70e67652e75fea81@haiku-os.org> #2685: vfork: out of memory -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Running sqlite-3.5.9 test seems to consume all memory (256MB) and swap(512MB) at, or after, async-3-1.1 test, plus last sysinfo I managed to run shows 30088 used semaphore out of 32768 (perhaps a leak?). The number increased all at onced. In order to run the test, one needs first to install tcl-8.5.4, which is easily compilable by using the unix version. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 19:14:59 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 17:14:59 -0000 Subject: [Haiku-bugs] [Haiku] #2683: I can't connect SE K800i In-Reply-To: <041.911a5073e3bb945f0ef5e4b9ec399432@haiku-os.org> References: <041.911a5073e3bb945f0ef5e4b9ec399432@haiku-os.org> Message-ID: <050.d085c456445cbf8772137d49c1f8ee80@haiku-os.org> #2683: I can't connect SE K800i --------------------------+------------------------------------------------- Reporter: Hubert | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate Comment: Duplicate of 2684 (more information on that ticket). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 21:12:48 2008 From: trac at haiku-os.org (revivaldbm) Date: Sat, 30 Aug 2008 19:12:48 -0000 Subject: [Haiku-bugs] [Haiku] #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " Message-ID: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " --------------------------+------------------------------------------------- Reporter: revivaldbm | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- I attempted to compile Haiku and had some trouble. When I typed in and ran jam -q haiku-image this error was shown: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 21:33:39 2008 From: trac at haiku-os.org (bga) Date: Sat, 30 Aug 2008 19:33:39 -0000 Subject: [Haiku-bugs] [Haiku] #2687: Multi-function USB card reader does not work. Message-ID: <038.64b1d42d138e2d74be44573b2ccc05c3@haiku-os.org> #2687: Multi-function USB card reader does not work. -------------------------+-------------------------------------------------- Reporter: bga | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- USB in general dose work on my machine. Even plugging in a pen-drive works without problems. But I have this multi-function card reader that does not work. When I connect it, I get these messages in syslog: KERN: usb_ehci: qtd (0x04028980) error: 0x00080248 KERN: usb_ehci: qtd (0x04028b80) error: 0x00080248 KERN: usb_ehci: qtd (0x04028d80) error: 0x00080248 KERN: USB BusManager: error while setting device address In Linux and Windows, this shows up as several different devices (one for each card it supports, like MMC, SD, Memory Stick, etc) in case that matters. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 21:34:08 2008 From: trac at haiku-os.org (bga) Date: Sat, 30 Aug 2008 19:34:08 -0000 Subject: [Haiku-bugs] [Haiku] #2687: Multi-function USB card reader does not work. In-Reply-To: <038.64b1d42d138e2d74be44573b2ccc05c3@haiku-os.org> References: <038.64b1d42d138e2d74be44573b2ccc05c3@haiku-os.org> Message-ID: <047.15dd3892ea14a0948c72b4d963449738@haiku-os.org> #2687: Multi-function USB card reader does not work. --------------------------+------------------------------------------------- Reporter: bga | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Description changed by bga: Old description: > USB in general dose work on my machine. Even plugging in a pen-drive > works without problems. But I have this multi-function card reader that > does not work. When I connect it, I get these messages in syslog: > > KERN: usb_ehci: qtd (0x04028980) error: 0x00080248 > KERN: usb_ehci: qtd (0x04028b80) error: 0x00080248 > KERN: usb_ehci: qtd (0x04028d80) error: 0x00080248 > KERN: USB BusManager: error while setting device address > > In Linux and Windows, this shows up as several different devices (one for > each card it supports, like MMC, SD, Memory Stick, etc) in case that > matters. New description: USB in general dose work on my machine. Even plugging in a pen-drive works without problems. But I have this multi-function card reader that does not work. When I connect it, I get these messages in syslog: {{{ KERN: usb_ehci: qtd (0x04028980) error: 0x00080248 KERN: usb_ehci: qtd (0x04028b80) error: 0x00080248 KERN: usb_ehci: qtd (0x04028d80) error: 0x00080248 KERN: USB BusManager: error while setting device address }}} In Linux and Windows, this shows up as several different devices (one for each card it supports, like MMC, SD, Memory Stick, etc) in case that matters. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 21:47:01 2008 From: trac at haiku-os.org (kaliber) Date: Sat, 30 Aug 2008 19:47:01 -0000 Subject: [Haiku-bugs] [Haiku] #2688: lldiv is declared in stdlib.h, but not implemented (easy) Message-ID: <042.920b11a311d386a474a218ca22dd2868@haiku-os.org> #2688: lldiv is declared in stdlib.h, but not implemented (easy) -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Function lldiv() is declared in headers/posix/stdlib.h, but not implemented in src/system/libroot/posix/stdlib/div.c -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Aug 30 23:58:01 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 30 Aug 2008 21:58:01 -0000 Subject: [Haiku-bugs] [Haiku] #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " In-Reply-To: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> References: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> Message-ID: <054.c441df3bd76834b938cd81fa9ea7496e@haiku-os.org> #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " ---------------------------+------------------------------------------------ Reporter: revivaldbm | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): You have to provide more info for this to be helpful, like what platform you're building on (apparently some Linux), with what compiler and cross- compiler, and the complete output "jam" (and its subprocesses) produced. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 00:49:03 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 22:49:03 -0000 Subject: [Haiku-bugs] [Haiku] #2682: Network instability issues since net_timer changes In-Reply-To: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> References: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> Message-ID: <053.7f0f0fa4201109e19b5c1f62f31d33bf@haiku-os.org> #2682: Network instability issues since net_timer changes ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by anevilyak): Also note this affects svn, a checkout will go dead after a while. I'm now running a current build with only 26980/26981's changes reverted and it's checking out perfectly. So something in those changes is definitely the issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 01:15:36 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 30 Aug 2008 23:15:36 -0000 Subject: [Haiku-bugs] [Haiku] #2682: Network instability issues since net_timer changes In-Reply-To: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> References: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> Message-ID: <053.693401b4cc660a077233809dc31022de@haiku-os.org> #2682: Network instability issues since net_timer changes ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by bonefish): * priority: normal => high Comment: I also ran a few svn test checkouts (mostly to play with the I/O stuff, though) with "https://" (r27246). One failed with what was apparently a corruption of the protocol data (some XML parser error), though several others succeeded, the only difference being some changed debug output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 01:20:05 2008 From: trac at haiku-os.org (anevilyak) Date: Sat, 30 Aug 2008 23:20:05 -0000 Subject: [Haiku-bugs] [Haiku] #2682: Network instability issues since net_timer changes In-Reply-To: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> References: <044.daabb81a0de194b16f721ff00f4aa80c@haiku-os.org> Message-ID: <053.9a693604f1809cef0d2d10ccc7528604@haiku-os.org> #2682: Network instability issues since net_timer changes ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by anevilyak): That sounds like the sshd problem I was seeing. With svn (via svn+ssh) I'm simply seeing svn just halt in mid checkout, though it responds to ctrl+c ok. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 10:02:25 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 08:02:25 -0000 Subject: [Haiku-bugs] [Haiku] #2689: ftp does not release "tcp send" lock on exit (ctrl^C) Message-ID: <042.a8234ca32c3e03257578ac3c987b9ba5@haiku-os.org> #2689: ftp does not release "tcp send" lock on exit (ctrl^C) ------------------------------------+--------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- I ran ftp, hit ctrl^C before it could get connected (at least I think), then re-ran ftp and try to connect to the same server. It hangs on {{{ TCPEndpoint::_WaitForEstablished }}} It *seems* that the previous instance did not release the lock correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 10:04:27 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 08:04:27 -0000 Subject: [Haiku-bugs] [Haiku] #2690: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:464): fFirst != __null && fLast != _ ... ) Message-ID: <042.f9e9fe38319e132630f31081515768fa@haiku-os.org> #2690: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:464): fFirst != __null && fLast != _ ... ) ---------------------------+------------------------------------------------ Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Happene on shutdown after doing heavy I/O. {{{ list: 0x90bf1d38, element: 0x807b92c0 PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:464): fFirst != __null && fLast != __null && (fFirst != fLast || Welcome to Kernel Debugging Land... Thread 6949 "shutdown worker" running on CPU 0 kdebug> bt stack trace for thread 6949 "shutdown worker" kernel stack: 0x91ed1000 to 0x91ed5000 user stack: 0x70145000 to 0x70185000 frame caller :function + offset 0 91ed4a34 (+ 48) 800566a1 :invoke_debugger_command + 0x00f5 1 91ed4a64 (+ 64) 80056491 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 91ed4aa4 (+ 64) 80056819 :invoke_debugger_command_pipe + 0x009d 3 91ed4ae4 (+ 48) 80057d54 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 91ed4b14 (+ 64) 8005718e :EvaluateCommand__16ExpressionParserPCcRi + 0x02ba 5 91ed4b54 (+ 224) 8005917c :evaluate_debug_command + 0x0088 6 91ed4c34 (+ 64) 80054aa2 :kernel_debugger_loop__Fv + 0x01ae 7 91ed4c74 (+ 48) 80055675 :kernel_debugger + 0x0121 8 91ed4ca4 (+ 192) 80055549 :panic + 0x0029 9 91ed4d64 (+ 96) 8002bbf3 :write_cached_block__FP11block_cacheP12cached_blockb + 0x0133 10 91ed4dc4 (+ 64) 8002e306 :block_cache_sync + 0x006a 11 91ed4e04 (+ 48) 80598dd3 :_FlushLog__7JournalbT1 + 0x00e3 12 91ed4e34 (+ 48) 80598e1f :FlushLogAndBlocks__7Journal + 0x002b 13 91ed4e64 (+ 48) 8059cd8d :Sync__6Volume + 0x0025 14 91ed4e94 (+ 48) 8059df36 :bfs_sync__FP9fs_volume + 0x0022 15 91ed4ec4 (+ 64) 80092ff4 :fs_sync__Fl + 0x0144 16 91ed4f04 (+ 48) 80093519 :_kern_sync + 0x0019 17 91ed4f34 (+ 16) 800946cb :_user_sync + 0x000b 18 91ed4f44 (+ 100) 800be6f2 :pre_syscall_debug_done + 0x0002 (nearest) user iframe at 0x91ed4fa8 (end = 0x91ed5000) eax 0x57 ebx 0x5b6d40 ecx 0x70184ef0 edx 0xffff0104 esi 0x1802bfb0 edi 0x1802bdb8 ebp 0x70184f0c esp 0x91ed4fdc eip 0xffff0104 eflags 0x212 user esp 0x70184ef0 vector: 0x63, error code: 0x0 19 91ed4fa8 (+ 0) ffff0104 20 70184f0c (+ 64) 0024bdbf <_APP_>:_WorkerDoShutdown__15ShutdownProcess + 0x01e7 21 70184f4c (+ 48) 0024bb2c <_APP_>:_Worker__15ShutdownProcess + 0x0020 22 70184f7c (+ 48) 0024bb03 <_APP_>:_WorkerEntry__15ShutdownProcessPv + 0x001f 23 70184fac (+ 48) 0052ebd8 :_get_next_team_info + 0x005c (nearest) 24 70184fdc (+ 0) 70184fec 258174:shutdown worker_6949_stack at 0x70145000 + 0x3ffec kdebug> reboot }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 10:13:28 2008 From: trac at haiku-os.org (revivaldbm) Date: Sun, 31 Aug 2008 08:13:28 -0000 Subject: [Haiku-bugs] [Haiku] #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " In-Reply-To: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> References: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> Message-ID: <054.4d8f604396968c85772ed62658e8a434@haiku-os.org> #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " ---------------------------+------------------------------------------------ Reporter: revivaldbm | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by revivaldbm): Right then, as you have been able to tell, I'm running Linux, Fedora 9 is the distro, the cross-compiler was 2.95, and the output of jam in full was (without the multiple "patience" messages): ...found 71264 target(s)... ...updating 8244 target(s)... InitScript1 generated/haiku.image-init-vars C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o src/tools/fs_shell/unistd.cpp:36:23: error: stropts.h: No such file or directory src/tools/fs_shell/unistd.cpp: In function ?int fssh_ioctl(int, long unsigned int, ...)?: src/tools/fs_shell/unistd.cpp:173: error: ?ioctl? was not declared in this scope cc -c "src/tools/fs_shell/unistd.cpp" -O -Wall -Wno-trigraphs -Wno-ctor- dtor-privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign- compare -Wno-multichar -DFS_SHELL=1 -D_ZETA_USING_DEPRECATED_API_=1 -D_ZETA_TS_FIND_DIR_=1 -DARCH_x86 -D_NO_INLINE_ASM -D__INTEL__ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DHAIKU_HOST_PLATFORM_LINUX -iquote build/user_config_headers -iquote build/config_headers -iquote src/tools/fs_shell -iquote generated/objects/common/tools/fs_shell -iquote generated/objects/linux/x86/common/tools/fs_shell -iquote generated/objects/haiku/x86/common/tools/fs_shell -I headers/build -I headers/build/os -I headers/build/os/kernel -I headers/build/os/storage -I headers/build/os/support -I headers/private/fs_shell -I headers/private/shared -I headers/build/host/linux -o "generated/objects/linux/x86/release/tools/fs_shell/unistd.o" ; ...failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o ... ...skipped fs_shell.a for lack of fs_shell.a(unistd.o)... ...skipped bfs_shell for lack of fs_shell.a... ...skipped haiku.image-init-vars for lack of bfs_shell... ...skipped haiku.image for lack of haiku.image-init-vars... ...failed updating 1 target(s)... ...skipped 4 target(s)... ...updated 1 target(s)... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 10:58:03 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 08:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #2688: lldiv is declared in stdlib.h, but not implemented (easy) In-Reply-To: <042.920b11a311d386a474a218ca22dd2868@haiku-os.org> References: <042.920b11a311d386a474a218ca22dd2868@haiku-os.org> Message-ID: <051.1bb06a58465bc37eb81314bf2a9b4f93@haiku-os.org> #2688: lldiv is declared in stdlib.h, but not implemented (easy) --------------------------------+------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by andreasf): * cc: andreas.faerber at web.de (added) Comment: Salvatore was searching for unimplemented POSIX functions recently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 11:50:15 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 09:50:15 -0000 Subject: [Haiku-bugs] [Haiku] #2691: TemplateNotFound: Template "macros.rss" not found Message-ID: <043.fbd5d6e013d5429bd03c2677a09b035e@haiku-os.org> #2691: TemplateNotFound: Template "macros.rss" not found --------------------------+------------------------------------------------- Reporter: andreasf | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- ==== How to Reproduce ==== While doing a GET operation on `/log/`, Trac issued an internal error. ''This I got when checking why the log feed (the one we're supposed to use instead of shortened Timeline) doesn't refresh:'' http://dev.haiku-os.org/log/?verbose=on&format=rss&limit=50 Request parameters: {{{ {'format': u'rss', 'limit': u'50', 'path': u'/', 'verbose': u'on'} }}} User Agent was: `Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_4; de-de) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.2 Safari/525.20.1` ==== System Information ==== || '''Trac''' || `0.11.1` || || '''Python''' || `2.5.1 (r251:54863, Nov 3 2007, 02:54:36) [C]` || || '''setuptools''' || `0.6c8` || || '''psycopg2''' || `2.0.6` || || '''Genshi''' || `0.5` || || '''Pygments''' || `0.10` || || '''Subversion''' || `1.4.5 (r25188)` || || '''jQuery:''' || `1.2.6` || ==== Python Traceback ==== {{{ Traceback (most recent call last): File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/main.py", line 423, in _dispatch_request dispatcher.dispatch(req) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/main.py", line 219, in dispatch data, content_type) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/chrome.py", line 683, in render_template template = self.load_template(filename, method=method) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/chrome.py", line 667, in load_template return self.templates.load(filename, cls=cls) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 221, in load filename, encoding=encoding) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 259, in _instantiate allow_exec=self.allow_exec) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/base.py", line 377, in __init__ self.stream = list(self._prepare(self._parse(source, encoding))) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/base.py", line 444, in _prepare cls=cls or self.__class__) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 231, in load raise TemplateNotFound(filename, search_path) TemplateNotFound: Template "macros.rss" not found }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 12:12:18 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 10:12:18 -0000 Subject: [Haiku-bugs] [Haiku] #2691: TemplateNotFound: Template "macros.rss" not found In-Reply-To: <043.fbd5d6e013d5429bd03c2677a09b035e@haiku-os.org> References: <043.fbd5d6e013d5429bd03c2677a09b035e@haiku-os.org> Message-ID: <052.5996074eabc9e83a8f7b5f9768170bfb@haiku-os.org> #2691: TemplateNotFound: Template "macros.rss" not found ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by andreasf): The Timeline feed does not seem affected btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 12:43:42 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 10:43:42 -0000 Subject: [Haiku-bugs] [Haiku] #2688: lldiv is declared in stdlib.h, but not implemented (easy) In-Reply-To: <042.920b11a311d386a474a218ca22dd2868@haiku-os.org> References: <042.920b11a311d386a474a218ca22dd2868@haiku-os.org> Message-ID: <051.d45da1869b5c419368e79d8cf23a2885@haiku-os.org> #2688: lldiv is declared in stdlib.h, but not implemented (easy) --------------------------------+------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by emitrax): * status: new => closed * resolution: => fixed Comment: Replying to [comment:1 andreasf]: > Salvatore was searching for unimplemented POSIX functions recently. Not what I had in mind. ;-) Implemented in r27250. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 14:13:23 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 12:13:23 -0000 Subject: [Haiku-bugs] [Haiku] #2093: Missing POSIX headers libgen.h (was: Missing POSIX headers) In-Reply-To: <042.b47a244b90b3a72148ccd293e3525aea@haiku-os.org> References: <042.b47a244b90b3a72148ccd293e3525aea@haiku-os.org> Message-ID: <051.55e5e8d35a27a0708b17a1ef2ae487e8@haiku-os.org> #2093: Missing POSIX headers libgen.h --------------------------+------------------------------------------------- Reporter: begasus | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by emitrax): features.h seems not to be a POSIX header. Opening a different ticket for fenv.h as it is not related to libgen.h. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 14:13:50 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 12:13:50 -0000 Subject: [Haiku-bugs] [Haiku] #2093: Missing POSIX header libgen.h (was: Missing POSIX headers libgen.h) In-Reply-To: <042.b47a244b90b3a72148ccd293e3525aea@haiku-os.org> References: <042.b47a244b90b3a72148ccd293e3525aea@haiku-os.org> Message-ID: <051.7d2332b09849a5efd2216eecad03fbe3@haiku-os.org> #2093: Missing POSIX header libgen.h --------------------------+------------------------------------------------- Reporter: begasus | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 14:38:36 2008 From: trac at haiku-os.org (emitrax) Date: Sun, 31 Aug 2008 12:38:36 -0000 Subject: [Haiku-bugs] [Haiku] #2692: Missing POSIX header fenv.h Message-ID: <042.cfc8ff7bc5121b37df840a965a583acd@haiku-os.org> #2692: Missing POSIX header fenv.h -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- http://www.opengroup.org/onlinepubs/000095399/basedefs/fenv.h.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 15:30:13 2008 From: trac at haiku-os.org (bonefish) Date: Sun, 31 Aug 2008 13:30:13 -0000 Subject: [Haiku-bugs] [Haiku] #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " In-Reply-To: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> References: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> Message-ID: <054.30ff978c4c87de6c71dc0362388f6d8a@haiku-os.org> #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " ---------------------------+------------------------------------------------ Reporter: revivaldbm | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:2 revivaldbm]: > Right then, as you have been able to tell, I'm running Linux, Fedora 9 is the distro, the cross-compiler was 2.95, and the output of jam in full was (without the multiple "patience" messages): > > ...found 71264 target(s)... > ...updating 8244 target(s)... > InitScript1 generated/haiku.image-init-vars > C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o > src/tools/fs_shell/unistd.cpp:36:23: error: stropts.h: No such file or directory Seems to be that the Fedora (or Linux or glibc) folks have made a brilliant move by removing the header which is the POSIXly correct place for the ioctl() prototype: [http://www.opengroup.org/onlinepubs/009695399/basedefs/stropts.h.html stropts.h]. Google turned up [http://eatmyrandom.blogspot.com/2008/05 /stroptsh-no-such-file-or-directory.html this article]. Unless more distributions start removing this header, I don't feel particularly inclined to introduce special-casing for this idiocy. Please just {{{touch /usr/include/stropts.h}}} for the time being. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 15:31:09 2008 From: trac at haiku-os.org (oco) Date: Sun, 31 Aug 2008 13:31:09 -0000 Subject: [Haiku-bugs] [Haiku] #2693: TemplateNotFound: Template "macros.html" not found Message-ID: <038.4e24f14047e17592f8c304390866e44c@haiku-os.org> #2693: TemplateNotFound: Template "macros.html" not found --------------------------+------------------------------------------------- Reporter: oco | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- ==== How to Reproduce ==== While doing a GET operation on `/log/`, Trac issued an internal error. ''It seems that the revision log view (in Browse source) does not work anymore'' Request parameters: {{{ {'path': u'/'} }}} User Agent was: `Mozilla/5.0 (BeOS; U; Haiku BePC; en-US; rv:1.8.1.12) Gecko/20080210 BonEcho/2.0.0.12` ==== System Information ==== || '''Trac''' || `0.11.1` || || '''Python''' || `2.5.1 (r251:54863, Nov 3 2007, 02:54:36) [C]` || || '''setuptools''' || `0.6c8` || || '''psycopg2''' || `2.0.6` || || '''Genshi''' || `0.5` || || '''Pygments''' || `0.10` || || '''Subversion''' || `1.4.5 (r25188)` || || '''jQuery:''' || `1.2.6` || ==== Python Traceback ==== {{{ Traceback (most recent call last): File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/main.py", line 423, in _dispatch_request dispatcher.dispatch(req) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/main.py", line 219, in dispatch data, content_type) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/chrome.py", line 683, in render_template template = self.load_template(filename, method=method) File "/opt/csw/lib/python/site- packages/Trac-0.11.1-py2.5.egg/trac/web/chrome.py", line 667, in load_template return self.templates.load(filename, cls=cls) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 221, in load filename, encoding=encoding) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 259, in _instantiate allow_exec=self.allow_exec) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/base.py", line 377, in __init__ self.stream = list(self._prepare(self._parse(source, encoding))) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/base.py", line 444, in _prepare cls=cls or self.__class__) File "build/bdist.solaris-2.10-i86pc/egg/genshi/template/loader.py", line 231, in load raise TemplateNotFound(filename, search_path) TemplateNotFound: Template "macros.html" not found }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 15:43:13 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 13:43:13 -0000 Subject: [Haiku-bugs] [Haiku] #2693: TemplateNotFound: Template "macros.html" not found In-Reply-To: <038.4e24f14047e17592f8c304390866e44c@haiku-os.org> References: <038.4e24f14047e17592f8c304390866e44c@haiku-os.org> Message-ID: <047.b93da6375a922a1a9a1be79f57d7ee46@haiku-os.org> #2693: TemplateNotFound: Template "macros.html" not found ---------------------------+------------------------------------------------ Reporter: oco | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: andreas.faerber at web.de (added) Comment: Probably related to #2691 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 21:34:21 2008 From: trac at haiku-os.org (oco) Date: Sun, 31 Aug 2008 19:34:21 -0000 Subject: [Haiku-bugs] [Haiku] #2694: [pairs] Sometime, pairs show two times the same pair. In-Reply-To: <038.813f97d4e1b4c1cd995324195b5c748d@haiku-os.org> References: <038.813f97d4e1b4c1cd995324195b5c748d@haiku-os.org> Message-ID: <047.7b607a1fa57be1dc21b74a485e87dc71@haiku-os.org> #2694: [pairs] Sometime, pairs show two times the same pair. ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by oco): Here is the screenshot : http://olivier.coursiere.free.fr/images/TwoTimesTheSamePair.png I can not upload it here right now because of bug 2660 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 15:59:18 2008 From: trac at haiku-os.org (revivaldbm) Date: Sun, 31 Aug 2008 13:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " In-Reply-To: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> References: <045.bcb63f75c5507f9d5f682b6264755f74@haiku-os.org> Message-ID: <054.d6d56a369689916ca47076c5ea002d87@haiku-os.org> #2686: "failed C++ generated/objects/linux/x86/release/tools/fs_shell/unistd.o " ---------------------------+------------------------------------------------ Reporter: revivaldbm | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by revivaldbm): I done so, however it still won't compile: src/tools/fs_shell/unistd.cpp: In function ?int fssh_ioctl(int, long unsigned int, ...)?: src/tools/fs_shell/unistd.cpp:173: error: ?ioctl? was not declared in this scope I downloaded a copy of stropts.h from koders.com, however there are other header files it requires which I cannot find. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 17:11:37 2008 From: trac at haiku-os.org (oco) Date: Sun, 31 Aug 2008 15:11:37 -0000 Subject: [Haiku-bugs] [Haiku] #2694: [pairs] Sometime, pairs show two times the same pair. Message-ID: <038.813f97d4e1b4c1cd995324195b5c748d@haiku-os.org> #2694: [pairs] Sometime, pairs show two times the same pair. --------------------------+------------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Sometime, pairs show two times the same pair as you can see on the attached image. I am not sure if it was intended. On the other hand, it add some complexity to the game... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 17:16:41 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 15:16:41 -0000 Subject: [Haiku-bugs] [Haiku] #2695: [XSI] Implement SA_SIGINFO for sigaction Message-ID: <043.2aada406c5c434c8914ba048254ebb99@haiku-os.org> #2695: [XSI] Implement SA_SIGINFO for sigaction -------------------------+-------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Haiku currently supports default POSIX signal handlers with no additional signal info, and BeOS' derived signal handlers with additional register access and user-supplied data. Not yet supported are the extended POSIX signal handlers with {{{siginfo_t}}} and {{{ucontext_t}}} arguments. Some parts thereof are already prepared in the headers but commented out since not implemented on the kernel side. http://www.opengroup.org/onlinepubs/009695399/functions/sigaction.html I had recently submitted a first draft patch for the x86 kernel side signal frame setup. Some fields are not initialized yet, and some information is not (yet) easily obtainable according to Ingo. http://www.freelists.org/archives/haiku-development/08-2008/msg00262.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 21:40:42 2008 From: trac at haiku-os.org (kaliber) Date: Sun, 31 Aug 2008 19:40:42 -0000 Subject: [Haiku-bugs] [Haiku] #2696: unimplemented functions Message-ID: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> #2696: unimplemented functions -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I wrote a buggy script which detects declared but not implemented functions (symbols) in Haiku. It found (not a full list yet): {{{ stdio.h: _ftell setjmp.h: _setjmp nl_types.h: catclose catgets catopen math.h: __fpclassifyl __signbitf gamma_r gammaf_r iconv.h: functions implemented in libtextencoding? search.h: hcreate hdestroy hsearch remque stdlib.h: random_r setstate_r srandom_r wctype.h: towctrans wchar.h: fgetws getwchar wcsftime libio.h: _IO_feof_unlocked _IO_ferror_unlocked _IO_getc_unlocked ? _IO_peekc_unlocked ? _IO_putc_unlocked ? }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 17:28:10 2008 From: trac at haiku-os.org (andreasf) Date: Sun, 31 Aug 2008 15:28:10 -0000 Subject: [Haiku-bugs] [Haiku] #2660: [Trac] can't attach files In-Reply-To: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> References: <040.d2d04a15553399068990b155cbf15cea@haiku-os.org> Message-ID: <049.11350f15a940d848ee619ac327c1ff79@haiku-os.org> #2660: [Trac] can't attach files ---------------------------+------------------------------------------------ Reporter: diver | Owner: nielx Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: andreas.faerber at web.de (added) * status: closed => reopened * resolution: fixed => Comment: Just encountered the same issue at ticket #2695. In between uniqueness messages as above, on one try I also got a "too many files open" error with non-styled Python traceback. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Aug 31 20:48:49 2008 From: trac at haiku-os.org (aldeck) Date: Sun, 31 Aug 2008 18:48:49 -0000 Subject: [Haiku-bugs] [Haiku] #591: [Deskbar] doesn't redraw it's shelf In-Reply-To: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> References: <040.c35092ca1f9369e6b422d7499c4b39a3@haiku-os.org> Message-ID: <049.aba92c4df19194861ea87790e8a5480f@haiku-os.org> #591: [Deskbar] doesn't redraw it's shelf -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: Fixed in r27258 -- Ticket URL: Haiku The Haiku operating system.