From trac at haiku-os.org Tue Jul 1 06:40:12 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 01 Jul 2008 04:40:12 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.1861706432d56d68e8ea0f99a5de6917@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): For reference, I tried a few more builds and managed to panic the same way every time...is there any extra information I can gather from the kernel debugger that'd be helpful? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 11:21:11 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 01 Jul 2008 09:21:11 -0000 Subject: [Haiku-bugs] [Haiku] #2424: usb disk not published if plugged during boot (vmware) In-Reply-To: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> References: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> Message-ID: <051.6fcc7c1855c7ab60fed9dd2f6b68d9ff@haiku-os.org> #2424: usb disk not published if plugged during boot (vmware) ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Quick test on the fly. ;-) Let me know if you need anything else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 11:31:43 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 09:31:43 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.95c632722cdf06f79f7c781ed8d71e45@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * priority: normal => critical * milestone: R1 => R1/alpha1 Comment: Replying to [comment:3 anevilyak]: > For reference, I tried a few more builds and managed to panic the same way every time... Cool, we tried a few times, but never could -- respectively ran into other problems. > is there any extra information I can gather from the kernel debugger that'd be helpful? Yep, in vm.cpp make fault_get_page() and fault_find_page() non-inline (and maybe non-static), so that they aren't inlined into vm_soft_fault(). When you reproduce it next time the function offset in the stack trace function where the kernel page fault occurs would be important to know (should be in one of these three functions -- don't mind the rest of the stack trace). Please add an objdump of that function to the ticket (best get that on the build platform). That should provide us with the exact location in the source where things go wrong. It pretty much depends on that, what to investigate in the kernel debugger. You can do some general looking around though: You can use the "call" command to get the vm_soft_fault() parameters and thus the user fault address and kind of fault (read/write). The address gets you the area in question, via the area you can use "cache_tree" and "cache" to have a look at the caches that might be involved -- something may or may not look suspicious. Normally mutex_lock/unlock() come in pairs. That the object pointer becomes NULL inbetween is certainly weird. Maybe it already helps to know the exact location where that happens and have a keen-eyed look at the source to turn the bug up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 14:06:06 2008 From: trac at haiku-os.org (axeld) Date: Tue, 01 Jul 2008 12:06:06 -0000 Subject: [Haiku-bugs] [Haiku] #2473: Admin - Components - Owner no longer sorted Message-ID: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> #2473: Admin - Components - Owner no longer sorted --------------------------+------------------------------------------------- Reporter: axeld | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- The owner list is no longer sorted, and makes it therefore pretty hard to use. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 14:50:37 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 01 Jul 2008 12:50:37 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.9ebc6faf07ede49c960d2bf7e63ff93d@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Objdumps added (let me know if those aren't what you wanted please). Occasionally the build does error out early on a general OS error in mimeset for some reason, but this succeeds upon restarting jam again. In any case, I won't be able to try building again until I'm home in a few hours, sorry for the slow turnaround time. Will let you know what happens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 15:15:54 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 13:15:54 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.53b017d5c223ad80e3f43de7cb439d97@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:5 anevilyak]: > Objdumps added (let me know if those aren't what you wanted please). Yep, those are fine. Just need the updated page fault address, too. From the same kernel build the objdumps have been made from. > Occasionally the build does error out early on a general OS error in mimeset for some reason, We've tracked this one down. It's an app server race condition that is probably also responsible for other issues (weird window sizes, black GUI parts). Will commit a fix soon. > but this succeeds upon restarting jam again. In any case, I won't be able to try building again until I'm home in a few hours, sorry for the slow turnaround time. Will let you know what happens. Cool, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 15:42:14 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 01 Jul 2008 13:42:14 -0000 Subject: [Haiku-bugs] [Haiku] #2245: OpenGrok search is very much out of date In-Reply-To: <050.52e169c3eecc428c1bb91eccc4bcb163@haiku-os.org> References: <050.52e169c3eecc428c1bb91eccc4bcb163@haiku-os.org> Message-ID: <059.c4f6d9d5fd7a8b383f2bb71c90e67007@haiku-os.org> #2245: OpenGrok search is very much out of date ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by mmlr): I've just checked and it seems it is fully up to date now. The last revision is r26191 which is the most current revision. So this could be closed I think. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 15:48:43 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 01 Jul 2008 13:48:43 -0000 Subject: [Haiku-bugs] [Haiku] #2055: Eric's Ulimate Solitare, and Axia fail to run In-Reply-To: <042.064a83db9214403e601aae69c1b487c1@haiku-os.org> References: <042.064a83db9214403e601aae69c1b487c1@haiku-os.org> Message-ID: <051.4140962a4151f81d38a2a86de5bba173@haiku-os.org> #2055: Eric's Ulimate Solitare, and Axia fail to run ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): The screenshot and the debug output are sadly not really helpful as is. Please run the Ultimate binary from the Terminal or check the syslog. They should display the missing symbol at hand (that Tracker doesn't display it is tracked in another ticket I think). In the GDB from Axia, please run the "bt" command and include its output. Backtraces are more or less necessary to track where the problem starts out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 16:20:12 2008 From: trac at haiku-os.org (mmlr) Date: Tue, 01 Jul 2008 14:20:12 -0000 Subject: [Haiku-bugs] [Haiku] #2074: Time Preferences window doesn't show up. In-Reply-To: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> References: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> Message-ID: <053.9fa25352d296ebf7e5def3e3c8e46d47@haiku-os.org> #2074: Time Preferences window doesn't show up. ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): This should work now due to the post install script that does mimesetting. Can this be confirmed/closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 17:27:02 2008 From: trac at haiku-os.org (meanwhile) Date: Tue, 01 Jul 2008 15:27:02 -0000 Subject: [Haiku-bugs] [Haiku] #2074: Time Preferences window doesn't show up. In-Reply-To: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> References: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> Message-ID: <053.e8f77db54dcf6182ce12b7635f7479a4@haiku-os.org> #2074: Time Preferences window doesn't show up. ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): I hope somebody else can test this, since -at the moment- I don't have the hardware to run the latest Haiku connected to the internet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 17:49:13 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 15:49:13 -0000 Subject: [Haiku-bugs] [Haiku] #2331: [MediaPlayer] sometimes starts with corrupted interface In-Reply-To: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> References: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> Message-ID: <049.4f6aae44205418f712088e930aeeba12@haiku-os.org> #2331: [MediaPlayer] sometimes starts with corrupted interface ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by bonefish): The first part is probably fixed in r26192. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 17:51:35 2008 From: trac at haiku-os.org (meanwhile) Date: Tue, 01 Jul 2008 15:51:35 -0000 Subject: [Haiku-bugs] [Haiku] #2074: Time Preferences window doesn't show up. In-Reply-To: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> References: <044.8a988cb09c5ee854715ace5acb737743@haiku-os.org> Message-ID: <053.283281bb65664bb5a29c750797d5a22f@haiku-os.org> #2074: Time Preferences window doesn't show up. ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Replying to [comment:4 meanwhile]: > I hope somebody else can test this, since -at the moment- I don't have the hardware to run the latest Haiku connected to the internet. (...as changing the date and rebooting doesn't seem to work) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 18:41:06 2008 From: trac at haiku-os.org (stippi) Date: Tue, 01 Jul 2008 16:41:06 -0000 Subject: [Haiku-bugs] [Haiku] #256: [app_server] strange color conversion In-Reply-To: <040.7d94de2c4eee8ddb9e3e482f415d5bc1@haiku-os.org> References: <040.7d94de2c4eee8ddb9e3e482f415d5bc1@haiku-os.org> Message-ID: <049.6799eca8c63c99810e401ae49a794bcf@haiku-os.org> #256: [app_server] strange color conversion ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Hopefully fixed by r26192. Please reopen if you see it again. The same bug affected Tracker (upper 10% black background and very small icon text size), LaunchBox (black top icon(s)), Playground (similar to screenshot "weird.PNG") and probably other apps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 18:41:58 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 16:41:58 -0000 Subject: [Haiku-bugs] [Haiku] #1960: Terminal crash on resize In-Reply-To: <040.7bdfa53a9c29233f892db4fa7a580f73@haiku-os.org> References: <040.7bdfa53a9c29233f892db4fa7a580f73@haiku-os.org> Message-ID: <049.0b1120fd0df11315c3ed1af2b814b852@haiku-os.org> #1960: Terminal crash on resize --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should be fixed in r26192. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 18:43:34 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 16:43:34 -0000 Subject: [Haiku-bugs] [Haiku] #1997: Restart dialog occasionally comes up with infinite (or extremely large) height In-Reply-To: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> References: <044.5af3e31c218bbd027ebbb17e33bee520@haiku-os.org> Message-ID: <053.f9e02c0600dd6e26abf694dbe5742c57@haiku-os.org> #1997: Restart dialog occasionally comes up with infinite (or extremely large) height -----------------------------+---------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should be fixed in r26192. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 18:45:27 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 16:45:27 -0000 Subject: [Haiku-bugs] [Haiku] #1960: Terminal crash on resize In-Reply-To: <040.7bdfa53a9c29233f892db4fa7a580f73@haiku-os.org> References: <040.7bdfa53a9c29233f892db4fa7a580f73@haiku-os.org> Message-ID: <049.ba27469c729465b1fad26ae6d88ec376@haiku-os.org> #1960: Terminal crash on resize --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by bonefish): Closed this one accidentally, but I guess it is fixed after my recent work on the Terminal anyway. Please reopen, if you encounter it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 20:20:51 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 01 Jul 2008 18:20:51 -0000 Subject: [Haiku-bugs] [Haiku] #2474: Serial port driver needed for Oxford Semi UART 16950 Message-ID: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> #2474: Serial port driver needed for Oxford Semi UART 16950 -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- This is a mini-pci card that uses an Oxford Semiconductor UART to add 4 serial ports, it just needs a driver. From listdev: vendor 1415: Oxford Semiconductor Ltd device 9510: 0x16PCI954 (quad 16950 UART) function 1 (Disabled) vendor 1415: Oxford Semicondutor Ltd device 950c: Unknown -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 23:07:43 2008 From: trac at haiku-os.org (BenoitRen) Date: Tue, 01 Jul 2008 21:07:43 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected Message-ID: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ---------------------------+------------------------------------------------ Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ I run Haiku nightlies on real hardware. My Creative SoundBlaster 16 PCI card does not get detected by Haiku. And I don't just mean that it doesn't have drivers for it. It doesn't show up in syslog or listdev. Everything else is being detected properly. I'm attaching the syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 23:18:04 2008 From: trac at haiku-os.org (umccullough) Date: Tue, 01 Jul 2008 21:18:04 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.80d07eb89aa326cc05f3daa0b5640915@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by umccullough): If I'm not mistaken, these cards were based on the Ensoniq chips (es1370/71/73) and even offered some sort of backward-compatible ISA- emulation features or something... I think I've got a variant of this card at home somewhere - I'll dig it up and give it a try myself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 1 23:46:31 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 01 Jul 2008 21:46:31 -0000 Subject: [Haiku-bugs] [Haiku] #2474: Serial port driver needed for Oxford Semi UART 16950 In-Reply-To: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> References: <042.ce04e5f346a84679de8107cba84f44fc@haiku-os.org> Message-ID: <051.2a1f0ff699df3937309258c7197195ba@haiku-os.org> #2474: Serial port driver needed for Oxford Semi UART 16950 --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * owner: bonefish => axeld * component: Drivers/TTY => Drivers Comment: Do we really need unsupported hardware in Trac? Haiku doesn't (and probably never will) support thousands of hardware devices. I don't really see the point in cluttering the bug tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 00:26:46 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 01 Jul 2008 22:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.6ec9522beb2e7cba2fa5b2a6937a8e31@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): Please create a new syslog with r26205 or newer. I added error output for ATAPI commands. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 00:29:17 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 01 Jul 2008 22:29:17 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.d14e5e60faad05468730ddadad9422a6@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * status: new => assigned Comment: Is this problem still present? Might have been fixed by the tracker mime update change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 02:25:57 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 02 Jul 2008 00:25:57 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.0249cd576bc690a1967ca8a9a348a469@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Hi, Now I get: {{{ 9db5ae04 (+120) 800321c5 :_mutex_unlock + 0x0045 9db5ae7c (+160) 80097a76 :vm_soft_fault__FulbT1 + 0x0296 call 25184 12 -3 yields: 9db5ae7c 80097a76 :vm_soft_fault__FUlbT1(0x18031078, 0x800e7c01, 0xc001 (49153)) }}} Doing cache_tree on 0x18031078 yields ***READ/WRITE FAULT*** In any case, I'm leaving the box in the kernel debugger, please let me know what else I can gather that'd be any use here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 06:49:17 2008 From: trac at haiku-os.org (umccullough) Date: Wed, 02 Jul 2008 04:49:17 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.632ff53a4d7189cdd1e46b4c37b40fcd@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by umccullough): It appears that I do have an SB 16 PCI card - labeled CT4740 (is that the same as yours?) I'll give it a try shortly in my core 2 duo box. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 09:27:54 2008 From: trac at haiku-os.org (korli) Date: Wed, 02 Jul 2008 07:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #2443: kernel missing strupr In-Reply-To: <040.991a17b0a9c3b63cf61943223a15b6ae@haiku-os.org> References: <040.991a17b0a9c3b63cf61943223a15b6ae@haiku-os.org> Message-ID: <049.c6d0ff012611d96f719e59f845878484@haiku-os.org> #2443: kernel missing strupr ----------------------------+----------------------------------------------- Reporter: monni | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * owner: axeld => korli -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 11:20:52 2008 From: trac at haiku-os.org (oco) Date: Wed, 02 Jul 2008 09:20:52 -0000 Subject: [Haiku-bugs] [Haiku] #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT Message-ID: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT -------------------------------+-------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- In AboutSystem, the copyright label display "2001-%ld" instead of "2001-2008". It seems the problem come from the use of B_UTF8_COPYRIGHT in the string. Without it, copyright years are written correctly. It could be possible to workaround the problem in AboutSystem. But, it would mainly hide the real problem in sprintf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 12:03:53 2008 From: trac at haiku-os.org (jackburton) Date: Wed, 02 Jul 2008 10:03:53 -0000 Subject: [Haiku-bugs] [Haiku] #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT In-Reply-To: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> References: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> Message-ID: <047.8e1a672ef4d23792c1795bac6df194b9@haiku-os.org> #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by jackburton): I suspect this being a symptom of #1855. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 13:43:53 2008 From: trac at haiku-os.org (stippi) Date: Wed, 02 Jul 2008 11:43:53 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.40ce5496cf1f754f4be8ae0b30b6a5de@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): This is definitely still a problem and as far as we have analyzed it here, it seems to be a problem in the disk subsystem, so likely AHCI. At the moment, we are trying to see if we can find the change that brought up these pauses. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 13:56:20 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 02 Jul 2008 11:56:20 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.bf1737a11714a3ebb6f9b3781eda7c03@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Not sure if this is the same, but I'm doing an svn checkout of the Haiku sources to an AHCI attached SATA disk here and from time to time it stalls for a few seconds and then continues normally (each maybe 30 seconds or so). When these stalls happen the syslog reads: {{{ KERN: ahci: ExecuteAtaRequest port 0: device timeout KERN: ahci: sata_request::abort called for command 0x25 KERN: ahci: AHCIPort::ResetPort port 0 KERN: ahci: AHCIPort::ResetPort port 0, deviceBusy 0, forceDeviceReset 0 KERN: ahci: AHCIPort::PostReset port 0 KERN: ahci: device signature 0x00000101 (ATA) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 14:17:43 2008 From: trac at haiku-os.org (stippi) Date: Wed, 02 Jul 2008 12:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.5e6fce04513fb499a53509263eeb558d@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Yes, this is the very same issue and I am getting the same output when it happens. During the pauses, icons will not refresh on the Desktop. When they finally refresh again, the above output is printed in the syslog. I am suspecting that these pauses started happening at around r25647 - r25649, but I am not sure and we have not yet tried to revert just the changes from those revisions since later changes make this a bit more difficult. What may also be the case is that the problem was there all along but got undetected before these changes. Marcus, what do you think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 14:48:36 2008 From: trac at haiku-os.org (axeld) Date: Wed, 02 Jul 2008 12:48:36 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.29d97aa8e4fbeaf6724498f924aae632@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): As I pointed out to Ingo on the phone, this might very well be a problem of the interrupt handling. Ie. the edge vs. level detection or selection might not work properly on newer machines anymore, and therefore, interrupts could get lost. At least that's a theory of mine, and I've seen quite a few problems that could be caused by this. I'll intend to look into it in the next few days. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 16:19:55 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 02 Jul 2008 14:19:55 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.05c21298884d5289c52d89057e3db819@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): The error handling in ahci has been improved, starting with r25647 it can now continue after all errors, but will reset the controller first, added in r25649. What takes so long is waiting for the timeout (because no interrupt is received), it was 5 sec in r25597 and has been increased to 20 sec in r25649 (because cache sync is slow). The ahci driver design is pretty simple, inside ExecuteSataRequest() it will execute the command, and waits for the interrupt. fCommandsActive is spinlock protected (except for the abort case), fRegs->ci is changed by the hardware from 1 to 0 if the command execution is complete. (This could be optimized, by starting a timer, and processing the command finish inside the interrupt, without semaphore. Also the sata_request could be made a member of AHCIPort, I want to do so later.) I'm not working on ahci right now, feel free to debug this Axel :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 16:36:41 2008 From: trac at haiku-os.org (axeld) Date: Wed, 02 Jul 2008 14:36:41 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.8e891c6fde18d9bb6c38f21c5b86755c@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): I don't really intend to touch AHCI; I think it's a general Haiku problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 16:56:06 2008 From: trac at haiku-os.org (stippi) Date: Wed, 02 Jul 2008 14:56:06 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.a81d21a7ef26efcbb9b048f23b530852@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * owner: marcusoverhagen => stippi * status: assigned => new Comment: We think we have found the problem... going to confirm soon. Hang on! :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 17:39:31 2008 From: trac at haiku-os.org (stippi) Date: Wed, 02 Jul 2008 15:39:31 -0000 Subject: [Haiku-bugs] [Haiku] #2359: weird pauses during disk access In-Reply-To: <041.e34358929f14904b9a385153c518f095@haiku-os.org> References: <041.e34358929f14904b9a385153c518f095@haiku-os.org> Message-ID: <050.1f83bc94957a2f798b3fd4fd858bee07@haiku-os.org> #2359: weird pauses during disk access ---------------------------+------------------------------------------------ Reporter: stippi | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r26223. It was a race condition that the interrupt was issued before the thread initializing the transfer waited for the release of the semaphore (and the semaphore was only release if someone waited for it). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 17:47:15 2008 From: trac at haiku-os.org (umccullough) Date: Wed, 02 Jul 2008 15:47:15 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.416bf33f92a8a3f4c1db524afb309c24@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by umccullough): Well, it may or may not be the same revision card (Mine is detected as a Creative SB PCI128/Ensoniq AudioPCI 5880) But I attached linux lspci output, Haiku syslog, and Haiku listdev output in case that helps track down your issue. I'll look again, I may even have another card of this series somewhere around here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 17:54:52 2008 From: trac at haiku-os.org (umccullough) Date: Wed, 02 Jul 2008 15:54:52 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.343c95674c7505b5db0d3668655ae9da@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by umccullough): One more thought, have you tried pulling the card out and re-seating it? I've had problems where cards aren't detected due to dust or foreign matter in the PCI slot. Does Linux detect it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 19:13:07 2008 From: trac at haiku-os.org (axeld) Date: Wed, 02 Jul 2008 17:13:07 -0000 Subject: [Haiku-bugs] [Haiku] #2424: usb disk not published if plugged during boot (vmware) In-Reply-To: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> References: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> Message-ID: <051.cb57567ad9416aed08db09d630dedc7b@haiku-os.org> #2424: usb disk not published if plugged during boot (vmware) ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): Well, that at least doesn't seem to have anything to do with this particular problem :-) It's probably another USB issue (I'm *so* glad that Michael tackled this!!! :-)). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 19:38:41 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 02 Jul 2008 17:38:41 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.75d8310ed8256410b2ceab318108a7f9@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Could this perhaps be another victim of ticket #3 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 19:42:40 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 02 Jul 2008 17:42:40 -0000 Subject: [Haiku-bugs] [Haiku] #2424: usb disk not published if plugged during boot (vmware) In-Reply-To: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> References: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> Message-ID: <051.cb58edc70dfc11c58da060acd064d652@haiku-os.org> #2424: usb disk not published if plugged during boot (vmware) ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): In fact the timeout handling I introduced was broken at first. Could you please retry with a current revision and check if this still happens? Please open a new bug if it does. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 20:11:00 2008 From: trac at haiku-os.org (korli) Date: Wed, 02 Jul 2008 18:11:00 -0000 Subject: [Haiku-bugs] [Haiku] #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT In-Reply-To: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> References: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> Message-ID: <047.64a6f1aa2d3918f20b82319a5e53db2f@haiku-os.org> #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by korli): AboutSystem does display here correctly the copyright label with the years. How to reproduce ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 20:26:23 2008 From: trac at haiku-os.org (idefix) Date: Wed, 02 Jul 2008 18:26:23 -0000 Subject: [Haiku-bugs] [Haiku] #2477: Haiku's bootman doesn't show the same partitions as BeOS's Message-ID: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> #2477: Haiku's bootman doesn't show the same partitions as BeOS's --------------------------+------------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- The partition list of Haiku's bootman differs from BeOS's bootman. First of all, only the partitions on the first harddisk are listed. Apparently B_GET_BIOS_DRIVE_ID isn't implemented yet, see [http://dev .haiku-os.org/changeset/25044 Changeset 25044]. Secondly, the Intel Extended Partition is listed which isn't bootable as far as I know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 20:31:07 2008 From: trac at haiku-os.org (BenoitRen) Date: Wed, 02 Jul 2008 18:31:07 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.d8b28438329c891ec80d3a84b7400c77@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by BenoitRen): I booted Puppy Linux on this PC, and went through the ALSA wizard. It didn't detect my sound card. Then I requested the list of PCI devices, and it didn't list it there. My sound card works fine in Windows, though. It's possible that ticket #3 is at work here, as before passing control to the OS, the BIOS displays a list of all detected hardware, and one entry is "Multimedia Controller", with an assigned IRQ of "NA". Looking through the .inf file that's part of Creative's drivers, the id of my card can be either of the following: CTL0001, CTL0031, CTL0041, CTL0043. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 21:05:03 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 02 Jul 2008 19:05:03 -0000 Subject: [Haiku-bugs] [Haiku] #2478: makebootable makes everything unbootable Message-ID: <042.26b418c43549ef987e93525b874dc523@haiku-os.org> #2478: makebootable makes everything unbootable --------------------------+------------------------------------------------- Reporter: emitrax | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Funny summary, but that's exactly what happens. I'm trying to install haiku on real hardware from linux, and when I run makebootable on the partition where I just dd'ed haiku-image I get the following error {{{ emitrax at freak ~/programming/haiku/haiku $ sudo generated/objects/linux/x86/release/tools/makebootable/platform/bios_ia32/makebootable /dev/hdb3 Partition::SetTo(): active: 0 Partition::SetTo(): active: 0 Partition::CheckLocation() - end after session: 70005358080 (session: 33822351360) intel: _ParsePrimary(): partition 1: bad location, ignoring Partition::SetTo(): active: 0 Partition::CheckLocation() - end after session: 81956689920 (session: 33822351360) intel: _ParsePrimary(): partition 2: bad location, ignoring Partition::SetTo(): active: 0 }}} When I reboot the system, not matter what I try to run (ubuntu mostly), I get the following error from grub: {{{ Error 18: Selected cylinder exceeds maximun supported by BIOS }}} To fix it, I had to run a linux live cd, run cfdisk and rewrite the partition table. Let me know if you need anything else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 21:18:21 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 02 Jul 2008 19:18:21 -0000 Subject: [Haiku-bugs] [Haiku] #2478: makebootable makes everything unbootable In-Reply-To: <042.26b418c43549ef987e93525b874dc523@haiku-os.org> References: <042.26b418c43549ef987e93525b874dc523@haiku-os.org> Message-ID: <051.89b5b29af3551d531e8a7eb440b77cd6@haiku-os.org> #2478: makebootable makes everything unbootable ---------------------------+------------------------------------------------ Reporter: emitrax | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by emitrax): BTW: This is my the first disk where I have installed the bootloader, along with my linux root partition. {{{ Disk /dev/hda: 20.0 GB, 20020396032 bytes 255 heads, 63 sectors/track, 2434 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xc6dfc6df Device Boot Start End Blocks Id System /dev/hda1 * 1 63 506047 82 Linux swap / Solaris /dev/hda2 64 2434 19045057+ 83 Linux }}} And this is my second disk where I keep a few partition. For the record, there used to be two bfs partition, one for BeOS Max Edition (which I used to install haiku) and one for haiku, and they both used to boot fines. {{{ Disk /dev/hdb: 81.9 GB, 81964302336 bytes 255 heads, 63 sectors/track, 9964 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x8f800000 Device Boot Start End Blocks Id System /dev/hdb1 1 3647 29294496 83 Linux /dev/hdb2 3648 8511 39070080 5 Extended /dev/hdb3 8512 9964 11671222+ 83 Linux /dev/hdb5 3648 6079 19535008+ 83 Linux /dev/hdb6 6080 8511 19535008+ 83 Linux }}} The partition I'm now trying to install haiku on is hdb3. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 2 21:32:17 2008 From: trac at haiku-os.org (korli) Date: Wed, 02 Jul 2008 19:32:17 -0000 Subject: [Haiku-bugs] [Haiku] #2443: kernel missing strupr In-Reply-To: <040.991a17b0a9c3b63cf61943223a15b6ae@haiku-os.org> References: <040.991a17b0a9c3b63cf61943223a15b6ae@haiku-os.org> Message-ID: <049.f8e7fb264cf47f211aa591fbff20d15b@haiku-os.org> #2443: kernel missing strupr ----------------------------+----------------------------------------------- Reporter: monni | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Thanks! applied in r26226 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 00:29:55 2008 From: trac at haiku-os.org (umccullough) Date: Wed, 02 Jul 2008 22:29:55 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.352675355b937636ed41e4600577e106@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by umccullough): Is it possible you have the BIOS set to not set an IRQ for that specific slot? What happens if you move the card to another slot entirely? Older machines had a way to reset ESCD information from the BIOS - you could try that... but I'm not sure if that was ISA specific or not (I'm guessing it was since it doesn't seem to be a feature on newer machines). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 01:06:51 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 02 Jul 2008 23:06:51 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.6a73aa1e95c7888768302c64798f0e22@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Sorry, I should have been more explicit: With the userland address you have, you can get the area the address resides in via {{{area 0x18031078}}}. The area should have a VM cache, which is listed by the "area" command. This one can be fed to "cache_tree" or "cache". Anyway, the new crash address says that we happen to be in vm_soft_fault(), fault_get_page() returned B_OK and a valid page, but a NULL pageSource. This shouldn't happen and looking through the sources I haven't spotted anything that might cause it. Can you please add a check at the end of fault_get_page() if the cache to return is NULL and panic() if so (add the page to the panic() message). The same for fault_find_page() -- in case of {{{*_restart == true}}} a NULL cache is fine, though. If one of the panic()s is triggered the output of "page" for the page (if it is non-NULL) would be interesting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 01:10:29 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 02 Jul 2008 23:10:29 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.3da8a5ef5cbc699269f220ce4169f3f2@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): area 0x18031078 actually returns several pages worth of areas, is this normal? Note that for all cases, the area name is 'heap'. Will make the changes asked and rebuild in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 01:11:22 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 02 Jul 2008 23:11:22 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.f54ba108d69e4e17886cae9e33d6c3a1@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Also note, the base is always 0x18000000, but the size varies, as does the owner. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 02:49:27 2008 From: trac at haiku-os.org (lawsonwa) Date: Thu, 03 Jul 2008 00:49:27 -0000 Subject: [Haiku-bugs] [Haiku] #2479: System reboots before reaching splash screen Message-ID: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> #2479: System reboots before reaching splash screen --------------------------------+------------------------------------------- Reporter: lawsonwa | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Expected behavior: The sytem boots to the Haiku desktop. Experienced behavior: The system will reboot before reaching the haiku splash screen. Steps to reproduce: Attempt to book Haiku from disk. Motherboard - Gigabyte P35-DSR3 (rev 2.0) Processor - Intel Core2 Duo E6550. Boot Volume - SATA hard disk (/dev/sda4 in Linux) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 05:27:56 2008 From: trac at haiku-os.org (Bouncer) Date: Thu, 03 Jul 2008 03:27:56 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.9834e58d8f6b089d380e96dc969cd663@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by Bouncer): OK - Here is the latest syslog, for r26212 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 06:35:36 2008 From: trac at haiku-os.org (Bouncer) Date: Thu, 03 Jul 2008 04:35:36 -0000 Subject: [Haiku-bugs] [Haiku] #2480: DriveSetup Partition names are out of Sync. Message-ID: <042.aba42e5535725ea887e019bfdd0c4939@haiku-os.org> #2480: DriveSetup Partition names are out of Sync. -----------------------+---------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Referring to the image I am attaching. Referring to 'screen1.png' attachment: 1) I select /dev/disk/ata/0/master/1 (ie: The 'Experimental' partition) 2) From the Menu - I 'Initiallize' it. As a 'Be Filesystem'. Confirming my choice. 3) When asked - I Input a new name eg: 'Second-Haiku'. And hit the 'Initiallize' button. Again confirming my action. Referring to the attachment 'screen2.png' a) The Graphic image has not changed the Volume Name. It is still displaying 'Experimental'. (Ignore what appears to be a mis-spelling. The name was simply clipped when I dragged the pop-up out of the way. The fact that it did not refresh reliably -may be a second error.) b) the Device listing however - has changed the Volume Name. It is correctly displayed as 'Second-Haiku'. c) And the Display popup informs me that I have successfully Initiallized the 'Haiku' Partition. Where did that come from? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 08:24:32 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Thu, 03 Jul 2008 06:24:32 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.7f96ce4eb91bd44b949019581db1dd4a@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): Are you sure that a CD is inserted? Can you please insert / cycle a CD and try again? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 09:25:30 2008 From: trac at haiku-os.org (oco) Date: Thu, 03 Jul 2008 07:25:30 -0000 Subject: [Haiku-bugs] [Haiku] #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT In-Reply-To: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> References: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> Message-ID: <047.3636f6d975f7c73bfc63e7c5a7e69905@haiku-os.org> #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by oco): Oups ! It is my mistake. It is my quick and dirty workaround for bug #2041 that cause the problem in the AboutSystem. So, i think we can close this one... Sorry... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 09:46:25 2008 From: trac at haiku-os.org (korli) Date: Thu, 03 Jul 2008 07:46:25 -0000 Subject: [Haiku-bugs] [Haiku] #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT In-Reply-To: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> References: <038.327cb0dd810b154746ca2d9a6657041d@haiku-os.org> Message-ID: <047.2893543c66ce55d2eefe3b2aab12f49a@haiku-os.org> #2476: snprintf does not like UTF8 characters like B_UTF8_COPYRIGHT --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 09:46:46 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 03 Jul 2008 07:46:46 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.431f109670e1d9b2cd548468170c7df1@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:9 anevilyak]: > area 0x18031078 actually returns several pages worth of areas, is this normal? Note that for all cases, the area name is 'heap'. Will make the changes asked and rebuild in any case. Yep, the area of the team in which the crash happens is the interesting one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 11:51:46 2008 From: trac at haiku-os.org (stippi) Date: Thu, 03 Jul 2008 09:51:46 -0000 Subject: [Haiku-bugs] [Haiku] #2479: System reboots before reaching splash screen In-Reply-To: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> References: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> Message-ID: <052.b92c29e631f3efe4ccd1724da1c65ba8@haiku-os.org> #2479: System reboots before reaching splash screen ---------------------------------+------------------------------------------ Reporter: lawsonwa | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): If you build your own images, you could try to switch to the new ATA bus manager. Change the file src/add-ons/kernel/bus_managers/Jamfile, the line {{{ SubInclude HAIKU_TOP src add-ons kernel bus_managers ide ; -> SubInclude HAIKU_TOP src add-ons kernel bus_managers ata ; }}} Does that change anything? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 12:10:54 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 03 Jul 2008 10:10:54 -0000 Subject: [Haiku-bugs] [Haiku] #1744: Amilo A7640W: Network doesn't work (sis900) In-Reply-To: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> References: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> Message-ID: <054.0d355b1e86897ff78e301fb029505602@haiku-os.org> #1744: Amilo A7640W: Network doesn't work (sis900) ------------------------------+--------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by jackburton): I see lots of "RX underrun" interrupts in the syslog, but nothing else. Is it possible that this problem is caused by too many devices sharing the same interrupt ? The NIC is on irq line 5, just like the audio card, the 4-in-1 card reader, and the usb controller. On linux this card is on IRQ line 18, and doesnt' share IRQs with any other device. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 12:12:38 2008 From: trac at haiku-os.org (lawsonwa) Date: Thu, 03 Jul 2008 10:12:38 -0000 Subject: [Haiku-bugs] [Haiku] #2479: System reboots before reaching splash screen In-Reply-To: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> References: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> Message-ID: <052.e8688568c10482d685849772700c9deb@haiku-os.org> #2479: System reboots before reaching splash screen ---------------------------------+------------------------------------------ Reporter: lawsonwa | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by lawsonwa): Using the ATA bus manager gives the same results. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 13:00:17 2008 From: trac at haiku-os.org (mmlr) Date: Thu, 03 Jul 2008 11:00:17 -0000 Subject: [Haiku-bugs] [Haiku] #2479: System reboots before reaching splash screen In-Reply-To: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> References: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> Message-ID: <052.446b577849650ae9a501921b30555a9c@haiku-os.org> #2479: System reboots before reaching splash screen ---------------------------------+------------------------------------------ Reporter: lawsonwa | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by mmlr): It looks like this happens in the bootloader already so the ide/ata bus managers aren't yet used. I had "similar" issues when doing the kernel heap rewrite yesterday. I had uninitialized memory in there that would lead to a triple fault and therefore a reboot. It didn't show up in QEMU as it entirely depends on what happens to be in the RAM pages at the time (under QEMU it was all 0 so didn't cause problems). So maybe there are some uninitialized variables/structures/pointers used in the bootloader that usually happen to be 0, but on this specific system/configuration aren't? Of course this is just a wild guess because the outcome is the same, there are of course many other possible reasons for this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 14:07:45 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 03 Jul 2008 12:07:45 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.121f931922f2890c593f425032789f68@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): The panic happens in fault_find_page, which gets called by fault_get_page, page address is 0x9b109ed4, dump is: {{{ PAGE: 0x9b109ed4 queue_next, prev: 0x80082d87, 0x9b109f44 physical_number: 9f2004e0 cache: 0x9f200720 cache_offset: 51 cache_next: 0x00000000 type: 1 state: busy wired_count: 0 usage_count: 2 busy_writing: 0 area_mappings: }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 14:37:35 2008 From: trac at haiku-os.org (stippi) Date: Thu, 03 Jul 2008 12:37:35 -0000 Subject: [Haiku-bugs] [Haiku] #2245: OpenGrok search is very much out of date In-Reply-To: <050.52e169c3eecc428c1bb91eccc4bcb163@haiku-os.org> References: <050.52e169c3eecc428c1bb91eccc4bcb163@haiku-os.org> Message-ID: <059.bb2dac74467f957d23c6e89aa305a4a8@haiku-os.org> #2245: OpenGrok search is very much out of date ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Ok, closing. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 16:22:02 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 03 Jul 2008 14:22:02 -0000 Subject: [Haiku-bugs] [Haiku] #2480: DriveSetup Partition names are out of Sync. In-Reply-To: <042.aba42e5535725ea887e019bfdd0c4939@haiku-os.org> References: <042.aba42e5535725ea887e019bfdd0c4939@haiku-os.org> Message-ID: <051.292d684aaa4a0ae5b8350f0e3c07822d@haiku-os.org> #2480: DriveSetup Partition names are out of Sync. --------------------------------------+------------------------------------- Reporter: Bouncer | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by anevilyak): * owner: axeld => stippi * component: - General => Applications/DriveSetup Comment: Switching this to the correct component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 17:01:28 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 03 Jul 2008 15:01:28 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.f47bcc91adf8c97a74f0c73935c6ad23@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Also, just to be sure I did it correctly, the panic check I had in fault_find_page was {{{ if (!(*_restart) && cache == NULL) }}}, right before the values are written into the passed in pointers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 17:30:52 2008 From: trac at haiku-os.org (stippi) Date: Thu, 03 Jul 2008 15:30:52 -0000 Subject: [Haiku-bugs] [Haiku] #1823: On some systems (real hardware) any direct to framebuffer drawing is really slow In-Reply-To: <041.7df384fc5474b32190f81eeeb4a63aa8@haiku-os.org> References: <041.7df384fc5474b32190f81eeeb4a63aa8@haiku-os.org> Message-ID: <050.bef730912bcb6da098faa6f8f716371d@haiku-os.org> #1823: On some systems (real hardware) any direct to framebuffer drawing is really slow ----------------------------+----------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by stippi): This seemed to have helped, I got a new syslog. However, I am getting Internal Server Errors when I try to attach it. Therefor I am pasting what seems to me to be the relevant output: {{{ 2008-07-03 15:05:29 KERN: allocate_commpage_entry(4, 34) -> 0xffff0118 2008-07-03 15:05:29 KERN: set_memory_write_back base 0 length 3ff80000 2008-07-03 15:05:29 KERN: find_nearest 3ff80000 0 2008-07-03 15:05:29 KERN: find_nearest 1ff80000 1 2008-07-03 15:05:29 KERN: find_nearest ff80000 2 2008-07-03 15:05:29 KERN: find_nearest 7f80000 3 2008-07-03 15:05:29 KERN: find_nearest 3f80000 4 2008-07-03 15:05:29 KERN: find_nearest 1f80000 5 2008-07-03 15:05:29 KERN: find_nearest 80000 5 2008-07-03 15:05:29 KERN: find_nearest 80000 4 2008-07-03 15:05:29 KERN: find_nearest 80000 3 2008-07-03 15:05:29 KERN: find_nearest 80000 2 2008-07-03 15:05:29 KERN: find_nearest 80000 1 2008-07-03 15:05:29 KERN: solutions: 0x40000000 0x80000 2008-07-03 15:05:29 KERN: allocate MTRR slot 0, base = 0, length = 40000000, type=0x6 2008-07-03 15:05:29 KERN: allocate MTRR slot 1, base = 3ff80000, length = 80000, type=0x0 2008-07-03 15:05:29 KERN: allocate MTRR slot 2, base = f0000000, length = 400000, type=0x1 [...] 2008-07-03 15:05:29 KERN: Radeon - init_hardware: Version: 5.1.6.0 2008-07-03 15:05:29 KERN: Radeon - Radeon_FindRom: found ROM @0xc0000 2008-07-03 15:05:29 KERN: Radeon - Radeon_CardDetect: found supported device pci index 2, device 0x1002/0x5b60 2008-07-03 15:05:29 KERN: Radeon - init_driver: 2008-07-03 15:05:29 KERN: AGP: bus manager init 2008-07-03 15:05:29 KERN: AGP: found 0 AGP devices 2008-07-03 15:05:29 KERN: Radeon - GetDriverSettings: 2008-07-03 15:05:29 KERN: Radeon - Radeon_FindRom: found ROM @0xc0000 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: device: 010000 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: old PCI command state: 0x00000007 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: physical address of memory-mapped I/O: 0xfe9e0000-0xfe9effff 2008-07-03 15:05:29 KERN: Radeon - Radeon_GetPLLInfo: ref_clk=2700, ref_div=12, xclk=20000, min_freq=20000, max_freq=40000 from Legacy BIOS 2008-07-03 15:05:29 KERN: Radeon - Radeon_GetConnectorInfoFromBIOS: Port0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-3 2008-07-03 15:05:29 KERN: Radeon - Radeon_GetConnectorInfoFromBIOS: Port1: DDCType-3, DACType-0, TMDSType-1, ConnectorType-3 2008-07-03 15:05:29 KERN: Radeon - Radeon_GetTMDSInfoFromBios: DFP table revision: 4 2008-07-03 15:05:29 KERN: Radeon - RADEON_GetAccessibleVRAM: Generation 2 PCI interface, using max accessible memory 2008-07-03 15:05:29 KERN: Radeon - Radeon_DetectRAM: Detected total video RAM=131072K, accessible=131072K (PCI BAR=131072K) 2008-07-03 15:05:29 KERN: Radeon - Radeon_DetectRAM: 128 MB SDR SGRAM found on 64 wide bus 2008-07-03 15:05:29 KERN: Radeon - Radeon_UnmapDevice: 2008-07-03 15:05:29 KERN: Radeon - probeDevice: found Radeon X300 (RV370) 5B60; ASIC: rv380 2008-07-03 15:05:29 KERN: Radeon - probeDevice: making /dev/graphics/1002_5B60_010000 2008-07-03 15:05:29 KERN: Radeon - Radeon_ProbeDevices: 1 supported devices 2008-07-03 15:05:29 KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/radeon 2008-07-03 15:05:29 KERN: S3: init_hardware() - no supported devices 2008-07-03 15:05:29 KERN: savage: init_hardware - no supported devices 2008-07-03 15:05:29 KERN: vesa: init_hardware() 2008-07-03 15:05:29 KERN: vesa: init_driver() 2008-07-03 15:05:29 KERN: vesa: publish_devices() 2008-07-03 15:05:29 KERN: vesa: find_device() 2008-07-03 15:05:29 KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/vesa 2008-07-03 15:05:29 KERN: Radeon - open_hook: name=graphics/1002_5B60_010000, flags=2, cookie=0x90c5e720 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: device: 010000 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: old PCI command state: 0x00000006 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: physical address of memory-mapped I/O: 0xfe9e0000-0xfe9effff 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: physical address of framebuffer: 0xf0000000-0xf7ffffff 2008-07-03 15:05:29 KERN: allocate MTRR slot 3, base = f0000000, length = 8000000, type=0x1 2008-07-03 15:05:29 KERN: Radeon - Radeon_MapDevice: mapped frame buffer @0x98000000 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: Copy of Laptop Display Regs for Reference: 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: LVDS GEN = 804008a 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: LVDS PLL = 128c 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: TMDS PLL = 1fb800cd 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: TMDS TRANS = 10000040 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: FP1 GEN = bc2c000 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: FP2 GEN = 1240080c 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: TV DAC = 7660142 2008-07-03 15:05:29 KERN: Radeon - createGARTBuffer: 2008-07-03 15:05:29 KERN: Radeon - initGATT: 2008-07-03 15:05:29 KERN: Radeon - initGATT: GATT_ptr=0x93800000, GATT_phys=0x02a61000 2008-07-03 15:05:29 KERN: pci_gart_map_area: 2457 2008-07-03 15:05:29 KERN: Radeon - Radeon_InitMemController: Graphics card address mapping: 2008-07-03 15:05:29 KERN: Radeon - Radeon_InitMemController: local memory 0x8000000 at 0xf0000000 2008-07-03 15:05:29 KERN: Radeon - Radeon_InitMemController: PCI GART 0x2000000 at 0x3ff80000 2008-07-03 15:05:29 KERN: Radeon - Radeon_InitMemController: disabled AGP GART 0x400000 at 0x42000000 2008-07-03 15:05:29 KERN: Radeon - Radeon_SetupIRQ: installed IRQ @ 11 2008-07-03 15:05:29 KERN: AGP: get_nth_agp_info(index 0) 2008-07-03 15:05:29 KERN: Radeon - Radeon_Set_AGP: No AGP capable devices found. 2008-07-03 15:05:29 KERN: Radeon - Radeon_FirstOpen: DMA is diabled using PIO mode 2008-07-03 15:05:29 KERN: Radeon - open_hook: returning 0x00000000 2008-07-03 15:05:29 KERN: Radeon - Radeon_DetectTVOut: 2008-07-03 15:05:29 KERN: DDC: ddc2_read(): DDC information read failure 2008-07-03 15:05:29 KERN: Last message repeated 3 times. 2008-07-03 15:05:29 KERN: Radeon - Radeon_ReadEDID: Found DDC-capable monitor @0x0060 2008-07-03 15:05:29 KERN: Radeon - Radeon_DetectDisplays: Edid Data for CRTC 1 on line 3 }}} Hope this is useful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 18:11:05 2008 From: trac at haiku-os.org (korli) Date: Thu, 03 Jul 2008 16:11:05 -0000 Subject: [Haiku-bugs] [Haiku] #1823: On some systems (real hardware) any direct to framebuffer drawing is really slow In-Reply-To: <041.7df384fc5474b32190f81eeeb4a63aa8@haiku-os.org> References: <041.7df384fc5474b32190f81eeeb4a63aa8@haiku-os.org> Message-ID: <050.c469efbb25a08306c5304d942984818e@haiku-os.org> #1823: On some systems (real hardware) any direct to framebuffer drawing is really slow ----------------------------+----------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): Hey Stephan, as I see them, MTRR seem like in my setup. Maybe you noticed there is an overlapping of MTRR 2 et 3. Could you try to disable the setup of MTTR 2 in src/system/kernel/debug/frame_buffer_console.cpp (function frame_buffer_console_init_post_modules) ? HTH J?r?me -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 18:52:40 2008 From: trac at haiku-os.org (axeld) Date: Thu, 03 Jul 2008 16:52:40 -0000 Subject: [Haiku-bugs] [Haiku] #1744: Amilo A7640W: Network doesn't work (sis900) In-Reply-To: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> References: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> Message-ID: <054.385b7698065cf9f50280d2fc5b839a2b@haiku-os.org> #1744: Amilo A7640W: Network doesn't work (sis900) ------------------------------+--------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by axeld): This is possible if there is a driver that doesn't play well in this case. But you can easily prove that theory by removing the drivers of those other devices - if the driver then works nicely, we can look further :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 20:01:29 2008 From: trac at haiku-os.org (BenoitRen) Date: Thu, 03 Jul 2008 18:01:29 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.d340488fd4533f8d09ddafaf46133a26@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Comment(by BenoitRen): I've looked through my BIOS settings, and there is no setting that has to do with my sound card. I'd rather not move it to another slot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 20:25:16 2008 From: trac at haiku-os.org (korli) Date: Thu, 03 Jul 2008 18:25:16 -0000 Subject: [Haiku-bugs] [Haiku] #2475: SoundBlaster 16 PCI is not detected In-Reply-To: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> References: <044.f65fe568c476028519c411dcc19738e7@haiku-os.org> Message-ID: <053.f15fbaecb738870b987074df11c5ad6e@haiku-os.org> #2475: SoundBlaster 16 PCI is not detected ----------------------------+----------------------------------------------- Reporter: BenoitRen | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * owner: axeld => korli * component: System/Kernel => Drivers/Audio -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 20:35:41 2008 From: trac at haiku-os.org (korli) Date: Thu, 03 Jul 2008 18:35:41 -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.a4968bdad62b4d24229417589e586fc2@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: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): Could you try again with r26239 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 22:05:39 2008 From: trac at haiku-os.org (nielx) Date: Thu, 03 Jul 2008 20:05:39 -0000 Subject: [Haiku-bugs] [Haiku] #2473: Admin - Components - Owner no longer sorted In-Reply-To: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> References: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> Message-ID: <049.7de7c5b96dbc2d43990d69606565cba5@haiku-os.org> #2473: Admin - Components - Owner no longer sorted ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by nielx): * owner: haiku-web => nielx * status: new => assigned Comment: Could you try again please? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 3 23:09:15 2008 From: trac at haiku-os.org (axeld) Date: Thu, 03 Jul 2008 21:09:15 -0000 Subject: [Haiku-bugs] [Haiku] #2473: Admin - Components - Owner no longer sorted In-Reply-To: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> References: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> Message-ID: <049.2a63093efafb4fb8f339c29203256d93@haiku-os.org> #2473: Admin - Components - Owner no longer sorted ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Unless I need to log out, nothing changed (I meant the "new component" box on the right, just in case). Thanks for looking into this! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 00:00:51 2008 From: trac at haiku-os.org (nielx) Date: Thu, 03 Jul 2008 22:00:51 -0000 Subject: [Haiku-bugs] [Haiku] #2473: Admin - Components - Owner no longer sorted In-Reply-To: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> References: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> Message-ID: <049.17eeb413024a52ae5ddabdf4818dd08c@haiku-os.org> #2473: Admin - Components - Owner no longer sorted ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by nielx): Ah I see. I think I found a fix but I need to test it. So more at a later stage. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 01:51:52 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 03 Jul 2008 23:51:52 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.56b6d4e16d2b11087b74b9b54c6bde2f@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Problem understood. Will look into fixing it tomorrow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 05:34:18 2008 From: trac at haiku-os.org (Bouncer) Date: Fri, 04 Jul 2008 03:34:18 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.67b38c546b46395263451acfb5351c3b@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by Bouncer): OK. 1) First - I boot a fresh Haiku installation (r26212) with an Audio CD in the DVD drive. 2) Since it does not see the disk - I cycle disk out and back in to the drive. Again - it does not see it. 3) I remove the Audio CD and load a data CD (an anonymous MS driver install disk). It does not auto-mount. But I do see an entry in the Mount list and I am able to mount it. 4) Next - I unmount and remove the data CD and re-insert the Audio CD. Again - it is not recognized. Have I been mistaken? Does Haiku not support regular audio CD's ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 11:02:10 2008 From: trac at haiku-os.org (stippi) Date: Fri, 04 Jul 2008 09:02:10 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working Message-ID: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working -------------------------+-------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- I searched the tickets for "USB Mouse" and didn't find this exact issue reported yet. It is not a new issue, I have been getting this from time to time for ages, but mistakenly thought that it had been reported before. Sometimes, mostly not shortly after booting, but after a while of using Haiku, my USB mouse and keyboard suddenly stop working. The sensor of the mouse goes off. My PS/2 devices continue to work. I looked at the syslog and found these lines: {{{ [...] usb_uhci: host controller halted USB ControlPipe: timeout waiting for queued request to complete USB Hub 2: error updating port status USB ControlPipe: timeout waiting for queued request to complete USB Hub 2: error updating port status USB ControlPipe: timeout waiting for queued request to complete USB Hub 2: error updating port status USB ControlPipe: timeout waiting for queued request to complete USB Hub 2: error updating port status [...] }}} The last two lines keep repeating. Usually, the hot plugging works good for me, but after this situation, the hot plugging (switching the KVM) does not recover from the error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 12:11:45 2008 From: trac at haiku-os.org (axeld) Date: Fri, 04 Jul 2008 10:11:45 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.4eddbb879fd9491d46241f50ef6fe866@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Definitely works over here with a SATA DVD ROM drive. What audio CD is it? Have you tried different ones? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 13:55:18 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Fri, 04 Jul 2008 11:55:18 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.16e9de9f69031269607e90e129727cfe@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): The only failing commands are: "ATAPI packet 00", Test unit ready, fails when no CD is inserted. "ATAPI packet 28", Read, might fail for non-data CDs. Auto-mounting doesn't seem to work for me, too. Execept during boot. I don't know why audio CDs don't work. Perhaps B_SCSI_READ_CD uses the wrong command for this CD-ROM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 14:16:16 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 04 Jul 2008 12:16:16 -0000 Subject: [Haiku-bugs] [Haiku] #2424: usb disk not published if plugged during boot (vmware) In-Reply-To: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> References: <042.35df8cd311a0e56b991fc311ff4aae9d@haiku-os.org> Message-ID: <051.5115a17c1f04e748924f04de92298164@haiku-os.org> #2424: usb disk not published if plugged during boot (vmware) ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): It happens indeed with r26239 . Opening a new bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 14:18:45 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 04 Jul 2008 12:18:45 -0000 Subject: [Haiku-bugs] [Haiku] #2482: Panic while automounting usb stick Message-ID: <042.53b170180f676ceb1ce08291f051bbdb@haiku-os.org> #2482: Panic while automounting usb stick -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- It seems it happens only on first boot, but I'm not sure whether it is a coincidence, those a race condition, or not. See screenshots attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 15:24:21 2008 From: trac at haiku-os.org (diver) Date: Fri, 04 Jul 2008 13:24:21 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition Message-ID: <040.6709c6f248972105379daa19a294e843@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I mounted my ext3 partition (nice work btw, Axel!) where I store my "/home" folder in Ubuntu. I launched some files (mp3, txt) and they all opened just fine. Then I tried to open .png image, after that I noticed frozen ShowImage window (which couldn't be killed) and high cpu activity. I then took a look at which thread consumed cpu power and it was syslog_sender. Then I did "tail -f /var/log/syslog" and I saw that much information is being written and continue to writing to syslog. So I typed sync just in case. Then I tried to unmount that ext3 partition from Tracker using "Force unmount" button. After that partition didn't disappear from Desktop, but disappeared from "/" folder and Desktop context menu. I decided to reboot and shutdown window said that Tracker is not responding, I used kill button and after that reboot completed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 15:49:32 2008 From: trac at haiku-os.org (diver) Date: Fri, 04 Jul 2008 13:49:32 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.3b85307e74f22a3a8b8e2b9ae5d12a4c@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): I just tried again and I could reproduce it. Am I right tat this could point to 3 issues? 1. Unkillable ShowImage window. 2. Refresh desktop icons after force unmount 3. Something is wrong with this .png image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 16:09:59 2008 From: trac at haiku-os.org (diver) Date: Fri, 04 Jul 2008 14:09:59 -0000 Subject: [Haiku-bugs] [Haiku] #2429: [Terminal] Resizing Terminal is very slow In-Reply-To: <040.a0c743f1f2844c26f136b86ba429050c@haiku-os.org> References: <040.a0c743f1f2844c26f136b86ba429050c@haiku-os.org> Message-ID: <049.fe35a70d05c8116f271b636ea155693e@haiku-os.org> #2429: [Terminal] Resizing Terminal is very slow ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): I tried VESA mode and it indeed removed slowness and flickering. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 16:10:02 2008 From: trac at haiku-os.org (diver) Date: Fri, 04 Jul 2008 14:10:02 -0000 Subject: [Haiku-bugs] [Haiku] #2432: [app_server] Moving a tracker window above terminal lags badly In-Reply-To: <040.504a13814b1143f7d5f53bcf62b7fd78@haiku-os.org> References: <040.504a13814b1143f7d5f53bcf62b7fd78@haiku-os.org> Message-ID: <049.63a3294e3e6b93d7569bb42ad85782c9@haiku-os.org> #2432: [app_server] Moving a tracker window above terminal lags badly ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): I tried VESA mode and it indeed removed slowness and flickering. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 16:12:33 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 04 Jul 2008 14:12:33 -0000 Subject: [Haiku-bugs] [Haiku] #2482: Panic while automounting usb stick In-Reply-To: <042.53b170180f676ceb1ce08291f051bbdb@haiku-os.org> References: <042.53b170180f676ceb1ce08291f051bbdb@haiku-os.org> Message-ID: <051.0e3c69d8529a97928f5021d22bc9ddbd@haiku-os.org> #2482: Panic while automounting usb stick ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: This is not a race condition or anything, it's a plain simple timeout that happens. The device does not respond quickly enough therefore usb_disk will abort and return a timeout error ("error: Operation timed out"). The timeout I (arbitrarily) set is 2 seconds right now, which might just not be enough. Please increase the timeout in src/add- ons/kernel/drivers/disk/usb/usb_disk/usb_disk.cpp line 145 by a second until you don't see this happening anymore and report how much it needs. Other subsystems seem to use timeouts of up to 20 seconds, but I don't really want to increase it that much. Maybe 3 or 5 seconds would be acceptable though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 16:16:09 2008 From: trac at haiku-os.org (diver) Date: Fri, 04 Jul 2008 14:16:09 -0000 Subject: [Haiku-bugs] [Haiku] #2457: [Firefox] Link broken, and runtime_loader cannot open file libmozjs.so In-Reply-To: <043.9b7f1fded642b58271f2a289f5d606a2@haiku-os.org> References: <043.9b7f1fded642b58271f2a289f5d606a2@haiku-os.org> Message-ID: <052.88407fc2d1bef495ddd692adca7c18a3@haiku-os.org> #2457: [Firefox] Link broken, and runtime_loader cannot open file libmozjs.so ---------------------------+------------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): This is how I start firefox which comes from OptionalPackage: cd /boot/apps/firefox ./firefox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 17:47:46 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 04 Jul 2008 15:47:46 -0000 Subject: [Haiku-bugs] [Haiku] #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku In-Reply-To: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> References: <044.56406569b88a99d8ac7750d826ed82b0@haiku-os.org> Message-ID: <053.bf69d78605916dafc4f1bea007280456@haiku-os.org> #2471: PANIC: page fault but interrupts were disabled. Touching address 0x00000008 from eip 0x80031f85 while building Haiku ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26248. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 17:52:19 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 04 Jul 2008 15:52:19 -0000 Subject: [Haiku-bugs] [Haiku] #2429: [Terminal] Resizing Terminal is very slow In-Reply-To: <040.a0c743f1f2844c26f136b86ba429050c@haiku-os.org> References: <040.a0c743f1f2844c26f136b86ba429050c@haiku-os.org> Message-ID: <049.1147624c4ff30ebd9532389d088d2b69@haiku-os.org> #2429: [Terminal] Resizing Terminal is very slow ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Thank! Closing as dup of #1823 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 17:53:07 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 04 Jul 2008 15:53:07 -0000 Subject: [Haiku-bugs] [Haiku] #2432: [app_server] Moving a tracker window above terminal lags badly In-Reply-To: <040.504a13814b1143f7d5f53bcf62b7fd78@haiku-os.org> References: <040.504a13814b1143f7d5f53bcf62b7fd78@haiku-os.org> Message-ID: <049.6f14f067d25e24a378d41766b78b7bc3@haiku-os.org> #2432: [app_server] Moving a tracker window above terminal lags badly ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => duplicate Comment: Thank! Closing as dup of #1823 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 19:23:44 2008 From: trac at haiku-os.org (korli) Date: Fri, 04 Jul 2008 17:23:44 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.1a4b55f4292935db879031a1e62a9b4f@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * owner: axeld => mmlr Comment: Seems it's due to Michael's changes to kernel heap allocator. Reassigning to let him check. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 19:45:33 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 04 Jul 2008 17:45:33 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.a0dd6234763124866c54dd0b6fe53b92@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * owner: mmlr => axeld Comment: Nope, except for the missing newline in the dprintf (fixed in r26251) there's nothing wrong from the heap perspective. With previous revisions of the heap this would simply have hit a panic("huge allocation") right away while the requests are now handled through areas. The debug output is purely informational. The real problem at hand is that someone actually allocates/reallocates such a huge amount of memory through the kernel heap. Since this is happening from an ext3 partition and the corresponding filesystem add-on is pretty new still I'll take the liberty to reassign this back to Axel :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 20:17:04 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 04 Jul 2008 18:17:04 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.02920a1177bf90fcee6f228a10c977df@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Looking through it only quickly I would point my finger at ext2_read_pages(). There file_map_translate() is called, which in turn adds vectors to the file map, which then reallocates the array. This is the only place I could see a realloc coming from. Note that taking an allocation size of 8298240 bytes would amount to an extent count of 345760, as each file_extent is 24 bytes. So I guess either the ext2_read_pages() function has a problem, or something got messed up so the ext2 filesystem add-on actually thinks it requires such a large amount of file_extents. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 20:35:30 2008 From: trac at haiku-os.org (kaliber) Date: Fri, 04 Jul 2008 18:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #2459: KDL while trying to jam In-Reply-To: <042.aa306801161a488a952f2e71252f40cb@haiku-os.org> References: <042.aa306801161a488a952f2e71252f40cb@haiku-os.org> Message-ID: <051.10177fb71d2a79f26f8788a9b48f2c22@haiku-os.org> #2459: KDL while trying to jam ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kaliber): Duplicate of bug 2471 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 4 20:43:32 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 04 Jul 2008 18:43:32 -0000 Subject: [Haiku-bugs] [Haiku] #2459: KDL while trying to jam In-Reply-To: <042.aa306801161a488a952f2e71252f40cb@haiku-os.org> References: <042.aa306801161a488a952f2e71252f40cb@haiku-os.org> Message-ID: <051.6baa658e92194a633d53c3e0c53f195c@haiku-os.org> #2459: KDL while trying to jam ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: Duplicate of now fixed bug #2471. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 5 10:52:47 2008 From: trac at haiku-os.org (mrsunshine) Date: Sat, 05 Jul 2008 08:52:47 -0000 Subject: [Haiku-bugs] [Haiku] #2366: Mouse stops working In-Reply-To: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> References: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> Message-ID: <054.136fbe765c705929a46b022de7f694bb@haiku-os.org> #2366: Mouse stops working --------------------------------+------------------------------------------- Reporter: mrsunshine | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by mrsunshine): * cc: tomas.wilhelmsson at gmail.com (added) * platform: All => x86 Comment: KERN: ps2: probe_mouse Standard PS/2 mouse found [[BR]] KERN: auich: init_hardware() [[BR]] KERN: auvia: init_hardware() [[BR]] KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/audio/hmulti/emuxki [[BR]] KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 [[BR]] KERN: ps2: devfs_unpublish_device input/mouse/ps2/0, status = 0x00000000 [[BR]] KERN: ps2: devfs_unpublish_device input/mouse/ps2/1, status = 0x00000000 [[BR]] KERN: ps2: devfs_unpublish_device input/mouse/ps2/2, status = 0x00000000 [[BR]] KERN: ps2: keyboard found [[BR]] KERN: ps2: hot removal of input/mouse/ps2/3 [[BR]] KERN: ps2: ps2_mouse_disconnect input/mouse/ps2/3 [[BR]] KERN: ps2: devfs_unpublish_device input/mouse/ps2/3, status = 0x00000000 [[BR]] The output i get now from the syslog, still same problem tho (r26258) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 5 23:37:52 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 05 Jul 2008 21:37:52 -0000 Subject: [Haiku-bugs] [Haiku] #2366: Mouse stops working In-Reply-To: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> References: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> Message-ID: <054.ee655c14ab3c7c1951bc2a48a2e4241a@haiku-os.org> #2366: Mouse stops working --------------------------------+------------------------------------------- Reporter: mrsunshine | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by marcusoverhagen): * status: new => assigned Comment: Please enable #define TRACE_PS2 in src/add-ons/kernel/bus_managers/ps2/ps2_common.h compile, install capture a new syslog, move the mouse until it doesn't work anymore. What kind of mouse is that? What kind of motherboard/notebook? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 00:37:12 2008 From: trac at haiku-os.org (mrsunshine) Date: Sat, 05 Jul 2008 22:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #2366: Mouse stops working In-Reply-To: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> References: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> Message-ID: <054.7ecee1386b9d3cdf9b980e07c24252fb@haiku-os.org> #2366: Mouse stops working --------------------------------+------------------------------------------- Reporter: mrsunshine | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by mrsunshine): Its a touchpad on a acer 3050 laptop -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 09:52:55 2008 From: trac at haiku-os.org (laplace) Date: Sun, 06 Jul 2008 07:52:55 -0000 Subject: [Haiku-bugs] [Haiku] #1727: Haiku panics with vm_page fault/double fault after 20-30s usage In-Reply-To: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> References: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> Message-ID: <047.fe5fe54eef78a99e6ffb51a92c834e46@haiku-os.org> #1727: Haiku panics with vm_page fault/double fault after 20-30s usage ----------------------------+----------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by laplace): Applied patch by JiSheng Zhang in r26272. Please test. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 14:08:53 2008 From: trac at haiku-os.org (nielx) Date: Sun, 06 Jul 2008 12:08:53 -0000 Subject: [Haiku-bugs] [Haiku] #2473: Admin - Components - Owner no longer sorted In-Reply-To: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> References: <040.3496a1447e53e3a12ad6fc71e0e1f1f9@haiku-os.org> Message-ID: <049.541d26dfb1b20e7fbee3f0c2d580b670@haiku-os.org> #2473: Admin - Components - Owner no longer sorted ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by nielx): * status: assigned => closed * resolution: => fixed Comment: Fixed locally, upstream [http://trac.edgewall.org/ticket/7412 ticket #7412]. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 14:38:01 2008 From: trac at haiku-os.org (nielx) Date: Sun, 06 Jul 2008 12:38:01 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.f6cdd2af5c5f832932557fcab91a7a0a@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by nielx): Could you please elaborate on where you are missing the nested components? They are working in ticket details, and when writing a new ticket, and when adding a component to the query. Can you please elaborate? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 18:29:34 2008 From: trac at haiku-os.org (mauricek) Date: Sun, 06 Jul 2008 16:29:34 -0000 Subject: [Haiku-bugs] [Haiku] #2422: [Cortex] useless menus In-Reply-To: <040.b3135044b47e24a1a50d326ade3acb6a@haiku-os.org> References: <040.b3135044b47e24a1a50d326ade3acb6a@haiku-os.org> Message-ID: <049.16cec39d7ef808cfd219e2e9884317a7@haiku-os.org> #2422: [Cortex] useless menus ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by mauricek): * cc: haiku at kaldience.com (added) Comment: The last two points are invalid. 1. "Window->Start Control Panel". Each addon is allowed to have a custom user interface, which can be started in addition, while the regular way is over parameters with the Media Theme "designing" the interface. 2. "Themes->Haiku Theme". Theoretically it is possible to have your own theme. This will/should be displayed in that menu then, so that the user can decide on a theme to use. This is R5 Media Kit functionality, which has been used quite rarely, but is available nevertheless. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 20:57:47 2008 From: trac at haiku-os.org (monni) Date: Sun, 06 Jul 2008 18:57:47 -0000 Subject: [Haiku-bugs] [Haiku] #2484: FindPetition doesn't handle cases when event has alternative opcodes Message-ID: <040.2f6c124ce0b32ca434c41ecf66c29c00@haiku-os.org> #2484: FindPetition doesn't handle cases when event has alternative opcodes -------------------------------+-------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- When trying to find matching message, LocalDeviceHandler::FindPetition stops looking for correct message if event matches but opcode isn't correct. In some cases there is alternative opcodes for same event. Experienced behaviour: Message is not found Expected behaviour: continue looking until opcode matches or runs out of subitems in fEventsWanted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 6 23:49:23 2008 From: trac at haiku-os.org (atomozero) Date: Sun, 06 Jul 2008 21:49:23 -0000 Subject: [Haiku-bugs] [Haiku] #1609: NetworkStatus -> No Link In-Reply-To: <044.c3485fc46adb9faa461baf3ebe86aa0c@haiku-os.org> References: <044.c3485fc46adb9faa461baf3ebe86aa0c@haiku-os.org> Message-ID: <053.bdcbaee659a2dca56028c69c3a950334@haiku-os.org> #1609: NetworkStatus -> No Link ------------------------------+--------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by atomozero): * status: closed => reopened * resolution: fixed => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 12:00:09 2008 From: trac at haiku-os.org (axeld) Date: Mon, 07 Jul 2008 10:00:09 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.245a637adb3446e85217fced7db92558@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): In fact, the file map implementation was pretty simple - it was enough for the extent based BFS, but wasn't up to handle something like ext2. I've improved it in r26260, but we should actually use a sparse array, and don't need to have space for the whole file (right now, it allows for partial maps, but only it still has to be contiguous, and start from offset 0). Even though it should rarely happen for real, but ext2 could easily need as many extents as outlined by Michael; it remembers each file block individually. It would also be nice if we could flush the file map in low memory situations. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 12:25:26 2008 From: trac at haiku-os.org (tqh) Date: Mon, 07 Jul 2008 10:25:26 -0000 Subject: [Haiku-bugs] [Haiku] #1727: Haiku panics with vm_page fault/double fault after 20-30s usage In-Reply-To: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> References: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> Message-ID: <047.2b89548820e2b59afd1abd0cea6c143e@haiku-os.org> #1727: Haiku panics with vm_page fault/double fault after 20-30s usage ----------------------------+----------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by tqh): I have confirmed that firewire is running, and it hasn't caused any problems here yet. I have only tested for a very short time, so more testing needed. (As I understood the commits this was a workaround for another problem. Is there a bug for that problem already?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 12:45:42 2008 From: trac at haiku-os.org (axeld) Date: Mon, 07 Jul 2008 10:45:42 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.c184e73f27591cec68dfdfa83461bab1@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): For example, the "Component:" field in this ticket shows "Website/Trac". When I click on the pop-up, all existing components will be shown (which are quite a lot). Up until recently, a second component field appeared after having selected a top component category (like "Website"). The components were truly nested, and they aren't any longer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 13:01:06 2008 From: trac at haiku-os.org (mmlr) Date: Mon, 07 Jul 2008 11:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.888c60446c6a090db1bfdb829f3e5c3b@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): This seems to work for me. The attached screenshot shows how this looks for me with Firefox 3.0 on XP (at work). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 13:01:08 2008 From: trac at haiku-os.org (lawsonwa) Date: Mon, 07 Jul 2008 11:01:08 -0000 Subject: [Haiku-bugs] [Haiku] #2479: System reboots before reaching splash screen In-Reply-To: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> References: <043.b9f5d8c8b09be93df1f1b9d1b0cae25d@haiku-os.org> Message-ID: <052.bfa8182f4f716e84e9096d980a09d5a8@haiku-os.org> #2479: System reboots before reaching splash screen ---------------------------------+------------------------------------------ Reporter: lawsonwa | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by lawsonwa): I tried again at rev 26283 and the system now boots as expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 14:14:48 2008 From: trac at haiku-os.org (oruizdorantes) Date: Mon, 07 Jul 2008 12:14:48 -0000 Subject: [Haiku-bugs] [Haiku] #2484: FindPetition doesn't handle cases when event has alternative opcodes In-Reply-To: <040.2f6c124ce0b32ca434c41ecf66c29c00@haiku-os.org> References: <040.2f6c124ce0b32ca434c41ecf66c29c00@haiku-os.org> Message-ID: <049.04f130f36a2d3e547a67ce26e1a1e569@haiku-os.org> #2484: FindPetition doesn't handle cases when event has alternative opcodes --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by oruizdorantes): The idea is that each opcodeExpected index inside the BMessage has to match its eventExpected index. There are 2 different events that contains Opcode (CommandStatus and CommandComplete) they cannot be inside the request with a ramdom index. You can achieve this by Adding first those pairs in the request and last events the ones which do not require opcode. So it is actually the expected/needed behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 19:11:32 2008 From: trac at haiku-os.org (scottmc) Date: Mon, 07 Jul 2008 17:11:32 -0000 Subject: [Haiku-bugs] [Haiku] #2196: testgl fails In-Reply-To: <042.11118a6d0c0b8ec1681ba5ba415ca14b@haiku-os.org> References: <042.11118a6d0c0b8ec1681ba5ba415ca14b@haiku-os.org> Message-ID: <051.100cc72f7367ce8e5cd419f74d6d4528@haiku-os.org> #2196: testgl fails --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): Here's a link to a native Haiku compiled SDL library, version 1.2.13, with both shared and static libs: http://ports.haiku-files.org/downloads/12 I've attached the test files to this ticket to help out testing any fixes to this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 23:54:02 2008 From: trac at haiku-os.org (euan) Date: Mon, 07 Jul 2008 21:54:02 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.1738250bfe947ca192d1dabc9edfe4c5@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by euan): i tested with the r26265 changes. still no change. Is there anything I can do to recommend / override the timer used? Any specific debug that could be enabled? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 7 23:56:48 2008 From: trac at haiku-os.org (dustin howett) Date: Mon, 07 Jul 2008 21:56:48 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.7d905bf2cc2891c04a35df697f9ddbff@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by dustin howett): Turning off SMP in the boot menu should disable the APIC timer. Of course, that's not an optimal solution, if you need/want SMP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 15:21:55 2008 From: trac at haiku-os.org (mt) Date: Tue, 08 Jul 2008 13:21:55 -0000 Subject: [Haiku-bugs] [Haiku] #2485: firefox cannot run on gcc4/gcc2 mixed mode. Message-ID: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> #2485: firefox cannot run on gcc4/gcc2 mixed mode. -----------------------------------+---------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- On r26317 (gcc4 / gcc2 mixed mode, build by gcc4) firefox 2.0.0.15 cannot run. (from Terminal and from Tracker.) {{{ ~> /boot/home/firefox/firefox-bin runtime_loader: Buffer not big enough for section string section runtime_loader: Failed to get gcc version for /boot/home/firefox/firefox- bin runtime_loader: elf_resolve_symbol: could not resolve symbol '__ti9exception' resolve symbol "__ti9exception" returned: -2147478780 runtime_loader: troubles relocating: 0x80001304 (image: libstdc++.r4.so) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 18:23:07 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 16:23:07 -0000 Subject: [Haiku-bugs] [Haiku] #2486: [MediaPlayer] crash in mp3_decoder Message-ID: <040.9df1630b7e59c1e84f462e0ac0441912@haiku-os.org> #2486: [MediaPlayer] crash in mp3_decoder ----------------------------------+----------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Crash occurred on some random search. {{{ Thread 3508 caused an exception: Segment violation 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/libmedia.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libmedia.so Reading symbols from /boot/beos/system/lib/libtracker.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtracker.so Reading symbols from /boot/beos/system/lib/libtranslation.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libtextencoding.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtextencoding.so Reading symbols from /boot/beos/system/lib/libstdc++.r4.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libstdc++.r4.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/libpng.so...done. Loaded symbols for /boot/beos/system/lib/libpng.so Reading symbols from /boot/beos/system/lib/libz.so...done. Loaded symbols for /boot/beos/system/lib/libz.so Reading symbols from /boot/beos/system/add- ons/media/plugins/avi_reader...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/avi_reader Reading symbols from /boot/beos/system/add- ons/media/plugins/avcodec...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/avcodec Reading symbols from /boot/beos/system/add- ons/media/plugins/mp3_decoder...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/mp3_decoder [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/beos/apps/MediaPlayer (3493) thread MediaPlayer Audio Ou control (3508)] 0x00c2273b in III_antialias () from /boot/beos/system/add-ons/media/plugins/mp3_decoder (gdb) bt #0 0x00c2273b in III_antialias () from /boot/beos/system/add-ons/media/plugins/mp3_decoder #1 0x00c237e9 in do_layer3 () from /boot/beos/system/add-ons/media/plugins/mp3_decoder #2 0x97ed40d2 in ?? () #3 0x43865524 in ?? () #4 0x185ccae9 in ?? () #5 0x93631fda in ?? () #6 0x78286aa3 in ?? () #7 0x293ef184 in ?? () #8 0x185d4195 in ?? () #9 0xf8215280 in ?? () #10 0x78288629 in ?? () #11 0xe2856fdb in ?? () #12 0x0000040f in ?? () #13 0x7828878c in ?? () #14 0x00c1d88d in mp3Decoder::DecodeNextChunk () from /boot/beos/system/add-ons/media/plugins/mp3_decoder Previous frame inner to this frame (corrupt stack?) (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 18:25:05 2008 From: trac at haiku-os.org (FSV) Date: Tue, 08 Jul 2008 16:25:05 -0000 Subject: [Haiku-bugs] [Haiku] #2488: Crash: Kernel Debug on... Message-ID: <038.44eb62f4ba371ff204b386dd7e75c46c@haiku-os.org> #2488: Crash: Kernel Debug on... ---------------------------+------------------------------------------------ Reporter: FSV | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: x64 Blocking: | ---------------------------+------------------------------------------------ ... Core 2 Duo 4500 (2.2GHz)/2 GB RAM/i965Pro (Asus P5B)/Radeon 1950 Pro Regular boot from flash-drive (Kingston Data Traveler 2 GB). Image r26311 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 18:24:54 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 16:24:54 -0000 Subject: [Haiku-bugs] [Haiku] #2487: [MediaPlayer] crash in avcodec Message-ID: <040.a31919a724712d1f9fe5d7197d6a548d@haiku-os.org> #2487: [MediaPlayer] crash in avcodec ----------------------------------+----------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Another crash on some random search {{{ Thread 3780 caused an exception: Segment violation 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/libmedia.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libmedia.so Reading symbols from /boot/beos/system/lib/libtracker.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtracker.so Reading symbols from /boot/beos/system/lib/libtranslation.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libtextencoding.so... (no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtextencoding.so Reading symbols from /boot/beos/system/lib/libstdc++.r4.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libstdc++.r4.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/libpng.so...done. Loaded symbols for /boot/beos/system/lib/libpng.so Reading symbols from /boot/beos/system/lib/libz.so...done. Loaded symbols for /boot/beos/system/lib/libz.so Reading symbols from /boot/beos/system/add- ons/media/plugins/avi_reader...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/avi_reader Reading symbols from /boot/beos/system/add- ons/media/plugins/avcodec...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/avcodec Reading symbols from /boot/beos/system/add- ons/media/plugins/mp3_decoder...done. Loaded symbols for /boot/beos/system/add-ons/media/plugins/mp3_decoder [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/beos/apps/MediaPlayer (3764) thread frame generator (3780)] 0x00a621e7 in MPV_decode_mb () from /boot/beos/system/add-ons/media/plugins/avcodec (gdb) bt #0 0x00a621e7 in MPV_decode_mb () from /boot/beos/system/add-ons/media/plugins/avcodec #1 0x00b3eca4 in ?? () from /boot/beos/system/add- ons/media/plugins/avcodec #2 0x185e60d0 in ?? () #3 0x00000000 in ?? () #4 0x0000007f in ?? () #5 0x00000000 in ?? () #6 0x00000130 in ?? () #7 0x00000260 in ?? () #8 0x00001300 in ?? () #9 0x00000260 in ?? () #10 0x186b69d8 in ?? () #11 0x186b69d0 in ?? () #12 0x00a09391 in decode_slice () from /boot/beos/system/add-ons/media/plugins/avcodec #13 0x185e60d0 in ?? () #14 0x186be130 in ?? () #15 0x00000000 in ?? () #16 0x00a094b8 in decode_slice () from /boot/beos/system/add-ons/media/plugins/avcodec #17 0x185e60d0 in ?? () #18 0x186be130 in ?? () #19 0x00000010 in ?? () #20 0x00a091ac in decode_slice () ---Type to continue, or q to quit--- from /boot/beos/system/add-ons/media/plugins/avcodec #21 0x00b3eca4 in ?? () from /boot/beos/system/add- ons/media/plugins/avcodec #22 0x180b38b0 in ?? () #23 0x185e60d0 in ?? () #24 0x180b38b0 in ?? () #25 0x005558c4 in ?? () from /boot/beos/system/lib/libmedia.so #26 0x00000001 in ?? () #27 0x18087e40 in ?? () #28 0x00a0a391 in ff_h263_decode_frame () from /boot/beos/system/add-ons/media/plugins/avcodec #29 0x185e60d0 in ?? () #30 0x180b38b0 in ?? () #31 0x000008e0 in ?? () #32 0x00a09954 in ff_h263_decode_frame () from /boot/beos/system/add-ons/media/plugins/avcodec #33 0x00b3eca4 in ?? () from /boot/beos/system/add- ons/media/plugins/avcodec #34 0x18087e40 in ?? () #35 0x782c9a90 in ?? () #36 0x180b38b0 in ?? () #37 0x180a7a58 in ?? () #38 0x185e60d0 in ?? () #39 0x782c9a98 in ?? () #40 0x18087e40 in ?? () #41 0x005558c4 in ?? () from /boot/beos/system/lib/libmedia.so ---Type to continue, or q to quit--- #42 0x1808a188 in ?? () #43 0x782c9a94 in ?? () #44 0x782c99e8 in ?? () #45 0x00000020 in ?? () #46 0x185e60c0 in ?? () #47 0x782c9a2c in ?? () #48 0x00531903 in MediaExtractorChunkProvider::GetNextChunk () from /boot/beos/system/lib/libmedia.so Previous frame inner to this frame (corrupt stack?) (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 18:31:18 2008 From: trac at haiku-os.org (VinDuv) Date: Tue, 08 Jul 2008 16:31:18 -0000 Subject: [Haiku-bugs] [Haiku] #2489: No boot when HyperThreading is activated Message-ID: <041.b2aecae886747a7c51d2dc551386ed43@haiku-os.org> #2489: No boot when HyperThreading is activated --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- I am currently testing Haiku on a PC with two (physical) Xeon processors.[[BR]] If HyperThreading is activated, when I start Haiku, the system reboots almost instantly. I can not get into the boot menu.[[BR]] Haiku works fine if I disable HT. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 18:50:56 2008 From: trac at haiku-os.org (FSV) Date: Tue, 08 Jul 2008 16:50:56 -0000 Subject: [Haiku-bugs] [Haiku] #2490: File version as on VMS (DEC VAX) Message-ID: <038.05578fbde91413a4e84bcb8f3eaaa7cc@haiku-os.org> #2490: File version as on VMS (DEC VAX) ------------------------------+--------------------------------------------- Reporter: FSV | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Before, Sorry for my English. Dear sirs, in operational system VMS of computers DEC VAX there was one delightful opportunity, - OS kept all versions of files. Those are, when you wrote down the same file in the same place of file system the operation system did not overwrite an old file, and added to a name of a new file number of its version. The name of a file looked so: '''File_name.file_extention:file_version_number''' If the same opportunity could be realized in Haiku, it would be full DELIGHT! For clearing file system from old versions of files the command '''purge''' has been stipulated. Has been stipulated also system purge. In Haiku it would be possible to realize this idea by means of attributes and essentially to develop. For example, in adjustments it is possible to provide following options: 1. Full switching-off of storage of versions of files. 2. To specify depth of preservation of versions of files. We shall tell, to store no more than three versions. At preservation of the new version, most old version automatically to delete. 3. Do not create versions for files, which size more the than set size. 4. Do not create versions for files of the certain type. 5. Do not create versions for the files few differing on time of updating. 6. Purge files it is more or less the than set size, an interval on time of creation, etc., etc. Dear developers, pay please attention to this opportunity. If doubt of its necessity, can it is meaningful open discussion? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 19:49:04 2008 From: trac at haiku-os.org (korli) Date: Tue, 08 Jul 2008 17:49:04 -0000 Subject: [Haiku-bugs] [Haiku] #1635: Gl Teapot Bad Rendering On Window Size Expand In-Reply-To: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> References: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> Message-ID: <049.92f5a696f8dc5c1d199b46a471632063@haiku-os.org> #1635: Gl Teapot Bad Rendering On Window Size Expand ---------------------------------+------------------------------------------ Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by korli): * owner: korli => axeld * component: Kits/OpenGL Kit => Servers/app_server Comment: Stippi confirmed it could be an app_server issue (likely a clipping update). Changing component. Also moving the window also updates the clipping. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 22:15:21 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 08 Jul 2008 20:15:21 -0000 Subject: [Haiku-bugs] [Haiku] #2491: Haiku Live CD reboots right away Message-ID: <042.38879f23f8d7cb36f37dea462941c54a@haiku-os.org> #2491: Haiku Live CD reboots right away ---------------------+------------------------------------------------------ Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ I created a boot cd with the following {{{ jam -q haiku-boot-cd jam -q haiku-image cdrecord dev=/dev/hda -v -eject -dao -data generated/haiku-boot-cd.iso generated/haiku.image }}} but when I boot from the cd the system reboots right away. Here is a the output of lspci from linux {{{ 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) 05:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02) 05:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 05:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 05:09.2 System peripheral: Ricoh Co Ltd Device 0843 (rev 01) 05:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 05:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) }}} Any idea? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 22:22:46 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 08 Jul 2008 20:22:46 -0000 Subject: [Haiku-bugs] [Haiku] #2492: Bouncing text in text entry box Message-ID: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> #2492: Bouncing text in text entry box -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When I select partial text from a text entry box, the text moves down by one pixel and then up by one pixel as long as I leave my left mouse button down. Wasn't sure if this was a bug or if it was supposed to be that way. To check it, hit alt-f then type something in the find box, and then highlight some of the text with your mouse and keep the button down, the text will now be bouncing up and down. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 22:45:43 2008 From: trac at haiku-os.org (stippi) Date: Tue, 08 Jul 2008 20:45:43 -0000 Subject: [Haiku-bugs] [Haiku] #2492: Bouncing text in text entry box In-Reply-To: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> References: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> Message-ID: <051.fe9389d37740ff1359fa7d6b94a806ce@haiku-os.org> #2492: Bouncing text in text entry box ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): I am pretty sure that this is a duplicate, have you searched the database? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 22:56:02 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 20:56:02 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading Message-ID: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> #2493: [Network] slow file downloading --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I just downloaded a file from my local ftp server using firefox and I noticed that download speed is several times slower then when downloading same file from same machine under ubuntu. From Haiku it was 2mb/s, from Ubuntu it was 10mb/s. Tested on real hw, using Intel Pro 100 nic. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:00:24 2008 From: trac at haiku-os.org (umccullough) Date: Tue, 08 Jul 2008 21:00:24 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading In-Reply-To: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> References: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> Message-ID: <049.85ab4fc352d47b0ac82163a15ea1e649@haiku-os.org> #2493: [Network] slow file downloading ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by umccullough): Doesn't the ipro100 driver have some serious performance issues in the interrupt handler already? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:02:13 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:02:13 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.d4674072e80e3f6283be31c861cfe6e0@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): Can't reproduce it anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:09:35 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:09:35 -0000 Subject: [Haiku-bugs] [Haiku] #2494: [bfs] corruption after downloading two 700mb files from ftp Message-ID: <040.48ec56f52b6a91da2d577b5bbe645f42@haiku-os.org> #2494: [bfs] corruption after downloading two 700mb files from ftp ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I just finished compiling latest revision, so partition was fresh. The I rebooted to haiku and downloaded two 700mb files from my local ftp server and I noticed some strange things. [[BR]] In search window of tracker bookmark icon changed with StyledEdit icon, I closed this window and reopening it again and this time it was yes another icon. I then thought something happens with icon cache in tracker and restarted it via ProcessController, when desktop appears again all icons changed to generic be_app icon.[[BR]] After reboot to linux I mounted haiku partition to copy some backtrace I've made during last session, but when I opened this file after backtrace text I saw some random data. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:10:44 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 08 Jul 2008 21:10:44 -0000 Subject: [Haiku-bugs] [Haiku] #2492: Bouncing text in text entry box In-Reply-To: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> References: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> Message-ID: <051.ff367e6777d2c2a593fe590fdf7fd864@haiku-os.org> #2492: Bouncing text in text entry box ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Looks like this is a dupe of #2134 and the second example listed on that ticket is something else I had noticed recently as well, hadn't occurred to me that those two issues might be the same things. In that second example the text moves up a lot more than 1 pixel though. You can close this as a dupe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:13:28 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:13:28 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading In-Reply-To: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> References: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> Message-ID: <049.04519ac59e977d77442b087c6958151f@haiku-os.org> #2493: [Network] slow file downloading ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): If it helps I could retest using sysconnect diver for builtin Marvell Yukon nic. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:27:29 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:27:29 -0000 Subject: [Haiku-bugs] [Haiku] #2495: [MediaPlayer] Pressing left/right arrows do unexpected things Message-ID: <040.441442108019c83e01b7d8693ffffb88@haiku-os.org> #2495: [MediaPlayer] Pressing left/right arrows do unexpected things --------------------------------------+------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Pressing left/right arrows when watching a movie in MediaPlayer do unexpected things like starts current movie again. [[BR]] Some years ago I suggested hotkeys for BeOS port of VLC, which never been implemented. Those suggestions are still available in videolan wiki at http://wiki.videolan.org/BeOS, they could need some cleaning, but most of them should make MediaPlayer a pleasure to use already. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:34:03 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:34:03 -0000 Subject: [Haiku-bugs] [Haiku] #2496: [nvidia] screen is half shifted at 1440x900 resolution Message-ID: <040.291e6523d7181d32969747f3a4c8df4a@haiku-os.org> #2496: [nvidia] screen is half shifted at 1440x900 resolution -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- When i boot Haiku, first thing I do is launching Screen to change resolution to my monitor native one - 1440x900.[[BR]] The only problem with it is that I have to press Auto button of my monitor when to center half shifted screen. When I reboot to ubuntu I have to press it again. And this is kind of annoying to do every time.[[BR]] It's an nVidia NV18 [GeForce4 MX 440 AGP 8x] (rev a4) 10de:0181 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:36:03 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 08 Jul 2008 21:36:03 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.beac2ea58e50249047967e369d062b23@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): reproducible here, audio CDs can't be read with CDDA -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:37:05 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:37:05 -0000 Subject: [Haiku-bugs] [Haiku] #2497: [AboutSystem] right textview is not selectable Message-ID: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> #2497: [AboutSystem] right textview is not selectable --------------------------+------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- AboutSystem right textview is not selectable. It should either be selectable or ibeam cursor should be removed to not confuse end user. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:39:31 2008 From: trac at haiku-os.org (stippi) Date: Tue, 08 Jul 2008 21:39:31 -0000 Subject: [Haiku-bugs] [Haiku] #2492: Bouncing text in text entry box In-Reply-To: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> References: <042.185653a2d03108a1fd5157d5cf0d2674@haiku-os.org> Message-ID: <051.13c4427aabacad35039244174a8f3ca0@haiku-os.org> #2492: Bouncing text in text entry box ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: Thanks for looking it up, I was a bit in a hurry I must admit! :-P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:40:14 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:40:14 -0000 Subject: [Haiku-bugs] [Haiku] #2498: [MediaPlayer] don't use overlay for video Message-ID: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> #2498: [MediaPlayer] don't use overlay for video --------------------------------------+------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- MediaPlayer use DrawBitmap mode instead of overlay. Same video in VLC use overlays. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:52:25 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:52:25 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap Message-ID: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap -----------------------------------+---------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Hotkeys doesn't work with Russian keymap. [[BR]] I can't close windows (alt+w) or anything else I used to use when current keymap is Russian, and I suspect several others as well.[[BR]] I know that it's the same behavior as in BeOS, but I really think it was a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 8 23:57:57 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 21:57:57 -0000 Subject: [Haiku-bugs] [Haiku] #2500: [app_server] moving cursor above toolbar of firefox make sound distorted Message-ID: <040.22697654cd2d151b8e8fa468c353009a@haiku-os.org> #2500: [app_server] moving cursor above toolbar of firefox make sound distorted --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Moving cursor above toolbar of firefox make sound distorted in the same time cpu load is only 30%. [[BR]] 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a4) [[BR]] I have a suspicion that app_server generates too many mouse events. so I assign it to this component. Please correct if it's not the case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:22:24 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 08 Jul 2008 22:22:24 -0000 Subject: [Haiku-bugs] [Haiku] #2337: After the recent vesa changes haiku hangs at boot In-Reply-To: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> References: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> Message-ID: <048.0d260047ef97bcf7ed603317be0ca359@haiku-os.org> #2337: After the recent vesa changes haiku hangs at boot -------------------------------+-------------------------------------------- Reporter: ddew | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by bonefish): Similar behavior here (Lenovo T61 with nVidia gfx): Switching the screen mode took roughly 2 mins. r26325 fixes this problem. Works as expected, now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:31:45 2008 From: trac at haiku-os.org (euan) Date: Tue, 08 Jul 2008 22:31:45 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.b8ebbe1ee1151b8481324ecf16f380ef@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by euan): no change with SMP off. :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:33:17 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 08 Jul 2008 22:33:17 -0000 Subject: [Haiku-bugs] [Haiku] #1489: Add Icon in File Type gives General system error in Icon-O-Matic In-Reply-To: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> References: <042.7c37d799a2396dfbbbb4c35f75639ba7@haiku-os.org> Message-ID: <051.8484148ec2ddb403f5a65b541a26d559@haiku-os.org> #1489: Add Icon in File Type gives General system error in Icon-O-Matic ----------------------------------------+----------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Comment(by scottmc): Perhaps "Add Icon..." should open up a file select box on a folder that has icons in it? And maybe add another option (or two) for "New Icon" which would open Icon-O-Matic in a mode that would be ready to create a new icon, and give no error. Perhaps the other option would be "Edit Icon" which would be greyed out if no icon is yet present. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:38:48 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 08 Jul 2008 22:38:48 -0000 Subject: [Haiku-bugs] [Haiku] #2501: Regression: USB Keyboard not Working on Lenovo T61 Message-ID: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> #2501: Regression: USB Keyboard not Working on Lenovo T61 -------------------------+-------------------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- r26330 My USB keyboard doesn't work on my T61 anymore. When booting with the keyboard plugged into the laptop itself, the keyboard doesn't work. The USB mouse plugged into the docking station works as expected. When the keyboard is also plugged into the docking station neither keyboard nor mouse do work. Serial debug output for both situations attached. I experienced a similar behavior quite a while ago, but at the point of closing #1764 everything worked like a charm. Apparently later changes broke things again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:40:05 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 08 Jul 2008 22:40:05 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.102521dac9f5ab227bedc31750d09375@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by marcusoverhagen): Should be fixed in r26332, please test. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:43:36 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 08 Jul 2008 22:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #2501: Regression: USB Keyboard not Working on Lenovo T61 In-Reply-To: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> References: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> Message-ID: <052.cbb405eec0bb36a380521f2625050e9b@haiku-os.org> #2501: Regression: USB Keyboard not Working on Lenovo T61 --------------------------+------------------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bonefish): BTW, I'll be bringing the hardware on Monday. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 00:49:01 2008 From: trac at haiku-os.org (diver) Date: Tue, 08 Jul 2008 22:49:01 -0000 Subject: [Haiku-bugs] [Haiku] #529: [NetPositive] bookmark icon doesn't drawn In-Reply-To: <040.728a5ad6e126fbf166d2d1b5b027156f@haiku-os.org> References: <040.728a5ad6e126fbf166d2d1b5b027156f@haiku-os.org> Message-ID: <049.830886293a4e755681e6e4c9ad820591@haiku-os.org> #529: [NetPositive] bookmark icon doesn't drawn ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by diver): * component: - General => Servers/app_server Comment: This seems to be fixed recently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 02:46:13 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 09 Jul 2008 00:46:13 -0000 Subject: [Haiku-bugs] [Haiku] #2501: Regression: USB Keyboard not Working on Lenovo T61 In-Reply-To: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> References: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> Message-ID: <052.7a40d398da3cc2c16477d08ce70f9bdf@haiku-os.org> #2501: Regression: USB Keyboard not Working on Lenovo T61 --------------------------+------------------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by marcusoverhagen): * cc: marcusoverhagen (added) Comment: You can try to enable TRACE_PS2 in ps2_common.h to see if the usb mouse data is delivered by legacy emulation through the ps2 port. You can also try to revert r22617 to see if the ps2 selftest command makes a difference. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 02:51:13 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 09 Jul 2008 00:51:13 -0000 Subject: [Haiku-bugs] [Haiku] #2360: PS/2 keyboard and touchpad not working on cold boots In-Reply-To: <039.3e1478899be58b63dbf44ba1dcd5fe3c@haiku-os.org> References: <039.3e1478899be58b63dbf44ba1dcd5fe3c@haiku-os.org> Message-ID: <048.a13b25c91b6dd42e8a54551c52cea508@haiku-os.org> #2360: PS/2 keyboard and touchpad not working on cold boots -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by marcusoverhagen): for reference http://www.usb.org/developers/devclass_docs/usb_le9.pdf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 02:36:57 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 09 Jul 2008 00:36:57 -0000 Subject: [Haiku-bugs] [Haiku] #2366: Mouse stops working In-Reply-To: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> References: <045.c9bb9ea4ce2baae23931e56f0120843d@haiku-os.org> Message-ID: <054.6aa9717ffd1ef048a56dafb7030c0214@haiku-os.org> #2366: Mouse stops working --------------------------------+------------------------------------------- Reporter: mrsunshine | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by marcusoverhagen): You said on IRC that it once worked. what revision did break it? (try binary search) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 04:22:29 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 09 Jul 2008 02:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.29cdcc52e7dfc4083ebb0ea886144485@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * priority: normal => high * component: - General => System/Kernel * milestone: R1 => R1/alpha1 Comment: I think I understand the core of the problem, now. One issue is, as already mentioned, that jam uses a lot of heap (checking closer to the end of the build process it was about 270 MB) and when fork()ing twice that amount is reserved due to missing swap support.(*) The second problem is, that the block cache unnecessarily binds reserved memory in unused blocks. It doesn't free blocks until the low memory state is at least B_LOW_MEMORY_NOTE, which happens when only 2048 free pages are left. There are several issues. First of all the reserved memory and free pages aren't directly related. The available memory is just the lower boundary for pages that are either free or only used in caches (i.e. can be freed at any time). If for instance only 10 MB available memory are left although there are more than 2048 free pages, we won't be in any low memory state. fork()ing jam at that point will fail, since additional 270 MB would need to be reserved. At the same time hundreds of MB could be bound in unused blocks. Possible changes to improve the situation: - Low memory states might also need to be triggered by low amount of available memory. - The block cache needs to indicate somehow how much memory it could free, if necessary. - vm_try_reserve_memory() might need to trigger freeing of memory and wait. There might also be other problems. When checking the caches situation in roughly the middle of a "jam @image" the kernel heap consisted of a 16 MB area and 11 additional 4 MB areas. This sounds like quite a bit more than it should be. Not sure to what degree this is indirectly caused by the massive caching that happens (i.e. allocations for cache structures, vnode structures, page mappings). Will examine this some more. (*) ATM there's a bug (already fixed in my branch) that after the first fork() + exec() there's no memory reserved for jam's heap itself. Whenever the heap is resized (which should happen quite a few times during the build process) that is remedied though, and the subsequent fork() will indeed cause twice the heap size to be reserved. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 04:40:20 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 09 Jul 2008 02:40:20 -0000 Subject: [Haiku-bugs] [Haiku] #2502: svn checkout via ssh prompts for password several times Message-ID: <044.788ea692f447950a1313a5dfef8329ea@haiku-os.org> #2502: svn checkout via ssh prompts for password several times ---------------------------------------------+------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ If I try to do an svn co via svn+ssh using Michael Lotz's svn package + OpenSSH, it first asks me to accept the key like normal, but then asks for my password three times. This doesn't appear to be a negotiation failure since intentionally mistyping my password does result in it indicating a password error and re-prompting, while typing it correctly results in an additional prompt, but no warning/error. After typing it in three times, the checkout starts like it should. Anything that can be done to verify where the problem is here? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 05:09:48 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 09 Jul 2008 03:09:48 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.79b3108dce1209a5dfebfc3a00b371c0@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): This might not necessarily be useful any more, but for reference, caches tells me the following after an svn checkout: total committed memory: 967630848, total used pages: 253214 83254 caches (82965 root caches), sorted by page count per cache tree 0x90d759d8: pages: 51203 - tracing log 0x90d6bb40: pages: 4096 - kernel heap 0x90d6ba50: pages: 2816 - page structures 0x90d75d98: pages: 1664 - sem_table 0x90e5b0f0: pages: 1536 - radeon local memory - a cache tree for libbe with 73 pages committed. 20 or so additional RAM caches for additional heap, all 1024 pages, completely committed 1024 pages for Radeon GATT another 912 pages for heap 854 pages for contig:/usr/home/rene/devel/haiku (where I had my checkout going), though the /usr prefix confuses me. 4 vnode caches, 617, 617, 602 and 602 pages 512 pages for memalign area 333 heap pages for team 120 327 heap pages for team 117 112 pages for a libroot cache tree many many pages of block cache buffers, each 256 pages. A few others, less significant. All in all, I can confirm the block cache is definitely eating me alive also. Anything else that'd be of interest? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 05:11:58 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 09 Jul 2008 03:11:58 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.6714c9f389e3e59528e52923fdf922f9@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Also, typing 'q' while still scrolling through that list (it was down to areas of 3 pages or so, and I decided those probably weren't important here), KDL froze entirely. Should I file a ticket for that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 06:16:41 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 09 Jul 2008 04:16:41 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.508c85107107215f0735c98e62d84832@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by emitrax): Replying to [comment:13 anevilyak]: > Also, typing 'q' while still scrolling through that list (it was down to areas of 3 pages or so, and I decided those probably weren't important here), KDL froze entirely. Should I file a ticket for that? That's actually temporarily. It has happened to me too, but eventually KDL gets back to life after a minute or so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 06:25:27 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 09 Jul 2008 04:25:27 -0000 Subject: [Haiku-bugs] [Haiku] #2503: ftp crashed Message-ID: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> #2503: ftp crashed -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- while downloading a file of 700 mb from my local ftp server, ftp crashed. I think due to connection that got missing. Couldn't get any screenshots. BTW: when connecting to the ftp server some messages about termcap get displayed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 06:32:40 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 09 Jul 2008 04:32:40 -0000 Subject: [Haiku-bugs] [Haiku] #2503: ftp crashed In-Reply-To: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> References: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> Message-ID: <051.62ebcf1a0685ea6673f985330812ceb8@haiku-os.org> #2503: ftp crashed ------------------------------------+--------------------------------------- Reporter: emitrax | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by emitrax): Actually it is to reproduce. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 08:20:34 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 09 Jul 2008 06:20:34 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading In-Reply-To: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> References: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> Message-ID: <049.15405056c10e2b88d34e246728c21d08@haiku-os.org> #2493: [Network] slow file downloading ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by scottmc): Dupe of #1958 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 08:26:27 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 09 Jul 2008 06:26:27 -0000 Subject: [Haiku-bugs] [Haiku] #2503: ftp crashed In-Reply-To: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> References: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> Message-ID: <051.11d403e485c6c1bcb52e47a07283acd8@haiku-os.org> #2503: ftp crashed ------------------------------------+--------------------------------------- Reporter: emitrax | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): That second bug listed here was reported in #1958, but the ftp crash may be new. Can you post the output from listdev on that pc? Maybe network driver related? I get various crashes with the realtek 8139 driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 08:48:33 2008 From: trac at haiku-os.org (korli) Date: Wed, 09 Jul 2008 06:48:33 -0000 Subject: [Haiku-bugs] [Haiku] #2483: [kernel] problems opening png image from ext3 partition In-Reply-To: <040.6709c6f248972105379daa19a294e843@haiku-os.org> References: <040.6709c6f248972105379daa19a294e843@haiku-os.org> Message-ID: <049.f4225e68adf1ff89e2fbfb8ae0ccb7f4@haiku-os.org> #2483: [kernel] problems opening png image from ext3 partition ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Thanks for the update! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 09:01:42 2008 From: trac at haiku-os.org (korli) Date: Wed, 09 Jul 2008 07:01:42 -0000 Subject: [Haiku-bugs] [Haiku] #2490: File version as on VMS (DEC VAX) In-Reply-To: <038.05578fbde91413a4e84bcb8f3eaaa7cc@haiku-os.org> References: <038.05578fbde91413a4e84bcb8f3eaaa7cc@haiku-os.org> Message-ID: <047.1265ab03c384eb1ff7b15926e3eb3341@haiku-os.org> #2490: File version as on VMS (DEC VAX) -------------------------------+-------------------------------------------- Reporter: FSV | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Component: File Systems/BFS | Version: Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by korli): * version: R1 development => * milestone: R1 => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 09:31:32 2008 From: trac at haiku-os.org (korli) Date: Wed, 09 Jul 2008 07:31:32 -0000 Subject: [Haiku-bugs] [Haiku] #2498: [MediaPlayer] doesn't use overlay for video (was: [MediaPlayer] don't use overlay for video) In-Reply-To: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> References: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> Message-ID: <049.09bf232ea3c156ad7f78dc60d3ba8154@haiku-os.org> #2498: [MediaPlayer] doesn't use overlay for video ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Description changed by korli: Old description: > MediaPlayer use DrawBitmap mode instead of overlay. > > Same video in VLC use overlays. New description: MediaPlayer uses DrawBitmap mode instead of overlay. Same video in VLC use overlays. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 09:35:33 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 09 Jul 2008 07:35:33 -0000 Subject: [Haiku-bugs] [Haiku] #2498: [MediaPlayer] doesn't use overlay for video In-Reply-To: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> References: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> Message-ID: <049.79f2b832a29928531a2a6535486b773e@haiku-os.org> #2498: [MediaPlayer] doesn't use overlay for video ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by mmlr): Duplicate of bug #2405? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 09:38:40 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 09 Jul 2008 07:38:40 -0000 Subject: [Haiku-bugs] [Haiku] #2337: After the recent vesa changes haiku hangs at boot In-Reply-To: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> References: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> Message-ID: <048.34dde4ca23a52d369ef0a59de5dd48a0@haiku-os.org> #2337: After the recent vesa changes haiku hangs at boot -------------------------------+-------------------------------------------- Reporter: ddew | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by PieterPanman): For some reason my old account didn't work anymore and password recovery didn't help. I created a new account. The problem for me is solved with regarding the vesa mode changes. Thank you! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 11:19:29 2008 From: trac at haiku-os.org (stippi) Date: Wed, 09 Jul 2008 09:19:29 -0000 Subject: [Haiku-bugs] [Haiku] #529: [NetPositive] bookmark icon doesn't drawn In-Reply-To: <040.728a5ad6e126fbf166d2d1b5b027156f@haiku-os.org> References: <040.728a5ad6e126fbf166d2d1b5b027156f@haiku-os.org> Message-ID: <049.42bed0bbe95a82cf1bee51b629d506d6@haiku-os.org> #529: [NetPositive] bookmark icon doesn't drawn ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Yes, it was fixed by Michael Lotz, when he found out that even B_RGB32 can have B_TRANSPARENT_MAGIC pixels. (He corrected other colorspaces as well.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 12:07:42 2008 From: trac at haiku-os.org (stippi) Date: Wed, 09 Jul 2008 10:07:42 -0000 Subject: [Haiku-bugs] [Haiku] #609: BView::GetMouse lags in 3dmix In-Reply-To: <051.f41095dc4551a1c7c3a073dd3abfcba0@haiku-os.org> References: <051.f41095dc4551a1c7c3a073dd3abfcba0@haiku-os.org> Message-ID: <060.db1b44037e8e4d60cace68eb4b10dd7b@haiku-os.org> #609: BView::GetMouse lags in 3dmix -------------------------------+-------------------------------------------- Reporter: genki0 at gmail.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r26337. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 12:34:15 2008 From: trac at haiku-os.org (korli) Date: Wed, 09 Jul 2008 10:34:15 -0000 Subject: [Haiku-bugs] [Haiku] #2337: After the recent vesa changes haiku hangs at boot In-Reply-To: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> References: <039.71dd3b0394d1905149cf0322daff9a9c@haiku-os.org> Message-ID: <048.cadde97793aebf23be323d032ab02430@haiku-os.org> #2337: After the recent vesa changes haiku hangs at boot -------------------------------+-------------------------------------------- Reporter: ddew | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: thanks for the update! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 12:39:36 2008 From: trac at haiku-os.org (mmu_man) Date: Wed, 09 Jul 2008 10:39:36 -0000 Subject: [Haiku-bugs] [Haiku] #2342: No system timer interrupt on some ATI chipsets In-Reply-To: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> References: <039.3674ba47b1d07ce0d804a70edffeeb2b@haiku-os.org> Message-ID: <048.e2d2cfbd718a54ccc37eb328ac1fe16c@haiku-os.org> #2342: No system timer interrupt on some ATI chipsets ----------------------------+----------------------------------------------- Reporter: euan | Owner: mmu_man Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmu_man): As I said I have a fix pending, but I need to clean it up, please be patient. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 13:11:18 2008 From: trac at haiku-os.org (monni) Date: Wed, 09 Jul 2008 11:11:18 -0000 Subject: [Haiku-bugs] [Haiku] #2290: bluetooth crashes when removing device In-Reply-To: <040.007f6bc38c42a1ccbbd6956a21e2033d@haiku-os.org> References: <040.007f6bc38c42a1ccbbd6956a21e2033d@haiku-os.org> Message-ID: <049.142af938ec7ede8f2b761ab31d2bed83@haiku-os.org> #2290: bluetooth crashes when removing device --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): http://dev.haiku-os.org/browser/haiku/trunk/src/add- ons/kernel/drivers/bluetooth/h2/h2generic/h2util.c#L65 Needs to check if nbuf is NULL... After that NO... I mean NO.... KDL ;) Related to same file, it has several lines with "nbuf->COOKIEFIELD == NULL" that really should be "nbuf->COOKIEFIELD == 0" as COOKIEFIELD isn't of pointer type. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 13:57:04 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 09 Jul 2008 11:57:04 -0000 Subject: [Haiku-bugs] [Haiku] #2502: svn checkout via ssh prompts for password several times In-Reply-To: <044.788ea692f447950a1313a5dfef8329ea@haiku-os.org> References: <044.788ea692f447950a1313a5dfef8329ea@haiku-os.org> Message-ID: <053.0fa443315bf074c4bc13c66848fa22fb@haiku-os.org> #2502: svn checkout via ssh prompts for password several times ----------------------------------------------+----------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: The same happens in Linux (tested with Subversion 1.4.4). svn seems to open three connections (or one connection three times). I seem to recall having read quite a while ago that they wanted to fix that. Obviously they haven't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 14:05:14 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 09 Jul 2008 12:05:14 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.261e9b43c234ac2f64e84648ad82bf6c@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:13 anevilyak]: > Also, typing 'q' while still scrolling through that list (it was down to areas of 3 pages or so, and I decided those probably weren't important here), KDL froze entirely. Should I file a ticket for that? Nope, it's not a bug. "q" quits the blue screen output, the command continues and prints the remaining output to the serial port only (which can take some time). You can use "a" to actually abort the command. Since the current "q" behavior is not what one wants in most cases, we might want to make it a hidden feature and make the other the default. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 14:56:34 2008 From: trac at haiku-os.org (stippi) Date: Wed, 09 Jul 2008 12:56:34 -0000 Subject: [Haiku-bugs] [Haiku] #2498: [MediaPlayer] doesn't use overlay for video In-Reply-To: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> References: <040.f459f2a46448d748965bab8bec212887@haiku-os.org> Message-ID: <049.b86f38c499403d5707ea86ae6f6b9c99@haiku-os.org> #2498: [MediaPlayer] doesn't use overlay for video ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: Yes, duplicate of #2405. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 17:00:53 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 09 Jul 2008 15:00:53 -0000 Subject: [Haiku-bugs] [Haiku] #2503: ftp crashed In-Reply-To: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> References: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> Message-ID: <051.dd1c5cdaa3edbe2a3d3256c377932eb1@haiku-os.org> #2503: ftp crashed ------------------------------------+--------------------------------------- Reporter: emitrax | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by emitrax): I don't have problem transferring small files. Only big ones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 18:02:04 2008 From: trac at haiku-os.org (kaliber) Date: Wed, 09 Jul 2008 16:02:04 -0000 Subject: [Haiku-bugs] [Haiku] #2041: In some cases, __mbrtowc can enter in an infinite loop In-Reply-To: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> References: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> Message-ID: <047.1d147ac940595183267c84c8079555d9@haiku-os.org> #2041: In some cases, __mbrtowc can enter in an infinite loop --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by kaliber): Due to bug(s) in mbrtowc() 16 tests from sed-4.1.5 are failing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 18:42:56 2008 From: trac at haiku-os.org (El-Al) Date: Wed, 09 Jul 2008 16:42:56 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (disks icon) Message-ID: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> #2504: Haiku freezes at bootup (disks icon) -----------------------+---------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- My system freezes at bootup when the disc icon is highlighted. With on screen debug on the system prints the following output: usb_uhci: no devices found usb_ohci: successfully started the controller usb_ehci: claiming ownership of the host controller usb_ehci: successfully took ownership of the host controller usb_ehci: successfully started the controller At this point the cursor freezes and nothing happens. A hard reboot is required. This was a working haiku system until the driver architecture got overhauled. Iv'e tried all the safe mode options to no avail. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 18:58:18 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 09 Jul 2008 16:58:18 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (disks icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.3df7df41df2d3b8d38efc8bfbd895741@haiku-os.org> #2504: Haiku freezes at bootup (disks icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Can you please try removing the usb_disk driver from "/boot/beos/system /add-ons/kernel/drivers/bin" and see if this changes behaviour. If it does it is an OHCI issue (bug #1044) otherwise it's something else :-). When this happens, are you still able to enter KDL by pressing F12? If so, please run the "ints" command and check for exceptionally large numbers and post back here if you find any. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 18:58:45 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 09 Jul 2008 16:58:45 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (disks icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.3c3ee93ac2c53d07bef5782c0787a185@haiku-os.org> #2504: Haiku freezes at bootup (disks icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Description changed by mmlr: Old description: > My system freezes at bootup when the disc icon is highlighted. > With on screen debug on the system prints the following output: > > usb_uhci: no devices found > usb_ohci: successfully started the controller > usb_ehci: claiming ownership of the host controller > usb_ehci: successfully took ownership of the host controller > usb_ehci: successfully started the controller > > At this point the cursor freezes and nothing happens. > A hard reboot is required. This was a working haiku system until the > driver architecture got overhauled. Iv'e tried all the safe mode options > to no avail. New description: My system freezes at bootup when the disc icon is highlighted. With on screen debug on the system prints the following output: {{{ usb_uhci: no devices found usb_ohci: successfully started the controller usb_ehci: claiming ownership of the host controller usb_ehci: successfully took ownership of the host controller usb_ehci: successfully started the controller }}} At this point the cursor freezes and nothing happens. A hard reboot is required. This was a working haiku system until the driver architecture got overhauled. Iv'e tried all the safe mode options to no avail. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 19:15:49 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 09 Jul 2008 17:15:49 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (disks icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.01293dffc078447324ea2726784f7c45@haiku-os.org> #2504: Haiku freezes at bootup (disks icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by PieterPanman): Which revision? I had something similar, but it turned out to be #2337. If you wait for 10 minutes, does it finally boot? Any release prior to r26325 might cause this -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 21:01:50 2008 From: trac at haiku-os.org (El-Al) Date: Wed, 09 Jul 2008 19:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) (was: Haiku freezes at bootup (disks icon)) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.ad480ac3f8cd37ef32c4cf5779da362a@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by El-Al): I removed usb_disk from the build, rebooted with a ps2 mouse/keyboard and got a completely different set of errors: get_boot_partition(): boot volume message: field: "booted from image", type: BOOL (0x424f4f4c) [0] false I can't seem to enter KDL at all by pressing F12. Also tried waiting for 15/20 minutes for it to boot. Still nothing. (This is an ASROCK mobo with ali/uli chipset and 2x AMD 64 3800+ cpus btw) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 22:28:06 2008 From: trac at haiku-os.org (monni) Date: Wed, 09 Jul 2008 20:28:06 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic Message-ID: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic -------------------------------+-------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- E-mailed this to Oliver earlier today and adding here to track progress ;) How to reproduce: disconnect bluetooth dongle while bluetooth_server is running Experienced behavior: unhandled page fault in kernel space at 0xdeadbef3 Expected behavior: wait for new dongle to appear Back trace: {{{ :device_close + 0x009d :devfs_close__FP9fs_volumeP8fs_vnodePv + 0x0035 :file_close__FP15file_descriptor + 0x004c :put_fd + 0x006c :disconnect_mount_or_vnode_fds__FP8fs_mountP5vnode + 0x01e5 :vfs_disconnect_vnode + 0x003d :devfs_unpublish_device + 0x0067 :republish_driver__FP13legacy_driver + 0x0535 :legacy_driver_rescan + 0x0075 :devfs_rescan_driver + 0x0012 :RescanDrivers__5StackP11rescan_item + 0x001b :ExploreThread__5StackPv + 0x0101 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 23:16:10 2008 From: trac at haiku-os.org (axeld) Date: Wed, 09 Jul 2008 21:16:10 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.047eeffeb62dcfa2901cb71bec4147b4@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): Replying to [comment:15 bonefish]: > Since the current "q" behavior is not what one wants in most cases, we might want to make it a hidden feature and make the other the default. That sounds like a good idea. How about 'q' for abort, and 'h' for hide, then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 23:20:48 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 09 Jul 2008 21:20:48 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.e48a6ecaaf222fdb3cf5d9779ac62ea5@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): No need for the PS/2 hardware. Removing usb_disk just causes the USB stack to be loaded later, it doesn't disable it. So you don't get the USB related messages anymore, but otherwise it hangs at more or less the same place? The output you posted isn't an error message BTW, it's just dumping the content of the boot volume message coming from the bootloader. Though if that's the only line that gets printed from the boot volume message that's strange. It should contain "booted from image", "partition offset", "boot method", "boot drive number" and "disk identifier". I could imagine it being an interrupt flood from ATA. You could try replacing the ide with the ata bus_manager to see if that makes a difference. To do that change the line saying "SubInclude HAIKU_TOP src add-ons kernel bus_managers ide ;" to "SubInclude HAIKU_TOP src add-ons kernel bus_managers ata ;" in the "src/add-ons/kernel/bus_managers/Jamfile" and maybe use "jam -a ide" once to make sure it is rebuilt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 9 23:47:57 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 09 Jul 2008 21:47:57 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.18ff2ef3fd85dac810cae788519f6fc9@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): I'm curious, under what circumstance is the 'h' actually desirable behavior? I.e. what KDL commands would you want to execute that actually have some effect beyond displaying pages of output? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 01:10:02 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 09 Jul 2008 23:10:02 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.4972e1ea0be301d18c2cf98ef4e83467@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): Replying to [comment:17 anevilyak]: > I'm curious, under what circumstance is the 'h' actually desirable behavior? I.e. what KDL commands would you want to execute that actually have some effect beyond displaying pages of output? If you have a serial line connection you may want to capture extensive output for further analysis without slowing it further down by also having it printed to the screen (besides that one would first need to disable pagination). I don't do that very often, but from time to time the feature is nice to have. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 11:21:04 2008 From: trac at haiku-os.org (jackburton) Date: Thu, 10 Jul 2008 09:21:04 -0000 Subject: [Haiku-bugs] [Haiku] #1744: Amilo A7640W: Network doesn't work (sis900) In-Reply-To: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> References: <045.ab8f9f0871424a91a93be05f068a6013@haiku-os.org> Message-ID: <054.0621d4258e616b2941fa1967acd72308@haiku-os.org> #1744: Amilo A7640W: Network doesn't work (sis900) ------------------------------+--------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Comment(by jackburton): Replying to [comment:17 axeld]: > This is possible if there is a driver that doesn't play well in this case. > But you can easily prove that theory by removing the drivers of those other devices - if the driver then works nicely, we can look further :-) I removed the usb drivers and the auich driver, but nothing changed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 12:24:08 2008 From: trac at haiku-os.org (diver) Date: Thu, 10 Jul 2008 10:24:08 -0000 Subject: [Haiku-bugs] [Haiku] #2506: [app_server] crash in WindowList::RemoveWindow () Message-ID: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> #2506: [app_server] crash in WindowList::RemoveWindow () --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Start MediaPlayer[[BR]] Press Alt+p to open Playlist[[BR]] Grab MediaPlayer window by tab and bring it to the second workspace (Alt+F2)[[BR]] Leave MediaPlayer at second workspace and go back to the first one (Alt+F1)[[BR]] Grab Playlist window by tab and bring it to the second workspace (Alt+F2)[[BR]] At this point you should see consoled session with gdb. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 12:33:09 2008 From: trac at haiku-os.org (diver) Date: Thu, 10 Jul 2008 10:33:09 -0000 Subject: [Haiku-bugs] [Haiku] #2507: [NetPositive] crash after closing it's preferences window Message-ID: <040.50a5debfb7bb3a648e1fffecaaf78605@haiku-os.org> #2507: [NetPositive] crash after closing it's preferences window --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- NetPositive crash after closing it's preferences window. Dunno if it reproducible. {{{ [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 857 caused an exception: Segment violation 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/libnetwork.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libnetwork.so Reading symbols from /boot/beos/system/lib/libtracker.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtracker.so Reading symbols from /boot/beos/system/lib/libtextencoding.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtextencoding.so Reading symbols from /boot/beos/system/lib/libmidi.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libmidi.so Reading symbols from /boot/beos/system/lib/libmail.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libmail.so Reading symbols from /boot/beos/system/lib/libtranslation.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libgame.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libgame.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/libpng.so...done. Loaded symbols for /boot/beos/system/lib/libpng.so Reading symbols from /boot/beos/system/lib/libz.so...done. Loaded symbols for /boot/beos/system/lib/libz.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/beos/system/lib/libmidi2.so...done. Loaded symbols for /boot/beos/system/lib/libmidi2.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/libfluidsynth.so...done. Loaded symbols for /boot/beos/system/lib/libfluidsynth.so [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /BeOS/beos/apps/NetPositive (784) thread w>Preferences (857)] 0x004ab213 in BView::~BView () from /boot/beos/system/lib/libbe.so (gdb) bt #0 0x004ab213 in BView::~BView () from /boot/beos/system/lib/libbe.so #1 0x004625dc in BMenuField::~BMenuField () from /boot/beos/system/lib/libbe.so #2 0x004ab21f in BView::~BView () from /boot/beos/system/lib/libbe.so #3 0x00496c0c in BTab::~BTab () from /boot/beos/system/lib/libbe.so #4 0x004977c3 in BTabView::~BTabView () from /boot/beos/system/lib/libbe.so #5 0x004ab21f in BView::~BView () from /boot/beos/system/lib/libbe.so #6 0x00332561 in PrefsView::~PrefsView () #7 0x004ab21f in BView::~BView () from /boot/beos/system/lib/libbe.so #8 0x004b5f1b in BWindow::~BWindow () from /boot/beos/system/lib/libbe.so #9 0x00413796 in BLooper::Quit () from /boot/beos/system/lib/libbe.so #10 0x004b662a in BWindow::Quit () from /boot/beos/system/lib/libbe.so #11 0x00414e1f in BLooper::_QuitRequested () from /boot/beos/system/lib/libbe.so #12 0x0041331a in BLooper::DispatchMessage () from /boot/beos/system/lib/libbe.so #13 0x004b8ebd in BWindow::DispatchMessage () from /boot/beos/system/lib/libbe.so #14 0x004bc678 in BWindow::task_looper () from /boot/beos/system/lib/libbe.so #15 0x0041488b in BLooper::_task0_ () from /boot/beos/system/lib/libbe.so #16 0x009859c0 in thread_entry () from /boot/beos/system/lib/libroot.so #17 0x70206fec in ?? () (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 12:35:21 2008 From: trac at haiku-os.org (diver) Date: Thu, 10 Jul 2008 10:35:21 -0000 Subject: [Haiku-bugs] [Haiku] #2508: [MediaPlayer] add icons to playlis Message-ID: <040.3c02746f75c9f993e7f48b6966e7e379@haiku-os.org> #2508: [MediaPlayer] add icons to playlis --------------------------------------+------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- MediaPlayer already show icons in Recent menu.[[BR]] It would be nice if it would the same for Playlist menu and Playlist window itself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 13:11:29 2008 From: trac at haiku-os.org (tqh) Date: Thu, 10 Jul 2008 11:11:29 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.220201f5725975fd92ff1b4a2d6e91ea@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by tqh): Info from Sergei D (fyysik, who is having issues with trac):[[BR]][[BR]] We use for internal Mozilla communication BeOS ports, and to have access for those ports from different components and threads we assign to ports name, which must be unique.[[BR]] For that purpose we're using "current thread" identifier printed in octal form as port name - at stage of port creation. Then when we need somewhere to communicate, we are getting port by find_port - again, using portname created from current thread "number.[[BR]] - see[[BR]] http://lxr.mozilla.org/mozilla1.8/source/xpcom/threads/plevent.c#382 [[BR]] http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsAppShell.cpp#122 [[BR]] http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#93 [[BR]] [[BR]] To get current port ID we use methods PR_GetCurrentThread() from NSPR (NS runtime kit):[[BR]] http://lxr.mozilla.org/mozilla1.8/source/nsprpub/pr/src/bthreads/btthread.c#417 [[BR]] [[BR]] and there is something wrong. I'm not so competent yet to analyze btthreads code, but once I replaced all calls for PR_GetCurrentThread() in 3 places mentioned above, plus this one (NB!!!, may be quite important, as it uses another PR method - mGuiThread = PR_CreateThread(PR_SYSTEM_THREAD,*)): [[BR]] http://lxr.mozilla.org/mozilla1.8/source/widget/src/beos/nsToolkit.cpp#231 [[BR]] [[BR]] with simple native find_thread(0) - all started to work as "expected" in Haiku - mozilla apps can now run simultaneously.[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 13:17:26 2008 From: trac at haiku-os.org (tqh) Date: Thu, 10 Jul 2008 11:17:26 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.e99bf243919999239ee0c6967a86ed96@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by tqh): Also see http://community.livejournal.com/bezilla/282356.html for additional comments. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:10:30 2008 From: trac at haiku-os.org (diver) Date: Thu, 10 Jul 2008 12:10:30 -0000 Subject: [Haiku-bugs] [Haiku] #2411: [app_server] moving a splitter in Pe is too slow In-Reply-To: <040.0800d6ad08776db3f71f410c7a9ff55f@haiku-os.org> References: <040.0800d6ad08776db3f71f410c7a9ff55f@haiku-os.org> Message-ID: <049.3c4b88454fe149e1874da88fea4ba92b@haiku-os.org> #2411: [app_server] moving a splitter in Pe is too slow ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): Speed seems to be improved quite a bit recently, but there still a little lag exist. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:16:58 2008 From: trac at haiku-os.org (axeld) Date: Thu, 10 Jul 2008 12:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.b59dd34eff98b87e43cdbb818ab4c1ae@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Just tested: it does work fine with Firefox 3, but it doesn't work with Firefox 2. Since Haiku currently only has version 2, maybe we should change that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:29:39 2008 From: trac at haiku-os.org (diver) Date: Thu, 10 Jul 2008 12:29:39 -0000 Subject: [Haiku-bugs] [Haiku] #514: [NetPositive] slow scroll with middle button In-Reply-To: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> References: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> Message-ID: <049.7f2b5e3c86bf9b162e584aececf9db0b@haiku-os.org> #514: [NetPositive] slow scroll with middle button ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by diver): * component: Kits/Interface Kit => Servers/app_server Comment: This seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:37:34 2008 From: trac at haiku-os.org (stippi) Date: Thu, 10 Jul 2008 12:37:34 -0000 Subject: [Haiku-bugs] [Haiku] #2411: [app_server] moving a splitter in Pe is too slow In-Reply-To: <040.0800d6ad08776db3f71f410c7a9ff55f@haiku-os.org> References: <040.0800d6ad08776db3f71f410c7a9ff55f@haiku-os.org> Message-ID: <049.447af3525901b388f2e0974a105a0af4@haiku-os.org> #2411: [app_server] moving a splitter in Pe is too slow ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ah, thanks for the update. I've tried it. I could not make out any delay more than would be normal. Maybe the other bug about the slow drawing kicks in? The cause of the problem is fixed anyways by removing old mouse moved messages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:39:16 2008 From: trac at haiku-os.org (stippi) Date: Thu, 10 Jul 2008 12:39:16 -0000 Subject: [Haiku-bugs] [Haiku] #514: [NetPositive] slow scroll with middle button In-Reply-To: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> References: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> Message-ID: <049.ef103af74a36dc6e5c61b03cc7dd26c9@haiku-os.org> #514: [NetPositive] slow scroll with middle button ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ah yeah, that would be another fix of the removal of old mouse messages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 14:47:46 2008 From: trac at haiku-os.org (xspager) Date: Thu, 10 Jul 2008 12:47:46 -0000 Subject: [Haiku-bugs] [Haiku] #2506: [app_server] crash in WindowList::RemoveWindow () In-Reply-To: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> References: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> Message-ID: <049.8de0e296fddcad25ebe091f6ad3f6f67@haiku-os.org> #2506: [app_server] crash in WindowList::RemoveWindow () ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by xspager): Also the playlist seems to open on the first workspace, or in the original MediaPlayer Workspace. Still on revision #26348. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 15:24:50 2008 From: trac at haiku-os.org (axeld) Date: Thu, 10 Jul 2008 13:24:50 -0000 Subject: [Haiku-bugs] [Haiku] #2506: [app_server] crash in WindowList::RemoveWindow () In-Reply-To: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> References: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> Message-ID: <049.6054c3531b5ac309beb43e72baf16eb5@haiku-os.org> #2506: [app_server] crash in WindowList::RemoveWindow () ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * priority: normal => critical * status: new => assigned * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 15:58:40 2008 From: trac at haiku-os.org (mt) Date: Thu, 10 Jul 2008 13:58:40 -0000 Subject: [Haiku-bugs] [Haiku] #2485: firefox cannot run on gcc4/gcc2 mixed mode. In-Reply-To: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> References: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> Message-ID: <046.8bc44299a419ff09e803033f620de9d4@haiku-os.org> #2485: firefox cannot run on gcc4/gcc2 mixed mode. ------------------------------------+--------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by mt): I can run firefox on r26368 gcc4/gcc2 mixed mode, thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 16:04:36 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 10 Jul 2008 14:04:36 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.0a26dc7e26858893b07c9367b5eac0eb@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: This was obviously a bug in the Mozilla (BeOS port) code. You can't expect that object pointers are unique across applications. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 16:06:59 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 10 Jul 2008 14:06:59 -0000 Subject: [Haiku-bugs] [Haiku] #1537: Freecell 0.92 quits responding In-Reply-To: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> References: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> Message-ID: <051.31357810b070d49cb5bd94721037c7bb@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 Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): This one may or may not have been fixed with the recent fix of removing of old mouse messages. Have to play lots more freecell to know for sure though. It used to happen after 2 or 3 games, I've now gotten to 4 or 5 without it happening, bug the mouse seems more spastic than usual, although that might be due to VMware, I'll have to try it on real hardware to know for sure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 16:17:50 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 10 Jul 2008 14:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #2485: firefox cannot run on gcc4/gcc2 mixed mode. In-Reply-To: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> References: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> Message-ID: <046.cfce26731679f68faa2951a0b9652aa9@haiku-os.org> #2485: firefox cannot run on gcc4/gcc2 mixed mode. ------------------------------------+--------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by bonefish): Nothing changed in Haiku in this respect. We still use a 4 KB buffer for the section string section. If FireFox' section is bigger, running a version built with the other gcc will fail. I suppose you're running a different FireFox version now, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 16:17:49 2008 From: trac at haiku-os.org (axeld) Date: Thu, 10 Jul 2008 14:17:49 -0000 Subject: [Haiku-bugs] [Haiku] #2506: [app_server] crash in WindowList::RemoveWindow () In-Reply-To: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> References: <040.c347d6ce16fb8888bb7af9ddacb12877@haiku-os.org> Message-ID: <049.6c5d58da39b81611ecd421da4ae001e8@haiku-os.org> #2506: [app_server] crash in WindowList::RemoveWindow () ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26371. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:00:06 2008 From: trac at haiku-os.org (shinta) Date: Thu, 10 Jul 2008 15:00:06 -0000 Subject: [Haiku-bugs] [Haiku] #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect Message-ID: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- When we unarchived BTextControl, the position of text rect of its text view (_BTextInput_) is bad. Top margin is too large. Haiku: r26161[[BR]] [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (bug No.20) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:03:25 2008 From: trac at haiku-os.org (axeld) Date: Thu, 10 Jul 2008 15:03:25 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.26ec9b74b5fbcd8d723f956b4fa4ae4d@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): Maybe I understood something incorrectly, but they are using thread IDs, not object pointers, right? At least, ports look like this on Firefox under BeOS: {{{ 352 p< :75 12 0}}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:05:11 2008 From: trac at haiku-os.org (axeld) Date: Thu, 10 Jul 2008 15:05:11 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.7949b997289e479135e5ad2d9241f85e@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Damn, I accidently had disabled JavaScript, and this feature obviously relies on this. Sorry for the confusion. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:08:40 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 10 Jul 2008 15:08:40 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.9fc2a4d6b0014501ff7c4852872d3129@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): Actually, it's doing an sprintf using the pointer address of the current thread's PRThread struct. This is incorrect, it should be using the native thread_id contained inside the struct, since, as Ingo pointed out, the PRThread *addr cannot possibly be guaranteed to be unique across apps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:11:53 2008 From: trac at haiku-os.org (El-Al) Date: Thu, 10 Jul 2008 15:11:53 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.110ca7a3e0ea99f2e04a620758673817@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by El-Al): A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:14:04 2008 From: trac at haiku-os.org (shinta) Date: Thu, 10 Jul 2008 15:14:04 -0000 Subject: [Haiku-bugs] [Haiku] #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect In-Reply-To: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> References: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> Message-ID: <050.f0f4299ea2ff6e7f14f9a0090dfdfe19@haiku-os.org> #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by shinta): In _BTextInput_::AlignTextRect(), LineHeight(0) returns 1 if BTextControl is unarchived. So, I used font_height instead of LineHeight(0). Additionaly, BTextControl::_InitData() doesn't need to configure text rect because AlignTextRect() is called just after. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 17:40:23 2008 From: trac at haiku-os.org (tqh) Date: Thu, 10 Jul 2008 15:40:23 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.b80b342eeb909309525609a124e860d8@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by tqh): Yes that is incorrect, I think it's as old as the BeOS port btw :) Not really sure if that is enough to explain this problem though. So this bug might get reopened after that fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 22:17:52 2008 From: trac at haiku-os.org (monni) Date: Thu, 10 Jul 2008 20:17:52 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.541d8e769729532fa3fd18b673c486cc@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): Added few panics just to make sure h2generic manages to print out all relevant information and looks like the passed in cookie is from outer space... it gives cookie = -559038737 which translates to 0xdeadbeef -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 18:44:41 2008 From: trac at haiku-os.org (tqh) Date: Thu, 10 Jul 2008 16:44:41 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.e19f9b3331cda27b3295d5f9e2ae8136@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by tqh): Sergei has confirmed that the PRThread has the same pointer address in the different apps in Haiku. I would have thought this would be quite unlikely, but so it is. Therefore they find the same port. Fixing so that thread_id is used in the name as it should will probably fix this. BeOS does something different in mem allocation so the apps pointers are in different addresses. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 10 23:48:12 2008 From: trac at haiku-os.org (monni) Date: Thu, 10 Jul 2008 21:48:12 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.d6ad0bf3186ed9f1e1e6d58d30a134d4@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): {{{ KERN: USB Hub 1: port 1 disabled KERN: BT fetch_device: (0x90ca30cc) KERN: usb_uhci: td (0x02473bc0) error: status: 0x214507ff; token: 0x01e08369; KERN: BT device_removed: device_removed(0x90ca30cc) KERN: usb_uhci: td (0x02473be0) error: status: 0x214507ff; token: 0x01e08369; KERN: BT kill_device: kill_device(0x90ca30cc) KERN: usb_uhci: td (0x02473c00) error: status: 0x214507ff; token: 0x01e08369; KERN: BT publish_devices: publish_devices() KERN: BT publish_devices: published 0 devices KERN: BT fetch_device: (0x90ca30cc) KERN: BT device_close: device_close(0x90ca30cc) KERN: BT device_close: device_close(0x90ca30cc) hdev = 0 KERN: BT device_close: Stopping device 0 and cancelling queues... KERN: USB Stack: tried to get object with invalid usb_id KERN: BT device_close: Cancelled EVENTS on device 0 KERN: USB Stack: tried to get object with invalid usb_id KERN: BT device_close: Cancelled ACL in on device 0 KERN: USB Stack: tried to get object with invalid usb_id KERN: BT device_close: Cancelled ACL out on device 0 KERN: BT device_free: device_free() called on bluetooth/h2generic KERN: BT uninit_driver: uninit_driver() KERN: BT kill_device: kill_device(0x90ca30cc) }}} Crash is caused by several calls to kill_device with same pointer... kill_device frees the pointer which sends the cookie to outer space. http://dev.haiku-os.org/browser/haiku/trunk/src/add- ons/kernel/drivers/bluetooth/h2/h2generic/h2generic.c#L157 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 00:22:45 2008 From: trac at haiku-os.org (nielx) Date: Thu, 10 Jul 2008 22:22:45 -0000 Subject: [Haiku-bugs] [Haiku] #2466: Nested components gone since recently In-Reply-To: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> References: <040.c03a85e7a3f81ced760aea2afee2be16@haiku-os.org> Message-ID: <049.b68ac4fa76724d86af41b36f1f4a9eb7@haiku-os.org> #2466: Nested components gone since recently ---------------------------+------------------------------------------------ Reporter: axeld | Owner: nielx Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by nielx): No problem! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 01:43:14 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 10 Jul 2008 23:43:14 -0000 Subject: [Haiku-bugs] [Haiku] #2510: get_iovec_memory_map: invalid io_vec passed Message-ID: <043.d4340acd917f394b07a5d2c01593e47b@haiku-os.org> #2510: get_iovec_memory_map: invalid io_vec passed ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ r26375 When building the Haiku image dd failed with "Value too large for defined type" while trying to write the 95th MB. The serial output features: {{{ get_iovec_memory_map: invalid io_vec passed (Value too large for defined type) }}} Haven't been able to reproduce it yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 04:49:29 2008 From: trac at haiku-os.org (Bouncer) Date: Fri, 11 Jul 2008 02:49:29 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.78fa7eb7f9955d60c0fc49e10b49c5f3@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by Bouncer): I am pleased to report that audio CD's in my SATA DVD ROM are now being detected. I was able to mount and unmount the CD's without any incidents. All Files are viewable. I think this ticket can be closed now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 05:18:16 2008 From: trac at haiku-os.org (Bouncer) Date: Fri, 11 Jul 2008 03:18:16 -0000 Subject: [Haiku-bugs] [Haiku] #2511: MediaPlayer will not play .wav files from an Audio CD Message-ID: <042.048e59600583eba011fdf084878f0e7b@haiku-os.org> #2511: MediaPlayer will not play .wav files from an Audio CD -----------------------+---------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I did a search for this problem. And found a single match in the comments given for r21153. With not even a TODO. So - if only to make sure this problem is tracked, and not forgotten, here it is again. a) MediaPlayer gives an error if directly accessing the wav file on the Audio CD. b) If the wav file is dragged to the desktop. It is then playable by MediaPlayer. This is on real hardware. SATA DVD Rom drive. Intel HD Audio sound. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 05:38:38 2008 From: trac at haiku-os.org (Bouncer) Date: Fri, 11 Jul 2008 03:38:38 -0000 Subject: [Haiku-bugs] [Haiku] #2512: vlc does not play either wav or mp3 files. Message-ID: <042.55af99727f86b9d169c61243a40f9ec4@haiku-os.org> #2512: vlc does not play either wav or mp3 files. -----------------------+---------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- On real hardware. With Intel HD Audio. The VLC player puts out extremly distorted sound. Basically - its no sound at all most of the time But every second or so - a tiny window opens up for maybe just 50 or 100 ms - and you hear a tiny burst of sound. The sound bursts come in slightly faster than once per second. Over a 20 second interval - I counted 22 or 23 of them. The volume and tone of these tiny sound bursts also seem to correlate with the natural rythym of the music that was being played. For comparision. MediaPlayer plays the same files very well. Without any distortion at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 07:46:48 2008 From: trac at haiku-os.org (scottmc) Date: Fri, 11 Jul 2008 05:46:48 -0000 Subject: [Haiku-bugs] [Haiku] #1537: Freecell 0.92 quits responding In-Reply-To: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> References: <042.ddea47a145b387ae5cc52984d69fbc15@haiku-os.org> Message-ID: <051.ce16d7ae4ee27d7b255d96b9301d93be@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 Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Nope, still there. Just took a couple more hands and the disappearing card problem showed up again. This was with r26340. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 12:20:21 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Fri, 11 Jul 2008 10:20:21 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.52afb370ecbfd9aa1dd904b4327885c3@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 12:44:56 2008 From: trac at haiku-os.org (axeld) Date: Fri, 11 Jul 2008 10:44:56 -0000 Subject: [Haiku-bugs] [Haiku] #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. In-Reply-To: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> References: <042.b13887cc0728cce31a596d269889fffc@haiku-os.org> Message-ID: <051.219df444e4da23796514b23dc25673bf@haiku-os.org> #2469: Haiku (r26165) does not detect SATA DVD/CDROM drive. ---------------------------+------------------------------------------------ Reporter: Bouncer | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): I just checked on another system of mine, and there the SATA DVD-ROM doesn't seem to work. I'll investigate this before reopening the ticket, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 13:36:07 2008 From: trac at haiku-os.org (oruizdorantes) Date: Fri, 11 Jul 2008 11:36:07 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.15489fa2f293e3d6fde9fe2dbf4e67ae@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by oruizdorantes): Its a pleasure fix bugs when someone else has done all the tracking work :) Thanks a lot Monni, there is a TODO pointing this possible problem. BTW you added more debug output, feel free to send me the patch. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 13:45:50 2008 From: trac at haiku-os.org (axeld) Date: Fri, 11 Jul 2008 11:45:50 -0000 Subject: [Haiku-bugs] [Haiku] #2512: vlc does not play either wav or mp3 files. In-Reply-To: <042.55af99727f86b9d169c61243a40f9ec4@haiku-os.org> References: <042.55af99727f86b9d169c61243a40f9ec4@haiku-os.org> Message-ID: <051.57c5317c752e5416b218f26b04d7a649@haiku-os.org> #2512: vlc does not play either wav or mp3 files. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by axeld): I guess you are using the OpenSound HD Audio driver? Have you tried disabling MMX/SSE support in VLC and see if that helps? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 14:22:27 2008 From: trac at haiku-os.org (monni) Date: Fri, 11 Jul 2008 12:22:27 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.a26c15b52fdc63b87e8f49bcf5605a24@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): Well... It's only half of the issue... Now we need to make it wait for the "new" dongle... I looked into it briefly but looks like something doesn't work correctly after reconnect as name of LocalDevice is dongle type and not "siam-0" as it is right after boot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 14:50:26 2008 From: trac at haiku-os.org (galex) Date: Fri, 11 Jul 2008 12:50:26 -0000 Subject: [Haiku-bugs] [Haiku] #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu-Siemens AMILO Pro V3505 Message-ID: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu- Siemens AMILO Pro V3505 --------------------------------+------------------------------------------- Reporter: galex | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- After boot screen I get Segmentation fault in Painter::FillRectNoClipping like [http://dev.haiku-os.org/ticket/2350 #2350] How to reproduce: boot haiku from USB Flash Drive. Tested with r26181, r26346, r26375 downloaded from build haiku-files. Experienced behavior: segfault. Expected behavior: Booting to Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 14:56:12 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 12:56:12 -0000 Subject: [Haiku-bugs] [Haiku] #2512: vlc does not play either wav or mp3 files. In-Reply-To: <042.55af99727f86b9d169c61243a40f9ec4@haiku-os.org> References: <042.55af99727f86b9d169c61243a40f9ec4@haiku-os.org> Message-ID: <051.b1bd2fbc7ebb5d30b797acc3690e41ed@haiku-os.org> #2512: vlc does not play either wav or mp3 files. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): This may be a bug in VLC when the buffer size and respectively latency is so high, or it may be a bug in our BSoundPlayer implementation (also about big buffers/latency). I remember Francois mentioned in IRC that he had to decrease the OSS buffersize to make VLC work. It's not a bug in the OSS code though. Either VLC or the Haiku code that VLC uses, I think BSoundsPlayer or whatever it was called... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 15:19:01 2008 From: trac at haiku-os.org (mt) Date: Fri, 11 Jul 2008 13:19:01 -0000 Subject: [Haiku-bugs] [Haiku] #2485: firefox cannot run on gcc4/gcc2 mixed mode. In-Reply-To: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> References: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> Message-ID: <046.1dd31d1901480580a70564bc8c7448bd@haiku-os.org> #2485: firefox cannot run on gcc4/gcc2 mixed mode. ------------------------------------+--------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by mt): I retested with firefox 2.0.0.14, 2.0.0.15pre, 2.0.0.15 , and they seems to run fine. I think problem is fixed by clean installing r26368. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:21:02 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 14:21:02 -0000 Subject: [Haiku-bugs] [Haiku] #2514: Enlarged Terminal wraps input line overwriting beginning Message-ID: <041.0709cde09fcc236684912295319f2232@haiku-os.org> #2514: Enlarged Terminal wraps input line overwriting beginning -----------------------------------+---------------------------------------- Reporter: stippi | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Make the Terminal wider and enter a longer command line. Before you get to the right end of the window, the cursor will be replaced to the beginning of the line overwriting what you already wrote. Maybe the wrap-around happens at about the position of the original Terminal width. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:23:52 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 14:23:52 -0000 Subject: [Haiku-bugs] [Haiku] #2515: Problems copying long Terminal output and reinserting it into Terminal Message-ID: <041.a33123a376a5ce08c358b656ab91ab9c@haiku-os.org> #2515: Problems copying long Terminal output and reinserting it into Terminal -----------------------------------+---------------------------------------- Reporter: stippi | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- I think the output simply has "new lines" inserted where the "soft" line breaks are in the output. For example, I wanted to delete all object files used in a GCC command line to fix a linkage problem (had some corrupt object files). The pasted text contained line breaks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:25:14 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 14:25:14 -0000 Subject: [Haiku-bugs] [Haiku] #2516: Problems selecting the last character of a line in Terminal Message-ID: <041.99d5f629beaa21d13f66fda7e5778d99@haiku-os.org> #2516: Problems selecting the last character of a line in Terminal -----------------------------------+---------------------------------------- Reporter: stippi | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- When output reaches the right side of the Terminal window, selecting the very last character of that line cannot be done with the mouse. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:45:17 2008 From: trac at haiku-os.org (oruizdorantes) Date: Fri, 11 Jul 2008 14:45:17 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.61931d9d6014289d438cb97aebeb3f1f@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: new => assigned Comment: Bluetooth_server is not yet monitoring devices(DeviceManager class is basically a stub). This is one of the reasons for example, so this feature will take longer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:51:04 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 11 Jul 2008 14:51:04 -0000 Subject: [Haiku-bugs] [Haiku] #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu-Siemens AMILO Pro V3505 In-Reply-To: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> References: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> Message-ID: <049.b8521893b705b8babd41449fc44c0660@haiku-os.org> #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu- Siemens AMILO Pro V3505 ---------------------------------+------------------------------------------ Reporter: galex | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by mmlr): Ehm, so this is a duplicate of #2350 then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:56:24 2008 From: trac at haiku-os.org (galex) Date: Fri, 11 Jul 2008 14:56:24 -0000 Subject: [Haiku-bugs] [Haiku] #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu-Siemens AMILO Pro V3505 In-Reply-To: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> References: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> Message-ID: <049.0c77e8ef751d4d7c43692e41e3d014bb@haiku-os.org> #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu- Siemens AMILO Pro V3505 ---------------------------------+------------------------------------------ Reporter: galex | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by galex): After boot screen I get segmentation fault in Painter::FillRectNoClipping like #2350 How to reproduce: boot haiku from USB Flash Drive. Tested with r26181, r26346, r26375 downloaded from haiku-files. Experienced behavior: segfault. Expected behavior: Booting to Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 16:58:12 2008 From: trac at haiku-os.org (galex) Date: Fri, 11 Jul 2008 14:58:12 -0000 Subject: [Haiku-bugs] [Haiku] #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu-Siemens AMILO Pro V3505 In-Reply-To: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> References: <040.69d3dd668cba362cf2f3ab2007870640@haiku-os.org> Message-ID: <049.8940cf3f2e7a1b1ee18e617caabd0641@haiku-os.org> #2513: Segmentation fault in Painter::FillRectNoClipping when booting on Fujitsu- Siemens AMILO Pro V3505 ---------------------------------+------------------------------------------ Reporter: galex | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by galex): Doh, damn firefox. In #2350 it's on eeePC in failsafe video mode. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:34:41 2008 From: trac at haiku-os.org (meanwhile) Date: Fri, 11 Jul 2008 17:34:41 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.1c85055a0ecf9310d0cf4d1582febdb8@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): I forgot to mention what I did before: After problems (described in #2461), I reformatted the troublesome Haiku partition using PartitionMagic into another filesystem (FAT32), then installed BeOS 5 Pro onto it, from its original install-disc. When asked by the BeOS 5 Pro installer if I wanted to initialize the partition, I chose 'yes' and used the 1024 blocksize. After installing had completed, I checked if the BeOS 5 Pro was properly installed and it was. It was this partition, named 'no name' (see above), that I then tried to initialize, using DriveSetup from another - but still working- Haiku partition on the same PC. Stippi, please let me know if you think this is a DriveSetup bug that can be solved someday, or if it is something inevitable that has to do with recent changes in Haiku. Or maybe DriveSetup can initialize other filesystems like NTFS or FAT32? I'd try that then. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:37:48 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:37:48 -0000 Subject: [Haiku-bugs] [Haiku] #711: [app_server] extremely high cpu usage on replicant movement In-Reply-To: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> References: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> Message-ID: <049.bd2c40a39abb1ccadd8b1aa29958129c@haiku-os.org> #711: [app_server] extremely high cpu usage on replicant movement ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: low | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): Stippi, could this be a dup of bug #1837? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:41:03 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:41:03 -0000 Subject: [Haiku-bugs] [Haiku] #2517: [3dMix] can't open 3dMix project files Message-ID: <040.90af497bc239e53580d1b79c33a76274@haiku-os.org> #2517: [3dMix] can't open 3dMix project files --------------------+------------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------+------------------------------------------------------- Right clicking 3dMix project file and selecting open with 3dMix doesn't open this project. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:43:40 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:43:40 -0000 Subject: [Haiku-bugs] [Haiku] #1481: no sound In-Reply-To: <039.17024d8366da73a31f46e1ab8ee64d5c@haiku-os.org> References: <039.17024d8366da73a31f46e1ab8ee64d5c@haiku-os.org> Message-ID: <048.fbebcdea5baf7ddcf6278432d8a203fa@haiku-os.org> #1481: no sound ----------------------+----------------------------------------------------- Reporter: rino | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Comment(by diver): This bug seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:44:35 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:44:35 -0000 Subject: [Haiku-bugs] [Haiku] #1669: Fails on boot In-Reply-To: <041.97a88b3be8ceb6eaa0b7a84bc846bc33@haiku-os.org> References: <041.97a88b3be8ceb6eaa0b7a84bc846bc33@haiku-os.org> Message-ID: <050.ec9e1fdfa155a6dc306c49ae8deaf19f@haiku-os.org> #1669: Fails on boot ---------------------------+------------------------------------------------ Reporter: artemm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): This bug seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:50:45 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:50:45 -0000 Subject: [Haiku-bugs] [Haiku] #2456: bugs.haiku-os.org doesn't work anymore In-Reply-To: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> References: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> Message-ID: <054.11c7fb9865a707ea1b39bc4d96ef3c14@haiku-os.org> #2456: bugs.haiku-os.org doesn't work anymore -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------+-------------------------------------------------- Comment(by diver): bugs.haiku-os.org is working again, so I think we could close this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:52:17 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:52:17 -0000 Subject: [Haiku-bugs] [Haiku] #380: [3dMix] crash on fountain star (was: [3dMix] crash on stars fountain) In-Reply-To: <040.2533fa66fdc956d5c30b1b61b0d9754e@haiku-os.org> References: <040.2533fa66fdc956d5c30b1b61b0d9754e@haiku-os.org> Message-ID: <049.d43ae674f9f39c8ae81335e393827234@haiku-os.org> #380: [3dMix] crash on fountain star ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by diver): * platform: => All -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:54:12 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:54:12 -0000 Subject: [Haiku-bugs] [Haiku] #312: Quake2 has awfully dodgy mouse input In-Reply-To: <049.c0bdb8d3925d0693b0e6ff5727bf3fb7@haiku-os.org> References: <049.c0bdb8d3925d0693b0e6ff5727bf3fb7@haiku-os.org> Message-ID: <058.7909f404f7fc2e69b6faa9fb09af2ea6@haiku-os.org> #312: Quake2 has awfully dodgy mouse input -----------------------------+---------------------------------------------- Reporter: johndrinkwater | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by diver): Could this be fixed with recent stippi mouse fixes? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:56:09 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:56:09 -0000 Subject: [Haiku-bugs] [Haiku] #507: [VLC] slider flickering In-Reply-To: <040.e44357474e6996a59441562c061cc5e4@haiku-os.org> References: <040.e44357474e6996a59441562c061cc5e4@haiku-os.org> Message-ID: <049.22b7744356c6a80140a47c22b4a80194@haiku-os.org> #507: [VLC] slider flickering ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by diver): * component: - General => Servers/app_server Comment: BTW, MediaPlayer's seeking slider have the same issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:03:22 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 18:03:22 -0000 Subject: [Haiku-bugs] [Haiku] #1097: ext3 filesystem add-on In-Reply-To: <041.be904ddc11b0505699feebe5277517d7@haiku-os.org> References: <041.be904ddc11b0505699feebe5277517d7@haiku-os.org> Message-ID: <050.1aea40260d3b7691b594bc40d3b1b37e@haiku-os.org> #1097: ext3 filesystem add-on ---------------------------+------------------------------------------------ Reporter: ekdahl | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): ext2 is written by Axel some time ago and it could read ext3 too. This could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:12:16 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 18:12:16 -0000 Subject: [Haiku-bugs] [Haiku] #1482: Haiku Boot Menu selection defaults to item at bottom of menu instead of top In-Reply-To: <042.7d717c02ebd1d75cb14bf5e343867fba@haiku-os.org> References: <042.7d717c02ebd1d75cb14bf5e343867fba@haiku-os.org> Message-ID: <051.9c6d21ba2c66fe01c435ba2952d6fe8d@haiku-os.org> #1482: Haiku Boot Menu selection defaults to item at bottom of menu instead of top ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): There is also red (i think) title which also confuce me, for several seconds i can't understand which item is selected and i have to move ip/down arrow to make sure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:16:30 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 18:16:30 -0000 Subject: [Haiku-bugs] [Haiku] #1550: Tracker crashes when clicking on column heading in Mail inbox folder In-Reply-To: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> References: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> Message-ID: <049.a97e2d2d1ee4aa6aed1767937e0be5ca@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 Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by diver): Back trace looks similar to bug #708, could this be a dup? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:32:03 2008 From: trac at haiku-os.org (meanwhile) Date: Fri, 11 Jul 2008 18:32:03 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.e42cf9e9c98cfa5767dbd7e9f20c2061@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Update: just managed to replace the working Haiku partition with the latest revision (without initializing)... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:41:08 2008 From: trac at haiku-os.org (oruizdorantes) Date: Fri, 11 Jul 2008 18:41:08 -0000 Subject: [Haiku-bugs] [Haiku] #2290: bluetooth crashes when removing device In-Reply-To: <040.007f6bc38c42a1ccbbd6956a21e2033d@haiku-os.org> References: <040.007f6bc38c42a1ccbbd6956a21e2033d@haiku-os.org> Message-ID: <049.b7c361014457574ff44782c85e342f71@haiku-os.org> #2290: bluetooth crashes when removing device --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:49:56 2008 From: trac at haiku-os.org (oruizdorantes) Date: Fri, 11 Jul 2008 18:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.d448bac9b6aa090ecdfeba4fd7f6a70d@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: assigned => closed * resolution: => fixed Comment: Fixed at rev 26382 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 21:01:44 2008 From: trac at haiku-os.org (meanwhile) Date: Fri, 11 Jul 2008 19:01:44 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.28b4a8216ad3e6633d50e645e58b1e61@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by meanwhile): Got a recent working Haiku partition again: r26375 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 21:15:51 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 19:15:51 -0000 Subject: [Haiku-bugs] [Haiku] #926: [app_server] could dead lock when scrolling in NetPositive In-Reply-To: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> References: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> Message-ID: <049.14b76d5553c4c720077945ca9aaf5529@haiku-os.org> #926: [app_server] could dead lock when scrolling in NetPositive ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, thanks for reminding! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 22:02:46 2008 From: trac at haiku-os.org (monni) Date: Fri, 11 Jul 2008 20:02:46 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.cd30d6ecaaa93d875364e15cb7ad0069@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by monni): * status: closed => reopened * resolution: fixed => Comment: Hmmm... looks like this crash is regression to fix in r26382 {{{ :event_complete + 0x0070 :Finished__8TransferUlUl + 0x0027 :FinishTransfers__4UHCI + 0x0441 :FinishThread__4UHCIPv + 0x001f }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 22:10:56 2008 From: trac at haiku-os.org (julun) Date: Fri, 11 Jul 2008 20:10:56 -0000 Subject: [Haiku-bugs] [Haiku] #1441: Crash when closing Icon-O-Matic In-Reply-To: <042.8792a919999be81602b89de7307dbff5@haiku-os.org> References: <042.8792a919999be81602b89de7307dbff5@haiku-os.org> Message-ID: <051.88ef282785e71573049c69df2dcd0285@haiku-os.org> #1441: Crash when closing Icon-O-Matic ----------------------------------------+----------------------------------- Reporter: kbogert | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by julun): * status: assigned => closed * resolution: => fixed Comment: Should be fixed in r26383. Note that these crashes happened on gcc4 builds only. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 22:35:49 2008 From: trac at haiku-os.org (korli) Date: Fri, 11 Jul 2008 20:35:49 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.735027f87eae277f11049c4cef9ddde3@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: assigned => closed * resolution: => fixed Comment: Thanks. Bug really fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 23:50:28 2008 From: trac at haiku-os.org (monni) Date: Fri, 11 Jul 2008 21:50:28 -0000 Subject: [Haiku-bugs] [Haiku] #2505: bluetooth_server provokes vm_page_fault in h2generic In-Reply-To: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> References: <040.728ba69a93cd77385ad6df43fb578dbf@haiku-os.org> Message-ID: <049.5dfdf5533da4a868e44aad2ed461ffc0@haiku-os.org> #2505: bluetooth_server provokes vm_page_fault in h2generic --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): syslog: {{{ KERN: BT h2generic device_control: ioctl() opcode 12999 size 17. KERN: BT h2generic device_control: device launched 0 KERN: BT command_complete: 21 19:04:0a: KERN: BT assembly_rx: count 6 0x00000000 0x80282400 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x80282400 KERN: Last message repeated 15 times. KERN: BT assembly_rx: count 1 0x00000000 0x80282400 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT h2generic device_close: device_close(0x90bdb198) KERN: BT h2generic device_close: device_close(0x90bdb198) hdev = 0 KERN: BT h2generic device_close: bluetooth/h2generic/0 not running?? KERN: BT h2generic device_free: device_free() called on bluetooth/h2generic KERN: BT h2generic kill_device: (0x90bdb198) KERN: BT h2generic device_open: device_open() KERN: BT h2generic device_open: Device not found in the open list! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:07:25 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:07:25 -0000 Subject: [Haiku-bugs] [Haiku] #1801: [audio_mixer] font sensitive issue (easy) (was: [audio_mixer] font sensitive issue) In-Reply-To: <040.a06646bdeaa72c1c6bd5d52641b43fd7@haiku-os.org> References: <040.a06646bdeaa72c1c6bd5d52641b43fd7@haiku-os.org> Message-ID: <049.5d88451460e59d181154efcb7aec80f1@haiku-os.org> #1801: [audio_mixer] font sensitive issue (easy) ----------------------------+----------------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:08:14 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:08:14 -0000 Subject: [Haiku-bugs] [Haiku] #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size (easy) (was: [HaikuImage] Remove Bitstream fonts to reduce haiku image size.) In-Reply-To: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> References: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> Message-ID: <049.2550919b6e6a8033eb12b9cd5e37b049@haiku-os.org> #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:11:03 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:11:03 -0000 Subject: [Haiku-bugs] [Haiku] #2315: [Workspaces] should have sticky menu (easy) (was: [Workspaces] should have sticky menu) In-Reply-To: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> References: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> Message-ID: <049.6284592d08570b6ad8db6af9ebf0e799@haiku-os.org> #2315: [Workspaces] should have sticky menu (easy) --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:11:39 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:11:39 -0000 Subject: [Haiku-bugs] [Haiku] #2320: [SoundRecorder] don't need zoom button (easy) (was: [SoundRecorder] don't need zoom button) In-Reply-To: <040.f32f73a71b4bcfbf0e0162c101b1d087@haiku-os.org> References: <040.f32f73a71b4bcfbf0e0162c101b1d087@haiku-os.org> Message-ID: <049.030b23e0c173133168682648ca87c145@haiku-os.org> #2320: [SoundRecorder] don't need zoom button (easy) -----------------------------------------+---------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------------+---------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:12:07 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:12:07 -0000 Subject: [Haiku-bugs] [Haiku] #2322: [Zip-O-Matic] don't need zoom button (easy) (was: [Zip-O-Matic] don't need zoom button.) In-Reply-To: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> References: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> Message-ID: <049.8769421350502a18358d0a56233a2408@haiku-os.org> #2322: [Zip-O-Matic] don't need zoom button (easy) ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:13:16 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:13:16 -0000 Subject: [Haiku-bugs] [Haiku] #2324: [DriveSetup] slow startup In-Reply-To: <040.f8a767766e0c28d850b6038d4491d6c1@haiku-os.org> References: <040.f8a767766e0c28d850b6038d4491d6c1@haiku-os.org> Message-ID: <049.8c3a7a3d85464ed7ca1b028f5aba60e0@haiku-os.org> #2324: [DriveSetup] slow startup --------------------------------------+------------------------------------- Reporter: diver | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by diver): This could be a dup of bug #1823 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:14:02 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:14:02 -0000 Subject: [Haiku-bugs] [Haiku] #2328: [bootman] doesn't have an icon (easy) (was: [bootman] doesn't have an icon) In-Reply-To: <040.89364c6d9184145346f9f07a314a64fb@haiku-os.org> References: <040.89364c6d9184145346f9f07a314a64fb@haiku-os.org> Message-ID: <049.7aa8b44027c45740d73a91d2f9360ab8@haiku-os.org> #2328: [bootman] doesn't have an icon (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:14:28 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:14:28 -0000 Subject: [Haiku-bugs] [Haiku] #2329: [bootman] starts at one position and then suddenly jumps to another (easy) (was: [bootman] starts at one position and then suddenly jumps to another) In-Reply-To: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> References: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> Message-ID: <049.d8655ad9ccd8b4aa5d2b61f014f1492d@haiku-os.org> #2329: [bootman] starts at one position and then suddenly jumps to another (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:14:34 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:14:34 -0000 Subject: [Haiku-bugs] [Haiku] #2330: [bootman] GUI should have size limits (easy) (was: [bootman] GUI should have size limits) In-Reply-To: <040.4ef3ccf800a0e171d7e4dce40c036d2d@haiku-os.org> References: <040.4ef3ccf800a0e171d7e4dce40c036d2d@haiku-os.org> Message-ID: <049.2e2cd3b7b8c046af248b276203da66f6@haiku-os.org> #2330: [bootman] GUI should have size limits (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:15:28 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:15:28 -0000 Subject: [Haiku-bugs] [Haiku] #2331: [MediaPlayer] sometimes starts with corrupted interface In-Reply-To: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> References: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> Message-ID: <049.3140eafa324ff2bcad84cdfc5b7c10db@haiku-os.org> #2331: [MediaPlayer] sometimes starts with corrupted interface ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by diver): I still see black parts after several restarts of MediaPlayer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:16:11 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:16:11 -0000 Subject: [Haiku-bugs] [Haiku] #2333: [CDPlayer] if there is no CD drive it should not show main UI after error message (easy) (was: [CDPlayer] if there is no CD drive it should not show main UI after error message.) In-Reply-To: <040.c8c924961d6d30fd71d686651fbaef16@haiku-os.org> References: <040.c8c924961d6d30fd71d686651fbaef16@haiku-os.org> Message-ID: <049.62873eee002430877d4640209891adeb@haiku-os.org> #2333: [CDPlayer] if there is no CD drive it should not show main UI after error message (easy) ------------------------------------+--------------------------------------- Reporter: diver | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CDPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:16:36 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:16:36 -0000 Subject: [Haiku-bugs] [Haiku] #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) (was: [Screen] "Do you wish to keep these settings" isn't font sensetive) In-Reply-To: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> References: <040.3438d1833d393abc639f0f12b2e633a3@haiku-os.org> Message-ID: <049.3a609f13a60485320f307c909094200b@haiku-os.org> #2370: [Screen] "Do you wish to keep these settings" isn't font sensetive (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:17:56 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:17:56 -0000 Subject: [Haiku-bugs] [Haiku] #2428: [sshd] can't start sshd In-Reply-To: <040.3a7f0b60cf673f0880f4f3c0762b5bb8@haiku-os.org> References: <040.3a7f0b60cf673f0880f4f3c0762b5bb8@haiku-os.org> Message-ID: <049.a3a3162c06df28b7d5821085fdb98feb@haiku-os.org> #2428: [sshd] can't start sshd ----------------------------------------------+----------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by diver): This should be closed as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:18:30 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:18:30 -0000 Subject: [Haiku-bugs] [Haiku] #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts In-Reply-To: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> References: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> Message-ID: <049.49593046376d44a662fcb65c2f4e9f6c@haiku-os.org> #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by diver): This seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:18:54 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:18:54 -0000 Subject: [Haiku-bugs] [Haiku] #2436: [MediaPlayer] don't need zoom button in info window (easy) (was: [MediaPlayer] don't need zoom button in info window) In-Reply-To: <040.a75b93392c6e5639b354b323faeaa92c@haiku-os.org> References: <040.a75b93392c6e5639b354b323faeaa92c@haiku-os.org> Message-ID: <049.253ebd8a91800aeefef8f06a1cfb2cdf@haiku-os.org> #2436: [MediaPlayer] don't need zoom button in info window (easy) ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:19:04 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:19:04 -0000 Subject: [Haiku-bugs] [Haiku] #2437: [MediaPlayer] add file icon in info window (easy) (was: [MediaPlayer] add file icon in info window) In-Reply-To: <040.bc873cae2598dad62834b26a943524bc@haiku-os.org> References: <040.bc873cae2598dad62834b26a943524bc@haiku-os.org> Message-ID: <049.d5eaab93ed12813d250775004c2e2d51@haiku-os.org> #2437: [MediaPlayer] add file icon in info window (easy) ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:19:12 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:19:12 -0000 Subject: [Haiku-bugs] [Haiku] #2438: [Tracker] add filetype icons in search window (easy) (was: [Tracker] add filetype icons in search window) In-Reply-To: <040.4e23a122ad6a64d4382002f48933d007@haiku-os.org> References: <040.4e23a122ad6a64d4382002f48933d007@haiku-os.org> Message-ID: <049.36eb6b8397a1de1d275d42159cb356e2@haiku-os.org> #2438: [Tracker] add filetype icons in search window (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:19:50 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:19:50 -0000 Subject: [Haiku-bugs] [Haiku] #2497: [AboutSystem] right textview is not selectable (easy) (was: [AboutSystem] right textview is not selectable) In-Reply-To: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> References: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> Message-ID: <049.972bec7617223b269f746ab6e76f7f30@haiku-os.org> #2497: [AboutSystem] right textview is not selectable (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:20:31 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 22:20:31 -0000 Subject: [Haiku-bugs] [Haiku] #2508: [MediaPlayer] add icons to playlist (easy) (was: [MediaPlayer] add icons to playlis) In-Reply-To: <040.3c02746f75c9f993e7f48b6966e7e379@haiku-os.org> References: <040.3c02746f75c9f993e7f48b6966e7e379@haiku-os.org> Message-ID: <049.8767e50cd9c20035a926b9d600679103@haiku-os.org> #2508: [MediaPlayer] add icons to playlist (easy) ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 00:58:58 2008 From: trac at haiku-os.org (scottmc) Date: Fri, 11 Jul 2008 22:58:58 -0000 Subject: [Haiku-bugs] [Haiku] #2322: [Zip-O-Matic] don't need zoom button (easy) In-Reply-To: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> References: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> Message-ID: <049.dce17868df790a438a40bc7d504b2a36@haiku-os.org> #2322: [Zip-O-Matic] don't need zoom button (easy) ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by scottmc): http://dev.haiku-os.org/browser/haiku/trunk/src/add- ons/tracker/zipomatic/ZipOMaticWindow.cpp Line 33, this seems to be commented out for some reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:09:35 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 11 Jul 2008 23:09:35 -0000 Subject: [Haiku-bugs] [Haiku] #2485: firefox cannot run on gcc4/gcc2 mixed mode. In-Reply-To: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> References: <037.56b5eeb3af785520f9a44bafaa9d8206@haiku-os.org> Message-ID: <046.e04ad25fa87562991db6e5feac7d4e17@haiku-os.org> #2485: firefox cannot run on gcc4/gcc2 mixed mode. ------------------------------------+--------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: OK, closing. Please re-open, if encountering the problem again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:10:03 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 11 Jul 2008 23:10:03 -0000 Subject: [Haiku-bugs] [Haiku] #2428: [sshd] can't start sshd In-Reply-To: <040.3a7f0b60cf673f0880f4f3c0762b5bb8@haiku-os.org> References: <040.3a7f0b60cf673f0880f4f3c0762b5bb8@haiku-os.org> Message-ID: <049.131865e7b597c217145e914e6b8edc92@haiku-os.org> #2428: [sshd] can't start sshd ----------------------------------------------+----------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:37:01 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 11 Jul 2008 23:37:01 -0000 Subject: [Haiku-bugs] [Haiku] #2514: Enlarged Terminal wraps input line overwriting beginning In-Reply-To: <041.0709cde09fcc236684912295319f2232@haiku-os.org> References: <041.0709cde09fcc236684912295319f2232@haiku-os.org> Message-ID: <050.4eba56f9093370d87ebd9f51e7d2add6@haiku-os.org> #2514: Enlarged Terminal wraps input line overwriting beginning ------------------------+--------------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * owner: jackburton => axeld * component: Applications/Terminal => - General Comment: Can't reproduce the bug according to your description. I can reproduce it though, when the Terminal window is resized while a program other than the shell is running in the foreground (less, vim,...). After terminating the program the described behavior can be observed. Apparently bash/readline doesn't re-get the terminal window size for some reason. Might be a bug in the bash/readline version we're using or just in the Haiku port. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:38:37 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 11 Jul 2008 23:38:37 -0000 Subject: [Haiku-bugs] [Haiku] #2516: Problems selecting the last character of a line in Terminal In-Reply-To: <041.99d5f629beaa21d13f66fda7e5778d99@haiku-os.org> References: <041.99d5f629beaa21d13f66fda7e5778d99@haiku-os.org> Message-ID: <050.22b67703f9d9b0f8850d386da682cda5@haiku-os.org> #2516: Problems selecting the last character of a line in Terminal ------------------------------------+--------------------------------------- Reporter: stippi | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * owner: jackburton => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:38:12 2008 From: trac at haiku-os.org (bonefish) Date: Fri, 11 Jul 2008 23:38:12 -0000 Subject: [Haiku-bugs] [Haiku] #2515: Problems copying long Terminal output and reinserting it into Terminal In-Reply-To: <041.a33123a376a5ce08c358b656ab91ab9c@haiku-os.org> References: <041.a33123a376a5ce08c358b656ab91ab9c@haiku-os.org> Message-ID: <050.d8c5c6edde3c6c825c0fd851c88923ae@haiku-os.org> #2515: Problems copying long Terminal output and reinserting it into Terminal ------------------------------------+--------------------------------------- Reporter: stippi | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * owner: jackburton => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 01:47:08 2008 From: trac at haiku-os.org (cebif) Date: Fri, 11 Jul 2008 23:47:08 -0000 Subject: [Haiku-bugs] [Haiku] #2518: KDL fetching new email messages Message-ID: <040.992d6cd00874b550a333ad419955e931@haiku-os.org> #2518: KDL fetching new email messages ---------------------------------+------------------------------------------ Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------+------------------------------------------ If I right click on the BeMail icon on the Deskbar and select Send Receive new messages. After a few seconds KDL results. It only partially gets all the messages available before KDL. This is reproduceable every time. I will post the version I was testing and a backtrace shortly -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 02:16:21 2008 From: trac at haiku-os.org (cebif) Date: Sat, 12 Jul 2008 00:16:21 -0000 Subject: [Haiku-bugs] [Haiku] #2518: KDL fetching new email messages In-Reply-To: <040.992d6cd00874b550a333ad419955e931@haiku-os.org> References: <040.992d6cd00874b550a333ad419955e931@haiku-os.org> Message-ID: <049.34c9b7a8f36ba9181e49bc1d93bcde1a@haiku-os.org> #2518: KDL fetching new email messages ----------------------------------+----------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Comment(by cebif): I was testing with r26181 raw image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:02:00 2008 From: trac at haiku-os.org (cebif) Date: Sat, 12 Jul 2008 01:02:00 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading Message-ID: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading -------------------------+-------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- I have got a KI1000LCD Line Interactive UPS (KI Series) connected to serial port 1. Every time Haiku boots or I start a application it beeps continuously and at irregular intervals. When I disabled the serial port from the bios there was no beeping. When I started Haiku without the serial port disabled but in Safe Mode,it did not stop the beeping. When I say safe mode everything was selected. It does not seem to cause any real problems with Haiku performance but if there was a software driver for this UPS would this be causing problems? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 22:35:49 2008 From: trac at haiku-os.org (korli) Date: Fri, 11 Jul 2008 20:35:49 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.735027f87eae277f11049c4cef9ddde3@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: assigned => closed * resolution: => fixed Comment: Thanks. Bug really fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:07:54 2008 From: trac at haiku-os.org (umccullough) Date: Sat, 12 Jul 2008 01:07:54 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading In-Reply-To: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> References: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> Message-ID: <049.d453d89b73ad8e63fc4ab4d71b607ea4@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading --------------------------+------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by umccullough): Probably a result of Haiku spitting out pages and pages of debug info to the serial port by default currently :) I think you can turn this feature off in the kernel settings in the meantime, but I don't have that info in front of my right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:19:37 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 12 Jul 2008 01:19:37 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading In-Reply-To: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> References: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> Message-ID: <049.f9188ac927dd104576df1832e06ddf40@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading --------------------------+------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: Please have a look at ~/config/settings/kernel/drivers/kernel (or data/settings/kernel/drivers/kernel in the source tree, if you build your own images). You can disable serial debug output or send it to another serial port. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:29:25 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 12 Jul 2008 01:29:25 -0000 Subject: [Haiku-bugs] [Haiku] #2515: Problems copying long Terminal output and reinserting it into Terminal In-Reply-To: <041.a33123a376a5ce08c358b656ab91ab9c@haiku-os.org> References: <041.a33123a376a5ce08c358b656ab91ab9c@haiku-os.org> Message-ID: <050.b7abafe9ee793a773d137d6943dd5aa4@haiku-os.org> #2515: Problems copying long Terminal output and reinserting it into Terminal ------------------------------------+--------------------------------------- Reporter: stippi | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26387. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:40:16 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 12 Jul 2008 01:40:16 -0000 Subject: [Haiku-bugs] [Haiku] #2516: Problems selecting the last character of a line in Terminal In-Reply-To: <041.99d5f629beaa21d13f66fda7e5778d99@haiku-os.org> References: <041.99d5f629beaa21d13f66fda7e5778d99@haiku-os.org> Message-ID: <050.4964b1d3d052052801a09751b5e161a0@haiku-os.org> #2516: Problems selecting the last character of a line in Terminal ------------------------------------+--------------------------------------- Reporter: stippi | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26388. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:07:48 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 18:07:48 -0000 Subject: [Haiku-bugs] [Haiku] #1391: [Tracker] don't show icons for volumes in mount menu (easy) (was: [Tracker] don't show icons for volumes in mount menu) In-Reply-To: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> References: <040.f5865c80e044f4bb15995234801418c0@haiku-os.org> Message-ID: <049.a25372bba78e37ed481671190c04a2bf@haiku-os.org> #1391: [Tracker] don't show icons for volumes in mount menu (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 05:09:46 2008 From: trac at haiku-os.org (cebif) Date: Sat, 12 Jul 2008 03:09:46 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading In-Reply-To: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> References: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> Message-ID: <049.90445af8b72332cf41f8d92753237e61@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading --------------------------+------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by cebif): This is the content of my kernel file and the change I made: serial_debug_output false # disables serial debug output, default is enabled #serial_debug_port 0 # possible values: | # serial interface number (as enumerated by the BIOS) or the # base port of the serial interface to be used for kernel # debug output and the kernel debugger # default is 0 (COM1) #serial_debug_speed 57600 # possible values: <9600|19200|38400|57600|115200> # default is 115200 With the hash symbol deleted before the first line there is still a little bit of beeping but much less. For the line #Serial_debug_port 0 I also tried removing the hash and changing port number from 1 to 0, but that still did not stop all beeping so I put the hash symbol back in front. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 05:21:12 2008 From: trac at haiku-os.org (cebif) Date: Sat, 12 Jul 2008 03:21:12 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading In-Reply-To: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> References: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> Message-ID: <049.6acd38c75c61ae3d848a079b6d7377a0@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading --------------------------+------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by cebif): I re enabled serial port debug and switched the serial debug output to serial port 2 and that stopped all beeping. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 19:58:33 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 17:58:33 -0000 Subject: [Haiku-bugs] [Haiku] #926: [app_server] could dead lock when scrolling in NetPositive In-Reply-To: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> References: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> Message-ID: <049.9096b6e9097b24016df1687c20359c8d@haiku-os.org> #926: [app_server] could dead lock when scrolling in NetPositive ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): Please, close this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 20:00:55 2008 From: trac at haiku-os.org (diver) Date: Fri, 11 Jul 2008 18:00:55 -0000 Subject: [Haiku-bugs] [Haiku] #970: create an easy to use partition manager In-Reply-To: <045.dee3320bb44fc7e732bd7e932025cbfc@haiku-os.org> References: <045.dee3320bb44fc7e732bd7e932025cbfc@haiku-os.org> Message-ID: <054.0a38f9caf124321889b7c7a35df3af80@haiku-os.org> #970: create an easy to use partition manager --------------------------------------+------------------------------------- Reporter: wkornewald | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by diver): DriveSetup is already somewhat working, so this could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 11 21:18:23 2008 From: trac at haiku-os.org (stippi) Date: Fri, 11 Jul 2008 19:18:23 -0000 Subject: [Haiku-bugs] [Haiku] #711: [app_server] extremely high cpu usage on replicant movement In-Reply-To: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> References: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> Message-ID: <049.89ff46182cea191693750a7c2ec62a97@haiku-os.org> #711: [app_server] extremely high cpu usage on replicant movement ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: low | Milestone: R1 Component: Servers/app_server | Version: Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => duplicate Comment: Yes, indeed. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 03:13:20 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 12 Jul 2008 01:13:20 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.068ad477eb7fcbb0d20833398acb0fad@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bonefish): The problem seems to be fixed in r26375 in my branch. At least a complete "jam -q @image" worked with 824 MB (1 GB - 200 MB tracing buffer, also had kernel heap leak checking enabled). Might also work with less memory, but 512 MB is definitely not enough, since, as written earlier, after a fork() jam's heap alone requires 2 * 270 MB. Swap file support will be required in this case. I'll close the ticket when I've merged my branch into the trunk. If I forget, please do remind me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 13:50:58 2008 From: trac at haiku-os.org (shinta) Date: Sat, 12 Jul 2008 11:50:58 -0000 Subject: [Haiku-bugs] [Haiku] #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect In-Reply-To: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> References: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> Message-ID: <050.f16d5f50957bbeb43fa882a9253bd296@haiku-os.org> #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by shinta): Above patch fixes this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 16:04:44 2008 From: trac at haiku-os.org (mmlr) Date: Sat, 12 Jul 2008 14:04:44 -0000 Subject: [Haiku-bugs] [Haiku] #2518: KDL fetching new email messages In-Reply-To: <040.992d6cd00874b550a333ad419955e931@haiku-os.org> References: <040.992d6cd00874b550a333ad419955e931@haiku-os.org> Message-ID: <049.d8960700772ad70734fdb98994391161@haiku-os.org> #2518: KDL fetching new email messages ----------------------------------+----------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1914. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 16:04:56 2008 From: trac at haiku-os.org (mmlr) Date: Sat, 12 Jul 2008 14:04:56 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.1ee8cf2390a25faae5f355701366dade@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Old description: > and again, r24348 > > bfs: Insert:1301: Name in use > Last message repeated 2 times. > wait interval 524536, scan pages 4356, free 2046, target 2050 > wait interval 524304, scan pages 4358, free 2045, target 2051 > wait interval 524072, scan pages 4360, free 2044, target 2052 > wait interval 524072, scan pages 4360, free 2044, target 2052 > bfs: Insert:1301: Name in use > PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = > 0x91053d80)! > Welcome to Kernel Debugging Land... > Running on CPU 0 > kdebug> bt > stack trace for thread 298 "svn" > kernel stack: 0x93af4000 to 0x93af8000 > user stack: 0x7efe7000 to 0x7ffe7000 > frame caller :function + offset > 93af797c (+ 52) 80082db3 :invoke_debugger_command + 0x00cf > 93af79b0 (+ 64) 80083b54 :_ParseCommand__16ExpressionParserRi > + 0x01f8 > 93af79f0 (+ 48) 80083546 > :EvaluateCommand__16ExpressionParserPCcRi + 0x01de > 93af7a20 (+ 228) 80084c68 :evaluate_debug_command + 0x0088 > 93af7b04 (+ 64) 80081986 :kernel_debugger_loop__Fv + 0x017a > 93af7b44 (+ 48) 800825d1 :kernel_debugger + 0x010d > 93af7b74 (+ 192) 800824b9 :panic + 0x0029 > 93af7c34 (+ 64) 800486d6 :new_vnode + 0x005a > 93af7c74 (+ 64) 802d6d72 > :New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a > 93af7cb4 (+ 176) 802dd3f1 > :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571 > 93af7d64 (+ 96) 802e78eb :bfs_create_dir__FPvT0PCciPx + 0x0107 > 93af7dc4 (+ 320) 8004ab0a :dir_create__FiPcib + 0x0082 > 93af7f04 (+ 64) 8004ff78 :_user_create_dir + 0x0094 > 93af7f44 (+ 100) 80092652 :pre_syscall_debug_done + 0x0002 > (nearest) > iframe at 0x93af7fa8 (end = 0x93af8000) > eax 0x50 ebx 0x458bc8 ecx 0x7ffe6734 edx 0xffff0104 > esi 0x0 edi 0x19754e08 ebp 0x7ffe6760 esp 0x93af7fdc > eip 0xffff0104 eflags 0x206 > vector: 0x63, error code: 0x0 > 93af7fa8 (+ 0) ffff0104 > 7ffe6760 (+ 48) 0032691f > :unknown + 0xf91f > 7ffe6790 (+ 144) 002c8516 > :unknown + 0xd516 > 7ffe6820 (+ 64) 002c861b > :unknown + 0xd61b > 7ffe6860 (+ 64) 0024fd35 > :unknown + 0x1ad35 > 7ffe68a0 (+ 48) 0024d45f > :unknown + 0x1845f > 7ffe68d0 (+ 176) 0024dd6d > :unknown + 0x18d6d > 7ffe6980 (+ 64) 002b4bc5 > :unknown + 0x1bc5 > 7ffe69c0 (+ 96) 00299f78 > :unknown + 0x7f78 > 7ffe6a20 (+ 112) 0029ab5a > :unknown + 0x8b5a > 7ffe6a90 (+ 80) 00299126 > :unknown + 0x7126 > 7ffe6ae0 (+ 64) 00295466 > :unknown + 0x3466 > 7ffe6b20 (+ 176) 0023a1dc > :unknown + 0x51dc > 7ffe6bd0 (+ 160) 00230426 > :unknown + 0x18426 > 7ffe6c70 (+ 64) 002304f3 > :unknown + 0x184f3 > 7ffe6cb0 (+ 80) 0020c9b1 :unknown + > 0xc9b1 > 7ffe6d00 (+ 640) 002091fc :unknown + > 0x91fc > 7ffe6f80 (+ 44) 00204c45 :unknown + > 0x4c45 > 7ffe6fac (+ 48) 001007ca 3453:runtime_loader_seg0ro at 0x00100000 + 0x7ca > 7ffe6fdc (+ 0) 7ffe6fec 3452:svn_main_stack at 0x7efe7000 + 0xffffec > kdebug> vnode 0x90c1b300 > VNODE: 0x90c1b300 > device: -858993460 > id: 0 > ref_count: 78233 > private_node: 0x00000000 > mount: 0x3bbe0ad9 > covered_by: 0x00000001 > cache: 0xffffffff > flags: --- > advisory_lock: 0x00000000 > kdebug> > kdebug> mount  s > address id root covers cookie fs_name > 0x908ade00 1 0x908ade40 0x00000000 0x90861980 rootfs > 0x908ade80 2 0x908adf00 0x908adec0 0x908619c0 devfs > 0x908adf40 3 0x908adfc0 0x908adf80 0x908c4a50 pipefs > 0x908e2540 4 0x908e2600 0x908e2580 0x908f1000 bfs > 0x90b17880 5 0x90b17940 0x90b178c0 0x909d0c00 bfs > kdebug> mount 5 > MOUNT: 0x90b17880 > id: 5 > device_name: /dev/disk/ata/0/slave/raw > fs_name: bfs > cookie: 0x909d0c00 > root_vnode: 0x90b17940 > covers_vnode: 0x90b178c0 > partition: 0x908e9600 > lock: 4807 > flags: > kdebug> New description: and again, r24348 {{{ bfs: Insert:1301: Name in use Last message repeated 2 times. wait interval 524536, scan pages 4356, free 2046, target 2050 wait interval 524304, scan pages 4358, free 2045, target 2051 wait interval 524072, scan pages 4360, free 2044, target 2052 wait interval 524072, scan pages 4360, free 2044, target 2052 bfs: Insert:1301: Name in use PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 298 "svn" kernel stack: 0x93af4000 to 0x93af8000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 93af797c (+ 52) 80082db3 :invoke_debugger_command + 0x00cf 93af79b0 (+ 64) 80083b54 :_ParseCommand__16ExpressionParserRi + 0x01f8 93af79f0 (+ 48) 80083546 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 93af7a20 (+ 228) 80084c68 :evaluate_debug_command + 0x0088 93af7b04 (+ 64) 80081986 :kernel_debugger_loop__Fv + 0x017a 93af7b44 (+ 48) 800825d1 :kernel_debugger + 0x010d 93af7b74 (+ 192) 800824b9 :panic + 0x0029 93af7c34 (+ 64) 800486d6 :new_vnode + 0x005a 93af7c74 (+ 64) 802d6d72 :New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a 93af7cb4 (+ 176) 802dd3f1 :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571 93af7d64 (+ 96) 802e78eb :bfs_create_dir__FPvT0PCciPx + 0x0107 93af7dc4 (+ 320) 8004ab0a :dir_create__FiPcib + 0x0082 93af7f04 (+ 64) 8004ff78 :_user_create_dir + 0x0094 93af7f44 (+ 100) 80092652 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x93af7fa8 (end = 0x93af8000) eax 0x50 ebx 0x458bc8 ecx 0x7ffe6734 edx 0xffff0104 esi 0x0 edi 0x19754e08 ebp 0x7ffe6760 esp 0x93af7fdc eip 0xffff0104 eflags 0x206 vector: 0x63, error code: 0x0 93af7fa8 (+ 0) ffff0104 7ffe6760 (+ 48) 0032691f :unknown + 0xf91f 7ffe6790 (+ 144) 002c8516 :unknown + 0xd516 7ffe6820 (+ 64) 002c861b :unknown + 0xd61b 7ffe6860 (+ 64) 0024fd35 :unknown + 0x1ad35 7ffe68a0 (+ 48) 0024d45f :unknown + 0x1845f 7ffe68d0 (+ 176) 0024dd6d :unknown + 0x18d6d 7ffe6980 (+ 64) 002b4bc5 :unknown + 0x1bc5 7ffe69c0 (+ 96) 00299f78 :unknown + 0x7f78 7ffe6a20 (+ 112) 0029ab5a :unknown + 0x8b5a 7ffe6a90 (+ 80) 00299126 :unknown + 0x7126 7ffe6ae0 (+ 64) 00295466 :unknown + 0x3466 7ffe6b20 (+ 176) 0023a1dc :unknown + 0x51dc 7ffe6bd0 (+ 160) 00230426 :unknown + 0x18426 7ffe6c70 (+ 64) 002304f3 :unknown + 0x184f3 7ffe6cb0 (+ 80) 0020c9b1 :unknown + 0xc9b1 7ffe6d00 (+ 640) 002091fc :unknown + 0x91fc 7ffe6f80 (+ 44) 00204c45 :unknown + 0x4c45 7ffe6fac (+ 48) 001007ca 3453:runtime_loader_seg0ro at 0x00100000 + 0x7ca 7ffe6fdc (+ 0) 7ffe6fec 3452:svn_main_stack at 0x7efe7000 + 0xffffec kdebug> vnode 0x90c1b300 VNODE: 0x90c1b300 device: -858993460 id: 0 ref_count: 78233 private_node: 0x00000000 mount: 0x3bbe0ad9 covered_by: 0x00000001 cache: 0xffffffff flags: --- advisory_lock: 0x00000000 kdebug> kdebug> mount  s address id root covers cookie fs_name 0x908ade00 1 0x908ade40 0x00000000 0x90861980 rootfs 0x908ade80 2 0x908adf00 0x908adec0 0x908619c0 devfs 0x908adf40 3 0x908adfc0 0x908adf80 0x908c4a50 pipefs 0x908e2540 4 0x908e2600 0x908e2580 0x908f1000 bfs 0x90b17880 5 0x90b17940 0x90b178c0 0x909d0c00 bfs kdebug> mount 5 MOUNT: 0x90b17880 id: 5 device_name: /dev/disk/ata/0/slave/raw fs_name: bfs cookie: 0x909d0c00 root_vnode: 0x90b17940 covers_vnode: 0x90b178c0 partition: 0x908e9600 lock: 4807 flags: kdebug> }}} -- Comment(by mmlr): Closed #2518 as a duplicate of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 19:40:05 2008 From: trac at haiku-os.org (stippi) Date: Sat, 12 Jul 2008 17:40:05 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.2fdf0a415a6aa429e2e19c4b8773eb10@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): I am getting a similar error as long as I have the reiserfs add-on installed. But I am getting reiserfs related output in the Terminal when I try to init a partition. When I remove the reiserfs add-on, I can init the partition. However, your output looks different. We may work on partitioning in the next weeks. It doesn't really matter if the problem is in DriveSetup (probably not) or somewhere closer to the kernel and it's add-ons. It's just a bug that we need to fix. As long as it is reproducible, it should be relatively quick to find. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 19:44:53 2008 From: trac at haiku-os.org (stippi) Date: Sat, 12 Jul 2008 17:44:53 -0000 Subject: [Haiku-bugs] [Haiku] #2331: [MediaPlayer] sometimes starts with corrupted interface In-Reply-To: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> References: <040.13a8766c4f58d35f5d404fd344e6ab53@haiku-os.org> Message-ID: <049.b9b331cdd42f19d972b9f54af65605d1@haiku-os.org> #2331: [MediaPlayer] sometimes starts with corrupted interface ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by stippi): Yes, this is a different bug. The video view is sometimes still visible even though there is no video. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 19:50:38 2008 From: trac at haiku-os.org (stippi) Date: Sat, 12 Jul 2008 17:50:38 -0000 Subject: [Haiku-bugs] [Haiku] #2436: [MediaPlayer] don't need zoom button in info window (easy) In-Reply-To: <040.a75b93392c6e5639b354b323faeaa92c@haiku-os.org> References: <040.a75b93392c6e5639b354b323faeaa92c@haiku-os.org> Message-ID: <049.1ba88e6171d1a761edd55c462b03c8ce@haiku-os.org> #2436: [MediaPlayer] don't need zoom button in info window (easy) ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r26394. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 21:02:10 2008 From: trac at haiku-os.org (stippi) Date: Sat, 12 Jul 2008 19:02:10 -0000 Subject: [Haiku-bugs] [Haiku] #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect In-Reply-To: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> References: <041.40d78fe0f2827f2b08aad56db2e97923@haiku-os.org> Message-ID: <050.2324c48c44aeaae7ff9ec90507c796dd@haiku-os.org> #2509: Unarchived BTextControl's _BTextInput_ has a bad text rect ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): I don't understand the change to TextControl.cpp at all. As for the change to TextInput.cpp, I am not sure yet - it should be investigated why LineHeight(0) fails for the case when the control is unarchived. The patch looks like a workaround, not like the fix to the real problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 21:19:57 2008 From: trac at haiku-os.org (scottmc) Date: Sat, 12 Jul 2008 19:19:57 -0000 Subject: [Haiku-bugs] [Haiku] #2322: [Zip-O-Matic] don't need zoom button (easy) In-Reply-To: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> References: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> Message-ID: <049.712b4effbfc82bf6bf186f9ab15115f6@haiku-os.org> #2322: [Zip-O-Matic] don't need zoom button (easy) ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by scottmc): I would assume the patch i just posted will fix this, or it was ok as it was and this ticket should then just be closed as invalid. Note that the zipomatic windows defaults to be wider with this fix than without it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 12 21:40:25 2008 From: trac at haiku-os.org (stippi) Date: Sat, 12 Jul 2008 19:40:25 -0000 Subject: [Haiku-bugs] [Haiku] #2322: [Zip-O-Matic] don't need zoom button (easy) In-Reply-To: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> References: <040.bacad3ec1c27d9077e44b3111fcea32e@haiku-os.org> Message-ID: <049.356b06a7b11c0719856fd0d35ce1bb4b@haiku-os.org> #2322: [Zip-O-Matic] don't need zoom button (easy) ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by stippi): I just looked at the ZipOMaticWindow.cpp - it has special support for zooming and should "fit to size". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 00:28:41 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 12 Jul 2008 22:28:41 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.16b3b2de19aa134a3d310b9c8eb7d0f9@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Should be fixed in r26397. Please verify. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 00:56:03 2008 From: trac at haiku-os.org (cebif) Date: Sat, 12 Jul 2008 22:56:03 -0000 Subject: [Haiku-bugs] [Haiku] #1550: Tracker crashes when clicking on column heading in Mail inbox folder In-Reply-To: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> References: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> Message-ID: <049.4d33e3cafb030f811db1d751ab39f221@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 Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by cebif): I am no able to reproduce anymore either in r26181. The bug seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 09:55:58 2008 From: trac at haiku-os.org (kaliber) Date: Sun, 13 Jul 2008 07:55:58 -0000 Subject: [Haiku-bugs] [Haiku] #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes Message-ID: <042.049c3dcb127418abcb089c84f77dedd2@haiku-os.org> #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- On linux I am copying additional files to the haiku.image from late-image- script. I got error: {{{ cp -r generated/tmp/root/common /myfs/ could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes cp -r generated/tmp/root/home /myfs/ Error: Failed to open connection to FS shell: Connection refused ./build/scripts/late-image-script.sh: line 56: 28328 Segmentation fault $bfsShell -n $imageOffsetFlags "$imagePath" > /dev/null cp -r generated/tmp/root/var /myfs/ Error: Failed to open connection to FS shell: Connection refused }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 10:04:34 2008 From: trac at haiku-os.org (stippi) Date: Sun, 13 Jul 2008 08:04:34 -0000 Subject: [Haiku-bugs] [Haiku] #1550: Tracker crashes when clicking on column heading in Mail inbox folder In-Reply-To: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> References: <040.a10d9b5f0d2affec7076ac10d85c1beb@haiku-os.org> Message-ID: <049.154c623967bd75a70c7c8238cd04b920@haiku-os.org> #1550: Tracker crashes when clicking on column heading in Mail inbox folder -----------------------------------+---------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Probably fixed by fixes to the list class? Well... if it was reproducible every time, we can probably close it without mixed feelings... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 13:17:21 2008 From: trac at haiku-os.org (julun) Date: Sun, 13 Jul 2008 11:17:21 -0000 Subject: [Haiku-bugs] [Haiku] #2378: Print in PDF - Look & Feel issues In-Reply-To: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> References: <045.54459fb3785a385322f58ddaeaca1bac@haiku-os.org> Message-ID: <054.37c62a3b621753e91c7c24a1c10ea94b@haiku-os.org> #2378: Print in PDF - Look & Feel issues -------------------------+-------------------------------------------------- Reporter: un_spacyar | Owner: julun Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------+-------------------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed Comment: fixed in r26398 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 13:37:41 2008 From: trac at haiku-os.org (El-Al) Date: Sun, 13 Jul 2008 11:37:41 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.8ac251f9f2b9e1a91fe035e6966641c1@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) ------------------------+--------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by El-Al): Replying to [comment:6 El-Al]: > A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post. > > Even tried installing to an IDE drive as opposed to SATA. Same problem occurs. I guess the driver overhaul hasn't caused this problem at all. I'm stumped! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 16:33:25 2008 From: trac at haiku-os.org (julun) Date: Sun, 13 Jul 2008 14:33:25 -0000 Subject: [Haiku-bugs] [Haiku] #2351: Tracker crashing: va 0x14 not covered by area in address space In-Reply-To: <040.f136b3ca59c17ef606426ba56099bf0b@haiku-os.org> References: <040.f136b3ca59c17ef606426ba56099bf0b@haiku-os.org> Message-ID: <049.df5096fbd03b8216daecb963a217553c@haiku-os.org> #2351: Tracker crashing: va 0x14 not covered by area in address space ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed Comment: I'm going to close this one, it seems to be fixed with r26383.[[BR]] I tested with and without the patch on gcc 4 and the crash does not show up if the patch is applied. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 17:29:18 2008 From: trac at haiku-os.org (meanwhile) Date: Sun, 13 Jul 2008 15:29:18 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.0bae12b84d34374586ed9496677e0254@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Tried it from r26397 (see attachment) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 19:13:35 2008 From: trac at haiku-os.org (axeld) Date: Sun, 13 Jul 2008 17:13:35 -0000 Subject: [Haiku-bugs] [Haiku] #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading In-Reply-To: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> References: <040.4fc59b247a2bc06848cc8948b4f14a9a@haiku-os.org> Message-ID: <049.edc94b33fc3b2103e9dd720b8d9acadb@haiku-os.org> #2519: Uninterruptible power supply beeps on Haiku boot or Haiku applications loading --------------------------+------------------------------------------------- Reporter: cebif | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by axeld): The boot loader currently also spits out some debug info over the serial line. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 22:32:59 2008 From: trac at haiku-os.org (bbjimmy) Date: Sun, 13 Jul 2008 20:32:59 -0000 Subject: [Haiku-bugs] [Haiku] #1797: Possible block cache memory leak In-Reply-To: <044.ebaa1714126e859e0630a40a89decc83@haiku-os.org> References: <044.ebaa1714126e859e0630a40a89decc83@haiku-os.org> Message-ID: <053.70eaacbae2fdc0b68f8d8f31fbf70b33@haiku-os.org> #1797: Possible block cache memory leak ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bbjimmy): Replying to [comment:1 axeld]: > The ultimate check would be to have done these things on a different volume than the boot volume, and then unmount it. Unless there is any memory pressure, the block cache will not free up any memory. I am sure I am looking at the same issue. Performing: jam -q ...patience... ...patience... ...patience... ...found 67858 target(s)... ...updating 6981 target(s)... InitScript1 generated/haiku.image-init-vars vfork: Out of memory running r26389 I have only 448 MB of ram. I performed the jam on an svn checkout that resides on a different partition. Before the jam, 19% was used. The memory used peaked at 89% After the jam error, there was 49% still used ... mostly in System Resources & Cashes according to the ProcessController app. After dismounting the volume that contained the haiku source tree, I was back to 19% used. It seems that the issue is not a memory leak, but there is still an issue. This same computer can jam the haiku image from two trees at the same time using Ubuntu Linux, but I am unable to build Haiku within Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 22:52:58 2008 From: trac at haiku-os.org (anevilyak) Date: Sun, 13 Jul 2008 20:52:58 -0000 Subject: [Haiku-bugs] [Haiku] #1797: Possible block cache memory leak In-Reply-To: <044.ebaa1714126e859e0630a40a89decc83@haiku-os.org> References: <044.ebaa1714126e859e0630a40a89decc83@haiku-os.org> Message-ID: <053.7a8775a4e2a7f677a07e3c52cbc892ca@haiku-os.org> #1797: Possible block cache memory leak ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate Comment: This in fact a duplicate of 2046, on which much more information can be found. Closing this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 13 23:01:56 2008 From: trac at haiku-os.org (julun) Date: Sun, 13 Jul 2008 21:01:56 -0000 Subject: [Haiku-bugs] [Haiku] #1987: BeTask Manager - four problems In-Reply-To: <041.42ce7f7fc451eff37425955e6469652b@haiku-os.org> References: <041.42ce7f7fc451eff37425955e6469652b@haiku-os.org> Message-ID: <050.c1767bf6cedfa1d20f97a08c40e64b7a@haiku-os.org> #1987: BeTask Manager - four problems ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by julun): * status: new => closed * resolution: => fixed Comment: Hi, most of the problems are fixed already, the only remaining part is nr. 2. This seems not so easy to fix, i had a look into the implementation of TaskManager and it turns out to be a problem of our app_server implementation. Asking for window_info seems somehow depend on a window order in R5, whereas we have a kind of unordered list which will in this case return the Tracker Desktop window first. So the check performed in TaskManager will always succeed for the first window. Part 3 should be fixed with r26406, but i can't tell about the others. I'm going to close this task and reopen a new one with more specific info about the xkill - app_server relationship. Regards, Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 03:25:33 2008 From: trac at haiku-os.org (bbjimmy) Date: Mon, 14 Jul 2008 01:25:33 -0000 Subject: [Haiku-bugs] [Haiku] #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory In-Reply-To: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> References: <043.1cfb30e72db22561a05514d8f15e3964@haiku-os.org> Message-ID: <052.5841ccab96dc7a975d553d0813ee75a7@haiku-os.org> #2046: jam on haiku-host occasionally fails with the message: vfork: Out of memory ----------------------------+----------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bbjimmy): * cc: black.belt.jimmy at gmail.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 08:45:14 2008 From: trac at haiku-os.org (mauricek) Date: Mon, 14 Jul 2008 06:45:14 -0000 Subject: [Haiku-bugs] [Haiku] #1275: Playing aiff type sounds locks up system In-Reply-To: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> References: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> Message-ID: <049.7d395e2dcf59e262f3d5a1aa0a4473b6@haiku-os.org> #1275: Playing aiff type sounds locks up system -----------------------------+---------------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by mauricek): * cc: haiku at kaldience.com (added) Comment: Is this still reproducable? While I was trying to verify this some weeks ago, I was not able to do so. Could you by chance provide a file which forces this behavior? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 10:24:19 2008 From: trac at haiku-os.org (axeld) Date: Mon, 14 Jul 2008 08:24:19 -0000 Subject: [Haiku-bugs] [Haiku] #1097: ext3 filesystem add-on In-Reply-To: <041.be904ddc11b0505699feebe5277517d7@haiku-os.org> References: <041.be904ddc11b0505699feebe5277517d7@haiku-os.org> Message-ID: <050.a223501079fe2ac19af3021e61a8440b@haiku-os.org> #1097: ext3 filesystem add-on --------------------------------+------------------------------------------- Reporter: ekdahl | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/ext2 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: File Systems => File Systems/ext2 Comment: A cleanly mounted ext3 volume is compatible with ext2. Ext4's file extents will need some adaption, but for now, it works nicely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 12:12:48 2008 From: trac at haiku-os.org (cebif) Date: Mon, 14 Jul 2008 10:12:48 -0000 Subject: [Haiku-bugs] [Haiku] #2352: Keybooard and mouse freeze after hot-plugging USB camera In-Reply-To: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> References: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> Message-ID: <049.7708270fcfb9510bb478cd55ff21bd51@haiku-os.org> #2352: Keybooard and mouse freeze after hot-plugging USB camera --------------------------+------------------------------------------------- Reporter: cebif | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by cebif): After testing in r26181 there is no more problem hot plugging the camera into USB port. I can also mount it and access photos. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 14:33:33 2008 From: trac at haiku-os.org (mt) Date: Mon, 14 Jul 2008 12:33:33 -0000 Subject: [Haiku-bugs] [Haiku] #2521: ProcessController can't be installed in the deskbar. (gcc4 haiku) Message-ID: <037.cf39780e5d04f8660d84109da8db867c@haiku-os.org> #2521: ProcessController can't be installed in the deskbar. (gcc4 haiku) --------------------------+------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- R26407 (build by gcc4) can't install ProcessController in the deskbar at boot time. (Perhaps it have been occurred older revision.) syslog says: {{{ USER: instantiate_object failed: Failed to find exported Instantiate static function for class P. USER: instantiate_object failed: Failed to find exported Instantiate static function for class M. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 14 19:37:38 2008 From: trac at haiku-os.org (axeld) Date: Mon, 14 Jul 2008 17:37:38 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.71bf93981d423e1c88cc33a6a43ee8a4@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26409. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 00:15:23 2008 From: trac at haiku-os.org (cebif) Date: Mon, 14 Jul 2008 22:15:23 -0000 Subject: [Haiku-bugs] [Haiku] #1275: Playing aiff type sounds locks up system In-Reply-To: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> References: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> Message-ID: <049.0594d5ab1a71dbfd28a146d70dc11004@haiku-os.org> #1275: Playing aiff type sounds locks up system -----------------------------+---------------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by cebif): This is still a problem playing aiff sounds with the Preferences, Sounds app and MediaPlayer. If I play them with VLC there is no problem. Also I am finding the mouse pointer locking up from the start now, when a aiff sound finishes playing. I will upload one of the aiff sound files. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 02:03:00 2008 From: trac at haiku-os.org (bga) Date: Tue, 15 Jul 2008 00:03:00 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.ef871b4902ffe33b01cbfd588c3e23c3@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Changes (by bga): * status: closed => reopened * resolution: fixed => Comment: Maybe it is not exactly the same problem but the memory graphs still look wrong. They are stuck at the 0 position (although currently there is 378.9 Mb used with 190.6 mb of cached memory. The graphic didn?t change even once since boot. staying flat at position 0. So, reopening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 02:30:00 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 15 Jul 2008 00:30:00 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.c4826a18fe62937dbe2cf23a5c553846@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Comment(by anevilyak): Are you sure you rebuilt your stuff properly? It works fine over here, watching the cache / mem graphs steadily increase during an SVN checkout. How much RAM is on the box you're trying this with? mine's 1GB. Also, is the mem graph the only one you see issues with? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 14:24:20 2008 From: trac at haiku-os.org (bga) Date: Tue, 15 Jul 2008 12:24:20 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.de7652fbab2fab7bd44bc58ab7b4f1ad@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Comment(by bga): Yes, I am. Tried at home with a Intel Core 2 Quad Extreme and 4 Gb of memory (around 3.5 detected by Haiku). Tried again here at work under VMWare with a full build (erased the generated directory). Configured with 2 Gb of RAM and one virtual CPU. Started a svn checkou and with around 20% of the memory used, the graph was still at position 0 (see new screen capture). I only have this problem with the memory monitors. Others work but I just noticed that in the CPU monitor, the graph keeps changing. From one redraw to another, peaks and valleys disappear and reappear again, which is kinda odd. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 15:13:08 2008 From: trac at haiku-os.org (bga) Date: Tue, 15 Jul 2008 13:13:08 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.3c5ffc74b81791e9f998cce017d3d053@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Comment(by bga): So if I change the memory amount in VMWare to 1 Gb, it works as expected. I guess there is a signed int overflow somewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 15:53:58 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 15 Jul 2008 13:53:58 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode Message-ID: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> #2522: KDL - invalid opcode -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This happened with r26404, but I've seen it happen with a couple different images build in the past week or so. Usually happens sometime during a ./configure, sometimes when checking assert.h, sometimes when finding the max commandline length. Attached are screenshots from a couple different crashes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 18:00:33 2008 From: trac at haiku-os.org (axeld) Date: Tue, 15 Jul 2008 16:00:33 -0000 Subject: [Haiku-bugs] [Haiku] #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. In-Reply-To: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> References: <038.f2747008e213280136a7fc295af0a269@haiku-os.org> Message-ID: <047.e1c462474ee168de05014b02aaa9c61a@haiku-os.org> #2140: ActivityMonitor shows graphics at the 0 position for positions close to the current one. -------------------------------------------+-------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: That's a different bug that should have always appeared with more than 2 GB of memory. Anyway it's fixed in r26430. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 15 18:10:10 2008 From: trac at haiku-os.org (nielx) Date: Tue, 15 Jul 2008 16:10:10 -0000 Subject: [Haiku-bugs] [Haiku] #2456: bugs.haiku-os.org doesn't work anymore In-Reply-To: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> References: <045.86f88dc879182a5647ab21a6ced7babf@haiku-os.org> Message-ID: <054.9aade5fde057c92326bada3dafd7e462@haiku-os.org> #2456: bugs.haiku-os.org doesn't work anymore -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: nielx Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------+-------------------------------------------------- Comment(by nielx): No, it does not work correctly yet. Apache should rewrite the URL's to dev .haiku-os.org: now it uses the bugs.haiku-os.org urls as proper trac urls, which is not something I want. Will wait until after my vacation though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 16 00:55:42 2008 From: trac at haiku-os.org (cebif) Date: Tue, 15 Jul 2008 22:55:42 -0000 Subject: [Haiku-bugs] [Haiku] #1275: Playing aiff type sounds locks up system In-Reply-To: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> References: <040.472b2f6bf17cd1714c15ffa720db257c@haiku-os.org> Message-ID: <049.1962ae8c871d45f16156b56bd83ebe1f@haiku-os.org> #1275: Playing aiff type sounds locks up system -----------------------------+---------------------------------------------- Reporter: cebif | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by cebif): I was testing with r26181 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 16 05:19:54 2008 From: trac at haiku-os.org (umccullough) Date: Wed, 16 Jul 2008 03:19:54 -0000 Subject: [Haiku-bugs] [Haiku] #973: [Tracker] crash on quit via ProcessController In-Reply-To: <040.8cd3a8bfe8ecab10c7e88525c12c1842@haiku-os.org> References: <040.8cd3a8bfe8ecab10c7e88525c12c1842@haiku-os.org> Message-ID: <049.13ae290853888a4f03afa67d46fed93c@haiku-os.org> #973: [Tracker] crash on quit via ProcessController -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by umccullough): FWIW, the gcc4 Tracker crash on quit issue I was having before seems to be gone since r26383 now. Since this bug is still closed, this is just for information only. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 16 08:37:51 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 16 Jul 2008 06:37:51 -0000 Subject: [Haiku-bugs] [Haiku] #2523: Invalid Argument while trying to configure and/or make packages in Haiku Message-ID: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> #2523: Invalid Argument while trying to configure and/or make packages in Haiku -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I've bee running into this one quite a bit in the past week or so. Attached are a couple screenshots. Not sure if this is related to the invalid opcode issue or if this is something else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 03:03:27 2008 From: trac at haiku-os.org (stippi) Date: Thu, 17 Jul 2008 01:03:27 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.aa329753dee23c20d53e68f3c478009e@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): Please try again with r26465, DriveSetup could be confused in various ways. The preparation for modifications would then fail before initializing a partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 18:28:44 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 17 Jul 2008 16:28:44 -0000 Subject: [Haiku-bugs] [Haiku] #2494: [bfs] corruption after downloading two 700mb files from ftp In-Reply-To: <040.48ec56f52b6a91da2d577b5bbe645f42@haiku-os.org> References: <040.48ec56f52b6a91da2d577b5bbe645f42@haiku-os.org> Message-ID: <049.ac44c70860564e2537cc4546589fa7e1@haiku-os.org> #2494: [bfs] corruption after downloading two 700mb files from ftp -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by emitrax): What's the size of your haiku partition? Did you manage to reboot Haiku? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 18:50:45 2008 From: trac at haiku-os.org (diver) Date: Thu, 17 Jul 2008 16:50:45 -0000 Subject: [Haiku-bugs] [Haiku] #2494: [bfs] corruption after downloading two 700mb files from ftp In-Reply-To: <040.48ec56f52b6a91da2d577b5bbe645f42@haiku-os.org> References: <040.48ec56f52b6a91da2d577b5bbe645f42@haiku-os.org> Message-ID: <049.796ad46090613bcdafd27231f8313e5c@haiku-os.org> #2494: [bfs] corruption after downloading two 700mb files from ftp -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by diver): It's 2,9Gb. I think I didn't tried to reboot after this issue, I just reinitialized it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 19:13:13 2008 From: trac at haiku-os.org (korli) Date: Thu, 17 Jul 2008 17:13:13 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.91c5178e0ec0ace536e42af9ad43b351@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by korli): is this bug still valid ? (just asking) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 20:29:31 2008 From: trac at haiku-os.org (kaliber) Date: Thu, 17 Jul 2008 18:29:31 -0000 Subject: [Haiku-bugs] [Haiku] #2524: dlopen cannot find system libraries Message-ID: <042.cdc349c967c2a7d7856ecdfb29131a33@haiku-os.org> #2524: dlopen cannot find system libraries -----------------------------------+---------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- dlopen() searches for libraries only in add-ons directories. I think it should also search in system directories like /boot/common/lib etc. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 20:30:48 2008 From: trac at haiku-os.org (idefix) Date: Thu, 17 Jul 2008 18:30:48 -0000 Subject: [Haiku-bugs] [Haiku] #2525: Black background with HVIF icons Message-ID: <041.c4970fbe2f4bc8d70135ed28ac4055f6@haiku-os.org> #2525: Black background with HVIF icons -----------------------+---------------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- In some places HVIF icons show a black background when it should be transparent. See attached screenshots. This is on r26452 with 16 bit colour space. (The drop-down boxes doesn't work in NetSurf, so I can't select the right component.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 20:53:51 2008 From: trac at haiku-os.org (idefix) Date: Thu, 17 Jul 2008 18:53:51 -0000 Subject: [Haiku-bugs] [Haiku] #2525: Black background with HVIF icons In-Reply-To: <041.c4970fbe2f4bc8d70135ed28ac4055f6@haiku-os.org> References: <041.c4970fbe2f4bc8d70135ed28ac4055f6@haiku-os.org> Message-ID: <050.e97f278c0fad38867bf158611de9a225@haiku-os.org> #2525: Black background with HVIF icons -----------------------------+---------------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by idefix): * owner: axeld => stippi * component: - General => User Interface -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 21:33:38 2008 From: trac at haiku-os.org (mmlr) Date: Thu, 17 Jul 2008 19:33:38 -0000 Subject: [Haiku-bugs] [Haiku] #2525: Black background with HVIF icons In-Reply-To: <041.c4970fbe2f4bc8d70135ed28ac4055f6@haiku-os.org> References: <041.c4970fbe2f4bc8d70135ed28ac4055f6@haiku-os.org> Message-ID: <050.1eb5e292b9c6283184a931f241657fb4@haiku-os.org> #2525: Black background with HVIF icons -----------------------------+---------------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Fixed in r26474. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 21:56:53 2008 From: trac at haiku-os.org (euan) Date: Thu, 17 Jul 2008 19:56:53 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.f40dc7846b5d08b2dfa1488eae2ddfed@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by euan): as the original reporter I believe this bug is generally resolved for the majority of systems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 17 23:07:55 2008 From: trac at haiku-os.org (idefix) Date: Thu, 17 Jul 2008 21:07:55 -0000 Subject: [Haiku-bugs] [Haiku] #2526: Mouse preference window vertically compressed Message-ID: <041.7626d7f1b2da228b1bd93de62666776a@haiku-os.org> #2526: Mouse preference window vertically compressed -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- See screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 01:17:20 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 17 Jul 2008 23:17:20 -0000 Subject: [Haiku-bugs] [Haiku] #2527: PANIC: vm_page_fault: unhandled page fault in kernel space at 0x1001004, ip 0x8004fafb Message-ID: <044.09dcb199e85b7f2328bd68e6916dc739@haiku-os.org> #2527: PANIC: vm_page_fault: unhandled page fault in kernel space at 0x1001004, ip 0x8004fafb -------------------------+-------------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/TTY | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- I went to open a file in vim, and then hit page down, and was greeted by the KDL in the subject line. Backtrace is as follows {{{ kernel_debugger_stuff :panic + 0x0029 :vm_page_fault + 0x00b1 :page_fault_exception + 0x00b1 :int_bottom + 0x0036 (nearest) iframe at 0xa11efb9c (end = 0xa11efbf4) eax 0x1001000 ebx 09x13d1040 ecx 0x0 edx 0x913d1040 esi 0x1 edi 0x80992060 ebp 0xa11efc04 esp 0xa11efbd0 eip 0x8004fafb eflags 0x10206 vector: 0xe, error code: 0x0 :notify_select_events + 0x001b :notify_select_event + 0x0027 :notify_select_event_pool + 0x005c :tty_notify_select_event__FP3ttyUc + 0x0031 :tty_notify_if_available__FP3ttyT0b + 0x0085 :_._12ReaderLocker + 0x0069 :tty_input_read__FP10tty_cookiePvPUl + 0x04cc :slave_read__FPvxT0Pul + 0x0027 :devfs_read__FP9fs_volumeP8fs_vnodePvxT2PUl + 0x017b :file_read__FP15file_descriptorxPVPul + 0x0044 :common_user_io__FixPvUlb + 0x017d :_user_read + 0x0028 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0xa11effa8 (end = 0xa11f0000) eax 0x7c ebx 0x633e48 ecx 0x70080f40 edx 0xffff0104 esi 0x343cb8 edi 0x0 ebp 0x70080f7c esp 0xa11effdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 25 a11effa8 (+ 0) ffff0104 26 70080f7c (+48) 00318fa0 <_APP_>:OpenPTY + 0x01a0 (nearest) 27 70080fac (+48) 005abac0 :_get_next_team_info + 0x005c (nearest) 28 70080fdc (+ 0) 70080fec 122723:vim_async_read_4651_stack at 0x70041000 + 0x33fec }}} I'm not sure how easy this will be to replicate as I've used vim quite a bit and never seen this one before, but will let you know if I find a consistent way to duplicate it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 02:07:56 2008 From: trac at haiku-os.org (stippi) Date: Fri, 18 Jul 2008 00:07:56 -0000 Subject: [Haiku-bugs] [Haiku] #2526: Mouse preference window vertically compressed In-Reply-To: <041.7626d7f1b2da228b1bd93de62666776a@haiku-os.org> References: <041.7626d7f1b2da228b1bd93de62666776a@haiku-os.org> Message-ID: <050.9534fc132c699b29e02a9b210229b80c@haiku-os.org> #2526: Mouse preference window vertically compressed --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for the note, fixed in r26479. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 03:54:29 2008 From: trac at haiku-os.org (stippi) Date: Fri, 18 Jul 2008 01:54:29 -0000 Subject: [Haiku-bugs] [Haiku] #2480: DriveSetup Partition names are out of Sync. In-Reply-To: <042.aba42e5535725ea887e019bfdd0c4939@haiku-os.org> References: <042.aba42e5535725ea887e019bfdd0c4939@haiku-os.org> Message-ID: <051.53f920c300fb196067721d30306cf724@haiku-os.org> #2480: DriveSetup Partition names are out of Sync. --------------------------------------+------------------------------------- Reporter: Bouncer | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r26465. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 12:34:48 2008 From: trac at haiku-os.org (tqh) Date: Fri, 18 Jul 2008 10:34:48 -0000 Subject: [Haiku-bugs] [Haiku] #1727: Haiku panics with vm_page fault/double fault after 20-30s usage In-Reply-To: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> References: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> Message-ID: <047.69c39a2a9065a110dbffa37fca8ea236@haiku-os.org> #1727: Haiku panics with vm_page fault/double fault after 20-30s usage ----------------------------+----------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by tqh): This seems to be fixed here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 14:36:36 2008 From: trac at haiku-os.org (meanwhile) Date: Fri, 18 Jul 2008 12:36:36 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.857a76274e7d42f04d7629a59a8fb508@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Added attachment with the results from r26477. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 14:57:14 2008 From: trac at haiku-os.org (stippi) Date: Fri, 18 Jul 2008 12:57:14 -0000 Subject: [Haiku-bugs] [Haiku] #2470: DriveSetup error preparing disk In-Reply-To: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> References: <044.9b2151f6213841ef86cc77e910c35f81@haiku-os.org> Message-ID: <053.0bc587f24134800fa1ac30db20b51a95@haiku-os.org> #2470: DriveSetup error preparing disk ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): This looks more like a problem in the disk device manager from the output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 13:59:18 2008 From: trac at haiku-os.org (marcusoverhagen) Date: Fri, 18 Jul 2008 11:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #2360: PS/2 keyboard and touchpad not working on cold boots In-Reply-To: <039.3e1478899be58b63dbf44ba1dcd5fe3c@haiku-os.org> References: <039.3e1478899be58b63dbf44ba1dcd5fe3c@haiku-os.org> Message-ID: <048.23a1038a7fb56bd3f9baee6fbceed27c@haiku-os.org> #2360: PS/2 keyboard and touchpad not working on cold boots -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by marcusoverhagen): * status: new => assigned Comment: I think there is a problem with the BIOS emulation of the PS2 controller. In case of cold boot, it doesn't seem to be in the correct state, and doesn't behave properly. cold boot logfile: {{{ 1308 KERN: ps2: active multiplexing not supported [...] 1352 KERN: ps2: ps2_dev_command wait for ack res 0x80000009, wait-time 4001009 1353 KERN: ps2: ps2_dev_command result 0x80000009 1354 KERN: ps2: reset mouse failed 1355 KERN: ps2: probe_mouse reset failed 1356 KERN: ps2: probing mouse input/mouse/ps2/0 failed }}} warm boot logfile: {{{ 1321 KERN: ps2: active multiplexing v1.1 enabled [...] 1362 KERN: ps2: ps2_dev_command wait for input res 0x00000000, wait- time 326018 1363 KERN: ps2: ps2_dev_command rx: 0xaa 1364 KERN: ps2: ps2_dev_command rx: 0x00 1365 KERN: ps2: ps2_dev_command result 0x00000000 1366 KERN: ps2: reset mouse success }}} Please attach a logfile of a cold boot without USB drivers and without any external USB devices or docking station attached. It's either a problem of USB legacy emulation not properly entering the "USB extrinsic support with keyboard controller" mode (see page 11 of the usb_le9 pdf), or the bios is expecting some PS2 commands (that we don't send yet) before it enters a functioning state. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 18 22:40:36 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 18 Jul 2008 20:40:36 -0000 Subject: [Haiku-bugs] [Haiku] #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision In-Reply-To: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> References: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> Message-ID: <048.cea944b1004ebfd11c83921d9e46e2c7@haiku-os.org> #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision ---------------------------------+------------------------------------------ Reporter: koki | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r24690. The cause was in fact a difference in behavior between R5 and Haiku, but this behavior isn't actually documented anywhere in the BeBook and was more something found by random curiosity at the time, so I'm not sure any other app relies on it. For the time being I've fixed it in Vision itself. To clarify: When Vision's ResizeView got a MouseMoved notification, it would ask its BWindow for the current message in the queue, so as to pass that on to whichever view was in fact the target of the resize, since different resize behavior is needed for the nick lists vs the window list. In BeOS r5 and 5.1, this would contain the BPoint for the MouseMoved in window- relative coordinates. In Haiku, it already appears to be pre-converted to the coordinate in the view's space, which needless to say was confusing Vision quite a bit. r24690 should pull an updated package that contains this fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 00:36:22 2008 From: trac at haiku-os.org (stippi) Date: Fri, 18 Jul 2008 22:36:22 -0000 Subject: [Haiku-bugs] [Haiku] #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision In-Reply-To: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> References: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> Message-ID: <048.03a00a2f2352f8229665ee2d21dbc34a@haiku-os.org> #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision ---------------------------------+------------------------------------------ Reporter: koki | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): I've also changed Haiku in r26491 to have BeOS compatible B_MOUSE_MOVED messages, as was intended by BWindow::_SanitizeMessage(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 01:45:34 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 18 Jul 2008 23:45:34 -0000 Subject: [Haiku-bugs] [Haiku] #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision In-Reply-To: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> References: <039.65ce4f04ce1470c4f5319da11ac0dff0@haiku-os.org> Message-ID: <048.a75942a8c41efa4e2370a162b7c1d061@haiku-os.org> #2460: Mouse doesn't follow split window divider when dragging it sideways in Vision ---------------------------------+------------------------------------------ Reporter: koki | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by anevilyak): Good catch! Here's hoping that fixes some other apps with odd mouse behavior. Reverted my Vision workarounds in r26493. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 09:55:39 2008 From: trac at haiku-os.org (umccullough) Date: Sat, 19 Jul 2008 07:55:39 -0000 Subject: [Haiku-bugs] [Haiku] #2078: Add stdio_ext.h header In-Reply-To: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> References: <043.3f57e3ce095a508ddfa4d0f69a6fe6eb@haiku-os.org> Message-ID: <052.19c480031809e108ecb4cdc40a1476d6@haiku-os.org> #2078: Add stdio_ext.h header --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by umccullough): I ran into the gettext issue and Begasus pointed me here, so I attached a patch that adds a basic stdio_ext.h. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 10:19:58 2008 From: trac at haiku-os.org (meanwhile) Date: Sat, 19 Jul 2008 08:19:58 -0000 Subject: [Haiku-bugs] [Haiku] #2528: Can't delete selected text from Terminal using Delete key Message-ID: <044.79e084ce142a22950aa6ca3aeb928451@haiku-os.org> #2528: Can't delete selected text from Terminal using Delete key -----------------------+---------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- After selecting either generated text or text written by self, trying to delete it -with the Delete key on my keyboard- fails. Tried with r26477 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 11:16:31 2008 From: trac at haiku-os.org (monni) Date: Sat, 19 Jul 2008 09:16:31 -0000 Subject: [Haiku-bugs] [Haiku] #2529: update-all doesn't trigger re-downloading optional packages Message-ID: <040.1af68ffe92518659c4a14cdeef282489@haiku-os.org> #2529: update-all doesn't trigger re-downloading optional packages --------------------------+------------------------------------------------- Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- When running "jam -q @image update-all" with r26482 or later it should re- download and unzip Vision. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 13:49:59 2008 From: trac at haiku-os.org (idefix) Date: Sat, 19 Jul 2008 11:49:59 -0000 Subject: [Haiku-bugs] [Haiku] #2530: Horizontal slider isn't extended to window anymore Message-ID: <041.79a9eb51d4db05cf1cdd753cf80d3bcb@haiku-os.org> #2530: Horizontal slider isn't extended to window anymore ----------------------------+----------------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Horizontal sliders used to extend to the entire window, but now they are much smaller. This causes alignment issues in various applications and even text becomes garbled, see attached screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 15:04:19 2008 From: trac at haiku-os.org (stippi) Date: Sat, 19 Jul 2008 13:04:19 -0000 Subject: [Haiku-bugs] [Haiku] #2530: Horizontal slider isn't extended to window anymore In-Reply-To: <041.79a9eb51d4db05cf1cdd753cf80d3bcb@haiku-os.org> References: <041.79a9eb51d4db05cf1cdd753cf80d3bcb@haiku-os.org> Message-ID: <050.4444719352badcbb5ace9a18b73f02ab@haiku-os.org> #2530: Horizontal slider isn't extended to window anymore -----------------------------+---------------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks a lot, fixed in r26502. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 16:00:58 2008 From: trac at haiku-os.org (bonefish) Date: Sat, 19 Jul 2008 14:00:58 -0000 Subject: [Haiku-bugs] [Haiku] #2528: Can't delete selected text from Terminal using Delete key In-Reply-To: <044.79e084ce142a22950aa6ca3aeb928451@haiku-os.org> References: <044.79e084ce142a22950aa6ca3aeb928451@haiku-os.org> Message-ID: <053.5496768333cfc29fef108882dbde8380@haiku-os.org> #2528: Can't delete selected text from Terminal using Delete key ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: A terminal isn't a text editor. This is the expected behavior. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 16:42:39 2008 From: trac at haiku-os.org (idefix) Date: Sat, 19 Jul 2008 14:42:39 -0000 Subject: [Haiku-bugs] [Haiku] #2531: DHCP changes IP every 5 minutes Message-ID: <041.1c8e63a7ba536400632bfe3ae7c29d16@haiku-os.org> #2531: DHCP changes IP every 5 minutes --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- When I connect my Haiku computer to my Windows XP computer (with Internet Connection Sharing enabled), Haiku gets a new IP-address every 5 minutes. BeOS R5 (on the Haiku computer) doesn't show this behaviour. The network card Haiku uses is a 3Com Etherlink XL 3C900B. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 16:49:38 2008 From: trac at haiku-os.org (idefix) Date: Sat, 19 Jul 2008 14:49:38 -0000 Subject: [Haiku-bugs] [Haiku] #2531: DHCP changes IP every 5 minutes In-Reply-To: <041.1c8e63a7ba536400632bfe3ae7c29d16@haiku-os.org> References: <041.1c8e63a7ba536400632bfe3ae7c29d16@haiku-os.org> Message-ID: <050.177d6d3285adf91d6a0e8ef4bdf6647f@haiku-os.org> #2531: DHCP changes IP every 5 minutes ---------------------------------+------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by idefix): Normally this computer gets its IP from the ADSL-modem's DHCP-server, but it gives the same IP adddress every time. I still haven't found out how to get the modem to log DHCP requests... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 16:52:44 2008 From: trac at haiku-os.org (idefix) Date: Sat, 19 Jul 2008 14:52:44 -0000 Subject: [Haiku-bugs] [Haiku] #2531: DHCP changes IP address every 5 minutes (was: DHCP changes IP every 5 minutes) In-Reply-To: <041.1c8e63a7ba536400632bfe3ae7c29d16@haiku-os.org> References: <041.1c8e63a7ba536400632bfe3ae7c29d16@haiku-os.org> Message-ID: <050.75282adf07b0447d9400b0e91581f0b5@haiku-os.org> #2531: DHCP changes IP address every 5 minutes ---------------------------------+------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 19 17:51:29 2008 From: trac at haiku-os.org (meanwhile) Date: Sat, 19 Jul 2008 15:51:29 -0000 Subject: [Haiku-bugs] [Haiku] #2528: Can't delete selected text from Terminal using Delete key In-Reply-To: <044.79e084ce142a22950aa6ca3aeb928451@haiku-os.org> References: <044.79e084ce142a22950aa6ca3aeb928451@haiku-os.org> Message-ID: <053.d87aaee6e5d7ef01b689e61e5b70e969@haiku-os.org> #2528: Can't delete selected text from Terminal using Delete key ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by meanwhile): Oops, well...never too old to learn, I guess...Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 20 00:37:17 2008 From: trac at haiku-os.org (xspager) Date: Sat, 19 Jul 2008 22:37:17 -0000 Subject: [Haiku-bugs] [Haiku] #2532: Video/Audio on Dell Latitude LS :( Message-ID: <042.083503791c860b07774e8d36dacea3a0@haiku-os.org> #2532: Video/Audio on Dell Latitude LS :( ---------------------------------------+------------------------------------ Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------------------+------------------------------------ I just install Haiku on my laptop, an old Dell Latitude LS, it even works well, but i can see a black stripe on the screen, and when i play anything, this stripe get a lot of colors, each pixel one color :| that changes over the time, and only when playing a audio file. Note that when the workspace color appears on the screen i don`t see the constant black stripe, it just shows later on boot process. Note too, that this machine works well on the FreeBSD, sound and video, but i`m not right about the sound on Linux(Ubuntu), the video behaves strangely sometimes, but is well most of time. I belive that this problem is relative to the strange NeoMagic chips, in this machine they are, NM2200 [ MagicMedia 256AV Audio ], [ MagicGraph 256AV ] (Video). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 20 00:45:04 2008 From: trac at haiku-os.org (xspager) Date: Sat, 19 Jul 2008 22:45:04 -0000 Subject: [Haiku-bugs] [Haiku] #2532: Video/Audio on Dell Latitude LS :( In-Reply-To: <042.083503791c860b07774e8d36dacea3a0@haiku-os.org> References: <042.083503791c860b07774e8d36dacea3a0@haiku-os.org> Message-ID: <051.688a6cae822796b81f5e84a3f2bbda1f@haiku-os.org> #2532: Video/Audio on Dell Latitude LS :( ----------------------------------------+----------------------------------- Reporter: xspager | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ----------------------------------------+----------------------------------- Comment(by xspager): When i play sound on my machine it make a strange noise on the speaker too, at the same time the strange thin black stripe gets a lot o colors on it`s pixels. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 21 12:54:34 2008 From: trac at haiku-os.org (axeld) Date: Mon, 21 Jul 2008 10:54:34 -0000 Subject: [Haiku-bugs] [Haiku] #2075: BMessageFilter handles BView's B_MOUSE_DOWN in BWindow coordinate In-Reply-To: <041.1b66d8aca1d0db00e5bf6cb28178382f@haiku-os.org> References: <041.1b66d8aca1d0db00e5bf6cb28178382f@haiku-os.org> Message-ID: <050.2d36ea3e79808cd97b3280595fb31119@haiku-os.org> #2075: BMessageFilter handles BView's B_MOUSE_DOWN in BWindow coordinate ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 21 12:54:12 2008 From: trac at haiku-os.org (axeld) Date: Mon, 21 Jul 2008 10:54:12 -0000 Subject: [Haiku-bugs] [Haiku] #2075: BMessageFilter handles BView's B_MOUSE_DOWN in BWindow coordinate In-Reply-To: <041.1b66d8aca1d0db00e5bf6cb28178382f@haiku-os.org> References: <041.1b66d8aca1d0db00e5bf6cb28178382f@haiku-os.org> Message-ID: <050.24328a22495658c357501f6f80508f0c@haiku-os.org> #2075: BMessageFilter handles BView's B_MOUSE_DOWN in BWindow coordinate ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: closed => reopened * resolution: fixed => Comment: This change has been reverted in r26491 - "where" always only contains window coordinates, also in BeOS. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 21 14:26:04 2008 From: trac at haiku-os.org (stippi) Date: Mon, 21 Jul 2008 12:26:04 -0000 Subject: [Haiku-bugs] [Haiku] #1732: autodetecting resolution does not work for some grafix boards In-Reply-To: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> References: <041.f80704f6eca5f056dca0e5ca1f18a602@haiku-os.org> Message-ID: <050.d5437270738b3b575330ee023328e203@haiku-os.org> #1732: autodetecting resolution does not work for some grafix boards ---------------------------------+------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: I have found the problem in the Radeon driver. Because it depends on which link you chose to plug in your screen, it also explains why it worked for Marcus and not for me. The repeated screen contents on the right side are an effect of how the Radeon driver handles non-native resolutions. It drives the screen at its native resolution, I think because it thinks the screen is a laptop panel that has no other capabilities, and then does nothing about the extra space (TODO in the code mentions there would be garbage there). Fixed in r26540. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 21 22:32:09 2008 From: trac at haiku-os.org (ekdahl) Date: Mon, 21 Jul 2008 20:32:09 -0000 Subject: [Haiku-bugs] [Haiku] #1836: OpenGL output not visible on screenshots In-Reply-To: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> References: <041.35c11d2f8648ac43478bc54b950533aa@haiku-os.org> Message-ID: <050.e1de355a7b8b5748c4ef3476cc850230@haiku-os.org> #1836: OpenGL output not visible on screenshots ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by ekdahl): Yes, I can confirm that it works here too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 21 22:40:08 2008 From: trac at haiku-os.org (donn) Date: Mon, 21 Jul 2008 20:40:08 -0000 Subject: [Haiku-bugs] [Haiku] #2533: Terminal drops ^D Message-ID: <039.14cedee87e14a9715154d2f5a2be9ebe@haiku-os.org> #2533: Terminal drops ^D -----------------------------------+---------------------------------------- Reporter: donn | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Terminal ignores D, so it's difficult to exit command line applications that expect EOF, for example Python interpreter. Apparently, because TermView::KeyDown() partially confuses this input with B_END, whose value is also 0x4. But rawChar != B_END, so eventually it's just not handled by that case branch, and in the nothing comes out because it didn't go through the default case. The behavior can be fixed by adding an else {} clause, in the B_END branch, similar to the default branch, but that seems like kind of a band- aid. D should probably not match B_END. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 00:14:16 2008 From: trac at haiku-os.org (donn) Date: Mon, 21 Jul 2008 22:14:16 -0000 Subject: [Haiku-bugs] [Haiku] #2533: Terminal drops ^D In-Reply-To: <039.14cedee87e14a9715154d2f5a2be9ebe@haiku-os.org> References: <039.14cedee87e14a9715154d2f5a2be9ebe@haiku-os.org> Message-ID: <048.d2761289f658e01c4aa472e0227427ec@haiku-os.org> #2533: Terminal drops ^D ------------------------------------+--------------------------------------- Reporter: donn | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by donn): Note that other character values may be broken here. For example, \ matches B_LEFT_ARROW. I would suggest you dispatch off rawChar rather than *bytes in that big case expression, since most branches follow the same logic and have the same problem. The "if (rawChar == " test can then be omitted from each of those branches. I also omitted the test for H, which looks like a mistake to me. That works for me: it fixes a handful of broken control characters, and doesn't break anything I expected to work. Something might need to be done for keypad keys, though, as I seem to have lost the numeric keypad. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 00:15:13 2008 From: trac at haiku-os.org (bonefish) Date: Mon, 21 Jul 2008 22:15:13 -0000 Subject: [Haiku-bugs] [Haiku] #2533: Terminal drops ^D In-Reply-To: <039.14cedee87e14a9715154d2f5a2be9ebe@haiku-os.org> References: <039.14cedee87e14a9715154d2f5a2be9ebe@haiku-os.org> Message-ID: <048.fe498ec71b567b9a3dc832d89b76d4cb@haiku-os.org> #2533: Terminal drops ^D ------------------------------------+--------------------------------------- Reporter: donn | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r26550. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 00:47:23 2008 From: trac at haiku-os.org (mmlr) Date: Mon, 21 Jul 2008 22:47:23 -0000 Subject: [Haiku-bugs] [Haiku] #2501: Regression: USB Keyboard not Working on Lenovo T61 In-Reply-To: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> References: <043.21a9039e9f771deab75ff403f6f09c50@haiku-os.org> Message-ID: <052.c69df3ae16fc4c55ee783c506af69a34@haiku-os.org> #2501: Regression: USB Keyboard not Working on Lenovo T61 --------------------------+------------------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: This is in fact a duplicate of bug #1889 and fixed in r26552. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 00:48:16 2008 From: trac at haiku-os.org (mmlr) Date: Mon, 21 Jul 2008 22:48:16 -0000 Subject: [Haiku-bugs] [Haiku] #1889: USB plugs on IBM T60 docking station do not work In-Reply-To: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> References: <041.77f36565f665fa528021d2ef48b05963@haiku-os.org> Message-ID: <050.0fbdd5f81c8f9a3dd40ee33bea786a57@haiku-os.org> #1889: USB plugs on IBM T60 docking station do not work --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26552. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 12:34:29 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 10:34:29 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.cfe10c0109f1aa9ba6a3b9f1ff4785d6@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam at wolke7.net | Owner: leavengood Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by jackburton): Could this have been fixed in r26491 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 12:36:55 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 10:36:55 -0000 Subject: [Haiku-bugs] [Haiku] #1307: [MediaPlayer] jumping on screen In-Reply-To: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> References: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> Message-ID: <049.1cf8523f7b43d43fb1ae8fd83c46e297@haiku-os.org> #1307: [MediaPlayer] jumping on screen ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Could this have been fixed in r26491 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 12:40:37 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 10:40:37 -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.4b6216fb78dfc2ac1c370580615174df@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: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by jackburton): Is this fixed now ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 12:51:14 2008 From: trac at haiku-os.org (stippi) Date: Tue, 22 Jul 2008 10:51:14 -0000 Subject: [Haiku-bugs] [Haiku] #1826: A menu won't close when you click on their item in the menu bar the second time In-Reply-To: <040.2ba1141406563d5292168e0ca41690e3@haiku-os.org> References: <040.2ba1141406563d5292168e0ca41690e3@haiku-os.org> Message-ID: <049.87ee3feb2c8a4f34d422dfbf62e43b85@haiku-os.org> #1826: A menu won't close when you click on their item in the menu bar the second time ---------------------------------+------------------------------------------ Reporter: axeld | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Fixed in r26561. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 12:53:58 2008 From: trac at haiku-os.org (stippi) Date: Tue, 22 Jul 2008 10:53:58 -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.9f4d41cb00bd050f6b21042c67e2efb4@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): Scott, so OHCI is not working for you reliably? Or do you think the problem may not be OHCI but one of the drivers using it. In the later case, we could close this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 13:07:02 2008 From: trac at haiku-os.org (stippi) Date: Tue, 22 Jul 2008 11:07:02 -0000 Subject: [Haiku-bugs] [Haiku] #1808: [Screen] will not close if BMenu is activated In-Reply-To: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> References: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> Message-ID: <049.d4df8e4852b92eeaa72b21a7b448e2b4@haiku-os.org> #1808: [Screen] will not close if BMenu is activated ---------------------------------+------------------------------------------ Reporter: diver | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * milestone: R1/alpha1 => R1 Comment: I cannot reproduce this problem at all. I am trying on real hardware and tried with various programs. In Screen, I can open any popup menu and click the window close button while the popup is still open. Screen always quits as expected. I also tried sending Screen a timed quit message from a Terminal while a popup is open. Both BMenuBar and BMenu poll mouse messages from the history. So they should never miss button events. How can this problem be reproduced? I am moving it out of the alpha tickets anyways. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 13:46:50 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 11:46:50 -0000 Subject: [Haiku-bugs] [Haiku] #1808: [Screen] will not close if BMenu is activated In-Reply-To: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> References: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> Message-ID: <049.62678324cefff33d9690737451a774a1@haiku-os.org> #1808: [Screen] will not close if BMenu is activated ---------------------------------+------------------------------------------ Reporter: diver | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by jackburton): Replying to [comment:14 stippi]: > I cannot reproduce this problem at all. I am trying on real hardware and tried with various programs. In Screen, I can open any popup menu and click the window close button while the popup is still open. Screen always quits as expected. I also tried sending Screen a timed quit message from a Terminal while a popup is open. > > Both BMenuBar and BMenu poll mouse messages from the history. So they should never miss button events. They poll mouse messages from the _window_ history. IOW: if another window is closed by app_server's code (when clicking on the close button, for example), the BMenu client side code could receive the message later. > How can this problem be reproduced? I am moving it out of the alpha tickets anyways. Maybe it has been fixed by your latest changes to mouse messages handling. To reproduce, I just clicked on the window close button and released very quickly, while the popup was opened. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 13:54:27 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 11:54:27 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.8d1ea20405e5c26e11695ab157bb9b0f@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by jackburton): Did you try to check if CTRL is selected as shortcut key in the Menu preflet ? The italian keymap has the same "issue". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 14:08:35 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 12:08:35 -0000 Subject: [Haiku-bugs] [Haiku] #2137: BeScreenCapture program is not functional In-Reply-To: <043.06465f14b94fce6d5a533c780ac357b2@haiku-os.org> References: <043.06465f14b94fce6d5a533c780ac357b2@haiku-os.org> Message-ID: <052.fb868d3f5e44d60f747b4b676361e099@haiku-os.org> #2137: BeScreenCapture program is not functional ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by jackburton): That's because the media kit currently doesn't support recording/encoding. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 14:11:22 2008 From: trac at haiku-os.org (jackburton) Date: Tue, 22 Jul 2008 12:11:22 -0000 Subject: [Haiku-bugs] [Haiku] #2139: Wrong modifier show in menus. In-Reply-To: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> References: <038.eea7ad73e2098548665dad03e9f8ea9c@haiku-os.org> Message-ID: <047.aaceda08bcae552e343b3afa241026f1@haiku-os.org> #2139: Wrong modifier show in menus. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by jackburton): The modifiers situation is a bit confusing: Using the italian keymap, the CTRL shortcut key is the default, and if I choose ALT as shortcut key, then I can't produce some symbols anymore (I.e. the @ symbol, which is produced with ALT-GR + the ? key, in the italian keymap). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 14:27:41 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 22 Jul 2008 12:27:41 -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.1f402c58f8bf88a87b161b30e448eb79@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: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by anevilyak): I want to say on the fly detection of CDs is fixed now, though this still leaves the (known) issue that the ata bus manager which I'm currently using doesn't support ATAPI at all yet, so I'd have to switch back to ide to verify. Will do hopefully later today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 15:54:13 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 13:54:13 -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.a7ff1d566362de9bf2bdd138c26b3646@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): I'll put a fresh image on that board today and report back soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 16:48:32 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 22 Jul 2008 14:48:32 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.a71ed2273b2c37237527ea78fd407c19@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): This one has just happened to me too, while running the configure of bonnie++ which I've ran already many times with no problems. The only difference this time is that I was doing another operation that required I/O (e.g. wget). The command called by the configure that causes the invalid opcode seems to be sed, although bt would return sh being the thread causing the crash. Any suggestions about what I can check if it happens again? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 18:37:43 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 16:37:43 -0000 Subject: [Haiku-bugs] [Haiku] #2217: Terminal replicant graphic scrolls off the screen In-Reply-To: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> References: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> Message-ID: <051.22760d3ced83c32f4a8f747c81c6a789@haiku-os.org> #2217: Terminal replicant graphic scrolls off the screen ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Since the replicant feature has been removed from the terminal this bug can be closed as it's no longer valid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 20:40:25 2008 From: trac at haiku-os.org (kvdman) Date: Tue, 22 Jul 2008 18:40:25 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps Message-ID: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> #2534: Menu background issues with R5 Apps ----------------------------------+----------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I've noticed a couple issues with the menu behaviour of certain R5 apps. They seemed to work fine before, but now in AbiWord (yes it still crashes) the toolbar icons have a red background (appeared normally before), and some of GoBe Productive's toolbar icons are totally black; as well as the colour picker. Tested on rev26546. Please see the attached pictures. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 20:44:03 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 22 Jul 2008 18:44:03 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.c48247aaa1fb3a93a7679cddba60bcff@haiku-os.org> #2534: Menu background issues with R5 Apps -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * owner: axeld => stippi Comment: Most likely this is another case of using B_RGB32 where B_RGBA32 should be used. Reassigning to Stephan since this is related to some of his recent work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 20:44:22 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 22 Jul 2008 18:44:22 -0000 Subject: [Haiku-bugs] [Haiku] #2534: Menu background issues with R5 Apps In-Reply-To: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> References: <041.75dfe4426ff189167b2874fa6dc6b8a9@haiku-os.org> Message-ID: <050.7312f585d62cec968a315771d00b97fc@haiku-os.org> #2534: Menu background issues with R5 Apps ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * component: Kits/Application Kit => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 22:43:29 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 20:43:29 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.38abac95f38d24f25078675012ae3541@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by scottmc): This ticket actually has a handful of tasks still to be done. There is a milestone on HaikuPorts for it: http://ports.haiku-files.org/query?group=status&milestone=Haiku+self- hosting Many of them are now including in the haiku development builds even though the tickets aren't closed: http://haiku-files.org/files/optional- packages/[[BR]] From Ingo's list above:[[BR]] * subversion ~~ * OpenSSH (not directly development related, but needed for BerliOS non-anonymous svn) ~~ * gettext: Needed by the auto tools for certain packages. ~~ * make is a build tool, but included in the Haiku sources. I'd like to re-port it. ~~ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 23:27:25 2008 From: trac at haiku-os.org (stippi) Date: Tue, 22 Jul 2008 21:27:25 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.ba14d7af9824c5a3b65a86dc76e18818@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): The previous BFS and file map bugs could corrupt the file system and file contents quite badly. Are you doing this with a completely fresh image? I could imagine that garbage was either in executable code, or libraries or something like that in such a way that it would still load, but then contained bad instructions. Could this be the case? I don't know what is needed to trigger this panic. Maybe the kernel itself or a driver contained such garbage? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 23:28:31 2008 From: trac at haiku-os.org (stippi) Date: Tue, 22 Jul 2008 21:28:31 -0000 Subject: [Haiku-bugs] [Haiku] #2217: Terminal replicant graphic scrolls off the screen In-Reply-To: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> References: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> Message-ID: <051.365d4a669a005298256fb8ef797917bd@haiku-os.org> #2217: Terminal replicant graphic scrolls off the screen ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: Ok, I guess this makes sense. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 23:35:30 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 21:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.ddff20b25a24ae277846e951f20c5494@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): "The previous BFS and file map bugs could corrupt the file system" Define previous.. Do you know about when that was, as this bug just showed up recently and if related to the "BFS and file map bugs" you refer too, if those are fixed that could very well have been the cause of this issue. I haven't run into the invalid opcode in the last few days, but then again I haven't been stressing the system. I do suspect that files were getting corrupted or just that the autotools hate me... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 22 23:42:19 2008 From: trac at haiku-os.org (anevilyak) Date: Tue, 22 Jul 2008 21:42:19 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.26392d700dae32f29aeed3188c23ca72@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): That one was fixed in r26531 specifically. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:13:52 2008 From: trac at haiku-os.org (diver) Date: Tue, 22 Jul 2008 22:13:52 -0000 Subject: [Haiku-bugs] [Haiku] #1808: [Screen] will not close if BMenu is activated In-Reply-To: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> References: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> Message-ID: <049.a1d965324a86435f35641d336aadb8b4@haiku-os.org> #1808: [Screen] will not close if BMenu is activated ---------------------------------+------------------------------------------ Reporter: diver | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): I can't reproduce it anymore, please close it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:17:47 2008 From: trac at haiku-os.org (diver) Date: Tue, 22 Jul 2008 22:17:47 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.326c54f67ff4f68caed5076bd00e80f3@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by diver): Yeah, Ctrl is selected as shortcut key, I tried with Ctrl+w to close a window, but this also didn't work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:26:27 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 22:26:27 -0000 Subject: [Haiku-bugs] [Haiku] #1633: KDL when accessing a file on a CD-ROM In-Reply-To: <041.9ce519cbbcb7dea64f8186cbc8dcd238@haiku-os.org> References: <041.9ce519cbbcb7dea64f8186cbc8dcd238@haiku-os.org> Message-ID: <050.2e652e60380105c5e10c76731b1a1592@haiku-os.org> #1633: KDL when accessing a file on a CD-ROM ------------------------------------+--------------------------------------- Reporter: vzsolt | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by scottmc): Looks like this one should be closed. I haven't had any troubles reading from DVD under VMWare recently. Looks like this one was fixed months ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:37:12 2008 From: trac at haiku-os.org (diver) Date: Tue, 22 Jul 2008 22:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #2462: /var/tmp missing from image In-Reply-To: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> References: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> Message-ID: <050.fa3fc5a33915d087a9250a31d8f7945e@haiku-os.org> #2462: /var/tmp missing from image ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by diver): I this still an issue? I tried to download several files in firefox and it works just fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:37:39 2008 From: trac at haiku-os.org (diver) Date: Tue, 22 Jul 2008 22:37:39 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading In-Reply-To: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> References: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> Message-ID: <049.a993bd4ba9fe14c263be31b21616ed88@haiku-os.org> #2493: [Network] slow file downloading ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): Please close this as a dupe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:40:50 2008 From: trac at haiku-os.org (diver) Date: Tue, 22 Jul 2008 22:40:50 -0000 Subject: [Haiku-bugs] [Haiku] #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts In-Reply-To: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> References: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> Message-ID: <049.ed0f8a8b94c308116d0c8a8b904fa0e6@haiku-os.org> #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by diver): Please close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 00:54:42 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 22:54:42 -0000 Subject: [Haiku-bugs] [Haiku] #581: Crash while mounting a BFS partition In-Reply-To: <054.1e1d33154fb61b9895e81855c3eaa99a@haiku-os.org> References: <054.1e1d33154fb61b9895e81855c3eaa99a@haiku-os.org> Message-ID: <063.a5eede6a977cfd28706854316a322a04@haiku-os.org> #581: Crash while mounting a BFS partition ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Comment(by scottmc): I assume this one is fixed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 01:14:04 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 23:14:04 -0000 Subject: [Haiku-bugs] [Haiku] #1637: Frozen empty desktop with an inert cursor on startup. In-Reply-To: <044.7afb4d43680843f4ca5fa4d787a00c12@haiku-os.org> References: <044.7afb4d43680843f4ca5fa4d787a00c12@haiku-os.org> Message-ID: <053.8849e91ee1736a5d7a0332aa0262ccf0@haiku-os.org> #1637: Frozen empty desktop with an inert cursor on startup. ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): This one looks like it can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 01:20:00 2008 From: trac at haiku-os.org (scottmc) Date: Tue, 22 Jul 2008 23:20:00 -0000 Subject: [Haiku-bugs] [Haiku] #1677: Strange behaviour with images and games... In-Reply-To: <041.15c28956e275fc18e7fa4b5d56380289@haiku-os.org> References: <041.15c28956e275fc18e7fa4b5d56380289@haiku-os.org> Message-ID: <050.542fe536e03e7b9823b5bc93b6c493a1@haiku-os.org> #1677: Strange behaviour with images and games... ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by scottmc): * cc: haiku at scottmc.com (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 03:05:30 2008 From: trac at haiku-os.org (kvdman) Date: Wed, 23 Jul 2008 01:05:30 -0000 Subject: [Haiku-bugs] [Haiku] #2462: /var/tmp missing from image In-Reply-To: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> References: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> Message-ID: <050.57dbb4b43a0b2e92988102494050f8d2@haiku-os.org> #2462: /var/tmp missing from image ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kvdman): No, please close it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 06:43:56 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 23 Jul 2008 04:43:56 -0000 Subject: [Haiku-bugs] [Haiku] #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes In-Reply-To: <042.049c3dcb127418abcb089c84f77dedd2@haiku-os.org> References: <042.049c3dcb127418abcb089c84f77dedd2@haiku-os.org> Message-ID: <051.d8f2a2784dbdabf1ef1f9027d2d2aaca@haiku-os.org> #2520: could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by scottmc): * cc: haiku at scottmc.com (added) Comment: I get something similar when trying to add extra zip files to my images: {{{ Unzipping generated/download/automake-1.10.1-gcc2-2008-03-24-1.zip ... could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes Unzipping generated/download/bison-2.3-gcc2-2008-03-28.zip ... Error: Failed to open connection to FS shell: Connection refused Unzipping generated/download/flex-2.5.35-gcc2-2008-03-28.zip ... Error: Failed to open connection to FS shell: Connection refused }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 08:38:43 2008 From: trac at haiku-os.org (jackburton) Date: Wed, 23 Jul 2008 06:38:43 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.65691aad0631f2140a0d63b1a62aa161@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by jackburton): What happens if you open the menu preflet, choose ALT as shortcut, then choose CTRL again ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 10:33:14 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 08:33:14 -0000 Subject: [Haiku-bugs] [Haiku] #1808: [Screen] will not close if BMenu is activated In-Reply-To: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> References: <040.a69f9d24bc603e51bd4cf2387bcc3ba6@haiku-os.org> Message-ID: <049.1ac4707e8fa4550b65e2c1286cab9ac1@haiku-os.org> #1808: [Screen] will not close if BMenu is activated ---------------------------------+------------------------------------------ Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Thanks for the feedback! Please reopen if someone does happen do encounter it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:21:16 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 23 Jul 2008 09:21:16 -0000 Subject: [Haiku-bugs] [Haiku] #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) Message-ID: <042.192a0aec42da9c9c6d55e28eb579e336@haiku-os.org> #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Since I don't know which lock should be held first (there should be an order) I'll leave it to someone else. {{{ kdebug> thread 738 THREAD: 0x914de000 id: 738 (0x2e2) name: "sh" all_next: 0x9149d800 team_next: 0x00000000 q_next: 0x913c4800 priority: 10 (next 10) state: waiting next_state: waiting cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: mutex 0x8010129c fault_handler: 0x00000000 args: 0x90d1c4b0 0x00000000 entry: 0x800458ac team: 0x90cc42e8, "sh" exit.sem: 8263 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 15626 kernel_stack_base: 0x90b11000 user_stack_area: 15628 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 10903338 user_time: 3868782 flags: 0x0 architecture dependant section: esp: 0x90b149a8 ss: 0x00000010 fpu_state at 0x914de380 kdebug> mutex 0x8010129c mutex 0x8010129c: name: legacy driver flags: 0x0 holder: 25 waiting threads: 738 kdebug> thread 25 THREAD: 0x913c3800 id: 25 (0x19) name: "usb explore" all_next: 0x00000000 team_next: 0x913c3000 q_next: 0x800f79c0 priority: 5 (next 5) state: waiting next_state: waiting cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: mutex 0x90b7d9b8 fault_handler: 0x00000000 args: 0x90b6d500 0x00000000 entry: 0x80700858 team: 0x90b7b000, "kernel_team" exit.sem: 100 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 115 kernel_stack_base: 0x8016e000 user_stack_area: -1 user_stack_base: 0x00000000 user_local_storage: 0x00000000 kernel_errno: 0x0 (No error) kernel_time: 452272 user_time: 0 flags: 0x0 architecture dependant section: esp: 0x80171cbc ss: 0x00000010 fpu_state at 0x913c3b80 kdebug> mutex 0x90b7d9b8 mutex 0x90b7d9b8: name: devfs lock flags: 0x0 holder: 738 waiting threads: 25 2786 2820 2825 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:28:46 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 23 Jul 2008 09:28:46 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.1996ecc0ea67c2ed228f2db894531b08@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by andreasf): Replying to [comment:18 scottmc]: > This ticket actually has a handful of tasks still to be done. There is a milestone on HaikuPorts for it: While the HaikuPorts milestone is certainly relevant for development on Haiku, Ingo indicated above that this ticket could be closed despite the missing tools he listed. So what's keeping this develop-directory ticket open would be only the missing develop contents, no? If we do want to track other tool availability, we could do so in a separate ticket, now that Trac has dependency tracking. I'll look into packaging neon and Subversion 1.4.x shortly. For the freetype headers I had a one-line patch against OptionalPackages to add them, but it was useless without {{{freetype-config}}} (which would need to be built first) and pkg-config files (that may need to be preprocessed before copying). {{{ Index: build/jam/OptionalPackages =================================================================== --- build/jam/OptionalPackages (Revision 25608) +++ build/jam/OptionalPackages (Arbeitskopie) @@ -92,6 +92,7 @@ AddHeaderDirectoryToHaikuImage libs ncurses : 3rdparty ; AddHeaderDirectoryToHaikuImage libs png : 3rdparty ; AddHeaderDirectoryToHaikuImage libs zlib : 3rdparty ; + AddHeaderDirectoryToHaikuImage libs freetype2 : 3rdparty ; if $(HAIKU_GCC_VERSION[1]) > 2 { # gcc 4 }}} I dropped that incomplete patch for my Bluetooth patch and was short on time lately. This line could already be added if still missing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:49:31 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 09:49:31 -0000 Subject: [Haiku-bugs] [Haiku] #581: Crash while mounting a BFS partition In-Reply-To: <054.1e1d33154fb61b9895e81855c3eaa99a@haiku-os.org> References: <054.1e1d33154fb61b9895e81855c3eaa99a@haiku-os.org> Message-ID: <063.f819f04ec9edc9da4d594df28f2bbf32@haiku-os.org> #581: Crash while mounting a BFS partition ----------------------------------+----------------------------------------- Reporter: daneel at rootshell.be | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Yes, very likely that this was fixed meanwhile. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:50:26 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 09:50:26 -0000 Subject: [Haiku-bugs] [Haiku] #2462: /var/tmp missing from image In-Reply-To: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> References: <041.d8284931d6b42b46a331400f20f42405@haiku-os.org> Message-ID: <050.76719f7a2e489222de98b803f91a8c13@haiku-os.org> #2462: /var/tmp missing from image ------------------------+--------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, thanks for the feedback! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:52:21 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 09:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.5c9578a21e33cbe8a8066ec129c82887@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by stippi): I was also wondering about the same thing. It looks to me like the keymaps don't define the very same combination of modifier mappings that the Menu preflet will define. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:57:16 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 09:57:16 -0000 Subject: [Haiku-bugs] [Haiku] #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts In-Reply-To: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> References: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> Message-ID: <049.52edbc63ddc8fb8f67c12cc399fc98b3@haiku-os.org> #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:57:48 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 09:57:48 -0000 Subject: [Haiku-bugs] [Haiku] #2493: [Network] slow file downloading In-Reply-To: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> References: <040.a146a7cca41423629634a23e38561f26@haiku-os.org> Message-ID: <049.344d7de0a8c716a6cd161b83683da121@haiku-os.org> #2493: [Network] slow file downloading ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => duplicate -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 11:59:27 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 09:59:27 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot Message-ID: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Bug report from [http://qube.ru/users/damoklas damoklas] Since a few revisions Haiku don't boot anymore, it reboots just after boot logo appears on screen.[[BR]] Safemode options doesn't change anything.[[BR]] [[BR]] haiku.image.r26477 works[[BR]] haiku.image.r26493 don't work[[BR]] [[BR]] CPU ? AMD Athlon? XP 2500+ (Barton)[[BR]] Motherboard ? ABIT NF7?S2G[[BR]] 1GB DDR RAM[[BR]] HDD ? SAMSUNG SP0812N (IDE)[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 12:03:54 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 10:03:54 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.d337fb560063dff3e5d956364b033185@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by diver): Replying to [comment:3 jackburton]: > What happens if you open the menu preflet, choose ALT as shortcut, then choose CTRL again ? If I select ALT, shortcuts doesn't work either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 12:42:44 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 23 Jul 2008 10:42:44 -0000 Subject: [Haiku-bugs] [Haiku] #2537: Ftp crash causes a deadlock in journal area Message-ID: <042.1055dbf1708c0ebe23dd83df92671c13@haiku-os.org> #2537: Ftp crash causes a deadlock in journal area -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Ftp crash while doing a mget of a few files, and (perhaps it's just a coincidence) while trying to open one of them already downloaded. After the crash, the journal area is locked. Unfortunately I forgot to get the backtrace of this thread. {{{ THREAD: 0x913c0800 id: 9 (0x9) name: "block notifier/writer" all_next: 0x00000000 team_next: 0x9136a000 q_next: 0x800f79c0 priority: 5 (next 5) state: ready next_state: ready cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: fault_handler: 0x00000000 args: 0x00000000 0x00000000 entry: 0x80029fdc team: 0x90b7b000, "kernel_team" exit.sem: 34 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 95 kernel_stack_base: 0x8015d000 user_stack_area: -1 user_stack_base: 0x00000000 user_local_storage: 0x00000000 kernel_errno: 0x0 (No error) kernel_time: 7691481 user_time: 0 flags: 0x0 architecture dependant section: esp: 0x8016084c ss: 0x00000010 fpu_state at 0x913c0b80 kdebug> mutex 0x90b8c2d4 mutex 0x90b8c2d4: name: bfs journal flags: 0x0 holder: 9 waiting threads: 85 300 203 192 200 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 13:17:21 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 11:17:21 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.1a21da7e2a917063ef064a6a74031a93@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Note that there is already an subversion 1.4.6 package available as the "Subversion" OptionalPackage. It was added in r26158 and has been in there for 4 weeks now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 13:26:24 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 11:26:24 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.9c91297c99284a784ef01e25f75a6dbf@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): I am trying to take care of make and an updated makefile engine. Many BeOS software relies on that. Ingo wrote a better/updated version that handles object dependencies better a couple years back, I wanted to compile a proper optional package from that. I also prepared an optional package for CVS. I did compile pkg-config on/for Haiku, but it requires changes to the SetupEnvironment script. I need to figure out if this can be done via the OptionalPackage build feature of if I need to find another way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 13:28:38 2008 From: trac at haiku-os.org (andreasf) Date: Wed, 23 Jul 2008 11:28:38 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.dabbe51f52beff5e9422bef8f70a04c6@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by andreasf): Replying to [comment:20 mmlr]: > Note that there is already an subversion 1.4.6 package available as the "Subversion" OptionalPackage. It was added in r26158 and has been in there for 4 weeks now. Thanks for the notice, I've not been running Haiku for a number of weeks. I am going to work on Subversion anyway since I heard Subversion 1.5 was out by now. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 13:28:46 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 11:28:46 -0000 Subject: [Haiku-bugs] [Haiku] #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) In-Reply-To: <042.192a0aec42da9c9c6d55e28eb579e336@haiku-os.org> References: <042.192a0aec42da9c9c6d55e28eb579e336@haiku-os.org> Message-ID: <051.77a9437b4f19246a1a4cdc8654222388@haiku-os.org> #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Do you have any directions on how to reproduce that? What was the shell up to when this happened (stack traces would be helpful)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 13:40:02 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 11:40:02 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot In-Reply-To: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> References: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> Message-ID: <049.a0f5c25d11a885cf066d77aabb06550b@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): That was most probably uncovered by r26492. The change itself is not problematic, but it enabled APIC timers on non-SMP systems. Probably there is a problem with the timer and/or APIC code in this case. Please try removing the "gAPICTimer" on line 41 of src/system/kernel/arch/x86/arch_timer.c to verify that. If this resolves the reboot problem we would need to look into better verifying the functionality of the APIC or review the APIC setup code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 14:17:28 2008 From: trac at haiku-os.org (jackburton) Date: Wed, 23 Jul 2008 12:17:28 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot In-Reply-To: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> References: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> Message-ID: <049.61379b36f528c7010018e5f69694d009@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by jackburton): Replying to [comment:1 mmlr]: > That was most probably uncovered by r26492. The change itself is not problematic, but it enabled APIC timers on non-SMP systems. Probably there is a problem with the timer and/or APIC code in this case. Please try removing the "gAPICTimer" on line 41 of src/system/kernel/arch/x86/arch_timer.c to verify that. If this resolves the reboot problem we would need to look into better verifying the functionality of the APIC or review the APIC setup code. There seems to be some faulty BIOSes which cause problems when using the local APIC (as you already pointed out, btw). We should have a kernel setting and a safe mode option to disable the use of the local APIC. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 15:04:10 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 13:04:10 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot In-Reply-To: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> References: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> Message-ID: <049.ea56eead8160c2148c1f58fdb94a4b24@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): The local APIC is necessary when doing SMP anyway (as it is responsible for inter-CPU messaging) and always seemed to work fine for all the configurations I have used it on. Therefore using APIC timers when doing SMP should be pretty much OK. Using it for non-SMP configurations has a higher chance of not working, because the local APIC is not strictly needed on a non-SMP system and I can very well imagine that there are broken local APICs / BIOSes in those cases. We might just change the code a bit again so that local APICs aren't used at all in the non-SMP case, as this seemed to work fine up to now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 15:46:33 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 13:46:33 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot In-Reply-To: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> References: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> Message-ID: <049.6e42805ea9afb8e85931eda49faa8df9@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Just curious, is there any inherent advantage to the APIC timer over the PIT? Better precision or anything like that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 16:14:44 2008 From: trac at haiku-os.org (kallisti5) Date: Wed, 23 Jul 2008 14:14:44 -0000 Subject: [Haiku-bugs] [Haiku] #1906: BeIDE crash In-Reply-To: <040.101ee775fff9b72592882d61daa31318@haiku-os.org> References: <040.101ee775fff9b72592882d61daa31318@haiku-os.org> Message-ID: <049.1feb194916f41cccee8a3d2e57864e65@haiku-os.org> #1906: BeIDE crash ---------------------------+------------------------------------------------ Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by kallisti5): verified still present on r26257 vm_soft_fault: va 0x6669649b not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x6669649b, ip 0x3136c7, write 0, user 1, thread 0x20b vm_page_fault: sending team "BeIDE" 0x1fa SIGSEGV, ip 0x3136c7 ("BeIDE_seg0ro" +0x1136c7) stack trace: 0x0027ba0a (BeIDE_seg0ro + 0x7ba0a) 0x006aab22 (libbe.so_seg0ro + 0xadb22) 0x0074e78a (libbe.so_seg0ro + 0x15178a) 0x006ac1ab (libbe.so_seg0ro + 0xaf1ab) 0x006aa6a6 (libbe.so_seg0ro + 0xad6a6) 0x0075101d (libbe.so_seg0ro + 0x15401d) 0x007547d8 (libbe.so_seg0ro + 0x1577d8) 0x006abc17 (libbe.so_seg0ro + 0xaec17) 0x008649f0 (libroot.so_seg0ro + 0x249f0) 0x70102fec (w>About BeIDE_523_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 0x800acc60, write 0, user 0, thread 0x20b debug_server: Thread 523 entered the debugger: Segment violation stack trace, current PC 0x3136c7 _._t10VideoCoder1Z7MemArea + 0x17: (0x70102c10) 0x27ba0a _._8AboutBox + 0x46 (0x70102c2c) 0x6aab22 Quit__7BLooper + 0xde (0x70102c5c) 0x74e78a Quit__7BWindow + 0xc6 (0x70102c8c) 0x6ac1ab _QuitRequested__7BLooperP8BMessage + 0x107 (0x70102d0c) 0x6aa6a6 DispatchMessage__7BLooperP8BMessageP8BHandler + 0x46 (0x70102d3c) 0x75101d DispatchMessage__7BWindowP8BMessageP8BHandler + 0x174d (0x70102f1c) 0x7547d8 task_looper__7BWindow + 0x270 (0x70102f7c) 0x6abc17 _task0___7BLooperPv + 0x3f (0x70102fac) 0x8649f0 _get_next_team_info + 0x5c (closest symbol) wait interval 911822, scan pages 1225, free 1857, target 190 wait interval 982828, scan pages 651, free 2010, target 37 wait interval 997215, scan pages 535, free 2041, target 6 debug_server: Killing team 506 (/boot/develop/BeIDE/BeIDE) debug_server: TeamDebugHandler::Init(): Failed to get info for team 506: Operation on invalid team debug_server: KillTeam(): Error getting info for team 506: Operation on invalid team debug_server: Killing team 506 () -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 16:28:26 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 14:28:26 -0000 Subject: [Haiku-bugs] [Haiku] #2536: [kernel] Haiku reboots upon boot In-Reply-To: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> References: <040.778ae482cc9d3e26ff51514c66328c51@haiku-os.org> Message-ID: <049.a53e7e04ee502b7ea13ce12c1f3c0334@haiku-os.org> #2536: [kernel] Haiku reboots upon boot ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Well, it's a controller built into the processor, so it has the advantage of having less overhead compared to an external controller. It probably has a higher precision too, though I wouldn't know the numbers. The local APIC is part of processors since the Pentium Pro, so it's nothing just recently introduced. The problem is, as mentioned above, that it is not strictly necessary on non-SMP systems, so its exposure is far less which makes unrecognized bugs more likely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 18:49:02 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 16:49:02 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition Message-ID: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Steps to reproduce: - mount second BFS partition. - cd to partition in a Terminal - open DriveSetup - attempt to unmount via DriveSetup (error -> busy) - close Terminal - attempt to unmount via DriveSetup (error -> busy) - open Terminal and use Terminal unmount command -> KDL {{{ vnode 0x90bb27f8 PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 218 "unmount" kernel stack: 0x806c4000 to 0x806c8000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 806c7c14 (+ 32) 80052268 :invoke_debugger_command + 0x00da 1 806c7c34 (+ 48) 8005236b :invoke_pipe_segment(debugger_command_pipe*, long, char*) + 0x006f 2 806c7c64 (+ 32) 80052438 :invoke_debugger_command_pipe + 0x008e 3 806c7c84 (+ 32) 80052f32 :ExpressionParser::_ParseCommandPipe(int&) + 0x0084 4 806c7ca4 (+ 48) 80053516 :ExpressionParser::EvaluateCommand(char const*, int&) + 0x010c 5 806c7cd4 (+ 192) 800535cf :evaluate_debug_command + 0x0089 6 806c7d94 (+ 64) 800516ae :kernel_debugger + 0x024c 7 806c7dd4 (+ 176) 80051795 :panic + 0x002d 8 806c7e84 (+ 64) 80079ff7 :dec_vnode_ref_count(vnode*, bool, bool) + 0x0057 9 806c7ec4 (+ 80) 8007dd72 :fs_unmount(char*, long, unsigned long, bool) + 0x017c 10 806c7f14 (+ 48) 8007e11b :_user_unmount + 0x006f 11 806c7f44 (+ 100) 800a0622 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x806c7fa8 (end = 0x806c8000) eax 0x50 ebx 0x2b1e00 ecx 0x7ffeeecc edx 0xffff0104 esi 0x7ffef5bc edi 0x7ffef544 ebp 0x7ffeeee8 esp 0x806c7fdc eip 0xffff0104 eflags 0x206 vector: 0x63, error code: 0x0 12 806c7fa8 (+ 0) ffff0104 13 7ffeeee8 (+ 128) 00200a10 <_APP_>:main + 0x00c8 14 7ffeef68 (+ 52) 002007fd <_APP_>:_start + 0x0051 15 7ffeef9c (+ 64) 0010019a 3526:runtime_loader_seg0ro at 0x00100000 + 0x19a 16 7ffeefdc (+ 0) 7ffeefec 3525:unmount_main_stack at 0x7efef000 + 0xffffec kdebug> vnode 0x90bb27f8 VNODE: 0x90bb27f8 device: 4 id: 2053 ref_count: -1 private_node: 0x90bb63fc mount: 0x90b08eb0 covered_by: 0x00000000 cache: 0x00000000 flags: --- advisory_lock: 0x00000000 kdebug> vnodes 4 address dev inode ref cache fs-node locking flags 0x90bb27f8 4 2053 -1 0x00000000 0x90bb63fc 0x00000000 --- 0x90bb2a18 4 2055 0 0x00000000 0x90bb694c 0x00000000 --- 0x90bb26e8 4 2119 0 0x00000000 0x90bb6aa0 0x00000000 --- 0x90bb2908 4 2251 0 0x00000000 0x90bb66a4 0x00000000 --- 0x90bb2fac 4 2276 0 0x00000000 0x90bbd2a8 0x00000000 --- 0x90bb2e58 4 2277 0 0x00000000 0x90bbd7f8 0x00000000 --- 0x90bb2d48 4 2278 0 0x00000000 0x90bbd550 0x00000000 --- 0x90bbb330 4 2273 0 0x00000000 0x90bbc154 0x00000000 --- 0x90bbb3fc 4 2274 0 0x00000000 0x90bbc3fc 0x00000000 --- 0x90bb2cc0 4 2275 0 0x00000000 0x90bbd3fc 0x00000000 --- 0x90bb2990 4 2284 0 0x00000000 0x90bb67f8 0x00000000 --- 0x90bbb264 4 2282 0 0x00000000 0x90bbde9c 0x00000000 --- 0x90bb2dd0 4 2283 0 0x00000000 0x90bbd6a4 0x00000000 --- 0x90bbb044 4 2332 0 0x00000000 0x90bb6e9c 0x00000000 --- 0x90bbb0cc 4 2370 0 0x00000000 0x90bbd000 0x00000000 --- 0x90bbb154 4 2449 0 0x00000000 0x90bbd154 0x00000000 --- 0x90bbb2ec 4 2476 0 0x90b371e0 0x90bbc000 0x00000000 --- 0x90bbb3b8 4 2477 0 0x90b3be10 0x90bbc2a8 0x00000000 --- 0x90bb2f24 4 2478 0 0x90b44870 0x90bbdaa0 0x00000000 --- 0x90bbb000 4 2484 0 0x90b40e10 0x90bbdbf4 0x00000000 --- 0x90bbb484 4 2488 0 0x90b60960 0x90bbc550 0x00000000 --- 0x90bb2c38 4 2581 0 0x00000000 0x90bb6d48 0x00000000 --- 0x90bb2ee0 4 2614 0 0x00000000 0x90bbd94c 0x00000000 --- 0x90bbb1dc 4 2647 0 0x00000000 0x90bbdd48 0x00000000 --- kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:05:40 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 17:05:40 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.50108f751e5961e760181341eaf4b76f@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): This seems to be consistently reproducible by the way, the same set of steps crashes it both on my box and mmu_man's. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:13:34 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 17:13:34 -0000 Subject: [Haiku-bugs] [Haiku] #2539: [app_server] crash in HWInterface::_CopyToFront Message-ID: <040.caf03ae097bdc95f0143934989227c22@haiku-os.org> #2539: [app_server] crash in HWInterface::_CopyToFront --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- When using VESA mode I tried to change resolution app_server crashed in HWInterface::_CopyToFront. {{{ Segment violation Switching to team /boot/beos/system.servers/app_server HWInterface::_CopyToFront HWInterface::CopyBackToFront AccelerantHWInterface::CopyBackToFront HWInterface::Invalidate HWInterface::MoveCursorTo }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:26:20 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 17:26:20 -0000 Subject: [Haiku-bugs] [Haiku] #2540: [intel_extreme] can't boot Haiku unless I use fail-safe video mode Message-ID: <040.bb1d87fe6b171f34055e1828662e38b3@haiku-os.org> #2540: [intel_extreme] can't boot Haiku unless I use fail-safe video mode --------------------------------------------+------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------------+------------------------------- Haiku wont boot to desktop unless i select "Use fail-safe video mode" option.[[BR]][[BR]] If I don't select this option Haiku will freeze when loading app_server showing black screen with some noisy intel_extreme lines telling something about pll.[[BR]][[BR]] Asus P5GC-MX. 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) 00:02.0 0300: 8086:2772 (rev 02) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:33:27 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 17:33:27 -0000 Subject: [Haiku-bugs] [Haiku] #1641: KDL: rtl8139 In-Reply-To: <043.5f4af7ba053274031187f62bac03de4a@haiku-os.org> References: <043.5f4af7ba053274031187f62bac03de4a@haiku-os.org> Message-ID: <052.89081a102329f2fa6c5469cbbbf8386f@haiku-os.org> #1641: KDL: rtl8139 ------------------------------+--------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: 2452 ------------------------------+--------------------------------------------- Changes (by diver): * component: - General => Drivers/Network Comment: Same problem here, for me it could crash at boot or at firefox start or a few moments later.[[BR]]As rtl8139 is so common nic these days I would recommend to fix it until alpha. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:36:21 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 17:36:21 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.d5258ed91663f8e3cd5990912cf02410@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Could this be the culprit? {{{ in fs_unmount: if ((flags & B_FORCE_UNMOUNT) == 0) { mutex_unlock(&sVnodeMutex); put_vnode(mount->root_vnode); return B_BUSY; } I don't see why it's doing put_vnode there, since it seems to release the ref as needed much earlier after checking the path, and I don't see any other obvious path that does this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:39:03 2008 From: trac at haiku-os.org (diver) Date: Wed, 23 Jul 2008 17:39: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.2e4d80fe201bbfce4611a4cb6417574a@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): Same problem here with Asus P5GC-MX and sata hdd. Changing ide to ata "fixes" the problem, but now Haiku boots about 2 minutes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:48:54 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 17:48:54 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.47ec7a079732eb37886a62b8f61cadae@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): Yeah, that's more or less a "known" problem, already pointed out in bug #1982 I think. The attachment there got shreddered it seems though and before nobody had the time to really check the patch. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:52:47 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 17:52:47 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.202e92eabe3f068dd18eeb71fbf70708@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Ah, I didn't notice that one since a quick search didn't really match the kpanic description I'm hitting. Maybe the ASSERT was added later? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 19:55:40 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 17:55:40 -0000 Subject: [Haiku-bugs] [Haiku] #2022: Add r###### to the Haiku Build Factory images In-Reply-To: <042.8b191dac14a7dfcafd9b82447b288c99@haiku-os.org> References: <042.8b191dac14a7dfcafd9b82447b288c99@haiku-os.org> Message-ID: <051.a3efb955667dbc0e9ad9e0fb647c5e92@haiku-os.org> #2022: Add r###### to the Haiku Build Factory images --------------------------+------------------------------------------------- Reporter: scottmc | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Website R1 Component: Website | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => invalid Comment: Then I guess this can be closed as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 20:02:41 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 23 Jul 2008 18:02:41 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.a2e2298670b4732eb2b71890f3f91885@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by mmlr): No, the assert was there once already, but only got reenabled recently. The message in bug #1988 pretty much matches this one, but the reason for the assert to fail is different in the case there. I think the observation is correct and would vote for removing the put_vnode() line. You could do so and test if the reference counting is correct then. If so, please feel free to commit the change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 20:06:57 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 18:06:57 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.772309d2ef31f4a62ae807a95d94c7b5@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): Will test when I get home in a few hours, thanks for confirming. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 20:37:15 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 23 Jul 2008 18:37:15 -0000 Subject: [Haiku-bugs] [Haiku] #1828: PackageInstaller is missing an icon In-Reply-To: <040.d38a997ec14c6fc50d062666271e1df5@haiku-os.org> References: <040.d38a997ec14c6fc50d062666271e1df5@haiku-os.org> Message-ID: <049.f90946b1cf5bdcebab00da2eff049083@haiku-os.org> #1828: PackageInstaller is missing an icon --------------------------------------------+------------------------------- Reporter: korli | Owner: sil2100 Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------------+------------------------------- Comment(by scottmc): Looks like this one was fixed but not closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 21:41:41 2008 From: trac at haiku-os.org (stippi) Date: Wed, 23 Jul 2008 19:41:41 -0000 Subject: [Haiku-bugs] [Haiku] #2539: [app_server] crash in HWInterface::_CopyToFront In-Reply-To: <040.caf03ae097bdc95f0143934989227c22@haiku-os.org> References: <040.caf03ae097bdc95f0143934989227c22@haiku-os.org> Message-ID: <049.8ce5e2e94a444c18caea004c3355847d@haiku-os.org> #2539: [app_server] crash in HWInterface::_CopyToFront ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: I've seen this too once. Thanks for reporting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 22:08:27 2008 From: trac at haiku-os.org (korli) Date: Wed, 23 Jul 2008 20:08:27 -0000 Subject: [Haiku-bugs] [Haiku] #1828: PackageInstaller is missing an icon In-Reply-To: <040.d38a997ec14c6fc50d062666271e1df5@haiku-os.org> References: <040.d38a997ec14c6fc50d062666271e1df5@haiku-os.org> Message-ID: <049.ac63be99a59c54f15c3166479afeafc5@haiku-os.org> #1828: PackageInstaller is missing an icon --------------------------------------------+------------------------------- Reporter: korli | Owner: sil2100 Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------------+------------------------------- Comment(by korli): Hmm no, the icon is the Expander one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 22:52:20 2008 From: trac at haiku-os.org (scottmc) Date: Wed, 23 Jul 2008 20:52:20 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.2804336978e4f4790d2a5d78e85b1263@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): I've been using r26547 for awhile now without seeing this issue or the one reported in #2523 so I suppose we can close both of these and if they show back up we'll just reopen them, but it seems to be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 23:40:34 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 21:40:34 -0000 Subject: [Haiku-bugs] [Haiku] #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition In-Reply-To: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> References: <044.34411df52ad4097b7b4450f5552c750c@haiku-os.org> Message-ID: <053.5ffe28aee3bfafa21d4f3f7ff7246dbd@haiku-os.org> #2538: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:799): oldRefCount > 0 while attempting to unmount partition ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r26586. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 23:41:03 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 21:41:03 -0000 Subject: [Haiku-bugs] [Haiku] #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel In-Reply-To: <040.07f9632ff503a91bdd3f366026b60cfc@haiku-os.org> References: <040.07f9632ff503a91bdd3f366026b60cfc@haiku-os.org> Message-ID: <049.ec1ec9bb1b8696d7449a7fcc7c420a82@haiku-os.org> #1982: unmount bug: PANIC: vm_page_fault: unhandled page fault in kernel ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r26586. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 23:45:28 2008 From: trac at haiku-os.org (monni) Date: Wed, 23 Jul 2008 21:45:28 -0000 Subject: [Haiku-bugs] [Haiku] #2291: vm_soft_fault when discovering bluetooth devices In-Reply-To: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> References: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> Message-ID: <049.956ffad5665ab84099bc96a68f163956@haiku-os.org> #2291: vm_soft_fault when discovering bluetooth devices --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by monni): crash happens inside bt_discovery got stack trace that contains only <_APP_>:DumpInfo__FPQ29Bluetooth11LocalDevice + 0x01a2 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 23:46:53 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 23 Jul 2008 21:46:53 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.17d527da52b4aceaf349073e4a2e527d@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Replying to [comment:2 stippi]: > The previous BFS and file map bugs could corrupt the file system and file contents quite badly. Are you doing this with a completely fresh image? I could imagine that garbage was either in executable code, or libraries or something like that in such a way that it would still load, but then contained bad instructions. Could this be the case? I don't know what is needed to trigger this panic. Maybe the kernel itself or a driver contained such garbage? I've always use fresh vmware image, so I don't think it's related. I'll see if I manage to trigger it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 23 23:50:41 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 23 Jul 2008 21:50:41 -0000 Subject: [Haiku-bugs] [Haiku] #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) In-Reply-To: <042.192a0aec42da9c9c6d55e28eb579e336@haiku-os.org> References: <042.192a0aec42da9c9c6d55e28eb579e336@haiku-os.org> Message-ID: <051.cae517205d41d8afda581f0b34a6650c@haiku-os.org> #2535: Deadlock discovered: usb explore (legacy mutex) - sh (devfs mutex) ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Honestly I don't remember. Perhaps it was while unpacking a tarball. I'm sorry, but I totally forgot to get a stack trace of the threads. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 00:46:54 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 22:46:54 -0000 Subject: [Haiku-bugs] [Haiku] #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume Message-ID: <044.8315fee1c81a77a90971bc5bf0f75d8f@haiku-os.org> #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume ------------------------------+--------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- If I quickly mount/unmount a BFS volume (easiest way for me was cmd+m/cmd+u in DriveSetup), I get the following kernel panic every single time. {{{ stack trace for thread 210 "bfs block allocator" kernel stack: 0xa105b000 to 0xa105f000 frame caller :function + offset 0 a105eac4 (+ 48) 800564d5 :invoke_debugger_command + 0x00ed 1 a105eaf4 (+ 64) 800562cd :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 a105eb34 (+ 64) 80056615 :invoke_debugger_command_pipe + 0x009d 3 a105eb74 (+ 48) 800574f0 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 a105eba4 (+ 48) 80056ea6 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 a105ebd4 (+ 224) 800588bc :evaluate_debug_command + 0x0088 6 a105ecb4 (+ 64) 80054ab2 :kernel_debugger_loop__Fv + 0x017a 7 a105ecf4 (+ 48) 800554e3 :kernel_debugger + 0x0117 8 a105ed24 (+ 192) 800553c1 :panic + 0x0029 9 a105ede4 (+ 64) 800a62fd :vm_page_fault + 0x00b1 10 a105ee24 (+ 64) 800b304d :page_fault_exception + 0x00b1 11 a105ee64 (+ 12) 800b65a6 :int_bottom + 0x0036 (nearest) iframe at 0xa105ee70 (end = 0xa105eec8) eax 0x1 ebx 0xdeadbef3 ecx 0x915894c0 edx 0xd2 esi 0xd2 edi 0x19d9c ebp 0xa105eed8 esp 0xa105eea4 eip 0x80037c47 eflags 0x10202 vector: 0xe, error code: 0x0 12 a105ee70 (+ 104) 80037c47 :recursive_lock_lock + 0x003f 13 a105eed8 (+ 48) 8079ba3f :Lock__7JournalP11Transaction + 0x0023 14 a105ef08 (+ 48) 8079be05 :Start__11TransactionP6Volumex + 0x0035 15 a105ef38 (+ 160) 8078886e :_Initialize__14BlockAllocatorP14BlockAllocator + 0x032e 16 a105efd8 (+ 32) 8004c7bf :_create_kernel_thread_kentry__Fv + 0x001b 17 a105eff8 (+1593446408) 8004c75c :thread_kthread_exit__Fv + 0x0000 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 00:47:15 2008 From: trac at haiku-os.org (anevilyak) Date: Wed, 23 Jul 2008 22:47:15 -0000 Subject: [Haiku-bugs] [Haiku] #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume In-Reply-To: <044.8315fee1c81a77a90971bc5bf0f75d8f@haiku-os.org> References: <044.8315fee1c81a77a90971bc5bf0f75d8f@haiku-os.org> Message-ID: <053.33bb6ed36bc151b19e2532a3dd496282@haiku-os.org> #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume -------------------------------+-------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by anevilyak): * priority: normal => high * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 05:19:28 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 24 Jul 2008 03:19:28 -0000 Subject: [Haiku-bugs] [Haiku] #2523: Invalid Argument while trying to configure and/or make packages in Haiku In-Reply-To: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> References: <042.ea65a08f83ea9b402de562e8c591d9cc@haiku-os.org> Message-ID: <051.62f7236de06571d04142d9161c876a97@haiku-os.org> #2523: Invalid Argument while trying to configure and/or make packages in Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Seems this still happens in r26573, so it wasn't fixed by r26531 afterall. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 05:25:44 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 24 Jul 2008 03:25:44 -0000 Subject: [Haiku-bugs] [Haiku] #2522: KDL - invalid opcode In-Reply-To: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> References: <042.b29c7e7febff5a4bfd2fc7dd4e2af28f@haiku-os.org> Message-ID: <051.82efb289ad87d6c79b288ea9f72cd164@haiku-os.org> #2522: KDL - invalid opcode ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): This one still happens in r26573 as well, so it wasn't fixed by r26531 afterall. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 10:53:17 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 24 Jul 2008 08:53:17 -0000 Subject: [Haiku-bugs] [Haiku] #2080: Mount point not removed In-Reply-To: <043.139366edbbb73d2d48ce4f81b47abf79@haiku-os.org> References: <043.139366edbbb73d2d48ce4f81b47abf79@haiku-os.org> Message-ID: <052.211d9d707def01e7cf297c1a06edc027@haiku-os.org> #2080: Mount point not removed --------------------------------------+------------------------------------- Reporter: andreasf | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by andreasf): Sounds like r26593 might have resolved this issue? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 11:17:19 2008 From: trac at haiku-os.org (stippi) Date: Thu, 24 Jul 2008 09:17:19 -0000 Subject: [Haiku-bugs] [Haiku] #2080: Mount point not removed In-Reply-To: <043.139366edbbb73d2d48ce4f81b47abf79@haiku-os.org> References: <043.139366edbbb73d2d48ce4f81b47abf79@haiku-os.org> Message-ID: <052.95fe1992bd3f4604a8c2cf486858fe7c@haiku-os.org> #2080: Mount point not removed --------------------------------------+------------------------------------- Reporter: andreasf | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Yes, thanks. Fixed in r26593. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 11:19:13 2008 From: trac at haiku-os.org (mmlr) Date: Thu, 24 Jul 2008 09:19:13 -0000 Subject: [Haiku-bugs] [Haiku] #2352: Keybooard and mouse freeze after hot-plugging USB camera In-Reply-To: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> References: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> Message-ID: <049.2fb4e79173a3fc4f62bd5095c60ecf12@haiku-os.org> #2352: Keybooard and mouse freeze after hot-plugging USB camera --------------------------+------------------------------------------------- Reporter: cebif | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): I added a one second timeout to usb_disk once. Interesting would be to know if it still freezes for that amount when you plug it in. Does it freeze for about a second or does it work continually. If it works continually I'll just close this bug as fixed, otherwise I'll still close it, as the timeout is tracked in another bug already ;-). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 15:42:22 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 13:42:22 -0000 Subject: [Haiku-bugs] [Haiku] #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts In-Reply-To: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> References: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> Message-ID: <049.7cf4fb8cfd05de9a4eceb979b0b65580@haiku-os.org> #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by diver): Ups, sorry, I've kust managed to reproduce it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:14:02 2008 From: trac at haiku-os.org (the ringmaster) Date: Thu, 24 Jul 2008 17:14:02 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps Message-ID: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> #2542: force quit for stubborn apps ----------------------------+----------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- I would like to see some sort of force quit funtionality added to Haiku's window manager. Some applications, if they don't crash, will lock up and there really isn't a way that I know of to quit them when they do this. thanks -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:17:23 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 17:17:23 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.cdfb19bb36625cf24e850afed899d055@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by anevilyak): You can actually do that with things like ProcessController. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:22:17 2008 From: trac at haiku-os.org (koki) Date: Thu, 24 Jul 2008 17:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.d1e40e597a0d8c9fbbd75214b26184e4@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by koki): This functionality already exists: click on the locked up application in the Deskbar while pressing press shift-ctrl-alt, and the app will be killed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:28:37 2008 From: trac at haiku-os.org (the ringmaster) Date: Thu, 24 Jul 2008 17:28:37 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.b7a2c7867bf14cb1b9faefb3412d6983@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by the ringmaster): why can't we have it where when you are clicking on the close buttons and nothing happen. Haiku (or the program that is actually doing the quitting) will automatically force the shutdown of the app(s). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:40:35 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 24 Jul 2008 17:40:35 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.bbf3d9bd7a721ae065291474597f566c@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by emitrax): I'm in favor of adding such as functionality, like they do in GNOME, although applications should never lock up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:42:28 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 17:42:28 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.ae67c83b31a56742fe391b8f21d4f2cd@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by anevilyak): It wouldn't be wise to do that without asking, some apps might take some time to shutdown or whatnot, i.e. if they have to commit back large amounts of data, close network connections or whatnot, so imo this should only be done if the user specifically asks for it. That having been said there's already several ways to do this, I don't see the point in adding another one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:46:13 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 24 Jul 2008 17:46:13 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.62ac21921e785799c6154bef34cc8850@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by emitrax): In GNOME, if an application does not respond and the user keep asking to close the application, the WM pops up a little window and ask esplicitly to kill the application with all the risk of loosing data. I think this way of doing thing is better, and easier to discover for the user, than pressing 3 bottons + a mouse click. How would I know this functionality is already there? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:51:28 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 17:51:28 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.acd2d24345bbe2efe185af3361770547@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by anevilyak): I already mentioned ProcessController also, I'm well aware of how gnome behaves. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:52:07 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 17:52:07 -0000 Subject: [Haiku-bugs] [Haiku] #2544: BTextControl::ResizeToPreferred() Does not resize to propper size Message-ID: <048.ca319343b0dfc9e650de84f23059ea49@haiku-os.org> #2544: BTextControl::ResizeToPreferred() Does not resize to propper size ----------------------------+----------------------------------------------- Reporter: oruizdorantes | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- in kits/bluetooth/UI/PincodeWindow.cpp The following code: fPincodeText = new BTextControl(BRect(rect1.left, rect1.bottom + V_SEPARATION , 0, 0), "pincode TextControl","PIN code:", "", NULL); fPincodeText->ResizeToPreferred(); Seems not to affect to the control -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:51:59 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 17:51:59 -0000 Subject: [Haiku-bugs] [Haiku] #2543: BTextControl::ResizeToPreferred() Does not resize to propper size Message-ID: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> #2543: BTextControl::ResizeToPreferred() Does not resize to propper size ---------------------------+------------------------------------------------ Reporter: oruizdorantes | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ in kits/bluetooth/UI/PincodeWindow.cpp The following code: fPincodeText = new BTextControl(BRect(rect1.left, rect1.bottom + V_SEPARATION , 0, 0), "pincode TextControl","PIN code:", "", NULL); fPincodeText->ResizeToPreferred(); Seems not to affect to the control -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:54:11 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 17:54:11 -0000 Subject: [Haiku-bugs] [Haiku] #2544: BTextControl::ResizeToPreferred() Does not resize to propper size In-Reply-To: <048.ca319343b0dfc9e650de84f23059ea49@haiku-os.org> References: <048.ca319343b0dfc9e650de84f23059ea49@haiku-os.org> Message-ID: <057.457837a684f17d4f95a08d1112306ad1@haiku-os.org> #2544: BTextControl::ResizeToPreferred() Does not resize to propper size -----------------------------+---------------------------------------------- Reporter: oruizdorantes | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2543. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:53:52 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 17:53:52 -0000 Subject: [Haiku-bugs] [Haiku] #2543: BTextControl::ResizeToPreferred() Does not resize to propper size In-Reply-To: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> References: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> Message-ID: <057.ce0a347e797062cb41f6ebe0154decc7@haiku-os.org> #2543: BTextControl::ResizeToPreferred() Does not resize to propper size ----------------------------+----------------------------------------------- Reporter: oruizdorantes | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by oruizdorantes): * status: new => closed * resolution: => duplicate -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:54:48 2008 From: trac at haiku-os.org (mmlr) Date: Thu, 24 Jul 2008 17:54:48 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.c0fa727a7ad860daadc6dc0b8b8afe70@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by mmlr): There are already four ways of doing that: ProcessController (installed by default in the Deskbar), the "vulcan death grip" mentioned by Koki, through the Team Monitor brought up by ctrl-alt-delete and by kill in the Terminal. There might be even more ways I forgot to mention. So can we please refrain from adding yet another method? I take it from your mention of "window manager" that you come from a Unix/Linux background where this feature might be implemented like you outlined. In cases like this though I really find it more appropriate to invest the little time it takes and learn how to do it on a different system, instead of modifying the system to become more similar to something else. Haiku is not Unix/Linux, there is no separate window manager or the like and I don't really see the point of just copying the behaviour of another system if the features are already there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:56:52 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 17:56:52 -0000 Subject: [Haiku-bugs] [Haiku] #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts In-Reply-To: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> References: <040.9067a0d249e84e8475e8c8026ecb5e74@haiku-os.org> Message-ID: <049.558bd74e92a4635e32f4c16b917c000a@haiku-os.org> #2433: [MediaPlayer] moving slider in MediaPlayer leaves artifacts ---------------------------------------+------------------------------------ Reporter: diver | Owner: marcusoverhagen Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by diver): * status: closed => reopened * resolution: fixed => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 19:56:51 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 17:56:51 -0000 Subject: [Haiku-bugs] [Haiku] #2543: BTextControl::ResizeToPreferred() Does not resize to propper size In-Reply-To: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> References: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> Message-ID: <057.1572ad01d8c7886e1fcf85f2eb33c66a@haiku-os.org> #2543: BTextControl::ResizeToPreferred() Does not resize to propper size ---------------------------------+------------------------------------------ Reporter: oruizdorantes | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: closed => reopened * resolution: duplicate => * component: - General => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 20:01:06 2008 From: trac at haiku-os.org (the ringmaster) Date: Thu, 24 Jul 2008 18:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #2092: ActivityMonitor replicant does not display (replicant) handle In-Reply-To: <039.c998637d4b3c20600fa2c0b5cbcfd577@haiku-os.org> References: <039.c998637d4b3c20600fa2c0b5cbcfd577@haiku-os.org> Message-ID: <048.dc2b4b56bfcb211f8ac4e8b4f495af26@haiku-os.org> #2092: ActivityMonitor replicant does not display (replicant) handle ---------------------------------+------------------------------------------ Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by the ringmaster): I was just going to point this out. I see now more people are seeing it. It is an ugly bug when know as little as I do about hidden features of deskbar. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 20:12:23 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 18:12:23 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues Message-ID: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues -----------------------+---------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Recently I changed my noname GeForce4 MX440 with Albatron GeForce4 MX420 I've got all sort of random problems.[[BR]] {{{ "(card A)" 10de:0181 (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a4) "(card B)" 10de:0172 (rev a3) 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 420] (rev a3) }}} Boot logo appeared with "Input is unsupported" message from monitor, though boot logo was just fine. Several seconds later media_addon_server crashed.[[BR]] {{{ Thread 144 called debugger(): Can't register system time source [Switching to team /boot/beos/system/servers/media_addon_server (144) thread media_addon_server (144)] 0xffff0102 in ?? () (gdb) bt #0 0xffff0102 in ?? () #1 0x005255f6 in debugger () from /boot/beos/system/lib/libroot.so #2 0x002063e0 in MediaAddonServer::ReadyToRun () #3 0x002b1965 in BApplication::DispatchMessage () from /boot/beos/system/lib/libbe.so #4 0x002bc011 in BLooper::task_looper () from /boot/beos/system/lib/libbe.so #5 0x002b01dd in BApplication::Run () from /boot/beos/system/lib/libbe.so #6 0x002087e6 in main () (gdb) }}} Only Terminal and Deskbar have been loaded and ProcessController showed constant cpu loading.[[BR]] I typed "top" in terminal and media_server and fxp intr handler (I have an Intel nic) both used 50% of cpu time.[[BR]] With 1st (card A) I never saw this problems. [[BR]] USB mouse didn't work, even after hot replug. [[BR]] Also fonts looked a little better than with 1st card which i described in #2415. [[BR]] Could this font corruption be caused by some combination of modern wide screen and old GeForce card? [[BR]] Then I created new tab in terminal and at this point app_server freezed. I was able to access kdl via F12. Then I rebooted and selected "Use fail-safe video" option, this didn't change anything.[[BR]] When I switched (card B) with (card A), all problems are gone. Also surface of (card B) was very hot. Ubuntu is working stable with this graphic card. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 20:30:16 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 18:30:16 -0000 Subject: [Haiku-bugs] [Haiku] #2291: vm_soft_fault when discovering bluetooth devices In-Reply-To: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> References: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> Message-ID: <049.963bf5e15337ea988e97e5abdf2ee74f@haiku-os.org> #2291: vm_soft_fault when discovering bluetooth devices --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: assigned => closed Comment: Fixed at revision 26612. Calling receive_data() with null pointer for receiver. thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 20:32:35 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 18:32:35 -0000 Subject: [Haiku-bugs] [Haiku] #2291: vm_soft_fault when discovering bluetooth devices In-Reply-To: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> References: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> Message-ID: <049.a11367fc48bb862f84d7ccb25a048af6@haiku-os.org> #2291: vm_soft_fault when discovering bluetooth devices --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: closed => reopened Comment: Fixed at revision 26612. Calling receive_data() with null pointer for receiver. thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 21:50:50 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 24 Jul 2008 19:50:50 -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.6248e4b8d590de8db4c2aeeb50f3b489@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): Ok, progress, I can plug my USB-Compact flash card reader into the AMD Geode board and it sees my 2 Haiku partitions, and auto mounted them. But if I unplug the reader or the card from the reader it drops into KDL. I've attached serial debug from 3 boot sessions, look for the reboot command between them. Unmounting them first and then unplugging works as it's supposed to, so it seems just needs to handle the unplugging condition now. USB mouse works fine, as does USB keyboard. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 22:15:35 2008 From: trac at haiku-os.org (axeld) Date: Thu, 24 Jul 2008 20:15:35 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.850cac049a55175bc4fa370740a5b846@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by axeld): I think we should make the team monitor more accessible instead, maybe an additional Deskbar entry could help with that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:06:01 2008 From: trac at haiku-os.org (axeld) Date: Thu, 24 Jul 2008 21:06:01 -0000 Subject: [Haiku-bugs] [Haiku] #2315: [Workspaces] should have sticky menu (easy) In-Reply-To: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> References: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> Message-ID: <049.8fa81f2610f875dec141db95c312734b@haiku-os.org> #2315: [Workspaces] should have sticky menu (easy) --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:05:43 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 24 Jul 2008 21:05:43 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.bb2a648c65f5f1a5562bae80bb483b6e@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by emitrax): It's not about making Haiku behave like any other linux based OS, it's about making this operation as easy as possible and IMHO the way GNOME handles this, from an user point of view, it is simple the best one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:15:27 2008 From: trac at haiku-os.org (oruizdorantes) Date: Thu, 24 Jul 2008 21:15:27 -0000 Subject: [Haiku-bugs] [Haiku] #2291: vm_soft_fault when discovering bluetooth devices In-Reply-To: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> References: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> Message-ID: <049.286c64c589aab952915f1c166e70971e@haiku-os.org> #2291: vm_soft_fault when discovering bluetooth devices --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: reopened => closed * resolution: => fixed Comment: false reopen due browser refresh -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:23:22 2008 From: trac at haiku-os.org (koki) Date: Thu, 24 Jul 2008 21:23:22 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.b8014c18302aec1b6b06b4286bd91932@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by koki): Being able to Kill a non-responsive app clicking on the close button sounds very logical. Are there any technical issues for not wanting to do it this way, or is it a matter of wanting to stick to BeOS behavior for R1? If the latter, then this could be put on the list of desired features for post R1 releases. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:32:32 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 21:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #2315: [Workspaces] should have sticky menu (easy) In-Reply-To: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> References: <040.9e06b469df6582f988842c61bcf014b8@haiku-os.org> Message-ID: <049.f46327b93f0e946ce20a9e9f105c6c80@haiku-os.org> #2315: [Workspaces] should have sticky menu (easy) --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by diver): There seems to be menu related issue, when one right click Workspaces and menu under mouse cursor will be selected instantly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:33:59 2008 From: trac at haiku-os.org (mmlr) Date: Thu, 24 Jul 2008 21:33:59 -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.5fcdd2fe8c355e9f9c3316de191cedc3@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: No, the KDLs you get this way are perfectly valid. What you do is actively destructive. When it says it could not write back blocks it actually means that you just lost data. A removed device will cause an unmount, as expected, but if there is still unflushed data, a KDL is fine (for now, later for a release it will probably just put the warnings into syslog or pop up an alert). The system cannot know when you are about to unplug the device and therefore it has no way to write the changes back in time (later on we will want to support aggressive write back for removable devices to minimize the impact, however it will never be safe to surprise remove a mounted media). As soon as you unplugged the device it is pretty much too late. Therefore always unmount your volumes (unless they are mounted read-only) before unplugging the media. Anyway this is not a USB or usb_disk issue as they seem to work as expected, that is the devices are working and the unplug triggers an unmount. [[BR]] [[BR]] Closing this ticket as OHCI works now to the required level. Missing is the isochronous support, which is tracked for OHCI and EHCI in ticket #1045. If anyone encounters bugs in OHCI, please open new tickets for them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:36:24 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 21:36:24 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.2c3c604fd5b314fdb0ccad0d8b5be35c@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by diver): I would like to have this feature too, it's seems logical how gnome handles it. I faced too much BeOS apps which will not close (or rather leave deskbar entry) while i would like it to close cleanly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:41:25 2008 From: trac at haiku-os.org (diver) Date: Thu, 24 Jul 2008 21:41:25 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues In-Reply-To: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> References: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> Message-ID: <049.658ef9fe62114d7b9c59b90544c1ec88@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by diver): I don't know which component this ticket should be assigned, so please do. I would like to help with investigation, so feel free to ask me to do more testing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:45:03 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 21:45:03 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues In-Reply-To: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> References: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> Message-ID: <049.fc885a97b7313cf0c9f5225cb421e0ed@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by anevilyak): * component: - General => Drivers/Graphics/nVidia -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:45:51 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 21:45:51 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues In-Reply-To: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> References: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> Message-ID: <049.3969bd60d77f28082b97a8205bf7a198@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues --------------------------------------+------------------------------------- Reporter: diver | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by anevilyak): * owner: axeld => rudolfc Comment: Reassigning to Rudolf so he can check if it is in fact an nvidia driver issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 24 23:49:33 2008 From: trac at haiku-os.org (anevilyak) Date: Thu, 24 Jul 2008 21:49:33 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.5b0339367cfb48c9206e1cddd4edd7cb@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by anevilyak): The problem I have with that approach that I've quite often run into on *nix is that it's very difficult to accurately guess if an app is in fact unresponsive or simply taking some time to complete its shutdown tasks. Especially if the system is under load, having to pull stuff out of swap or whatnot, I've often had it suggest I kill an app that's in the middle of saving a document, where if I'd actually listen to it and click kill I'd probably lose/corrupt my data. Hence I'd prefer this to be more of a deliberate action on the part of the user than automatically suggested. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 02:59:47 2008 From: trac at haiku-os.org (koki) Date: Fri, 25 Jul 2008 00:59:47 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.a579b35be9522dc2a67fb1b0c5253ff7@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by koki): > The problem I have with that approach that I've quite often run into on *nix > is that it's very difficult to accurately guess if an app is in fact > unresponsive or simply taking some time to complete its shutdown tasks... Lack of responsiveness due to an app being busy is very rare in BeOS; it also sort of goes against the Haiku-has-no-hour-glass responsiveness that we preach. So I am not sure this argument holds ground. Strictly from a user POV, clicking on the close button shows an unequivocal intent by the user to terminate the app. Whether this is because the user is done using the app or due to the app becoming unresponsive, it is not relevant. But if you want to avoid situations such as the one you describe, how is using the Team Monitor to kill the app different from clicking on the close button? Does the Team Monitor provide a visual clue of unresponsive apps to the user (I don't remember)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 04:49:01 2008 From: trac at haiku-os.org (the ringmaster) Date: Fri, 25 Jul 2008 02:49:01 -0000 Subject: [Haiku-bugs] [Haiku] #2546: haiku doesn't recognize an AMD phenom processor Message-ID: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> #2546: haiku doesn't recognize an AMD phenom processor ----------------------------+----------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- I have haiku running in vmware on top of my Arch install. I've attached a text file output of sysinfo. You can see the "AMD (null)" in there. Also the pulse application says unknown where the processor name should be. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 10:28:52 2008 From: trac at haiku-os.org (meanwhile) Date: Fri, 25 Jul 2008 08:28:52 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.9ffbd8c83bceeea4228a37b8d65f929d@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by meanwhile): @Koki: From memory, the Team Monitor shows the unresponsive app in red vs. the responsive apps in black from the active apps list. If this particular app is then selected from the list, the Team Monitor tells the user about its suspicion of the app "seeming to behave badly". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 11:14:14 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 25 Jul 2008 09:14:14 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues In-Reply-To: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> References: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> Message-ID: <049.8ca58befb3b09cad6bbe9da03ec0e942@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues --------------------------------------+------------------------------------- Reporter: diver | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by mmlr): The fxp interrupt handler taking up all the CPU time was reported in bug #2084 already. Interesting is that this only happens with a specific setup of the mentioned cards here. This might hint into the direction of interrupt handling in the shared/non-shared case. I doubt that it's an nVidia problem in that case and would rather think it's caused by the ipro100 driver (that the fxp interrupt handler belongs to). Could you check the output of the "ints" command in KDL and also check what IRQs are assigned to the cards in each configuration. You can find that in the early part of the syslog where the PCI info is dumped. Check the "interrupt_line" of both devices, the graphics card and the network card to see if they are the same with either configuration. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 11:58:13 2008 From: trac at haiku-os.org (cebif) Date: Fri, 25 Jul 2008 09:58:13 -0000 Subject: [Haiku-bugs] [Haiku] #2352: Keybooard and mouse freeze after hot-plugging USB camera In-Reply-To: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> References: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> Message-ID: <049.db5a251ce1175837bd7ba9f67b0e4a2f@haiku-os.org> #2352: Keybooard and mouse freeze after hot-plugging USB camera --------------------------+------------------------------------------------- Reporter: cebif | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by cebif): Quote from mmir: "I added a one second timeout to usb_disk once. Interesting would be to know if it still freezes for that amount when you plug it in. Does it freeze for about a second or does it work continually" There is no freeze when I mount the camera. It appears on the desktop instantly and I can move the mouse straight away to double click the icon and open it. There is another thing that might be a different bug; if I have the mount settings to "Automatic Disk Mounting" set at "All Disks" I still have to manually mount it. Also if I have "Disk Mounting During Boot" set at "All Disks" it does not appear on the desktop after booting. I have to manually mount it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 12:01:57 2008 From: trac at haiku-os.org (mmlr) Date: Fri, 25 Jul 2008 10:01:57 -0000 Subject: [Haiku-bugs] [Haiku] #2352: Keybooard and mouse freeze after hot-plugging USB camera In-Reply-To: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> References: <040.d090c87ff84feb479ec9fd3e67ca4890@haiku-os.org> Message-ID: <049.a4b6451565cf68d794e0f8236740f181@haiku-os.org> #2352: Keybooard and mouse freeze after hot-plugging USB camera --------------------------+------------------------------------------------- Reporter: cebif | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: In that case I'll close it as fixed. The mount thing is definitely another bug. Please check if it is already reported and if not open a new bug report for that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 12:52:12 2008 From: trac at haiku-os.org (emitrax) Date: Fri, 25 Jul 2008 10:52:12 -0000 Subject: [Haiku-bugs] [Haiku] #2118: Bash Upgrade In-Reply-To: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> References: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> Message-ID: <051.c33c401c6044f4d5e1004c05a9e2f53e@haiku-os.org> #2118: Bash Upgrade ----------------------------------------------+----------------------------- Reporter: emitrax | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Applications/Command Line Tools | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by emitrax): I managed to build bash-3.2 within Haiku and it seems to work fine, beside the termcap warning similar to the ftp one when running the binary. Anyway, anyone aware of any test I can do before going further with the Jamfile? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 20:41:13 2008 From: trac at haiku-os.org (oco) Date: Fri, 25 Jul 2008 18:41:13 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 Message-ID: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 --------------------------+------------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Here is a little patch to compile BeServed under Visual Studio 2008 (the Windows part). Unfortunately, it is not possible to compile under a free version of Visual Studio as BeServed require MFC's, only available in full versions. As it is difficult to get the needed tools, i have uploaded some binaries : - the server : http://olivier.coursiere.free.fr/download/BeServed.exe - the control panel application (for configuration) : http://olivier.coursiere.free.fr/download/FileSharing.cpl I have not tested much, but it should work. The patch is only a compile fix. Visual Studio as also complaining about mixed end of line in some files (authentication.cpp and BeServed.cpp). I don't know which style should be chose for those Windows only files. All this stuff was waiting on my computer since a few months... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 25 21:18:17 2008 From: trac at haiku-os.org (oco) Date: Fri, 25 Jul 2008 19:18:17 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 In-Reply-To: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> References: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> Message-ID: <047.877f98df7440cb10a704f001a6e00055@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by oco): A few notes about installation : - copy the control panel application in the c:\windows\system32 directory - run "BeServerd.exe -install" from the command line to install BeServed as a Windows service. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 01:16:56 2008 From: trac at haiku-os.org (scottmc) Date: Fri, 25 Jul 2008 23:16:56 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization Message-ID: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I have a drive with 2 haiku partitions on it. I named them Haiku-CF1 and Haiku-CF2. I then unmounted CF2 and used Drive Setup to initialize CF2. After it was done it falsely reported that CF1 was successfully initialized. Screenshots attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 01:25:53 2008 From: trac at haiku-os.org (anevilyak) Date: Fri, 25 Jul 2008 23:25:53 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization In-Reply-To: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> References: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> Message-ID: <051.0aa923b05adea639b7453a3262d11bba@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization --------------------------------------+------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by anevilyak): * owner: axeld => stippi * component: - General => Applications/DriveSetup Comment: Switching components -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 09:15:40 2008 From: trac at haiku-os.org (humdinger) Date: Sat, 26 Jul 2008 07:15:40 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.c3e185c8bc504c204046e6477278327e@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by humdinger): IMO, I'd be best to merge ProcessController and TeamMonitor, i.e. CTRL+ALT+DEL invokes ProcessController with a windowed interface and the features of TeamMonitor (Kill, Reboot, Restart Desktop, marking unresponsive teams red etc.). Maybe with tabbed views and also the ActivityMonitor replicant integrated. And, why not if it's possible, invoke this new ?ber-TeamController when a QuitRequested doesn't respond in a reasonable time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 19:06:44 2008 From: trac at haiku-os.org (idefix) Date: Sat, 26 Jul 2008 17:06:44 -0000 Subject: [Haiku-bugs] [Haiku] #2549: Can't change video mode when monitor can't display current video mode Message-ID: <041.26e7c8bcc69ce7ad54f7c6bf25988948@haiku-os.org> #2549: Can't change video mode when monitor can't display current video mode --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I have a nVidia TNT2 card which used to have a CRT monitor connected to it, working at 1024x768 @ 85 Hz. Now I have connected a LCD monitor, but it doesn't like the 85 Hz so it displays a warning message. No matter what I try, I can't set the video mode to 60 Hz without connecting the CRT monitor again. At first I tried to set in the bootloader the 'safe video mode' to 800x600. Haiku boots then with the bootscreen at 800x600 @ 60 Hz, but as soon the desktop loads the video mode is set to 1024x768 @ 85 Hz. Secondly I tried to set the 'safe video mode' to 800x600 and also set the 'use save video mode'-flag. Haiku boots then into a desktop at 800x600 @ 60 Hz, but as it is using the vesa driver I can't change the video mode for the nVidia driver. So when it boots normally again, it's 1024x768 @ 85 Hz. Thirdly I remembered the [Ctrl]-[Alt]-[Shift]-[F12] keystroke which in BeOS causes the display to VGA mode @ 60 Hz. In Haiku however I go into the kernel debugger (as I discovered in the serial output, the monitor still displayed a warning). At this moment I can't see how I can change the video mode without connecting the CRT monitor. A couple of solutions to this problem:[[BR]] First, the nVidia driver should detect that the new monitor can't handle the current video mode. See bug #1696. Secondly the [Ctrl]-[Alt]-[Shift]-[F12] keystroke should work the same as in BeOS. Thirdly, as the bootloader already differentiate between the 'safe video mode'-setting with the 'use save video mode'-flag on or off, the setting with the flag off could be used to tell the nVidia driver the new resolution. The 'save video mode' should then be renamed to 'video mode'. When it has a value other than default, that video mode would be sent to the videocard-driver. If the 'use save video mode'-flag is on, that value would be used by the vesa-driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 19:51:13 2008 From: trac at haiku-os.org (stippi) Date: Sat, 26 Jul 2008 17:51:13 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.2d6f5f1a4f7a2c6439183c8874cf5477@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by stippi): I am with emitrax and koki on this one. It should be possible to get it working in a reliable way (time out in Deskbar for reply message, time outs in window quit loop in BApplication, some magic in app_server when closing windows, etc). Misbehaving apps do happen and the hidden features to kill them are not helpful to non-techy users. If an app does take a long time to close, it should anticipate this case and behave in a way that does not irritate the user. Either it closes it's windows and keeps saving, or better yet, it needs to display a progress bar for long lasting operations. The user is not to be irritated, no matter what. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 20:36:16 2008 From: trac at haiku-os.org (korli) Date: Sat, 26 Jul 2008 18:36:16 -0000 Subject: [Haiku-bugs] [Haiku] #2546: haiku doesn't recognize an AMD phenom processor In-Reply-To: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> References: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> Message-ID: <058.d34882785b69492724d4dc163dfede56@haiku-os.org> #2546: haiku doesn't recognize an AMD phenom processor -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by korli): Applied a patch in r26642. Please test. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 20:58:08 2008 From: trac at haiku-os.org (stippi) Date: Sat, 26 Jul 2008 18:58:08 -0000 Subject: [Haiku-bugs] [Haiku] #2548: Drive Setup reports wrong volume name after an initilization In-Reply-To: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> References: <042.3b9be49b4797cc568de5cea15739bd4e@haiku-os.org> Message-ID: <051.71ba7e9937365cb99a10d4c374d7c527@haiku-os.org> #2548: Drive Setup reports wrong volume name after an initilization --------------------------------------+------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by stippi): * status: new => assigned Comment: r26643 should fix this, can you confirm? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 26 22:12:36 2008 From: trac at haiku-os.org (stippi) Date: Sat, 26 Jul 2008 20:12:36 -0000 Subject: [Haiku-bugs] [Haiku] #2550: [ReiserFS] PANIC: Had reserved page, but there is none! Message-ID: <041.9681d17a4cea51d751205cc3ecc19f9d@haiku-os.org> #2550: [ReiserFS] PANIC: Had reserved page, but there is none! ---------------------------+------------------------------------------------ Reporter: stippi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ When copying large data from a ReiserFS volume, eventually I get this panic, seems to be reproducable every time. The used memory goes up and up in ProcessController, maybe this is actually a leak. Here is the stack crawl: {{{ ... kernel>:panic kernel>:vm_page_allocate_page kernel>:map_tmap kernel>:vm_map_page kernel>:vm_create_annonymous_area kernel>:create_area kernel>:area_allocate_pages kernel>:CreateSlab kernel>:object_cache_reserved_internal kernel>:object_cache_alloc kernel>:Allocate kernel>:NewBlock kernel>:get_cached_block kernel>:block_cache_get_etc kernel>:block_cache_get reiserfs>:_GetBlock reiserfs>:_SetTo reiserfs>:_ReadBlock reiserfs>:GetBlock(BlockCache) reiserfs>:GetBlock(Tree) reiserfs>:_ReadIndirectItem reiserfs>:ReadAt reiserfs>:reiserfs_read }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 27 12:29:20 2008 From: trac at haiku-os.org (diver) Date: Sun, 27 Jul 2008 10:29:20 -0000 Subject: [Haiku-bugs] [Haiku] #2350: Segment violation in FillRectNoClipping when booting on eeePC In-Reply-To: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> References: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> Message-ID: <052.736f530bb52ab307b6189b484d3f5efd@haiku-os.org> #2350: Segment violation in FillRectNoClipping when booting on eeePC ---------------------------------+------------------------------------------ Reporter: exparrot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by diver): User [http://qube.ru/users/olegms OlegMS] reports that he gets the same crash with his Dell inspiron 1300 backtrace is identical to already attached IMAGE_00174.jpg. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 27 12:44:13 2008 From: trac at haiku-os.org (stippi) Date: Sun, 27 Jul 2008 10:44:13 -0000 Subject: [Haiku-bugs] [Haiku] #2350: Segment violation in FillRectNoClipping when booting on eeePC In-Reply-To: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> References: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> Message-ID: <052.15953ab449d41ac385bf1bd9e5d2a29f@haiku-os.org> #2350: Segment violation in FillRectNoClipping when booting on eeePC ---------------------------------+------------------------------------------ Reporter: exparrot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by stippi): The problem seems to be that app_server and the graphics driver are out of sync with regards to the current resolution. In another words, the app_server thinks that the driver is in another resolution than it actually is. Then it writes to the frame buffer out of bounds which leads to the crash. From what I hear from mmlr, the problem can be worked around by copying a resolution settings file which forces an initial mode switch and syncs app_server to the driver or vice versa. (mmlr, does a vesa settings file suffice?) I have not yet had a chance to look into the root cause of the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 27 14:47:26 2008 From: trac at haiku-os.org (mmlr) Date: Sun, 27 Jul 2008 12:47:26 -0000 Subject: [Haiku-bugs] [Haiku] #2350: Segment violation in FillRectNoClipping when booting on eeePC In-Reply-To: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> References: <043.ce9d77215cfc36086efc92cb4307b7f9@haiku-os.org> Message-ID: <052.22846b7cdcb765c9722a6a24d6e53fe1@haiku-os.org> #2350: Segment violation in FillRectNoClipping when booting on eeePC ---------------------------------+------------------------------------------ Reporter: exparrot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by mmlr): The way I work around it is to boot in safe video mode by booth setting "Use Failsafe Video Mode" and choosing a video mode in the boot menu, then when booted use the Screen preflet to select any mode different than the current one (doesn't matter). This will cause a settings file to be written. The resolution used when rebooting is then chosen based on the preferred mode of the graphics driver disregarding the settings file. The issue seems that the preferred mode isn't used when there is no settings file at all. What I could imagine is that when there is a settings file it will try to set that mode, which will fail for the intel driver (as it only allows the native resolution) and then fall back to the preferred mode. If there is no settings file, it won't try setting the mode and won't fall back either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 28 11:50:51 2008 From: trac at haiku-os.org (axeld) Date: Mon, 28 Jul 2008 09:50:51 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.4e36c917b5be154bfed0825a16e2e2d4@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by axeld): I think this is happening so rarely that I don't feel it's necessary to add a special solution to Haiku. As a novice user, it's probably easier to deal with a minimized app than to decide whether or not an app should be killed. I would rather argue that applications that tend to deadlock should be fixed. FYI OS X does not have any other way to kill an app besides the team monitor. Besides for Finder, I never had to use it there, either. On BeOS, I usually only need it for Firefox. On Ubuntu and Windows (which both have that feature), I have to use it quite often, though. Let's please just not get there :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 28 12:53:23 2008 From: trac at haiku-os.org (stippi) Date: Mon, 28 Jul 2008 10:53:23 -0000 Subject: [Haiku-bugs] [Haiku] #2542: force quit for stubborn apps In-Reply-To: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> References: <049.f835ce873c0b1f52f7b1f99ee51ac006@haiku-os.org> Message-ID: <058.b503263f13afeab509ef53b5da16d5b4@haiku-os.org> #2542: force quit for stubborn apps -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by stippi): I am pretty sure that no one disagrees that effort should be put into applications for them to always behave well. But this is about how "the computer" behaves in the case something goes wrong. And this separates good software from ok software. Somewhere, sometimes, something will go wrong which someone didn't anticipate in his software, and for that case is this feature. It's an OS versus applications thing, the OS is our job while applications may not be in our control. If some proposed solution does not work in some case, that's one thing, but I think the feature itself is still desirable and maybe there is a way to make it work reliably. IMHO we should think about it and keep this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 28 21:58:54 2008 From: trac at haiku-os.org (emitrax) Date: Mon, 28 Jul 2008 19:58:54 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick Message-ID: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick ----------------------------------+----------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- A picture is worth a thousand word. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 28 23:21:21 2008 From: trac at haiku-os.org (axeld) Date: Mon, 28 Jul 2008 21:21:21 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.8d71181fa2c42ea4df6194b29769c0bd@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): Actually I don't see what would be wrong there besides the volumes, or is it just what you mean? :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 28 23:26:37 2008 From: trac at haiku-os.org (emitrax) Date: Mon, 28 Jul 2008 21:26:37 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.194ccba48ddde50906682817567b0eb9@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by emitrax): Yes, the volumes in the Desktop directory is what I meant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 05:45:39 2008 From: trac at haiku-os.org (the ringmaster) Date: Tue, 29 Jul 2008 03:45:39 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.818e994bb6a080b23120fd9c2346b2e5@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by the ringmaster): looks normal to me. Those volumes that it shows last are located on your desktop. If you want to move a file or copy a file to your desktop, i do believe you can just hit "Desktop" the second from last in the hierarchy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 09:42:25 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 29 Jul 2008 07:42:25 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.431be2abd0541e3835a58c2c7764cc4f@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by emitrax): Nope. That's not my desktop. That's the desktop directory in the bfs volume that is in the USB stick. I initialize it and name it Haiku as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 09:49:04 2008 From: trac at haiku-os.org (koki) Date: Tue, 29 Jul 2008 07:49:04 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.210f4c9f44a3ca8f19bcdc996f5f0009@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by koki): Isn't this because all BFS volumes have a home folder by default? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 09:59:48 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 29 Jul 2008 07:59:48 -0000 Subject: [Haiku-bugs] [Haiku] #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick In-Reply-To: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> References: <042.e6e01440def40c6dd3c1403a7fc32d47@haiku-os.org> Message-ID: <051.fe4ca351307474d525db70c4d34c7bf1@haiku-os.org> #2551: [Tracker]: Copy To shows wrong content of Desktop directory when selecting a bfs volume on a usb stick -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by emitrax): Naming the volume in a different way result in the correct behavior. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 11:52:21 2008 From: trac at haiku-os.org (axeld) Date: Tue, 29 Jul 2008 09:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #2543: BTextControl::ResizeToPreferred() Does not resize to propper size In-Reply-To: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> References: <048.c46d021fc2f56a8cfcc623a73fba4254@haiku-os.org> Message-ID: <057.4e1078be82bb4ad627be048c6d8374af@haiku-os.org> #2543: BTextControl::ResizeToPreferred() Does not resize to propper size ---------------------------------+------------------------------------------ Reporter: oruizdorantes | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by axeld): Does this code work in BeOS? Looking at the code in BTextControl, it should work fine, though. Can you provide a minimal test program that reproduces the problem? There are some test apps in src/tests/servers/app that might provide you with a usable shell (like view_state). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 15:32:19 2008 From: trac at haiku-os.org (emitrax) Date: Tue, 29 Jul 2008 13:32:19 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 Message-ID: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- It actually happens a few revision ago and I don't know how to trigger it again. {{{ PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 3595 "grep" kernel stack: 0x90b50000 to 0x90b54000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b53644 (+ 48) 800542cd :invoke_debugger_command + 0x00ed 1 90b53674 (+ 64) 800540c5 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 90b536b4 (+ 64) 8005440d :invoke_debugger_command_pipe + 0x009d 3 90b536f4 (+ 48) 800552e8 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 90b53724 (+ 48) 80054c9e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 90b53754 (+ 224) 800566b4 :evaluate_debug_command + 0x0088 6 90b53834 (+ 64) 800528de :kernel_debugger_loop__Fv + 0x017a 7 90b53874 (+ 48) 8005330f :kernel_debugger + 0x0117 8 90b538a4 (+ 192) 800531ed :panic + 0x0029 9 90b53964 (+ 64) 80037758 :_mutex_lock + 0x00e0 10 90b539a4 (+ 48) 8003763f :mutex_switch_lock + 0x005b 11 90b539d4 (+ 48) 800a98b1 :vm_cache_acquire_locked_page_cache + 0x0085 12 90b53a04 (+ 64) 800ace95 :steal_page__FP7vm_pageb + 0x0019 13 90b53a44 (+ 128) 800ad076 :steal_pages__FPP7vm_pageUlb + 0x0066 14 90b53ac4 (+ 48) 800adec7 :vm_page_reserve_pages + 0x0097 15 90b53af4 (+ 256) 800a6a0d :vm_soft_fault__FUlbT1 + 0x0225 16 90b53bf4 (+ 64) 800a6586 :vm_page_fault + 0x002e 17 90b53c34 (+ 64) 800b341d :page_fault_exception + 0x00b1 18 90b53c74 (+ 12) 800b6976 :int_bottom + 0x0036 (nearest) iframe at 0x90b53c80 (end = 0x90b53cd8) eax 0x0 ebx 0x18034000 ecx 0x400 edx 0x914ceaec esi 0x8ef80000 edi 0x18034000 ebp 0x90b53d04 esp 0x90b53cb4 eip 0x800b6608 eflags 0x210206 vector: 0xe, error code: 0x2 19 90b53c80 (+ 132) 800b6608 :arch_cpu_user_memcpy + 0x001e (nearest) 20 90b53d04 (+ 176) 8002e326 :cache_io__FPvT0xUlPUlb + 0x03d2 21 90b53db4 (+ 64) 8002ea1d :file_cache_read + 0x002d 22 90b53df4 (+ 80) 8059246e :ReadAt__5InodexPUcPUl + 0x00da 23 90b53e44 (+ 64) 8059ed6e :bfs_read__FP9fs_volumeP8fs_vnodePvxT2PUl + 0x0076 24 90b53e84 (+ 64) 8008a340 :file_read__FP15file_descriptorxPvPUl + 0x0044 25 90b53ec4 (+ 80) 8007ad8d :common_user_io__FixPvUlb + 0x017d 26 90b53f14 (+ 48) 8007b228 :_user_read + 0x0028 27 90b53f44 (+ 100) 800b6ba2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b53fa8 (end = 0x90b54000) eax 0x7c ebx 0x2be908 ecx 0x7ffeee20 edx 0xffff0104 esi 0x8000 edi 0x0 ebp 0x7ffeee5c esp 0x90b53fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 28 90b53fa8 (+ 0) ffff0104 29 7ffeee5c (+ 80) 002028a0 <_APP_>:_term_after + 0x04b8 (nearest) 30 7ffeeeac (+ 64) 00203416 <_APP_>:_term_after + 0x102e (nearest) 31 7ffeeeec (+ 48) 00203883 <_APP_>:_term_after + 0x149b (nearest) 32 7ffeef1c (+ 96) 00204eba <_APP_>:main + 0x0ef2 33 7ffeef7c (+ 48) 00202307 <_APP_>:_start + 0x005b 34 7ffeefac (+ 48) 001008ea 80289:runtime_loader_seg0ro at 0x00100000 + 0x8ea 35 7ffeefdc (+ 0) 7ffeefec 80288:grep_main_stack at 0x7efef000 + 0xffffec kdebug> mutex 0x90cc4ed0 mutex 0x90cc4ed0: name: vm_cache flags: 0x0 holder: 3595 waiting threads: kdebug> thread bonnie++ THREAD: 0x914b2000 id: 1375 (0x55f) name: "bonnie++" all_next: 0x91480000 team_next: 0x00000000 q_next: 0x800fdc00 priority: 10 (next 10) state: waiting next_state: waiting cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: mutex 0x90b8e2d4 fault_handler: 0x00000000 args: 0x90bbeca8 0x00000000 entry: 0x80047f6c team: 0x90c05744, "bonnie++" exit.sem: 15474 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 30812 kernel_stack_base: 0x90b20000 user_stack_area: 30814 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 46889683 user_time: 31341082 flags: 0x200 architecture dependant section: esp: 0x90b23c68 ss: 0x00000010 fpu_state at 0x914b2380 kdebug> bt 1375 stack trace for thread 1375 "bonnie++" kernel stack: 0x90b20000 to 0x90b24000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b23cc4 (+ 32) 800404a2 :context_switch__FP6threadT0 + 0x0026 1 90b23ce4 (+ 64) 8004070c :scheduler_reschedule + 0x0248 2 90b23d24 (+ 48) 8003780c :_mutex_lock + 0x0194 3 90b23d54 (+ 48) 80036c43 :recursive_lock_lock + 0x0053 4 90b23d84 (+ 48) 80597a1f :Lock__7JournalP11Transaction + 0x0023 5 90b23db4 (+ 48) 80597de5 :Start__11TransactionP6Volumex + 0x0035 6 90b23de4 (+ 64) 805925d5 :WriteAt__5InodeR11TransactionxPCUcPUl + 0x013d 7 90b23e24 (+ 96) 8059ee44 :bfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x00cc 8 90b23e84 (+ 64) 8008a398 :file_write__FP15file_descriptorxPCvPUl + 0x0044 9 90b23ec4 (+ 80) 8007ad8d :common_user_io__FixPvUlb + 0x017d 10 90b23f14 (+ 48) 8007b280 :_user_write + 0x0028 11 90b23f44 (+ 100) 800b6ba2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b23fa8 (end = 0x90b24000) eax 0x7e ebx 0x2f4908 ecx 0x7ffeeb90 edx 0xffff0104 esi 0x7ffeec3c edi 0xb4b ebp 0x7ffeebcc esp 0x90b23fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 12 90b23fa8 (+ 0) ffff0104 13 7ffeebcc (+ 48) 00204cde :unknown + 0x4cde 14 7ffeebfc (+ 128) 00203a17 :unknown + 0x3a17 15 7ffeec7c (+ 768) 0020356b :unknown + 0x356b 16 7ffeef7c (+ 48) 0020290f :unknown + 0x290f 17 7ffeefac (+ 48) 001008ea 30815:runtime_loader_seg0ro at 0x00100000 + 0x8ea 18 7ffeefdc (+ 0) 7ffeefec 30814:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> mutex 0x90b8e2d4 mutex 0x90b8e2d4: name: bfs journal flags: 0x0 holder: 1377 waiting threads: 1375 1376 kdebug> bt 1376 stack trace for thread 1376 "bonnie++" kernel stack: 0x90b24000 to 0x90b28000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b27cc4 (+ 32) 800404a2 :context_switch__FP6threadT0 + 0x0026 1 90b27ce4 (+ 64) 8004070c :scheduler_reschedule + 0x0248 2 90b27d24 (+ 48) 8003780c :_mutex_lock + 0x0194 3 90b27d54 (+ 48) 80036c43 :recursive_lock_lock + 0x0053 4 90b27d84 (+ 48) 80597a1f :Lock__7JournalP11Transaction + 0x0023 5 90b27db4 (+ 48) 80597de5 :Start__11TransactionP6Volumex + 0x0035 6 90b27de4 (+ 64) 805925d5 :WriteAt__5InodeR11TransactionxPCUcPUl + 0x013d 7 90b27e24 (+ 96) 8059ee44 :bfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x00cc 8 90b27e84 (+ 64) 8008a398 :file_write__FP15file_descriptorxPCvPUl + 0x0044 9 90b27ec4 (+ 80) 8007ad8d :common_user_io__FixPvUlb + 0x017d 10 90b27f14 (+ 48) 8007b280 :_user_write + 0x0028 11 90b27f44 (+ 100) 800b6ba2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b27fa8 (end = 0x90b28000) eax 0x7e ebx 0x2f4908 ecx 0x7ffeeb90 edx 0xffff0104 esi 0x7ffeec3c edi 0x96d ebp 0x7ffeebcc esp 0x90b27fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 12 90b27fa8 (+ 0) ffff0104 13 7ffeebcc (+ 48) 00204cde :unknown + 0x4cde 14 7ffeebfc (+ 128) 00203a17 :unknown + 0x3a17 15 7ffeec7c (+ 768) 0020356b :unknown + 0x356b 16 7ffeef7c (+ 48) 0020290f :unknown + 0x290f 17 7ffeefac (+ 48) 001008ea 30846:runtime_loader_seg0ro at 0x00100000 + 0x8ea 18 7ffeefdc (+ 0) 7ffeefec 30845:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> bt 1377 stack trace for thread 1377 "bonnie++" kernel stack: 0x90b28000 to 0x90b2c000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b2b6e4 (+ 32) 800404a2 :context_switch__FP6threadT0 + 0x0026 1 90b2b704 (+ 64) 8004070c :scheduler_reschedule + 0x0248 2 90b2b744 (+ 64) 80041a54 :switch_sem_etc + 0x0390 3 90b2b784 (+ 48) 8004166c :acquire_sem + 0x001c 4 90b2b7b4 (+ 112) 806dfe96 :periph_read_write + 0x020a 5 90b2b824 (+ 80) 806dfc33 :periph_read + 0x003f 6 90b2b874 (+ 64) 806db974 :das_read__FP15das_handle_infoPC9phys_vecsxUlUlPUl + 0x0040 7 90b2b8b4 (+ 160) 805ab964 :block_io_readv_int + 0x042c 8 90b2b954 (+ 80) 805ac140 :block_io_read + 0x0040 9 90b2b9a4 (+ 80) 800623ad :devfs_read__FP9fs_volumeP8fs_vnodePvxT2PUl + 0x0121 10 90b2b9f4 (+ 64) 8008a340 :file_read__FP15file_descriptorxPvPUl + 0x0044 11 90b2ba34 (+ 96) 8007b665 :_kern_read + 0x0145 12 90b2ba94 (+ 64) 800bfc5a :read_pos + 0x0036 13 90b2bad4 (+ 80) 8002a06f :get_cached_block__FP11block_cachexPbb + 0x010b 14 90b2bb24 (+ 80) 8002ce0e :block_cache_get_etc + 0x004e 15 90b2bb74 (+ 64) 80583a9a :SetTo__15AllocationBlockR15AllocationGroupUs + 0x00ae 16 90b2bbb4 (+ 128) 80584b09 :AllocateBlocks__14BlockAllocatorR11TransactionlUsUsUsR9block_run + 0x017d 17 90b2bc34 (+ 80) 80584f5f :Allocate__14BlockAllocatorR11TransactionP5InodexR9block_runUs + 0x018f 18 90b2bc84 (+ 304) 80592c50 :_GrowStream__5InodeR11Transactionx + 0x0300 19 90b2bdb4 (+ 48) 80594249 :SetFileSize__5InodeR11Transactionx + 0x0069 20 90b2bde4 (+ 64) 80592643 :WriteAt__5InodeR11TransactionxPCUcPUl + 0x01ab 21 90b2be24 (+ 96) 8059ee44 :bfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x00cc 22 90b2be84 (+ 64) 8008a398 :file_write__FP15file_descriptorxPCvPUl + 0x0044 23 90b2bec4 (+ 80) 8007ad8d :common_user_io__FixPvUlb + 0x017d 24 90b2bf14 (+ 48) 8007b280 :_user_write + 0x0028 25 90b2bf44 (+ 100) 800b6ba2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b2bfa8 (end = 0x90b2c000) eax 0x7e ebx 0x2f4908 ecx 0x7ffeeb90 edx 0xffff0104 esi 0x7ffeec3c edi 0xaf9 ebp 0x7ffeebcc esp 0x90b2bfdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 26 90b2bfa8 (+ 0) ffff0104 27 7ffeebcc (+ 48) 00204cde :unknown + 0x4cde 28 7ffeebfc (+ 128) 00203a17 :unknown + 0x3a17 29 7ffeec7c (+ 768) 0020356b :unknown + 0x356b 30 7ffeef7c (+ 48) 0020290f :unknown + 0x290f 31 7ffeefac (+ 48) 001008ea 30877:runtime_loader_seg0ro at 0x00100000 + 0x8ea 32 7ffeefdc (+ 0) 7ffeefec 30876:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> thread 1377 THREAD: 0x914b6800 id: 1377 (0x561) name: "bonnie++" all_next: 0x91487800 team_next: 0x00000000 q_next: 0x800fdc00 priority: 10 (next 10) state: ready next_state: ready cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: fault_handler: 0x00000000 args: 0x90b71618 0x00000000 entry: 0x80047f6c team: 0x90c05e88, "bonnie++" exit.sem: 15504 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 30874 kernel_stack_base: 0x90b28000 user_stack_area: 30876 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 47384764 user_time: 31419292 flags: 0x0 architecture dependant section: esp: 0x90b2b688 ss: 0x00000010 fpu_state at 0x914b6b80 kdebug> continue }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 29 18:28:06 2008 From: trac at haiku-os.org (axeld) Date: Tue, 29 Jul 2008 16:28:06 -0000 Subject: [Haiku-bugs] [Haiku] #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume In-Reply-To: <044.8315fee1c81a77a90971bc5bf0f75d8f@haiku-os.org> References: <044.8315fee1c81a77a90971bc5bf0f75d8f@haiku-os.org> Message-ID: <053.383fc9833ffbb247d14f091f09f554cf@haiku-os.org> #2541: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbefb, ip 0x80037c47 when rapidly mount/unmounting a volume -------------------------------+-------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r26679. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 01:38:04 2008 From: trac at haiku-os.org (bonefish) Date: Tue, 29 Jul 2008 23:38:04 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 In-Reply-To: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> References: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> Message-ID: <051.0a4d7b8fc8e77d16c535e29d49ba1475@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): The problem is relatively simple: cache_io() uses user_memcpy() with the cache lock held. The user memory is not yet mapped, and vm_page_reserve_pages() coincidently tries to steal a page from the same cache. Possible solutions: - Lock the memory upfront. - Mark the pages busy, unlock the cache, user_memcpy(), lock the cache, mark pages unbusy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 05:06:39 2008 From: trac at haiku-os.org (the ringmaster) Date: Wed, 30 Jul 2008 03:06:39 -0000 Subject: [Haiku-bugs] [Haiku] #2546: haiku doesn't recognize an AMD phenom processor In-Reply-To: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> References: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> Message-ID: <058.b8f01273f8624751f9930717c6a53d94@haiku-os.org> #2546: haiku doesn't recognize an AMD phenom processor -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by the ringmaster): This does seem to be fixed now thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 05:10:09 2008 From: trac at haiku-os.org (the ringmaster) Date: Wed, 30 Jul 2008 03:10:09 -0000 Subject: [Haiku-bugs] [Haiku] #2553: date format doesn't refresh when preferences are changed Message-ID: <049.f8c6598658c0fc96cb5ceb2532eb5b6f@haiku-os.org> #2553: date format doesn't refresh when preferences are changed ----------------------------------+----------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- As a test I changed the file manager preference from 12 hr to 24. As you can see the new is overlapping the old. I have the right component right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 05:43:10 2008 From: trac at haiku-os.org (NateEag) Date: Wed, 30 Jul 2008 03:43:10 -0000 Subject: [Haiku-bugs] [Haiku] #1355: [GLTeapot] last frame stays on screen at close In-Reply-To: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> References: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> Message-ID: <049.c9b9f7f349869c449844dd0be0626096@haiku-os.org> #1355: [GLTeapot] last frame stays on screen at close ------------------------------+--------------------------------------------- Reporter: diver | Owner: phoudoin Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by NateEag): * cc: Nate4D at gmail.com (added) Comment: I noticed this problem playing with Haiku on my Ubuntu box in Qemu, and poked at it until I found what I believe is the correct solution. I'm a total novice at Haiku/BeOS, though, so I'm not sure this is the right fix. When comparing GLTeapot with some other apps, though, I noticed that the "Quit" menu item posted a B_QUIT_REQUESTED message directly, which does not appear to be the usual approach. I'm attaching a patch that solves the problem for me, modeled after the way mediaplayer handles quitting via the menu. I assume that quitting via the close button (Alt+W) is handled by BWindow or similar, and thus, that path didn't suffer from this problem, nor would it in any application as long as BWindow does things right? Anyway, if someone has the time, please take a look at the patch and see whether it looks like the right approach. There are some stylistic things I'm not too sure about, so please suggest any appropriate alterations. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 10:07:14 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 30 Jul 2008 08:07:14 -0000 Subject: [Haiku-bugs] [Haiku] #2553: date format doesn't refresh when preferences are changed In-Reply-To: <049.f8c6598658c0fc96cb5ceb2532eb5b6f@haiku-os.org> References: <049.f8c6598658c0fc96cb5ceb2532eb5b6f@haiku-os.org> Message-ID: <058.3967b162f8dc127d5e20734d38b191a3@haiku-os.org> #2553: date format doesn't refresh when preferences are changed -----------------------------------+---------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: Duplicate of bug #1816. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 10:07:41 2008 From: trac at haiku-os.org (mmlr) Date: Wed, 30 Jul 2008 08:07:41 -0000 Subject: [Haiku-bugs] [Haiku] #1816: Tracker doesn't properly redraw modified date column when date&time format changed (seems easy) In-Reply-To: <038.2f568491c4d0c08de3126845fafd75e7@haiku-os.org> References: <038.2f568491c4d0c08de3126845fafd75e7@haiku-os.org> Message-ID: <047.273086062bfb362b3b288624d1ddf05d@haiku-os.org> #1816: Tracker doesn't properly redraw modified date column when date&time format changed (seems easy) -----------------------------+---------------------------------------------- Reporter: hma | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -----------------------------+---------------------------------------------- Comment(by mmlr): See the duplicate ticket #2553 for a screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 10:39:45 2008 From: trac at haiku-os.org (stippi) Date: Wed, 30 Jul 2008 08:39:45 -0000 Subject: [Haiku-bugs] [Haiku] #2546: haiku doesn't recognize an AMD phenom processor In-Reply-To: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> References: <049.cb7903cb2eecfdcb913e9ab560cb4b1a@haiku-os.org> Message-ID: <058.172febd5cc57872d16724e681cdf8b3f@haiku-os.org> #2546: haiku doesn't recognize an AMD phenom processor -----------------------------+---------------------------------------------- Reporter: the ringmaster | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for checking back! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 10:44:16 2008 From: trac at haiku-os.org (stippi) Date: Wed, 30 Jul 2008 08:44:16 -0000 Subject: [Haiku-bugs] [Haiku] #1355: [GLTeapot] last frame stays on screen at close In-Reply-To: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> References: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> Message-ID: <049.15163eb266390707d778eab858692e92@haiku-os.org> #1355: [GLTeapot] last frame stays on screen at close ------------------------------+--------------------------------------------- Reporter: diver | Owner: phoudoin Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by stippi): The previous method of posting B_QUIT_REQUESTED directly is perfectly allowed. I would look for this problem in the area where the app_server and BDirectWindows communicate the clipping state. There should be a race condition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 12:17:04 2008 From: trac at haiku-os.org (stim) Date: Wed, 30 Jul 2008 10:17:04 -0000 Subject: [Haiku-bugs] [Haiku] #1477: Network preference app crashes when no device present. In-Reply-To: <041.7e68ebaf24cda8a106367d0b448d0ff5@haiku-os.org> References: <041.7e68ebaf24cda8a106367d0b448d0ff5@haiku-os.org> Message-ID: <050.f2ca0de77dfa791151795a736ec62407@haiku-os.org> #1477: Network preference app crashes when no device present. ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by stim): * cc: stimbrown at fastmail.com.au (added) Comment: Is this still a problem? If I remove all NICs from the VMWare config and run the network preferences, there is no crash for me - or am I misunderstanding the ticket? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 14:31:45 2008 From: trac at haiku-os.org (PieterPanman) Date: Wed, 30 Jul 2008 12:31:45 -0000 Subject: [Haiku-bugs] [Haiku] #1632: Extended syslog capabilities in KDL In-Reply-To: <044.6ac11a63a86ec99c5571203023261f3f@haiku-os.org> References: <044.6ac11a63a86ec99c5571203023261f3f@haiku-os.org> Message-ID: <053.0039db27aa3de43ed44cf184c67e4f07@haiku-os.org> #1632: Extended syslog capabilities in KDL ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by PieterPanman): I suppose r26684 fixed 2), so this ticket can be closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 15:11:47 2008 From: trac at haiku-os.org (NateEag) Date: Wed, 30 Jul 2008 13:11:47 -0000 Subject: [Haiku-bugs] [Haiku] #1355: [GLTeapot] last frame stays on screen at close In-Reply-To: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> References: <040.737ff0af8a5b492c0eb342df8e8072bf@haiku-os.org> Message-ID: <049.056eb87cb822f0a71bc7a1e4e6a5099d@haiku-os.org> #1355: [GLTeapot] last frame stays on screen at close ------------------------------+--------------------------------------------- Reporter: diver | Owner: phoudoin Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by NateEag): Okay. Thanks for the info. I don't have tons of free time, but I may keep looking at this when I do have the time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 17:03:13 2008 From: trac at haiku-os.org (axeld) Date: Wed, 30 Jul 2008 15:03:13 -0000 Subject: [Haiku-bugs] [Haiku] #1632: Extended syslog capabilities in KDL In-Reply-To: <044.6ac11a63a86ec99c5571203023261f3f@haiku-os.org> References: <044.6ac11a63a86ec99c5571203023261f3f@haiku-os.org> Message-ID: <053.9763f5aac53216a9b7afac1e2b842700@haiku-os.org> #1632: Extended syslog capabilities in KDL ----------------------------+----------------------------------------------- Reporter: pieterpan | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: Unscheduled Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Indeed, thanks for the note! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 21:13:58 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 30 Jul 2008 19:13:58 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 In-Reply-To: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> References: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> Message-ID: <051.b513cbb5765e2b3e5e2abadca07e4a7c@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): I actually mananaged to triggered it again by simply running bonnie++. I tried with the attached patch as you said. Please review. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 21:34:01 2008 From: trac at haiku-os.org (kaliber) Date: Wed, 30 Jul 2008 19:34:01 -0000 Subject: [Haiku-bugs] [Haiku] #2554: send gdb changes upstream Message-ID: <042.f689b93996a594b444647a9de6bf7587@haiku-os.org> #2554: send gdb changes upstream --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- {{{ svn diff svn://svn.berlios.de/haiku/haiku/vendor/gdb/6.3/ svn://svn.berlios.de/haiku/haiku/trunk/src/bin/gdb }}} and maybe update from 6.3 to 6.8? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 21:59:04 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 30 Jul 2008 19:59:04 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null Message-ID: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null -----------------------+---------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I haven't investigate it yet, just posting to get some thoughs. It happened while running the following bonnie++ plus a simple script that works on attributes, but I don't think it's relevant. {{{ condition variable: 0x90b0fd38 PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null Welcome to Kernel Debugging Land... Thread 3072 "bonnie++" running on CPU 0 kdebug> bt stack trace for thread 3072 "bonnie++" kernel stack: 0x90b08000 to 0x90b0c000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b0b984 (+ 48) 8005493d :invoke_debugger_command + 0x00ed 1 90b0b9b4 (+ 64) 80054735 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 90b0b9f4 (+ 64) 80054a7d :invoke_debugger_command_pipe + 0x009d 3 90b0ba34 (+ 48) 80055958 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 90b0ba64 (+ 48) 8005530e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 90b0ba94 (+ 224) 80056d24 :evaluate_debug_command + 0x0088 6 90b0bb74 (+ 64) 80052db6 :kernel_debugger_loop__Fv + 0x01a2 7 90b0bbb4 (+ 48) 8005394b :kernel_debugger + 0x0117 8 90b0bbe4 (+ 192) 80053829 :panic + 0x0029 9 90b0bca4 (+ 80) 800310c3 :Publish__17ConditionVariablePCvPCc + 0x011b 10 90b0bcf4 (+ 112) 800b05f1 :vm_page_write_modified_page_range + 0x027d 11 90b0bd64 (+ 32) 800b0757 :vm_page_write_modified_pages + 0x002b 12 90b0bd84 (+ 48) 800adad3 :WriteModified__7VMCache + 0x002f 13 90b0bdb4 (+ 32) 8002efd4 :file_cache_sync + 0x0018 14 90b0bdd4 (+ 240) 8059460b :Sync__5Inode + 0x002b 15 90b0bec4 (+ 48) 8059d731 :bfs_fsync__FP9fs_volumeP8fs_vnode + 0x0021 16 90b0bef4 (+ 48) 8008cb68 :common_sync__Fib + 0x004c 17 90b0bf24 (+ 32) 80091378 :_user_fsync + 0x0018 18 90b0bf44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b0bfa8 (end = 0x90b0c000) eax 0x60 ebx 0x2f4908 ecx 0x7ffeca40 edx 0xffff0104 esi 0x7ffeec3c edi 0x7d04 ebp 0x7ffeca6c esp 0x90b0bfdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 19 90b0bfa8 (+ 0) ffff0104 20 7ffeca6c (+ 48) 00205368 94564:bonnie++_seg0ro at 0x00200000 + 0x5368 21 7ffeca9c (+ 96) 002046dd 94564:bonnie++_seg0ro at 0x00200000 + 0x46dd 22 7ffecafc (+ 48) 00207776 94564:bonnie++_seg0ro at 0x00200000 + 0x7776 23 7ffecb2c (+ 64) 002078da 94564:bonnie++_seg0ro at 0x00200000 + 0x78da 24 7ffecb6c (+8320) 00204809 94564:bonnie++_seg0ro at 0x00200000 + 0x4809 25 7ffeebec (+ 144) 00203e7a 94564:bonnie++_seg0ro at 0x00200000 + 0x3e7a 26 7ffeec7c (+ 768) 0020356b 94564:bonnie++_seg0ro at 0x00200000 + 0x356b 27 7ffeef7c (+ 48) 0020290f 94564:bonnie++_seg0ro at 0x00200000 + 0x290f 28 7ffeefac (+ 48) 001008ea 94559:runtime_loader_seg0ro at 0x00100000 + 0x8ea 29 7ffeefdc (+ 0) 7ffeefec 94574:bonnie++_main_stack at 0x7efef000 + 0xffffeca kdebug> team TEAM: 0x90c04d14 id: 3072 (0xc00) name: 'bonnie++' args: './bonnie++ -m haiku -u 0 -b -d ../Desktop/' next: 0x90c0445c parent: 0x90c04000 (id = 199) children: 0x00000000 num_threads: 1 state: 1 flags: 0x0 io_context: 0x90bd7a40 address_space: 0x957bbf00 main_thread: 0x914b5800 thread_list: 0x914b5800 group_id: 199 session_id: 190 kdebug> teams team id parent name 0x90b7ce88 186 0x90b7ca2c Terminal 0x90c04174 94 0x90b7c000 media_server 0x90b7c000 1 0x00000000 kernel_team 0x90c04ba0 3071 0x90c04000 bonnie++ 0x90c04d14 3072 0x90c04000 bonnie++ 0x90c0445c 96 0x90b7c000 midi_server 0x90c04e88 3073 0x90c04000 bonnie++ 0x90b7c174 190 0x90b7ce88 sh 0x90c045d0 97 0x90b7c000 print_server 0x90c04a2c 3079 0x90c048b8 dd 0x90c04744 134 0x90c04174 media_addon_server 0x90c04000 199 0x90b7c174 bonnie++ 0x90b7c8b8 76 0x90b7c000 syslog_daemon 0x90c042e8 201 0x90b7ce88 Terminal 0x90b7cba0 80 0x90b7c744 input_server 0x90b7c2e8 49 0x90b7c000 registrar 0x90c048b8 205 0x90c042e8 sh 0x90b7c45c 54 0x90b7c000 debug_server 0x90b7c5d0 55 0x90b7c000 net_server 0x90b7c744 56 0x90b7c000 app_server 0x90b7ca2c 88 0x90b7c000 Tracker 0x90b7cd14 90 0x90b7c000 Deskbar kdebug> bt 3071 stack trace for thread 3071 "bonnie++" kernel stack: 0x90b04000 to 0x90b08000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b07704 (+ 32) 800409da :context_switch__FP6threadT0 + 0x0026 1 90b07724 (+ 64) 80040c44 :scheduler_reschedule + 0x0248 2 90b07764 (+ 64) 80041f2c :switch_sem_etc + 0x0368 3 90b077a4 (+ 48) 80041b6c :acquire_sem + 0x001c 4 90b077d4 (+ 112) 806dfe96 :periph_read_write + 0x020a 5 90b07844 (+ 80) 806dfc7f :periph_write + 0x003f 6 90b07894 (+ 64) 806db9c0 :das_write__FP15das_handle_infoPC9phys_vecsxUlUlPUl + 0x0040 7 90b078d4 (+ 160) 805abf64 :block_io_writev_int + 0x04d4 8 90b07974 (+ 80) 805ac224 :block_io_write + 0x0040 9 90b079c4 (+ 96) 800636e8 :devfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0178 10 90b07a24 (+ 192) 800892ae :common_file_io_vec_pages__FP5vnodePvPC11file_io_vecUlPC5iovecUlPUlPUlT7b + 0x02da 11 90b07ae4 (+ 80) 80089c05 :write_file_io_vec_pages + 0x0059 12 90b07b34 (+ 224) 8059d149 :bfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0141 13 90b07c14 (+ 64) 8008a8e7 :vfs_write_pages + 0x0037 14 90b07c54 (+ 64) 8002ff80 :Write__12VMVnodeCachexPC5iovecUlPUl + 0x002c 15 90b07c94 (+ 80) 800af5a8 :write_page__FP7vm_page + 0x0074 16 90b07ce4 (+ 128) 800b0617 :vm_page_write_modified_page_range + 0x02a3 17 90b07d64 (+ 32) 800b0757 :vm_page_write_modified_pages + 0x002b 18 90b07d84 (+ 48) 800adad3 :WriteModified__7VMCache + 0x002f 19 90b07db4 (+ 32) 8002efd4 :file_cache_sync + 0x0018 20 90b07dd4 (+ 240) 8059460b :Sync__5Inode + 0x002b 21 90b07ec4 (+ 48) 8059d731 :bfs_fsync__FP9fs_volumeP8fs_vnode + 0x0021 22 90b07ef4 (+ 48) 8008cb68 :common_sync__Fib + 0x004c 23 90b07f24 (+ 32) 80091378 :_user_fsync + 0x0018 24 90b07f44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b07fa8 (end = 0x90b08000) eax 0x60 ebx 0x2f4908 ecx 0x7ffeca40 edx 0xffff0104 esi 0x7ffeec3c edi 0x4648 ebp 0x7ffeca6c esp 0x90b07fdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 25 90b07fa8 (+ 0) ffff0104 26 7ffeca6c (+ 48) 00205368 94547:bonnie++_seg0ro at 0x00200000 + 0x5368 27 7ffeca9c (+ 96) 002046dd 94547:bonnie++_seg0ro at 0x00200000 + 0x46dd 28 7ffecafc (+ 48) 00207776 94547:bonnie++_seg0ro at 0x00200000 + 0x7776 29 7ffecb2c (+ 64) 002078da 94547:bonnie++_seg0ro at 0x00200000 + 0x78da 30 7ffecb6c (+8320) 00204809 94547:bonnie++_seg0ro at 0x00200000 + 0x4809 31 7ffeebec (+ 144) 00203e7a 94547:bonnie++_seg0ro at 0x00200000 + 0x3e7a 32 7ffeec7c (+ 768) 0020356b 94547:bonnie++_seg0ro at 0x00200000 + 0x356b 33 7ffeef7c (+ 48) 0020290f 94547:bonnie++_seg0ro at 0x00200000 + 0x290f 34 7ffeefac (+ 48) 001008ea 94542:runtime_loader_seg0ro at 0x00100000 + 0x8ea 35 7ffeefdc (+ 0) 7ffeefec 94557:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> thread bonnie++ THREAD: 0x914b4000 id: 3071 (0xbff) name: "bonnie++" all_next: 0x91492000 team_next: 0x00000000 q_next: 0x914b2800 priority: 10 (next 10) state: waiting next_state: waiting cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: semaphore 154 fault_handler: 0x00000000 args: 0x957bd7f8 0x00000000 entry: 0x8004841c team: 0x90c04ba0, "bonnie++" exit.sem: 56031 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 94558 kernel_stack_base: 0x90b04000 user_stack_area: 94557 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 139263 user_time: 8814 flags: 0x0 architecture dependant section: esp: 0x90b076a8 ss: 0x00000010 fpu_state at 0x914b4380 kdebug> sem 154 SEM: 0x923eff48 id: 154 (0x9a) name: 'ccb_sem' owner: 1 count: -1 queue: 3071 last acquired by: 3071, count: 1 last released by: 35, count: 1 kdebug> bt 3079 stack trace for thread 3079 "dd" kernel stack: 0x90b00000 to 0x90b04000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b03c54 (+ 32) 800409da :context_switch__FP6threadT0 + 0x0026 1 90b03c74 (+ 64) 80040c44 :scheduler_reschedule + 0x0248 2 90b03cb4 (+ 32) 8004d71d :thread_yield + 0x0059 3 90b03cd4 (+ 144) 801f9792 :reseed + 0x0056 4 90b03d64 (+ 208) 801faba0 :random_read + 0x0064 5 90b03e34 (+ 80) 80062add :devfs_read__FP9fs_volumeP8fs_vnodePvxT2PUl + 0x0121 6 90b03e84 (+ 64) 8008bddc :file_read__FP15file_descriptorxPvPUl + 0x0044 7 90b03ec4 (+ 80) 8007c849 :common_user_io__FixPvUlb + 0x017d 8 90b03f14 (+ 48) 8007cce4 :_user_read + 0x0028 9 90b03f44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b03fa8 (end = 0x90b04000) eax 0x7c ebx 0x2b7908 ecx 0x7ffeee50 edx 0xffff0104 esi 0x1802f000 edi 0x200 ebp 0x7ffeee8c esp 0x90b03fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 10 90b03fa8 (+ 0) ffff0104 11 7ffeee8c (+ 48) 002024ae <_APP_>:usage + 0x070e (nearest) 12 7ffeeebc (+ 64) 002037c4 <_APP_>:usage + 0x1a24 (nearest) 13 7ffeeefc (+ 128) 00204078 <_APP_>:main + 0x03f0 14 7ffeef7c (+ 48) 00201c7b <_APP_>:_start + 0x005b 15 7ffeefac (+ 48) 001008ea 94771:runtime_loader_seg0ro at 0x00100000 + 0x8ea 16 7ffeefdc (+ 0) 7ffeefec 94770:dd_main_stack at 0x7efef000 + 0xffffec kdebug> thead 3079 THREAD: 0x914b2800 id: 3079 (0xc07) name: "dd" all_next: 0x91462000 team_next: 0x00000000 q_next: 0x91488800 priority: 10 (next 10) state: ready next_state: ready cpu: 0x00000000 sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: fault_handler: 0x00000000 args: 0x957bd870 0x00000000 entry: 0x8004841c team: 0x90c04a2c, "dd" exit.sem: 56150 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 94768 kernel_stack_base: 0x90b00000 user_stack_area: 94770 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 478002 user_time: 89609 flags: 0x200 architecture dependant section: esp: 0x90b03bf8 ss: 0x00000010 fpu_state at 0x914b2b80 kdebug> continue ide: ide_timeout() bus 0x90b86660 PANIC: Condition variable 0x90b0fd38 not published, found: 0x90b0bd38 Welcome to Kernel Debugging Land... Thread 3073 "bonnie++" running on CPU 0 kdebug> thread 3073 THREAD: 0x914b4800 id: 3073 (0xc01) name: "bonnie++" all_next: 0x91484000 team_next: 0x00000000 q_next: 0x913eb800 priority: 10 (next 10) state: running next_state: ready cpu: 0x801156c0 (0) sig_pending: 0x0 (blocked: 0x0) in_kernel: 1 waiting for: fault_handler: 0x80054958 args: 0x957bd7f8 0x00000000 entry: 0x8004841c team: 0x90c04e88, "bonnie++" exit.sem: 56042 exit.status: 0x0 (No error) exit.reason: 0x0 exit.signal: 0x0 exit.waiters: kernel_stack_area: 94592 kernel_stack_base: 0x90b0c000 user_stack_area: 94591 user_stack_base: 0x7efef000 user_local_storage: 0x7ffef000 kernel_errno: 0x0 (No error) kernel_time: 103630 user_time: 8516 flags: 0x0 architecture dependant section: esp: 0x90b0f6a8 ss: 0x00000010 fpu_state at 0x914b4b80 kdebug> bt 3073 stack trace for thread 3073 "bonnie++" kernel stack: 0x90b0c000 to 0x90b10000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b0f984 (+ 48) 8005493d :invoke_debugger_command + 0x00ed 1 90b0f9b4 (+ 64) 80054735 :invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079 2 90b0f9f4 (+ 64) 80054a7d :invoke_debugger_command_pipe + 0x009d 3 90b0fa34 (+ 48) 80055958 :_ParseCommandPipe__16ExpressionParserRi + 0x0234 4 90b0fa64 (+ 48) 8005530e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 5 90b0fa94 (+ 224) 80056d24 :evaluate_debug_command + 0x0088 6 90b0fb74 (+ 64) 80052db6 :kernel_debugger_loop__Fv + 0x01a2 7 90b0fbb4 (+ 48) 8005394b :kernel_debugger + 0x0117 8 90b0fbe4 (+ 192) 80053829 :panic + 0x0029 9 90b0fca4 (+ 80) 80031206 :Unpublish__17ConditionVariableb + 0x00da 10 90b0fcf4 (+ 112) 800b06e2 :vm_page_write_modified_page_range + 0x036e 11 90b0fd64 (+ 32) 800b0757 :vm_page_write_modified_pages + 0x002b 12 90b0fd84 (+ 48) 800adad3 :WriteModified__7VMCache + 0x002f 13 90b0fdb4 (+ 32) 8002efd4 :file_cache_sync + 0x0018 14 90b0fdd4 (+ 240) 8059460b :Sync__5Inode + 0x002b 15 90b0fec4 (+ 48) 8059d731 :bfs_fsync__FP9fs_volumeP8fs_vnode + 0x0021 16 90b0fef4 (+ 48) 8008cb68 :common_sync__Fib + 0x004c 17 90b0ff24 (+ 32) 80091378 :_user_fsync + 0x0018 18 90b0ff44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b0ffa8 (end = 0x90b10000) eax 0x60 ebx 0x2f4908 ecx 0x7ffeca40 edx 0xffff0104 esi 0x7ffeec3c edi 0xb95a ebp 0x7ffeca6c esp 0x90b0ffdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 19 90b0ffa8 (+ 0) ffff0104 20 7ffeca6c (+ 48) 00205368 94581:bonnie++_seg0ro at 0x00200000 + 0x5368 21 7ffeca9c (+ 96) 002046dd 94581:bonnie++_seg0ro at 0x00200000 + 0x46dd 22 7ffecafc (+ 48) 00207776 94581:bonnie++_seg0ro at 0x00200000 + 0x7776 23 7ffecb2c (+ 64) 002078da 94581:bonnie++_seg0ro at 0x00200000 + 0x78da 24 7ffecb6c (+8320) 00204809 94581:bonnie++_seg0ro at 0x00200000 + 0x4809 25 7ffeebec (+ 144) 00203e7a 94581:bonnie++_seg0ro at 0x00200000 + 0x3e7a 26 7ffeec7c (+ 768) 0020356b 94581:bonnie++_seg0ro at 0x00200000 + 0x356b 27 7ffeef7c (+ 48) 0020290f 94581:bonnie++_seg0ro at 0x00200000 + 0x290f 28 7ffeefac (+ 48) 001008ea 94576:runtime_loader_seg0ro at 0x00100000 + 0x8ea 29 7ffeefdc (+ 0) 7ffeefec 94591:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> bt 3071 stack trace for thread 3071 "bonnie++" kernel stack: 0x90b04000 to 0x90b08000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b07704 (+ 32) 800409da :context_switch__FP6threadT0 + 0x0026 1 90b07724 (+ 64) 80040c44 :scheduler_reschedule + 0x0248 2 90b07764 (+ 64) 80041f2c :switch_sem_etc + 0x0368 3 90b077a4 (+ 48) 80041b6c :acquire_sem + 0x001c 4 90b077d4 (+ 112) 806dfe96 :periph_read_write + 0x020a 5 90b07844 (+ 80) 806dfc7f :periph_write + 0x003f 6 90b07894 (+ 64) 806db9c0 :das_write__FP15das_handle_infoPC9phys_vecsxUlUlPUl + 0x0040 7 90b078d4 (+ 160) 805abf64 :block_io_writev_int + 0x04d4 8 90b07974 (+ 80) 805ac224 :block_io_write + 0x0040 9 90b079c4 (+ 96) 800636e8 :devfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0178 10 90b07a24 (+ 192) 800892ae :common_file_io_vec_pages__FP5vnodePvPC11file_io_vecUlPC5iovecUlPUlPUlT7b + 0x02da 11 90b07ae4 (+ 80) 80089c05 :write_file_io_vec_pages + 0x0059 12 90b07b34 (+ 224) 8059d149 :bfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0141 13 90b07c14 (+ 64) 8008a8e7 :vfs_write_pages + 0x0037 14 90b07c54 (+ 64) 8002ff80 :Write__12VMVnodeCachexPC5iovecUlPUl + 0x002c 15 90b07c94 (+ 80) 800af5a8 :write_page__FP7vm_page + 0x0074 16 90b07ce4 (+ 128) 800b0617 :vm_page_write_modified_page_range + 0x02a3 17 90b07d64 (+ 32) 800b0757 :vm_page_write_modified_pages + 0x002b 18 90b07d84 (+ 48) 800adad3 :WriteModified__7VMCache + 0x002f 19 90b07db4 (+ 32) 8002efd4 :file_cache_sync + 0x0018 20 90b07dd4 (+ 240) 8059460b :Sync__5Inode + 0x002b 21 90b07ec4 (+ 48) 8059d731 :bfs_fsync__FP9fs_volumeP8fs_vnode + 0x0021 22 90b07ef4 (+ 48) 8008cb68 :common_sync__Fib + 0x004c 23 90b07f24 (+ 32) 80091378 :_user_fsync + 0x0018 24 90b07f44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b07fa8 (end = 0x90b08000) eax 0x60 ebx 0x2f4908 ecx 0x7ffeca40 edx 0xffff0104 esi 0x7ffeec3c edi 0x4648 ebp 0x7ffeca6c esp 0x90b07fdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 25 90b07fa8 (+ 0) ffff0104 26 7ffeca6c (+ 48) 00205368 94547:bonnie++_seg0ro at 0x00200000 + 0x5368 27 7ffeca9c (+ 96) 002046dd 94547:bonnie++_seg0ro at 0x00200000 + 0x46dd 28 7ffecafc (+ 48) 00207776 94547:bonnie++_seg0ro at 0x00200000 + 0x7776 29 7ffecb2c (+ 64) 002078da 94547:bonnie++_seg0ro at 0x00200000 + 0x78da 30 7ffecb6c (+8320) 00204809 94547:bonnie++_seg0ro at 0x00200000 + 0x4809 31 7ffeebec (+ 144) 00203e7a 94547:bonnie++_seg0ro at 0x00200000 + 0x3e7a 32 7ffeec7c (+ 768) 0020356b 94547:bonnie++_seg0ro at 0x00200000 + 0x356b 33 7ffeef7c (+ 48) 0020290f 94547:bonnie++_seg0ro at 0x00200000 + 0x290f 34 7ffeefac (+ 48) 001008ea 94542:runtime_loader_seg0ro at 0x00100000 + 0x8ea 35 7ffeefdc (+ 0) 7ffeefec 94557:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> bt 3072 stack trace for thread 3072 "bonnie++" kernel stack: 0x90b08000 to 0x90b0c000 user stack: 0x7efef000 to 0x7ffef000 frame caller :function + offset 0 90b0b704 (+ 32) 800409da :context_switch__FP6threadT0 + 0x0026 1 90b0b724 (+ 64) 80040c44 :scheduler_reschedule + 0x0248 2 90b0b764 (+ 64) 80041f2c :switch_sem_etc + 0x0368 3 90b0b7a4 (+ 48) 80041b6c :acquire_sem + 0x001c 4 90b0b7d4 (+ 112) 806dfe96 :periph_read_write + 0x020a 5 90b0b844 (+ 80) 806dfc7f :periph_write + 0x003f 6 90b0b894 (+ 64) 806db9c0 :das_write__FP15das_handle_infoPC9phys_vecsxUlUlPUl + 0x0040 7 90b0b8d4 (+ 160) 805abf64 :block_io_writev_int + 0x04d4 8 90b0b974 (+ 80) 805ac224 :block_io_write + 0x0040 9 90b0b9c4 (+ 96) 800636e8 :devfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0178 10 90b0ba24 (+ 192) 800892ae :common_file_io_vec_pages__FP5vnodePvPC11file_io_vecUlPC5iovecUlPUlPUlT7b + 0x02da 11 90b0bae4 (+ 80) 80089c05 :write_file_io_vec_pages + 0x0059 12 90b0bb34 (+ 224) 8059d149 :bfs_write_pages__FP9fs_volumeP8fs_vnodePvxPC5iovecUlPUl + 0x0141 13 90b0bc14 (+ 64) 8008a8e7 :vfs_write_pages + 0x0037 14 90b0bc54 (+ 64) 8002ff80 :Write__12VMVnodeCachexPC5iovecUlPUl + 0x002c 15 90b0bc94 (+ 80) 800af5a8 :write_page__FP7vm_page + 0x0074 16 90b0bce4 (+ 128) 800b0617 :vm_page_write_modified_page_range + 0x02a3 17 90b0bd64 (+ 32) 800b0757 :vm_page_write_modified_pages + 0x002b 18 90b0bd84 (+ 48) 800adad3 :WriteModified__7VMCache + 0x002f 19 90b0bdb4 (+ 32) 8002efd4 :file_cache_sync + 0x0018 20 90b0bdd4 (+ 240) 8059460b :Sync__5Inode + 0x002b 21 90b0bec4 (+ 48) 8059d731 :bfs_fsync__FP9fs_volumeP8fs_vnode + 0x0021 22 90b0bef4 (+ 48) 8008cb68 :common_sync__Fib + 0x004c 23 90b0bf24 (+ 32) 80091378 :_user_fsync + 0x0018 24 90b0bf44 (+ 100) 800b8472 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90b0bfa8 (end = 0x90b0c000) eax 0x60 ebx 0x2f4908 ecx 0x7ffeca40 edx 0xffff0104 esi 0x7ffeec3c edi 0x7d04 ebp 0x7ffeca6c esp 0x90b0bfdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 25 90b0bfa8 (+ 0) ffff0104 26 7ffeca6c (+ 48) 00205368 94564:bonnie++_seg0ro at 0x00200000 + 0x5368 27 7ffeca9c (+ 96) 002046dd 94564:bonnie++_seg0ro at 0x00200000 + 0x46dd 28 7ffecafc (+ 48) 00207776 94564:bonnie++_seg0ro at 0x00200000 + 0x7776 29 7ffecb2c (+ 64) 002078da 94564:bonnie++_seg0ro at 0x00200000 + 0x78da 30 7ffecb6c (+8320) 00204809 94564:bonnie++_seg0ro at 0x00200000 + 0x4809 31 7ffeebec (+ 144) 00203e7a 94564:bonnie++_seg0ro at 0x00200000 + 0x3e7a 32 7ffeec7c (+ 768) 0020356b 94564:bonnie++_seg0ro at 0x00200000 + 0x356b 33 7ffeef7c (+ 48) 0020290f 94564:bonnie++_seg0ro at 0x00200000 + 0x290f 34 7ffeefac (+ 48) 001008ea 94559:runtime_loader_seg0ro at 0x00100000 + 0x8ea 35 7ffeefdc (+ 0) 7ffeefec 94574:bonnie++_main_stack at 0x7efef000 + 0xffffec kdebug> reboot }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 22:16:58 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 30 Jul 2008 20:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null In-Reply-To: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> References: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> Message-ID: <051.175b4752294b9800af9b5fba5f1367c6@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): After a quick look, it seems like the state of the page is set to BUSY without holding the sPageLock. While that may cause a race condition, I'm not sure if it's the cause. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 22:34:11 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 30 Jul 2008 20:34:11 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null In-Reply-To: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> References: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> Message-ID: <051.f06f73895d4cf9d1e8efc31735f9fc64@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): While I was at it I did a grep of "page->state = " src/system/kernel/vm/* and src/system/kernel/cache/* and checked those places where the state is set without holding the page lock. Patch attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 23:30:23 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 30 Jul 2008 21:30:23 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null In-Reply-To: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> References: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> Message-ID: <051.91cf349c49eb74969a285722bd410b49@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by bonefish): Did you by any chance encounter this problem while using the patch in #2552? At least theoretically it could be the cause, since it would set the page state to modified twice in the write case, the first time without the cache lock held. If after the first time one of the fsync() threads gets the lock, it might mark the page busy and publish a condition variable. Afterwards cache_io() would set the page to modified again, allowing the second fsync() thread to mark it busy and publish another condition variable (first panic()). After continuing the first fsync() thread would try to unpublish its condition variable (second panic()). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 30 23:35:49 2008 From: trac at haiku-os.org (bonefish) Date: Wed, 30 Jul 2008 21:35:49 -0000 Subject: [Haiku-bugs] [Haiku] #2554: send gdb changes upstream In-Reply-To: <042.f689b93996a594b444647a9de6bf7587@haiku-os.org> References: <042.f689b93996a594b444647a9de6bf7587@haiku-os.org> Message-ID: <051.2089db9f36b0a94538252fc262e68204@haiku-os.org> #2554: send gdb changes upstream ---------------------------+------------------------------------------------ Reporter: kaliber | Owner: bonefish Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * priority: normal => low Comment: I don't think the maintainers will accept a patch against version 6.3. Furthermore they won't accept the patch as is, since it doesn't follow their coding style. So the procedure is to update first, complete the implementation (there's still stuff missing), adjust the coding style, and afterwards send the patch. I plan to do that eventually, but I'm not in a particular hurry. I'm also not quite sure whether it might be better to add ptrace support to Haiku after all. This would simplify the port significantly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 00:39:29 2008 From: trac at haiku-os.org (emitrax) Date: Wed, 30 Jul 2008 22:39:29 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null In-Reply-To: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> References: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> Message-ID: <051.f5789ec3513017f8b6ee5502e1a1618c@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Actually yes. The patch is applied. What do you suggest? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 01:22:51 2008 From: trac at haiku-os.org (kvdman) Date: Wed, 30 Jul 2008 23:22:51 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.d5fb450287e5f5a424e60a287e4a06cf@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by kvdman): Please close this: [http://www.haikuware.com/20080730230/latest/haiku-running-on-asus-eeepc] I can second powelly's findings. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 06:45:38 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 31 Jul 2008 04:45:38 -0000 Subject: [Haiku-bugs] [Haiku] #2556: ASSERT FAILED (src/add-ons/kernel/file_systems/bfs/BPlusTree.cpp:1769) Message-ID: <042.f68738e89e9fb3cd02cb14e47e0a0637@haiku-os.org> #2556: ASSERT FAILED (src/add-ons/kernel/file_systems/bfs/BPlusTree.cpp:1769) ------------------------------+--------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Not sure if this is the same as #2555 or if it's different. Happened when i tried to delete a file, on r26693. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 06:48:41 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 31 Jul 2008 04:48:41 -0000 Subject: [Haiku-bugs] [Haiku] #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked Message-ID: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Got this also on r26693. May or may not be related to #2555 or #2556? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 09:22:09 2008 From: trac at haiku-os.org (axeld) Date: Thu, 31 Jul 2008 07:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #1671: Asus EEEPC can't boot. In-Reply-To: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> References: <041.c509a05634e93da784321f9bc9d62670@haiku-os.org> Message-ID: <050.f3e082a2f57135e3f2f0aa2ff4cf136c@haiku-os.org> #1671: Asus EEEPC can't boot. ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Seems to work for quite some time, it definitely boots fine on the Eee 900, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 09:43:16 2008 From: trac at haiku-os.org (axeld) Date: Thu, 31 Jul 2008 07:43:16 -0000 Subject: [Haiku-bugs] [Haiku] #2556: ASSERT FAILED (src/add-ons/kernel/file_systems/bfs/BPlusTree.cpp:1769) In-Reply-To: <042.f68738e89e9fb3cd02cb14e47e0a0637@haiku-os.org> References: <042.f68738e89e9fb3cd02cb14e47e0a0637@haiku-os.org> Message-ID: <051.37ba19a470a5708fa397cdcae71b32be@haiku-os.org> #2556: ASSERT FAILED (src/add-ons/kernel/file_systems/bfs/BPlusTree.cpp:1769) -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Just because they both start with "ASSERT FAILED", it doesn't mean it's the same thing - the message after that describes the actual problem. So in any case, you did the right thing by opening separate bug reports :-) Fixed in r26694. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 12:57:47 2008 From: trac at haiku-os.org (emitrax) Date: Thu, 31 Jul 2008 10:57:47 -0000 Subject: [Haiku-bugs] [Haiku] #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked In-Reply-To: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> References: <042.0ea1778ed6e448d727c4b8157a78403f@haiku-os.org> Message-ID: <051.328bd645c7a1916086921597251d0478@haiku-os.org> #2557: PANIC: rw_lock_read_unlock(): lock 0x90bf5550 not read-locked ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by emitrax): Just a hint for next time. Use the mutex command with the exadecimal number of the lock. It'll give devs useful information about the mutex. As for the bug is doesn't seem related to #2555. This one has more to do with the recent commit r26671 where the function was added. I'm not sure, but the lock seems double referenced. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 16:35:35 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 31 Jul 2008 14:35:35 -0000 Subject: [Haiku-bugs] [Haiku] #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null In-Reply-To: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> References: <042.f49909b6c512ca6d303c183505b167fa@haiku-os.org> Message-ID: <051.b86a6744505ebfa3fab662e139935e45@haiku-os.org> #2555: PANIC: ASSERT FAILED (src/system/kernel/condition_variable.cpp:206): sConditionVariableHash.Lookup(object) == __null ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: Replying to [comment:4 emitrax]: > Actually yes. The patch is applied. What do you suggest? Revert it. I will look into it tonight. Regarding setting the page state; it is OK to set it to busy and reset it without holding the pages lock. Anyway, closing this ticket. Please reopen it, if you can reproduce the problem without the #2552 patch applied. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 20:09:11 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 31 Jul 2008 18:09:11 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption Message-ID: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> #2558: File corruption ------------------------------+--------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- I'm seeing apparently random file corruption on my two BFS volumes at r26698. While compiling, e.g., expat, compilation fails with various errors resulting from (newly) corrupted files, such as Makefile containing NUL chars or source files such as lib/xmlparse.c and lib/xmltok.h containing garbage. Same happens for system headers such as be/support/Errors.h on the freshly initialized boot volume. Since I haven't run Haiku for some time, DeadYak suggested to check r26532. Will do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 20:22:17 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 31 Jul 2008 18:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.12434b57d9e7435004847207e0f219ff@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): Afterwards, chkbfs says that the volume is read-only and fixes some block allocation mismatches. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 21:24:21 2008 From: trac at haiku-os.org (bonefish) Date: Thu, 31 Jul 2008 19:24:21 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 In-Reply-To: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> References: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> Message-ID: <051.43640c4c29b35cf633e141c1a25d0e4e@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Should be fixed in r26700. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 21:40:12 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 31 Jul 2008 19:40:12 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.4dc41971112f0e32803b170ddea8a968@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): No problems in r26532! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 23:13:05 2008 From: trac at haiku-os.org (scottmc) Date: Thu, 31 Jul 2008 21:13:05 -0000 Subject: [Haiku-bugs] [Haiku] #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 In-Reply-To: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> References: <042.31a070a64466cd2ff49bebc81a0afba2@haiku-os.org> Message-ID: <051.50f596e7a61c88036df2dc66e83dae6b@haiku-os.org> #2552: PANIC: _mutex_lock(): double lock of 0x90cc4ed0 by thread 3595 ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): Replying to [comment:2 emitrax]: > I actually mananaged to triggered it again by simply running bonnie++. > I tried with the attached patch as you said. Please review. @emitrax, Does that mean that you fixed #1412? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 31 23:26:44 2008 From: trac at haiku-os.org (andreasf) Date: Thu, 31 Jul 2008 21:26:44 -0000 Subject: [Haiku-bugs] [Haiku] #2558: File corruption In-Reply-To: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> References: <043.542b980fac7d39a4c962a5ddab0ee05e@haiku-os.org> Message-ID: <052.554a7764dbd408c2c0674cbdde4722c7@haiku-os.org> #2558: File corruption -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by andreasf): r26700 still fails: Expat's configure hangs after "config.status: creating expat_config.h" with high CPU activity on both cores. Makefile.in contained garbage again. Unable to Ctrl+C it, and in KDL 'threads' appears to report sh running; no improvement after continuing. After a restart (from the menu), chkbfs fixed 32565 blocks allocated that should not be. (sounds scary) -- Ticket URL: Haiku The Haiku operating system.