From trac at haiku-os.org Mon Oct 1 04:37:09 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 02:37:09 -0000 Subject: [Haiku-bugs] [Haiku] #1490: VLC opens videos in a tiny window In-Reply-To: <042.bb5519b82b1d76c33e484bb80d5bd914@haiku-os.org> References: <042.bb5519b82b1d76c33e484bb80d5bd914@haiku-os.org> Message-ID: <051.f2bc487196861aee67daf90f4f8be694@haiku-os.org> #1490: VLC opens videos in a tiny window ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): Confirmed fix, VLC plays videos fine now. Nice work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 06:02:34 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 04:02:34 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.01c8a8a721a67fa35344fd08074a977e@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ------------------------------+--------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Tracker | Version: R1 development Resolution: | Platform: x86 ------------------------------+--------------------------------------------- Comment (by scottmc): I'm seen it happen on startup with r22389, not every reboot and not always tracker. Saw deskbar crash on the very first r22389 bootup, pressing ctrl-alt-del then restart desktop brought it back. In 10 or so reboots i've seen tracker crash 2 or 3 of those times, deskbar once, and even had media_server crash once. Didn't see this happen prior to this image, my previous image was from 4-5 days ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 06:56:05 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 04:56:05 -0000 Subject: [Haiku-bugs] [Haiku] #1510: System freezes when trying to "SaveAs" from StyledEdit Message-ID: <042.61d2bcf9860bd0c992afb863027e91fa@haiku-os.org> #1510: System freezes when trying to "SaveAs" from StyledEdit --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- I think it's happening elsewhere as well, but I am able to repeat the failure by opening up a text file in StyledEdit and trying to "SaveAs". Everything freezes up except the mouse. This is with r22389 and may or may not have something to do with #1509. I'll try it again and press F12 this time and see if I can get more debug info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 13:08:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 11:08:18 -0000 Subject: [Haiku-bugs] [Haiku] #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 Message-ID: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- occured with r22394 (but might be related to the ahci driver) PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0xa1 "w>add-ons" kernel stack: 0x947c4000 to 0x947c8000 user stack: 0x70249000 to 0x70289000 frame caller :function + offset 947c70c0 (+ 52) 80083321 :invoke_command + 0x0075 947c70f4 (+ 48) 80083572 :kernel_debugger + 0x020e 947c7124 (+ 176) 80083609 :panic + 0x002d 947c71d4 (+ 32) 8008c3ef :x86_push_iframe + 0x0026 947c71f4 (+ 128) 8008b641 :i386_handle_trap + 0x002a 947c7274 (+ 88) 8008e34e :kernel_stack + 0x0005 (nearest) 947c72cc (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 947c73a4 (+ 48) 8005c412 :vm_page_fault + 0x0034 947c73d4 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x947c746c (end = 0x947c74c0) eax 0x815be82b ebx 0x908b0000 ecx 0xe8458000 edx 0xe8458d00 esi 0x0 edi 0xe8458d04 ebp 0x947c74bc esp 0x947c749c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 947c7464 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 947c74bc (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 947c7594 (+ 48) 8005c412 :vm_page_fault + 0x0034 947c75c4 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x947c765c (end = 0x947c76b0) eax 0x815be82b ebx 0x908b0000 ecx 0xe8458000 edx 0xe8458d00 esi 0x0 edi 0xe8458d04 ebp 0x947c76ac esp 0x947c768c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 947c7654 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 947c76ac (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 947c7784 (+ 48) 8005c412 :vm_page_fault + 0x0034 947c77b4 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x947c784c (end = 0x947c78a0) eax 0x815be82b ebx 0x908b0000 ecx 0x947c7000 edx 0xe8458d00 esi 0x908b0000 edi 0x947c790b ebp 0x947c789c esp 0x947c787c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 947c7844 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 947c789c (+ 40) 800560b5 :_Z16test_lock_memoryP16vm_address_spacemRb + 0x0029 947c78c4 (+ 96) 8005c2a7 :lock_memory + 0x0087 947c7924 (+ 64) 8026ae79 :block_io_readv + 0x0039 947c7964 (+ 144) 80043677 :_Z16devfs_read_pagesPvS_S_xPK5iovecmPmb + 0x00f7 947c79f4 (+ 64) 80047fa8 :vfs_read_pages + 0x0034 947c7a34 (+ 752) 80063b10 :_Z8pages_ioP14file_cache_refxPK5iovecmPmb + 0x00c0 947c7d24 (+ 32) 80063f73 :file_cache_read_pages + 0x001f 947c7d44 (+ 64) 80259605 :_Z14bfs_read_pagesPvS_S_xPK5iovecmPmb + 0x00fb 947c7d84 (+ 64) 80047fa8 :vfs_read_pages + 0x0034 947c7dc4 (+ 64) 80065024 :_Z10store_readP8vm_storexPK5iovecmPmb + 0x0032 947c7e04 (+ 224) 8005b980 :_Z13vm_soft_faultmbb + 0x0422 947c7ee4 (+ 48) 8005c412 :vm_page_fault + 0x0034 947c7f14 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x947c7fac (end = 0x947c8000) eax 0x4 ebx 0x6232a4 ecx 0x70288af0 edx 0x0 esi 0x70288af0 edi 0x18106b10 ebp 0x70288acc esp 0x947c7fdc eip 0x5cb480 eflags 0x10206 user esp 0x70288a90 vector: 0xe, error code: 0x4 947c7fa4 (+ 0) 005cb480 :unknown + 0x133480 70288acc (+ 96) 005895fc :unknown + 0xf15fc 70288b2c (+ 128) 0058b138 :unknown + 0xf3138 70288bac (+ 64) 0051c1b0 :unknown + 0x841b0 70288bec (+ 48) 0051b060 :unknown + 0x83060 70288c1c (+ 128) 002b6226 :unknown + 0xb4226 70288c9c (+ 32) 002b6273 :unknown + 0xb4273 70288cbc (+ 640) 0035d175 :unknown + 0x15b175 70288f3c (+ 96) 00359904 :unknown + 0x157904 70288f9c (+ 32) 002b79ee :unknown + 0xb59ee 70288fbc (+ 32) 0064690e :unknown + 0x2190e 70288fdc (+ 0) 70288fec 1416:w>TrackerWindow_a1_stack at 0x70249000 + 0x3ffec kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 13:17:57 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 11:17:57 -0000 Subject: [Haiku-bugs] [Haiku] #1512: deadlock after clicking on Deskbar Message-ID: <050.70652cbc7cad0548d42aa7be3175e7b3@haiku-os.org> #1512: deadlock after clicking on Deskbar -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- After clicking on Deskbar (which doesn't react), the mouse continues to work for about 1 second, then everything freezes reproduceable. Occured with r22394 PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> wait 4 thread id state sem/cv cpu pri stack team name 0x90ae9800 82 waiting 4 - 104 0x94649000 47 AT Keyboard 1 watcher 0x90afb800 85 waiting 4 - 15 0x94668000 54 w>Deskbar 0x9090a800 29 waiting 4 - 5 0x803c0000 1 syslog sender 0x90a5d000 69 waiting 4 - 10 0x90703000 56 big brother is watching you 0x90a29000 4d waiting 4 - 103 0x906cb000 47 _input_server_event_loop_ 0x90a2d000 51 waiting 4 - 90 0x906db000 37 event loop 0x90988000 32 waiting 4 - 10 0x803d3000 2f timer_thread 0x9098e000 36 waiting 4 - 10 0x803e3000 36 net_server kdebug> sem 4 SEM: 0x93f5f0b0 id: 0x4 name: 'kernel_aspacelock' owner: 0x0 count: 0xfffffff8 queue: 85 51 4d 32 69 36 82 29 last acquired by: 133, count: 1024 last released by: 133, count: 1 kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 13:37:54 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 11:37:54 -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.4aa5a5f566ac94e055a9eeb0168c04d9@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by jackburton): r22392 works fine here (r22393 and r22394 don't seem to change anything important). No AHCI here, though, so it might be related to that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 14:15:38 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 12:15:38 -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.01d82dba179db0e0c3351557f042ad85@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): This might be an SMP problem. This is a core 2 duo sytem, running at 2.4 GHz. I "downclocked" it to 900 MHz and now I'm able to use Deskbar for a few seconds, can even run the About app. However, it deadlocks soon, with the same semaphore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 14:42:04 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 12:42:04 -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.d6b7c8ee740dd3c013fdf4b39346bb02@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => critical Comment: Can you reproduce this with GCC 2.95.3? Also, can you provide a stack trace from the deskbar thread? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 14:44:40 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 12:44:40 -0000 Subject: [Haiku-bugs] [Haiku] #1513: write access attempted on read-only area 0x441 at 0x946667d9 Message-ID: <050.93b7f14f49d2754969c5483c58c79d7e@haiku-os.org> #1513: write access attempted on read-only area 0x441 at 0x946667d9 -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- {{{ write access attempted on read-only area 0x441 at 0x946667d9 vm_page_fault: vm_soft_fault returned error 'Permission denied' on fault at 0x946667d9, ip 0x80062c81, write 1, user 0, thread 0x4c CPU 1 halted! PANIC: vm_page_fault: unhandled page fault in kernel space at 0x946667d9, ip 0x80062c81 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x4c "daemon" kernel stack: 0x906c7000 to 0x906cb000 user stack: 0x70000000 to 0x70040000 frame caller :function + offset 906ca9f4 (+ 52) 80083321 :invoke_command + 0x0075 906caa28 (+ 48) 80083572 :kernel_debugger + 0x020e 906caa58 (+ 176) 80083609 :panic + 0x002d 906cab08 (+ 64) 8005c487 :vm_page_fault + 0x00a9 906cab48 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x906cabe0 (end = 0x906cac34) eax 0xffffe23f ebx 0x946667b5 ecx 0x1f edx 0x906cac20 esi 0xec835356 edi 0x909a5600 ebp 0x906cac44 esp 0x906cac10 eip 0x80062c81 eflags 0x10246 vector: 0xe, error code: 0x3 906cabd8 (+ 108) 80062c81 :cache_start_sub_transaction + 0x00ab 906cac44 (+ 48) 8025286d :_ZN7Journal4LockEP11Transaction + 0x0087 906cac74 (+ 32) 8025292c :_ZN11Transaction5StartEP6Volumex + 0x0032 906cac94 (+ 64) 8024e34d :_ZN5Inode7WriteAtER11TransactionxPKhPm + 0x00bb 906cacd4 (+ 112) 8025a4db :_Z9bfs_writePvS_S_xPKvPm + 0x0103 906cad44 (+ 48) 800480b8 :_Z10file_writeP15file_descriptorxPKvPm + 0x002e 906cad74 (+ 64) 80047592 :_user_write + 0x00b2 906cadb4 (+ 368) 80038c93 :syscall_dispatcher + 0x0e59 906caf24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 iframe at 0x906cafac (end = 0x906cb000) eax 0x65 ebx 0x537100 ecx 0x400 edx 0x0 esi 0x29 edi 0x7003dfb9 ebp 0x7003be4c esp 0x906cafdc eip 0xffff0102 eflags 0x212 vector: 0x63, error code: 0x0 906cafa4 (+ 0) ffff0102 7003be4c (+8448) 002036fe :unknown + 0x36fe 7003df4c (+8272) 00202a88 :unknown + 0x2a88 7003ff9c (+ 32) 00202acb :unknown + 0x2acb 7003ffbc (+ 32) 004bd90e :unknown + 0x2190e 7003ffdc (+ 0) 7003ffec 641:daemon_4c_stack at 0x70000000 + 0x3ffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 14:48:49 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 12:48:49 -0000 Subject: [Haiku-bugs] [Haiku] #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 In-Reply-To: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> References: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> Message-ID: <059.de1277d1a1b99cfcafa849bc525787d1@haiku-os.org> #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): The problem happens less frequently when underclocking the CPU to 900 MHz Here are some other back traces for the same ASSERT, made at full CPU speed. {{{ CPU 1 halted! PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0xac "w>TrackerWindow" kernel stack: 0x90707000 to 0x9070b000 user stack: 0x70000000 to 0x70040000 frame caller :function + offset 9070a5f0 (+ 52) 80083321 :invoke_command + 0x0075 9070a624 (+ 48) 80083572 :kernel_debugger + 0x020e 9070a654 (+ 176) 80083609 :panic + 0x002d 9070a704 (+ 32) 8008c3ef :x86_push_iframe + 0x0026 9070a724 (+ 128) 8008b641 :i386_handle_trap + 0x002a 9070a7a4 (+ 88) 8008e34e :kernel_stack + 0x0005 (nearest) 9070a7fc (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 9070a8d4 (+ 48) 8005c412 :vm_page_fault + 0x0034 9070a904 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x9070a99c (end = 0x9070a9f0) eax 0x815be82b ebx 0x908b0000 ecx 0xe8458000 edx 0xe8458d00 esi 0x0 edi 0xe8458d04 ebp 0x9070a9ec esp 0x9070a9cc eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 9070a994 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 9070a9ec (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 9070aac4 (+ 48) 8005c412 :vm_page_fault + 0x0034 9070aaf4 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x9070ab8c (end = 0x9070abe0) eax 0x815be82b ebx 0x908b0000 ecx 0xe8d44000 edx 0xe8458d00 esi 0x0 edi 0xe8d44595 ebp 0x9070abdc esp 0x9070abbc eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 9070ab84 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 9070abdc (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 9070acb4 (+ 48) 8005c412 :vm_page_fault + 0x0034 9070ace4 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x9070ad7c (end = 0x9070add0) eax 0x1 ebx 0xe8d44589 ecx 0x93f5f000 edx 0xe8d44595 esi 0x1 edi 0x9466c7b5 ebp 0x9070ade4 esp 0x9070adac eip 0x800911d5 eflags 0x10286 vector: 0xe, error code: 0x2 9070ad74 (+ 112) 800911d5 :atomic_add + 0x0008 (nearest) 9070ade4 (+ 48) 80059625 :vm_area_get_locked_cache + 0x002b 9070ae14 (+ 208) 8005b691 :_Z13vm_soft_faultmbb + 0x0133 9070aee4 (+ 48) 8005c412 :vm_page_fault + 0x0034 9070af14 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x9070afac (end = 0x9070b000) eax 0x3f ebx 0x6c0100 ecx 0x18189ba0 edx 0x18189ba0 esi 0x1818a068 edi 0x9 ebp 0x7003f75c esp 0x9070afdc eip 0x64f6dc eflags 0x10202 user esp 0x7003f734 vector: 0xe, error code: 0x6 9070afa4 (+ 0) 0064f6dc :unknown + 0x2a6dc 7003f75c (+ 48) 0064fc76 :unknown + 0x2ac76 7003f78c (+ 80) 0064febc :unknown + 0x2aebc 7003f7dc (+ 48) 006510d7 :unknown + 0x2c0d7 7003f80c (+ 32) 002bbe9a :unknown + 0xb9e9a 7003f82c (+ 32) 002bbf7b :unknown + 0xb9f7b 7003f84c (+ 48) 002bbfac :unknown + 0xb9fac 7003f87c (+ 320) 00517eae :unknown + 0x7feae 7003f9bc (+ 736) 0051cbf6 :unknown + 0x84bf6 7003fc9c (+ 32) 002b6282 :unknown + 0xb4282 7003fcbc (+ 640) 0035d175 :unknown + 0x15b175 7003ff3c (+ 96) 00359904 :unknown + 0x157904 7003ff9c (+ 32) 002b79ee :unknown + 0xb59ee 7003ffbc (+ 32) 0064690e :unknown + 0x2190e 7003ffdc (+ 0) 7003ffecPANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 }}} {{{ CPU 0 halted! PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 Welcome to Kernel Debugging Land... Running on CPU 1 kdebug> sc stack trace for thread 0x33 "main_mime" kernel stack: 0x803d7000 to 0x803db000 user stack: 0x70082000 to 0x700c2000 frame caller :function + offset 803d9c60 (+ 52) 80083321 :invoke_command + 0x0075 803d9c94 (+ 48) 80083572 :kernel_debugger + 0x020e 803d9cc4 (+ 176) 80083609 :panic + 0x002d 803d9d74 (+ 32) 8008c3ef :x86_push_iframe + 0x0026 803d9d94 (+ 128) 8008b641 :i386_handle_trap + 0x002a 803d9e14 (+ 88) 8008e34e :kernel_stack + 0x0005 (nearest) 803d9e6c (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 803d9f44 (+ 48) 8005c412 :vm_page_fault + 0x0034 803d9f74 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x803da00c (end = 0x803da060) eax 0x815be82b ebx 0x908b0000 ecx 0xe8458000 edx 0xe8458d00 esi 0x0 edi 0xe8458d04 ebp 0x803da05c esp 0x803da03c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 803da004 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 803da05c (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 803da134 (+ 48) 8005c412 :vm_page_fault + 0x0034 803da164 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x803da1fc (end = 0x803da250) eax 0x815be82b ebx 0x908b0000 ecx 0xe8458000 edx 0xe8458d00 esi 0x0 edi 0xe8458d04 ebp 0x803da24c esp 0x803da22c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 803da1f4 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 803da24c (+ 216) 8005b5ec :_Z13vm_soft_faultmbb + 0x008e 803da324 (+ 48) 8005c412 :vm_page_fault + 0x0034 803da354 (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x803da3ec (end = 0x803da440) eax 0x815be82b ebx 0x908b0000 ecx 0xa0243000 edx 0xe8458d00 esi 0x908b0000 edi 0x803da4ab ebp 0x803da43c esp 0x803da41c eip 0x80055fb4 eflags 0x10286 vector: 0xe, error code: 0x0 803da3e4 (+ 88) 80055fb4 :vm_area_lookup + 0x0026 803da43c (+ 40) 800560b5 :_Z16test_lock_memoryP16vm_address_spacemRb + 0x0029 803da464 (+ 96) 8005c2a7 :lock_memory + 0x0087 803da4c4 (+ 192) 8026a979 :block_io_readwrite + 0x0495 803da584 (+ 48) 8026ae0c :block_io_readv_int + 0x0025 803da5b4 (+ 48) 8026ae3e :block_io_read + 0x002b 803da5e4 (+ 48) 80055511 :_ZN11IOScheduler7ProcessER9IORequest + 0x0047 803da614 (+ 128) 80043546 :_Z10devfs_readPvS_S_xS_Pm + 0x00d4 803da694 (+ 48) 80048084 :_Z9file_readP15file_descriptorxPvPm + 0x002e 803da6c4 (+ 64) 8004715f :_kern_read + 0x009f 803da704 (+ 48) 800960f8 :read_pos + 0x0036 803da734 (+ 80) 80061443 :_Z16get_cached_blockP11block_cachexPbb + 0x00f3 803da784 (+ 64) 80061583 :_Z25get_writable_cached_blockP11block_cachexxxlb + 0x0063 803da7c4 (+ 80) 80061f5a :block_cache_get_writable_etc + 0x00a2 803da814 (+ 48) 80061fb3 :block_cache_get_writable + 0x001f 803da844 (+ 96) 8024323d :_ZN10CachedNode13InternalSetToEP11Transactionx + 0x013b 803da8a4 (+ 48) 80243323 :_ZN10CachedNode19SetToWritableHeaderER11Transaction + 0x0065 803da8d4 (+ 80) 80243ab1 :_ZN9BPlusTree5SetToER11TransactionP5Inodel + 0x0095 803da924 (+ 32) 80243c72 :_ZN9BPlusTreeC1ER11TransactionP5Inodel + 0x0056 803da944 (+ 112) 8024afe7 :_ZN14InodeAllocator10CreateTreeEv + 0x005d 803da9b4 (+ 208) 8025029e :_ZN5Inode6CreateER11TransactionPS_PKclimPbPxPS2_ + 0x0544 803daa84 (+ 112) 802506df :_ZN5Inode15CreateAttributeER11TransactionPKcmPPS_ + 0x004f 803daaf4 (+ 384) 802509f4 :_ZN5Inode14WriteAttributeER11TransactionPKclxPKhPm + 0x0228 803dac74 (+ 64) 80247877 :_ZN9Attribute5WriteER11TransactionP11attr_cookiexPKhPm + 0x0055 803dacb4 (+ 128) 80259d59 :_Z14bfs_write_attrPvS_S_xPKvPm + 0x0079 803dad34 (+ 64) 80048457 :_Z10attr_writeP15file_descriptorxPKvPm + 0x0043 803dad74 (+ 64) 80047592 :_user_write + 0x00b2 803dadb4 (+ 368) 80038c93 :syscall_dispatcher + 0x0e59 803daf24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 iframe at 0x803dafac (end = 0x803db000) eax 0x65 ebx 0x576100 ecx 0x0 edx 0x0 esi 0xd edi 0x1802ff5b ebp 0x700c1c3c esp 0x803dafdc eip 0xffff0102 eflags 0x216 vector: 0x63, error code: 0x0 803dafa4 (+ 0) ffff0102 700c1c3c (+ 64) 003bb01e :unknown + 0x17601e 700c1c7c (+ 144) 003cf88d :unknown + 0x18a88d 700c1d0c (+ 48) 003cf9da :unknown + 0x18a9da 700c1d3c (+ 224) 0021e552 :unknown + 0x1e552 700c1e1c (+ 288) 0021e822 :unknown + 0x1e822 700c1f3c (+ 32) 002f9282 :unknown + 0xb4282 700c1f5c (+ 64) 002fa924 :unknown + 0xb5924 700c1f9c (+ 32) 002fa9ee :unknown + 0xb59ee 700c1fbc (+ 32) 004fc90e :unknown + 0x2190e 700c1fdc (+ 0) 700c1fec 346:main_mime_33_stack at 0x70082000 + 0x3ffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 15:02:10 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 13:02:10 -0000 Subject: [Haiku-bugs] [Haiku] #1514: PANIC: no range for address 0xffd283ff Message-ID: <050.a35e9f7b51b0b82a7728f60871f0e762@haiku-os.org> #1514: PANIC: no range for address 0xffd283ff -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- also there was no disk read error before, this happened: {{{ bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error CPU 1 halted! PANIC: no range for address 0xffd283ff }}} Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x117 "AboutSystem" kernel stack: 0x947a1000 to 0x947a5000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 947a4a40 (+ 52) 80083321 :invoke_command + 0x0075 947a4a74 (+ 48) 80083572 :kernel_debugger + 0x020e 947a4aa4 (+ 176) 80083609 :panic + 0x002d 947a4b54 (+ 48) 80060e96 :_ZN11block_cache4FreeEPv + 0x0034 947a4b84 (+ 48) 80062c7b :cache_start_sub_transaction + 0x00a5 947a4bb4 (+ 48) 8025286d :_ZN7Journal4LockEP11Transaction + 0x0087 947a4be4 (+ 32) 8025292c :_ZN11Transaction5StartEP6Volumex + 0x0032 947a4c04 (+ 64) 80259fc4 :_Z14bfs_create_dirPvS_PKciPx + 0x010a 947a4c44 (+ 336) 8004f904 :_Z10dir_createiPcib + 0x005e 947a4d94 (+ 48) 8004f991 :_user_create_dir + 0x0071 947a4dc4 (+ 352) 8003895d :syscall_dispatcher + 0x0b23 947a4f24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 iframe at 0x947a4fac (end = 0x947a5000) eax 0x4d ebx 0x55c100 ecx 0x3 edx 0x180103f0 esi 0x4ba31c edi 0x0 ebp 0x7ffe63e8 esp 0x947a4fdc eip 0xffff0102 eflags 0x212 vector: 0x63, error code: 0x0 947a4fa4 (+ 0) ffff0102 7ffe63e8 (+ 80) 004b267c :unknown + 0xf67c 7ffe6438 (+ 32) 004b2712 :unknown + 0xf712 7ffe6458 (+ 48) 004b27e9 :unknown + 0xf7e9 7ffe6488 (+ 128) 004ae3a5 :unknown + 0xb3a5 7ffe6508 (+ 96) 004ae72c :unknown + 0xb72c 7ffe6568 (+2032) 00205637 :unknown + 0x5637 7ffe6d58 (+ 176) 002072ef :unknown + 0x72ef 7ffe6e08 (+ 48) 00207464 :unknown + 0x7464 7ffe6e38 (+ 320) 002093f0 :unknown + 0x93f0 7ffe6568 (+2032) 00205637 :unknown + 0x5637 7ffe6d58 (+ 176) 002072ef :unknown + 0x72ef 7ffe6e08 (+ 48) 00207464 :unknown + 0x7464 7ffe6e38 (+ 320) 002093f0 :unknown + 0x93f0 7ffe6f78 (+ 52) 0020468d :unknown + 0x468d 7ffe6fac (+ 48) 00100104 1692:runtime_loader_seg0ro at 0x00100000 + 0x104 7ffe6fdc (+ 0) 7ffe6fec 1691:/boot/beos/apps/AboutSystem_mai at 0x7efe7000 + 0xffffec kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 15:03:16 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 13:03:16 -0000 Subject: [Haiku-bugs] [Haiku] #1514: PANIC: no range for address 0xffd283ff In-Reply-To: <050.a35e9f7b51b0b82a7728f60871f0e762@haiku-os.org> References: <050.a35e9f7b51b0b82a7728f60871f0e762@haiku-os.org> Message-ID: <059.eb69677d7c15eab54f0dd637a948c54a@haiku-os.org> #1514: PANIC: no range for address 0xffd283ff ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Old description: > also there was no disk read error before, this happened: > > {{{ > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: BPlusTree::SeekDown() could not open node 1024 > bfs: Insert:1266: General system error > bfs: Create:2363: General system error > bfs: WriteAttribute:898: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: BPlusTree::SeekDown() could not open node 1024 > bfs: Insert:1266: General system error > bfs: Create:2363: General system error > bfs: WriteAttribute:898: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: BPlusTree::SeekDown() could not open node 1024 > bfs: Insert:1266: General system error > bfs: Create:2363: General system error > bfs: WriteAttribute:898: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: BPlusTree::SeekDown() could not open node 1024 > bfs: Insert:1266: General system error > bfs: Create:2363: General system error > bfs: WriteAttribute:898: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 > bfs: b+tree node at 1024 could not be loaded > bfs: Find:1860: General system error > CPU 1 halted! > PANIC: no range for address 0xffd283ff > }}} > > Welcome to Kernel Debugging Land... > Running on CPU 0 > kdebug> bt > stack trace for thread 0x117 "AboutSystem" > kernel stack: 0x947a1000 to 0x947a5000 > user stack: 0x7efe7000 to 0x7ffe7000 > frame caller :function + offset > 947a4a40 (+ 52) 80083321 :invoke_command + 0x0075 > 947a4a74 (+ 48) 80083572 :kernel_debugger + 0x020e > 947a4aa4 (+ 176) 80083609 :panic + 0x002d > 947a4b54 (+ 48) 80060e96 :_ZN11block_cache4FreeEPv + 0x0034 > 947a4b84 (+ 48) 80062c7b :cache_start_sub_transaction + 0x00a5 > 947a4bb4 (+ 48) 8025286d :_ZN7Journal4LockEP11Transaction + > 0x0087 > 947a4be4 (+ 32) 8025292c :_ZN11Transaction5StartEP6Volumex + > 0x0032 > 947a4c04 (+ 64) 80259fc4 :_Z14bfs_create_dirPvS_PKciPx + 0x010a > 947a4c44 (+ 336) 8004f904 :_Z10dir_createiPcib + 0x005e > 947a4d94 (+ 48) 8004f991 :_user_create_dir + 0x0071 > 947a4dc4 (+ 352) 8003895d :syscall_dispatcher + 0x0b23 > 947a4f24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 > iframe at 0x947a4fac (end = 0x947a5000) > eax 0x4d ebx 0x55c100 ecx 0x3 edx 0x180103f0 > esi 0x4ba31c edi 0x0 ebp 0x7ffe63e8 esp 0x947a4fdc > eip 0xffff0102 eflags 0x212 > vector: 0x63, error code: 0x0 > 947a4fa4 (+ 0) ffff0102 > 7ffe63e8 (+ 80) 004b267c > :unknown + 0xf67c > 7ffe6438 (+ 32) 004b2712 > :unknown + 0xf712 > 7ffe6458 (+ 48) 004b27e9 > :unknown + 0xf7e9 > 7ffe6488 (+ 128) 004ae3a5 > :unknown + 0xb3a5 > 7ffe6508 (+ 96) 004ae72c > :unknown + 0xb72c > 7ffe6568 (+2032) 00205637 > :unknown + 0x5637 > 7ffe6d58 (+ 176) 002072ef > :unknown + 0x72ef > 7ffe6e08 (+ 48) 00207464 > :unknown + 0x7464 > 7ffe6e38 (+ 320) 002093f0 > :unknown + 0x93f0 > 7ffe6568 (+2032) 00205637 > :unknown + 0x5637 > 7ffe6d58 (+ 176) 002072ef > :unknown + 0x72ef > 7ffe6e08 (+ 48) 00207464 > :unknown + 0x7464 > 7ffe6e38 (+ 320) 002093f0 > :unknown + 0x93f0 > 7ffe6f78 (+ 52) 0020468d > :unknown + 0x468d > 7ffe6fac (+ 48) 00100104 1692:runtime_loader_seg0ro at 0x00100000 + 0x104 > 7ffe6fdc (+ 0) 7ffe6fec > 1691:/boot/beos/apps/AboutSystem_mai at 0x7efe7000 + 0xffffec > kdebug> New description: also there was no disk read error before, this happened: {{{ bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: BPlusTree::SeekDown() could not open node 1024 bfs: Insert:1266: General system error bfs: Create:2363: General system error bfs: WriteAttribute:898: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error bfs: invalid node (0xa0254400) read from offset 1024, inode at 90781 bfs: b+tree node at 1024 could not be loaded bfs: Find:1860: General system error CPU 1 halted! PANIC: no range for address 0xffd283ff Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x117 "AboutSystem" kernel stack: 0x947a1000 to 0x947a5000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 947a4a40 (+ 52) 80083321 :invoke_command + 0x0075 947a4a74 (+ 48) 80083572 :kernel_debugger + 0x020e 947a4aa4 (+ 176) 80083609 :panic + 0x002d 947a4b54 (+ 48) 80060e96 :_ZN11block_cache4FreeEPv + 0x0034 947a4b84 (+ 48) 80062c7b :cache_start_sub_transaction + 0x00a5 947a4bb4 (+ 48) 8025286d :_ZN7Journal4LockEP11Transaction + 0x0087 947a4be4 (+ 32) 8025292c :_ZN11Transaction5StartEP6Volumex + 0x0032 947a4c04 (+ 64) 80259fc4 :_Z14bfs_create_dirPvS_PKciPx + 0x010a 947a4c44 (+ 336) 8004f904 :_Z10dir_createiPcib + 0x005e 947a4d94 (+ 48) 8004f991 :_user_create_dir + 0x0071 947a4dc4 (+ 352) 8003895d :syscall_dispatcher + 0x0b23 947a4f24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 iframe at 0x947a4fac (end = 0x947a5000) eax 0x4d ebx 0x55c100 ecx 0x3 edx 0x180103f0 esi 0x4ba31c edi 0x0 ebp 0x7ffe63e8 esp 0x947a4fdc eip 0xffff0102 eflags 0x212 vector: 0x63, error code: 0x0 947a4fa4 (+ 0) ffff0102 7ffe63e8 (+ 80) 004b267c :unknown + 0xf67c 7ffe6438 (+ 32) 004b2712 :unknown + 0xf712 7ffe6458 (+ 48) 004b27e9 :unknown + 0xf7e9 7ffe6488 (+ 128) 004ae3a5 :unknown + 0xb3a5 7ffe6508 (+ 96) 004ae72c :unknown + 0xb72c 7ffe6568 (+2032) 00205637 :unknown + 0x5637 7ffe6d58 (+ 176) 002072ef :unknown + 0x72ef 7ffe6e08 (+ 48) 00207464 :unknown + 0x7464 7ffe6e38 (+ 320) 002093f0 :unknown + 0x93f0 7ffe6568 (+2032) 00205637 :unknown + 0x5637 7ffe6d58 (+ 176) 002072ef :unknown + 0x72ef 7ffe6e08 (+ 48) 00207464 :unknown + 0x7464 7ffe6e38 (+ 320) 002093f0 :unknown + 0x93f0 7ffe6f78 (+ 52) 0020468d :unknown + 0x468d 7ffe6fac (+ 48) 00100104 1692:runtime_loader_seg0ro at 0x00100000 + 0x104 7ffe6fdc (+ 0) 7ffe6fec 1691:/boot/beos/apps/AboutSystem_mai at 0x7efe7000 + 0xffffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 15:22:02 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 13:22:02 -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.bc2ae20189191ea42dc72ce4fc41c138@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): I couldn't exaclty reproduce it. A similar deadlock occured now, but the thread that acquired the semaphore seems to be gone. Please see attached logfile. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 15:24:48 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 13:24:48 -0000 Subject: [Haiku-bugs] [Haiku] #1515: Pagefault in arch_thread_init_kthread_stack Message-ID: <050.23857671f43e493322603210ef192649@haiku-os.org> #1515: Pagefault in arch_thread_init_kthread_stack -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- {{{ vm_soft_fault: va 0x251837b5 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x251837b5, ip 0x800965a6, write 1, user 0, thread 0x84 CPU 1 halted! PANIC: vm_page_fault: unhandled page fault in kernel space at 0x251837b5, ip 0x800965a6 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> sc stack trace for thread 0x84 "w>Deskbar" kernel stack: 0x94664000 to 0x94668000 user stack: 0x700c3000 to 0x70103000 frame caller :function + offset 94667aa8 (+ 52) 80083321 :invoke_command + 0x0075 94667adc (+ 48) 80083572 :kernel_debugger + 0x020e 94667b0c (+ 176) 80083609 :panic + 0x002d 94667bbc (+ 64) 8005c487 :vm_page_fault + 0x00a9 94667bfc (+ 144) 8008b878 :i386_handle_trap + 0x0261 iframe at 0x94667c94 (end = 0x94667ce8) eax 0x3000 ebx 0x0 ecx 0x251837b5 edx 0x0 esi 0x90aae800 edi 0x90a2f000 ebp 0x94667ce4 esp 0x94667cc4 eip 0x800965a6 eflags 0x10206 vector: 0xe, error code: 0x2 94667c8c (+ 88) 800965a6 :memset + 0x0016 94667ce4 (+ 32) 8008c7e0 :arch_thread_init_kthread_stack + 0x0024 94667d04 (+ 96) 8003f09a :_Z13create_threadPKclPFlPFlPvES1_ES1_S1_lbl + 0x02ce 94667d64 (+ 80) 80040108 :_user_spawn_thread + 0x004c 94667db4 (+ 368) 800383ab :syscall_dispatcher + 0x0571 94667f24 (+ 128) 8008b92c :i386_handle_trap + 0x0315 iframe at 0x94667fac (end = 0x94668000) eax 0x1d ebx 0x704100 ecx 0x4d2558 edx 0x18053100 esi 0x18052f58 edi 0x18053100 ebp 0x70102bfc esp 0x94667fdc eip 0xffff0102 eflags 0x216 vector: 0x63, error code: 0x0 94667fa4 (+ 0) ffff0102 70102bfc (+ 80) 0034cc88 :unknown + 0x106c88 70102c4c (+ 64) 0034ce02 :unknown + 0x106e02 70102c8c (+ 640) 003a0993 :unknown + 0x15a993 70102f0c (+ 48) 0021fa2a :unknown + 0x1fa2a 70102f3c (+ 96) 0039d904 :unknown + 0x157904 70102f9c (+ 32) 002fb9ee :unknown + 0xb59ee 70102fbc (+ 32) 0068a90e :unknown + 0x2190e 70102fdc (+ 0) 70102fec 1052:w>Deskbar_84_stack at 0x700c3000 + 0x3ffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 15:32:38 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 13:32:38 -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.0a8023ed0a212aff4b3df100d28bf5a2@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): I think I got it reproduced now. This time the Deskbar's menu tracking thread was the holder of sem 4. See attached logfile. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 20:48:50 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 18:48:50 -0000 Subject: [Haiku-bugs] [Haiku] #1516: Various file operations fail when the filename is the empty string. Message-ID: <038.53b6e67d746aa701a16fd438b12abd23@haiku-os.org> #1516: Various file operations fail when the filename is the empty string. -----------------------+---------------------------------------------------- Reporter: mjw | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Various file operations fail when the filename is the empty string. For example, stat( "", &statbuf ) should return -1 with errno set to ENOENT, however on Haiku it returns 0. I assume statbuf will be filled with random stuff. Other things I have tried, access( "", F_OK ) returns 0, whereas I would expect it to return -1 with errno set to ENOENT. Things such as stat( NULL, &statbuf ) work correctly. fopen( "", "r" ) returns a valid open FILE *, but the file can not be read from. I assume there are other operations (like open()) that exhibit the same symptoms. I traced the code down to vnode_path_to_vnode in haiku/src/system/kernel/fs/vfs.cpp, but decided that a fix should come from somebody who knows what they are doing. I have a noddy test case to attach to the bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 21:33:09 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 19:33:09 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.22c68195d42ce4768cb51c9909b2255d@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by tonestone57): * component: Add-Ons/Tracker => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:02:09 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:02:09 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.b910fd2db5511b752c8f83d58efccdb9@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): I assume this is the same thing experienced in #1512. This was mentioned in comments from forum post: http://haiku- os.org/community/forum/tired_of_running_haiku_under_vms#comment-7970 (comments starting at 7970 and below) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:02:31 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:02:31 -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.0ea3a49fd304e52d915edd8663643907@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by umccullough): I'm guessing #1509 is a duplicate of this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:04:43 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:04:43 -0000 Subject: [Haiku-bugs] [Haiku] #1517: registrar crash during boot Message-ID: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> #1517: registrar crash during boot -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Application crashes during boot with gcc 2.95, on core 2 duo 2.4 GHz Occured with r22394 INIT: Bootscript started reading page from store 0x9098a940 (cache 0x90992b00) returned: Device/File/Resource busy! vm_page_fault: vm_soft_fault returned error 'Device/File/Resource busy' on fault at 0x410f24, ip 0x410f24, write 0, user 1, thread 0x39 vm_page_fault: sending team "/boot/beos/system/servers/regis" 0x2f SIGSEGV, ip 0x410f24 ("libbe.so_seg0ro" +0x1c8f24) stack trace: 0x003f8213 (libbe.so_seg0ro + 0x1b0213) 0x003f796e (libbe.so_seg0ro + 0x1af96e) 0x003cbae1 (libbe.so_seg0ro + 0x183ae1) 0x003e7b3f (libbe.so_seg0ro + 0x19fb3f) 0x003eea78 (libbe.so_seg0ro + 0x1a6a78) 0x003ee6cf (libbe.so_seg0ro + 0x1a66cf) 0x00312138 (libbe.so_seg0ro + 0xca138) 0x0050fa40 (libroot.so_seg0ro + 0x20a40) 0x70143fec (create_app_meta_mime (s)_39_sta + 0x3ffec) 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 0x80098b64, write 0, user 0, thread 0x39 user_debug_exception_occurred(): Failed to install debugger: thread: 57: Bad port ID 54: DEBUGGER: You need to have a valid app_server connection first! debug_server: Thread 54 entered the debugger: Debugger call: `You need to have a valid app_server connection first!' stack trace, current PC 0xffff0102 : (0x7ffe6cac) 0x2cd73b __Q28BPrivate13AppServerLink + 0x73 (0x7ffe6cdc) 0x2c90a5 _._12BApplication + 0x69 (0x7ffe6d1c) 0x20d53d _._9NetServer + 0xa9 (0x7ffe6d4c) 0x20c484 main + 0x6c (0x7ffe6f7c) 0x209267 _start + 0x5b (0x7ffe6fac) 0x1007ae (runtime_loader_seg0ro + 0x7ae) debug_server: Killing team 54 (/boot/beos/system/servers/net_server) debug_server: TeamDebugHandler::Init(): Failed to get info for team 54: Operation on invalid team debug_server: KillTeam(): Error getting info for team 54: Operation on invalid team debug_server: Killing team 54 () intel_extreme: init_hardware() intel_extreme: init_hardware() failed: No such file or directory matrox: init_hardware() failed: General system error neomagic: init_hardware() failed: General system error Radeon - init_hardware: Version: 5.1.6.0 Radeon - Radeon_CardDetect: no supported devices found radeon: init_hardware() failed: General system error savage: init_hardware - no supported devices s3savage: init_hardware() failed: General system error vesa: init_hardware() vesa: init_driver() vesa: publish_devices() vesa: find_device() loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa via: init_hardware() failed: General system error vesa: vesa_init() completed successfully! vesa: acc: vesa.accelerant -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:12:40 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:12:40 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.4542d0856be641ffae663d1f1238f8d1@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by scottmc): Probably not the same as #1512, as this isn't a freeze up, it's the deskbar and/or tracker and/or other crashing with a dialog box... We are able to press the continue button and then press ctrl-alt-alt. Then click on restart desktop and then everything is fine. Well except for the other instabilities that have also been reported with the latest builds. But these recent bugs might all be inter-related though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:14:47 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:14:47 -0000 Subject: [Haiku-bugs] [Haiku] #1517: registrar crash during boot In-Reply-To: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> References: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> Message-ID: <059.a0eadb5acc1b47839e301fea37dcfdc4@haiku-os.org> #1517: registrar crash during boot ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Old description: > Application crashes during boot with gcc 2.95, on core 2 duo 2.4 GHz > Occured with r22394 > > INIT: Bootscript started > reading page from store 0x9098a940 (cache 0x90992b00) returned: > Device/File/Resource busy! > vm_page_fault: vm_soft_fault returned error 'Device/File/Resource busy' > on fault at 0x410f24, ip 0x410f24, write 0, user 1, thread 0x39 > vm_page_fault: sending team "/boot/beos/system/servers/regis" 0x2f > SIGSEGV, ip 0x410f24 ("libbe.so_seg0ro" +0x1c8f24) > stack trace: > 0x003f8213 (libbe.so_seg0ro + 0x1b0213) > 0x003f796e (libbe.so_seg0ro + 0x1af96e) > 0x003cbae1 (libbe.so_seg0ro + 0x183ae1) > 0x003e7b3f (libbe.so_seg0ro + 0x19fb3f) > 0x003eea78 (libbe.so_seg0ro + 0x1a6a78) > 0x003ee6cf (libbe.so_seg0ro + 0x1a66cf) > 0x00312138 (libbe.so_seg0ro + 0xca138) > 0x0050fa40 (libroot.so_seg0ro + 0x20a40) > 0x70143fec (create_app_meta_mime (s)_39_sta + 0x3ffec) > 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 0x80098b64, write 0, user 0, thread 0x39 > user_debug_exception_occurred(): Failed to install debugger: thread: 57: > Bad port ID > 54: DEBUGGER: You need to have a valid app_server connection first! > debug_server: Thread 54 entered the debugger: Debugger call: `You need to > have a valid app_server connection first!' > stack trace, current PC 0xffff0102 : > (0x7ffe6cac) 0x2cd73b __Q28BPrivate13AppServerLink + 0x73 > (0x7ffe6cdc) 0x2c90a5 _._12BApplication + 0x69 > (0x7ffe6d1c) 0x20d53d _._9NetServer + 0xa9 > (0x7ffe6d4c) 0x20c484 main + 0x6c > (0x7ffe6f7c) 0x209267 _start + 0x5b > (0x7ffe6fac) 0x1007ae (runtime_loader_seg0ro + 0x7ae) > debug_server: Killing team 54 (/boot/beos/system/servers/net_server) > debug_server: TeamDebugHandler::Init(): Failed to get info for team 54: > Operation on invalid team > debug_server: KillTeam(): Error getting info for team 54: Operation on > invalid team > debug_server: Killing team 54 () > intel_extreme: init_hardware() > intel_extreme: init_hardware() failed: No such file or directory > matrox: init_hardware() failed: General system error > neomagic: init_hardware() failed: General system error > Radeon - init_hardware: Version: 5.1.6.0 > Radeon - Radeon_CardDetect: no supported devices found > radeon: init_hardware() failed: General system error > savage: init_hardware - no supported devices > s3savage: init_hardware() failed: General system error > vesa: init_hardware() > vesa: init_driver() > vesa: publish_devices() > vesa: find_device() > loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa > via: init_hardware() failed: General system error > vesa: vesa_init() completed successfully! > vesa: acc: vesa.accelerant New description: Application crashes during boot with gcc 2.95, on core 2 duo 2.4 GHz Occured with r22394 {{{ INIT: Bootscript started reading page from store 0x9098a940 (cache 0x90992b00) returned: Device/File/Resource busy! vm_page_fault: vm_soft_fault returned error 'Device/File/Resource busy' on fault at 0x410f24, ip 0x410f24, write 0, user 1, thread 0x39 vm_page_fault: sending team "/boot/beos/system/servers/regis" 0x2f SIGSEGV, ip 0x410f24 ("libbe.so_seg0ro" +0x1c8f24) stack trace: 0x003f8213 (libbe.so_seg0ro + 0x1b0213) 0x003f796e (libbe.so_seg0ro + 0x1af96e) 0x003cbae1 (libbe.so_seg0ro + 0x183ae1) 0x003e7b3f (libbe.so_seg0ro + 0x19fb3f) 0x003eea78 (libbe.so_seg0ro + 0x1a6a78) 0x003ee6cf (libbe.so_seg0ro + 0x1a66cf) 0x00312138 (libbe.so_seg0ro + 0xca138) 0x0050fa40 (libroot.so_seg0ro + 0x20a40) 0x70143fec (create_app_meta_mime (s)_39_sta + 0x3ffec) 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 0x80098b64, write 0, user 0, thread 0x39 user_debug_exception_occurred(): Failed to install debugger: thread: 57: Bad port ID 54: DEBUGGER: You need to have a valid app_server connection first! debug_server: Thread 54 entered the debugger: Debugger call: `You need to have a valid app_server connection first!' stack trace, current PC 0xffff0102 : (0x7ffe6cac) 0x2cd73b __Q28BPrivate13AppServerLink + 0x73 (0x7ffe6cdc) 0x2c90a5 _._12BApplication + 0x69 (0x7ffe6d1c) 0x20d53d _._9NetServer + 0xa9 (0x7ffe6d4c) 0x20c484 main + 0x6c (0x7ffe6f7c) 0x209267 _start + 0x5b (0x7ffe6fac) 0x1007ae (runtime_loader_seg0ro + 0x7ae) debug_server: Killing team 54 (/boot/beos/system/servers/net_server) debug_server: TeamDebugHandler::Init(): Failed to get info for team 54: Operation on invalid team debug_server: KillTeam(): Error getting info for team 54: Operation on invalid team debug_server: Killing team 54 () intel_extreme: init_hardware() intel_extreme: init_hardware() failed: No such file or directory matrox: init_hardware() failed: General system error neomagic: init_hardware() failed: General system error Radeon - init_hardware: Version: 5.1.6.0 Radeon - Radeon_CardDetect: no supported devices found radeon: init_hardware() failed: General system error savage: init_hardware - no supported devices s3savage: init_hardware() failed: General system error vesa: init_hardware() vesa: init_driver() vesa: publish_devices() vesa: find_device() loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa via: init_hardware() failed: General system error vesa: vesa_init() completed successfully! vesa: acc: vesa.accelerant }}} Comment (by marcusoverhagen): another boot, this time Tracker crashed {{{ vesa: vesa_init() completed successfully! vesa: acc: vesa.accelerant reading page from store 0x90a206e0 (cache 0x90a22380) returned: Device/File/Resource busy! vm_page_fault: vm_soft_fault returned error 'Device/File/Resource busy' on fault at 0x609004, ip 0x10351c, write 0, user 1, thread 0x53 vm_page_fault: sending team "/boot/beos/system/Tracker" 0x53 SIGSEGV, ip 0x10351c ("runtime_loader_seg0ro" +0x351c) stack trace: 0x00103599 (runtime_loader_seg0ro + 0x3599) 0x00101b21 (runtime_loader_seg0ro + 0x1b21) 0x00102377 (runtime_loader_seg0ro + 0x2377) 0x0010253c (runtime_loader_seg0ro + 0x253c) 0x00100782 (runtime_loader_seg0ro + 0x782) 0x7ffe6fec (/boot/beos/system/Tracker_main_ + 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 0x80098b64, write 0, user 0, thread 0x53 debug_server: Thread 83 entered the debugger: Segment violation stack trace, current PC 0x10351c (runtime_loader_seg0ro + 0x351c): (0x7ffe6edc) 0x103599 (runtime_loader_seg0ro + 0x3599) (0x7ffe6f0c) 0x101b21 (runtime_loader_seg0ro + 0x1b21) (0x7ffe6f3c) 0x102377 (runtime_loader_seg0ro + 0x2377) (0x7ffe6f6c) 0x10253c (runtime_loader_seg0ro + 0x253c) (0x7ffe6fac) 0x100782 (runtime_loader_seg0ro + 0x782) emuxki: init_hardware() }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:30:37 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:30:37 -0000 Subject: [Haiku-bugs] [Haiku] #1517: registrar crash during boot In-Reply-To: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> References: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> Message-ID: <059.a4418b224ba9c40433d8059b484814f2@haiku-os.org> #1517: registrar crash during boot ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): And another crash, again Tracker during boot, full debug output attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:35:07 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:35:07 -0000 Subject: [Haiku-bugs] [Haiku] #1517: registrar crash during boot In-Reply-To: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> References: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> Message-ID: <059.60179510d560fcaebb60b39814c10f61@haiku-os.org> #1517: registrar crash during boot ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by axeld): Ah, that's a simpler one: if the inode cannot be locked (because it's written to), the vnode store's operation may now fail (since my latest changes...). I should probably sit back and think this through again :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:36:37 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:36:37 -0000 Subject: [Haiku-bugs] [Haiku] #1518: nVidia driver does not work with N7600GS card Message-ID: <041.6fd9222743858eb0021210d15066a0ca@haiku-os.org> #1518: nVidia driver does not work with N7600GS card -------------------------------------+-------------------------------------- Reporter: hitech | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- I'm using the AGP graphics card ASUS N7600GS Silent based on nVidia chipset. The Haiku driver is not working in Zeta 1.21. I receive screen resolution of 800x600, 8 bits color and 60 Hz refresh rate, and I can't change it. Interesting, but this card is listed among supported ones: In "Devices" system tool, under "VGA", I have "Vendor: Nvidia Corporation (0x10de)" and "Card ID: 0x2e1". It also states that I have no resource conflicts. In file http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/add- ons/kernel/drivers/graphics/nvidia/driver.c, this card ID is listed among supported: . . . . . . . . . static uint16 nvidia_device_list[] = { . . . . . 0x02e1, /* Nvidia GeForce 7600 GS */ . . . . . . } Apparently, either the driver does not recognize my graphics card correctly, or?.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 1 23:46:36 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 21:46:36 -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.fcd8f5f3914d347453c754837d97ad8f@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by bonefish): According to deadlock_menutracking.txt the thread is creating the kernel stack area for an new thread. In insert_area() it apparently accesses invalid memory. If vm.cpp was compiled with gcc 4 and no debugging the instruction would try to access vm_area::base with %edx (0xe8458d00) being the area pointer. deadlock3.txt is interesting too: The thread that holds the kernel address space lock still lives -- it is still queued in the semaphore -- but it's no longer in the thread hash table. So it is apparently in the last phase of its death. Probably it is currently deleting its kernel stack area and accesses invalid memory. This would at least allow for the same explanation as in the other case. So, supposedly the area/address space structures become invalid at some point. Given that it doesn't seem to be reproducible on a single CPU, a SMP-only race condition seems likely. Browsing through some code, I found at least one of those, though it seems a little unlikely to be that well reproducible: In thread_exit2() we call put_death_stack(), but don't hold (and cannot hold) the thread spinlock. Between releasing the spinlock in put_death_stack() and reacquiring it in thread_exit2() another thread could grab our still used death stack. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 00:48:46 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 22:48:46 -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.7ca0e2a9a81f5714e005c45cb1fd1d08@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by bonefish): I've fixed the death stack issue in r22403. I don't think it's likely that this was the cause of the problem, but it wouldn't harm to check. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 01:01:23 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 23:01:23 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB Message-ID: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- The firewire driver creates 193 single areas called "fw ir Area" with 4kByte each. Those should be combined or optimized. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 01:36:55 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 23:36:55 -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.5ebe72be7ad43583faa85ebaace3bdb4@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): This problem is not reproduceable with GCC 2.95.3 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 01:37:42 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 01 Oct 2007 23:37:42 -0000 Subject: [Haiku-bugs] [Haiku] #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 In-Reply-To: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> References: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> Message-ID: <059.777754cb49bf80240a0a6815a1a85adb@haiku-os.org> #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): This problem is not reproduceable with GCC 2.95.3, only with GCC4 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 07:02:53 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 05:02:53 -0000 Subject: [Haiku-bugs] [Haiku] #1520: Cursor ghosting when trying to rename in tracker Message-ID: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> #1520: Cursor ghosting when trying to rename in tracker ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- I've attached a screenshot to show how this looks when it happens. Not sure if this is video driver related or something else. This happens on a laptop with a Radeon Mobility 9600. When renaming a file or folder in tracker the cursor leaves behind an image of itself adter each character is typed in. Moving the window cleans this up. Just a minor visual annoyance. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 08:45:31 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 06:45:31 -0000 Subject: [Haiku-bugs] [Haiku] #1520: Cursor ghosting when trying to rename in tracker In-Reply-To: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> References: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> Message-ID: <051.320f7473bc30cbcc731106037553726b@haiku-os.org> #1520: Cursor ghosting when trying to rename in tracker -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by meanwhile): Same thing here on a laptop with a Radeon Mobility 9600, whereas a desktop I have running Haiku doesn't show this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 08:56:11 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 06:56:11 -0000 Subject: [Haiku-bugs] [Haiku] #1520: Cursor ghosting when trying to rename in tracker In-Reply-To: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> References: <042.b87be069ea06c15b6ff80881aac67e2e@haiku-os.org> Message-ID: <051.25cc1d578fcffd63b6fe03b392d787d1@haiku-os.org> #1520: Cursor ghosting when trying to rename in tracker -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Happens under vmware too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:36:03 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:36:03 -0000 Subject: [Haiku-bugs] [Haiku] #807: Add ftp(d), telnet(d), ... In-Reply-To: <040.f9033b0adc5458d058a4313993d40591@haiku-os.org> References: <040.f9033b0adc5458d058a4313993d40591@haiku-os.org> Message-ID: <049.4464e5d8c61beec052c860ee3aff1759@haiku-os.org> #807: Add ftp(d), telnet(d), ... -----------------------------------+---------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:36:33 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:36:33 -0000 Subject: [Haiku-bugs] [Haiku] #805: Fast read/write locker In-Reply-To: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> References: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> Message-ID: <049.fa79e198e07d9640ff5cb9b1cdfb11de@haiku-os.org> #805: Fast read/write locker ----------------------------+----------------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * platform: => All * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:37:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #800: ICMP In-Reply-To: <040.8d5ca9a0e9258419f459abf36d63ccd1@haiku-os.org> References: <040.8d5ca9a0e9258419f459abf36d63ccd1@haiku-os.org> Message-ID: <049.fe805a68598d02a2655a4b81b46b98c7@haiku-os.org> #800: ICMP -----------------------------------------+---------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: - Network & Internet/Stack | Version: Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:37:39 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:37:39 -0000 Subject: [Haiku-bugs] [Haiku] #798: TCP In-Reply-To: <040.f98897edf5e803e659e0644435e93510@haiku-os.org> References: <040.f98897edf5e803e659e0644435e93510@haiku-os.org> Message-ID: <049.3a80e47345fc0646ebd1ff7e1f853f29@haiku-os.org> #798: TCP ---------------------------------------+------------------------------------ Reporter: axeld | Owner: hugosantos Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: - Network & Internet/TCP | Version: Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: agalante => hugosantos * platform: => All * component: - Network & Internet/Stack => - Network & Internet/TCP * milestone: R1 Network Stack => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:38:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:38:16 -0000 Subject: [Haiku-bugs] [Haiku] #798: TCP In-Reply-To: <040.f98897edf5e803e659e0644435e93510@haiku-os.org> References: <040.f98897edf5e803e659e0644435e93510@haiku-os.org> Message-ID: <049.9eb1be33cd45f7c60024ba233479370b@haiku-os.org> #798: TCP ---------------------------------------+------------------------------------ Reporter: axeld | Owner: hugosantos Type: enhancement | Status: closed Priority: normal | Milestone: R1/alpha Component: - Network & Internet/TCP | Version: Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: It's basically done - everything that's still missing should be opened as a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:39:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:39:10 -0000 Subject: [Haiku-bugs] [Haiku] #797: UDP In-Reply-To: <040.d86ecaa4cd423cfd3ff6d8b8cc58e801@haiku-os.org> References: <040.d86ecaa4cd423cfd3ff6d8b8cc58e801@haiku-os.org> Message-ID: <049.e6858b07427dbcd59de88fa6162d892d@haiku-os.org> #797: UDP -----------------------------------------+---------------------------------- Reporter: axeld | Owner: zooey Type: enhancement | Status: closed Priority: normal | Milestone: R1 Network Stack Component: - Network & Internet/Stack | Version: Resolution: fixed | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * status: assigned => closed * platform: => All * resolution: => fixed Comment: Besides ICMP error handling (see #800), it's basically done. All other issues should be opened as a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:39:38 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:39:38 -0000 Subject: [Haiku-bugs] [Haiku] #806: Revise locking In-Reply-To: <040.c5d48dcd29a6f8500905b53bd63e59b3@haiku-os.org> References: <040.c5d48dcd29a6f8500905b53bd63e59b3@haiku-os.org> Message-ID: <049.0a4a5f89319daef231f9b94bd07500ed@haiku-os.org> #806: Revise locking -----------------------------------+---------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: high | Milestone: R1 Component: - Network & Internet | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:39:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:39:16 -0000 Subject: [Haiku-bugs] [Haiku] #1521: Haiku Radeon driver dont contains the 9550 ID Message-ID: <041.3d4e9ab694d49899af296f5eda7cd48f@haiku-os.org> #1521: Haiku Radeon driver dont contains the 9550 ID -------------------------------------+-------------------------------------- Reporter: miqlas | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Hello! I try to use the Haiku Radeon driver on my system, but is not working. Please, check the driver. I think the driver dont contains the 9550 Device ID: 0x4153 Thank You! [miqlas] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:40:43 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:40:43 -0000 Subject: [Haiku-bugs] [Haiku] #869: [IPCP] get ConnectOnDemand working In-Reply-To: <045.650384fa7e39174dd7d5ad0a9d887e49@haiku-os.org> References: <045.650384fa7e39174dd7d5ad0a9d887e49@haiku-os.org> Message-ID: <054.14b1aa33f7e51c62d49ec7f7e4f84236@haiku-os.org> #869: [IPCP] get ConnectOnDemand working ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: wkornewald Type: bug | Status: new Priority: high | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:40:57 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:40:57 -0000 Subject: [Haiku-bugs] [Haiku] #808: Get userland stack to run again In-Reply-To: <040.75b609fd5ba9da8b1559e8dc6775b813@haiku-os.org> References: <040.75b609fd5ba9da8b1559e8dc6775b813@haiku-os.org> Message-ID: <049.c2605e334cd319a82f0770def11105d3@haiku-os.org> #808: Get userland stack to run again -----------------------------------------+---------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: - Network & Internet/Stack | Version: Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * platform: => All * milestone: R1 Network Stack => Unscheduled -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:41:38 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:41:38 -0000 Subject: [Haiku-bugs] [Haiku] #810: Complete net_buffer implementation In-Reply-To: <040.b67c409a5c961cdf38855994ee972751@haiku-os.org> References: <040.b67c409a5c961cdf38855994ee972751@haiku-os.org> Message-ID: <049.259ba68e1ecebcf753b66e82b37c6985@haiku-os.org> #810: Complete net_buffer implementation -----------------------------------------+---------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/Stack | Version: Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:42:06 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:42:06 -0000 Subject: [Haiku-bugs] [Haiku] #812: Port PPP to the new stack In-Reply-To: <040.7001a6f42d4b1262a3b436b5fc78d042@haiku-os.org> References: <040.7001a6f42d4b1262a3b436b5fc78d042@haiku-os.org> Message-ID: <049.208cffcdf9e33ca2168d0d4a14bf102b@haiku-os.org> #812: Port PPP to the new stack ---------------------------------------+------------------------------------ Reporter: axeld | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * platform: => All * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:42:47 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:42:47 -0000 Subject: [Haiku-bugs] [Haiku] #820: Network preferences In-Reply-To: <040.51b3d1ed078a0ace0f53e4d8d6d5fcef@haiku-os.org> References: <040.51b3d1ed078a0ace0f53e4d8d6d5fcef@haiku-os.org> Message-ID: <049.f10c92d4d231e3e9a108a5e570bc5b46@haiku-os.org> #820: Network preferences -----------------------------------+---------------------------------------- Reporter: axeld | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: - Network & Internet | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * cc: wkornewald (removed) * owner: => stippi * platform: => All * milestone: R1 Network Stack => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:43:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:43:59 -0000 Subject: [Haiku-bugs] [Haiku] #871: when PPP module gets unloaded, reloaded, and unloaded the system crashes In-Reply-To: <045.9afbfc1127f00999fc802625d0774233@haiku-os.org> References: <045.9afbfc1127f00999fc802625d0774233@haiku-os.org> Message-ID: <054.a56c031af933335f0427210ac87992a6@haiku-os.org> #871: when PPP module gets unloaded, reloaded, and unloaded the system crashes ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: wkornewald Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:44:39 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:44:39 -0000 Subject: [Haiku-bugs] [Haiku] #873: automatically create an interface instance for every configuration file In-Reply-To: <045.5a7f9db062a16fd701bbc643b8208f97@haiku-os.org> References: <045.5a7f9db062a16fd701bbc643b8208f97@haiku-os.org> Message-ID: <054.76ea71813253c2e9e622d54298294996@haiku-os.org> #873: automatically create an interface instance for every configuration file ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:44:52 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:44:52 -0000 Subject: [Haiku-bugs] [Haiku] #922: add CHAP authentication support In-Reply-To: <045.54b9091d3914f3c06fc8ac4cd0093df6@haiku-os.org> References: <045.54b9091d3914f3c06fc8ac4cd0093df6@haiku-os.org> Message-ID: <054.f698e9fecbaf4ec0ec0affea92d4e917@haiku-os.org> #922: add CHAP authentication support ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:45:33 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:45:33 -0000 Subject: [Haiku-bugs] [Haiku] #923: add dial-up (phone line) modem support In-Reply-To: <045.785dd022e65906d2c01718e66a94fe40@haiku-os.org> References: <045.785dd022e65906d2c01718e66a94fe40@haiku-os.org> Message-ID: <054.f81b12589fe2a5e6915a6b48563b979a@haiku-os.org> #923: add dial-up (phone line) modem support ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:46:06 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:46:06 -0000 Subject: [Haiku-bugs] [Haiku] #1057: add PPP connection replicant and connection dialog In-Reply-To: <045.a780d079d080721592cb95ae0fd5098e@haiku-os.org> References: <045.a780d079d080721592cb95ae0fd5098e@haiku-os.org> Message-ID: <054.26bcc91fabcf58af93695f47c61dec0e@haiku-os.org> #1057: add PPP connection replicant and connection dialog ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 Comment: This should be integrated with the NetworkStatus application. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:46:20 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:46:20 -0000 Subject: [Haiku-bugs] [Haiku] #1058: simplify PPP preflet and integrate it into our network preflet In-Reply-To: <045.a80d7c78f336cec31dfc57040cf1f0f1@haiku-os.org> References: <045.a80d7c78f336cec31dfc57040cf1f0f1@haiku-os.org> Message-ID: <054.bdfe656d9c8a1f27291fed835b961d5d@haiku-os.org> #1058: simplify PPP preflet and integrate it into our network preflet ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:46:45 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:46:45 -0000 Subject: [Haiku-bugs] [Haiku] #1059: [IPCP] update DNS server list In-Reply-To: <045.d93e2afd355acfd6cecaa1d3b2d258b8@haiku-os.org> References: <045.d93e2afd355acfd6cecaa1d3b2d258b8@haiku-os.org> Message-ID: <054.097f9de50861154def5e27c7f6773d01@haiku-os.org> #1059: [IPCP] update DNS server list ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Network & Internet/PPP | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * owner: wkornewald => * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:47:04 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:47:04 -0000 Subject: [Haiku-bugs] [Haiku] #804: "ifconfig" should support :x notion In-Reply-To: <040.93b1801264f6c039cf7e3217f0c00997@haiku-os.org> References: <040.93b1801264f6c039cf7e3217f0c00997@haiku-os.org> Message-ID: <049.0fa0705d1380ec7fcb423a0a9aab69bf@haiku-os.org> #804: "ifconfig" should support :x notion -----------------------------------+---------------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - Network & Internet | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:47:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:47:19 -0000 Subject: [Haiku-bugs] [Haiku] #813: Manage routes via a radix tree In-Reply-To: <040.d5948eb1b0fa9b56d8c4cc97d6ed3ea6@haiku-os.org> References: <040.d5948eb1b0fa9b56d8c4cc97d6ed3ea6@haiku-os.org> Message-ID: <049.bfe68140522a2e50ea54383641ccc617@haiku-os.org> #813: Manage routes via a radix tree -----------------------------------------+---------------------------------- Reporter: axeld | Owner: Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - Network & Internet/Stack | Version: Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * milestone: R1 Network Stack => R1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:19 -0000 Subject: [Haiku-bugs] [Haiku] #152: PANIC: heap overgrew itself In-Reply-To: <054.b2a065af31403c988fc7482631f5f594@haiku-os.org> References: <054.b2a065af31403c988fc7482631f5f594@haiku-os.org> Message-ID: <063.8cd98cd41e3f8d51a105f8e5dec3c260@haiku-os.org> #152: PANIC: heap overgrew itself ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:27 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:27 -0000 Subject: [Haiku-bugs] [Haiku] #195: [app_server] crash in WindowLayer::Frontmost() In-Reply-To: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> References: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> Message-ID: <049.afcadc47f5af276e51d73850a8d34cae@haiku-os.org> #195: [app_server] crash in WindowLayer::Frontmost() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:40 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:40 -0000 Subject: [Haiku-bugs] [Haiku] #533: [KDL] while trying to unzip large .zip file In-Reply-To: <040.bee54cea413bd446baf3d7d2438111d9@haiku-os.org> References: <040.bee54cea413bd446baf3d7d2438111d9@haiku-os.org> Message-ID: <049.5de353c63cab5e844c5aa23f3b13dbea@haiku-os.org> #533: [KDL] while trying to unzip large .zip file ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:48 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:48 -0000 Subject: [Haiku-bugs] [Haiku] #717: kernel: Panic out of range In-Reply-To: <053.77529c3ae36c88bf29329a76e8ecfba6@haiku-os.org> References: <053.77529c3ae36c88bf29329a76e8ecfba6@haiku-os.org> Message-ID: <062.76395c30c11b1a591104e8f38de5d88a@haiku-os.org> #717: kernel: Panic out of range ---------------------------------+------------------------------------------ Reporter: kutspam at wolke7.net | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:33 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:33 -0000 Subject: [Haiku-bugs] [Haiku] #517: Copying a large file drops to KDL In-Reply-To: <040.932583ba647d8ad8ecbac107517d7f8e@haiku-os.org> References: <040.932583ba647d8ad8ecbac107517d7f8e@haiku-os.org> Message-ID: <049.faefbfeebf9b71963898630ddded6164@haiku-os.org> #517: Copying a large file drops to KDL ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:51:11 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:51:11 -0000 Subject: [Haiku-bugs] [Haiku] #837: [app_server] crash in Desktop::Cursor() In-Reply-To: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> References: <040.b80f98b20f9cfa1b997b8dd28ecbd29e@haiku-os.org> Message-ID: <049.f2027bcc38983031287d8751dd09003d@haiku-os.org> #837: [app_server] crash in Desktop::Cursor() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:50:55 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:50:55 -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.5c4eb9cb99c3004c9a45c670e0df1733@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:51:47 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:51:47 -0000 Subject: [Haiku-bugs] [Haiku] #355: [Tracker] slow content loading In-Reply-To: <040.2074b918bab1c74774802bf1cba01aea@haiku-os.org> References: <040.2074b918bab1c74774802bf1cba01aea@haiku-os.org> Message-ID: <049.c9a0dd46b49c2a6436e8c0b18bc94dcc@haiku-os.org> #355: [Tracker] slow content loading -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha Component: - Applications | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:51:53 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:51:53 -0000 Subject: [Haiku-bugs] [Haiku] #1322: vm_soft_fault: va 0xdeadbeef not covered by area in address space In-Reply-To: <048.70588a658c5a09ec1e2ea800dfb954d1@haiku-os.org> References: <048.70588a658c5a09ec1e2ea800dfb954d1@haiku-os.org> Message-ID: <057.86bdc0de203e72b10501eea57bd730a8@haiku-os.org> #1322: vm_soft_fault: va 0xdeadbeef not covered by area in address space ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:52:00 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:52:00 -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.938854c24e1553686f57ac1a30c2db8b@haiku-os.org> #1512: deadlock after clicking on Deskbar ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 12:59:24 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 10:59:24 -0000 Subject: [Haiku-bugs] [Haiku] #195: [app_server] crash in WindowLayer::Frontmost() In-Reply-To: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> References: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> Message-ID: <049.a38126914ea09b43fa01cc5f655f9375@haiku-os.org> #195: [app_server] crash in WindowLayer::Frontmost() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): I have been working on this bug by changing the locking a bit in app_server. The weird thing is that this crashing bug does not happen in the test_environment. Try running all sorts of apps, including stress_test which opens windows like crazy and then switching workspaces works fine. At least after I fixed a couple of deadlocks which were more easily provoked with my locking changes. When I try this on Haiku though, most apps will hang and not open any window anymore, so I must have messed something up. I will try again with the recent fixes to the kernel and post my results here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 13:59:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 11:59:16 -0000 Subject: [Haiku-bugs] [Haiku] #634: [app_server] crash in Painter::FillRectNoClipping() In-Reply-To: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> References: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> Message-ID: <049.dc787f41d1c26090678dfa34d31ae285@haiku-os.org> #634: [app_server] crash in Painter::FillRectNoClipping() ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 14:18:48 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 12:18:48 -0000 Subject: [Haiku-bugs] [Haiku] #1388: [kernel] crash on ping -s 15000 In-Reply-To: <040.50041ee2d5435b8aa5717f6db6fd8459@haiku-os.org> References: <040.50041ee2d5435b8aa5717f6db6fd8459@haiku-os.org> Message-ID: <049.dae193ccbeeb87795ea26890e8f4e2ab@haiku-os.org> #1388: [kernel] crash on ping -s 15000 -----------------------------------------+---------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha Component: - Network & Internet/Stack | Version: R1 development Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by axeld): * priority: normal => critical * component: Servers/net_server => - Network & Internet/Stack * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 14:22:29 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 12:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB In-Reply-To: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> References: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> Message-ID: <059.4da27e264756eec0d334c9d253f0ea0c@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 14:24:52 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 12:24:52 -0000 Subject: [Haiku-bugs] [Haiku] #1253: panic invalid bin_index 24 In-Reply-To: <050.97fb4a9b6485f66702a4183f5078c094@haiku-os.org> References: <050.97fb4a9b6485f66702a4183f5078c094@haiku-os.org> Message-ID: <059.1a63db86f316aca4ab900bb3860a8ac9@haiku-os.org> #1253: panic invalid bin_index 24 ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 14:25:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 12:25:32 -0000 Subject: [Haiku-bugs] [Haiku] #534: [BPopUpMenu] checker glitches In-Reply-To: <040.5f1142f415a0d3c5ec23ea69bdff9e46@haiku-os.org> References: <040.5f1142f415a0d3c5ec23ea69bdff9e46@haiku-os.org> Message-ID: <049.d4d9b8419a7a21cdb061da964fe75a2a@haiku-os.org> #534: [BPopUpMenu] checker glitches ------------------------+--------------------------------------------------- Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * platform: => All * resolution: => fixed Comment: I've fixed that recently, although the BMenu could take care of setting the margins big enough on BMenuField menus. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 14:29:36 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 12:29:36 -0000 Subject: [Haiku-bugs] [Haiku] #1198: Email preferences UI broken In-Reply-To: <039.a4498156e7370cb0ef87d78e3640849f@haiku-os.org> References: <039.a4498156e7370cb0ef87d78e3640849f@haiku-os.org> Message-ID: <048.3d6ee1d538d65c8d61ffb831b75322be@haiku-os.org> #1198: Email preferences UI broken ---------------------------------+------------------------------------------ Reporter: koki | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: - Preferences/Mail | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:05:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:05:10 -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.22b2706b824a1d4ac8941adee7cbf030@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: | Platform: All ----------------------------------+----------------------------------------- Comment (by stippi): anxiety, I have reviewed and applied your patch here locally. I have found one problem in your code which you might be interested in: char* copyOfString = (char*)malloc(bString.Length()); sprintf(copyOfString, "%s", bString.String()); ... will overwrite one byte of memory. bString.Length() returns the length of the string _excluding_ the byte necessary for the null termination. I guess sprintf() will write the byte anyways. So correct would be to allocate Length() + 1 bytes. Even easier is using strdup() though. The rest of your patch was fine. Thanks for the contribution! What's your real name I want to add you to Contributors. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:23:36 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:23:36 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Greek (keyboard) bug for BeMail. In-Reply-To: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> References: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> Message-ID: <052.acf83e7d4f7bc598269f8404eb5c27b8@haiku-os.org> #1022: Greek (keyboard) bug for BeMail. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:25:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:25:16 -0000 Subject: [Haiku-bugs] [Haiku] #1288: StyledEdit does not print when there is only one line of text In-Reply-To: <044.0880b7c01fcf05a6a1607f433df9f5ae@haiku-os.org> References: <044.0880b7c01fcf05a6a1607f433df9f5ae@haiku-os.org> Message-ID: <053.2d385d96a3b7cb9decd815004d4aec7f@haiku-os.org> #1288: StyledEdit does not print when there is only one line of text ----------------------------------------+----------------------------------- Reporter: bnickname | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/StyledEdit | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Changes (by jackburton): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:26:44 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:26:44 -0000 Subject: [Haiku-bugs] [Haiku] #715: BTextView::HideTyping not implemented In-Reply-To: <040.137cc10e634eb0b194c10801532e9567@haiku-os.org> References: <040.137cc10e634eb0b194c10801532e9567@haiku-os.org> Message-ID: <049.9a8a5ce2944a155269459546a85ec641@haiku-os.org> #715: BTextView::HideTyping not implemented ---------------------------------+------------------------------------------ Reporter: korli | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:27:52 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:27:52 -0000 Subject: [Haiku-bugs] [Haiku] #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded In-Reply-To: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> References: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> Message-ID: <050.e526bdc9c81c7527c8515c687243c8ad@haiku-os.org> #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => assigned * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:30:17 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:30:17 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.9a7b775f5b62ca1cef9d4bd7695a3ad8@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: normal | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => assigned * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:34:04 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:34:04 -0000 Subject: [Haiku-bugs] [Haiku] #834: Disconnecting USB mouse/keyboard problem In-Reply-To: <050.11a34ba32bb1c4d0bc43cff169b7c01d@haiku-os.org> References: <050.11a34ba32bb1c4d0bc43cff169b7c01d@haiku-os.org> Message-ID: <059.fcb29194f9a8d3f40ccbb3963ae38ae5@haiku-os.org> #834: Disconnecting USB mouse/keyboard problem ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by mmlr): Transfer canceling has been implemented by now. Also much of the connect/disconnect handling has been revised. Can this bug still be reproduced? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 15:37:28 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 13:37:28 -0000 Subject: [Haiku-bugs] [Haiku] #271: drag & drop is broken, can crash or deadlock app_server In-Reply-To: <050.fc2777c8090bdf680d9d05920eebf216@haiku-os.org> References: <050.fc2777c8090bdf680d9d05920eebf216@haiku-os.org> Message-ID: <059.4d150f63b3d2ea4b03a0c17458616ab5@haiku-os.org> #271: drag & drop is broken, can crash or deadlock app_server ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: mmlr Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by mmlr): I haven't encountered drag&drop issues in a while now and all the affected bugs have been closed. Can we therefore agree on closing this ticket too and open up new ones with concrete steps to reproduce when they appear? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 16:10:15 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 14:10:15 -0000 Subject: [Haiku-bugs] [Haiku] #1491: input_server might be blocked on a modal panel during shutdown In-Reply-To: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> References: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> Message-ID: <051.dd5604c61a1cfb7e63072d3830938c39@haiku-os.org> #1491: input_server might be blocked on a modal panel during shutdown --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by scottmc): I haven't seen this happening in recent builds (as of 22389), might be fixed now? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 16:52:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 14:52:10 -0000 Subject: [Haiku-bugs] [Haiku] #271: drag & drop is broken, can crash or deadlock app_server In-Reply-To: <050.fc2777c8090bdf680d9d05920eebf216@haiku-os.org> References: <050.fc2777c8090bdf680d9d05920eebf216@haiku-os.org> Message-ID: <059.4de389a060cece00db4a3a61a850db47@haiku-os.org> #271: drag & drop is broken, can crash or deadlock app_server ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: mmlr Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Agreed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 16:53:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 14:53:32 -0000 Subject: [Haiku-bugs] [Haiku] #824: Booting from CD causes the floppy to constantly be polled In-Reply-To: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> References: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> Message-ID: <058.853b8432e22784b8d792cbb9dfcd2ce8@haiku-os.org> #824: Booting from CD causes the floppy to constantly be polled -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 17:16:24 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 15:16:24 -0000 Subject: [Haiku-bugs] [Haiku] #1500: [Clock] crash on exit In-Reply-To: <040.768331538ebcdc2845e8910f5e29e1d7@haiku-os.org> References: <040.768331538ebcdc2845e8910f5e29e1d7@haiku-os.org> Message-ID: <049.eadd4f8a48e4748188586c45a68b4425@haiku-os.org> #1500: [Clock] crash on exit -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: fixed in r22411. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 17:19:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 15:19:59 -0000 Subject: [Haiku-bugs] [Haiku] #1432: BStatusBar is not invalidating the correct regions when being resized In-Reply-To: <041.f0f33c648ff2e0f7f26a894ddb74997a@haiku-os.org> References: <041.f0f33c648ff2e0f7f26a894ddb74997a@haiku-os.org> Message-ID: <050.a92548d95905cdd44f836435eaa62d0a@haiku-os.org> #1432: BStatusBar is not invalidating the correct regions when being resized -------------------------------+-------------------------------------------- Reporter: stippi | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: fixed in r22370. BStatusBar is not calculating the preferred size correctly though, ignoring the texts below the bar I think. Different bug though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 17:23:08 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 15:23:08 -0000 Subject: [Haiku-bugs] [Haiku] #606: [FileTypes] file type window vs application type In-Reply-To: <040.fe6152e57c10babc6912c10d5d0bfb8e@haiku-os.org> References: <040.fe6152e57c10babc6912c10d5d0bfb8e@haiku-os.org> Message-ID: <049.9a7639347832e0db3e3951d8f48bdb5b@haiku-os.org> #606: [FileTypes] file type window vs application type ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Preferences | Version: Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Old description: > If you open BitmapDrawing in filetypes it will open file type window > instead of > application type. New description: If you open BitmapDrawing in filetypes it will open file type window instead of application type. Comment: Neither of those are real apps, but the build system now adds required attributes. Fixed in r22412. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 17:25:41 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 15:25:41 -0000 Subject: [Haiku-bugs] [Haiku] #1000: [Tracker] selected icons disappering In-Reply-To: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> References: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> Message-ID: <049.c0199ed5537aafab212e1123eb84b390@haiku-os.org> #1000: [Tracker] selected icons disappering -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 17:24:20 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 15:24:20 -0000 Subject: [Haiku-bugs] [Haiku] #852: [bin:gdb] won't quit correctly In-Reply-To: <040.7964588d81742cbd1482691cfe2dc5a0@haiku-os.org> References: <040.7964588d81742cbd1482691cfe2dc5a0@haiku-os.org> Message-ID: <049.02653e6a87f637009d770db9a8383287@haiku-os.org> #852: [bin:gdb] won't quit correctly ----------------------------+----------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * owner: axeld => bonefish * status: reopened => new -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 19:21:25 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 17:21:25 -0000 Subject: [Haiku-bugs] [Haiku] #687: Trying to write file when the disk its almost full In-Reply-To: <054.e104b11cb15e98c4dbd78fc16c28dfe4@haiku-os.org> References: <054.e104b11cb15e98c4dbd78fc16c28dfe4@haiku-os.org> Message-ID: <063.16cef9a8d8eb87b9708b1fb0798751fe@haiku-os.org> #687: Trying to write file when the disk its almost full ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by axeld): * platform: => All * milestone: R1 => R1/alpha Old description: > I was trying to copy/unzip files .. > > Look the screens. New description: I was trying to copy/unzip files .. Look the screens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 19:22:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 17:22:16 -0000 Subject: [Haiku-bugs] [Haiku] #693: Cannot Change Resolution per Workspace (easy) In-Reply-To: <054.cded4538db07e83281123e6417f59949@haiku-os.org> References: <054.cded4538db07e83281123e6417f59949@haiku-os.org> Message-ID: <063.e571f9e815c5e19b7b1b130a1c7a213b@haiku-os.org> #693: Cannot Change Resolution per Workspace (easy) ----------------------------------+----------------------------------------- Reporter: greg.gd at woosh.co.nz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:24:58 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:24:58 -0000 Subject: [Haiku-bugs] [Haiku] #827: app_server refresh bug on workspace change In-Reply-To: <040.30a6c0efdf243b349fb45b7f56ca7435@haiku-os.org> References: <040.30a6c0efdf243b349fb45b7f56ca7435@haiku-os.org> Message-ID: <049.a870410ed8125bb78ec617bc089fbcac@haiku-os.org> #827: app_server refresh bug on workspace change ---------------------------------+------------------------------------------ Reporter: axeld | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:25:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:25:12 -0000 Subject: [Haiku-bugs] [Haiku] #735: [Tracker] open with window content is shifted In-Reply-To: <040.fc768be9eb4b00e804da92509649778d@haiku-os.org> References: <040.fc768be9eb4b00e804da92509649778d@haiku-os.org> Message-ID: <049.cf008d72fc987f4edf68f341f5b18a10@haiku-os.org> #735: [Tracker] open with window content is shifted -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Tracker | Version: Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:25:22 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:25:22 -0000 Subject: [Haiku-bugs] [Haiku] #756: [app_server] crash in WindowList::RemoveWindow() In-Reply-To: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> References: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> Message-ID: <049.1ba03910b1d4940d6aa5df14e8c3909a@haiku-os.org> #756: [app_server] crash in WindowList::RemoveWindow() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:25:28 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:25:28 -0000 Subject: [Haiku-bugs] [Haiku] #827: app_server refresh bug on workspace change In-Reply-To: <040.30a6c0efdf243b349fb45b7f56ca7435@haiku-os.org> References: <040.30a6c0efdf243b349fb45b7f56ca7435@haiku-os.org> Message-ID: <049.55f4f6f83718724446d34e68c7ed691b@haiku-os.org> #827: app_server refresh bug on workspace change ---------------------------------+------------------------------------------ Reporter: axeld | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:41:41 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:41:41 -0000 Subject: [Haiku-bugs] [Haiku] #1361: Haiku wont boot on Asus P5W DH Deluxe In-Reply-To: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> References: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> Message-ID: <050.7c55e04dcfdaa4129e26c905b5f99113@haiku-os.org> #1361: Haiku wont boot on Asus P5W DH Deluxe ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by aldeck): It works in AHCI mode with r22412 :D I'm having the random tracker or deskbar crash on startup but thats another bug. Tried with a SATA disk with bios IDE emulation and it doesn't boot (will attach a serial log soon). I didn't retry with a PATA disk though. (for reference chipset is Intel 975X / Intel ICH7R) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 20:49:42 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 18:49:42 -0000 Subject: [Haiku-bugs] [Haiku] #1521: Haiku Radeon driver dont contains the 9550 ID In-Reply-To: <041.3d4e9ab694d49899af296f5eda7cd48f@haiku-os.org> References: <041.3d4e9ab694d49899af296f5eda7cd48f@haiku-os.org> Message-ID: <050.f7e89667a9935d9adec636f751ee19c7@haiku-os.org> #1521: Haiku Radeon driver dont contains the 9550 ID --------------------------------------+------------------------------------- Reporter: miqlas | Owner: euan Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by euan): * status: new => assigned Comment: this device ID is present in the driver. Can you provide a syslog for analysis? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:01:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:01:10 -0000 Subject: [Haiku-bugs] [Haiku] #1051: Disk Device Manager -- Implement Missing Disk Device Jobs In-Reply-To: <043.8272c9ee9d35d156fb2ca9da7f22c844@haiku-os.org> References: <043.8272c9ee9d35d156fb2ca9da7f22c844@haiku-os.org> Message-ID: <052.0d1110a1432d25fb9f284a82a172d500@haiku-os.org> #1051: Disk Device Manager -- Implement Missing Disk Device Jobs ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:01:47 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:01:47 -0000 Subject: [Haiku-bugs] [Haiku] #1052: Disk Device Manager -- Implement the Notification Mechanism In-Reply-To: <043.22a9372307491f325800fed7946227a2@haiku-os.org> References: <043.22a9372307491f325800fed7946227a2@haiku-os.org> Message-ID: <052.89907f6c95ab180c2195314870aa8014@haiku-os.org> #1052: Disk Device Manager -- Implement the Notification Mechanism ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:02:22 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #1053: Write Support in the Intel Partitioning Module In-Reply-To: <043.39f8e14bdd816d4f0d794bd49c4e7683@haiku-os.org> References: <043.39f8e14bdd816d4f0d794bd49c4e7683@haiku-os.org> Message-ID: <052.bc6ce73f16aa9133a4777b3b81c4e8fb@haiku-os.org> #1053: Write Support in the Intel Partitioning Module ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:02:44 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:02:44 -0000 Subject: [Haiku-bugs] [Haiku] #1054: Disk Device API -- Create Disk Device Parameter Editor Add-On Interface In-Reply-To: <043.cf4d8cc06a0b6273fee550445da44243@haiku-os.org> References: <043.cf4d8cc06a0b6273fee550445da44243@haiku-os.org> Message-ID: <052.abd0cac5a31bec98adaa9c13608e7a89@haiku-os.org> #1054: Disk Device API -- Create Disk Device Parameter Editor Add-On Interface -------------------------------+-------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:04:22 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:04:22 -0000 Subject: [Haiku-bugs] [Haiku] #1266: Unrecognised Partition Table errors In-Reply-To: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> References: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> Message-ID: <048.9c4f734d2860422c28446a908b176d73@haiku-os.org> #1266: Unrecognised Partition Table errors ----------------------------+----------------------------------------------- Reporter: euan | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha Comment: Any news? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:05:35 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:05:35 -0000 Subject: [Haiku-bugs] [Haiku] #1268: Incorporation of the well known live cd scripts in the build. In-Reply-To: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> References: <043.0ec3b288215ac8d81edd1780fc68e6bc@haiku-os.org> Message-ID: <052.e05265c95b046a7dd07366864b35e8d0@haiku-os.org> #1268: Incorporation of the well known live cd scripts in the build. ---------------------------+------------------------------------------------ Reporter: kaoutsis | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:06:04 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:06:04 -0000 Subject: [Haiku-bugs] [Haiku] #1491: input_server might be blocked on a modal panel during shutdown In-Reply-To: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> References: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> Message-ID: <051.f500374e9695a2de4ae2fe7ede65e18b@haiku-os.org> #1491: input_server might be blocked on a modal panel during shutdown --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:40:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:40:59 -0000 Subject: [Haiku-bugs] [Haiku] #852: [bin:gdb] won't quit correctly In-Reply-To: <040.7964588d81742cbd1482691cfe2dc5a0@haiku-os.org> References: <040.7964588d81742cbd1482691cfe2dc5a0@haiku-os.org> Message-ID: <049.38937693c32a6ba3e7e0656c72bf4997@haiku-os.org> #852: [bin:gdb] won't quit correctly ----------------------------+----------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * milestone: R1 => R1/alpha Comment: I can't reproduce the problem described in #478. I also tried a few crash situations, but gdb would always quit properly when closing the Terminal window. The problem might have been fixed by my changes regarding waitpid() or related stuff a few weeks ago. Unless you can still reproduce it, I would close it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 22:41:38 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 20:41:38 -0000 Subject: [Haiku-bugs] [Haiku] #1266: Unrecognised Partition Table errors In-Reply-To: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> References: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> Message-ID: <048.0500aee36b9f4a63479ef62e6bd2d5c8@haiku-os.org> #1266: Unrecognised Partition Table errors ----------------------------+----------------------------------------------- Reporter: euan | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Apologies I haven't been able to build haiku for a few weeks on linux due to several hardware changes. Was trying today to fix linux to test sata and this bug, but it didn't get far enough. Gimme a few more days if I don't get back to you later tonight, pretty please. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 23:05:58 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 21:05:58 -0000 Subject: [Haiku-bugs] [Haiku] #1492: PowerStatus app seems to be non-functional? In-Reply-To: <042.1dfc86fbfca4bedbe33bd7dd8ae05b04@haiku-os.org> References: <042.1dfc86fbfca4bedbe33bd7dd8ae05b04@haiku-os.org> Message-ID: <051.70160132230a53c28d6cce54fcde209a@haiku-os.org> #1492: PowerStatus app seems to be non-functional? -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/power_daemon | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by scottmc): Ok, still getting KDL with trying to run this with apm enabled on the thinkpad 570E, this time though I happened to have a serial cable attached, so here's the serial debug from power on up to and including the KDL after trying to start PowerStatus app. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 2 23:05:58 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 21:05:58 -0000 Subject: [Haiku-bugs] [Haiku] #1492: PowerStatus app seems to be non-functional? In-Reply-To: <042.1dfc86fbfca4bedbe33bd7dd8ae05b04@haiku-os.org> References: <042.1dfc86fbfca4bedbe33bd7dd8ae05b04@haiku-os.org> Message-ID: <051.70160132230a53c28d6cce54fcde209a@haiku-os.org> #1492: PowerStatus app seems to be non-functional? -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/power_daemon | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by scottmc): Ok, still getting KDL with trying to run this with apm enabled on the thinkpad 570E, this time though I happened to have a serial cable attached, so here's the serial debug from power on up to and including the KDL after trying to start PowerStatus app. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 00:28:53 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 22:28:53 -0000 Subject: [Haiku-bugs] [Haiku] #1266: Unrecognised Partition Table errors In-Reply-To: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> References: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> Message-ID: <048.28dc17c5b1da47bdfec67b457381fd76@haiku-os.org> #1266: Unrecognised Partition Table errors ----------------------------+----------------------------------------------- Reporter: euan | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by euan): Tested with r22233 Fat partition is now mountable, but attempting to write to it ended in error due to the write_bad_block problem that is subsequently fixed in recent commits. I can't update as SVN appears to be down. So it appears to be fixed. Syslog attached (fatTest.log) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 00:56:36 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 22:56:36 -0000 Subject: [Haiku-bugs] [Haiku] #1522: Crash on ALT+Q while adding a view containing a bitmap+offscreen view in App constructor to window Message-ID: <040.c4371dbb988f258a8dbbefdb769f6327@haiku-os.org> #1522: Crash on ALT+Q while adding a view containing a bitmap+offscreen view in App constructor to window --------------------------------+------------------------------------------- Reporter: julun | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- This is related to Ticket#1500.[[BR]] The orginal Be sample code created a window and a view in the app ctor, after that the window was locked and the view was added to the window as child.[[BR]] The special thing is that the view contains a bitmap with an offscreen view. While creating and adding the view containing the bitmap in the window ctor, everything works fine on ALT+Q. Doing this in the app ctor crashes the app on ALT+Q.[[BR]] Not creating and adding the bitmap with offscreen view, you can add the visible view in the app or window ctor without problems on quit. see attached sample code and stack trace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:31:04 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:31:04 -0000 Subject: [Haiku-bugs] [Haiku] #1437: Num Lock on at boot up In-Reply-To: <042.cbb0e6cb809b3eb335f2c04185f2c233@haiku-os.org> References: <042.cbb0e6cb809b3eb335f2c04185f2c233@haiku-os.org> Message-ID: <051.a67ce044d385b10a3548c5467d8b2e54@haiku-os.org> #1437: Num Lock on at boot up ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - Preferences | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:33:00 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:33:00 -0000 Subject: [Haiku-bugs] [Haiku] #1491: input_server might be blocked on a modal panel during shutdown In-Reply-To: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> References: <042.d51e2e51e6517b98989051fe8f0f17ea@haiku-os.org> Message-ID: <051.9752a5cbb51a5bc7e9b8403672bffb31@haiku-os.org> #1491: input_server might be blocked on a modal panel during shutdown --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: I haven't changed anything, but if no one can reproduce it anymore, I can as well close it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:36:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #1266: Unrecognised Partition Table errors In-Reply-To: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> References: <039.87acc4486e8656ddd16ec2e1dfd0277d@haiku-os.org> Message-ID: <048.f2c847520765fe945386e7d91f5091a7@haiku-os.org> #1266: Unrecognised Partition Table errors ----------------------------+----------------------------------------------- Reporter: euan | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks for the update. I close this ticket then. If the FAT FS problem persists with a current revision, please open a new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:48:31 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:48:31 -0000 Subject: [Haiku-bugs] [Haiku] #1361: Haiku wont boot on Asus P5W DH Deluxe In-Reply-To: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> References: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> Message-ID: <050.b24296d891e8ae65bbdb50d9351ddc09@haiku-os.org> #1361: Haiku wont boot on Asus P5W DH Deluxe ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by marcusoverhagen): * status: new => assigned Comment: I have exactly the same board and use it for ahci driver development. I also observed the same problem in IDE emulation mode. That is a bug somewhere in the IDE stack. Technically, AHCI is closer to a SCSI interface, and thus is using the SCSI stack and not the IDE stack. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:13:41 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:13:41 -0000 Subject: [Haiku-bugs] [Haiku] #1524: While the mouse pointer is over an popup, you can't go up or down using the keyboard Message-ID: <040.9dc2f19ea90bfee8d7a67c1cbdf99d32@haiku-os.org> #1524: While the mouse pointer is over an popup, you can't go up or down using the keyboard --------------------------------+------------------------------------------- Reporter: julun | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- open a popup, i.e time preflet timezone popup move the mouse over an item in the popup try the up or down key, the highlighted item stays at the mouse pointer -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 01:09:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 02 Oct 2007 23:09:59 -0000 Subject: [Haiku-bugs] [Haiku] #1523: Press ALT+W on opened popup will close it, try to access the popup again will crash the containing app Message-ID: <040.969d062f5b4077e5711ccc2ee8d1557c@haiku-os.org> #1523: Press ALT+W on opened popup will close it, try to access the popup again will crash the containing app --------------------------------+------------------------------------------- Reporter: julun | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- Steps: open Deskbar menu press ALT+W to close the menu try to open the menu again, deskbar crashes [[BR]] this works on every popup, it is not related to Deskbar -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 05:26:14 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 03:26:14 -0000 Subject: [Haiku-bugs] [Haiku] #1525: Haiku fails to detect CDs regardless of filesystem on nforce4 ATAPI Message-ID: <044.07e79bc131825ca3c4dde60e10ce127b@haiku-os.org> #1525: Haiku fails to detect CDs regardless of filesystem on nforce4 ATAPI --------------------------+------------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | --------------------------+------------------------------------------------- I've tried an ISO9660 CD, a Joliet CD, and also the R5 Pro hybrid CD. In none of said cases does the mount menu detect the volume, nor does mounting manually via the command line work (invalid argument). The CD drive itself appears to be detected though, as an entry is present in devfs at /dev/atapi/4/master/raw, and is hosted on an nforce4's PATA channels (its sister SATA controller is correctly recognizing and booting from the hdd on SATA). Motherboard: Asus A8N-SLI (Nforce4 + PCI Express, on-board nvidia SATA and PATA controllers) Please let me know what extra debug info would be useful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 06:53:37 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 04:53:37 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues Message-ID: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> #1526: TTY deadlock issues ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ running objdump -r on a large executable and then hitting ctrl+c caused Terminal to deadlock. Upon further investigation, Terminal was also rendered unkillable, and according to the kernel debugger the thread was hanging on trying to autolock gGlobalTTYLock. According to Travis it would probably be good if the sem was acquired with the interruptible flag set here and appropriate error handling for the interrupted case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 08:01:28 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 06:01:28 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.baf8a177f857f64ae1c380d893437914@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: emitrax Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * owner: mmlr => emitrax * status: assigned => new Comment: Reassigning to Salvatore as he will work on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 09:00:49 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 07:00:49 -0000 Subject: [Haiku-bugs] [Haiku] #1524: While the mouse pointer is over an popup, you can't go up or down using the keyboard In-Reply-To: <040.9dc2f19ea90bfee8d7a67c1cbdf99d32@haiku-os.org> References: <040.9dc2f19ea90bfee8d7a67c1cbdf99d32@haiku-os.org> Message-ID: <049.7433e1faf075945884c798c072c62d73@haiku-os.org> #1524: While the mouse pointer is over an popup, you can't go up or down using the keyboard ---------------------------------+------------------------------------------ Reporter: julun | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: This actually is a dup of #919 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 09:01:50 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 07:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #1523: Press ALT+W on opened popup will close it, try to access the popup again will crash the containing app In-Reply-To: <040.969d062f5b4077e5711ccc2ee8d1557c@haiku-os.org> References: <040.969d062f5b4077e5711ccc2ee8d1557c@haiku-os.org> Message-ID: <049.545e187f06282f13409cffbe49bfce44@haiku-os.org> #1523: Press ALT+W on opened popup will close it, try to access the popup again will crash the containing app ---------------------------------+------------------------------------------ Reporter: julun | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: dup of #1269 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 09:08:54 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 07:08:54 -0000 Subject: [Haiku-bugs] [Haiku] #582: Deskbar displays empty Haiku menu In-Reply-To: <054.a34a197cc42a843788451aba9ca3c3d1@haiku-os.org> References: <054.a34a197cc42a843788451aba9ca3c3d1@haiku-os.org> Message-ID: <063.37a900f3cb76a4affd291a71e4b4192b@haiku-os.org> #582: Deskbar displays empty Haiku menu ----------------------------------+----------------------------------------- Reporter: koki at digintrans.com | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by jackburton): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 11:55:23 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 09:55:23 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues In-Reply-To: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> References: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> Message-ID: <053.de19858d3d3fae250a52bcb4edf09478@haiku-os.org> #1526: TTY deadlock issues ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * owner: axeld => bonefish -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 11:59:52 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 09:59:52 -0000 Subject: [Haiku-bugs] [Haiku] #1525: Haiku fails to detect CDs regardless of filesystem on nforce4 ATAPI In-Reply-To: <044.07e79bc131825ca3c4dde60e10ce127b@haiku-os.org> References: <044.07e79bc131825ca3c4dde60e10ce127b@haiku-os.org> Message-ID: <053.b5e0f69676b9a6b697336978447f92d5@haiku-os.org> #1525: Haiku fails to detect CDs regardless of filesystem on nforce4 ATAPI ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by axeld): * owner: axeld => bonefish Comment: I guess you haven't put in the CD from the start on, but have switched it while Haiku was running? If so, it's more or less a duplicate of #1052 :-) The disk device manager currently does not check for any changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 14:57:25 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 12:57:25 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues In-Reply-To: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> References: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> Message-ID: <053.eb94cedc7d024a41136d9ea02216e8f0@haiku-os.org> #1526: TTY deadlock issues ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => assigned * milestone: R1 => R1/alpha Comment: Stack traces of the involved threads (the one blocking on the semaphore and the one that acquired the semaphore last) would help tremendously. I'll see, if I can reproduce it myself. Making the lock interruptible won't be necessary. It is supposed to be held only for a short time. No operations that can block for a longer time are performed with the lock held. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 15:03:30 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 13:03:30 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues In-Reply-To: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> References: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> Message-ID: <053.d93d0d7b17bf5135517097c2b6c7856d@haiku-os.org> #1526: TTY deadlock issues ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): I'll see what I can do, unfortunately at the time I wasn't aware of how to track this one down further since I didn't know what sem was involved without rebooting back to linux to check the sources on the stack trace I got from the terminal thread, so I don't know which other thread actually had the lock held. Will let you know if I manage to reproduce it again tonight. May not be related but I do also occasionally notice temporary freezes in the Terminal (5 secs or so), but I'm not sure if that's Terminal app or TTY layer related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 15:42:31 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 13:42:31 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.153a6a23e21fe6776c2b889a6bc55ddd@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by bonefish): * cc: bonefish (added) Comment: The problem is this: {{{ reading page from store 0x908ef500 (cache 0x908dc980) returned: Device/File/Resource busy! vm_page_fault: vm_soft_fault returned error 'Device/File/Resource busy' on fault at 0x3c4206, ip 0x3c4206, write 0, user 1, thread 0x4b }}} It seems the TryLock() in bfs_read_pages() isn't a good idea after all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 15:46:35 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 13:46:35 -0000 Subject: [Haiku-bugs] [Haiku] #155: keyboard doesn't always work In-Reply-To: <050.8ac75a19fe23bcf26c4287d1e2ffb3f4@haiku-os.org> References: <050.8ac75a19fe23bcf26c4287d1e2ffb3f4@haiku-os.org> Message-ID: <059.633d407d459fd0c7c719c99386cc1806@haiku-os.org> #155: keyboard doesn't always work ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): Marcus, is there still a problem with republished devices ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:25:18 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:25:18 -0000 Subject: [Haiku-bugs] [Haiku] #1527: Selecting an area on the desktop leaves ghostlines Message-ID: <042.707491492d3c5dfcbc5a423133096d6e@haiku-os.org> #1527: Selecting an area on the desktop leaves ghostlines -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Screenshot attached shows this, similar to the cursor ghosting bug, #1520. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:26:59 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:26:59 -0000 Subject: [Haiku-bugs] [Haiku] #1528: SoundPlay fails to load with Missing Sybol error Message-ID: <042.bbcba4a4294c30b932c21f13e23f7e19@haiku-os.org> #1528: SoundPlay fails to load with Missing Sybol error -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- SoundPlay 4.9.3 fails to load, giving a Missing Symbol errror. Screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:27:04 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:27:04 -0000 Subject: [Haiku-bugs] [Haiku] #1529: SoundPlay fails to load with Missing Sybol error Message-ID: <042.91475ffe8f833bcc70bf25eccf240a3f@haiku-os.org> #1529: SoundPlay fails to load with Missing Sybol error -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- SoundPlay 4.9.3 fails to load, giving a Missing Symbol errror. Screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:28:56 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:28:56 -0000 Subject: [Haiku-bugs] [Haiku] #1529: SoundPlay fails to load with Missing Sybol error In-Reply-To: <042.91475ffe8f833bcc70bf25eccf240a3f@haiku-os.org> References: <042.91475ffe8f833bcc70bf25eccf240a3f@haiku-os.org> Message-ID: <051.f9a2ae42256fbc157e44de6db6748e9d@haiku-os.org> #1529: SoundPlay fails to load with Missing Sybol error ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): Sorry for the double post. Keep this one as it has the screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:42:14 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:42:14 -0000 Subject: [Haiku-bugs] [Haiku] #1261: Can't load Haiku on a pc with Ati Radeon 9200 In-Reply-To: <042.11b485cf27f9b4d16fefc2076f130cff@haiku-os.org> References: <042.11b485cf27f9b4d16fefc2076f130cff@haiku-os.org> Message-ID: <051.d42a03bef3d960c3fa05a083829ecc4a@haiku-os.org> #1261: Can't load Haiku on a pc with Ati Radeon 9200 --------------------------------------+------------------------------------- Reporter: modeenf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by scottmc): Have you tried "safe video mode"? Right after the HAIKU logo on the black screen shows up press the spacebar, then try select safe video mode option and see if that lets you boot the rest of the way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:52:58 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:52:58 -0000 Subject: [Haiku-bugs] [Haiku] #1528: SoundPlay fails to load with Missing Sybol error In-Reply-To: <042.bbcba4a4294c30b932c21f13e23f7e19@haiku-os.org> References: <042.bbcba4a4294c30b932c21f13e23f7e19@haiku-os.org> Message-ID: <051.c2bcde1914a57599956f7967c79bedd4@haiku-os.org> #1528: SoundPlay fails to load with Missing Sybol error ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1529. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 17:25:01 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 15:25:01 -0000 Subject: [Haiku-bugs] [Haiku] #1529: SoundPlay fails to load with Missing Sybol error In-Reply-To: <042.91475ffe8f833bcc70bf25eccf240a3f@haiku-os.org> References: <042.91475ffe8f833bcc70bf25eccf240a3f@haiku-os.org> Message-ID: <051.2aafe63b0bf9b24cd1f2b3043cf49aa9@haiku-os.org> #1529: SoundPlay fails to load with Missing Sybol error ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Duplicate of #899. Please always search for old bugs before opening new ones, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 17:26:09 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 15:26:09 -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.fd102f2d4790ef0c7b1251d60ef8823e@haiku-os.org> #1527: Selecting an area on the desktop leaves ghostlines ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => stippi * component: - General => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 18:32:58 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 16:32:58 -0000 Subject: [Haiku-bugs] [Haiku] #1434: device manager loads driver too often In-Reply-To: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> References: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> Message-ID: <059.f07152625fbf186f1fcfd0ad46f72124@haiku-os.org> #1434: device manager loads driver too often ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by marcusoverhagen): This is turning into a serious problem now. As can be seen in the devicemanager.txt attachment, the board has two ahci controller devices, "0:31:2" and "5:0:0". The device manager loads the driver multiple times (1st error) and since the userCookie isn't always set correct, the pciDevice pointer is sometimes invalid and sometimes crashes. The pointer 0x90926300 in this crash isn't correct. ahci: ahci_sim_init_bus: pciDevice 0x90926300 ahci: AHCIController::Init 0:0:0 vendor 8086, device 277c vm_soft_fault: kernel thread accessing invalid user memory! vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x31, ip 0x802c12c1, write 0, user 0, thread 0x9 CPU 1 halted! PANIC: vm_page_fault: unhandled page fault in kernel space at 0x31, ip 0x802c12c1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 16:42:14 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 14:42:14 -0000 Subject: [Haiku-bugs] [Haiku] #1261: Can't load Haiku on a pc with Ati Radeon 9200 In-Reply-To: <042.11b485cf27f9b4d16fefc2076f130cff@haiku-os.org> References: <042.11b485cf27f9b4d16fefc2076f130cff@haiku-os.org> Message-ID: <051.d42a03bef3d960c3fa05a083829ecc4a@haiku-os.org> #1261: Can't load Haiku on a pc with Ati Radeon 9200 --------------------------------------+------------------------------------- Reporter: modeenf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by scottmc): Have you tried "safe video mode"? Right after the HAIKU logo on the black screen shows up press the spacebar, then try select safe video mode option and see if that lets you boot the rest of the way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 18:51:51 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 16:51:51 -0000 Subject: [Haiku-bugs] [Haiku] #1510: System freezes when trying to "SaveAs" from StyledEdit In-Reply-To: <042.61d2bcf9860bd0c992afb863027e91fa@haiku-os.org> References: <042.61d2bcf9860bd0c992afb863027e91fa@haiku-os.org> Message-ID: <051.d40d3e76e12de2a888a04bf201ae1412@haiku-os.org> #1510: System freezes when trying to "SaveAs" from StyledEdit ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): This seems to have gone away now, as of r22409 and r22412 at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 18:52:25 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 16:52:25 -0000 Subject: [Haiku-bugs] [Haiku] #1434: device manager loads driver too often In-Reply-To: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> References: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> Message-ID: <059.d0cab7601fb049703f8884d3adaa99e1@haiku-os.org> #1434: device manager loads driver too often ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by marcusoverhagen): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 3 21:34:17 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 19:34:17 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues In-Reply-To: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> References: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> Message-ID: <053.07dc912cef80732cb52c62c0b7e350e4@haiku-os.org> #1526: TTY deadlock issues ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: I couldn't reproduce a problem with gGlobalTTYLock, but I could reproduce the hanging after Ctrl-C. This issue is fixed in r22421. As long as we don't use many benaphores in the kernel, it is often relatively easy to track kernel deadlocks down (without looking at the sources). You can do that in the kernel debugger and basically only need the "teams", "threads" (or "thread"), and "sem" commands. With "threads" or "thread" one can find out what semaphore a thread is waiting for. "sem" lists the threads waiting for a semaphore, the semaphore count, and, most interestingly, what thread acquired/released the semaphore last (last_acquirer/last_releaser -- if last_acquirer is negative, the semaphore has been released by last_releaser after it has been acquired by -last_acquirer). So, when you've found a semaphore that seems to be involved in a deadlock, "sem" tells you who acquired the semaphore last, "thread" in turn shows the semaphore that thread is waiting for. Alternating "sem" and "thread" until a cycle is found will then uncover the deadlock. Theoretically the same works for userland deadlocks as well, but only when BLocker is used semaphore style (can be hacked to always be). Otherwise the last acquirer is not trackable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 01:47:39 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 03 Oct 2007 23:47:39 -0000 Subject: [Haiku-bugs] [Haiku] #1517: registrar crash during boot In-Reply-To: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> References: <050.7685cbe69c66ac2522eaba130b4c7202@haiku-os.org> Message-ID: <059.f1ed5d9fce1249b6751eaaff9789fd4b@haiku-os.org> #1517: registrar crash during boot ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Platform: All ------------------------------+--------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1509. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 02:19:09 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 00:19:09 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work Message-ID: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Drivers/Graphics/nVidia | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- When booting with a NVIDIA GeForce FX 6600 PCIe card (id 0x0141), attached to a DVI TFT screen HP LP2465, only a black screen with a dotted pinc vertical line is shown. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 04:37:33 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 02:37:33 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.a78550a5d9cbfbb43631702fb007189e@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tonestone57): Thanks bonefish, I'm hoping someone will fix it soon. I was going to do further testing with a newer Haiku image but had no time. The crashing was only occurring with tracker when first starting up Haiku. I must have had tracker crash about 5 ( to 7 ) times and deskbar 3 times on about 12 boot ups. This is on a single core, Athlon XP system. I believe those with multi- core were experiencing the tracker crashing more often. I'll retest Haiku image once I know this bug has been fixed. PS bug 1512 sounded similar, but that one concerns the system "freezing" and this one is about tracker and/or deskbar crashing on boot. Though the same issue might be affecting both bugs? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 05:48:23 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 03:48:23 -0000 Subject: [Haiku-bugs] [Haiku] #1531: sounds preferences not remembered after reboot Message-ID: <040.284ee2d80f2b7251b41caf9c0f4c134d@haiku-os.org> #1531: sounds preferences not remembered after reboot ----------------------------------+----------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Sounds | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- If I copy some wav sounds to /boot/beos/etc/sounds, then apply wav sounds to events in Sounds preferences application, when I reboot the settings are lost. To reproduce: 1) Open Preferences/Sounds. 2)Assign a wav sound like BeStartup.wav to BeStartup. 3) Close the Sounds application. 4) Reboot On reboot the BeStartup.wav sound does not play. On openning Preferences Sounds the assigned sound is seen to be lost. This is reproduceable always. The version I was testing was: r22418 on its own partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 08:41:29 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 06:41:29 -0000 Subject: [Haiku-bugs] [Haiku] #1526: TTY deadlock issues In-Reply-To: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> References: <044.711f523947bc0f1f0b0c649f32064ce6@haiku-os.org> Message-ID: <053.ec0e387a6f1dd8a59fb02ec60974d571@haiku-os.org> #1526: TTY deadlock issues ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:4 bonefish]: > > Theoretically the same works for userland deadlocks as well, but only when BLocker is used semaphore style (can be hacked to always be). We could make it so when DEBUG is defined (I did that for BHandler) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 09:02:33 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 07:02:33 -0000 Subject: [Haiku-bugs] [Haiku] #1469: ls od dir commands produce illegible colors. In-Reply-To: <042.991bbed1e47687a2904060181d8b41c2@haiku-os.org> References: <042.991bbed1e47687a2904060181d8b41c2@haiku-os.org> Message-ID: <051.bc437a551e41170c681f1d971286b21b@haiku-os.org> #1469: ls od dir commands produce illegible colors. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by jackburton): * owner: jackburton => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 11:45:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 09:45:11 -0000 Subject: [Haiku-bugs] [Haiku] #1518: nVidia driver does not work with N7600GS card In-Reply-To: <041.6fd9222743858eb0021210d15066a0ca@haiku-os.org> References: <041.6fd9222743858eb0021210d15066a0ca@haiku-os.org> Message-ID: <050.3976989466c56f116165f05f4d472b89@haiku-os.org> #1518: nVidia driver does not work with N7600GS card --------------------------------------+------------------------------------- Reporter: hitech | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by axeld): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 13:31:58 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 11:31:58 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.3cb5cfe100553492a72a02aef417ab1d@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 13:32:09 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 11:32:09 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.882d743a8c40a2b06693e928a08d00a7@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => critical -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 14:45:38 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 12:45:38 -0000 Subject: [Haiku-bugs] [Haiku] #1509: Tracker Crashes When Starting / Booting Haiku In-Reply-To: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> References: <046.44f5665e6d7d9e51d20705b581c65113@haiku-os.org> Message-ID: <055.2d7a0b37eca16588d16fa36183aa5b33@haiku-os.org> #1509: Tracker Crashes When Starting / Booting Haiku ----------------------------+----------------------------------------------- Reporter: tonestone57 | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r22434. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 14:59:53 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 12:59:53 -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.e06735d8120aa34a9194385cc4e9ca49@haiku-os.org> #1527: Selecting an area on the desktop leaves ghostlines ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Since this only showed up lately, it might be related to wrong handling of fractional coordinates ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 16:15:06 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 14:15:06 -0000 Subject: [Haiku-bugs] [Haiku] #1532: Cursor ghosting in StyledEdit Message-ID: <042.4387d1b3b3f62d6c56d4c19997b86b7e@haiku-os.org> #1532: Cursor ghosting in StyledEdit --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- This is similar to #1520, but not sure that it is the same cause or not. To duplicate, open a text file in StyledEdit. Click in the text area somewhere and then press the down arrow key to move the cursor down, hold it down for a few lines. This will sometimes leave a vertical line next to text you've already passed, where the cursor was drawn but not removed. I'll see if I can get a screenshot of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 16:27:24 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 14:27:24 -0000 Subject: [Haiku-bugs] [Haiku] #1532: Cursor ghosting in StyledEdit In-Reply-To: <042.4387d1b3b3f62d6c56d4c19997b86b7e@haiku-os.org> References: <042.4387d1b3b3f62d6c56d4c19997b86b7e@haiku-os.org> Message-ID: <051.1401b7b23ce6915dadb3475005c18ddd@haiku-os.org> #1532: Cursor ghosting in StyledEdit ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: dup of #1520 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 17:25:54 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 15:25:54 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Greek (keyboard) bug for BeMail. In-Reply-To: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> References: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> Message-ID: <052.f17c76e6aadd738c689c093540722cf2@haiku-os.org> #1022: Greek (keyboard) bug for BeMail. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 19:54:13 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 17:54:13 -0000 Subject: [Haiku-bugs] [Haiku] #1176: vmware VIDE error In-Reply-To: <050.7583c71c95c7ea989018a85575d9b142@haiku-os.org> References: <050.7583c71c95c7ea989018a85575d9b142@haiku-os.org> Message-ID: <059.5a5477343a95356448c53daea4f6bfcb@haiku-os.org> #1176: vmware VIDE error ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by bonefish): * cc: bonefish (added) Comment: This problem is so annoying, particularly when working on the disk device manager. Any chance I can bribe you (beer at the next BeGeistert?) into looking into it? :-P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 21:58:27 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 19:58:27 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Dead keys and inlineinput crash Mail. In-Reply-To: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> References: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> Message-ID: <052.4756d11bea8839f5ffed6d207644d18f@haiku-os.org> #1022: Dead keys and inlineinput crash Mail. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * summary: Greek (keyboard) bug for BeMail. => Dead keys and inlineinput crash Mail. Old description: > Open BeMail for new mail. > Fill > Fill with bar You can write > Greek here, as normal, no crash here. > > Open Preferences => Keymap select > Greek keyboard (you are suppose that > you want to write Greek:-) > After selecting the Greek keymap, > you are writing to the body of the mail > some greek letters. When you press > key for tonos (english ; or raw key 0x45) > you go to gdb. > If you want to debug, you must > type some English instructions into the Terminal, > for example "where". > > So you go to the keymap program > to set language to American, > when click to American, you go directly > to KDL. > TODO: writing the kdl message. > > ps: opening a already composed email > with full greek text, there is no crash. New description: Open Mail for new mail. Fill Fill with bar You can write Greek here, as normal, no crash here. Open Preferences => Keymap select Greek keyboard (you are suppose that you want to write Greek:-) After selecting the Greek keymap, you are writing to the body of the mail some greek letters. When you press key for tonos (english ; or raw key 0x45) you go to gdb. If you want to debug, you must type some English instructions into the Terminal, for example "where". So you go to the keymap program to set language to American, when click to American, you go directly to KDL. TODO: writing the kdl message. ps: opening a already composed email with full greek text, there is no crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 21:58:57 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 19:58:57 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Dead keys and inlineinput crash Mail. In-Reply-To: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> References: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> Message-ID: <052.aeace106b5004480402dce8618b7e56f@haiku-os.org> #1022: Dead keys and inlineinput crash Mail. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * status: assigned => closed * resolution: => fixed Comment: Fixed in r22444 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 22:36:49 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 20:36:49 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm Message-ID: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> #1533: forcerm ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- I believe forcerm was part of R5. Anyways, I somehow ended up with a folder that contained some files in it that I couldn't delete off the disk... an enhancement to allow force delete would be good, or perhaps there's another way in Haiku I'm unaware of. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 22:52:53 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 20:52:53 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.ca398646cb065251335fc0c5fdf4b893@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by umccullough): Replying to [comment:1 umccullough]: > Isn't that what rm -rf is for? Perhaps I'm ignorant - I looked up the definition of -f and it seems to simply not prompt, and ignore missing files... So I can't find any documentation on what forcerm actually did other than "removes stubborn files" :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 22:55:52 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 20:55:52 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.439b66b5229db86105f25455f467f787@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): Oh, well yes, that's exactly what I wanted. Removing stubborn files. Wasn't there a key combination for force delete? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 22:58:35 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 20:58:35 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.ab3234db545d7fcaa7ba7d11c9c55562@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): Here's reference to 'forcerm' [http://209.85.165.104/search?q=cache:HiMSf7F- pusJ:www.betips.net/chunga.php%3Fid%3D538+forcerm+beos&hl=en&ct=clnk&cd=1&gl=ca] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 22:41:30 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 20:41:30 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.265a41250e42a20344f7899d219366a4@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by umccullough): Isn't that what rm -rf is for? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 4 23:57:21 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 21:57:21 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.57950b11984b5253d763889aa91b0928@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: "forcerm" is a work-around for a bug in the original BFS implementation. It does not apply to Haiku's BFS. If you somehow manage to create files that you can't delete, then please tell me how you did it, or please make an image available - and open another bug report for that :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:00:15 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:00:15 -0000 Subject: [Haiku-bugs] [Haiku] #1510: System freezes when trying to "SaveAs" from StyledEdit In-Reply-To: <042.61d2bcf9860bd0c992afb863027e91fa@haiku-os.org> References: <042.61d2bcf9860bd0c992afb863027e91fa@haiku-os.org> Message-ID: <051.ebc887e82d3c24d9086cee5e13c7af84@haiku-os.org> #1510: System freezes when trying to "SaveAs" from StyledEdit ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:04:19 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:04:19 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.5efc0562da6117c08751f11a237320ef@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): I'm not sure I could replicate the problem, but I had a lot of cache in Opera's temp directory, and I tried deleting the contents, but tracker got stuck about 40% of the way through, after waiting about 10 min. I reset the system. Upon reboot, I threw the entire folder in the trash, but when I tried to empty it, it gave an error that it couldn't delete some of the files. Upon checking the contents of that folder, the files weren't in there anymore, but tracker still gave the warnings for the specific files it can't delete. Actually I still have the disk image the problem is on, would you like it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:17:41 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:17:41 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.64e89e115ffdae6f629a99e70da9dbf7@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): That would definitely be helpful! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:23:37 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:23:37 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.137d4ebdbd407e0e0d074740df435a2c@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by umccullough): Replying to [comment:5 axeld]: > "forcerm" is a work-around for a bug in the original BFS implementation. It does not apply to Haiku's BFS. I was thinking something like that when I read the definition on betips... If anything else, the (inevitable) Haiku version of chkbfs should be able to fix any and all known issues like this right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:29:02 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:29:02 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.6aeaf7453ae743a720f5ef247b1cd4d3@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Replying to [comment:8 umccullough]: > If anything else, the (inevitable) Haiku version of chkbfs should be able to fix any and all known issues like this right? Exactly - unlike forcerm, chkbfs is unfortunately implicit with the design of BFS. It will be part of Haiku as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:33:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:33:11 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.17bf283b38d287b72c08c2a46310370e@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): try unzipping this folder and then sending it to the trash and deleting it. I may have to send you the disk image if this doesn't work (or if you delete it lol). [http://www.haikuware.com/downloads/Languages.zip] btw, did you get the paypal transfer for the thank you award Axel. Bye! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:35:40 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:35:40 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.cdc190f27f5a85438e5ca2e9775b892e@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): One question about chkbfs though... say in the case of a normal user, the situation occurs as it did to me. With the befs one talked about elegant and worry-free recoveries after power failures etc. and no check disk like in Windows... How is the average Joe going to know to run chkbfs from the terminal in order to repair an error in the filesystem/files like this?? thx -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:46:30 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:46:30 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.7e285489bfb60198fab6a8221ccf33e2@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by kvdman): Sorry, one more comment... OS X has a similar file system, how do they get around this? If there's a dirty unmount, or shutdown, that gets logged right? And then after so many dirty unmounts, their filesystem check gets initiated? Would Haiku have something similar? Isn't their also a file system check when you install system software or updates 'optimizing performance'? thx -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 00:53:23 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 04 Oct 2007 22:53:23 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.7d4b995135b8c3e564e94414197c4dd5@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by umccullough): > With the befs one talked about elegant and worry-free recoveries after power failures etc. and no check disk like in Windows I've always found that a bit annoying personally... it's just marketing talk. Perhaps it works like that in theory, but low power and power failures can do bad things to hardware which can subsequently do bad things to disks... so it's not a very smart statement. A stick of bad RAM can also cause untold amounts of damage to filesystems... In any case, the existence of chkbfs, and how it's run are two very separate discussions... once it's written, I suspect the "automation" of running it whenever necessary can be implemented as needed. Perhaps Tracker has some logic that watches for bad situations and alerts the user that they need to run chkbfs (which it will then prompt them for) - that's just details. Ultimately chkbfs must exist - just like every filesystem benefits from some type of consistency-checking utility. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 11:22:48 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 09:22:48 -0000 Subject: [Haiku-bugs] [Haiku] #1533: forcerm In-Reply-To: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> References: <041.aaaa6ab5439f8d22a9054e3347875ba6@haiku-os.org> Message-ID: <050.48be0e4f0bc9d2e5f1a9ed7b3a7671a4@haiku-os.org> #1533: forcerm -------------------------------+-------------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Replying to [comment:10 kvdman]: > try unzipping this folder and then sending it to the trash and deleting it. I may have to send you the disk image if this doesn't work (or if you delete it lol). > [http://www.haikuware.com/downloads/Languages.zip] Once you zipped it up and there still is the same problem, it's no BFS bug anymore. In this case, the files were directories, and I could easily delete them (ie. using "rm -rf"). So if that doesn't help on your image, I would need that. > btw, did you get the paypal transfer for the thank you award Axel. Sure, and thanks! BTW I've republished the lost newsletter "Why BFS needs chkbfs" as part of my blog: http://haiku-os.org/blog/axeld/2007-10-05/why_bfs_needs_chkbfs -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 15:32:00 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 13:32:00 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.6f40e153124c90ce7530eeedf0c3919c@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * cc: marcusoverhagen (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 17:29:25 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 15:29:25 -0000 Subject: [Haiku-bugs] [Haiku] #1534: Assert in DoublyLinkedList.h Message-ID: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> #1534: Assert in DoublyLinkedList.h -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- During shutdown: {{{ list: 0x90810810, element: 0x908bc4e0 PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:464): fFirst != 0 && fLast != 0 && (fFirst != fLast || element == Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x49 "Terminal" kernel stack: 0x90660000 to 0x90664000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 90663ca0 (+ 52) 8008e5c4 :invoke_command + 0x0074 90663cd4 (+ 48) 8008e6e2 :kernel_debugger_loop + 0x00de 90663d04 (+ 32) 8008f16e :kernel_debugger + 0x00b2 90663d24 (+ 192) 8008f0b1 :panic + 0x0029 90663de4 (+ 64) 8003ae40 :team_set_job_control_state + 0x012c 90663e24 (+ 128) 8003d7f4 :thread_exit + 0x0168 90663ea4 (+ 64) 80034acc :handle_signals + 0x0328 90663ee4 (+ 48) 8003dcbd :thread_at_kernel_exit + 0x0015 90663f14 (+ 144) 80097e16 :i386_handle_trap + 0x0402 iframe at 0x90663fac (end = 0x90664000) eax 0x0 ebx 0x830750 ecx 0x7ffe6e50 edx 0x0 esi 0x7ffef538 edi 0x7ffe7100 ebp 0x7ffe6f6c esp 0x90663fdc eip 0xffff0102 eflags 0x207 vector: 0x63, error code: 0x0 90663fa4 (+ 0) ffff0102 7ffe6f6c -- read fault }}} BTW. Seems that assert line is truncated. Maybe it's another bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 17:49:11 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 15:49:11 -0000 Subject: [Haiku-bugs] [Haiku] #1534: Assert in DoublyLinkedList.h In-Reply-To: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> References: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> Message-ID: <051.d6573bc22cc8d643811ba28a194f3d02@haiku-os.org> #1534: Assert in DoublyLinkedList.h ----------------------------+----------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * owner: axeld => bonefish * priority: normal => critical * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 18:00:29 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 16:00:29 -0000 Subject: [Haiku-bugs] [Haiku] #1534: Assert in DoublyLinkedList.h In-Reply-To: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> References: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> Message-ID: <051.b0ac874f2bdd4fc15c876073509c896c@haiku-os.org> #1534: Assert in DoublyLinkedList.h ----------------------------+----------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: assigned Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 18:57:06 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 16:57:06 -0000 Subject: [Haiku-bugs] [Haiku] #1534: Assert in DoublyLinkedList.h In-Reply-To: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> References: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> Message-ID: <051.528b446bf81fc99d8b77dc63a0960c3d@haiku-os.org> #1534: Assert in DoublyLinkedList.h ----------------------------+----------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r22450. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 19:06:03 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 17:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #1534: Assert in DoublyLinkedList.h In-Reply-To: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> References: <042.bdbb157f36ae9ade60917151ab3b2b56@haiku-os.org> Message-ID: <051.569fbe2eb7939a5641df8ffbee3a543b@haiku-os.org> #1534: Assert in DoublyLinkedList.h ----------------------------+----------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Regarding the truncated assert line: This is a limitation of panic(). It uses a 128 byte on-stack buffer to format the output. We could probably use a larger static buffer (per CPU?), but usually 128 are enough. For asserts source file and line number do suffice, since the truncated part is static text anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 19:17:11 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 17:17:11 -0000 Subject: [Haiku-bugs] [Haiku] #845: Haiku fails to build on x86_64 Linux In-Reply-To: <049.82a22c88477a874ab24dc8263770263a@haiku-os.org> References: <049.82a22c88477a874ab24dc8263770263a@haiku-os.org> Message-ID: <058.810b5bed00c70e4bbf0e514244ef0210@haiku-os.org> #845: Haiku fails to build on x86_64 Linux -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x64 -----------------------------+---------------------------------------------- Comment (by etteyafed): Replying to [ticket:845 johndrinkwater]: I can now build gcc4 and haiku with gcc4 on x86_64 but not with gcc 2.95.x yet. This may be unneeded info, but I didn't have time to read the follow ups completely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 19:29:25 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 17:29:25 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on SMP systems. Message-ID: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> #1535: Lock up on SMP systems. ------------------------------+--------------------------------------------- Reporter: etteyafed | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- The system in question is a HP Pavilion dv6000 with an Intel Core 2 Duo 5400 1.7ghz and 2gb ram. The chipset is Intel 945GM. Experienced behavior: When I try to move a window the whole system locks up including the mouse. The kernel debugger is accessible by pressing F12 but it does not open automatically. Expected behavior: The window moves as usual. How to reproduce: Try to move a window on the desktop. This issue is relevant to Rev. 22437 last I checked. I will verify this with 22450 ASAP and update with any changes. This system has no serial port so I might have to get a USB->Serial adapter for more info. I couldn't find anything in kdbg that looked wrong (but I didn't really know what to look for). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 19:42:59 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 17:42:59 -0000 Subject: [Haiku-bugs] [Haiku] #1536: bad interpreter: Argument too big Message-ID: <042.ef8fff23fd096746a0a4bd9248b395d2@haiku-os.org> #1536: bad interpreter: Argument too big -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Commands to reproduce the problem: {{{ echo '#!/bin/sh' > emptyscript.sh chmod +x emptyscript.sh ./emptyscript.sh }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 20:44:25 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 18:44:25 -0000 Subject: [Haiku-bugs] [Haiku] #1516: Various file operations fail when the filename is the empty string. In-Reply-To: <038.53b6e67d746aa701a16fd438b12abd23@haiku-os.org> References: <038.53b6e67d746aa701a16fd438b12abd23@haiku-os.org> Message-ID: <047.1b32f02eca60640f622d4612352604fe@haiku-os.org> #1516: Various file operations fail when the filename is the empty string. ------------------------+--------------------------------------------------- Reporter: mjw | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r22451. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 5 21:01:35 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 05 Oct 2007 19:01:35 -0000 Subject: [Haiku-bugs] [Haiku] #1536: bad interpreter: Argument too big In-Reply-To: <042.ef8fff23fd096746a0a4bd9248b395d2@haiku-os.org> References: <042.ef8fff23fd096746a0a4bd9248b395d2@haiku-os.org> Message-ID: <051.faf1f140fb4411554ddcaa60db421435@haiku-os.org> #1536: bad interpreter: Argument too big ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r22452. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 6 07:03:38 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 06 Oct 2007 05:03:38 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.4fb90b82b92bbf69802c8e2934a42cfa@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. -------------------------------+-------------------------------------------- Reporter: etteyafed | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by etteyafed): * summary: Lock up on SMP systems. => Lock up on system while using regular NVIDIA driver. Comment: Replying to [ticket:1535 etteyafed]: It this problem goes away if I enable failsafe video mode. The card I am using is an embedded GeForce Go 7400. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 6 07:04:40 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 06 Oct 2007 05:04:40 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.747513bb022d98f4f443444d28eb0205@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. --------------------------------------+------------------------------------- Reporter: etteyafed | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by etteyafed): * owner: stippi => axeld * component: - User Interface => Drivers/Graphics/nVidia -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 6 14:58:24 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 06 Oct 2007 12:58:24 -0000 Subject: [Haiku-bugs] [Haiku] #1361: IDE (native and emulated) doesn't work when a SATA AHCI controller is present In-Reply-To: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> References: <041.8ad85acdd1263df20aec0d3f566f2b59@haiku-os.org> Message-ID: <050.2fc33fca8c86e52752885416853bd794@haiku-os.org> #1361: IDE (native and emulated) doesn't work when a SATA AHCI controller is present ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by aldeck): * summary: Haiku wont boot on Asus P5W DH Deluxe => IDE (native and emulated) doesn't work when a SATA AHCI controller is present Comment: Changed the summary for future reference (better, ain't it?). For reference too, i'm noting here the revisions of your recent fixes: r22419, r22425 marcus: Does it work for you now? I didn't have time to test again, i will try next week :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 6 21:33:15 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 06 Oct 2007 19:33:15 -0000 Subject: [Haiku-bugs] [Haiku] #1537: Freecell 0.92 quits responding Message-ID: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> #1537: Freecell 0.92 quits responding -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Get Freecell 0.92 from BeBits, play 2-5 rounds. What happens is the game will not let you pick up or move any cards, if you wait about 5-10 seconds it will let you pick up one more card and then nothing works. I tried it on BeOS and don't see this happening. I think it might be the scheduler related or something like that? When it stops responding you can click the window close button and then restart the game which recalls where you left off, but if you had a card stuck to the cursor that card might now be missing thus your streak of winning 4 in a row is done ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 09:30:46 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 07:30:46 -0000 Subject: [Haiku-bugs] [Haiku] #1538: Page fault during installing perl from sources Message-ID: <042.0dde8fab91dee81d44fdc12b6183f486@haiku-os.org> #1538: Page fault during installing perl from sources ---------------------+------------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: All | ---------------------+------------------------------------------------------ I've successfully compiled (gcc 2.9.x) perl-5.8.8 under Haiku using: {{{ export LDLOADLIBS="-lnet" ./Configure -ds -e -Dosname=beos -Dcc=gcc -Duseshrplib }}} but during install (e.g. make install DESTDIR=/boot/home/perl) perl crashes: {{{ 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 0x6a6689, write 0, user 1, thread 0x27e5 vm_page_fault: sending team "./perl" 0x27e5 SIGSEGV, ip 0x6a6689 ("Cwd.so_seg0ro" +0x1689) stack trace: 0x002762a2 (libperl.so_seg0ro + 0x722a2) 0x0026f603 (libperl.so_seg0ro + 0x6b603) 0x00220d49 (libperl.so_seg0ro + 0x1cd49) 0x00220abe (libperl.so_seg0ro + 0x1cabe) 0x002242dc (libperl.so_seg0ro + 0x202dc) 0x00223fbc (libperl.so_seg0ro + 0x1ffbc) 0x0024b609 (libperl.so_seg0ro + 0x47609) 0x002488cc (libperl.so_seg0ro + 0x448cc) 0x002419bf (libperl.so_seg0ro + 0x3d9bf) 0x0021fe77 (libperl.so_seg0ro + 0x1be77) 0x0021efe0 (libperl.so_seg0ro + 0x1afe0) 0x002017b7 (perl_seg0ro + 0x17b7) 0x002013ef (perl_seg0ro + 0x13ef) 0x001007be (runtime_loader_seg0ro + 0x7be) 0x7ffe6fec (./perl_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 0x8009b1ec, write 0, user 0, thread 0x27e5 debug_server: Thread 10213 entered the debugger: Segment violation stack trace, current PC 0x6a6689 boot_Cwd + 0x25: (0x7ffe6b2c) 0x2762a2 Perl_pp_entersub + 0x4f2 (0x7ffe6b8c) 0x26f603 Perl_runops_standard + 0x33 (0x7ffe6bac) 0x220d49 Perl_call_sv + 0x6b9 (closest symbol) (0x7ffe6bcc) 0x220abe Perl_call_sv + 0x42e (0x7ffe6c7c) 0x2242dc Perl_call_list + 0x454 (closest symbol) (0x7ffe6cac) 0x223fbc Perl_call_list + 0x134 (0x7ffe6d0c) 0x24b609 Perl_newATTRSUB + 0xc0d (0x7ffe6dac) 0x2488cc Perl_utilize + 0x358 (0x7ffe6e1c) 0x2419bf Perl_yyparse + 0xf4f (0x7ffe6e8c) 0x21fe77 perl_parse + 0x118b (closest symbol) (0x7ffe6edc) 0x21efe0 perl_parse + 0x2f4 (0x7ffe6f3c) 0x2017b7 main + 0xa7 (0x7ffe6f7c) 0x2013ef _start + 0x5b (0x7ffe6fac) 0x1007be (runtime_loader_seg0ro + 0x7be) }}} and GDB says: {{{ GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 10213 caused an exception: Segment violation Reading symbols from /boot/home/perl-5.8.8/libperl.so...(no debugging symbols found)...done. Loaded symbols for /boot/home/perl-5.8.8/libperl.so Reading symbols from /boot/beos/system/lib/libnetwork.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libnetwork.so Reading symbols from /boot/beos/system/lib/libroot.so...done. Loaded symbols for /boot/beos/system/lib/libroot.so Reading symbols from /boot/beos/system/lib/libbe.so...done. Loaded symbols for /boot/beos/system/lib/libbe.so Reading symbols from /boot/beos/system/lib/libstdc++.r4.so...done. Loaded symbols for /boot/beos/system/lib/libstdc++.r4.so Reading symbols from /boot/home/perl-5.8.8/lib/auto/Cwd/Cwd.so...done. Loaded symbols for /boot/home/perl-5.8.8/lib/auto/Cwd/Cwd.so Reading symbols from /boot/home/perl-5.8.8//libperl.so...done. Loaded symbols for /boot/home/perl-5.8.8//libperl.so [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team ./perl installperl --destdir=/boot/home/perl (10213) thread perl (10213)] 0x006a6689 in boot_Cwd () from /boot/home/perl-5.8.8/lib/auto/Cwd/Cwd.so (gdb) thread apply all bt Thread 1 (team ./perl installperl --destdir=/boot/home/perl (10213) thread perl(10213)): #0 0x006a6689 in boot_Cwd () from /boot/home/perl-5.8.8/lib/auto/Cwd/Cwd.so #1 0x002762a2 in Perl_pp_entersub () from /boot/home/perl-5.8.8/libperl.so #2 0x0026f603 in Perl_runops_standard () from /boot/home/perl-5.8.8/libperl.so #3 0x00220d49 in S_call_body () from /boot/home/perl-5.8.8/libperl.so #4 0x00220abe in Perl_call_sv () from /boot/home/perl-5.8.8/libperl.so #5 0x002242dc in S_call_list_body () from /boot/home/perl-5.8.8/libperl.so #6 0x00223fbc in Perl_call_list () from /boot/home/perl-5.8.8/libperl.so #7 0x0024b609 in Perl_newATTRSUB () from /boot/home/perl-5.8.8/libperl.so #8 0x002488cc in Perl_utilize () from /boot/home/perl-5.8.8/libperl.so #9 0x002419bf in Perl_yyparse () from /boot/home/perl-5.8.8/libperl.so #10 0x0021fe77 in S_parse_body () from /boot/home/perl-5.8.8/libperl.so #11 0x0021efe0 in perl_parse () from /boot/home/perl-5.8.8/libperl.so #12 0x002017b7 in main () (gdb) }}} I don't know what's wrong. Maybe loading dynamic modules is broken? Dynamic modules were built with "gcc -nostart", in a linux it's compiled with "gcc -shared". BTW. Why "tcsetpgrp failed in terminal_inferior: Invalid Argument"? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 15:54:00 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 13:54:00 -0000 Subject: [Haiku-bugs] [Haiku] #1506: BMenuItem's trigger is drawn at incorrect position. In-Reply-To: <040.ec7352bc1d58463d63a4f52e5d641bad@haiku-os.org> References: <040.ec7352bc1d58463d63a4f52e5d641bad@haiku-os.org> Message-ID: <049.5379b6380e82958861980042ff43b5e7@haiku-os.org> #1506: BMenuItem's trigger is drawn at incorrect position. ---------------------------------+------------------------------------------ Reporter: hiron | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by hiron): * status: closed => reopened * resolution: fixed => Comment: The latter one is not fixed yet. fTriggerIndex still holds a byte position. In BMenuItem::SetTrigger(char) {{{ fTriggerIndex = pos - Label(); }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 19:20:58 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 17:20:58 -0000 Subject: [Haiku-bugs] [Haiku] #1506: BMenuItem's trigger is drawn at incorrect position. In-Reply-To: <040.ec7352bc1d58463d63a4f52e5d641bad@haiku-os.org> References: <040.ec7352bc1d58463d63a4f52e5d641bad@haiku-os.org> Message-ID: <049.12e06b7389d68a093deeb6ab13b7a970@haiku-os.org> #1506: BMenuItem's trigger is drawn at incorrect position. ---------------------------------+------------------------------------------ Reporter: hiron | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Thanks a lot for retesting! It's fixed now in r22476. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 21:58:06 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 19:58:06 -0000 Subject: [Haiku-bugs] [Haiku] #1539: strange problem with pipes Message-ID: <042.e8ab2f0e15091bb2d7be8041099d9de5@haiku-os.org> #1539: strange problem with pipes ---------------------+------------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: All | ---------------------+------------------------------------------------------ Try this under Haiku: {{{ seq 200 | while read line; do echo ":$line:"; done }}} The result is strange: {{{ :1: :: :9: :124: :156: :188: }}} I'm using rev. 22462 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 22:30:23 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 20:30:23 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell Message-ID: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> #1540: Home/End keys do not work in shell ------------------------------+--------------------------------------------- Reporter: hauser | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- Home and End keys are very useful in shell -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 22:31:14 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 20:31:14 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.a1bbce50589e9d472d518e5c4db2a597@haiku-os.org> #1540: Home/End keys do not work in shell -------------------------------+-------------------------------------------- Reporter: hauser | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by hauser): * type: bug => enhancement -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 22:33:14 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 20:33:14 -0000 Subject: [Haiku-bugs] [Haiku] #1541: Keyboard has too big repeat delay Message-ID: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> #1541: Keyboard has too big repeat delay ------------------------------+--------------------------------------------- Reporter: hauser | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- When you for example try to go to the beginning of a line with arrows (Home button does not work), it takes ages (or at least few seconds). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 22:38:56 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 20:38:56 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension Message-ID: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension ----------------------------+----------------------------------------------- Reporter: hauser | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- Side note: When opening GLDirectMode window with title "OpenGL Tests" is opening. It would be much better if its title would be the same as entry in the menu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 7 23:15:53 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 21:15:53 -0000 Subject: [Haiku-bugs] [Haiku] #1539: strange problem with pipes In-Reply-To: <042.e8ab2f0e15091bb2d7be8041099d9de5@haiku-os.org> References: <042.e8ab2f0e15091bb2d7be8041099d9de5@haiku-os.org> Message-ID: <051.971a3ad8f0db82a717bb0f305c796084@haiku-os.org> #1539: strange problem with pipes ----------------------+----------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All ----------------------+----------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 00:52:10 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 07 Oct 2007 22:52:10 -0000 Subject: [Haiku-bugs] [Haiku] #1539: strange problem with pipes In-Reply-To: <042.e8ab2f0e15091bb2d7be8041099d9de5@haiku-os.org> References: <042.e8ab2f0e15091bb2d7be8041099d9de5@haiku-os.org> Message-ID: <051.2b16d5d54d6079231d091b68da71c14e@haiku-os.org> #1539: strange problem with pipes ----------------------+----------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: fixed | Platform: All ----------------------+----------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r22480. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 03:04:25 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 01:04:25 -0000 Subject: [Haiku-bugs] [Haiku] #1543: Check libroot for Correct Use of errno (easy) Message-ID: <043.4d3b830eb2c70ab953651baa954f5755@haiku-os.org> #1543: Check libroot for Correct Use of errno (easy) -------------------------------+-------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- While BeOS API functions usually return error codes directly, POSIX functions just indicate an error by a special return value (often -1 or a NULL pointer) and set errno to the actual error code. Our libroot code (src/system/libroot, particularly the posix subdirectory) needs to be reviewed in this respect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 08:50:05 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 06:50:05 -0000 Subject: [Haiku-bugs] [Haiku] #1541: Keyboard has too big repeat delay In-Reply-To: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> References: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> Message-ID: <050.4a64daf5c9fd90cec83990665424579b@haiku-os.org> #1541: Keyboard has too big repeat delay -------------------------------+-------------------------------------------- Reporter: hauser | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by jackburton): You can reduce the delay with the "Keyboard" preference application. I think this should be marked as "invalid". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 09:56:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 07:56:24 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.37221168433f063a92c4631188b930fb@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by axeld): * owner: axeld => phoudoin -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 09:57:57 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 07:57:57 -0000 Subject: [Haiku-bugs] [Haiku] #1541: Keyboard has too big repeat delay In-Reply-To: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> References: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> Message-ID: <050.467e7b826bef88167331e97c82714097@haiku-os.org> #1541: Keyboard has too big repeat delay -------------------------------+-------------------------------------------- Reporter: hauser | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => low * type: enhancement => bug Comment: I think the default repeat rate is much too slow, though - so maybe we want to keep this open until we changed that as a reminder :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 09:59:17 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 07:59:17 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.b34348173653f32c926fbd1329cc031f@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by axeld): * owner: stippi => jackburton * type: enhancement => bug * component: - User Interface => - Applications/Terminal * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 11:09:14 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 09:09:14 -0000 Subject: [Haiku-bugs] [Haiku] #1543: Check libroot for Correct Use of errno (easy) In-Reply-To: <043.4d3b830eb2c70ab953651baa954f5755@haiku-os.org> References: <043.4d3b830eb2c70ab953651baa954f5755@haiku-os.org> Message-ID: <052.0cb946badff406a69137016b546bd810@haiku-os.org> #1543: Check libroot for Correct Use of errno (easy) --------------------------------+------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by karma): * cc: karma (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 11:17:26 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 09:17:26 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB In-Reply-To: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> References: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> Message-ID: <059.c94c4d4c3cf79a6e3f907150aa675d12@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by korli): * cc: absabs (added) Comment: These areas seem to be fully used (allocated size is 4kB). The sole optimization to be expected is grouping these areas. This implies their management at the module level. Is it really needed to avoid many single areas ? Is it possible to use resize_area() for the job ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 11:45:25 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 09:45:25 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.e65776a1ee3f9d5cb7a5f0769d42970a@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by pieterpan): I posted a small diff with a possible solution. I can't apply it, maybe someone can review it and apply it. What I also noticed, is that when you zoom the window, FrameResized does not seem to be called, but maybe it has other causes. FrameResized is called when you resize the window... Appserver bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 11:55:59 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 09:55:59 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB In-Reply-To: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> References: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> Message-ID: <059.2418ab1bf8d85869cfb9380cc7c9d39e@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): The address space allocator is pretty bad in Haiku (and BeOS, too) - while this will probably changed at some point in the future, grouping this area to a large one is very beneficial. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 13:45:48 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 11:45:48 -0000 Subject: [Haiku-bugs] [Haiku] #1544: Haiku doesn't detect boot partition on real hardware Message-ID: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> #1544: Haiku doesn't detect boot partition on real hardware -----------------------+---------------------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- I built Haiku rev22448 (compiled on Linux 32bit with gcc 2.95) and tried to run it on real hardware, it boots and shows the Haiku logo but suddenly it goes in KDL with a message like this: PANI: didn't find boot partition I generated the images with jam haiku-vmware-image. Both haiku.image and haiku.vmdk works (tested with qemu-kvm and VMware Server on openSUSE 10.3 32bit). Made the /dev/sda5 partition of type BeOS (tried with 100MB and even up to 500MB), then tried to dd the image: dd if=generated/haiku.image of=/dev/sda5 jam run ":makebootable" /dev/sda5 If I mount /dev/sda5 with the (readonly) BFS file system on Linux I see the Haiku folders and files so it seems that the dd went ok. Grub is configured like this: title Haiku rootnoverify (hd0,1) chainloader (hd0,4)+1 My computer is a AMD 64 x2 with 2GB RAM. Here's my hardware specs: 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE- 1394a-2000 Controller (PHY/Link) 03:08.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Unfortunately I don't have any serial port so I can't send the serial debug output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 15:37:06 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 13:37:06 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.f1ff0f3f401891856fb4b801526c3545@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by jackburton): Looks like TermView forwards those key to bash, so it's bash which doesnt' handle them. A very quick search on the internet resulted in this: in /etc/inputrc: # allow the use of the Home/End keys # "\e[1~": beginning-of-line # "\e[4~": end-of-line Uncomment the two lines and all is well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 15:56:15 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 13:56:15 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Dead keys and inlineinput crash Mail. In-Reply-To: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> References: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> Message-ID: <052.e6d861613cefc8a21f9094432223e76b@haiku-os.org> #1022: Dead keys and inlineinput crash Mail. ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Comment (by kaoutsis): Replying to [comment:10 jackburton]: > Fixed in r22444 thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 16:40:04 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 14:40:04 -0000 Subject: [Haiku-bugs] [Haiku] #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage In-Reply-To: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> References: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> Message-ID: <050.26219fd8ad3ec88036fba3e29c215588@haiku-os.org> #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage -----------------------------------+---------------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by tigerdog): Korli, I can test this any time - the problem is consistent on my machine across R5, BONE and Zeta when using this driver and the Haiku multi-audio driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 16:47:25 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 14:47:25 -0000 Subject: [Haiku-bugs] [Haiku] #1545: kernel dprintf should flush pending repeats every n seconds Message-ID: <040.f24a44f6d741f4165402e6426211bc23@haiku-os.org> #1545: kernel dprintf should flush pending repeats every n seconds ---------------------------+------------------------------------------------ Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ If a message is printed out ie every 100 ms, it won't appear unless a different message is printed out. There should be a time limit for dprintf repeats (from 1 to 5 seconds) to flush a pending repeats message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 14:32:19 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 12:32:19 -0000 Subject: [Haiku-bugs] [Haiku] #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage In-Reply-To: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> References: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> Message-ID: <050.a91ab7053996e5f3162c415683182197@haiku-os.org> #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage -----------------------------------+---------------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 17:58:58 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 15:58:58 -0000 Subject: [Haiku-bugs] [Haiku] #1545: kernel dprintf should flush pending repeats every n seconds In-Reply-To: <040.f24a44f6d741f4165402e6426211bc23@haiku-os.org> References: <040.f24a44f6d741f4165402e6426211bc23@haiku-os.org> Message-ID: <049.dfd43c293f2b773ac1625281d789b2df@haiku-os.org> #1545: kernel dprintf should flush pending repeats every n seconds ----------------------------+----------------------------------------------- Reporter: korli | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: The flushing already works if there are no new messages coming in, but I see what you mean, when they are constantly coming at a high frequency you will not get the periodic flush like under BeOS. I'll take a look at that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 18:08:48 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 16:08:48 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.ad0dfdd09ca3df5817591ed68fdd3140@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by bonefish): That's also in my .inputrc under BeOS. Together with: {{{ DEL: delete-char Control-f kill-word }}} I suppose we should just add an inputrc to the image. Unless someone has a better idea, of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 18:21:26 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 16:21:26 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.998d7fbfe23558e9cb09ab71ec343328@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by axeld): Well, I think the preferred solution would be to have those in the defaults; preferrably hard-coded, but a settings file would do, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 18:39:13 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 16:39:13 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.72e1d755e1be3280bd292c193a9ea7ab@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by axeld): Stefano, would you mind if I look into it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 18:54:22 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 16:54:22 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.9a55ac7bf643c46c833704950dd29c7c@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. --------------------------------------+------------------------------------- Reporter: etteyafed | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by etteyafed): This is a hi res photo of a back-trace after the lock up. http://etteyafed.homeip.net/images/haiku_debug/img-1.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 19:49:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 17:49:24 -0000 Subject: [Haiku-bugs] [Haiku] #1543: Check libroot for Correct Use of errno (easy) In-Reply-To: <043.4d3b830eb2c70ab953651baa954f5755@haiku-os.org> References: <043.4d3b830eb2c70ab953651baa954f5755@haiku-os.org> Message-ID: <052.5f110291bcaae947f3d4dd4c8430bb3e@haiku-os.org> #1543: Check libroot for Correct Use of errno (easy) --------------------------------+------------------------------------------- Reporter: bonefish | Owner: kaoutsis Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by kaoutsis): * owner: axeld => kaoutsis * status: new => assigned Comment: I will give it a try! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 20:34:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 18:34:24 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.4092cb136ba3e7fb96fac0d9987f84e9@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by axeld): I've attached a diff that would fix it within bash. Should I apply it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 20:46:05 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 18:46:05 -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.58d03281203a378121a34b3841d9e65d@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): any hardware specifications ? sound working on other OSes ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 22:27:48 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 20:27:48 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.37e0edcbf9abcc08c67c02517ea78690@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by jackburton): Replying to [comment:6 axeld]: > Stefano, would you mind if I look into it? Please do. But IMHO it would be better if we didn't touch bash code, and just put add an inputrc file to the image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 23:19:21 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 21:19:21 -0000 Subject: [Haiku-bugs] [Haiku] #1540: Home/End keys do not work in shell In-Reply-To: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> References: <041.3fad545243ac27c5aadb431af483aeee@haiku-os.org> Message-ID: <050.f7bb310ee9dfce28afdd856d55062c86@haiku-os.org> #1540: Home/End keys do not work in shell --------------------------------------+------------------------------------- Reporter: hauser | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: - Applications/Terminal | Version: R1 development Resolution: fixed | Platform: x86 --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r22488. Having an inputrc file would benefit other apps, too, but good defaults make even more sense to me (I wouldn't mind having both, though). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 8 23:41:04 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 21:41:04 -0000 Subject: [Haiku-bugs] [Haiku] #1546: AHCI drive not properly recognized Message-ID: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> #1546: AHCI drive not properly recognized --------------------------+------------------------------------------------- Reporter: ddew | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Haiku revision 22394 fails to recognize drives attached to the ICH9 ahci controller. The driver is loaded just fine and the disk appears to show up ok in the /dev tree but running diskinfo on the drive returns incorrect data for it. Attached is the serial output from testing driveinfo on the disk. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 00:02:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 08 Oct 2007 22:02:24 -0000 Subject: [Haiku-bugs] [Haiku] #1546: AHCI drive not properly recognized In-Reply-To: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> References: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> Message-ID: <048.750dcaa03d0a6bb9d0315cdd254419a6@haiku-os.org> #1546: AHCI drive not properly recognized ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by axeld): * owner: axeld => marcusoverhagen -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 03:36:46 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 01:36:46 -0000 Subject: [Haiku-bugs] [Haiku] #1250: hostname not fully implemented In-Reply-To: <048.998f79384d2b85ee25d1982821ad69c0@haiku-os.org> References: <048.998f79384d2b85ee25d1982821ad69c0@haiku-os.org> Message-ID: <057.941a575de774e357982af3736c3f9b21@haiku-os.org> #1250: hostname not fully implemented --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks for your work! It's fixed in r22492. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 03:37:53 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 01:37:53 -0000 Subject: [Haiku-bugs] [Haiku] #1311: [FileTypes] freeze on MediaPlayer start In-Reply-To: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> References: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> Message-ID: <049.b34c7d731e930526491481ed517db3a5@haiku-os.org> #1311: [FileTypes] freeze on MediaPlayer start --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Preferences/FileTypes | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 03:38:15 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 01:38:15 -0000 Subject: [Haiku-bugs] [Haiku] #1309: [app_server] freeze if you start Cortex In-Reply-To: <040.7925cc82c96689fa9699bb6d0181bdb0@haiku-os.org> References: <040.7925cc82c96689fa9699bb6d0181bdb0@haiku-os.org> Message-ID: <049.5161496dd21a6d9715dfc0c6ddeb498b@haiku-os.org> #1309: [app_server] freeze if you start Cortex ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 03:38:26 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 01:38:26 -0000 Subject: [Haiku-bugs] [Haiku] #1301: OS becoming slow In-Reply-To: <040.92b9f8ba7ac3f9f024df6f0530f6499e@haiku-os.org> References: <040.92b9f8ba7ac3f9f024df6f0530f6499e@haiku-os.org> Message-ID: <049.93e8dd6ee1232d2ea918d8b3146c1e91@haiku-os.org> #1301: OS becoming slow ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 03:40:35 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 01:40:35 -0000 Subject: [Haiku-bugs] [Haiku] #1329: Crashed BMenu (Deskbar/ProcessController's) covers Team Monitor and Debugger BAlerts In-Reply-To: <048.562604cc5df941ffcced4f74c9bbbf5d@haiku-os.org> References: <048.562604cc5df941ffcced4f74c9bbbf5d@haiku-os.org> Message-ID: <057.119f978f5a1226ae48a0d647613487ca@haiku-os.org> #1329: Crashed BMenu (Deskbar/ProcessController's) covers Team Monitor and Debugger BAlerts ---------------------------------+------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: This is a duplicate of bug #1152. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 04:06:38 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 02:06:38 -0000 Subject: [Haiku-bugs] [Haiku] #1421: Exiting KDL leaves KDL image on the screen In-Reply-To: <042.c1add564721e110ac7e93a5c5c023e8b@haiku-os.org> References: <042.c1add564721e110ac7e93a5c5c023e8b@haiku-os.org> Message-ID: <051.1136c9cda2de3363861ae70089e2263e@haiku-os.org> #1421: Exiting KDL leaves KDL image on the screen --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: As an end user, you are not expected to see this, anyway, ever - some day :-) It would require some work to be able to refresh the screen, and I just don't think it's worth it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 04:08:07 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 02:08:07 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.7bf2075d96ef47808e14cf39451abe41@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 04:08:31 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 02:08:31 -0000 Subject: [Haiku-bugs] [Haiku] #1538: Page fault during installing perl from sources In-Reply-To: <042.0dde8fab91dee81d44fdc12b6183f486@haiku-os.org> References: <042.0dde8fab91dee81d44fdc12b6183f486@haiku-os.org> Message-ID: <051.66b60cc91c9de01afdfb9cb83ff545d6@haiku-os.org> #1538: Page fault during installing perl from sources ----------------------+----------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System | Version: R1 development Resolution: | Platform: All ----------------------+----------------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 06:59:36 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 04:59:36 -0000 Subject: [Haiku-bugs] [Haiku] #1546: AHCI drive not properly recognized In-Reply-To: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> References: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> Message-ID: <048.582f55e0286b55086289ae25f6a19792@haiku-os.org> #1546: AHCI drive not properly recognized ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * status: new => assigned Comment: We do not have a diskinfo application in Haiku. Where can I find it, and what does it report? The drive itself seems to be recognized, it has 250GB capacity and 3 partitions: 74 ahci: AHCIPort::ScsiInquiry port 4 75 ahci: model number: ST3250824AS 76 ahci: serial number: 5ND2K1X1 77 ahci: firmware rev.: 3.AAE 78 ahci: lba 1, lba48 1, fUse48BitCommands 1, sectors 268435455, sectors48 488395055, size 250058268160 887 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4) 888 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4/0) 889 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4/0/0) 890 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4/0/1) 891 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4/0/2) 892 KDiskDeviceManager::_Scan(/dev/disk/scsi/0/4/0/raw) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 07:12:22 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 05:12:22 -0000 Subject: [Haiku-bugs] [Haiku] #1546: AHCI drive not properly recognized In-Reply-To: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> References: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> Message-ID: <048.eb9a04a6dff5d6f2f44c8bdae0844173@haiku-os.org> #1546: AHCI drive not properly recognized ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by umccullough): FWIW, I had problems also using an ICH9-based board... but I was using a 500gb disk in mine, and the Haiku partition was way out near the end... Haiku can successfully boot from a partition residing beyond 137gb right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 07:20:49 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 05:20:49 -0000 Subject: [Haiku-bugs] [Haiku] #1541: Keyboard has too big repeat delay In-Reply-To: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> References: <041.173a62088f03138a1fcf89c06e7660eb@haiku-os.org> Message-ID: <050.78c60d9c4c16be9c67e8a6b5a6a14100@haiku-os.org> #1541: Keyboard has too big repeat delay -------------------------------+-------------------------------------------- Reporter: hauser | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by marcusoverhagen): * cc: marcusoverhagen (added) Comment: I don't know if this "bug" describes USB or PS/2 keyboards. We have to keep in mind that some people might need long delays and low repeat rates in order to use the keybaord at all. The PS/2 driver is using the PS/2 keyboard reset standard settings, that also BeOS R5 used. That is delay = 0x01 (500 ms), rate = 0x0b (10.9 chr/sec). Of cause you can overrule this with the Keyboard preferences. While I use the fastest settings myself, I think we should keep the defaults slow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 07:32:26 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 05:32:26 -0000 Subject: [Haiku-bugs] [Haiku] #1546: AHCI drive not properly recognized In-Reply-To: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> References: <039.d77885971072c32580417a8c1e97cad1@haiku-os.org> Message-ID: <048.658c5a6f8178c64001f735f9e147b42b@haiku-os.org> #1546: AHCI drive not properly recognized ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by ddew): My bad, it was driveinfo or something to that effect. The disk in the log is fine but it won't show any partitions in tracker and the info I got from the terminal about it showed garbage for name, model and about 950mb as size. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 10:36:42 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 08:36:42 -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.a94741dc935414f185e0c84ddfe27b8b@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by atomozero): works on windows and linux if i dellete the driver it works whit OpenSound System the system is a centrino laptop Asus M2400N -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 12:07:37 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 10:07:37 -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.0e26397c09687002fc0bfe428bda5a00@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try to change in src/add- ons/kernel/drivers/audio/ac97/auich/io.c ? auich_codec_wait(): snooze(1) => snooze(10) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 12:19:21 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 10:19:21 -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.fbb7294aa002e1bb463904b9451c05cc@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try to change in src/add- ons/kernel/drivers/audio/ac97/auich/auich.c ? auich_setup() cmd | PCI_command_io => cmd | PCI_command_memory -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 15:01:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 13:01:19 -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.fb6997b189e51f74834dbc866979acfd@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by marcusoverhagen): ICH4 needs memory mapped io, and everything earlier uses port io -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 16:48:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 14:48:59 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.61bb4b9a4a1fe4d60e5db8d190aebfac@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. --------------------------------------+------------------------------------- Reporter: etteyafed | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by etteyafed): Another strange issue: If I try and boot normally I get a vm_page_fault. If I enable failsafe video mode this won't happen. This is not the same as the lock up described but may be related. Disabling IDE DMA also causes this to go away (this is the only way I can boot with the regular nvidia driver). I don't know what disabling the nvidia driver and disabling IDE DMA have in common but they both prevent this vm_page_fault. They don't both need to be enabled, just one or the other. Here is a link to the ri res photo of the page_fault: http://etteyafed.homeip.net/images/haiku_debug/img-2.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 20:40:54 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 18:40:54 -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.504dd417b90081acdaf364ea24b1a413@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by atomozero): i cant test :(( whit last version i cant boot :( PANIC: wm_page_fault:unhadled page fault in kernel space at 0x91bc48b, ip 0x800a4f63 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 20:46:16 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 18:46:16 -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.392a532538739c79877c3096183b2976@haiku-os.org> #1217: AUICH looping media_server ----------------------------+----------------------------------------------- Reporter: atomozero | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): then update to a working revision ... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 20:56:44 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 18:56:44 -0000 Subject: [Haiku-bugs] [Haiku] #1547: Panic in vfs_mount_boot_file_system() Message-ID: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> #1547: Panic in vfs_mount_boot_file_system() ---------------------------+------------------------------------------------ Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ KDiskSystem::Unload(): partitioning_systems/session/v1 -> 0 KDiskDeviceManager::_AddDiskSystem() done: No error file system: file_systems/cdda/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/cdda/v1) KDiskSystem::Load(): file_systems/cdda/v1 -> 1 KDiskSystem::Unload(): file_systems/cdda/v1 -> 0 KDiskDeviceManager::_AddDiskSystem() done: No error vm_soft_fault: va 0xe182f320 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xe182f320, ip 0x800a2a33, write 0, user 0, thread 0x8 PANIC: vm_page_fault: unhandled page fault in kernel space at 0xe182f320, ip 0x800a2a33 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x8 "main2" kernel stack: 0x800fa000 to 0x800fe000 frame caller :function + offset 800fd828 (+ 52) 8008c1eb :invoke_command + 0x0073 800fd85c (+ 48) 8008c332 :kernel_debugger_loop + 0x0102 800fd88c (+ 32) 8008cd8e :kernel_debugger + 0x00b6 800fd8ac (+ 192) 8008cccd :panic + 0x0029 800fd96c (+ 64) 8005d936 :vm_page_fault + 0x00a6 800fd9ac (+ 176) 800955ca :i386_handle_trap + 0x023a iframe at 0x800fda64 (end = 0x800fdab8) eax 0xe182f320 ebx 0xc ecx 0x90a2b850 edx 0x90a3c200 esi 0x800fdb48 edi 0x90a2e01e ebp 0x800fdac8 esp 0x800fda94 eip 0x800a2a33 eflags 0x210206 vector: 0xe, error code: 0x0 800fda5c (+ 108) 800a2a33 :strncmp + 0x0023 800fdac8 (+ 144) 8002ff75 :iterator_get_next_module__FP15module_iteratorPcPUl + 0x0439 800fdb58 (+ 64) 800306e4 :read_next_module_name + 0x0044 800fdb98 (+ 64) 8007b558 :_RescanDiskSystems__Q38BPrivate10DiskDevice18KDiskDeviceManagerb + 0x0064 800fdbd8 (+ 64) 8007b66c :RescanDiskSystems__Q38BPrivate10DiskDevice18KDiskDeviceManager + 0x0028 800fdc18 (+ 816) 8005553a :vfs_mount_boot_file_system + 0x018a 800fdf48 (+ 144) 8002f255 :main2 + 0x00d1 800fdfd8 (+ 32) 8003de57 :_create_kernel_thread_kentry__Fv + 0x001b 800fdff8 (+2146443272) 8003ddec :thread_kthread_exit__Fv + 0x0000 kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 20:57:03 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 18:57:03 -0000 Subject: [Haiku-bugs] [Haiku] #1547: Panic in vfs_mount_boot_file_system() In-Reply-To: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> References: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> Message-ID: <049.e135d8c3962234f01ce3ef3415a995ce@haiku-os.org> #1547: Panic in vfs_mount_boot_file_system() ----------------------------+----------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * cc: bonefish (added) * priority: normal => critical -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 21:13:37 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 19:13:37 -0000 Subject: [Haiku-bugs] [Haiku] #1548: Error in example code for BLocker in the Haiku Book Message-ID: <042.6bd369ca8ce661e79839e0bd3ac022d2@haiku-os.org> #1548: Error in example code for BLocker in the Haiku Book ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: nielx Type: bug | Status: new Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ http://factory.haiku- os.org/documentation/Haiku_Book_doxygen/html/classBLocker.html Typo, example code should be length not lenght in the example code: fLength += lenght; -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 22:03:52 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 20:03:52 -0000 Subject: [Haiku-bugs] [Haiku] #1549: crash in expr (btowc in libroot) Message-ID: <042.be6c2cb9518bf6d236ef9eddb8328eb6@haiku-os.org> #1549: crash in expr (btowc in libroot) -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Try this: {{{ expr "7" : "[0-9]" }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 22:10:40 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 20:10:40 -0000 Subject: [Haiku-bugs] [Haiku] #1547: Panic in vfs_mount_boot_file_system() In-Reply-To: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> References: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> Message-ID: <049.c0e9515ce3068c4ab3e8492bc71a5259@haiku-os.org> #1547: Panic in vfs_mount_boot_file_system() ----------------------------+----------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by mmlr): I had the exact same thing over here. Traced it down to the leftover "dos" filesystem add-on if you update an existing installation. If you remove "/boot/beos/system/add-ons/kernel/filesystems/dos" booting works as usual. But obviously it'd be nice if the crash could be avoided. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 22:31:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 20:31:12 -0000 Subject: [Haiku-bugs] [Haiku] #1547: Panic in vfs_mount_boot_file_system() In-Reply-To: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> References: <040.42b45a95307af4a68cfbacf5d4353184@haiku-os.org> Message-ID: <049.a2366c407d583309f01072edd3afe1ff@haiku-os.org> #1547: Panic in vfs_mount_boot_file_system() ----------------------------+----------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): It's not really possible to avoid crashing in this situation. The FS and partitioning system module API changed and since we don't want to increment the interface version number with every change during development, the kernel has no way of knowing that a module is obsolete. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 9 22:33:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 20:33:59 -0000 Subject: [Haiku-bugs] [Haiku] #1549: crash in expr (btowc in libroot) In-Reply-To: <042.be6c2cb9518bf6d236ef9eddb8328eb6@haiku-os.org> References: <042.be6c2cb9518bf6d236ef9eddb8328eb6@haiku-os.org> Message-ID: <051.b7b09a9fc248cc52ef586a2de7dc6640@haiku-os.org> #1549: crash in expr (btowc in libroot) --------------------------------+------------------------------------------- Reporter: kaliber | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by axeld): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 10 00:56:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 09 Oct 2007 22:56:12 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.9c4eb3352ad7f5449180445116c1d134@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. --------------------------------------+------------------------------------- Reporter: etteyafed | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by scottmc): For attaching photos to bug reports you should upload them using trac rather than hosting them offsite, just use the attach file button. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 10 03:39:56 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 10 Oct 2007 01:39:56 -0000 Subject: [Haiku-bugs] [Haiku] #1550: Tracker crashes when clicking on column heading in Mail inbox folder Message-ID: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> #1550: Tracker crashes when clicking on column heading in Mail inbox folder ------------------------------------+--------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- Tracker crashed when I tried to read the Mail inbox messages. 1)Right click on the Deskbar Mail icon. 2)Click on the # new messages. 3)Cliick Tracker column heading like; any column heading. If opened from the navigating to inbox from /home/Mail/inbox, then click on any column heading except; name and status in this case. Result is Tracker crashes. Reproduceable always. I was testing with r22494 on its own partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 10 22:49:13 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 10 Oct 2007 20:49:13 -0000 Subject: [Haiku-bugs] [Haiku] #1545: kernel dprintf should flush pending repeats every n seconds In-Reply-To: <040.f24a44f6d741f4165402e6426211bc23@haiku-os.org> References: <040.f24a44f6d741f4165402e6426211bc23@haiku-os.org> Message-ID: <049.01d0315ed4ec10654befa4047b050220@haiku-os.org> #1545: kernel dprintf should flush pending repeats every n seconds ----------------------------+----------------------------------------------- Reporter: korli | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Implemented in r22501. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 14:36:15 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 12:36:15 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.97f1ee8596b324f43660210c932023a5@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: low | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:17 marcusoverhagen]: > perhaps using strace will show where it is stuck during that half second Looks like what it's taking so much it's the BBitmap::ImportBits() calls in BMenuItem::_DrawShortcutSymbol(). I tried to uncomment those calls and the menu showed up instantly. Note that Drawing the bitmap themselves doesn't take so much time, instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 14:55:02 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 12:55:02 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.97eee9ad59852ca5b01ce6fcb6c317cf@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: low | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:18 jackburton]: > Looks like what it's taking so much it's the BBitmap::ImportBits() calls in BMenuItem::_DrawShortcutSymbol(). I tried to uncomment those calls and the menu showed up instantly. Note that Drawing the bitmap themselves doesn't take so much time, instead. And, I tracked it down further, and found out which it's the building of the color list inside PaletteConverter::SetTo() call, called because the MenuItems's Bitmaps are CMAP8, so they need a palette to be converted. Note that there's already a TODO Item in there. Maybe we should find a way to use the palette supplied by the app_server (already generated at startup), for bitmaps which have a connection with the app_server. Might not be trivial to be able to differentiate between the two, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 15:24:26 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 13:24:26 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.c4178355df0d5438b7ed4a9480c0414e@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: assigned Priority: low | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by jackburton): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 15:32:43 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 13:32:43 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.1faf5cc1d8469121079f7cafa4e1f200@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by jackburton): * status: assigned => closed * resolution: => fixed Comment: It's fixed in r22508. Now BApplications which have a connection to the app_server (all, except BServers) initialize the PaletteConverter on construction, using system_colors(), which uses the app_server's colormap, thus we avoid the loop which builds the colors, and avoid storing an extra colormap. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 15:46:09 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 13:46:09 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.e49f5f97cc8541bd580839e6944e901f@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): I don't think sharing the palette data even for apps without an app server connection should be all that big of a problem. The app server could put it into a separate area that could be cloned (read-only) by clients, regardless of whether they have a app server connection or not. Regarding the algorithm computing the index mapping: It's absolutely brute force. I didn't think that it would survive for such a long time, when I wrote it. It could be replaced by something more intelligent. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 15:50:10 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 13:50:10 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.ea03ba699133bdb04a77e990f97b87e1@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:22 bonefish]: > I don't think sharing the palette data even for apps without an app server connection should be all that big of a problem. The app server could put it into a separate area that could be cloned (read-only) by clients, regardless of whether they have a app server connection or not. Note, though, that that code is also used by the app_server, and that one can't obviously use BScreen::ColorMap() to get the palette (it would deadlock). > Regarding the algorithm computing the index mapping: It's absolutely brute force. I didn't think that it would survive for such a long time, when I wrote it. It could be replaced by something more intelligent. BTW I copied the same code to generate the palette within the app_server, so remember to change it there too :P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 19:30:26 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 17:30:26 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot Message-ID: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> #1551: r22509: no boot -----------------------+---------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Haiku r22509 (installed on a partition) opens up in the boot loader without bootvolume ('none' selected). When selecting 'Haiku' and 'continue booting' the selected 'Haiku' changes to 'none' again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 19:37:06 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 17:37:06 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot In-Reply-To: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> References: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> Message-ID: <053.87ca540e25154651b85c9baaa29b4728@haiku-os.org> #1551: r22509: no boot ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Initially, the last line is #255; after 'continu booting' the two final lines get written. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 19:38:52 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 17:38:52 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot In-Reply-To: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> References: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> Message-ID: <053.a319bc78741940456dae92147196d3c5@haiku-os.org> #1551: r22509: no boot ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Replying to [comment:1 meanwhile]: > Initially, the last line is #255; after 'continu booting' the two final lines get written. (Excuse me, meant was 'plain' 255) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 21:14:34 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 19:14:34 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot In-Reply-To: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> References: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> Message-ID: <053.c5c69a1eb3aa9c158b40044a72628c1e@haiku-os.org> #1551: r22509: no boot ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): The boot loader recognized 3 primary partitions and one extended partition containing 4 logical ones. The last logical partition, which is recognized as located at offset 6.57 GB with size 2.79 GB, is the boot partition. Apparently the boot loader fails to load the kernel from it. Is this the right partition? Can you check whether the kernel is properly installed and has the correct contents? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 21:49:58 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 19:49:58 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.c40a7511dbe980ba5448738541b3e394@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): Replying to [comment:23 jackburton]: > Replying to [comment:22 bonefish]: > > I don't think sharing the palette data even for apps without an app server connection should be all that big of a problem. The app server could put it into a separate area that could be cloned (read-only) by clients, regardless of whether they have a app server connection or not. > > Note, though, that that code is also used by the app_server, and that one can't obviously use BScreen::ColorMap() to get the palette (it would deadlock). That depends on the implementation of BScreen::ColorMap(), and as I wrote, I wouldn't use an app server connection at all (sending 32 KB through a port doesn't sound that nice anyway). The app server would do a manual initialization, everyone else would clone the app server's area lazily. The code for the app server's manual initialization could be reused as a fallback in clients (i.e. for the unlikely case that there's no app server). > > Regarding the algorithm computing the index mapping: It's absolutely brute force. I didn't think that it would survive for such a long time, when I wrote it. It could be replaced by something more intelligent. > > BTW I copied the same code to generate the palette within the app_server, so remember to change it there too :P Don't worry, I'm not going to change anything in this area anytime soon. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 22:03:33 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 20:03:33 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot In-Reply-To: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> References: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> Message-ID: <053.9077e907fad9a8ec49f279197ce339dc@haiku-os.org> #1551: r22509: no boot ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Something must have happened when using the CreateDeviceImage app the other day...I don't remember having that many partitions before. Anyhow, the good news is that I successfully re-copied everything from the mounted r25509 image again into the earlier Haiku install that wouldn't boot, this time with good result. Sorry for the hassle: this "bug" can now be marked invalid or solved (whichever applies). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 11 22:37:34 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 11 Oct 2007 20:37:34 -0000 Subject: [Haiku-bugs] [Haiku] #1551: r22509: no boot In-Reply-To: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> References: <044.a5242a887ac872a266a8ef8355e2cf0b@haiku-os.org> Message-ID: <053.3395097fad00a34cfd2eef1294fdf8c3@haiku-os.org> #1551: r22509: no boot ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 09:59:06 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 07:59:06 -0000 Subject: [Haiku-bugs] [Haiku] #1288: StyledEdit does not print when there is only one line of text In-Reply-To: <044.0880b7c01fcf05a6a1607f433df9f5ae@haiku-os.org> References: <044.0880b7c01fcf05a6a1607f433df9f5ae@haiku-os.org> Message-ID: <053.99c6dc1c13108ff7c9e370f384565d70@haiku-os.org> #1288: StyledEdit does not print when there is only one line of text ----------------------------------------+----------------------------------- Reporter: bnickname | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: - Applications/StyledEdit | Version: R1 development Resolution: fixed | Platform: All ----------------------------------------+----------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Replying to [comment:3 jackburton]: Fixed in r22511. Printing in StyledEdit is still very much broken though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 11:45:08 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 09:45:08 -0000 Subject: [Haiku-bugs] [Haiku] #1340: Terminal doesn't produce the EOF character on Ctrl-D In-Reply-To: <043.762cdc0ace9c1913e2eb184616685587@haiku-os.org> References: <043.762cdc0ace9c1913e2eb184616685587@haiku-os.org> Message-ID: <052.693a53689e9dcbc899f01d3b9a3fc7c9@haiku-os.org> #1340: Terminal doesn't produce the EOF character on Ctrl-D --------------------------------------+------------------------------------- Reporter: bonefish | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Terminal | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by jackburton): * status: assigned => closed * resolution: => fixed Comment: Original bug is fixed, and in r22512 I also check against "raw_char" instead of using "key". Seems to work fine. Closing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 12:17:39 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 10:17:39 -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.6a293ca2156a523b85331866c30edae1@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: There was indeed a deadlock in the EventFilter for keyboard events, I changed that recently to process the workspace switch event in the Desktop thread, so it should be fixed for good. The event filter tried to lock the desktop to switch workspaces, but the desktop could already be locked itself and trying to grab the event dispatcher lock... deadlock. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 12:23:47 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 10:23:47 -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.4c119c14db002fb4359b113d24f9f8da@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: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => assigned Comment: No, this was there all the time. Weird thing is that it sometimes works. I will figure it out eventually. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 16:02:34 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 14:02: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.2b54b21a54d4123d0eb0fc58353e5b9d@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: | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): Ok, so here's what I've noticed on my PC at least. Click and then drag the selection box down and to the right, I get vertical AND horizontal ghosting lines. Down and left I get only horizontal lines, up and right I get only vertical lines. And finally if I go up and left I get NO ghosting lines at all. I've not sure if this is only the case on my system or if this happens everwhere. This is on a Radeon 9600 mobility. So if it is this way for everyone then it might be related to fractional errors where you are off by .1 when erasing the lines? And it's not seen when subracting from bottom/right but is from the top/left. Anyways some clues to check into it with. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 16:53:04 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 14:53:04 -0000 Subject: [Haiku-bugs] [Haiku] #1544: Haiku doesn't detect boot partition on real hardware In-Reply-To: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> References: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> Message-ID: <053.7e496b3ca6825bee5a1bbb3c1c9c413e@haiku-os.org> #1544: Haiku doesn't detect boot partition on real hardware ------------------------+--------------------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by marcusoverhagen): try: rootnoverify (hd0,4) chainloader +1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 17:30:21 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 15:30:21 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 Message-ID: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Blender seems to start up and switch to a dark black full screen under Haiku but then crashes. Seems to be related to Mesa. I've attached the debugging info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 17:35:46 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 15:35:46 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. Message-ID: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> #1553: Metos crashing.. ----------------------------------+----------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- This might have to do with the last bug I filed for Blender. In particular, I see an error [tcsetpgrp failed in terminal_inferior: Invalid arguement]? Although it shows a bug in the app server I believe. Screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 17:40:15 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 15:40:15 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.6bc2f80376a28c93b06bd7d1d995f354@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): The Blender bug I'm referring to is here: [http://dev.haiku-os.org/ticket/1552] Blender is here: [http://bebits.com/app/61] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 17:42:02 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 15:42:02 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.4a763901259dc8e23f7c7a772b1a0135@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): Sorry, meant to add the Metos location here not blender: [http://bebits.com/app/3066] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 17:43:28 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 15:43:28 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.a4f242eb1a484cbb756c926b633e59c4@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): Looks like a dup of bug #195. But at least this crash is reproducible now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 18:22:57 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 16:22:57 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.4e165bedd8d8db53444cbe99b533e54f@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by bonefish): It would help tremendously to get a back trace (type "bt" in gdb). The "tcsetpgrp failed..." output is unrelated. It's an unimplemented feature in our gdb port and you'll see it on every crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 18:28:19 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 16:28:19 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.2360b98072d5e8b318aeca93ad166c2c@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): Ok thanks for that info.. hmm no way to attach additional files with this system? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 18:34:45 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 16:34:45 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.e4afaf557aac07f2d01105b43d1206a5@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): Here we go: [http://www.haikuware.com/images/stories/news/bugs/bt-from-metos.jpg] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 18:48:18 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 16:48:18 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.526d309a651a831645845263f2e94f1d@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by bonefish): Replying to [comment:5 kvdman]: > Ok thanks for that info.. hmm no way to attach additional files with this system? I would try the "Attach File" button in the "Attachments" section. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 19:26:02 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 17:26:02 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.cde9daa25532eab2b725789e5e09c874@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): Haha, I see it now! Thanks. Hope the info is useful, bye! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 19:31:38 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 17:31:38 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.aeaa57740e7846841f72c0c4cf8a0579@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jonas.kirilla): See #195, #266 and #1166. (MetOS, Cortex, ArtPaint, FontDemo, ... all palette window related?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 19:41:38 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 17:41:38 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.02057bb4f2d75c4378c20fd902b0a641@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): Hi Jonas, I've tested ArtPaint and FontDemo as you mention on rev22490, and they run fine and don't give the same error or any error. Cortex will lock my system, but I think this is a known bug. Metos will actually go directly to gdb. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 19:56:45 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 17:56:45 -0000 Subject: [Haiku-bugs] [Haiku] #1178: NetworkStatus replicant does not persist In-Reply-To: <039.31c4074f057b5a2a5fbe7c8ef923f985@haiku-os.org> References: <039.31c4074f057b5a2a5fbe7c8ef923f985@haiku-os.org> Message-ID: <048.000533ff37a2f57c5c1098e4c54cb1c9@haiku-os.org> #1178: NetworkStatus replicant does not persist -------------------------------+-------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by kvdman): * status: closed => reopened * resolution: fixed => Comment: Tested in 22490. The deskbar won't remember the replicants. Tried the network status app, and also the volume control from the media preferences 'show volume control in the deskbar'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 20:30:39 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 18:30:39 -0000 Subject: [Haiku-bugs] [Haiku] #1554: Clock demo app doesn't show the clock face or replicant grabber Message-ID: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> #1554: Clock demo app doesn't show the clock face or replicant grabber ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- r22510 Clock app does not show the clock face or replicant grabber. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 21:32:54 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 19:32:54 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.4d8c258da87fefd21448287f3f1c90af@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): backtrace ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 21:37:51 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 19:37:51 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.82e56f442a942dc8ff3ab1df80c8f566@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): Hi, This doesn't kill Haiku, but just Blender just crashes and gives the option of debugging, which is what I posted in the screenshot. I'm not sure how to do a backtrace in this case, or if you can? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 22:51:24 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 20:51:24 -0000 Subject: [Haiku-bugs] [Haiku] #1555: [Deskbar] crash in DeleteMenuWindow Message-ID: <040.7ec4d49a1f0249dde547e9386c4b4eb6@haiku-os.org> #1555: [Deskbar] crash in DeleteMenuWindow ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Deskbar | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- {{{vm_soft_fault: va 0xa5 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xa5, ip 0x360cb3, write 0, user 1, thread 0x1ad vm_page_fault: sending team "/boot/beos/system/Deskbar" 0x49 SIGSEGV, ip 0x360cb3 ("libbe.so_seg0ro" +0x115cb3) stack trace: 0x003632ea (libbe.so_seg0ro + 0x1182ea) 0x00362ccd (libbe.so_seg0ro + 0x117ccd) 0x006c4ad0 (libroot.so_seg0ro + 0x20ad0) 0x7003ffec (menu_tracking_1ad_stack + 0x3ffec) 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 0x8009b92c, write 0, user 0, thread 0x1ad debug_server: Thread 429 entered the debugger: Segment violation stack trace, current PC 0x360cb3 _DeleteMenuWindow__5BMenu + 0x3b: (0x7003fedc) 0x3632ea Track__8BMenuBarPllb + 0x59a (0x7003ff4c) 0x362ccd TrackTask__8BMenuBarPv + 0x7d (0x7003ffac) 0x6c4ad0 _get_next_team_info + 0x5c (closest symbol) }}} Found with r22510 in vmware. Don't know how to reproduce it yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 22:55:25 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 20:55:25 -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.f729e64d52f6f8cc6aae635b1ef84eb9@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: I could still deadlock it with r22510 under vmware, reopening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 23:01:39 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 21:01:39 -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.281f7228c4bf05694c6d8c0d3efbdc77@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Oh and strange thing is that Time & Date preflet still running, but i can't move any window and interface is not responding at all, but clock arrows are still moving. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 23:34:57 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 21:34:57 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.cd0114942164f3761fff3cc81267138f@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jonas.kirilla): The app_server does crash, even on a current release, if you launch like 7 copies of FontDemo simultaneously. I haven't used Metos myself, but perhaps Metos makes use of multiple floating palette windows, ending in the same result. I don't know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 23:42:15 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 21:42:15 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.1bcb5cc3cc17582d627f7d0bc8ec63d8@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by kvdman): I've tried to reproduce the FontDemo app crashing by opening up 7 copies, but was unable to... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 12 23:49:21 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 12 Oct 2007 21:49:21 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.b1a0b41dc99ebdc2cf95fadde91b6372@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jonas.kirilla): I'm sorry, kvdman. I assumed you had not tried copies. My apologies. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 03:11:29 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 01:11:29 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.c36d328d00404e284f1c61b0b67a0129@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by umccullough): Once in GDB - you should be able to use the "bt" command to run a backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 05:10:53 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 03:10:53 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.c6415342a233f4c5e2dceca27ff0008e@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): Hi, the problem is, it doesn't go into gdb. it just crashes and gives an option to debug. i guess gdb only gets invoked when haiku completely crashes (which it doesn't in this case); with the bug i just filed for metos (1553) haiku does crash and then i could do the backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 11:19:02 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 09:19:02 -0000 Subject: [Haiku-bugs] [Haiku] #1556: typo in pthread.h Message-ID: <042.59ee0934c37944fbce741e5e8e285dd4@haiku-os.org> #1556: typo in pthread.h ---------------------+------------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: All | ---------------------+------------------------------------------------------ Patch in attachment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 12:07:24 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 10:07:24 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.d6ea695b09804e9ba6a1a72f31c79029@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by stippi): When you actually click on the "option to debug", that's when you will get a Terminal with gdb to debug the program. In that Terminal, type "bt". GDB is presented in two ways, the normal way is the Terminal thing I just described, but for vital system servers (like the app_server or the input_server), GDB is run in that weird full screen mode. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 12:13:10 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 10:13:10 -0000 Subject: [Haiku-bugs] [Haiku] #1554: Clock demo app doesn't show the clock face or replicant grabber In-Reply-To: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> References: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> Message-ID: <051.da86c7a6f94f2755fd9c09214699f789@haiku-os.org> #1554: Clock demo app doesn't show the clock face or replicant grabber -----------------------------+---------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by meanwhile): Error message upon closing Clock (plus option to Debug; see attachment) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 12:47:51 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 10:47:51 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.047a6e8fd50588fa6bb9533f2c800485@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): I tried installing blender2.11-beos-5.0-i386.zip. It seems to depend on python. Which package should I use ? Please provide a stacktrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 12:52:35 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 10:52:35 -0000 Subject: [Haiku-bugs] [Haiku] #1544: Haiku doesn't detect boot partition on real hardware In-Reply-To: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> References: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> Message-ID: <053.76cd7d769b8da3368be9175baadc6576@haiku-os.org> #1544: Haiku doesn't detect boot partition on real hardware ------------------------+--------------------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by plfiorini): I tried now with r22527 and it boots. It wasn't a grub configuration problem because I tried your suggestion and it's the same. Maybe the recent partition changes made it working for me? Anyway now I have a completely different problem: frequency out of range, I'll open an issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 13:00:50 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 11:00:50 -0000 Subject: [Haiku-bugs] [Haiku] #1557: Frequency out of range Message-ID: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> #1557: Frequency out of range -------------------------------------+-------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Booting Haiku r22527 my screen becomes black after the Haiku splash screen and the monitor says the frequency is out range and I can't see anything. Hardware: AMD 64 x2 with 2GB RAM Here's lspci output: 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV 6150 (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE- 1394a-2000 Controller (PHY/Link) 03:08.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 13:24:33 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 11:24:33 -0000 Subject: [Haiku-bugs] [Haiku] #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have Message-ID: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- Extra attributes box in FileTypes have scrollbar even if no attribute exist. In the same time File recognition bpx doesn't habe this problem. To reproduce: * Launch FileTypes * Expand application list * Select Person * Select PDF document -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 13:25:52 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 11:25:52 -0000 Subject: [Haiku-bugs] [Haiku] #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have In-Reply-To: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> References: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> Message-ID: <049.ef3de8e1f65c368898e81f640c3077ee@haiku-os.org> #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Please ignore: "In the same time File recognition bpx doesn't habe this problem." I found a real problem after i wrote it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 13:34:53 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 11:34:53 -0000 Subject: [Haiku-bugs] [Haiku] #254: Wrongly enabled buttons in apps/prefs (easy) In-Reply-To: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> References: <040.d8c8cd1d285f2b0573c32a8a664894eb@haiku-os.org> Message-ID: <049.540c04728025b934e49dc4f48ce42ee9@haiku-os.org> #254: Wrongly enabled buttons in apps/prefs (easy) -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: low | Milestone: R1 Component: - Applications | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by diver): I found some problems: Menu: Selecting "Ctrl as Shortcut key" and back doesn't disable Revert button. Tracker preferences: Selecting "Show Volumes on Desktop" (which is default) enables Default button. This could be seen only once, to reproduce you have to reboot. And Background have Revert and Apply enabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 13:41:59 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 11:41:59 -0000 Subject: [Haiku-bugs] [Haiku] #1559: [Tracker] shifted volume icon Message-ID: <040.150d6e4e1058ad48cbfa7dc563379d69@haiku-os.org> #1559: [Tracker] shifted volume icon ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- If you change in Tracker preferences "Show Volume on Desktop" option to "Show Disks icon" and then press Defaults button Disks icon will disappear, but Haiku volume icon will not be moved back to the first position and will stay fourth instead. Please try several times to reproduce, as this sometimes work as intendent. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:00:49 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:00:49 -0000 Subject: [Haiku-bugs] [Haiku] #885: [app_server] deadlock on font change In-Reply-To: <040.b760b44f133d8b2ef5e9d9081757da9e@haiku-os.org> References: <040.b760b44f133d8b2ef5e9d9081757da9e@haiku-os.org> Message-ID: <049.c2be8d083cc1263f2822cb9c0e9750c2@haiku-os.org> #885: [app_server] deadlock on font change ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: Happens again 2 times in r22510, reopening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:10:23 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:10:23 -0000 Subject: [Haiku-bugs] [Haiku] #885: [app_server] deadlock on font change In-Reply-To: <040.b760b44f133d8b2ef5e9d9081757da9e@haiku-os.org> References: <040.b760b44f133d8b2ef5e9d9081757da9e@haiku-os.org> Message-ID: <049.c785f84e46027cc8b42265156d32caae@haiku-os.org> #885: [app_server] deadlock on font change ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): I could reproduce this deadlock by changing Bold Font 2-20 times. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:27:51 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:27:51 -0000 Subject: [Haiku-bugs] [Haiku] #1549: crash in expr (btowc in libroot) In-Reply-To: <042.be6c2cb9518bf6d236ef9eddb8328eb6@haiku-os.org> References: <042.be6c2cb9518bf6d236ef9eddb8328eb6@haiku-os.org> Message-ID: <051.dbdfd28f61557d694ceb452901b3d28b@haiku-os.org> #1549: crash in expr (btowc in libroot) --------------------------------+------------------------------------------- Reporter: kaliber | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r22529. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:32:31 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:32:31 -0000 Subject: [Haiku-bugs] [Haiku] #1560: [bin : pack_cis] crash on start Message-ID: <040.868026285632a542dc687272ebd81a67@haiku-os.org> #1560: [bin : pack_cis] crash on start ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Don't know what is pack_cis but it crash on launch. Will try to get back trace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:34:03 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:34:03 -0000 Subject: [Haiku-bugs] [Haiku] #1560: [bin : pack_cis] crash on start In-Reply-To: <040.868026285632a542dc687272ebd81a67@haiku-os.org> References: <040.868026285632a542dc687272ebd81a67@haiku-os.org> Message-ID: <049.fddd63b2af04bbb3ab2f11271f8df43c@haiku-os.org> #1560: [bin : pack_cis] crash on start -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by diver): {{{ 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 0x2021c0, write 0, user 1, thread 0x98 vm_page_fault: sending team "/boot/beos/bin/pack_cis" 0x98 SIGSEGV, ip 0x2021c0 ("pack_cis_seg0ro" +0x21c0) stack trace: 0x00202379 (pack_cis_seg0ro + 0x2379) 0x002013bf (pack_cis_seg0ro + 0x13bf) 0x001007be (runtime_loader_seg0ro + 0x7be) 0x7ffe6fec (/boot/beos/bin/pack_cis_main_st + 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 0x8009b92c, write 0, user 0, thread 0x98 debug_server: Thread 152 entered the debugger: Segment violation stack trace, current PC 0x2021c0 _term_after + 0xd20 (closest symbol): (0x7ffe6b4c) 0x202379 main + 0x12d (0x7ffe6f7c) 0x2013bf _start + 0x5b (0x7ffe6fac) 0x1007be (runtime_loader_seg0ro + 0x7be) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:47:58 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:47:58 -0000 Subject: [Haiku-bugs] [Haiku] #1561: [Deskbar] Scrollers are already attached! Message-ID: <040.0e9f97940db610c2c3bdc9df6e6841d4@haiku-os.org> #1561: [Deskbar] Scrollers are already attached! ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Deskbar | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- Trying to reproduce one of my old bugs i stress tested system by running all apps in /boot/beos/bin (whithout pack_cis, consoled and shutdown) }}} 369: DEBUGGER: Scrollers are already attached! debug_server: Thread 369 entered the debugger: Debugger call: `Scrollers are already attached!' stack trace, current PC 0xffff0102 : (0x701c560c) 0x36969f AttachScrollers__Q28BPrivate11BMenuWindow + 0x53 (0x701c565c) 0x361847 _UpdateWindowViewSize__5BMenub + 0x25f (0x701c56dc) 0x35cc4a AddItem__5BMenuP9BMenuIteml + 0xa2 (0x701c571c) 0x35cb9b AddItem__5BMenuP9BMenuItem + 0x2f (0x701c575c) 0x8cd997 Pulse__11TeamBarMenu + 0x48f (0x701c5c9c) 0x8cd4f6 Draw__11TeamBarMenuG5BRect + 0x62 (0x701c5cdc) 0x3b1b52 _Draw__5BViewG5BRect + 0xda (0x701c5d4c) 0x3b5e84 DispatchMessage__7BWindowP8BMessageP8BHandler + 0x12ec (0x701c5f1c) 0x3b987c task_looper__7BWindow + 0x270 (0x701c5f7c) 0x30aac3 _task0___7BLooperPv + 0x3f (0x701c5fac) 0x6c4ad0 _get_next_team_info + 0x5c (closest symbol) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:54:34 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:54:34 -0000 Subject: [Haiku-bugs] [Haiku] #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have In-Reply-To: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> References: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> Message-ID: <049.9493e30e82a648c3f7200d11d6250283@haiku-os.org> #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Old description: > Extra attributes box in FileTypes have scrollbar even if no attribute > exist. In the same time File recognition bpx doesn't habe this problem. > > To reproduce: > * Launch FileTypes > * Expand application list > * Select Person > * Select PDF document New description: Extra attributes box in FileTypes have scrollbar even if no attribute exist. In the same time File recognition box doesn't have this problem. To reproduce: * Launch FileTypes * Expand application list * Select Person * Select PDF document -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 14:54:48 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 12:54:48 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.c4ae72bebbf28fe66cf8609a432650bd@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): Hi, 'sh: bt: command not found' See the screenshot attached. Also, I'm using libypthon2.4.so in /home/config/lib You need to make a link in the same directory, and rename it libpython2.1.so -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:00:57 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:00:57 -0000 Subject: [Haiku-bugs] [Haiku] #1562: [registrar] crash Message-ID: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> #1562: [registrar] crash -------------------------------+-------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Trying to reproduce one of my old bugs i stress tested system by running almost all apps in /boot/beos/bin. This time whithout consoled, CortexAddonHost, pack_cis, sync, shutdown and vim) Registrar crashed and i was welcomed by fullscreened gdm complaining that it could not find it's core files, so bt doesn't work. {{{ vm_soft_fault: va 0x1d not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x1d, ip 0x315412, write 0, user 1, thread 0x2a vm_page_fault: sending team "/boot/beos/system/servers/regis" 0x26 SIGSEGV, ip 0x315412 ("libbe.so_seg0ro" +0xcd412) stack trace: 0x0031571c (libbe.so_seg0ro + 0xcd71c) 0x0031559e (libbe.so_seg0ro + 0xcd59e) 0x00306583 (libbe.so_seg0ro + 0xbe583) 0x00307ed5 (libbe.so_seg0ro + 0xbfed5) 0x00307ac3 (libbe.so_seg0ro + 0xbfac3) 0x00516ad0 (libroot.so_seg0ro + 0x20ad0) 0x700c1fec (main_mime_2a_stack + 0x3ffec) 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 0x8009b92c, write 0, user 0, thread 0x2a debug_server: Thread 42 entered the debugger: Segment violation stack trace, current PC 0x315412 IsFinished__C15RegistrarThread + 0x6: (0x700c1e9c) 0x31571c CleanupThreads__22RegistrarThreadManager + 0x50 (0x700c1edc) 0x31559e MessageReceived__22RegistrarThreadManagerP8BMessage + 0x2a (0x700c1f0c) 0x306583 DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b (0x700c1f3c) 0x307ed5 task_looper__7BLooper + 0x211 (0x700c1f7c) 0x307ac3 _task0___7BLooperPv + 0x3f (0x700c1fac) 0x516ad0 _get_next_team_info + 0x5c (closest symbol) 38: DEBUGGER: getNumAvailable() == 0 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:07:09 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:07:09 -0000 Subject: [Haiku-bugs] [Haiku] #1563: [bin: yes] command takes 100% cpu Message-ID: <040.6f9ea6d8bdc47d90e649c76384dfa25e@haiku-os.org> #1563: [bin: yes] command takes 100% cpu ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- yes command takes 100% cpu -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:22:58 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:22:58 -0000 Subject: [Haiku-bugs] [Haiku] #1564: [bin: vi] crashes if started from tracker Message-ID: <040.d2875dae1ee09a9c5063f43651d0841c@haiku-os.org> #1564: [bin: vi] crashes if started from tracker ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- vi will crashes if started from tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:45:33 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:45:33 -0000 Subject: [Haiku-bugs] [Haiku] #1565: [bin: updatedb] in null byte long Message-ID: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> #1565: [bin: updatedb] in null byte long ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- /boot/beos/bin/updatedb in null byte long. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:45:48 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:45:48 -0000 Subject: [Haiku-bugs] [Haiku] #1565: [bin: updatedb] is null byte long In-Reply-To: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> References: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> Message-ID: <049.a5e94557580f9e9eeb0386e85ecf13a8@haiku-os.org> #1565: [bin: updatedb] is null byte long -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by diver): * summary: [bin: updatedb] in null byte long => [bin: updatedb] is null byte long -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:46:31 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:46:31 -0000 Subject: [Haiku-bugs] [Haiku] #1565: [bin: updatedb] is null byte long In-Reply-To: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> References: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> Message-ID: <049.eb7dd0ebca6fa9a74296b31efc1ffcd3@haiku-os.org> #1565: [bin: updatedb] is null byte long -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:56:41 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:56:41 -0000 Subject: [Haiku-bugs] [Haiku] #1000: [Tracker] selected icons disappering In-Reply-To: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> References: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> Message-ID: <049.8353b1ebc565e8a597b1c0b77b9a5e37@haiku-os.org> #1000: [Tracker] selected icons disappering -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by diver): I think it's a dup of my own bug #880 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 15:57:32 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 13:57:32 -0000 Subject: [Haiku-bugs] [Haiku] #1566: lockf() not implemented Message-ID: <042.6a9cfbace4f6f891ec1ff46c546ac350@haiku-os.org> #1566: lockf() not implemented -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- It would be nice to have lockf() function. http://www.opengroup.org/onlinepubs/009695399/functions/lockf.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 16:40:47 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 14:40:47 -0000 Subject: [Haiku-bugs] [Haiku] #1566: lockf() not implemented In-Reply-To: <042.6a9cfbace4f6f891ec1ff46c546ac350@haiku-os.org> References: <042.6a9cfbace4f6f891ec1ff46c546ac350@haiku-os.org> Message-ID: <051.cdb34693a4c4309991451f28014678f2@haiku-os.org> #1566: lockf() not implemented --------------------------+------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by bonefish): We do already have fcntl(F_GETLK/F_SETLK[W]) support, and it looks like lockf() can be fully mapped to it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 16:46:02 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 14:46:02 -0000 Subject: [Haiku-bugs] [Haiku] #1544: Haiku doesn't detect boot partition on real hardware In-Reply-To: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> References: <044.9ee0057f5eb4e6b74bf92b05b47a061c@haiku-os.org> Message-ID: <053.28e87e815b7cfa66ff8615945fd630b8@haiku-os.org> #1544: Haiku doesn't detect boot partition on real hardware ------------------------+--------------------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: fixed | Platform: x86 ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: I haven't changed anything related in the disk device manager in the meantime, so I suppose, an AHCI related changed must have fixed. Anyway, closing the ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 16:53:20 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 14:53:20 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.136b96be5e7265c110c4bea5acb9c874@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * priority: normal => critical * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 17:16:08 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 15:16:08 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.4f047bb06dcecafd13b23af1bca35bd9@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): Ok, sorry don't know what was going on. Got the backtrace and attached it! Sorry for the confusion. Definitely seems to be MESA related... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 17:19:48 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 15:19:48 -0000 Subject: [Haiku-bugs] [Haiku] #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller Message-ID: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller ---------------------------------+------------------------------------------ Reporter: patrick lafarguette | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | ---------------------------------+------------------------------------------ Haiku fails to boot on an IDE HDD attached to the JMicron 363 controller of my P5B Deluxe motherboard. The JMB363 is set to AHCI in the BIOS. Haiku goes to KDL with "PANIC: did not find any boot partitions!". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 17:52:07 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 15:52:07 -0000 Subject: [Haiku-bugs] [Haiku] #1568: pthread_once() not implemented Message-ID: <042.f0ab400969d0b295fda30711b4ec7164@haiku-os.org> #1568: pthread_once() not implemented -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- http://www.opengroup.org/onlinepubs/007908799/xsh/pthread_once.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 18:05:10 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 16:05:10 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.b7cfd89ddfb9b1e4aabe8d0890cb80cd@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): I wanted to test MESA software renderer from BeOS Max v4b on Haiku to see if Blender would work with this version, but can't locate the binary, just the source. It's not located in the same place as in Haiku, and a search doesn't reveal it. Would it be named something else? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 18:27:42 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 16:27:42 -0000 Subject: [Haiku-bugs] [Haiku] #1557: Frequency out of range In-Reply-To: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> References: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> Message-ID: <053.7e42c4106938e79668f22219a0471c6d@haiku-os.org> #1557: Frequency out of range --------------------------------------+------------------------------------- Reporter: plfiorini | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by umccullough): Maybe you're experiencing the same as me: I've had problems with my integrated GeForce 6100 video - it yields a black screen for Haiku and Zeta - I suspect there's something wrong with the driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 18:27:43 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 16:27:43 -0000 Subject: [Haiku-bugs] [Haiku] #1562: [registrar] crash In-Reply-To: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> References: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> Message-ID: <049.abf564a33e18bf5b88178d69bb487232@haiku-os.org> #1562: [registrar] crash --------------------------------+------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by bonefish): Should be fixed in r22534/r22535. At least here all programs start (respectively fail to start) now, although it takes ages and the system is extremely unresponsive part of the time. Please verify. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 19:04:02 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 17:04:02 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.f3b9c1a5c84eacd0c610ca8cd8875db5@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by umccullough): oh, maybe gdb uses sc (stackcrawl) instead of bt (backtrace) - I can never remember :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 19:18:18 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 17:18:18 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.c73bfb2e4ec7041edfc2838c6a541287@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by plfiorini): I cannot reproduce it on r22535 both shutdown -r on console and graphical restart from deskbar reboot (on vmware). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 21:32:56 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 19:32:56 -0000 Subject: [Haiku-bugs] [Haiku] #1562: [registrar] crash In-Reply-To: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> References: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> Message-ID: <049.789a9129389c00175cb72e66dd4f45ee@haiku-os.org> #1562: [registrar] crash --------------------------------+------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by diver): Tested twice with r22537 and this time registrar no longer crash. I had to increase memory in vmware to be able to start all apps. It took about 5 min to complete and after that system became very unresponsive as you said. Please close this bug. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 22:02:17 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 20:02:17 -0000 Subject: [Haiku-bugs] [Haiku] #1562: [registrar] crash In-Reply-To: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> References: <040.a018c950fc2b637571331faf391f2d14@haiku-os.org> Message-ID: <049.7d03a4c2eee7bf9741d748e9d4152cc3@haiku-os.org> #1562: [registrar] crash --------------------------------+------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 13 21:42:37 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 19:42:37 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.ff33424d45a2950c6a5119eb4e4872a9@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): It does indeed work fine in VMWare...real hardware is a different kettle of fish though, much more variety there. Also iirc one of Axel's laptops likewise has strange issues with shutdown which might be related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 00:14:05 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 13 Oct 2007 22:14:05 -0000 Subject: [Haiku-bugs] [Haiku] #1548: Error in example code for BLocker in the Haiku Book In-Reply-To: <042.6bd369ca8ce661e79839e0bd3ac022d2@haiku-os.org> References: <042.6bd369ca8ce661e79839e0bd3ac022d2@haiku-os.org> Message-ID: <051.cac2472f4e9ee56c40954495cfb55bab@haiku-os.org> #1548: Error in example code for BLocker in the Haiku Book ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by nielx): * status: new => closed * resolution: => fixed Comment: Fixed in r22543. Thanks for reporting! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 08:35:14 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 06:35:14 -0000 Subject: [Haiku-bugs] [Haiku] #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller In-Reply-To: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> References: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> Message-ID: <063.a93af928ffc08d088137e94fb1fd7421@haiku-os.org> #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller ----------------------------------+----------------------------------------- Reporter: patrick lafarguette | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by plfiorini): It's like my bug -> http://dev.haiku-os.org/ticket/1544 Can you try r22527 and check if it works now? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 12:00:03 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 10:00:03 -0000 Subject: [Haiku-bugs] [Haiku] #1563: [bin: yes] command takes 100% cpu In-Reply-To: <040.6f9ea6d8bdc47d90e649c76384dfa25e@haiku-os.org> References: <040.6f9ea6d8bdc47d90e649c76384dfa25e@haiku-os.org> Message-ID: <049.217b437c9a94a9de3af023009eb053f0@haiku-os.org> #1563: [bin: yes] command takes 100% cpu -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: invalid | Platform: All -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: That's exactly what it's supposed to do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 12:07:19 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 10:07:19 -0000 Subject: [Haiku-bugs] [Haiku] #1560: [bin : pack_cis] crash on start In-Reply-To: <040.868026285632a542dc687272ebd81a67@haiku-os.org> References: <040.868026285632a542dc687272ebd81a67@haiku-os.org> Message-ID: <049.9d2f9a9e69ee0a451e8170f462fc03c2@haiku-os.org> #1560: [bin : pack_cis] crash on start -----------------------------+---------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by axeld): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 12:37:02 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 10:37:02 -0000 Subject: [Haiku-bugs] [Haiku] #1311: [FileTypes] freeze on MediaPlayer start In-Reply-To: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> References: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> Message-ID: <049.0554eb2eda31b259c7fcd671e1d2390a@haiku-os.org> #1311: [FileTypes] freeze on MediaPlayer start --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Preferences/FileTypes | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by diver): Tested more and it appears that you can't launch apps until MediaPlayer will not be killed, after that all apps that you launched in that frozen state will popup on screen. Tested with r22537 under vmware in linux. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 12:54:42 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 10:54:42 -0000 Subject: [Haiku-bugs] [Haiku] #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller In-Reply-To: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> References: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> Message-ID: <063.fbef372036ccd778908df6f79b522467@haiku-os.org> #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller ----------------------------------+----------------------------------------- Reporter: patrick lafarguette | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by patrick lafarguette): I tested r22528 to make the serial debug attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 13:09:05 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 11:09:05 -0000 Subject: [Haiku-bugs] [Haiku] #1553: Metos crashing.. In-Reply-To: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> References: <041.a7745381e94d6f481178a48370e59b67@haiku-os.org> Message-ID: <050.c688bdecc1601dcc6a5c201f7b8cfc19@haiku-os.org> #1553: Metos crashing.. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha Component: Kits/Application Kit | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed * milestone: R1 => R1/alpha Comment: Fixed in r22549. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 13:09:21 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 11:09:21 -0000 Subject: [Haiku-bugs] [Haiku] #195: [app_server] crash in WindowLayer::Frontmost() In-Reply-To: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> References: <040.11ebffe01d44a2857c38563186ab92b1@haiku-os.org> Message-ID: <049.b136c55f57abd3d523ec8aea1eaa2dc6@haiku-os.org> #195: [app_server] crash in WindowLayer::Frontmost() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Fixed in r22549. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 13:24:28 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 11:24:28 -0000 Subject: [Haiku-bugs] [Haiku] #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have In-Reply-To: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> References: <040.347d144e55777694d5c41605d73d90a3@haiku-os.org> Message-ID: <049.fafef6a2ad85f22d861d474587689110@haiku-os.org> #1558: [FileTypes] Extra attributes box have scrollbar which shouldn't have ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed * milestone: R1 => R1/alpha Comment: Fixed in r22550: it was a bug in BListView::MakeEmpty(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 14:36:07 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 12:36:07 -0000 Subject: [Haiku-bugs] [Haiku] #1000: [Tracker] selected icons disappering In-Reply-To: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> References: <040.bc0848edfd526ba3814a7cc00b61a48b@haiku-os.org> Message-ID: <049.81f3fd2ced716ed46b6927f3d9b2e130@haiku-os.org> #1000: [Tracker] selected icons disappering -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: - Applications/Tracker | Version: R1 development Resolution: duplicate | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 14:36:32 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 12:36:32 -0000 Subject: [Haiku-bugs] [Haiku] #880: [app_server] icon disappers if selected and then desktop right clicked In-Reply-To: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> References: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> Message-ID: <049.458336884af347769bbb5e57f22035de@haiku-os.org> #880: [app_server] icon disappers if selected and then desktop right clicked ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * milestone: R1 => R1/alpha Comment: Bug #1000 was a duplicate of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 16:45:59 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 14:45:59 -0000 Subject: [Haiku-bugs] [Haiku] #1569: [Tracker] scrollbar scrolling left-right with mouse wheel Message-ID: <040.70c06378d1646f9eadad0578e4826a15@haiku-os.org> #1569: [Tracker] scrollbar scrolling left-right with mouse wheel ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- You could scroll horizontal scrollbar left-right with mouse wheel. To reproduce: * start PackageInstaller * select config folder * scroll mouse wheel several times -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 16:47:40 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 14:47:40 -0000 Subject: [Haiku-bugs] [Haiku] #1570: [PackageInstaller] wont quit correctly Message-ID: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> #1570: [PackageInstaller] wont quit correctly ---------------------------------------------+------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/PackageInstaller | Version: R1 development Platform: All | ---------------------------------------------+------------------------------ Start PackageInstaller and press Cancel button in open dialog. PackageInstaller will stay in Deskbar. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 16:55:54 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 14:55:54 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.d9669182dc4f062f61042658a899945a@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by diver): app_server freeze wile trying to reproduce this bug. {{{ vm_soft_fault: va 0xffffffff not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xffffffff, ip 0x80097592, write 0, user 0, thread 0x110 vm_soft_fault: va 0xffffffff not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xffffffff, ip 0x80097592, write 0, user 0, thread 0x113 vm_soft_fault: va 0xc not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xc, ip 0x2e5e17, write 0, user 1, thread 0x1ff vm_page_fault: sending team "/boot/beos/demos/GLDirectMode" 0x1fa SIGSEGV, ip 0x2e5e17 ("libbe.so_seg0ro" +0xdee17) stack trace: 0x002e4588 (libbe.so_seg0ro + 0xdd588) 0x007340cf (Mesa Software Renderer_seg0ro + 0x170cf) 0x004cd0ab (libGL.so_seg0ro + 0x320ab) 0x00204383 (GLDirectMode_seg0ro + 0x4383) 0x0036bf1a (libbe.so_seg0ro + 0x164f1a) 0x004cd7d3 (libGL.so_seg0ro + 0x327d3) 0x002049ea (GLDirectMode_seg0ro + 0x49ea) 0x002c5abf (libbe.so_seg0ro + 0xbeabf) 0x00372645 (libbe.so_seg0ro + 0x16b645) 0x004897df (libgame.so_seg0ro + 0xf7df) 0x00375dcc (libbe.so_seg0ro + 0x16edcc) 0x00489b33 (libgame.so_seg0ro + 0xfb33) 0x002c6fff (libbe.so_seg0ro + 0xbffff) 0x005986a0 (libroot.so_seg0ro + 0x216a0) 0x70080fec (w>OpenGL Test_1ff_stack + 0x3ffec) 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 0x8009b7c8, write 0, user 0, thread 0x1ff debug_server: Thread 511 entered the debugger: Segment violation stack trace, current PC 0x2e5e17 _AssertPointer__7BBitmap + 0x17: (0x70080a1c) 0x2e4588 Bits__C7BBitmap + 0x20 (0x70080a4c) 0x7340cf LockGL__20MesaSoftwareRenderer + 0x3bb (0x70080acc) 0x4cd0ab LockGL__7BGLView + 0x37 (0x70080afc) 0x204383 FrameResized__12SampleGLViewff + 0x2f (0x70080b3c) 0x36bf1a MessageReceived__5BViewP8BMessage + 0x8a (0x70080c5c) 0x4cd7d3 MessageReceived__7BGLViewP8BMessage + 0x23 (0x70080c8c) 0x2049ea MessageReceived__12SampleGLViewP8BMessage + 0x46 (0x70080cbc) 0x2c5abf DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b (0x70080cec) 0x372645 DispatchMessage__7BWindowP8BMessageP8BHandler + 0x155d (0x70080ebc) 0x4897df DispatchMessage__13BDirectWindowP8BMessageP8BHandler + 0x27 (0x70080eec) 0x375dcc task_looper__7BWindow + 0x270 (0x70080f4c) 0x489b33 task_looper__13BDirectWindow + 0x1f (0x70080f7c) 0x2c6fff _task0___7BLooperPv + 0x3f (0x70080fac) 0x5986a0 _get_next_team_info + 0x5c (closest symbol) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 17:52:30 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 15:52:30 -0000 Subject: [Haiku-bugs] [Haiku] #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller In-Reply-To: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> References: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> Message-ID: <063.c0b392c2cac8624e8ce00390c33a1356@haiku-os.org> #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller ----------------------------------+----------------------------------------- Reporter: patrick lafarguette | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by umccullough): Don't forget to include a backtrace from kdl in the serial log :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 17:03:26 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 15:03:26 -0000 Subject: [Haiku-bugs] [Haiku] #1571: [audio_mixer] remove useless right info bar so Setup tab will fit in window Message-ID: <040.9615be92d428f54b02c4fb04af049cdf@haiku-os.org> #1571: [audio_mixer] remove useless right info bar so Setup tab will fit in window ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Remove right info bar from Audio Mixer so Setup tab in Media pref will fit in window, this will also hide somewhat strange horizontal bar from the bottom of that view. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 20:09:46 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 18:09:46 -0000 Subject: [Haiku-bugs] [Haiku] #1560: [bin : pack_cis] crash on start In-Reply-To: <040.868026285632a542dc687272ebd81a67@haiku-os.org> References: <040.868026285632a542dc687272ebd81a67@haiku-os.org> Message-ID: <049.105c92a19b7ece7b41f52c65e6ffb36f@haiku-os.org> #1560: [bin : pack_cis] crash on start -----------------------------+---------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Dunno why pcmcia-cs tools were included in the hd image. They were only tested in BeOS. "Fixed" in revision 22552. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 21:04:20 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 19:04:20 -0000 Subject: [Haiku-bugs] [Haiku] #1560: [bin : pack_cis] crash on start In-Reply-To: <040.868026285632a542dc687272ebd81a67@haiku-os.org> References: <040.868026285632a542dc687272ebd81a67@haiku-os.org> Message-ID: <049.60ed9cfe3e6f04697c98f7c11f926057@haiku-os.org> #1560: [bin : pack_cis] crash on start -----------------------------+---------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Comment (by kaliber): Replying to [comment:3 korli]: > Dunno why pcmcia-cs tools were included in the hd image. They were only tested in BeOS. "Fixed" in revision 22552. It was added "by mistake", look at bug #1131. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 21:58:21 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 19:58:21 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] can't be controlled by a mouse anymore In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.455716fe43c1f8545b0b7d29dd5ef1bc@haiku-os.org> #1310: [GLTeapot] can't be controlled by a mouse anymore ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): It seems changing the priority of the direct daemon thread to less than 15 let me control the teapot with the mouse. Stefano, should I change the priority of the direct daemon thread to (B_DISPLAY_PRIORITY - 1) ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 22:01:52 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 20:01:52 -0000 Subject: [Haiku-bugs] [Haiku] #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch In-Reply-To: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> References: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> Message-ID: <053.248780989b3c3c613f3796d878049fcb@haiku-os.org> #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch ----------------------------------+----------------------------------------- Reporter: pieterpan | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Media | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by korli): Can't reproduce. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 22:02:47 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 20:02:47 -0000 Subject: [Haiku-bugs] [Haiku] #1440: GL Teapot Seg Fault with Screensaver Test In-Reply-To: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> References: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> Message-ID: <049.0531a680745260ee3658508c59cb3921@haiku-os.org> #1440: GL Teapot Seg Fault with Screensaver Test ------------------------------+--------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): Can't reproduce. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 22:33:43 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 20:33:43 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.a3983e537c8f30c9f06b9fe2ed0e1cfe@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: I can still reproduce it with r22554, reopening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 22:34:05 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 20:34:05 -0000 Subject: [Haiku-bugs] [Haiku] #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch In-Reply-To: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> References: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> Message-ID: <053.88eb446241bba514d204ff5913dff044@haiku-os.org> #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch ----------------------------------+----------------------------------------- Reporter: pieterpan | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Media | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by diver): I can reproduce it with r22554 under vmware and it's a dup of bug #573 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 22:38:37 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 20:38:37 -0000 Subject: [Haiku-bugs] [Haiku] #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch In-Reply-To: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> References: <044.df4f669105e2006681d3ebd0a462b362@haiku-os.org> Message-ID: <053.2045b064d818009e182c999c0520a946@haiku-os.org> #1417: Media Preferences crashes with dropdown menu active followed by 'page' switch ----------------------------------+----------------------------------------- Reporter: pieterpan | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Preferences/Media | Version: R1 development Resolution: duplicate | Platform: All ----------------------------------+----------------------------------------- Changes (by korli): * status: new => closed * resolution: => duplicate Comment: I'm closing this one then. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 14 23:32:47 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 21:32:47 -0000 Subject: [Haiku-bugs] [Haiku] #1572: Haiku doesn't boot on SATA HDD nforce 430 chipset (Dell C521) Message-ID: <041.cc0506141dda10035a2abd06c7189f55@haiku-os.org> #1572: Haiku doesn't boot on SATA HDD nforce 430 chipset (Dell C521) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | --------------------------+------------------------------------------------- PANIC: did not find any boot partitions... Not sure that this is a bug, but just providing some information about the drive Haiku is unable to boot on. See the attached image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 01:14:23 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 14 Oct 2007 23:14:23 -0000 Subject: [Haiku-bugs] [Haiku] #1554: Clock demo app doesn't show the clock face or replicant grabber In-Reply-To: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> References: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> Message-ID: <051.f7ef41b8848890e4fcfe4645716445a1@haiku-os.org> #1554: Clock demo app doesn't show the clock face or replicant grabber -----------------------------+---------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by julun): fixed in Revision: 22560 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 08:51:31 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 06:51:31 -0000 Subject: [Haiku-bugs] [Haiku] #1573: Sample Be program Xmas crashes with a divide error Message-ID: <042.3a1ffb60eac3c9b934164162fab24482@haiku-os.org> #1573: Sample Be program Xmas crashes with a divide error -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I downloaded the Be Sample code from BeBits and build most of the sample code. Most ran with no issues other than text not fitting inside buttons and such, but the xmas program crashed, attached is a screenshot. Something about a divide error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 09:17:56 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 07:17:56 -0000 Subject: [Haiku-bugs] [Haiku] #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller In-Reply-To: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> References: <054.983500434cf84bb0bc847fba61417a53@haiku-os.org> Message-ID: <063.cb79bdbf648b23c81f1b75113f066221@haiku-os.org> #1567: Haiku doesn't boot on IDE HDD with JMicron 363 controller ----------------------------------+----------------------------------------- Reporter: patrick lafarguette | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by marcusoverhagen): * owner: axeld => marcusoverhagen -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 10:37:00 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 08:37:00 -0000 Subject: [Haiku-bugs] [Haiku] #1573: Sample Be program Xmas crashes with a divide error In-Reply-To: <042.3a1ffb60eac3c9b934164162fab24482@haiku-os.org> References: <042.3a1ffb60eac3c9b934164162fab24482@haiku-os.org> Message-ID: <051.6eacbf9e1fd63f877d4225c6acb0ef50@haiku-os.org> #1573: Sample Be program Xmas crashes with a divide error ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by jackburton): * owner: axeld => marcusoverhagen Comment: XMas uses the BSound api. Currently that api is unimplemented in haiku, and I'm not sure we'll ever implement it, since it's marked as deprecated. Although, I think we should at least change the BSound methods to return B_ERROR instead of B_OK. In any case, reassigning to Marcus. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 10:39:58 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 08:39:58 -0000 Subject: [Haiku-bugs] [Haiku] #1554: Clock demo app doesn't show the clock face or replicant grabber In-Reply-To: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> References: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> Message-ID: <051.7a8ab74c14f7cecc8f8c917a2f66e09d@haiku-os.org> #1554: Clock demo app doesn't show the clock face or replicant grabber -----------------------------+---------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by jackburton): Replying to [comment:2 julun]: > fixed in Revision: 22560 Julun, it's advised to write the revision as " r22560 ", so the bugtracker will automatically make a link to the related revision in the source repository. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 10:43:05 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 08:43:05 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.15c749984609229da964c859fbf75e93@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): It was fixed in r20799, but the change in r21961 made it show up again. And, although the symptoms are different, it has the same cause as bug #582. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 11:13:58 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 09:13:58 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.7c58058dd25644749794b058faa9560e@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): Stefano, could you have a look at a change I made in r22559 ? It fixed the menu issue I had, dunno if this is correct though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 11:35:52 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 09:35:52 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.819a5fe79c18198c994cf9787cee3c50@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:12 korli]: > Stefano, could you have a look at a change I made in r22559 ? It fixed the menu issue I had, dunno if this is correct though. That change looks okay. It's always good to keep on the defensive, at least. So this bug is fixed ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 11:55:33 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 09:55:33 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.8fc6b7b5a8149250f7009767b38495f6@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by korli): * status: reopened => closed * resolution: => fixed Comment: It seems fixed to me. Let's see if it is for diver :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 12:54:53 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 10:54:53 -0000 Subject: [Haiku-bugs] [Haiku] #1554: Clock demo app doesn't show the clock face or replicant grabber In-Reply-To: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> References: <042.c65f0053187b6569523e940a013bc473@haiku-os.org> Message-ID: <051.8451ce1dc58e1e5e1a0a9969647e2158@haiku-os.org> #1554: Clock demo app doesn't show the clock face or replicant grabber -----------------------------+---------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 16:19:31 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 14:19:31 -0000 Subject: [Haiku-bugs] [Haiku] #1565: [bin: updatedb] is null byte long In-Reply-To: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> References: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> Message-ID: <049.100565fd3db756705091a6b319514754@haiku-os.org> #1565: [bin: updatedb] is null byte long -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Old description: > /boot/beos/bin/updatedb in null byte long. New description: /boot/beos/bin/updatedb is null byte long. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 18:26:36 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 16:26:36 -0000 Subject: [Haiku-bugs] [Haiku] #1574: After reboot apps on non-boot partition disappear Message-ID: <044.92e2c0dad8c2e7bf2977ddc31c19cace@haiku-os.org> #1574: After reboot apps on non-boot partition disappear --------------------------------------+------------------------------------- Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/LaunchBox | Version: R1 development Platform: All | --------------------------------------+------------------------------------- This is on a vmimage, r22548. I have all 3rd party apps and data on its own image so I can update the system image without losing everything. Putting these "external" apps into the LaunchBox works until you reboot. Then the slots are empty... Yes, the app-image is mounted at that time. BTW, I think "Slot" is more fitting than "Button". I don't know if it's of any concern... Started from Terminal it says: Signature in rsrc doesn't match constructor arg, (application/x.vnd- YellowBites.LaunchBox, application/x.vnd.Haiku-Launchbox) I bet it's as minor as unrelated... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 19:55:02 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 17:55:02 -0000 Subject: [Haiku-bugs] [Haiku] #1574: After reboot apps on non-boot partition disappear In-Reply-To: <044.92e2c0dad8c2e7bf2977ddc31c19cace@haiku-os.org> References: <044.92e2c0dad8c2e7bf2977ddc31c19cace@haiku-os.org> Message-ID: <053.fa415b4a0cacdec7bdc082b204fb3082@haiku-os.org> #1574: After reboot apps on non-boot partition disappear ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/LaunchBox | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by korli): The signature is fixed in r22570. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 20:06:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 18:06:18 -0000 Subject: [Haiku-bugs] [Haiku] #1575: Screenshot of vlc (while playing a video) shows a black rectangle Message-ID: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> #1575: Screenshot of vlc (while playing a video) shows a black rectangle -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- a) open vlc to play an internet tv station stream. b) while vlc is playing the video, press "print screen" key to take a screenshot, c) open the screenshot-image with ShowImage, vlc window has a black rectangle. more: start vlc again, open a video, or let vlc plays the previous video; move litle by litle the ShowImage window (with contains the screenshot with the black vlc window, in front of vlc, surprise! in the black vlc window of the ShowImage, you see the video that vlc plays in the background. note: vlc doesn't have this behavior on r5, so i guess it is not vlc bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 20:15:11 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 18:15:11 -0000 Subject: [Haiku-bugs] [Haiku] #1565: [bin: updatedb] is null byte long In-Reply-To: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> References: <040.f23e8ce352de93d355fa7290ad371ca3@haiku-os.org> Message-ID: <049.5c3d84302a2c30827eed01f70f861503@haiku-os.org> #1565: [bin: updatedb] is null byte long -----------------------------+---------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r22572. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 20:20:20 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 18:20:20 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.00c2b8b1d4bc2a34712e74d90106ffd0@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by phoudoin): Patch applied. The crash happens in Mesa Software Renderer, because BBitmap can't be allocated with a (0,0,-1,-1) bound. Will fix it in a few minutes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 22:05:44 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 20:05:44 -0000 Subject: [Haiku-bugs] [Haiku] #1575: Screenshot of vlc (while playing a video) shows a black rectangle In-Reply-To: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> References: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> Message-ID: <052.17c825cd9411920c0d050e7e59afdb32@haiku-os.org> #1575: Screenshot of vlc (while playing a video) shows a black rectangle ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): Replying to [comment:1 korli]: > This is a feature of overlay : http://en.wikipedia.org/wiki/Video_overlay > I wouldn't consider this as a bug though. Thanks for the link. first i must make a correction (examine more closely the ticket): r5 has exactly the same behavior. the window in the screenshot is not black but gray (so the note on the description is not correct), i still don't know how this came out to my mind:) So i guess no screenshot is possible? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 23:36:21 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 21:36:21 -0000 Subject: [Haiku-bugs] [Haiku] #1575: Screenshot of vlc (while playing a video) shows a black rectangle In-Reply-To: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> References: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> Message-ID: <052.28212e6d53a7689e283f41e92771056c@haiku-os.org> #1575: Screenshot of vlc (while playing a video) shows a black rectangle ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * type: bug => enhancement * component: - General => Servers/app_server Comment: It's possible - the app_server could copy the overlay into the screenshot - like it already does for the hardware cursor. I'll change this to an extension :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 00:49:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 22:49:24 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten Message-ID: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> #1576: Some headers should be rewritten -----------------------+---------------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Here is a list in headers/os headers/os/add-ons/graphics/GraphicsCard.h headers/os/add-ons/input_server/InputServerDevice.h headers/os/add-ons/input_server/InputServerFilter.h headers/os/add-ons/input_server/InputServerMethod.h headers/os/app/PropertyInfo.h headers/os/be_apps/NetPositive/NetPositive.h headers/os/device/A2D.h headers/os/device/CAM.h headers/os/device/D2A.h headers/os/device/DigitalPort.h headers/os/device/Joystick.h headers/os/device/scsi.h headers/os/device/SerialPort.h headers/os/drivers/atomizer.h headers/os/drivers/bus_manager.h headers/os/drivers/ISA.h headers/os/drivers/midi_driver.h headers/os/drivers/PCI.h headers/os/drivers/USB_printer.h headers/os/drivers/USB_rle.h headers/os/drivers/USB_spec.h headers/os/game/DirectWindow.h headers/os/interface/ChannelControl.h headers/os/interface/ChannelSlider.h headers/os/interface/Input.h headers/os/interface/MenuBar.h headers/os/interface/MultiChannelControl.h headers/os/interface/OptionControl.h headers/os/interface/OptionPopUp.h headers/os/interface/PopUpMenu.h headers/os/interface/PrintJob.h headers/os/interface/TextView.h headers/os/kernel/image.h headers/os/kernel/scheduler.h headers/os/mail/E-mail.h headers/os/media/BufferConsumer.h headers/os/media/BufferGroup.h headers/os/media/Buffer.h headers/os/media/BufferProducer.h headers/os/media/Controllable.h headers/os/media/FileInterface.h headers/os/media/MediaAddOn.h headers/os/media/MediaDefs.h headers/os/media/MediaEventLooper.h headers/os/media/MediaFiles.h headers/os/media/MediaFormats.h headers/os/media/MediaNode.h headers/os/media/MediaRoster.h headers/os/media/ParameterWeb.h headers/os/media/PlaySound.h headers/os/media/RealtimeAlloc.h headers/os/media/SoundFile.h headers/os/media/Sound.h headers/os/media/SoundPlayer.h headers/os/media/TimeCode.h headers/os/media/TimedEventQueue.h headers/os/media/TimeSource.h headers/os/net/net_settings.h headers/os/opengl/GLView.h headers/os/translation/BitmapStream.h headers/os/translation/TranslationDefs.h headers/os/translation/TranslationErrors.h headers/os/translation/TranslationKit.h headers/os/translation/TranslatorAddOn.h headers/os/translation/TranslatorFormats.h -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 00:54:54 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 22:54:54 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.f263eaad99bac0665dd89ee17c47e831@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Old description: > Here is a list in headers/os > > headers/os/add-ons/graphics/GraphicsCard.h > headers/os/add-ons/input_server/InputServerDevice.h > headers/os/add-ons/input_server/InputServerFilter.h > headers/os/add-ons/input_server/InputServerMethod.h > headers/os/app/PropertyInfo.h > headers/os/be_apps/NetPositive/NetPositive.h > headers/os/device/A2D.h > headers/os/device/CAM.h > headers/os/device/D2A.h > headers/os/device/DigitalPort.h > headers/os/device/Joystick.h > headers/os/device/scsi.h > headers/os/device/SerialPort.h > headers/os/drivers/atomizer.h > headers/os/drivers/bus_manager.h > headers/os/drivers/ISA.h > headers/os/drivers/midi_driver.h > headers/os/drivers/PCI.h > headers/os/drivers/USB_printer.h > headers/os/drivers/USB_rle.h > headers/os/drivers/USB_spec.h > headers/os/game/DirectWindow.h > headers/os/interface/ChannelControl.h > headers/os/interface/ChannelSlider.h > headers/os/interface/Input.h > headers/os/interface/MenuBar.h > headers/os/interface/MultiChannelControl.h > headers/os/interface/OptionControl.h > headers/os/interface/OptionPopUp.h > headers/os/interface/PopUpMenu.h > headers/os/interface/PrintJob.h > headers/os/interface/TextView.h > headers/os/kernel/image.h > headers/os/kernel/scheduler.h > headers/os/mail/E-mail.h > headers/os/media/BufferConsumer.h > headers/os/media/BufferGroup.h > headers/os/media/Buffer.h > headers/os/media/BufferProducer.h > headers/os/media/Controllable.h > headers/os/media/FileInterface.h > headers/os/media/MediaAddOn.h > headers/os/media/MediaDefs.h > headers/os/media/MediaEventLooper.h > headers/os/media/MediaFiles.h > headers/os/media/MediaFormats.h > headers/os/media/MediaNode.h > headers/os/media/MediaRoster.h > headers/os/media/ParameterWeb.h > headers/os/media/PlaySound.h > headers/os/media/RealtimeAlloc.h > headers/os/media/SoundFile.h > headers/os/media/Sound.h > headers/os/media/SoundPlayer.h > headers/os/media/TimeCode.h > headers/os/media/TimedEventQueue.h > headers/os/media/TimeSource.h > headers/os/net/net_settings.h > headers/os/opengl/GLView.h > headers/os/translation/BitmapStream.h > headers/os/translation/TranslationDefs.h > headers/os/translation/TranslationErrors.h > headers/os/translation/TranslationKit.h > headers/os/translation/TranslatorAddOn.h > headers/os/translation/TranslatorFormats.h New description: Here is a list in headers/os. They should be reported in headers/build/. headers/os/add-ons/graphics/Accelerant.h headers/os/add-ons/graphics/GraphicsCard.h headers/os/add-ons/input_server/InputServerDevice.h headers/os/add-ons/input_server/InputServerFilter.h headers/os/add-ons/input_server/InputServerMethod.h headers/os/add-ons/tracker/TrackerAddOn.h headers/os/app/PropertyInfo.h headers/os/be_apps/NetPositive/NetPositive.h headers/os/device/A2D.h headers/os/device/CAM.h headers/os/device/D2A.h headers/os/device/DigitalPort.h headers/os/device/Joystick.h headers/os/device/scsi.h headers/os/device/SerialPort.h headers/os/drivers/atomizer.h headers/os/drivers/bus_manager.h headers/os/drivers/ISA.h headers/os/drivers/midi_driver.h headers/os/drivers/PCI.h headers/os/drivers/USB_printer.h headers/os/drivers/USB_rle.h headers/os/drivers/USB_spec.h headers/os/game/DirectWindow.h headers/os/interface/ChannelControl.h headers/os/interface/ChannelSlider.h headers/os/interface/Input.h headers/os/interface/MenuBar.h headers/os/interface/MultiChannelControl.h headers/os/interface/OptionControl.h headers/os/interface/OptionPopUp.h headers/os/interface/PopUpMenu.h headers/os/interface/PrintJob.h headers/os/interface/TextView.h headers/os/kernel/image.h headers/os/kernel/scheduler.h headers/os/mail/E-mail.h headers/os/media/BufferConsumer.h headers/os/media/BufferGroup.h headers/os/media/Buffer.h headers/os/media/BufferProducer.h headers/os/media/Controllable.h headers/os/media/FileInterface.h headers/os/media/MediaAddOn.h headers/os/media/MediaDefs.h headers/os/media/MediaEventLooper.h headers/os/media/MediaFiles.h headers/os/media/MediaFormats.h headers/os/media/MediaNode.h headers/os/media/MediaRoster.h headers/os/media/ParameterWeb.h headers/os/media/PlaySound.h headers/os/media/RealtimeAlloc.h headers/os/media/SoundFile.h headers/os/media/Sound.h headers/os/media/SoundPlayer.h headers/os/media/TimeCode.h headers/os/media/TimedEventQueue.h headers/os/media/TimeSource.h headers/os/net/net_settings.h headers/os/opengl/GLView.h headers/os/translation/BitmapStream.h headers/os/translation/TranslationDefs.h headers/os/translation/TranslationErrors.h headers/os/translation/TranslationKit.h headers/os/translation/TranslatorAddOn.h headers/os/translation/TranslatorFormats.h -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 01:25:03 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 23:25:03 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.17490b59696625c9ab2148df2c77fe51@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * owner: axeld => * priority: normal => high Comment: I just rewrote TrackerAddOn.h and kernel/image.h. net_settings.h can probably be removed, as we don't support that API anymore. When we want to distribute headers as well (ie. a developer environment for Haiku) we should have replaced all Be headers with our own. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 02:29:42 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 00:29:42 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.d9b5022855c04bf00307102005e65b6a@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * summary: USB/EHCI transfers sometimes don't work => USB/EHCI transfers sometimes time out -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 02:27:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 00:27:10 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes don't work Message-ID: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> #1577: USB/EHCI transfers sometimes don't work -------------------------+-------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- After Luzern, I updated my USB installation again, and since then I have serious problems with accessing USB mass storage devices. Some blocks/files whatever are listed in Tracker, but cannot be accessed, reading their data fails. It's even 100% reproducible with the same files. I have these problems with HDs as well as flash memory cards. Log file from a failed transfer is attached; the problem occurs at the end of the log. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 02:43:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 00:43:32 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.5025fb6abdecec63813d5c0d95c4a347@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by axeld): Just tried with r21904, but the problem persists. It might happen only on certain disks (I didn't have that flash disk before, and only rarely used that HD). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 03:18:00 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 01:18:00 -0000 Subject: [Haiku-bugs] [Haiku] #1440: GL Teapot Seg Fault with Screensaver Test In-Reply-To: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> References: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> Message-ID: <049.78963f809f071812b50d9f62f8eda24a@haiku-os.org> #1440: GL Teapot Seg Fault with Screensaver Test ------------------------------+--------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by cebif): korli, I tried with the r22586_vmware and the bug did not show. Next I will try with this same version on its own partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 15 20:48:39 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 15 Oct 2007 18:48:39 -0000 Subject: [Haiku-bugs] [Haiku] #1575: Screenshot of vlc (while playing a video) shows a black rectangle In-Reply-To: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> References: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> Message-ID: <052.47bb31d93badab7a504203c29fc461a6@haiku-os.org> #1575: Screenshot of vlc (while playing a video) shows a black rectangle ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): This is a feature of overlay : http://en.wikipedia.org/wiki/Video_overlay I wouldn't consider this as a bug though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 02:13:55 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 00:13:55 -0000 Subject: [Haiku-bugs] [Haiku] #1440: GL Teapot Seg Fault with Screensaver Test In-Reply-To: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> References: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> Message-ID: <049.f8402cc9eb7b7c16c361161835a72dad@haiku-os.org> #1440: GL Teapot Seg Fault with Screensaver Test ------------------------------+--------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by cebif): If you cannot reproduce it were you using a later version than r22494. I can still reproduce it with this. I don't know if this has any relevance but was it also in a virtual machine that you tried to reproduce it? I will see anyway for myself with a virtual machine with vmware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 04:27:35 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 02:27:35 -0000 Subject: [Haiku-bugs] [Haiku] #1440: GL Teapot Seg Fault with Screensaver Test In-Reply-To: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> References: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> Message-ID: <049.9e5cee0c73b5c6ba372b539649e86f79@haiku-os.org> #1440: GL Teapot Seg Fault with Screensaver Test ------------------------------+--------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by cebif): korli, I have just tried with r22586 on its own partition and cannot reproduce the bug with this version. The bug seems to have been fixed. Is it a side effect of fixing another bug/bugs? I was able to reproduce once something close to the original bug I reported but after many retries and gradually bringing all my own settings cannot reproduce it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 07:48:29 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 05:48:29 -0000 Subject: [Haiku-bugs] [Haiku] #1572: Haiku doesn't boot on SATA HDD nforce 430 chipset (Dell C521) In-Reply-To: <041.cc0506141dda10035a2abd06c7189f55@haiku-os.org> References: <041.cc0506141dda10035a2abd06c7189f55@haiku-os.org> Message-ID: <050.0f0862b555662b6874700fe1068b0d72@haiku-os.org> #1572: Haiku doesn't boot on SATA HDD nforce 430 chipset (Dell C521) ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * owner: axeld => marcusoverhagen -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 08:38:27 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 06:38:27 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.4d71405e22bd1aec5401cfdc1729f0b9@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by diver): Philippe, i guess you forgot to commit something? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 08:55:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 06:55:32 -0000 Subject: [Haiku-bugs] [Haiku] #1575: Screenshot of vlc (while playing a video) shows a black rectangle In-Reply-To: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> References: <043.43402d421bb72011bf289fe5a2d7ee2d@haiku-os.org> Message-ID: <052.f083b1e9ec49871169de7c14e13d7c11@haiku-os.org> #1575: Screenshot of vlc (while playing a video) shows a black rectangle ---------------------------------+------------------------------------------ Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:3 axeld]: > It's possible - the app_server could copy the overlay into the screenshot - like it already does for the hardware cursor. Does it ? But we don't even have an hardware cursor yet :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 10:59:18 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 08:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.4ce3194e3ab8f11713bbe41f4f3e8d4e@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by korli): Philippe committed something in r22573. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 12:40:02 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 10:40:02 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.954b9d6df86e82014c6d6cfa161b24f1@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by siarzhuk): * cc: siarzhuk (added) Comment: Which version of usb_scsi do you use? The one from bebits has some problem during converting READ_6/WRITE_6 to READ_10/WRITE_10. Patched version is here: http://zharik.host.sk/prahramy/usb_scsi-0.1.0-dev-9994.zip. Can you try it on your system? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:20:17 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:20:17 -0000 Subject: [Haiku-bugs] [Haiku] #1440: GL Teapot Seg Fault with Screensaver Test In-Reply-To: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> References: <040.38d2510a854ce5ad05a39246e27af7ff@haiku-os.org> Message-ID: <049.a000b7535f307863a69b0d77b08b73d2@haiku-os.org> #1440: GL Teapot Seg Fault with Screensaver Test ------------------------------+--------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: fixed | Platform: All ------------------------------+--------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Yes, it was crashing at a time, but not with the yesterday version, both on real hardware and vm. It should be a side effect of some other bug (vm/page daemon). I close the bug. Of course, it can be reopened if a crash happens with the same conditions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:24:17 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:24:17 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.0d4644de6cbc928e1c9974b39d9b2d3f@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: siarzhuk Type: bug | Status: new Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * cc: siarzhuk (removed) * owner: mmlr => siarzhuk Comment: I thought I would be using the latest version from Haiku's repository that allowed to be used with BeOS. Anyway, with that new version, the problems are gone, thanks! Does the version in the repository still suffer from this problem? If not, I would just close this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:24:13 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:24:13 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] can't be controlled by a mouse anymore In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.1a487830de278e6baa7bf7ccbdedf41d@haiku-os.org> #1310: [GLTeapot] can't be controlled by a mouse anymore ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by korli): * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:25:34 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:25:34 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] can't be controlled by a mouse anymore In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.c8d379349c22e7efc67f0f5d5135a3b5@haiku-os.org> #1310: [GLTeapot] can't be controlled by a mouse anymore ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by jackburton): But does work well here. Especially since Axel's changes to the scheduler. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:26:23 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:26:23 -0000 Subject: [Haiku-bugs] [Haiku] #1357: A default soundfont is missing In-Reply-To: <041.76501dc93bd5db88289d902f6b887c26@haiku-os.org> References: <041.76501dc93bd5db88289d902f6b887c26@haiku-os.org> Message-ID: <050.3ef54d096799620d1b2347e927579a2e@haiku-os.org> #1357: A default soundfont is missing ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Midi Kit | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): To be tested : http://www.ibiblio.org/thammer/HammerSound/localfiles/soundfonts/FluidR3122501.zip -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:28:34 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:28:34 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] can't be controlled by a mouse anymore In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.29293a3994036281060959848b235c3e@haiku-os.org> #1310: [GLTeapot] can't be controlled by a mouse anymore ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by korli): This bug is only exposed with 1 CPU machine and VMs. Is it your test case ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 15:19:15 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 13:19:15 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.8b439ea5a329196419e07813394c526f@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: siarzhuk Type: bug | Status: assigned Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by siarzhuk): * status: new => assigned Comment: Hm... it looks a bit suspect. Actual repository code already have this fix for 6-->10 conversion. Please left this bug opened until I check my working copy, that is targeted to cvs at sourceforge. It is possible that it still have some changes, that are not commited. The version, we have now in Haiku repository was transferred directly from my CVS at sis4be.sf.net. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 17:32:41 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 15:32:41 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] can't be controlled by a mouse anymore In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.5347a9fe6317ff488ac43b95fd58328a@haiku-os.org> #1310: [GLTeapot] can't be controlled by a mouse anymore ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Yes it is. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 20:25:47 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 18:25:47 -0000 Subject: [Haiku-bugs] [Haiku] #1464: Broken filesystem In-Reply-To: <042.ad13e25b1cf0cd07b3a83c5828412d59@haiku-os.org> References: <042.ad13e25b1cf0cd07b3a83c5828412d59@haiku-os.org> Message-ID: <051.05bd54cbf8d87eb0d4f82c4d4c783604@haiku-os.org> #1464: Broken filesystem ---------------------------+------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kaliber): I think this ticket can be closed as fixed. Seems that it was caused by some of VM bug(s). I cannot reproduce this again with current version of Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:27:40 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:27:40 -0000 Subject: [Haiku-bugs] [Haiku] #573: [Media] crash in BMenuBar In-Reply-To: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> References: <040.fd17dcff16b629d7aa86311d52a44bf2@haiku-os.org> Message-ID: <049.b30d1adef577599209fa2450d7d99f9c@haiku-os.org> #573: [Media] crash in BMenuBar ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by pieterpan): Is fixed for me (I reported it in #1417) Well done! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:28:14 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:28:14 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) Message-ID: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) -----------------------+---------------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Using the latest revision (r22589) to test to see if #1417 was fixed. (it is, btw) Have a core2duo laptop with ahci. Unfortunately now I'm greeted with a PANIC. Maybe VM or AHCI related, but AHCI has worked well before. {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0x31, ip 0x802c42c1 }}} See attached bt. Sorry, no serial debug log, as the laptop doesn't have serial port. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:35:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:35:10 -0000 Subject: [Haiku-bugs] [Haiku] #1464: Broken filesystem In-Reply-To: <042.ad13e25b1cf0cd07b3a83c5828412d59@haiku-os.org> References: <042.ad13e25b1cf0cd07b3a83c5828412d59@haiku-os.org> Message-ID: <051.3d083a8ffd9d688c25e71b17284a8d60@haiku-os.org> #1464: Broken filesystem ---------------------------+------------------------------------------------ Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:41:06 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:41:06 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) In-Reply-To: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> References: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> Message-ID: <053.b8a7a4ae4c60cfdc7f2f35efdfa21e41@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) ------------------------+--------------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by pieterpan): Forgot to mention that it continues to boot if I enable console output -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:46:27 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:46:27 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) In-Reply-To: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> References: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> Message-ID: <053.3f4f4fea14b310e0d9d99650eaebf806@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) ---------------------------+------------------------------------------------ Reporter: pieterpan | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by korli): * owner: axeld => marcusoverhagen * component: - General => Drivers/Disk -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 21:48:30 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 19:48:30 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) In-Reply-To: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> References: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> Message-ID: <053.26fb74f9070135d17d66f436ad276550@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => axeld * component: Drivers/Disk => System/Kernel Comment: This appears to be the same cause as bug #1434 The device manager loads the driver and passes an invalid cookie pointer -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 14:36:49 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 12:36:49 -0000 Subject: [Haiku-bugs] [Haiku] #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage In-Reply-To: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> References: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> Message-ID: <050.7b85452585b3b6bbb16f9e0e886168eb@haiku-os.org> #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage ----------------------------+----------------------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by korli): * component: Servers/media_server => Drivers/Audio -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 16 16:25:50 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 16 Oct 2007 14:25:50 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.c6e6fdffd47faa27442c72d29acb438e@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension -----------------------------+---------------------------------------------- Reporter: hauser | Owner: phoudoin Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by phoudoin): Replying to [comment:5 diver]: > Philippe, i guess you forgot to commit something? Indeed. The app/server crash/BBitmap failed assertion is not fixed yet. I didn't found the time to fix it last night, as the initial quick fix I had in mind for Mesa Software Renderer add-on was not enough, just postponing the crash a few calls later (in mesa code, not anymore in app_server). I will try to do it tonight... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 17 02:32:11 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 17 Oct 2007 00:32:11 -0000 Subject: [Haiku-bugs] [Haiku] #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage In-Reply-To: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> References: <041.aef0e30d8891ed34fce951ff7f901c5c@haiku-os.org> Message-ID: <050.f2307903515a6154b42f31329883ca21@haiku-os.org> #1425: Echo driver: sound dropouts with FireFox and 100%CPU usage ----------------------------+----------------------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tigerdog): Korli, this may be related to interrupt-sharing. I was able to eliminate the dropouts by making sure the card did not share an IRQ with any other device. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 17 11:08:59 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 17 Oct 2007 09:08:59 -0000 Subject: [Haiku-bugs] [Haiku] #1577: USB/EHCI transfers sometimes time out In-Reply-To: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> References: <040.0bb0062af3e87dbce6243f014a18b9e0@haiku-os.org> Message-ID: <049.1d348114d259a9c9299dbb0780acb96c@haiku-os.org> #1577: USB/EHCI transfers sometimes time out --------------------------+------------------------------------------------- Reporter: axeld | Owner: siarzhuk Type: bug | Status: assigned Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by axeld): It (or something very similar) just happened again, attached another log. It just doesn't seem to happen very often anymore, now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 17 17:27:46 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 17 Oct 2007 15:27:46 -0000 Subject: [Haiku-bugs] [Haiku] #1579: app_server crashes (rev.22595) Message-ID: <039.6848e613b7a5662fd4bd51d13c820242@haiku-os.org> #1579: app_server crashes (rev.22595) --------------------------------+------------------------------------------- Reporter: rdmr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- When running haiku natively app_server crashes and shows(consoled?) debugger (but not KDL). Tested with rev.22595 and rev.22589 before. - At rev.22589 it was only showing blue screen than lands to gdb. - At rev 22595 it shows blue screen with mouse cursor but also with right LCD resolution(1680x1050). But this also lands to gdb.[[BR]] Added screenshot of rev.22595. I was able to use it natively before, but after EDID changes(i think this is the problem cause if i'm not wrong) I can't use it anymore. ---- Specifications: HP nx8220 - Centrino 1.86 GHz - ATI Radeon Mobility X600 (64MB) - 2GB Ram -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 17 18:08:55 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 17 Oct 2007 16:08:55 -0000 Subject: [Haiku-bugs] [Haiku] #1579: app_server crashes (rev.22595) In-Reply-To: <039.6848e613b7a5662fd4bd51d13c820242@haiku-os.org> References: <039.6848e613b7a5662fd4bd51d13c820242@haiku-os.org> Message-ID: <048.b102e2c4a473a03af9c7bf061725fed0@haiku-os.org> #1579: app_server crashes (rev.22595) ---------------------------------+------------------------------------------ Reporter: rdmr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by rdmr): Seems to be fixed at rev.22596. Tested with rev.22597 and can use Haiku natively again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 17 18:13:20 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 17 Oct 2007 16:13:20 -0000 Subject: [Haiku-bugs] [Haiku] #1579: app_server crashes (rev.22595) In-Reply-To: <039.6848e613b7a5662fd4bd51d13c820242@haiku-os.org> References: <039.6848e613b7a5662fd4bd51d13c820242@haiku-os.org> Message-ID: <048.173e10520c77042e9da3947acc92bfbb@haiku-os.org> #1579: app_server crashes (rev.22595) ---------------------------------+------------------------------------------ Reporter: rdmr | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Hm, actually, r22595 should have fixed this problem already; I guess I'll have to look into it later, again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 15:53:24 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 13:53:24 -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.9c91ece85169ac07031b3ad574ab8fa4@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by axeld): Can you still reproduce this with r22614? At least I've fixed a few deadlock situations there. The Time&Date thing is really strange, though - that sounds like a different kind of deadlock. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 16:01:01 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 14:01:01 -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.070465efbf567b032809f21d6bce8940@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:15 axeld]: > Can you still reproduce this with r22614? At least I've fixed a few deadlock situations there. > The Time&Date thing is really strange, though - that sounds like a different kind of deadlock. I could reproduce that thing too, but by creating a new project with BeIDE. The GUI was all frozen, except the mouse pointer (which, AFAIK, is moved from another thread). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 18:45:45 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 16:45:45 -0000 Subject: [Haiku-bugs] [Haiku] #1566: lockf() not implemented In-Reply-To: <042.6a9cfbace4f6f891ec1ff46c546ac350@haiku-os.org> References: <042.6a9cfbace4f6f891ec1ff46c546ac350@haiku-os.org> Message-ID: <051.08240fc2971d86d3b42116ccfa836565@haiku-os.org> #1566: lockf() not implemented --------------------------+------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:1 bonefish]: > We do already have fcntl(F_GETLK/F_SETLK[W]) support, and it looks like lockf() can be fully mapped to it. I will have a look. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 19:29:57 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 17:29:57 -0000 Subject: [Haiku-bugs] [Haiku] #1479: Laptops fail to shutdown or restart properly In-Reply-To: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> References: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> Message-ID: <051.b414e064ab247e85e8ff3e146f8c9636@haiku-os.org> #1479: Laptops fail to shutdown or restart properly ----------------------+----------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All ----------------------+----------------------------------------------------- Comment (by axeld): Are there any problems left after r22617? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 19:30:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 17:30:11 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.ed3149ec680b6b18a990b60ea89ded29@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Can you reproduce this problem with r22617 or later? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 18 19:35:15 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 18 Oct 2007 17:35:15 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.9e516486b2f6f06dd003fc6b8230510c@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): Will give it a try, though depending on work that may have to wait for the weekend. Is your laptop no longer having issues? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 20 03:39:34 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 20 Oct 2007 01:39:34 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.aa59563660c6537aac89fd364e3a7c87@haiku-os.org> #1508: Odd behavior from shutdown -r ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): Confirmed as fixed, I get a correct reboot now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 20 13:30:48 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 20 Oct 2007 11:30:48 -0000 Subject: [Haiku-bugs] [Haiku] #1570: [PackageInstaller] wont quit correctly In-Reply-To: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> References: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> Message-ID: <049.7eb12c1f9cd8035ab49a909cfa8fbea2@haiku-os.org> #1570: [PackageInstaller] wont quit correctly ----------------------------------------------+----------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/PackageInstaller | Version: R1 development Resolution: | Platform: All ----------------------------------------------+----------------------------- Comment (by sil2100): I'll look into this as soon as I get my late work done. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 20 23:16:12 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 20 Oct 2007 21:16:12 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement Message-ID: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement -------------------------------+-------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Platform: x86 | -------------------------------+-------------------------------------------- The mouse freezes after moving the pointer briefly. Most of the time the mouse freeze is permanent, but in some cases it is intermittent. The keyboard remains functional, as does (at least apparently) the rest of the system. This was on r22626 nightly build running on HP Pavillion ZV5000 laptop with builtin PS/2 mousepad. FWIW, Haiku has been running on this hardware flawlessly for a long time, until I noticed this problem with the above- mentioned nightly build. Two syslogs attached: 1) Permanent freeze (syslog_1) 2) Intermittent mouse freeze (syslog_2) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 21 11:01:48 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 21 Oct 2007 09:01:48 -0000 Subject: [Haiku-bugs] [Haiku] #1508: Odd behavior from shutdown -r In-Reply-To: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> References: <044.be47552e93ad8ff1a02868b6fe58a2f3@haiku-os.org> Message-ID: <053.f1b8148e37dc14ddca89290676ad603a@haiku-os.org> #1508: Odd behavior from shutdown -r -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: System/Kernel => Drivers/Keyboard/PS2 Comment: Great, thanks! So that binary search recompile hours have paid off :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 21 11:26:10 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 21 Oct 2007 09:26:10 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.c0aa9f9c40e4ed7f5e3f0ecd2ee1368e@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by axeld): That could be caused by r22617 - I reverted an older change (r20883) in the PS/2 bus manager that caused many systems to lock up instead of reboot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 21 23:55:01 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 21 Oct 2007 21:55:01 -0000 Subject: [Haiku-bugs] [Haiku] #1570: [PackageInstaller] wont quit correctly In-Reply-To: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> References: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> Message-ID: <049.46e600213acca77ca2b5c005d8790f68@haiku-os.org> #1570: [PackageInstaller] wont quit correctly ----------------------------------------------+----------------------------- Reporter: diver | Owner: sil2100 Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/PackageInstaller | Version: R1 development Resolution: | Platform: All ----------------------------------------------+----------------------------- Changes (by korli): * owner: axeld => sil2100 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 06:25:45 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 04:25:45 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater Message-ID: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater --------------------------+------------------------------------------------- Reporter: kad77 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- I've discovered that the 'configure' scripts for legacy gcc and gcc4 will fail if you are using a texinfo package version 4.10 or above. The buildtools will not compile without 'makeinfo'. This updated package will likely hit more that Fedora 7 and Arch in the semi-near future. The script checks for 'makeinfo' version 4.4 or greater, but due to the exact regex used, 'configure' fails to recognize 4.10 and 4.11 are 'or greater'... and 'makeinfo' is not found, build fails. Look for this section in the two configure scripts: {{{ if ${MAKEINFO} --version \ | egrep 'texinfo[^0-9]*([1-3][0-9]|4\.[4-9]|[5-9])' >/dev/null 2>&1; then }}} I have made a slight modification, which fixes the build problem: {{{ egrep 'texinfo[^0-9]*([1-3][0-9]|4\.([4-9]|[1-9][0-9])|[5-9])' >/dev/null 2>&1; then }}} While this small change works for me, I did not test the fix on an older version of texinfo - though it should work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 06:35:36 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 04:35:36 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.c11048193fc054660c7a331ea872481d@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by kad77): While it is the ''buildtools'' sections I was referring to, it is the '''binutils''' configure script that the fix should be applied to. Patch the main binutils/configure script in both legacy gcc and gcc4 and things should work properly again with more recent texinfo builds. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 12:31:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 10:31:18 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.8099fd3378d22ea256dac02312e3b193@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): I rewrote DirectWindow.h. Should we keep track of the headers which are already rewritten in some way ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 13:41:13 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 11:41:13 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.5194393d051a4874385b8960314107d6@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): Yeah, just add a "Done" section in the description and move the header from the current list to this section. It should be good enough :) Thanks for looking into this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 14:09:48 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 12:09:48 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.d918a78b387549ec3e45e1fd5069a14f@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Would it make sense to reuse the "server_read_only_memory" area ? Currently it's only 4096 byte, though, so it'd need to be enlarged. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 16:29:40 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 14:29:40 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.cab5272f305900187efb1de409ba30a3@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Sure, why not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 16:34:09 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 14:34:09 -0000 Subject: [Haiku-bugs] [Haiku] #505: First click on BMenuBar will show empty MenuWindow In-Reply-To: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> References: <040.40190308ce66371cc7f5437d80c9bc43@haiku-os.org> Message-ID: <049.fae05df030c5b6db27ffbbd299193398@haiku-os.org> #505: First click on BMenuBar will show empty MenuWindow ------------------------+--------------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:26 axeld]: > Sure, why not. Ok. I already did that locally, but for some reason haiku doesn't boot on qemu anymore. And vmware doesn't work anymore after upgrading to ubuntu 7.10. Great. That will have to wait. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 17:00:36 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 15:00:36 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.9f99fc4fcdfdcb06f4b1e123b2c8686e@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Old description: > Here is a list in headers/os. They should be reported in headers/build/. > > headers/os/add-ons/graphics/Accelerant.h > headers/os/add-ons/graphics/GraphicsCard.h > headers/os/add-ons/input_server/InputServerDevice.h > headers/os/add-ons/input_server/InputServerFilter.h > headers/os/add-ons/input_server/InputServerMethod.h > headers/os/add-ons/tracker/TrackerAddOn.h > headers/os/app/PropertyInfo.h > headers/os/be_apps/NetPositive/NetPositive.h > headers/os/device/A2D.h > headers/os/device/CAM.h > headers/os/device/D2A.h > headers/os/device/DigitalPort.h > headers/os/device/Joystick.h > headers/os/device/scsi.h > headers/os/device/SerialPort.h > headers/os/drivers/atomizer.h > headers/os/drivers/bus_manager.h > headers/os/drivers/ISA.h > headers/os/drivers/midi_driver.h > headers/os/drivers/PCI.h > headers/os/drivers/USB_printer.h > headers/os/drivers/USB_rle.h > headers/os/drivers/USB_spec.h > headers/os/game/DirectWindow.h > headers/os/interface/ChannelControl.h > headers/os/interface/ChannelSlider.h > headers/os/interface/Input.h > headers/os/interface/MenuBar.h > headers/os/interface/MultiChannelControl.h > headers/os/interface/OptionControl.h > headers/os/interface/OptionPopUp.h > headers/os/interface/PopUpMenu.h > headers/os/interface/PrintJob.h > headers/os/interface/TextView.h > headers/os/kernel/image.h > headers/os/kernel/scheduler.h > headers/os/mail/E-mail.h > headers/os/media/BufferConsumer.h > headers/os/media/BufferGroup.h > headers/os/media/Buffer.h > headers/os/media/BufferProducer.h > headers/os/media/Controllable.h > headers/os/media/FileInterface.h > headers/os/media/MediaAddOn.h > headers/os/media/MediaDefs.h > headers/os/media/MediaEventLooper.h > headers/os/media/MediaFiles.h > headers/os/media/MediaFormats.h > headers/os/media/MediaNode.h > headers/os/media/MediaRoster.h > headers/os/media/ParameterWeb.h > headers/os/media/PlaySound.h > headers/os/media/RealtimeAlloc.h > headers/os/media/SoundFile.h > headers/os/media/Sound.h > headers/os/media/SoundPlayer.h > headers/os/media/TimeCode.h > headers/os/media/TimedEventQueue.h > headers/os/media/TimeSource.h > headers/os/net/net_settings.h > headers/os/opengl/GLView.h > headers/os/translation/BitmapStream.h > headers/os/translation/TranslationDefs.h > headers/os/translation/TranslationErrors.h > headers/os/translation/TranslationKit.h > headers/os/translation/TranslatorAddOn.h > headers/os/translation/TranslatorFormats.h New description: Here is a list in headers/os. They should be reported in headers/build/. headers/os/add-ons/graphics/Accelerant.h headers/os/add-ons/graphics/GraphicsCard.h headers/os/add-ons/input_server/InputServerDevice.h headers/os/add-ons/input_server/InputServerFilter.h headers/os/add-ons/input_server/InputServerMethod.h headers/os/app/PropertyInfo.h headers/os/be_apps/NetPositive/NetPositive.h headers/os/device/A2D.h headers/os/device/CAM.h headers/os/device/D2A.h headers/os/device/DigitalPort.h headers/os/device/Joystick.h headers/os/device/scsi.h headers/os/device/SerialPort.h headers/os/drivers/atomizer.h headers/os/drivers/bus_manager.h headers/os/drivers/ISA.h headers/os/drivers/midi_driver.h headers/os/drivers/PCI.h headers/os/drivers/USB_printer.h headers/os/drivers/USB_rle.h headers/os/drivers/USB_spec.h headers/os/interface/ChannelControl.h headers/os/interface/ChannelSlider.h headers/os/interface/Input.h headers/os/interface/MenuBar.h headers/os/interface/MultiChannelControl.h headers/os/interface/PopUpMenu.h headers/os/interface/PrintJob.h headers/os/interface/TextView.h headers/os/kernel/scheduler.h headers/os/mail/E-mail.h headers/os/media/BufferConsumer.h headers/os/media/BufferGroup.h headers/os/media/Buffer.h headers/os/media/BufferProducer.h headers/os/media/Controllable.h headers/os/media/FileInterface.h headers/os/media/MediaAddOn.h headers/os/media/MediaDefs.h headers/os/media/MediaEventLooper.h headers/os/media/MediaFiles.h headers/os/media/MediaFormats.h headers/os/media/MediaNode.h headers/os/media/MediaRoster.h headers/os/media/ParameterWeb.h headers/os/media/PlaySound.h headers/os/media/RealtimeAlloc.h headers/os/media/SoundFile.h headers/os/media/Sound.h headers/os/media/SoundPlayer.h headers/os/media/TimeCode.h headers/os/media/TimedEventQueue.h headers/os/media/TimeSource.h headers/os/net/net_settings.h headers/os/opengl/GLView.h headers/os/translation/BitmapStream.h headers/os/translation/TranslationDefs.h headers/os/translation/TranslationErrors.h headers/os/translation/TranslationKit.h headers/os/translation/TranslatorAddOn.h headers/os/translation/TranslatorFormats.h Done: headers/os/add-ons/tracker/TrackerAddOn.h headers/os/game/DirectWindow.h headers/os/kernel/image.h headers/os/interface/OptionControl.h headers/os/interface/OptionPopUp.h -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 17:11:07 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 15:11:07 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.7f8a3de8e7afb10f700fd2edbca62a49@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): By the way, do we really need all the headers reported in headers/build ? At least, I guess we don't need the whole interface kit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 21:24:20 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 19:24:20 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.2f270b0f79d1aa3427a0c106d955df55@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): FWIW, for testing purposes I replaced... /system/add-ons/kernel/bus_managers/ps2 /system/add-ons/kernel/drivers/bin/ps2_hid ...with the files from r22614, but it did not seem to have any effect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 22:31:37 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 20:31:37 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.1f90878e366864c03f9ad13c9e037216@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): Replying to [comment:6 jackburton]: > By the way, do we really need all the headers reported in headers/build ? At least, I guess we don't need the whole interface kit. Nope, feel free to remove whatever is not needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 22 22:36:52 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 20:36:52 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.57e88e87bf9cd89c41a1ed32ccfa124d@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Can you attach this change as a patch please. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 00:30:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 22 Oct 2007 22:30:18 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.b1a04e9161f9d541034315e0dc521d16@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by axeld): So it's likely caused by another change, and probably not related to the PS/2 driver at all, I suppose. Can you by any chance pin down the revision (at least more or less) since when you encounter these problems? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 09:52:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 07:52:32 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.ce4cf6b61df165db0aa5ee9c9720a6f4@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): Since I don't have the ability to build from source, I tested again with a fresh install of the oldest nightly build available on haikuhost.com. This was the same build that I had used for my previous test (r22614), so as expected, it did not work. :) I am a bit at a lose as to whether there is anything else that I can do to help the devs figure out what the problem is. If there is, feel free to let me know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 13:09:48 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 11:09:48 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.09e1c625e351054b04872b2dcfb0ff8c@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by axeld): Thanks for your help so far; this is just one more reason to finally get an image archive up and running. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 15:29:35 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 13:29:35 -0000 Subject: [Haiku-bugs] [Haiku] #1178: NetworkStatus replicant does not persist In-Reply-To: <039.31c4074f057b5a2a5fbe7c8ef923f985@haiku-os.org> References: <039.31c4074f057b5a2a5fbe7c8ef923f985@haiku-os.org> Message-ID: <048.0d23814c561033d3f09510f00f7eae0f@haiku-os.org> #1178: NetworkStatus replicant does not persist -------------------------------+-------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: When you reinstall Haiku, all add-ons are gone. I guess that might be your problem, because otherwise, I can't reproduce this. In any way, the original bug has been fixed, so please don't reopen this ticket. If your problem persists, and is reproducible via a reboot from a freshly installed Haiku, then please open a new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 19:25:32 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 17:25:32 -0000 Subject: [Haiku-bugs] [Haiku] #1582: Artifacts while resizing Message-ID: <044.ade7620cd1932f95a902871b9510bb5c@haiku-os.org> #1582: Artifacts while resizing ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/StyledEdit | Version: R1 development Platform: All | ---------------------------------------+------------------------------------ This is in vmware, r22624. Resizing StyledEdit leaves artifacts, but only if you deactivate the "Wrap Lines" option. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 19:27:10 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 17:27:10 -0000 Subject: [Haiku-bugs] [Haiku] #1582: Artifacts while resizing In-Reply-To: <044.ade7620cd1932f95a902871b9510bb5c@haiku-os.org> References: <044.ade7620cd1932f95a902871b9510bb5c@haiku-os.org> Message-ID: <053.e1d3f5dd198297a9cc6f21274cd85804@haiku-os.org> #1582: Artifacts while resizing ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/StyledEdit | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by humdinger): Oh, you should open a text file for that. Doesn't work with an empty StyledEdit window... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 23 20:04:56 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 23 Oct 2007 18:04:56 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing Message-ID: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> #1583: Fallback when Preferred App is missing -------------------------------+-------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- This is in vmware, r22624. I have several files, saved in BeOS R5 that have the attribute BEOS:PREF_APP set to application/x-vnd.Be-STEE. That's StyledEdit's signature in BeOS. Haiku's is changed to application/x-vnd.Haiku-StyledEdit. Consequently the system doesn't find the preferred application and offers to find an app to open the file. Wouldn't it make sense to fallback to the app determined by the file's MIME type? (In my case that would be text/x-trackerbase, which defaults to StyledEdit) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 07:42:08 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 05:42:08 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.4b376963ada009c24a761640821cd8d9@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by marcusoverhagen): The syslog lists in both cases KERN: ps2: hot removal of input/mouse/ps2/3 This is only printed on a very specific condition, as defined by the PS/2 active multiplexing specification, the error bit must be set, and data must match 0xfd. {{{ if (dev->history[0].error && data == 0xfd) { INFO("ps2: hot removal of %s\n", dev->name); }}} In the intermittent mouse freeze case, the mouse appears to be reconnected and disconnected a lot of times. Are you sure that you mouse and/or PS/2 connector is working correct? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 08:15:18 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 06:15:18 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.10fb8deb673a123c5e2cfa54d92fa802@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): Hi Marcus. Thanks for looking into this bug. This bug appears only in Haiku running in my laptop with a built-in mousepad. The mouse(pad) works just fine in ZETA/Win/Ubuntu, so I suppose that the hardware is not faulty. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 08:25:24 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 06:25:24 -0000 Subject: [Haiku-bugs] [Haiku] #1582: Artifacts while resizing In-Reply-To: <044.ade7620cd1932f95a902871b9510bb5c@haiku-os.org> References: <044.ade7620cd1932f95a902871b9510bb5c@haiku-os.org> Message-ID: <053.e62d02849bee54e81603a7cf1409b4d1@haiku-os.org> #1582: Artifacts while resizing ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/StyledEdit | Version: R1 development Resolution: duplicate | Platform: All ----------------------------------------+----------------------------------- Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: dup of #1532 and #1520. And most probably has the same cause as #1527. StyledEdit calls Refresh() with the correct parameters, so the problem is in the invalidation itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 18:53:06 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 16:53:06 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.6901fb6083d88749ab6a6a701ceef632@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by tombhadac): Ive attached an patch for it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 21:24:55 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 19:24:55 -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.b35ba977b8e3031a1e93632560048c37@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: | Platform: All ----------------------------------+----------------------------------------- Changes (by axeld): * cc: anxiety (added) Comment: Any news from this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 22:55:57 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 20:55:57 -0000 Subject: [Haiku-bugs] [Haiku] #1479: Laptops fail to shutdown or restart properly In-Reply-To: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> References: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> Message-ID: <051.70f28f58b98e84a84ba7007289a58a06@haiku-os.org> #1479: Laptops fail to shutdown or restart properly ----------------------+----------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All ----------------------+----------------------------------------------------- Comment (by scottmc): I tried it last night using r22629 and now the Thinkpad 570E won't even boot up all the wat into Haiku. It gets stuck on the black screen with the Haiku logo. I tried enabling onscreen debug output but it doesn't show up either. I tried rolling back to a Haiku image I had from Oct3rd and that one boots into Haiku just fine on this same PC. So I tried it again this morning with r22697 and got the same results as with r22629. Not what happened but something between Oct3rd and r22629 broke Haiku on this laptop. I can try hooking it up tomorrow to get serial debug output from it to help figure out where it's getting stuck. Also I did try disabling APM and ACPI in the kernel file on the r22629 build, but it still hung. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 24 23:26:10 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 21:26:10 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver Message-ID: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> #1584: Fonts not encoded by PDF printer driver ------------------------+--------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Platform: x86 | ------------------------+--------------------------------------------------- I've been using the font SGreek to write in the Greek alphabet. Unfortunately, printing a document with it from Gobe Productive or from StyledEdit comes out with the SGreek text in a normal Latin font rather than how it looks in the respective programs. The printer driver options have it set to encode the SGreek font, but it doesn't seem to do that. Also I've ruled out it being an issue with BePDF because I tried looking at these PDFs under Windows and they look the same. Kev -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 01:07:08 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 23:07:08 -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.aa39e8c917db3310eef6c885b8f91c27@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: | Platform: All ----------------------------------+----------------------------------------- Comment (by stippi): Could someone explain to me how this is "supposed" to work? Am I creating the correct kind of queries? Is it too late in the day and my brain too tired? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 01:41:05 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 24 Oct 2007 23:41:05 -0000 Subject: [Haiku-bugs] [Haiku] #1423: App Network Preferences fails to recover gateway ip after reboot In-Reply-To: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> References: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> Message-ID: <053.f2735afe3b47858c3f39ad531160fae8@haiku-os.org> #1423: App Network Preferences fails to recover gateway ip after reboot ---------------------------------+------------------------------------------ Reporter: sicutdeux | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/net_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Changes (by stippi): * owner: stippi => axeld * component: - Preferences/Network => Servers/net_server * milestone: R1 => R1/alpha Old description: > The app works nice except after a reboot it doesn't recover the ip from > the gateway, also the app can't create the /etc/resolv.conf, i had to > touch it manually before the app save the settings on it. New description: Gateway not added to routes on boot, but only when triggering the settings to be reloaded. Comment: I investigated a bit, and this should be a net_server bug, not a bug of the Network preflet. With the exact same settings file: on boot, net_server fails to add the gateway route in manual settings mode. When the Network preflet is used to (re)write the exact same settings file, the gateway is added propery. At first I thought it might be a problem in which order the settins are applied (the gateway is considered as pretty much the first thing), I thought it might need the other settings to be originally applied to work, but moving the gateway stuff down as the last thing in NetServer.cpp didn't help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 09:29:01 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 07:29:01 -0000 Subject: [Haiku-bugs] [Haiku] #1423: App Network Preferences fails to recover gateway ip after reboot In-Reply-To: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> References: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> Message-ID: <053.6557b1385d05efe1220ea064da6c0cdf@haiku-os.org> #1423: App Network Preferences fails to recover gateway ip after reboot ---------------------------------+------------------------------------------ Reporter: sicutdeux | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/net_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): I guess we are talking about the manual configuration, and not DHCP? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 10:52:04 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 08:52:04 -0000 Subject: [Haiku-bugs] [Haiku] #1423: App Network Preferences fails to recover gateway ip after reboot In-Reply-To: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> References: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> Message-ID: <053.6208e55372154e461fd45692deddf131@haiku-os.org> #1423: App Network Preferences fails to recover gateway ip after reboot ---------------------------------+------------------------------------------ Reporter: sicutdeux | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/net_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): Yes, manual configuration, not DHCP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 11:24:51 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 09:24:51 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) In-Reply-To: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> References: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> Message-ID: <053.d94367c009cf463c5f4dbfe273f08608@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Actually the problem resides in the device manager. KDiskDeviceManager::InitialDeviceScan(). Then the devfs triggers a device scan with "/dev", probe_for_driver_modules() includes the ahci pci device in the scan because its type "/dev/disk" starts with "/dev" (if it was an exact type match, it wouldn't find the disk devfs directory anyway). The ahci driver attachs its device to the ahci pci device. Then the devfs triggers a device scan with "/dev/disk", probe_for_driver_modules() includes the ahci pci device in the scan because its type "/dev/disk" starts with "/dev/disk". The ahci driver attachs again to the same ahci pci device. A possible fix would be to check whether a pci device has already a child device attached, and avoid a new scan in probe_for_driver_modules() or register_supporting_child_devices() when node->children is not null. Thoughts ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 12:51:33 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 10:51:33 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing In-Reply-To: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> References: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> Message-ID: <053.81905eff1cd4080f73f4cfd4e4724044@haiku-os.org> #1583: Fallback when Preferred App is missing --------------------------------+------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by stippi): There is different sides to this situation. For one thing, there could be something wrong with your installation (like you accidentally removed your preferred app or something). In that case, you might want this warning, otherwise you might be wondering why the file does not open in the app you have configured. But I don't know how likely that is. On the other hand, you could have gotten the files from someone else, similar to your situation above, in which case the system should not bother you with the missing app and simply open the file with whatever other app you do have. Since the system does offer you to find another app though, maybe that's good enough. It could additionally offer an easy way to remove the "preferred app" attribute of that particular file. In any case, it depends on how common we think those situations are in which you would want the notice. Thoughts? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 12:58:02 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 10:58:02 -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.d007f9901290b77a564e8257673b37c2@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): diver, can you still reproduce the deadlock when switching workspaces? I think I have fixed a deadlock when using the keyboard shortcuts to switch workspaces, while Axel later fixed some more that affected workspace switching with the mouse, if I understand correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 14:48:18 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 12:48:18 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu Message-ID: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> #1585: Haiku doesn't boot with qemu ---------------------------+------------------------------------------------ Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Lately I'm forced to test haiku under qemu (it has been some time). I found out it doesn't boot. It locks up on the logo screen. Attached is the serial log output. This is under ubuntu 7.10 with qemu 0.9.0. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:13:28 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:13:28 -0000 Subject: [Haiku-bugs] [Haiku] #634: [app_server] crash in Painter::FillRectNoClipping() In-Reply-To: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> References: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> Message-ID: <049.fb330cb62dec0f50c6f0129fb8b72c22@haiku-os.org> #634: [app_server] crash in Painter::FillRectNoClipping() ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: critical | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: I cannot make app_server crash at all with any of the ways described here: * Dragging Deskbar arround like mad while at the same time switching workspaces using the keyboard * Toggling ShowImage full screen mode, also while at the same time switching workspaces I think this bug has been fixed by fixing some of the race conditions in app_server that had to do with unlocking/locking the window lock to switch the locking type (single->all->single). I am not sure, but at least I cannot produce any app_server crash and neither any lockups. So I am closing this bug, please reopen if you can still reproduce it, but please update the description for how to reproduce it. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:20:36 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:20:36 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu In-Reply-To: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> References: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> Message-ID: <054.e510b2cd52bed84cec023de9ad311239@haiku-os.org> #1585: Haiku doesn't boot with qemu ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by stippi): Same here. In the meantime, you can boot Haiku in VMWare Player, which appears to be not supported by 7.10 at the moment, but when you download the player from the VMWare site, you can install it (run the install script with sudo and answer yes to pretty much everything) and it works fine and runs Haiku well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:24:03 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:24:03 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu In-Reply-To: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> References: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> Message-ID: <054.ccdd8421659d58677f371ea31cb4ba9d@haiku-os.org> #1585: Haiku doesn't boot with qemu ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:1 stippi]: > Same here. In the meantime, you can boot Haiku in VMWare Player, which appears to be not supported by 7.10 at the moment, Yeah, that's basically why I switched to qemu :) > but when you download the player from the VMWare site, you can install it (run the install script with sudo and answer yes to pretty much everything) and it works fine and runs Haiku well. Yeah I've read about this solution, thank you. But being a lazy man, I'd prefer the "ready" package :). I hoped they provided it earlier, though... sigh, I guess I'll have to dowload the player from the official site... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:27:13 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:27:13 -0000 Subject: [Haiku-bugs] [Haiku] #634: [app_server] crash in Painter::FillRectNoClipping() In-Reply-To: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> References: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> Message-ID: <049.36c47022d66b213d5b6a84f5a833fb51@haiku-os.org> #634: [app_server] crash in Painter::FillRectNoClipping() ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: closed => reopened * resolution: fixed => Comment: Ah s**t, I can still reproduce it: * Make sure there are a couple of windows showing on screen, place them so that there should be repaint events when dragging Deskbar in the next step * I had the Workspaces applet open, don't know if it makes a difference, maybe it's even the one that crashes? * Drag Deskbar arround like mad * At the same time, switch Workspaces forth and back using the keyboard shortcuts -> Should crash eventually in Painter::FillRectNoClipping() Since it's crashing in *Painter*, maybe it happens only when there is no hardware accelerated drawing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:43:36 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu In-Reply-To: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> References: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> Message-ID: <054.8896ee9a6d8607ec79024b9806f91a90@haiku-os.org> #1585: Haiku doesn't boot with qemu ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by axeld): I can reproduce the problem here as well; it seems to be the same bug that makes "sync" problematic in VMware, so I guess Qemu has improved/changed its IDE emulation. In any way, it boots fine when you turn off IDE DMA in the boot menu. HTH until it gets fixed :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:43:49 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:43:49 -0000 Subject: [Haiku-bugs] [Haiku] #562: [Gobe Productive] doesnt load splash screen correctly In-Reply-To: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> References: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> Message-ID: <058.24a6fc1c7d9b0c925e4360e7d26d228b@haiku-os.org> #562: [Gobe Productive] doesnt load splash screen correctly -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by kvdman): * platform: => All Comment: I have this problem as well with libprefs. Found sources here: [http://bryan.varnernet.com/software/beos/libprefs/] Can download libprefs1.2.5 here: http://files.bebits.com/pub/mirror/beware/libraries/ Old libprefs info here: [http://www.beatjapan.org/mirror/www.be.com/beware/Libraries/libprefs.html] I've tried libprefs1.2.5 and 1.2.3 and get the elf loader errors ('incorrect elf header'). The splash screen loads but stops on loading preferences (doesn't crash). How do you get a backtrace if the program doesn't crash?? I've attached a screenshot using gdb and the 'start' command. Don't know if this helps. Funny, I'm using my copy of GobeProductive from Zeta that I bought, and you'd figure the library would be on Zeta's disk, but it's not. I've read that Gobe uses the library to load the preferences, so how does it work on Zeta without the library? thx -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:49:42 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:49:42 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.c1306c492367b9ba2b06db247ed90484@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: x86 -------------------------+-------------------------------------------------- Comment (by kev): Also FWIW I've tried varying the compression (high-low) and compatibility settings (1.3, 1.4) and it doesn't seem to make any difference. Kev -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:56:31 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:56:31 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.03bbe326d40c9a92a36d308d62f55db0@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: x86 -------------------------+-------------------------------------------------- Changes (by laplace): * status: new => assigned Comment: Thank you for the bug report. From you observation it seems the changed settings are ignored. I will look into that when I have time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 15:59:47 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 13:59:47 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.e81d175312057cef3a112fe9335f82eb@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: x86 -------------------------+-------------------------------------------------- Comment (by kev): Thanks, that'd be great. BTW, the version I'm using is the 2.0 Beta 1 on BeBits. If I'm able to use one from the build factory under R5.0.3 let me know, I'll try it (last time I did this, with networking, I broke my system a few times. ;) ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:02:22 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.93f8ac61cc34e44c4abb866a5ffc6e11@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by kvdman): I've attached a bt from ff2.0.8, it's different from the previous attachment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:04:51 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:04:51 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing In-Reply-To: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> References: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> Message-ID: <053.431534a3337aa69d1025b85338c0d3ac@haiku-os.org> #1583: Fallback when Preferred App is missing --------------------------------+------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by axeld): I'm a bit torn, too. In the case of "preferred app of document invalid" I think we should have the option of removing that and try again. If however the FileType defaults to an invalid app, that hint should be silently ignored IMO. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:07:53 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:07:53 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.701d1906420a335f6921ab6767905de4@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by kvdman): There seems to be a lot more errors if you start from an empty profile, bt attached. This is on rev22677 btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:35:46 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:35:46 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing In-Reply-To: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> References: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> Message-ID: <053.10d0bd61168516412211390917ce5eb4@haiku-os.org> #1583: Fallback when Preferred App is missing --------------------------------+------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by humdinger): I'd argue for the second solution, i.e. fallback to the preferred app for that MIME type as set in the FileTypes preferences. That's what it is for, you determine which app you want to open this kind of file by default. So, when you don't have the app installed that your collegue, who mailed you the file, prefers for that particular file, your own favorite app is launched. Just imagine your annoying collegue always sets BEOS:PREF_APP to "emacs" and you have only the correct editor installed: "vi"... :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:37:02 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:37:02 -0000 Subject: [Haiku-bugs] [Haiku] #1423: App Network Preferences fails to recover gateway ip after reboot In-Reply-To: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> References: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> Message-ID: <053.a3b242640e25cf82fb1c00cebd57d984@haiku-os.org> #1423: App Network Preferences fails to recover gateway ip after reboot ---------------------------------+------------------------------------------ Reporter: sicutdeux | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: Servers/net_server | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:41:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:41:11 -0000 Subject: [Haiku-bugs] [Haiku] #739: Haiku bootloader does not detect boot volume In-Reply-To: <052.bd0dfe8f1064142d5688c9aaae2457ad@haiku-os.org> References: <052.bd0dfe8f1064142d5688c9aaae2457ad@haiku-os.org> Message-ID: <061.4a7a0ecab05ff402be955e34545d426f@haiku-os.org> #739: Haiku bootloader does not detect boot volume --------------------------------+------------------------------------------- Reporter: kev at brantaero.com | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by kev): Just tried with the latest build and the latest build's makebootable, and I still get the same thing, no boot volume found. The text at the bottom when I highlight the rescan option says to insert a USB stick or Haiku CD --is HD booting temporarily not an option? I have a CDRW, can I make a Haiku CD from that? As for QEMU, attached are a log and screenshot, it seems to be behaving pretty similarly to before. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 16:43:14 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 14:43:14 -0000 Subject: [Haiku-bugs] [Haiku] #739: Haiku bootloader does not detect boot volume In-Reply-To: <052.bd0dfe8f1064142d5688c9aaae2457ad@haiku-os.org> References: <052.bd0dfe8f1064142d5688c9aaae2457ad@haiku-os.org> Message-ID: <061.9695abb6c0f4a8860f9707c9bb0bf411@haiku-os.org> #739: Haiku bootloader does not detect boot volume --------------------------------+------------------------------------------- Reporter: kev at brantaero.com | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by kev): Except the processor never stops (well, after a couple minutes, anyway) being pegged at 100% until I kill QEMU. Not sure if that's new. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 17:10:00 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 15:10:00 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu In-Reply-To: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> References: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> Message-ID: <054.843e51c6b85ea97ea222ede8479cbaa0@haiku-os.org> #1585: Haiku doesn't boot with qemu ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:3 axeld]: > I can reproduce the problem here as well; it seems to be the same bug that makes "sync" problematic in VMware, so I guess Qemu has improved/changed its IDE emulation. > In any way, it boots fine when you turn off IDE DMA in the boot menu. HTH until it gets fixed :-) That works, indeed. Weird, I was sure I checked all the items in the safe boot menu... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 17:16:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 15:16:11 -0000 Subject: [Haiku-bugs] [Haiku] #1423: App Network Preferences fails to recover gateway ip after reboot In-Reply-To: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> References: <044.1230dd9053998b22d870e911d4f546bc@haiku-os.org> Message-ID: <053.0c43b28cc66ee00b8daaa1e09c6d0c64@haiku-os.org> #1423: App Network Preferences fails to recover gateway ip after reboot ---------------------------------+------------------------------------------ Reporter: sicutdeux | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/net_server | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r22723. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 17:36:08 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 15:36:08 -0000 Subject: [Haiku-bugs] [Haiku] #562: [Gobe Productive] doesnt load splash screen correctly In-Reply-To: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> References: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> Message-ID: <058.dcee386764b0d54f2228f86f3b606206@haiku-os.org> #562: [Gobe Productive] doesnt load splash screen correctly -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Old description: > Gobe opens a small bordered window in the centre of the screen, yet no > controls > are visible. > Doesn't crash, just stays there waiting for vulcan. New description: Gobe opens a small bordered window in the centre of the screen, yet no controls are visible. Doesn't crash, just stays there waiting for vulcan. Comment (by axeld): The libprefs of that archive are in PEF format, it's an ancient R3 Intel executable :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 17:43:23 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 15:43:23 -0000 Subject: [Haiku-bugs] [Haiku] #1586: Queries: not case-insensitive for "Umlauts" Message-ID: <044.56857434cb3c25e1eca375a31e7de779@haiku-os.org> #1586: Queries: not case-insensitive for "Umlauts" ------------------------------------+--------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- This is in vmware, r22714. When you do a query for any filename containing "?ber", the generated formula is (name=="*?[bB][eE][rR]*"). The "Umlaut" is not case- insensitive. It should be (name=="*[??][bB][eE][rR]*") -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 17:56:18 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 15:56:18 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.76e3653092a664da2ffb97b6dcffa5a4@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by tqh): Are there any error messages to accompany those backtraces? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 18:28:36 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 16:28:36 -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.38e0f194dca8b686e5c34b93a75a8f15@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: | Platform: All ----------------------------------+----------------------------------------- Comment (by humdinger): Replying to [comment:7 stippi]: > Could someone explain to me how this is "supposed" to work? Am I creating the > correct kind of queries? Is it too late in the day and my brain too tired? I'm not sure you refer to your code so far or the principle in general from a user's perspective. If it's the latter... The Mail app should use the queries defined in /boot/home/mail/queries and fill out the search strings with the according ones of the current email. So, the template query "Same Sender" would look like this: ((MAIL:from=="*[tT][eE][sS][tT]*")&&(BEOS:TYPE=="text/x-email")) When invoking the menu "Query|Same Sender", Mail would replace the search string (or strings when someone created a query template with more than one attribute to search) with the MAIL:from attribute of the current email file. The same for "Same Subject", replacing MAIL:subject. And "Same Recipient" (only really useful when composing a mail or opening one from your Sent folder, since for anything else you'll yourself be the recipient... :) ), replacing MAIL:to Selecting "Edit Queries..." (which IMO should be renamed to "Create new Query...) should open the folder /boot/home/mail/queries and a "Find..." query window set to "E-Mail by Attribute". Then you can save your new query template via drag&drop. Existing queries are altered as usual by invoking them and choosing "Edit Query" (Alt-E) from its menu. I like the submenu approach in the Query menu (though that doesn't work right now, does it?). You can quickly open an email from there directly. There should be sanity checks if your query would have hundreds of results though... Maybe an entry after 20 items called "...more..." that would do the same thing as if you clicked on the parent menu entry, e.g. "Same Sender", which should open the query result window. Question is: How do you display the results in the submenu? If you query for Same Sender, showing the queried attribute "FROM" wouldn't make sense. I'd all be the Same Sender, of course... Here, the subject would be informative. Vice versa with Same Subject, where the sender (FROM) would be nice... I guess we'd have to settle on the ugly filename. If we don't special-case the above two queries. Or we forget about the submenu and just open the query result window. This is getting long. I apologise and will elaborate if you need more opinion :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:01:13 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:01:13 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.d13461e77dd195000dd3e76b1aa985bf@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: invalid | Platform: x86 -------------------------+-------------------------------------------------- Changes (by laplace): * status: assigned => closed * resolution: => invalid Comment: I have tested the version from SVN repository under Haiku and it seems to work fine. PDF files created from a sample text in StyledEdit using different setting have different file sizes, that's an indication that the settings are respected. Therefore I have closed this bug as "invalid". Maybe I have the time to build a new version for BeOS, but I cannot promise it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:05:29 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:05:29 -0000 Subject: [Haiku-bugs] [Haiku] #562: [Gobe Productive] doesnt load splash screen correctly In-Reply-To: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> References: <049.5dc37ed4ee1661fc2a396305d0d43e3b@haiku-os.org> Message-ID: <058.9d66089f0451fbfd160e8b3c957a8d0a@haiku-os.org> #562: [Gobe Productive] doesnt load splash screen correctly -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r22724. libprefs is built into Gobe Productive and looped endlessly, since the private _klock_node_() function was not implemented in Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:17:39 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:17:39 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.b18ad489d67aa2e195e6d553f67d43d0@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by kvdman): I copied the libraries in /components and in the root directory over to /home/config/settings/lib. It now almost starts, but seems to be lots of errors! GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 547 caused an exception: Segment violation Reading symbols from /ZETA/home/Desktop/firefox/libmozjs.so...(no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libmozjs.so Reading symbols from /ZETA/home/Desktop/firefox/libxpcom.so...(no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libxpcom.so Reading symbols from /ZETA/home/Desktop/firefox/libxpcom_core.so... (no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libxpcom_core.so Reading symbols from /ZETA/home/Desktop/firefox/libplds4.so...(no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libplds4.so Reading symbols from /ZETA/home/Desktop/firefox/libplc4.so... (no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libplc4.so Reading symbols from /ZETA/home/Desktop/firefox/libnspr4.so...(no debugging symbols found)...done. Loaded symbols for /ZETA/home/Desktop/firefox/libnspr4.so Reading symbols from /boot/beos/system/lib/libbe.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libbe.so Reading symbols from /boot/beos/system/lib/libroot.so...done. Loaded symbols for /boot/beos/system/lib/libroot.so Reading symbols from /boot/beos/system/lib/libtracker.so...done. Loaded symbols for /boot/beos/system/lib/libtracker.so Reading symbols from /boot/beos/system/lib/libgame.so...done. Loaded symbols for /boot/beos/system/lib/libgame.so Reading symbols from /ZETA/home/Desktop/firefox/libsmime3.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libsmime3.so Reading symbols from /ZETA/home/Desktop/firefox/libssl3.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libssl3.so Reading symbols from /ZETA/home/Desktop/firefox/libnss3.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libnss3.so Reading symbols from /ZETA/home/Desktop/firefox/libsoftokn3.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libsoftokn3.so Reading symbols from /ZETA/home/Desktop/firefox/libxpcom_compat.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libxpcom_compat.so Reading symbols from /boot/home/config/lib/libstdc++.r4.so...done. Loaded symbols for /boot/home/config/lib/libstdc++.r4.so Reading symbols from /boot/beos/system/lib/libnetwork.so...done. Loaded symbols for /boot/beos/system/lib/libnetwork.so Reading symbols from /boot/beos/system/lib/libtranslation.so...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libmedia.so...done. Loaded symbols for /boot/beos/system/lib/libmedia.so Reading symbols from /boot/beos/system/lib/libtextencoding.so...done. Loaded symbols for /boot/beos/system/lib/libtextencoding.so Reading symbols from /ZETA/home/Desktop/firefox/components/libmyspell.so...done.Loaded symbols for /ZETA/home/Desktop/firefox/components/libmyspell.so Reading symbols from /ZETA/home/Desktop/firefox/libfreebl3.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libfreebl3.so Reading symbols from /ZETA/home/Desktop/firefox/libnssckbi.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/libnssckbi.so Reading symbols from /ZETA/home/Desktop/firefox/components/libspellchecker.so...done. Loaded symbols for /ZETA/home/Desktop/firefox/components/libspellchecker.so [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /ZETA/home/Desktop/firefox/firefox-bin (547) thread firefox-bin (547)] 0x00bcb43d in nsGlobalWindow::HandleDOMEvent () (gdb) bt #0 0x00bcb43d in nsGlobalWindow::HandleDOMEvent () #1 0x00ba54ba in nsXULDocument::HandleDOMEvent () #2 0x00b9a323 in nsXULElement::HandleDOMEvent () #3 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #4 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #5 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #6 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #7 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #8 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #9 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #10 0x00b9a2d8 in nsXULElement::HandleDOMEvent () #11 0x00b9cd8f in nsXULElement::HandleChromeEvent () #12 0x00bcb69b in nsGlobalWindow::HandleDOMEvent () #13 0x00adb54a in nsDocument::HandleDOMEvent () #14 0x00aeface in nsGenericElement::HandleDOMEvent () #15 0x0095c9bd in PresShell::HandleEventInternal () #16 0x0095c57f in PresShell::HandleEvent () #17 0x00bbd88c in nsViewManager::HandleEvent () #18 0x00bbcc85 in nsViewManager::DispatchEvent () #19 0x00bb5f5d in HandleEvent () #20 0x008fc17f in nsWindow::DispatchEvent () #21 0x008fc1fd in nsWindow::DispatchWindowEvent () #22 0x00901209 in nsWindow::DispatchMouseEvent () #23 0x008fff7c in nsWindow::CallMethod () ---Type to continue, or q to quit--- #24 0x0090895f in nsAppShell::Run () #25 0x00ebd9d1 in nsAppStartup::Run () #26 0x0069dd2a in XRE_main () #27 0x00697e46 in main () (gdb) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:21:04 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:21:04 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.4c56605e497537837e3abc6a5e199b69@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by kvdman): Attached a screenshot of some errors displayed before it loads... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:34:15 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:34:15 -0000 Subject: [Haiku-bugs] [Haiku] #634: [app_server] crash in Painter::FillRectNoClipping() In-Reply-To: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> References: <040.d9d78f49dbc29726ab6b5be27a347bbc@haiku-os.org> Message-ID: <049.5851bb5d5fa93fad25eaf54cdfd53607@haiku-os.org> #634: [app_server] crash in Painter::FillRectNoClipping() ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: critical | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Fixed in r22721. I only fixed the crashing result, not the true cause, but when I tried to investigate this, I couldn't: The region that the view tries to draw is clipped against the window content region. So for it to be out of bounds, both regions have to be, or there has to be a BRegion bug. To get more info on the regions involved, I inserted the same check for an out of bounds region before the call to the DrawingEngine, but I couldn't get it triggered. Don't know what that means. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:49:35 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:49:35 -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.0129ad37dd7162c41325e9baf367d6f7@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: While investigating #634, I have switched workspaces like mad all afternoon. I have not once experienced a lockup (running in VMWare). If there is another way to produce this, than by opening all apps at once and quickly switching workspaces at the same time either by keyboard shortcut or via the Workspaces applet (mouse), then please reopen... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 19:59:45 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 17:59:45 -0000 Subject: [Haiku-bugs] [Haiku] #693: Cannot Change Resolution per Workspace (easy) In-Reply-To: <054.cded4538db07e83281123e6417f59949@haiku-os.org> References: <054.cded4538db07e83281123e6417f59949@haiku-os.org> Message-ID: <063.8d3c3227d935e31ecd522b89bf6a1a01@haiku-os.org> #693: Cannot Change Resolution per Workspace (easy) ----------------------------------+----------------------------------------- Reporter: greg.gd at woosh.co.nz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Comment (by stippi): Considering the goal of that release, why was this bug moved to the R1/alpha milestone? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:11:18 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:11:18 -0000 Subject: [Haiku-bugs] [Haiku] #756: [app_server] crash in WindowList::RemoveWindow() In-Reply-To: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> References: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> Message-ID: <049.0fcad129a880c81228f75770326424ae@haiku-os.org> #756: [app_server] crash in WindowList::RemoveWindow() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): I can definitely not reproduce this bug by following the steps outlined in #755 (taking a window to another workspace that has another window associated with it, like a floating window). And there have been fixes to the window list stuff by Axel. Can this be closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:25:58 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:25:58 -0000 Subject: [Haiku-bugs] [Haiku] #1578: Panic on boot (AHCI and/or VM related?) In-Reply-To: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> References: <044.543adece4ef4bf6a92c3f1f538e74c9a@haiku-os.org> Message-ID: <053.68919cd8e55b3b632bf92fc79fc3ab69@haiku-os.org> #1578: Panic on boot (AHCI and/or VM related?) ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r22726. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:29:19 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:29:19 -0000 Subject: [Haiku-bugs] [Haiku] #1434: device manager loads driver too often In-Reply-To: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> References: <050.e3f1b2a2b21352b7f4852cd6c0743e73@haiku-os.org> Message-ID: <059.1ec4cff98eebb673afe325ca31dbdd2d@haiku-os.org> #1434: device manager loads driver too often ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ------------------------------+--------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Hopefully fixed in r22726. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:42:12 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:42:12 -0000 Subject: [Haiku-bugs] [Haiku] #880: [app_server] icon disappers if selected and then desktop right clicked In-Reply-To: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> References: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> Message-ID: <049.d84f2ebc0df96505792692e0b4f98e65@haiku-os.org> #880: [app_server] icon disappers if selected and then desktop right clicked ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: invalid | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => invalid Comment: R5 behaves exactly the same for both left and right click into empty desktop region when icons are selected (the icons are deselected and the context menu appears). So I am closing this bug as invalid (should not hold up R1/alpha at least :-)). That being said, I don't know what the expected behaviour is. Personally, I find it "expected" that clicking outside the selected icons deselects them even if the context menu opens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:44:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:44:11 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment violation [tcsetpgrp failed in terminal_inferior: Invalid Argument] Message-ID: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> #1587: Segment violation [tcsetpgrp failed in terminal_inferior: Invalid Argument] -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- While debugging #1479 on my thinkpad 570E I was able to get it to boot up with the crazy color video reported in #1169 and then set the video mode to 1024x768, 16bit color and reboot. It them boots up to a blue screen with a working hand cursor but after about 10 seconds drops to GDB with this error: [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 110 caused an exception: Segment violation Reading symbols yada yada.... ... ... ... Reading symbols from /boot/beos/system/add- ons/accelerants/neomagic.accelerant [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/beos/system/servers/app_server (42) thread w:68:Terminal 1 (110)] 0x002922ca in Painter::StraightLine () (gdb) Note that I typed this in by hand so might be typos. This was with r22697. I will attach serial debug as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:45:41 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:45:41 -0000 Subject: [Haiku-bugs] [Haiku] #756: [app_server] crash in WindowList::RemoveWindow() In-Reply-To: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> References: <040.ccd2ed67d2d136937906b83d1ab5107e@haiku-os.org> Message-ID: <049.e0f60afeba8e02636c87137eb7ad6306@haiku-os.org> #756: [app_server] crash in WindowList::RemoveWindow() ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This one should have been fixed with r22549 as well - please reopen if your mileage differs :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:48:32 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:48:32 -0000 Subject: [Haiku-bugs] [Haiku] #693: Cannot Change Resolution per Workspace (easy) In-Reply-To: <054.cded4538db07e83281123e6417f59949@haiku-os.org> References: <054.cded4538db07e83281123e6417f59949@haiku-os.org> Message-ID: <063.9182ae7920abe6b4c76e7d2118b2aa79@haiku-os.org> #693: Cannot Change Resolution per Workspace (easy) ----------------------------------+----------------------------------------- Reporter: greg.gd at woosh.co.nz | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ----------------------------------+----------------------------------------- Changes (by axeld): * milestone: R1/alpha => R1 Comment: I somehow identified this as a prominent feature of Haiku that the alpha version shouldn't miss. But I guess you're right :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:48:36 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:48:36 -0000 Subject: [Haiku-bugs] [Haiku] #1311: [FileTypes] freeze on MediaPlayer start In-Reply-To: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> References: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> Message-ID: <049.c944ddcd339b96f68af762ede0468d95@haiku-os.org> #1311: [FileTypes] freeze on MediaPlayer start --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Preferences/FileTypes | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by stippi): I followed the procedure both in VMWare and on real hardware, but I cannot reproduce this bug. Everything behaves fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:49:53 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:49:53 -0000 Subject: [Haiku-bugs] [Haiku] #1479: Laptops fail to shutdown or restart properly In-Reply-To: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> References: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> Message-ID: <051.eadb726c7886de5ca805b57edf1a873f@haiku-os.org> #1479: Laptops fail to shutdown or restart properly ----------------------+----------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All ----------------------+----------------------------------------------------- Comment (by scottmc): It looks like #1479 is partially fixed (might be completely fixed need to test more), that is when I try to shutdown now it will display a dialog box allowing my to click a button to reboot and it works. In r22597 it would just freeze up at that point. I have not yet played with the APM settings to see if it will auto shutoff. I will do more testing on this as I get time. I'm trying to work around #1587 right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 20:52:16 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 18:52:16 -0000 Subject: [Haiku-bugs] [Haiku] #1586: Queries: not case-insensitive for "Umlauts" In-Reply-To: <044.56857434cb3c25e1eca375a31e7de779@haiku-os.org> References: <044.56857434cb3c25e1eca375a31e7de779@haiku-os.org> Message-ID: <053.add86220834b410f11e395651e585176@haiku-os.org> #1586: Queries: not case-insensitive for "Umlauts" -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * milestone: R1 => Unscheduled Comment: This will be fixed when Haiku gets a locale kit - until then, you have to live with it, sorry. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 21:28:06 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 19:28:06 -0000 Subject: [Haiku-bugs] [Haiku] #1586: Queries: not case-insensitive for "Umlauts" In-Reply-To: <044.56857434cb3c25e1eca375a31e7de779@haiku-os.org> References: <044.56857434cb3c25e1eca375a31e7de779@haiku-os.org> Message-ID: <053.43e2ff8a848b1be519aaaa3cfb49bdf7@haiku-os.org> #1586: Queries: not case-insensitive for "Umlauts" -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by humdinger): That's OK. I was just wondering why the query didn't return all files I expected... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 21:57:11 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 19:57:11 -0000 Subject: [Haiku-bugs] [Haiku] #1479: Laptops fail to shutdown or restart properly In-Reply-To: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> References: <042.c07753455550244e662ef30c9307d15d@haiku-os.org> Message-ID: <051.0da2bd6d4f9d514aae977faad370bd5f@haiku-os.org> #1479: Laptops fail to shutdown or restart properly -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: System => Drivers/Keyboard/PS2 * milestone: R1 => R1/alpha Comment: Okay, thanks for the update. Fixed in r22617. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 21:58:22 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 19:58:22 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment violation [tcsetpgrp failed in terminal_inferior: Invalid Argument] In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.d3e54e787d9285ab1dda0376b7b25ced@haiku-os.org> #1587: Segment violation [tcsetpgrp failed in terminal_inferior: Invalid Argument] ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => stippi * priority: normal => high * component: - General => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 22:09:40 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 20:09:40 -0000 Subject: [Haiku-bugs] [Haiku] #1427: Firefox crashes on start In-Reply-To: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> References: <045.03840ccf9955876aa1eb5422e58ac464@haiku-os.org> Message-ID: <054.02a95cc124d50652f2e3fe0c51105656@haiku-os.org> #1427: Firefox crashes on start -------------------------+-------------------------------------------------- Reporter: tangobravo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by tqh): Most libs in Firefox are loaded by absolute path by Firefox itself, so shouldn't be moved. The ones that may be moved are the ones linked by the executable (firefox-bin) itself and the ones linked by those libs (and so on). The stubs are an 'ugly hack' to get around BeOS R5's poor handling of addon memory. The stubs are just libs that link to the real lib, the stub gets loaded in addon memory and the libs in ordinary. In Haiku and Zeta I'd recommend to delete the stubs as the loading mechanism will fallback to loading the real lib instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 22:35:29 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 20:35:29 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.a0fa31a7a8d8ea4906230599e54ee3d7@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by bonefish): * summary: Segment violation [tcsetpgrp failed in terminal_inferior: Invalid Argument] => Segment Violation in Painter::StraightLine() -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 23:05:27 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 21:05:27 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.27292ff337f7b869747c8b79259f5c9d@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: invalid | Platform: x86 -------------------------+-------------------------------------------------- Comment (by kev): Just to be clear, the bug I was having was with font embedding, I was just noting that the compression and compatibility settings didn't seem to make a difference. So, with the SVN version you can correctly output text in the SGreek font? Thanks, Kev -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Oct 25 23:38:03 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 21:38:03 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.07919c9a47c4136588a6454fb48e8747@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): I've a similar situation with a similar Thinkpad (570), maybe the serial debug from it can help as there are similarities in them as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 00:00:41 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 22:00:41 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.b1f6ba6ce211fcf4dae60259e6d08dcf@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): Sometimes when booting up it hangs with a black screen and the Haiku logo. Serial debug shows it hanging at: via: init_hardware() failed: General system error never getting to the next line, unless I try rebooting: ps2_hid: init_hardware So it seems there might also be an issue with ps2_hid: init_hardware as well. meanwhile do you see this same thing happening on your 570? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 00:27:35 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 22:27:35 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.4fb31c701a90d67e4c9c9ff9e64dfd80@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks, applied in r22729. I changed the "[0-9][0-9]" to "[1-9][0-9]", though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 00:44:57 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 22:44:57 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.a3ab794f548c56510a0c44af9643ac4c@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): In the setup here (two BeOS partitons and a Haiku partition, managed by Bootman) each Haiku revision has always hung at its bootscreen after a reboot from one of the BeOS installs. Restarting from Haiku also doesn't work: the cursor freezes at the stage in the restart process where the message 'Asking other processes to quit' is displayed. When choosing shutdown instead and then clicking the 'Restart System' button in the 'System is Shut Down' window, the cursor also freezes. Just found that a reboot from BeOS into Haiku gives "via: init_hardware() failed: General System error" as the last line of the debug output here too. At this point I can't reboot though; if you could let me know how you reboot to get to the next line ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 00:54:51 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 22:54:51 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.79afe7d3b50a9efccfc8498c48d64e36@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by mmu_man): * status: closed => reopened * resolution: fixed => Comment: B_DONT_DO_THAT ! Do *not* change a configure script directly. One must change configure.in and rerun autoconf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 01:09:09 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 25 Oct 2007 23:09:09 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.ddd9af49630c0311e4e26adf6ed047c3@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): BTW, this was all done with r22509. I'll get the latest revision in the next days to see if #1479 changed things here too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 03:56:00 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 01:56:00 -0000 Subject: [Haiku-bugs] [Haiku] #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater In-Reply-To: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> References: <040.19d1bea479b56a6825d20b11a596a6ea@haiku-os.org> Message-ID: <049.2661b432cc88a6ed6d617c94b70bdd87@haiku-os.org> #1581: 'makeinfo' detection broken in buildtools when using texinfo/makeinfo 4.10 or greater ---------------------------+------------------------------------------------ Reporter: kad77 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: reopened => closed * resolution: => fixed Comment: Thanks for the heads up. It's EDNTDOTHT in this case, though. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 09:37:34 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 07:37:34 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.084c8daf34f9b6d88e65cb98c626ade9@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: x86 -------------------------+-------------------------------------------------- Changes (by laplace): * status: closed => reopened * resolution: invalid => Comment: Oh, I had not tested it with that particular font. I have done this now and of course embedding does not work :-( Not sure yet what's the reason for that. I have opened this ticket again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 11:23:14 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 09:23:14 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.d263cdd19ca36e40b21942fa6923c339@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): As for restarting from Haiku, the reboot gets further in r22724: it now hangs at Haiku's bootscreen. However, except for the successfull very first boot of this revision, a next boot of it gives a GDB screen (see attachment). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 14:27:04 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 12:27:04 -0000 Subject: [Haiku-bugs] [Haiku] #1585: Haiku doesn't boot with qemu In-Reply-To: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> References: <045.e28f8386d225487affdf0168ad7b075d@haiku-os.org> Message-ID: <054.8dcad54e312f076e3fe09ae5ecb168e9@haiku-os.org> #1585: Haiku doesn't boot with qemu ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by mmlr): It works on a win32 QEMU (at work) and an image from the build factory (r22728). I think this is a GCC4 build, maybe this has an influence? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 14:38:26 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 12:38:26 -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.dd26555e9a1cc2fced736632ec258122@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: I tried the same with r22730 and managed to deadlock it twice. Strange but cursor in Terminal still blinks and i see ProcessController activity in Deskbar, but in the same time i can't move any window and system is not responding to mouse/keyboard events. I would like to reopen this bug as there are still some problems remain. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 14:50:35 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 12:50:35 -0000 Subject: [Haiku-bugs] [Haiku] #880: [app_server] icon disappers if selected and then desktop right clicked In-Reply-To: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> References: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> Message-ID: <049.25d8f73f4d62366699d0d9546dd31db7@haiku-os.org> #880: [app_server] icon disappers if selected and then desktop right clicked ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: invalid => Comment: Yes i know that R5 behaves exactly the same, but imho it's a bug and user don't have to see such visual glitches as it looks not professional and shouldn't be there in the first place ;-) I would like to reopen this bug, feel free to close it again if you feel so as you know it better. And you are right, it should not hold up R1/alpha. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:02:59 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:02:59 -0000 Subject: [Haiku-bugs] [Haiku] #1045: USB isochronous streams In-Reply-To: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> References: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> Message-ID: <054.4ade3fc5efe9862a70e24b3f9b0b4746@haiku-os.org> #1045: USB isochronous streams --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by korli): * cc: emitrax (added) Comment: Shouldn't this be reassigned to emitrax ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:08:14 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:08:14 -0000 Subject: [Haiku-bugs] [Haiku] #1045: USB isochronous streams In-Reply-To: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> References: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> Message-ID: <054.6c88b6288ae3b3df6d5c06197ced1350@haiku-os.org> #1045: USB isochronous streams --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by emitrax): The stack itself now has isochronous support, I'd split it into two different enhancement tickets, one for UHCI (which has not-well-tested support) and one for EHCI. What do you think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:09:22 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:09:22 -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.66328ec66aa808018b9acf0e1a463283@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): Just to be sure, by "I tried the same" you mean the way to reproduce this I outlined above? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:26:00 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:26:00 -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.be397ddf43371cb1548c079d1536c5f2@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Yes, i mean that i could reproduce it the way i describe it above. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:44:22 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:44:22 -0000 Subject: [Haiku-bugs] [Haiku] #1045: USB isochronous streams In-Reply-To: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> References: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> Message-ID: <054.625f8e26bdeb04081a04aee19c2c6ba5@haiku-os.org> #1045: USB isochronous streams --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): I'd leave it like this. It serves as a reminder and I think we can keep track of the three points it combines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 15:53:57 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 13:53:57 -0000 Subject: [Haiku-bugs] [Haiku] #1588: Geforce 8xxx support in Nvidia driver Message-ID: <044.679f530a49a59740ec283fdc0e2b6b04@haiku-os.org> #1588: Geforce 8xxx support in Nvidia driver -------------------------------------+-------------------------------------- Reporter: pieterpan | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- It would be very nice if the nvidia driver supported the Geforce 8xxx series. I've been in touch with Rudolf, he said it would be quite some work as things changed a bit. Anyway, just creating the ticket so we don't forget about it. More and more people with have these cards and they should work in Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 16:03:58 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 14:03:58 -0000 Subject: [Haiku-bugs] [Haiku] #1589: Fat file system recognized by mount, but NOT mountvolume and tracker Message-ID: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> #1589: Fat file system recognized by mount, but NOT mountvolume and tracker ------------------------------+--------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Since I don't have a working ethernet driver, I use a fat partition to copy files between Native Haiku and Windows. Unfortunately tracker and mountvolume does not recognize my fat partition as something it can mount. I can however mount it fine with the mount command {{{ mount -t fat /dev/disk/scsi/0/0/0/2 /fatdrive/ }}} I don't know if this is related to FAT or the FS subsystem/tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 16:13:25 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 14:13:25 -0000 Subject: [Haiku-bugs] [Haiku] #1311: [FileTypes] freeze on MediaPlayer start In-Reply-To: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> References: <040.3baa36675b550d7ffacb9e5dfaad35a3@haiku-os.org> Message-ID: <049.c77f045c4b5df96ca5ef993ed3c00558@haiku-os.org> #1311: [FileTypes] freeze on MediaPlayer start --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: - Preferences/FileTypes | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by diver): Tested with r22730 in vmware server in ubuntu 7.10 and still could easy reproduce FileTypes freeze. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 16:17:50 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 14:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #1590: Updated Broadcom Tigon3 ethernet driver Message-ID: <044.6cb95f5b2faf1c68ea7bdf26b3fe5cec@haiku-os.org> #1590: Updated Broadcom Tigon3 ethernet driver -------------------------+-------------------------------------------------- Reporter: pieterpan | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- It would be nice if Haiku supported the latest broadcom gigabit ethernet chips. Currently Nathan's [http://bebits.com/app/3909 driver] is in SVN, but it does not support new chips like the one in my laptop (BCM 5787M) Unfortunately the code his driver is based on was not updated much, and linux switched to a new codebase. So I see 2 options: Port the [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=blob;f=drivers/net/tg3.c;h=9034a05734efb86b503bfa01f8d6673f071ce1de;hb=HEAD linux driver] or use the FreeBSD network driver compatibility layer to use the [http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/ FreeBSD driver]. Most likely the last option would be easiest. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 16:18:27 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 14:18:27 -0000 Subject: [Haiku-bugs] [Haiku] #1590: Updated Broadcom Tigon3 ethernet driver In-Reply-To: <044.6cb95f5b2faf1c68ea7bdf26b3fe5cec@haiku-os.org> References: <044.6cb95f5b2faf1c68ea7bdf26b3fe5cec@haiku-os.org> Message-ID: <053.989ab73cc1b8b14318b918b4758a4446@haiku-os.org> #1590: Updated Broadcom Tigon3 ethernet driver ------------------------------+--------------------------------------------- Reporter: pieterpan | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by pieterpan): * component: - General => Drivers/Network -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 16:23:19 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 14:23:19 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.16543bb229cdf453876ab758db3b05f9@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): Replying to [comment:7 meanwhile]: > As for restarting from Haiku, the reboot gets further in r22724: it now hangs at Haiku's bootscreen. > However, except for the successfull very first boot of this revision, a next boot of it gives a GDB screen (see attachment). OK so it sounds as if both of our systems are doing the exact same thing. First boot hangs, and then a second boot attempy boots up but then drops to GDB with the Painter::StraightLine() seg fault. I'm not sure but this might be 2 or 3 bugs. Anyways we're here to test. Bug one would be why does it hang at "via: init_hardware() failed: General System error" or is it hanging on the ps2 command which is next? Bug two is this ticket, the Painter::StraightLine(). Anyone else seeing this or is it just with Neomagic chipset or just Thinkpad 570 series? A listdev of a 570E can be seen in ticket #1169. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 17:48:22 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 15:48:22 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.531553460c3b9115afaa385445004697@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): Could you try if you still get the crash in Painter::StraightLine() with r22736? My suspicion is that the graphics driver and/or accelerant are not being initialized properly, and the Painters are not attached to the frame buffer correctly. I don't really know though. Would be great to have such a machine to test... but maybe not me but someone able to maintain the Via driver... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 18:01:23 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 16:01:23 -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.b59451f31fb704d2b5539899ba8da0b1@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: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): This one gives me a headache - I can reproduce it fine... But for example not in the test environment, which is quite weird. But it gets better: I can reproduce it in VMWare (vesa mode), *but* if just keep doing it for long enough, the bug *goes* *away*. Literally. At one time, I could observe that when dragging from left/top towards right/bottom, which produces artifacts at the right/bottom side of the selection box, that it suddenly started to have the artifacts on the right side only. And then finally it was gone completely. Whenever someone argues a bit can only take on two values, 1 and 0, I am just gonna put on a knowing smile... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 18:59:11 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 16:59:11 -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.ec1845d6755120abcca92b1d20db7f4c@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: | Platform: All ---------------------------------+------------------------------------------ Comment (by scottmc): I was trying this out this morning with r22729 I think it was and the horizontal lines weren't there anymore but the vertical ones still were. And after trying it for about a minute the selection box froze on the screen and the icons disappeared. The cursor still worked except I could no longer make new selection boxes. I had to restart the system. Things like this make me glad a reboot in Haiku is only 15 seconds from shutdown till I can use it again ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 19:02:57 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 17:02:57 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.0cbca43db2eef66bf6760fcedf0e2af1@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): Tried it with r22736, but it still behaves the same. Maybe the debug info tells more... (see r22736debug.txt). Since last week I have a second TP 570, so it wouldn't hurt so much to see one of them leave for a testing period. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 19:21:55 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 17:21:55 -0000 Subject: [Haiku-bugs] [Haiku] #1587: Segment Violation in Painter::StraightLine() In-Reply-To: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> References: <042.8e5439fb7e48b4646cfb6462a3446d79@haiku-os.org> Message-ID: <051.eed835178a1b2ea52ed791cdbf500a93@haiku-os.org> #1587: Segment Violation in Painter::StraightLine() ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: high | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by meanwhile): Clarification: Now only at the third boot there's a GDB screen showing. The r22736.txt is the serial debug output; what shows at this 3rd boot is seen in 'screen.png'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Oct 26 19:51:40 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 26 Oct 2007 17:51:40 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. Message-ID: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> #1591: Gobe Productive crashing when quitting program. --------------------------------+------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- Hi, This is reproducible, Gobe Productive 2.0.1 will always crash when exiting. I'll provide the bt here. Sorry if this turns out weird, posting from within Opera/Haiku. 0xffff0102 in ?? () (gdb) bt #0 0xffff0102 in ?? () #1 0x00c2c596 in debugger () from /boot/beos/system/lib/libroot.so #2 0x00c337e5 in __assert_fail () from /boot/beos/system/lib/libroot.so #3 0x00c3866a in BPrivate::hoardHeap::freeBlock () from /boot/beos/system/lib/libroot.so #4 0x00c39716 in BPrivate::processHeap::free () from /boot/beos/system/lib/libroot.so #5 0x00c3ada0 in free () from /boot/beos/system/lib/libroot.so #6 0x00c2a68c in __builtin_delete () from /boot/beos/system/lib/libroot.so #7 0x00832ae4 in BArchivable::~BArchivable () from /boot/beos/system/lib/libbe.so #8 0x0073a826 in BBitmap::~BBitmap () from /boot/beos/system/lib/libbe.so #9 0x003652da in TBitmapManager::DeleteEntry () #10 0x00364e4a in TBitmapManager::~TBitmapManager () #11 0x0035bc2c in TApp::~TApp () #12 0x00361e47 in main () (gdb) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 27 16:16:00 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 27 Oct 2007 14:16:00 -0000 Subject: [Haiku-bugs] [Haiku] #1592: Query windows doesn't update while restoring file from trash ... Message-ID: <039.25ac09f89880bd2e05f541f62d439edd@haiku-os.org> #1592: Query windows doesn't update while restoring file from trash ... -----------------------+---------------------------------------------------- Reporter: rdmr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Create a file on desktop and search the same file with Find. Leave query window open. Now move the file,you have created, to trash. You see that the file in query window is also disappeared. Till here everything is normal. But when you try to restore the file to the desktop,while the query window still open, you see that it doesn't update the query window. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Oct 27 16:36:06 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 27 Oct 2007 14:36:06 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.7a57ce6c22e4c6573aba21960550cd29@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by kvdman): This also happens with Opera and some other apps I can't think of right now. I looked at the bt when Opera crashes on termination, and it doesn't look similar though, so I'm not sure if they're related. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 28 16:15:15 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 28 Oct 2007 15:15:15 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.bbf11eaf3883b1bf254552a62f7d710f@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * component: Servers/app_server => - General Old description: > Hi, > > This is reproducible, Gobe Productive 2.0.1 will always crash when > exiting. I'll provide the bt here. Sorry if this turns out weird, posting > from within Opera/Haiku. > > 0xffff0102 in ?? () > (gdb) bt > #0 0xffff0102 in ?? () > #1 0x00c2c596 in debugger () from /boot/beos/system/lib/libroot.so > #2 0x00c337e5 in __assert_fail () from /boot/beos/system/lib/libroot.so > #3 0x00c3866a in BPrivate::hoardHeap::freeBlock () > from /boot/beos/system/lib/libroot.so > #4 0x00c39716 in BPrivate::processHeap::free () > from /boot/beos/system/lib/libroot.so > #5 0x00c3ada0 in free () from /boot/beos/system/lib/libroot.so > #6 0x00c2a68c in __builtin_delete () from > /boot/beos/system/lib/libroot.so > #7 0x00832ae4 in BArchivable::~BArchivable () > from /boot/beos/system/lib/libbe.so > #8 0x0073a826 in BBitmap::~BBitmap () from > /boot/beos/system/lib/libbe.so > #9 0x003652da in TBitmapManager::DeleteEntry () > #10 0x00364e4a in TBitmapManager::~TBitmapManager () > #11 0x0035bc2c in TApp::~TApp () > #12 0x00361e47 in main () > (gdb) New description: Hi, This is reproducible, Gobe Productive 2.0.1 will always crash when exiting. I'll provide the bt here. Sorry if this turns out weird, posting from within Opera/Haiku. 0xffff0102 in ?? () (gdb) bt #0 0xffff0102 in ?? () #1 0x00c2c596 in debugger () from /boot/beos/system/lib/libroot.so #2 0x00c337e5 in __assert_fail () from /boot/beos/system/lib/libroot.so #3 0x00c3866a in BPrivate::hoardHeap::freeBlock () from /boot/beos/system/lib/libroot.so #4 0x00c39716 in BPrivate::processHeap::free () from /boot/beos/system/lib/libroot.so #5 0x00c3ada0 in free () from /boot/beos/system/lib/libroot.so #6 0x00c2a68c in __builtin_delete () from /boot/beos/system/lib/libroot.so #7 0x00832ae4 in BArchivable::~BArchivable () from /boot/beos/system/lib/libbe.so #8 0x0073a826 in BBitmap::~BBitmap () from /boot/beos/system/lib/libbe.so #9 0x003652da in TBitmapManager::DeleteEntry () #10 0x00364e4a in TBitmapManager::~TBitmapManager () #11 0x0035bc2c in TApp::~TApp () #12 0x00361e47 in main () (gdb) Comment: Usually not. Apps mostly crash on Haiku because the allocator has turned on debugging, and many apps are just buggy. I don't think Gobe will be an exception here; but at least the crash will likely go away for the release (because debugging will then be turned off by default). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 28 16:48:11 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 28 Oct 2007 15:48:11 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.4882bf44373390d8eaf39357e48b50d9@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Changes (by ahwayakchih): * platform: All => x86 Comment: I'm not sure if i should start new bug report or not, so, just in case, i'll add info here for now. I tried to boot Haiku (r22750) on laptop (it's benq joybook p52s, but AFAIK they come in various configurations) which has ATI SATA controller, and it also doesn't boot. Unfortunetly i have no way to get serial output. Please let me know if i can give You some additional info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Oct 28 22:40:49 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 28 Oct 2007 21:40:49 -0000 Subject: [Haiku-bugs] [Haiku] #1096: NVIDIA nForce ethernet driver In-Reply-To: <041.86dc8b3d54f4aee51e1abed72c1fb42e@haiku-os.org> References: <041.86dc8b3d54f4aee51e1abed72c1fb42e@haiku-os.org> Message-ID: <050.37acee372aae47b447256cabb8eed9e4@haiku-os.org> #1096: NVIDIA nForce ethernet driver ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by noph): Is there someone who still got the zipfile with the zeta-port of the nforce driver? A new post with the link would be highly appreciated! I will investigate what was done and try to do a new port of the driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 00:11:40 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 28 Oct 2007 23:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #1593: idle_time() not implemented app server side Message-ID: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> #1593: idle_time() not implemented app server side --------------------------------+------------------------------------------- Reporter: korli | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- idle_time() always returns 0. In fact, AS_IDLE_TIME is not implemented server side. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 06:29:40 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 05:29:40 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still Message-ID: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Daylight savings time for the United States was changed this year but when booting into Haiku today it thought the time was supposed to change when it's not supposed to happen until next week. Not sure if it's a bug in Haiku or if booting into BeOS today messed something up. Either way probably can't hurt to look at the code closer to make sure it is up to date with the 2007 changes to DST in the United States. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 06:38:37 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 05:38:37 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.8aa7f2d9274ca6fd1f0e4713a32891c1@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Changes (by scottmc): * component: - General => - Preferences/Time & Date Comment: Seems theres was an update last week: ftp://elsie.nci.nih.gov/pub/ So an update like was done for #1496 might be all that's needed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 08:47:17 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 07:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.eeb152ea9a69e1009534fab2fe661b8e@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: fixed | Platform: x86 -------------------------+-------------------------------------------------- Changes (by laplace): * status: reopened => closed * resolution: => fixed Comment: This font cannot be embedded due to licensing restrictions in the font file. Now a more detailed error message is written to the status window. This closes the ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 09:52:47 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 08:52:47 -0000 Subject: [Haiku-bugs] [Haiku] #1593: idle_time() not implemented app server side In-Reply-To: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> References: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> Message-ID: <049.c601a78eb4611761d41ee8a6497d24b7@haiku-os.org> #1593: idle_time() not implemented app server side ---------------------------------+------------------------------------------ Reporter: korli | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => assigned * milestone: R1 => R1/alpha -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 10:04:51 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 09:04:51 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.041a5e0a788e919f0db965da70344f66@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:2 axeld]: > Usually not. Apps mostly crash on Haiku because the allocator has turned on debugging, and many apps are just buggy. I don't think Gobe will be an exception here; but at least the crash will likely go away for the release (because debugging will then be turned off by default). By the way: we are using the hoard allocator. The version we're using is LGPL, but we can't update it to newer version because they've switched to GPL. Maybe we should consider alternative allocators, or even adapt our slab allocator to be used in userland too (AFAIK Sun did the same for their own slab allocator, cf. libumem) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 10:11:46 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 09:11:46 -0000 Subject: [Haiku-bugs] [Haiku] #1593: idle_time() not implemented app server side In-Reply-To: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> References: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> Message-ID: <049.cea0edc75643fbd369d555cca01675f9@haiku-os.org> #1593: idle_time() not implemented app server side ---------------------------------+------------------------------------------ Reporter: korli | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Implemented in r22758. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 10:20:42 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 09:20:42 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.c723d7bf66ab5bcbaaa1b1d6d4f63387@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Replying to [comment:3 jackburton]: > By the way: we are using the hoard allocator. The version we're using is LGPL, but we can't update it to newer version because they've switched to GPL. I know, but there is little reason to update it, it's complete. Later versions did not really change anything besides the license. > Maybe we should consider alternative allocators, or even adapt our slab allocator to be used in userland too (AFAIK Sun did the same for their own slab allocator, cf. libumem) We can of course experiment with that, but for now, I'm all for sticking to what we have. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 11:35:25 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 10:35:25 -0000 Subject: [Haiku-bugs] [Haiku] #1593: idle_time() not implemented app server side In-Reply-To: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> References: <040.e0dc6ac3d5846c3a1d2ffaabb8bc681f@haiku-os.org> Message-ID: <049.5f0797c84f3d2a6499451c4ac6219dea@haiku-os.org> #1593: idle_time() not implemented app server side ---------------------------------+------------------------------------------ Reporter: korli | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Comment (by korli): Thanks ! This was called from Tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 11:41:43 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 10:41:43 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.88ffa9dd70cfe6038d80a669f70dc441@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): Replying to [comment:3 jackburton]: > Maybe we should consider alternative allocators, or even adapt our slab allocator to be used in userland too (AFAIK Sun did the same for their own slab allocator, cf. libumem) Some alternatives: tcmalloc (from google perftools BSD License). nedmalloc (Boost Software License) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 11:46:26 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 10:46:26 -0000 Subject: [Haiku-bugs] [Haiku] #1576: Some headers should be rewritten In-Reply-To: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> References: <040.e83e7424b795679f4337b358ef6c301d@haiku-os.org> Message-ID: <049.89be47c2d7b53f7a9031ffbcda59670e@haiku-os.org> #1576: Some headers should be rewritten ------------------------+--------------------------------------------------- Reporter: korli | Owner: Type: bug | Status: new Priority: high | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Old description: > Here is a list in headers/os. They should be reported in headers/build/. > > headers/os/add-ons/graphics/Accelerant.h > headers/os/add-ons/graphics/GraphicsCard.h > headers/os/add-ons/input_server/InputServerDevice.h > headers/os/add-ons/input_server/InputServerFilter.h > headers/os/add-ons/input_server/InputServerMethod.h > headers/os/app/PropertyInfo.h > headers/os/be_apps/NetPositive/NetPositive.h > headers/os/device/A2D.h > headers/os/device/CAM.h > headers/os/device/D2A.h > headers/os/device/DigitalPort.h > headers/os/device/Joystick.h > headers/os/device/scsi.h > headers/os/device/SerialPort.h > headers/os/drivers/atomizer.h > headers/os/drivers/bus_manager.h > headers/os/drivers/ISA.h > headers/os/drivers/midi_driver.h > headers/os/drivers/PCI.h > headers/os/drivers/USB_printer.h > headers/os/drivers/USB_rle.h > headers/os/drivers/USB_spec.h > headers/os/interface/ChannelControl.h > headers/os/interface/ChannelSlider.h > headers/os/interface/Input.h > headers/os/interface/MenuBar.h > headers/os/interface/MultiChannelControl.h > headers/os/interface/PopUpMenu.h > headers/os/interface/PrintJob.h > headers/os/interface/TextView.h > headers/os/kernel/scheduler.h > headers/os/mail/E-mail.h > headers/os/media/BufferConsumer.h > headers/os/media/BufferGroup.h > headers/os/media/Buffer.h > headers/os/media/BufferProducer.h > headers/os/media/Controllable.h > headers/os/media/FileInterface.h > headers/os/media/MediaAddOn.h > headers/os/media/MediaDefs.h > headers/os/media/MediaEventLooper.h > headers/os/media/MediaFiles.h > headers/os/media/MediaFormats.h > headers/os/media/MediaNode.h > headers/os/media/MediaRoster.h > headers/os/media/ParameterWeb.h > headers/os/media/PlaySound.h > headers/os/media/RealtimeAlloc.h > headers/os/media/SoundFile.h > headers/os/media/Sound.h > headers/os/media/SoundPlayer.h > headers/os/media/TimeCode.h > headers/os/media/TimedEventQueue.h > headers/os/media/TimeSource.h > headers/os/net/net_settings.h > headers/os/opengl/GLView.h > headers/os/translation/BitmapStream.h > headers/os/translation/TranslationDefs.h > headers/os/translation/TranslationErrors.h > headers/os/translation/TranslationKit.h > headers/os/translation/TranslatorAddOn.h > headers/os/translation/TranslatorFormats.h > > Done: > headers/os/add-ons/tracker/TrackerAddOn.h > headers/os/game/DirectWindow.h > headers/os/kernel/image.h > headers/os/interface/OptionControl.h > headers/os/interface/OptionPopUp.h New description: Here is a list in headers/os. They should be reported in headers/build/. headers/os/add-ons/graphics/Accelerant.h headers/os/add-ons/graphics/GraphicsCard.h headers/os/add-ons/input_server/InputServerDevice.h headers/os/add-ons/input_server/InputServerFilter.h headers/os/add-ons/input_server/InputServerMethod.h headers/os/app/PropertyInfo.h headers/os/be_apps/NetPositive/NetPositive.h headers/os/device/A2D.h headers/os/device/CAM.h headers/os/device/D2A.h headers/os/device/DigitalPort.h headers/os/device/Joystick.h headers/os/device/scsi.h headers/os/device/SerialPort.h headers/os/drivers/atomizer.h headers/os/drivers/bus_manager.h headers/os/drivers/ISA.h headers/os/drivers/midi_driver.h headers/os/drivers/PCI.h headers/os/drivers/USB_printer.h headers/os/drivers/USB_rle.h headers/os/drivers/USB_spec.h headers/os/interface/ChannelControl.h headers/os/interface/ChannelSlider.h headers/os/interface/Input.h headers/os/interface/MultiChannelControl.h headers/os/interface/PrintJob.h headers/os/interface/TextView.h headers/os/kernel/scheduler.h headers/os/mail/E-mail.h headers/os/media/BufferConsumer.h headers/os/media/BufferGroup.h headers/os/media/Buffer.h headers/os/media/BufferProducer.h headers/os/media/Controllable.h headers/os/media/FileInterface.h headers/os/media/MediaAddOn.h headers/os/media/MediaDefs.h headers/os/media/MediaEventLooper.h headers/os/media/MediaFiles.h headers/os/media/MediaFormats.h headers/os/media/MediaNode.h headers/os/media/MediaRoster.h headers/os/media/ParameterWeb.h headers/os/media/PlaySound.h headers/os/media/RealtimeAlloc.h headers/os/media/SoundFile.h headers/os/media/Sound.h headers/os/media/SoundPlayer.h headers/os/media/TimeCode.h headers/os/media/TimedEventQueue.h headers/os/media/TimeSource.h headers/os/net/net_settings.h headers/os/opengl/GLView.h headers/os/translation/BitmapStream.h headers/os/translation/TranslationDefs.h headers/os/translation/TranslationErrors.h headers/os/translation/TranslationKit.h headers/os/translation/TranslatorAddOn.h headers/os/translation/TranslatorFormats.h Done: headers/os/add-ons/tracker/TrackerAddOn.h headers/os/game/DirectWindow.h headers/os/kernel/image.h headers/os/interface/MenuBar.h headers/os/interface/OptionControl.h headers/os/interface/OptionPopUp.h headers/os/interface/PopUpMenu.h Comment (by jackburton): Is BMultiChannelControl used anywhere ? To me it looks like an older version of BChannelControl/BChannelSlider interface. We might decide to just drop it and stick with the latter. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 11:50:24 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 10:50:24 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.f11306f06e84084888b9ad4c7029d0a8@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by korli): Please give details on the date, the timezone, and the revision of your system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 12:17:45 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 11:17:45 -0000 Subject: [Haiku-bugs] [Haiku] #1595: Refcounted BString implementation Message-ID: <045.8e4f227281ecd5c72df596c05c0757e7@haiku-os.org> #1595: Refcounted BString implementation -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: - General | Version: Platform: All | -------------------------+-------------------------------------------------- Would be nice to have a reference counted, copy on write implementation for BString. Nowadays most string implementations are reference counted, so equal strings are only stored once, reducing the memory footprint. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 14:36:23 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 13:36:23 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.ec59bdd60f55b4ab551f97d903c6941a@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Changes (by agmsmith): * cc: agmsmith at rogers.com (added) Comment: Sounds like that should fix it, just update the timezone data in both BeOS and Haiku (otherwise you'll get both of them fighting over the clock). I did that for BeOS R5.0.3, using a time zone file from Linux Fedora 7 (/usr/share/zoneinfo has the files) for my time zone, and then using prefs to select it. Fortunately Linux and BeOS/Haiku use the same file format, which is generated by the Zic time zone compiler. See the related man pages for more info. - Alex -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 14:48:46 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 13:48:46 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.1a24e215e08a3dfccf669a019cab944e@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by korli): Replying to [comment:3 agmsmith]: > Sounds like that should fix it, just update the timezone data in both BeOS and Haiku (otherwise you'll get both of them fighting over the clock). I did that for BeOS Sure we can update tzdata. What I don't understand is : the DST change occurring now is included in tzdata for months. I would suspect the timezone of scottmc's system to be something in Europe as DST happened on 10/28. So, to check this, we need more information on the configuration: date, timezone, svn revision. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 14:56:53 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 13:56:53 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.cdbcc0b4b1d6e21c39bc128b6d381bc5@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by scottmc): Replying to [comment:4 korli]: > I would suspect the timezone of scottmc's system to be something in Europe as DST happened on 10/28. > So, to check this, we need more information on the configuration: date, timezone, svn revision. Seems my laptop moved to Paris when I wasn't looking... When I move to a new version of Haiku I just copy all of the files from the image file onto my Haiku partition while in BeOS. This overwrites all my config info each time, and it seems I hadn't fixed the time zone setting this time. So yes, nothing wrong here. Ok to close ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 14:59:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 13:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #1594: Daylight Saving Time for United States appears to be off still In-Reply-To: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> References: <042.92ed276046c434fc0108739306a65ef9@haiku-os.org> Message-ID: <051.07fd1e9c4d9347c40af238137bff7e36@haiku-os.org> #1594: Daylight Saving Time for United States appears to be off still ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Preferences/Time & Date | Version: R1 development Resolution: invalid | Platform: All ----------------------------------------+----------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid Comment: Thanks for checking :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 15:12:51 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 14:12:51 -0000 Subject: [Haiku-bugs] [Haiku] #1584: Fonts not encoded by PDF printer driver In-Reply-To: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> References: <038.063456206f9cecba27d6fe3f608384d4@haiku-os.org> Message-ID: <047.3440fc925c46427f99c23cd89caba748@haiku-os.org> #1584: Fonts not encoded by PDF printer driver -------------------------+-------------------------------------------------- Reporter: kev | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Printing | Version: R1 development Resolution: fixed | Platform: x86 -------------------------+-------------------------------------------------- Comment (by kev): Oh...oops, I didn't know this technology even existed! Sorry about that. Thanks for updating the error messages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 18:36:43 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 17:36:43 -0000 Subject: [Haiku-bugs] [Haiku] #1570: [PackageInstaller] wont quit correctly In-Reply-To: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> References: <040.b7aa7b3c6c948c13ce5ca2c78a26b62a@haiku-os.org> Message-ID: <049.28fb8ab06e91ddc7a1467edd995bab39@haiku-os.org> #1570: [PackageInstaller] wont quit correctly ----------------------------------------------+----------------------------- Reporter: diver | Owner: sil2100 Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/PackageInstaller | Version: R1 development Resolution: fixed | Platform: All ----------------------------------------------+----------------------------- Changes (by sil2100): * status: new => closed * resolution: => fixed Comment: Fixed in r22754. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 20:53:29 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 19:53:29 -0000 Subject: [Haiku-bugs] [Haiku] #1106: Port USB mass storage driver to new SCSI module API In-Reply-To: <040.3f3b937e94160a49b76b6c6e5aff5d87@haiku-os.org> References: <040.3f3b937e94160a49b76b6c6e5aff5d87@haiku-os.org> Message-ID: <049.1d080f775f1d37d6def46b37d5809636@haiku-os.org> #1106: Port USB mass storage driver to new SCSI module API --------------------------+------------------------------------------------- Reporter: axeld | Owner: siarzhuk Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by diver): Any news, Siarzhuk? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 22:15:52 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 21:15:52 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel Message-ID: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ---------------------------+------------------------------------------------ Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ I'm not sure if my code is incorrect, but I suppose this should work. If a thread is acquiring a semaphore with infinite timeout, and another thread sends a signal to it, shouldn't the semaphore acquisition be interrupted ? If it should, then it's not working correctly. Attached is some code which shows the situation I'm talking about. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 23:25:16 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 22:25:16 -0000 Subject: [Haiku-bugs] [Haiku] #1591: Gobe Productive crashing when quitting program. In-Reply-To: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> References: <041.af0c41ace479d918b7490c031f0e042d@haiku-os.org> Message-ID: <050.32ab3f8a1d0510285b2ebb63c6f7e2fb@haiku-os.org> #1591: Gobe Productive crashing when quitting program. ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kvdman): Hi, 'Apps mostly crash on Haiku because the allocator has turned on debugging' I'm not sure what this means... I remember Axel's presentation at Google, and he said everything ran slow and crashed because debugging was enabled. Are the vmware images at haikuhost compiled with debugging enabled, or is that how does that work? thanks -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Oct 29 23:53:58 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 29 Oct 2007 22:53:58 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.4b5eb61a2d2fd5d261c47d36c6ea46a5@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): The attached code has a few issues -- maybe you just introduced them when turning this into a postable example? Besides the missing headers and using spawn_kernel_thread() (although it otherwise looks like a userland example), foo_thread() actually waits more than three weeks. When fixing the issues, the test works just fine with r22765. To answer the question in the code: If no SIGINT handler is installed, the main thread will commit suicide before returning from the syscall. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 08:32:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 07:32:59 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.e775b248ae77af77822e0f49526a3888@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:1 bonefish]: > The attached code has a few issues -- maybe you just introduced them when turning this into a postable example? Indeed. The actual code is very different, but I had to "camouflage" it... >Besides the missing headers and using spawn_kernel_thread() (although it otherwise >looks like a userland example), foo_thread() actually waits more than three weeks. >When fixing the issues, the test works just fine with r22765. I'll post the complete code when I get to the other machine. Thank you for your help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 08:35:02 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 07:35:02 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.7646731edbfe2a0fd586ea986ed621fd@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:1 bonefish]: > To answer the question in the code: If no SIGINT handler is installed, the main thread will commit suicide before returning from the syscall. Oh, that's probably what happens in my case, then. Seeing no advancement in the syslog, I thought the thread was blocked, while probably it was simply dead. Is there a way to simply interrupt the semaphore acquisition ? I guess in that case acquire_sem_etc() would return B_INTERRUPTED or B_WOULD_BLOCK ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:00:30 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:00:30 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.444eba625eff36e9a7439569c4a07187@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): You can either change the behaviour of SIGINT, or alternatively, just call suspend_thread()/resume_thread(). I guess we can close this ticket? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:02:07 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:02:07 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.e71ebd40799372d99e79d6812647b0ef@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Absolutely! Thank you! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:03:11 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:03:11 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.a7b135b92643d78472215ee0c2ef88f8@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by jackburton): * status: closed => reopened * resolution: fixed => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:03:22 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:03:22 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.c7e1ac6b92804ca11c473b7c7b1d8ee5@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Platform: All ----------------------------+----------------------------------------------- Changes (by jackburton): * status: reopened => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:14:40 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:14:40 -0000 Subject: [Haiku-bugs] [Haiku] #880: [app_server] icon disappers if selected and then desktop right clicked In-Reply-To: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> References: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> Message-ID: <049.d9fb5069bf14306b49df06200390b32e@haiku-os.org> #880: [app_server] icon disappers if selected and then desktop right clicked ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: Unscheduled Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * milestone: R1/alpha => Unscheduled Comment: Windows does it like this, Gnome does it like this, I think we should just stick with this behavior since it makes sense. If you want to do something with the selected files, you should right click on the selection. I'm changing milestone, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:20:09 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:20:09 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] The teapot can't be controlled by a mouse In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.dff0e3d4d47d55c60320b6cd6e5b374f@haiku-os.org> #1310: [GLTeapot] The teapot can't be controlled by a mouse ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by jackburton): * summary: [GLTeapot] can't be controlled by a mouse anymore => [GLTeapot] The teapot can't be controlled by a mouse Old description: > GLTeapot can't be controlled by a mouse anymore and cursor have black > background box now. New description: The teapot in GLTeapot can't be controlled by a mouse. It used to work sometime in the past. Comment: Sorry, I hadn't understood what you were talking about. I thought you were talking about the GLTeapot _window_. Not the teapot itself. I can reproduce the bug. I removed the part about the black cursor because that depends on not having a hardware cursor. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:25:21 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:25:21 -0000 Subject: [Haiku-bugs] [Haiku] #1310: [GLTeapot] The teapot can't be controlled by a mouse In-Reply-To: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> References: <040.331a3dc9623631958c936d219dd94328@haiku-os.org> Message-ID: <049.64bce7f3a8af63ece1b844941270c870@haiku-os.org> #1310: [GLTeapot] The teapot can't be controlled by a mouse ------------------------------+--------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1/alpha Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by jackburton): Replying to [comment:3 korli]: > It seems changing the priority of the direct daemon thread to less than 15 let me control the teapot with the mouse. > Stefano, should I change the priority of the direct daemon thread to (B_DISPLAY_PRIORITY - 1) ? I find it weird that lowering the priority would fix the problem. Or does it make sense ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 10:47:20 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 09:47:20 -0000 Subject: [Haiku-bugs] [Haiku] #880: [app_server] icon disappers if selected and then desktop right clicked In-Reply-To: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> References: <040.816a17610ad3f9b5a77648d1f7f9f8b1@haiku-os.org> Message-ID: <049.e5bf06aa77f6ace929b14e5118c9f4f9@haiku-os.org> #880: [app_server] icon disappers if selected and then desktop right clicked ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: Unscheduled Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Replying to [comment:5 jackburton]: I think you misunderstood me here. If you select desktop files and hold it for several seconds icons will _disappear_ and this is not the same as with Gnome, KDE or Explorer, this is just with Tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 12:31:43 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 11:31:43 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.9cb88d120039c1f638eda7ac5f3311e9@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by ahwayakchih): Hi, Stefano helped me modify debug output so i made it wait for ENTER each time debug starts from top of screen (so kinda paging-like feature). Thanks to that i made photo session of whole debug output :). Can i attach it here? I made photos in grayscale, cropped and resized, and packed with 7z, but it weights over 3MB anyway. Things i noticed: - disk modules (SATA, generic_id, etc... there are 4 of them IIRC) are loaded and tried 12 times. I have 12 partitions, so it looks like they are loaded for each partition. Isn't it strange? I thought module handles whole disk, and partitions are handled by file systems? - every time module is tried it returns "support: 0". Until last time, when generic_ide outputs "support: 0.3". - after that debug outputs: "INIT: main: done... begin idle loop on cpu 0" and nothing happens. It just stays like that until i get bored and reboot ;). Like i wrote above, i have 12 partitions. Haiku is on second partition (known as /dev/sda2 on Ubuntu linux). Please let me know if i can attach set of photos here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 12:36:43 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 11:36:43 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.68dbd0c71453068938c62094756606c8@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by stippi): I think it's ok to attach the photos. But I'd also like that patch to make the console output wait for return to keep going. I think that's useful. Certainly as an option. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 12:40:18 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 11:40:18 -0000 Subject: [Haiku-bugs] [Haiku] #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded In-Reply-To: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> References: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> Message-ID: <050.01f455d890e0aab726c5ee8025de6f2e@haiku-os.org> #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by stippi): Any news? :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 13:11:42 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 12:11:42 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.9e239449ff06028c16a7509f8c1a5e3e@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by ahwayakchih): OK, i attached zip files with photos. I'm sorry i had to split it to four archives, but TRAC was rejecting one big file (500000 bytes limit). I converted files to lower quality jpgs, but they shoul d still be readable :). As for patch, i already sent it to Stefano - he said he will see if it can be applied in some form to SVN code. Should i attach it here too (it's kinda hacky, and ugly compared to the clean code of blue_screen.cpp :)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 13:50:03 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 12:50:03 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.6be38594431de5d8d2f126fbb80143f5@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by ahwayakchih): OK, i attached hack here too :) Usage: - hit ENTER to let it continue until next "page" (of screen size) is full. - hit "q" to make it continue without stopping again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 15:07:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 14:07:19 -0000 Subject: [Haiku-bugs] [Haiku] #1596: Semaphore acquisition is not interrupted by a signal in the kernel In-Reply-To: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> References: <045.1f28251753dc58ab139b006c7033952c@haiku-os.org> Message-ID: <054.3866790b4d8aad1747795ae7a7bb68b1@haiku-os.org> #1596: Semaphore acquisition is not interrupted by a signal in the kernel ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Platform: All ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:3 jackburton]: > Is there a way to simply interrupt the semaphore acquisition ? I guess in that case acquire_sem_etc() would return B_INTERRUPTED or B_WOULD_BLOCK ? It would return B_INTERRUPTED. BTW, although Axel says, it's common practice, I don't think I've ever needed to interrupt a thread in such a way. The suspend_thread()/resume_thread() trick might introduce a race condition (if the thread in question is not yet waiting on the semaphore, it will have no effect). A common situation when one needs to wake up a thread potentially blocking on a semaphore or port is a program (or subsystem) termination. But then deleting the semaphore/port usually does the trick. Or set a flag + release it. In Haiku I introduced the new experimental wait_for_objects(). It can be used to wait for events on multiple semaphores, ports, threads, and FDs. If your case is not just a termination situation, but rather waiting for two events, wait_for_objects() might be exactly what you want to use. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 15:09:03 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 14:09:03 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.e154b1fe94b73c31b73c5463f3145883@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by scottmc): Replying to [comment:10 stippi]: > I think it's ok to attach the photos. But I'd also like that patch to make the console output wait for return to keep going. I think that's useful. Certainly as an option. This would be great to have as an option in the bootup menu, perhaps right next to the enable on-screen debug. If/when this is added I would be able to further debug the PC that started this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 15:20:50 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 14:20:50 -0000 Subject: [Haiku-bugs] [Haiku] #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded In-Reply-To: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> References: <041.c022125a69e34246c82d256fb12c5464@haiku-os.org> Message-ID: <050.997032d70c176b190a93af29080fde59@haiku-os.org> #1416: "usb explore" thread sometimes crashes shortly after desktop is loaded --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: assigned Priority: high | Milestone: R1/alpha Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Not really. It's difficult without being able to reproduce. I have looked over the explore code many times now and thought it was finally approaching stability. Do you have anything additional installed to the usb_hid driver when this occurs? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 19:32:29 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 18:32:29 -0000 Subject: [Haiku-bugs] [Haiku] #1597: [app_server] crash while starting opera Message-ID: <040.7e473e1542c3c3ffaef9773f6c7c6f7f@haiku-os.org> #1597: [app_server] crash while starting opera --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- I dloaded haikuware image to play with some apps like gobe and insite designer. Then i tried to launch opera and app_server crashed. bt will follow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Oct 30 19:34:19 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 30 Oct 2007 18:34:19 -0000 Subject: [Haiku-bugs] [Haiku] #1597: [app_server] crash in BPrivate::threadHeap::malloc In-Reply-To: <040.7e473e1542c3c3ffaef9773f6c7c6f7f@haiku-os.org> References: <040.7e473e1542c3c3ffaef9773f6c7c6f7f@haiku-os.org> Message-ID: <049.2b25699db9b639a5e85819c72af370c7@haiku-os.org> #1597: [app_server] crash in BPrivate::threadHeap::malloc ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * summary: [app_server] crash while starting opera => [app_server] crash in BPrivate::threadHeap::malloc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 31 07:42:25 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 31 Oct 2007 06:42:25 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB In-Reply-To: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> References: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> Message-ID: <059.34d23ba2bbf28433b808d148e11f5787@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): re combine the mem area is needed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 31 10:39:28 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 31 Oct 2007 09:39:28 -0000 Subject: [Haiku-bugs] [Haiku] #1519: firewire driver creates 193 areas of 4kB In-Reply-To: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> References: <050.42cefcca0166d6d3962ab7d2e39d385f@haiku-os.org> Message-ID: <059.b07f0e51f8c0049823aee53d7c3f858b@haiku-os.org> #1519: firewire driver creates 193 areas of 4kB -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: absabs Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by korli): * owner: korli => absabs -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Oct 31 10:40:13 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 31 Oct 2007 09:40:13 -0000 Subject: [Haiku-bugs] [Haiku] #1049: implement a FireWire stack In-Reply-To: <045.7b881a001168ff81f9db85a78abc6918@haiku-os.org> References: <045.7b881a001168ff81f9db85a78abc6918@haiku-os.org> Message-ID: <054.67f03f42a669ec34a9ca35e79bfe9cd4@haiku-os.org> #1049: implement a FireWire stack -------------------------------+-------------------------------------------- Reporter: wkornewald | Owner: absabs Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by korli): * owner: axeld => absabs -- Ticket URL: Haiku The Haiku operating system.