From trac at haiku-os.org Thu Feb 1 10:53:07 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 09:53:07 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.1f81fd2676cb5cc417aa0f13b0905be6@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented ---------------------------------+------------------------------------------ Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Old description: > With R5's keymap pref app you can drag the characters displayed on the > keyboard > to different keys replacing the 'old' character with the 'new' dragged > character. IIRC it is also possible to select 1 char from the text input > field > to a key. Note that the Zeta keymap pref app doesn't have this feature. > > Feature request: make a better implementation; not replace but 'switch' > characters, example Czech keymap is QWERTZ I'm used to QWERTY but only > want to > switch the Y , y and Z , z keys. You can more easily make your own keymap > by this. New description: With R5's keymap pref app you can drag the characters displayed on the keyboard to different keys replacing the 'old' character with the 'new' dragged character. IIRC it is also possible to select 1 char from the text input field to a key. Note that the Zeta keymap pref app doesn't have this feature. Feature request: make a better implementation; not replace but 'switch' characters, example Czech keymap is QWERTZ I'm used to QWERTY but only want to switch the Y , y and Z , z keys. You can more easily make your own keymap by this. Comment (by mmu_man): I think Zeta took some code from Haiku for the prefs, so it would explain it doesn't have that feature. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 11:45:44 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 10:45:44 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.4ea570cda7184fce373b41a2b8883082@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented ---------------------------------+------------------------------------------ Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): I think it would make sense to have a separate window with all the available characters , from which you could drag and drop them into the "keyboard" window. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 12:13:07 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 11:13:07 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.1b277f11b78fd51d22f508c66f733ccb@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented ---------------------------------+------------------------------------------ Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by wkornewald): While this is a neat feature I think it should be marked as low-priority. Most people will just stick with one of the pre-defined keymaps. Also, you can already modify keymaps with a text editor and the keymap tool in our repository. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 12:35:28 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 11:35:28 -0000 Subject: [Haiku-bugs] [Haiku] #989: Expander crashes when unzipping In-Reply-To: <045.7a5fcbe424e2140238488970b62ee06b@haiku-os.org> References: <045.7a5fcbe424e2140238488970b62ee06b@haiku-os.org> Message-ID: <054.4100724371028c328c95a3c499ef3c01@haiku-os.org> #989: Expander crashes when unzipping --------------------------------------+------------------------------------- Reporter: jackburton | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - Applications/Expander | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by jackburton): * status: closed => reopened * resolution: fixed => Comment: Seems to happen randomly. I'll try to find a way to reproduce it consistently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 14:05:50 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 13:05:50 -0000 Subject: [Haiku-bugs] [Haiku] #533: [KDL] while trying to unzip large .zip file In-Reply-To: <040.bee54cea413bd446baf3d7d2438111d9@haiku-os.org> References: <040.bee54cea413bd446baf3d7d2438111d9@haiku-os.org> Message-ID: <049.5470f57836bff462018dd96e90531065@haiku-os.org> #533: [KDL] while trying to unzip large .zip file ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by jackburton): * platform: => All Old description: > I tried to unzip 300mb zip archive, i double clicked it and pressed "Show > contents" in Expander window. After that it drops me to KDL with message: > > PANIC: realloc(): page 0xblablabla invalid bin_index 24 New description: I tried to unzip 300mb zip archive, i double clicked it and pressed "Show contents" in Expander window. After that it drops me to KDL with message: PANIC: realloc(): page 0xblablabla invalid bin_index 24 Comment: This doesn't look like a KDL. The backtrace is the same I have in bug #989. I think we can mark this as fixed (as the KDL does no longer happen) and keep that one instead ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 15:41:10 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 14:41:10 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.38cc831ddb63e6ee21267e187a3c93f9@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented -----------------------------------+---------------------------------------- Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Keymap | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * priority: normal => low * component: - Preferences => - Preferences/Keymap -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 15:54:01 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 14:54:01 -0000 Subject: [Haiku-bugs] [Haiku] #1004: Adding a printer doesn't do anything Message-ID: <045.bf96174578ffe5d24749dbac3ef5f645@haiku-os.org> #1004: Adding a printer doesn't do anything ----------------------------------+----------------------------------------- Reporter: jackburton | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/print_server | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- I tried to add a printer using the printer preflet, and nothing happened. Note that I also tried to start the print_server beforehand (it isn't started by default, maybe it should ?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 15:55:05 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 14:55:05 -0000 Subject: [Haiku-bugs] [Haiku] #1005: BHandler::StartWatching(BMessenger, ...) is implemented completely wrong Message-ID: <040.1b0e99150be863554ff67d45490e717f@haiku-os.org> #1005: BHandler::StartWatching(BMessenger, ...) is implemented completely wrong ----------------------------------+----------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- The above method is implemented incorrectly, and doesn't do what it should do. It should send a message to the BMessenger, and asking it to start observing it, not the other way around. This is the only way to observe handlers in other teams. It's needed for BFilePanel for example. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 17:08:17 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 16:08:17 -0000 Subject: [Haiku-bugs] [Haiku] #1005: BHandler::StartWatching(BMessenger, ...) is implemented completely wrong In-Reply-To: <040.1b0e99150be863554ff67d45490e717f@haiku-os.org> References: <040.1b0e99150be863554ff67d45490e717f@haiku-os.org> Message-ID: <049.3b1e8b1aa1f8b9ac0017266d5038eda9@haiku-os.org> #1005: BHandler::StartWatching(BMessenger, ...) is implemented completely wrong -----------------------------------+---------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r20029. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 18:31:44 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 17:31:44 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.0f975901fa750f8d38c5fe57d4230ffe@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * priority: normal => low Comment: How will we handle the case when someone adds more workspaces, goes to a new workspace, changes the resolution, and then clicks Revert? IMHO, it would be very bad to switch the user to some other workspace (esp. without him noticing). The same applies to Defaults. What speaks against having a fixed number of workspaces (e.g., 12, one for each F-key)? If that is not an option we could move all buttons into the screen prefs box, so they are visually separated from the workspace settings. This would be merely a "hack", though... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 18:55:06 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 17:55:06 -0000 Subject: [Haiku-bugs] [Haiku] #1006: inconsistent behavior of Revert button in Backgrounds preflet Message-ID: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> #1006: inconsistent behavior of Revert button in Backgrounds preflet ---------------------------------------+------------------------------------ Reporter: wkornewald | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Backgrounds | Version: R1 development Platform: All | ---------------------------------------+------------------------------------ Open the Backgrounds preflet, change something, click Apply. Result: you can't click on Revert, anymore. This is inconsistent behavior because in all other preflets Revert brings you back to the state at program start. Another problem is that after having switched the workspace you can't revert the settings for the modified workspace, anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 21:22:20 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 20:22:20 -0000 Subject: [Haiku-bugs] [Haiku] #1006: inconsistent behavior of Revert button in Backgrounds preflet In-Reply-To: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> References: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> Message-ID: <054.8a84dc420ed8a711ac5df4fe3b939f37@haiku-os.org> #1006: inconsistent behavior of Revert button in Backgrounds preflet ----------------------------------------+----------------------------------- Reporter: wkornewald | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by korli): * Revert lets you go back to the current workspace settings (even after having applied), and it's the good behavior. * I don't understand the second point. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 21:41:39 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 20:41:39 -0000 Subject: [Haiku-bugs] [Haiku] #1004: Adding a printer doesn't do anything In-Reply-To: <045.bf96174578ffe5d24749dbac3ef5f645@haiku-os.org> References: <045.bf96174578ffe5d24749dbac3ef5f645@haiku-os.org> Message-ID: <054.2266b7f7501c6b7346bb4f5f1a7f9178@haiku-os.org> #1004: Adding a printer doesn't do anything -----------------------------------+---------------------------------------- Reporter: jackburton | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/print_server | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by laplace): * status: new => closed * resolution: => fixed Comment: The print_server and Printers preflet assumed that B_USER_PRINTERS_DIRECTORY exists, however it does not exist in the haiku image. The directory is now created on demand in r20030 by print_server or the preflet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 21:54:38 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 20:54:38 -0000 Subject: [Haiku-bugs] [Haiku] #1007: Icon of default printer should not be black Message-ID: <042.03e5d6a21fcc5c6a72bf4d29681bd80b@haiku-os.org> #1007: Icon of default printer should not be black ---------------------------------+------------------------------------------ Reporter: laplace | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Print | Version: R1 development Platform: x86 | ---------------------------------+------------------------------------------ The icon of the default printer is black in the Printers preflet. IIRC it did display correctly with bitmap icons. I think HVIF icons has introduced this issue. Stephan please reassign this issue to me if you do not have time to fix it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 22:07:00 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 21:07:00 -0000 Subject: [Haiku-bugs] [Haiku] #1008: Page Setup / Print Setup fails to open Message-ID: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> #1008: Page Setup / Print Setup fails to open ------------------------+--------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: new Priority: blocker | Milestone: R1 Component: - Printing | Version: R1 development Platform: All | ------------------------+--------------------------------------------------- In StyledEdit the page setup dialog can be opened once. Subsequent attempts to open the page setup or print dialog fail because StyledEdit (actually BPrintJob) does not get a valid BMessenger to the print_server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 22:25:23 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 21:25:23 -0000 Subject: [Haiku-bugs] [Haiku] #1009: Window not updated that opens Print Page Setup dialog Message-ID: <042.f7e11fa4f903f6ffe890de875eab7ea0@haiku-os.org> #1009: Window not updated that opens Print Page Setup dialog ------------------------+--------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: new Priority: high | Milestone: R1 Component: - Printing | Version: R1 development Platform: All | ------------------------+--------------------------------------------------- The window (e.g. StyledEdit) that uses a BPrintJob to open a print page setup dialg is not updated when the dialog is displayed. BPrintJob does not open the dialog itself. Instead it sends a message to the print_server and blocks until it gets a response. TODO check behaviour in BeOS R5. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 22:38:32 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 21:38:32 -0000 Subject: [Haiku-bugs] [Haiku] #1006: inconsistent behavior of Revert button in Backgrounds preflet In-Reply-To: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> References: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> Message-ID: <054.d2475c51a9d782b6a40580be40b9320b@haiku-os.org> #1006: inconsistent behavior of Revert button in Backgrounds preflet ----------------------------------------+----------------------------------- Reporter: wkornewald | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Old description: > Open the Backgrounds preflet, change something, click Apply. Result: you > can't click on Revert, anymore. > > This is inconsistent behavior because in all other preflets Revert brings > you back to the state at program start. > > Another problem is that after having switched the workspace you can't > revert the settings for the modified workspace, anymore. New description: Open the Backgrounds preflet, change something, click Apply. Result: you can't click on Revert, anymore. Comment (by wkornewald): Replying to [comment:1 korli]: > * Revert lets you go back to the current workspace settings (even after having applied), and it's the good behavior. In order to analyze the problem, I've been playing with the Screen preflet which has the same behavior and I agree that for preflets which have an Apply button Revert should go back to the currently active configuration. What irritated me was that right after having clicked Apply I didn't get a chance to revert to the configuration before I pressed Apply. I don't see why this should be prohibited. If you make new changes after having clicked Apply the Revert button should only undo the new changes (like it already does). BTW, R5 has similar behavior for Screen (only Backgrounds is an exception): Revert always brings you back to the state at program start (even after having pressed Apply). I've tested this scheme, too, but I think that the suggestion above is more intuitive. In case you want to test that behavior, I've committed my modified version of Screen (it can still be reverted). At least, in R5 Backgrounds is not consistent with the other preflets, so I think we should fix that behavior. What do you think? > * I don't understand the second point. This is related to my suggestion above, but after having played around with the Screen preflet I think the second point is unnecessary and it's not worth the effort. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 1 23:39:53 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 01 Feb 2007 22:39:53 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.8de642581db377e1a65aecd5d95e7868@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by ekdahl): I find the Defaults button confusing. On vmware the default settings are 800x600 and 32 bpp. Pressing the Defaults button otoh changes the resolution to 640x480 and 8 bpp. The logical behaviour would be that the Defaults button changes to the resolution that was when no change had been done. On LCD monitors, I think the default should be the native resolution. Maybe that is already the case, I don't know (can't test because of unsupported sata controller). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 08:11:57 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 07:11:57 -0000 Subject: [Haiku-bugs] [Haiku] #1004: Adding a printer doesn't do anything In-Reply-To: <045.bf96174578ffe5d24749dbac3ef5f645@haiku-os.org> References: <045.bf96174578ffe5d24749dbac3ef5f645@haiku-os.org> Message-ID: <054.d6e541db79c6edcb560a90f4e98f777b@haiku-os.org> #1004: Adding a printer doesn't do anything -----------------------------------+---------------------------------------- Reporter: jackburton | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/print_server | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Comment (by jackburton): Replying to [comment:1 laplace]: > The print_server and Printers preflet assumed that B_USER_PRINTERS_DIRECTORY exists, however it does not exist in the haiku image. > The directory is now created on demand in r20030 by print_server or the preflet. Thank you! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 09:55:15 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 08:55:15 -0000 Subject: [Haiku-bugs] [Haiku] #986: PS/2 Keyboard doesn't work In-Reply-To: <041.36d0bb3b2e19e80f028c00cc04a2bee4@haiku-os.org> References: <041.36d0bb3b2e19e80f028c00cc04a2bee4@haiku-os.org> Message-ID: <050.cf5d2a274a39528018a27abdaf750bf4@haiku-os.org> #986: PS/2 Keyboard doesn't work -----------------------------------+---------------------------------------- Reporter: andybe | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * cc: wkornewald (added) Comment: Replying to [ticket:986 andybe]: > My ps2 keyboard doesn't work at all. usb keyboard works. Do you need help with configuring syslog? In `//home/config/settings/kernel/drivers/kernel` you should at least have {{{ syslog_debug_output true load_symbols true }}} The syslog is written to `//var/log/syslog`. Please boot into Haiku once and press a few keys on the keyboard that doesn't work. After that, please send us the syslog file. If you can somehow log the serial debug output you can alternatively use {{{ serial_debug_output true load_symbols true }}} and send us that log. BTW, which Haiku revision are you using? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 15:09:49 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 14:09:49 -0000 Subject: [Haiku-bugs] [Haiku] #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" Message-ID: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" ----------------------------------+----------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Screen | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- When "keeping" changes applied to "All Workspaces", the screen flickers needlessly. If the workspace count is 9, it flickers 8 times. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 16:14:06 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 15:14:06 -0000 Subject: [Haiku-bugs] [Haiku] #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" In-Reply-To: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> References: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> Message-ID: <057.fe22e604f9f71cf3ff541b33a1f12239@haiku-os.org> #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" ---------------------------------+------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by wkornewald): * cc: wkornewald (added) * component: - Preferences/Screen => Servers/app_server Comment: I had a quick shot and it looks like an app_server bug. In `ServerApp.cpp` the code for `AS_SCREEN_SET_MODE` doesn't use the workspace argument, at all. I think that with each call to `BScreen::SetMode()` the resolution is changed for all workspaces instead of only the given one. The preflet could set the screen mode for all workspaces with one single call (instead of iterating over all workspaces), but then the app_server would have to make sure that the current workspace is only updated if the mode changed. Otherwise, only the other workspaces should be updated. I also noticed that `BScreen::SetMode(mode, makeDefault)` sets the mode for all workspaces. In R5 it seems to change the mode for the active workspace, only. The Screen preflet assumes R5 behavior, BTW. I'll fix that one if nobody objects. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 17:23:18 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 16:23:18 -0000 Subject: [Haiku-bugs] [Haiku] #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" In-Reply-To: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> References: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> Message-ID: <057.d367f63741ab3f1592229f019009c1e7@haiku-os.org> #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" ---------------------------------+------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: While BeOS shows the same annoying behaviour, and this one actually depends on bug #693 (right now, as Waldemar also noticed, the workspace argument is ignored), I've changed the app_server to only apply a new screen mode if it isn't already the active one. And that accidently also fixes this bug (but not the real one) in r20049. Waldemar: if you want to fix bug #693, go ahead, but I'm not sure if ignoring AS_SCREEN_SET_MODE for other workspaces is the way to go if that was your intention. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 18:25:48 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 17:25:48 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.2d355a02eb59aaa24487e11ed0837ef9@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented -----------------------------------+---------------------------------------- Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Keymap | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by nutela): Replying to [comment:8 wkornewald]: I agree, the best compromise is IMO the BeOS R5 one, you have a buffer (the text edit field) and the keymap itself although I would not mind if there was an option in the style of modifier-key + dragging which would swap key's if you would drag 1 char from 1 key to another key. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 18:27:54 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 17:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #671: Drag and drop keys / chars on keys not implemented In-Reply-To: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> References: <053.f0523ad8bcd0bede88c93d2fead7e453@haiku-os.org> Message-ID: <062.9d27287c797dfa3bd3bf49a75f78fe58@haiku-os.org> #671: Drag and drop keys / chars on keys not implemented -----------------------------------+---------------------------------------- Reporter: kutspam at wolke7.net | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Keymap | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by nutela): And an option to add/remove/modify keys on the keyboard would be appropriate too but definetely an R2-feature. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 2 20:01:43 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 02 Feb 2007 19:01:43 -0000 Subject: [Haiku-bugs] [Haiku] #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" In-Reply-To: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> References: <048.00f1275653defc5652786846e0ba9329@haiku-os.org> Message-ID: <057.d35af3d24330bd225526b9b320d006f4@haiku-os.org> #1010: Screen Preferences: screen flickers a lot when "keeping" changes made to "All workspaces" ---------------------------------+------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Comment (by wkornewald): Replying to [comment:2 axeld]: > Waldemar: if you want to fix bug #693, go ahead, but I'm not sure if ignoring AS_SCREEN_SET_MODE for other workspaces is the way to go if that was your intention. It doesn't look easy and I don't want to get back into coding too much. Sorry. I'd rather fix small bugs and usability issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 04:10:37 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 03:10:37 -0000 Subject: [Haiku-bugs] [Haiku] #953: BMenuField not starting in sticky mode In-Reply-To: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> References: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> Message-ID: <054.3216f21f9a0267f087b8cf913109fb49@haiku-os.org> #953: BMenuField not starting in sticky mode ---------------------------------+------------------------------------------ Reporter: wkornewald | Owner: jackburton Type: bug | Status: closed Priority: high | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Comment (by leavengood): The problem is now when you click-and-hold on a BMenuField and then release the mouse over an item, the item is not selected and the menu stays open. I should probably open another bug for this. I'd try to fix it myself but that code is hairy!!! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 13:33:48 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 12:33:48 -0000 Subject: [Haiku-bugs] [Haiku] #948: Some applications don't show up in DeskBar In-Reply-To: <049.ac98f19c5cbb871dbb9c53b0f1ac1e9a@haiku-os.org> References: <049.ac98f19c5cbb871dbb9c53b0f1ac1e9a@haiku-os.org> Message-ID: <058.8062857093d361df2c87e81858bd8fac@haiku-os.org> #948: Some applications don't show up in DeskBar --------------------------------+------------------------------------------- Reporter: johndrinkwater | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: That there's no BEOS:APP_SIG attribute for applications that don't have a resource file is only natural (where should it come from?). The empty app signature problem was caused by the registrar sending out notification messages for pre-registered apps as soon as their team/thread IDs were known. If the app executable had no app signature attribute/resource the signature was still unknown at this point though. As of r20058 we only send notification messages for fully registered apps (just as BeOS R5). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 18:12:37 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 17:12:37 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.0035874ab3d8e7fc3cbbb14968db9f17@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: wkornewald Type: bug | Status: assigned Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * owner: stippi => wkornewald * status: new => assigned Comment: I'll fix the Defaults and Revert buttons to update the workspace count and make it possible to revert even after having changed all workspaces. This means that you have to press Apply to change the number of workspaces (currently, it takes effect, immediately, without pressing Apply). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 18:14:31 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 17:14:31 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. Message-ID: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ---------------------------+------------------------------------------------ Reporter: mmu_man | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ wait_for_thread() doesn't seem to always find death records of dead threads, and gives bad results anyway: ~>thtest err = 00000000 st = 00200aa0 err = 00000000 st = 00200aac ~>thtest err = 80001100 st = 001071ac err = 00000000 st = 00200aac ~>error 0x80001100 0x80001100: Bad thread ID In Zeta: $ ./thtest err = 00000000 st = 00000000 err = 00000000 st = 00000000 $ ./thtest err = 00000000 st = 00000000 err = 00000000 st = 00000000 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 18:57:34 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 17:57:34 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.f17785038b81226174cac7bfa7c9acc0@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => assigned Comment: The result of the first wait_for_thread() is random even under BeOS - to make it safe you have to remove the resume_thread(). To let it always fail, just add a short delay before wait_for_thread(). I'll look into the wrong return code, though; I guess I recently broke that when fixing arch_thread_enter_userspace(). It does work correctly in the case of the fibo_* tests, BTW. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:03:11 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:03:11 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.d53203c7fd80a99bd38d1193a35d45c1@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: wkornewald Type: bug | Status: assigned Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by axeld): Please don't, that's not an appropriate solution. Changes should be instant if possible, and the workspaces count is definitely an example of this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:10:41 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:10:41 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.6152f5b222df5713eb12475aeb931c0b@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by mmu_man): The first one doesn't seem very random to me (yes I tried other values), but maybe it got fixed in Dano. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:12:33 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:12:33 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.5ae80fb308c2a2ebff8ce0560479241d@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: wkornewald Type: bug | Status: assigned Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by wkornewald): I understand your concern and normally I would agree, but in this case I think it's not possible to do it differently. The preflet obviously has the philosophy that you must apply before changes take effect. It doesn't make sense to have one half take effect immediately while the other half requires pressing Apply. For the sake of consistency, the whole preflet should follow the same philosophy or the UI must be reorganized such that only one philosophy is visible at the same time (e.g.: use tabs). The latter will be difficult because it's not worth adding a separate section just for the workspace count. Do you have a better suggestion? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:32:44 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:32:44 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.7fa55c7404c8416242b8839992778f1a@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: It's not a bug in BeOS nor Dano - it's a bug in *your* code. As I said, to make it clearer, just add a delay after resume_thread() but before wait_for_thread(). Dano's wait_for_thread() will then fail as well (as it should). Anyway, the actual bug in Haiku is fixed in r20060, thanks for noticing! :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:46:40 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:46:40 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.b63ec18c1a0190081d6468e672a7e607@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: wkornewald Type: bug | Status: assigned Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by axeld): Yes, leave it as is :-) The only actual appropriate solution would be to move the "Defaults" and "revert" buttons into the second box. "Defaults" could even stay where it is and also set the workspaces count if you want this. The "Defaults" button is currently broken anyway, so we might as well just remove it for now, though. It should set the default resolution, and that should be your native panel resolution, or any other app_server provided resolution. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:47:11 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:47:11 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.ab86a011ba73660c26b3b9c57c46a439@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by mmu_man): Actually I tried sleep5&) after resume_thread and it didn't fail. I didn't dig the Haiku code, but BeOS keeps the death reason and return code around until the team dies in a list of struct death_rec (and the parent team inherits the last one... or rather the one from the first thread IIRC. which I think is why sometimes the tty gets mad, because the shell doesn't get the ret code it expected). Now I remember I wanted to extend death_rec to keep the kernel and user times to be able to implement the missing wait3 or wait4, whichever. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 19:47:41 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 18:47:41 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.ce881cd59f0e83770e44a1c0c9bceead@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by mmu_man): sleep(1) I meant -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 20:02:05 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 19:02:05 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.3580a1bbc9179c11657ed1edff762157@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): I tested with sleep(1) on Dano, and the same thing happens as on Haiku and on R5. If it doesn't happen with Zeta, then it got changed after Dano got "published". Nevertheless, it's not a bug, just a different behaviour. The shell doesn't have anything to do with this, as teams collect the death entries of their children (but not single threads, only teams). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 20:38:32 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 19:38:32 -0000 Subject: [Haiku-bugs] [Haiku] #1011: wait_for_thread doesn't seem to work. In-Reply-To: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> References: <042.e4c103c79362fe2cd246ea415ad7f37f@haiku-os.org> Message-ID: <051.8a49f292bdc682cb4e39eae578279edc@haiku-os.org> #1011: wait_for_thread doesn't seem to work. ----------------------------+----------------------------------------------- Reporter: mmu_man | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by mmu_man): I know I did some changes in the thread code in Zeta, but I'm sure I didn't change that. Now currently wait_for_thread searches in the death_recs for the calling thread's team. And yes it does have to do with teams as well, at least in BeOS since it's handled with the same death_rec list, a diing team leaving its own death_rec (that of it's first thread actually) in testimony to its parent team. The fact that the team's return value is arbitrarily that of its first thread makes me think it has to do with the tty getting messed up, as I suspect the shell might actually want another thread's rec but doesn't get it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 21:34:28 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 20:34:28 -0000 Subject: [Haiku-bugs] [Haiku] #1012: GUI doesn't redraw after starting Cortex Message-ID: <050.095b5d81cc13f47751fcc179ce8e739d@haiku-os.org> #1012: GUI doesn't redraw after starting Cortex ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- When starting Cortex, it's window doesn't show up. All active windows stop redrawing, including Desktop, Deskbar, Terminal and Tracker. It's still possible to move windows. Tested r20060 using vmware, reproduceable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 3 21:57:36 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 03 Feb 2007 20:57:36 -0000 Subject: [Haiku-bugs] [Haiku] #1012: GUI doesn't redraw after starting Cortex In-Reply-To: <050.095b5d81cc13f47751fcc179ce8e739d@haiku-os.org> References: <050.095b5d81cc13f47751fcc179ce8e739d@haiku-os.org> Message-ID: <059.ad9d9e7d81f5fbec89e348097c06d45f@haiku-os.org> #1012: GUI doesn't redraw after starting Cortex -------------------------------+-------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by mmu_man): Cortex seems to lock everything up here too, r20058 in qemu. Will test no real hw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 10:54:44 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 09:54:44 -0000 Subject: [Haiku-bugs] [Haiku] #242: [Deskbar] Show replicants In-Reply-To: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> References: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> Message-ID: <049.599b6cd9980622c9d935ae9807b132c0@haiku-os.org> #242: [Deskbar] Show replicants --------------------------------+------------------------------------------- Reporter: diver | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * cc: axeld (added) * owner: bonefish => darkwyrm Comment: I don't think this has anything to do with the registrar. GUI stuff is app server business. So I bounce the ticket back to darkwyrm, CCing to axeld who's always a good choice for dumping open bugs. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 11:41:42 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 10:41:42 -0000 Subject: [Haiku-bugs] [Haiku] #956: Building on linux fails during configuring In-Reply-To: <039.5df3b09fd7e02c1ebaca85f58faadcdb@haiku-os.org> References: <039.5df3b09fd7e02c1ebaca85f58faadcdb@haiku-os.org> Message-ID: <048.202a1186ffe0f714ac73aa272d35e79f@haiku-os.org> #956: Building on linux fails during configuring ---------------------------+------------------------------------------------ Reporter: elmo | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by bonefish): I works find here. I'm using OpenSUSE 10.2 with gcc 4.1.2, glibc 2.5 (don't think those two matter in this case), bash 3.1.17(1)-release, sed 4.1.5. It also worked before without problems under SuSE 9.2. The first error "config.sub: invalid option --targeti586-pc-haiku" probably causes the later errors. My best guess is that you don't use bash. So try running "bash" before invoking configure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 11:52:05 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 10:52:05 -0000 Subject: [Haiku-bugs] [Haiku] #956: Building on linux fails during configuring In-Reply-To: <039.5df3b09fd7e02c1ebaca85f58faadcdb@haiku-os.org> References: <039.5df3b09fd7e02c1ebaca85f58faadcdb@haiku-os.org> Message-ID: <048.f5c241ac02cbc30bbb3261bf7e57eeb1@haiku-os.org> #956: Building on linux fails during configuring ---------------------------+------------------------------------------------ Reporter: elmo | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: The shebang in build/scripts/build_cross_tools_gcc4 was missing. I added it in r20062. The problem should be fixed now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 12:22:21 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 11:22:21 -0000 Subject: [Haiku-bugs] [Haiku] #884: A few nifty shell scripts for synching/building In-Reply-To: <044.aa1c6d09409c100d42d57cae9989095c@haiku-os.org> References: <044.aa1c6d09409c100d42d57cae9989095c@haiku-os.org> Message-ID: <053.c59cb54855e4ad79cb96f0d6b930d5b9@haiku-os.org> #884: A few nifty shell scripts for synching/building ---------------------------+------------------------------------------------ Reporter: jamesb192 | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: I don't the scripts are *that* helpful. Most developers and enthusiastic testers have their own strategy to update and build the tree and others use the pre-built images anyway. I, for instance, have several generated subdirectories (generated-gcc2, generated-gcc4, generated-ppc) around (there's no need for symlinks, the build system supports arbitrarily named output directories anyway). Moreover splitting up stdout and stderr is not very helpful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 12:34:11 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 11:34:11 -0000 Subject: [Haiku-bugs] [Haiku] #242: [Deskbar] Show replicants In-Reply-To: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> References: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> Message-ID: <049.6f0fa3a7b36c6a5cbd4d17f4a2b85b92@haiku-os.org> #242: [Deskbar] Show replicants ---------------------------------+------------------------------------------ Reporter: diver | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * component: Servers/registrar => Servers/app_server Comment: While BeOS obviously does this using the registrar, I agree with Ingo that the app_server should handle this. Darkwyrm, feel free to implement it, but if you don't know where to look for this in the app_server, I can do it as well. As Stefano said, it's not really much work, especially not if you're already familiar with the code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 16:12:54 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 15:12:54 -0000 Subject: [Haiku-bugs] [Haiku] #1008: Page Setup / Print Setup fails to open In-Reply-To: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> References: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> Message-ID: <051.c6388a1936cb72eb4e31119829609c97@haiku-os.org> #1008: Page Setup / Print Setup fails to open -------------------------+-------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: new Priority: blocker | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Changes (by laplace): * cc: bonefish (added) Comment: Ingo do you know what is going on here? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 18:33:16 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 17:33:16 -0000 Subject: [Haiku-bugs] [Haiku] #1008: Page Setup / Print Setup fails to open In-Reply-To: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> References: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> Message-ID: <051.7b893bbcdfb0e780939c46b0076a415e@haiku-os.org> #1008: Page Setup / Print Setup fails to open -------------------------+-------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: new Priority: blocker | Milestone: R1 Component: - Printing | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Changes (by bonefish): * cc: axeld (added) Old description: > In StyledEdit the page setup dialog can be opened once. > Subsequent attempts to open the page setup or print dialog fail because > StyledEdit (actually BPrintJob) does not get a valid BMessenger to the > print_server. New description: In StyledEdit the page setup dialog can be opened once. Subsequent attempts to open the page setup or print dialog fail because StyledEdit (actually BPrintJob) does not get a valid BMessenger to the print_server. (The print server must be running. E.g. add a printer via the Printers preflet before.) Comment: I've tracked the problem down to the point that a reply port reused for synchronous messaging happens to be not empty, so that the BRoster::GetAppInfo() invoked by the BMessenger constructor gets the wrong reply from the registrar. Uncommenting the #if 0'd check code in the synchronous BMessage::_SendMessage() triggers the debugger (even earlier, when trying to open the File menu the second time). I wouldn't completely rule out, that the bug is in the StyledEdit or printing code, but it seems very likely that the app kit is to blame. So I throw axeld into the CC for good measure. :-P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 19:03:47 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 18:03:47 -0000 Subject: [Haiku-bugs] [Haiku] #242: [Deskbar] Show replicants In-Reply-To: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> References: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> Message-ID: <049.a9e41c23ac772bad5b0c5d6734b30a3a@haiku-os.org> #242: [Deskbar] Show replicants ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by darkwyrm): * cc: axeld (removed) * owner: darkwyrm => axeld Comment: This would be something better handled by you, Axel. I'm not at all familiar with BDragger and the app_server is something that I don't know very well anymore, either. Thanks for your willingness to handle it -- it'll take you much less time than it would me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 4 19:43:58 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 04 Feb 2007 18:43:58 -0000 Subject: [Haiku-bugs] [Haiku] #1013: Remove unused detail sections in Add Printer dialog Message-ID: <042.d8082f790246383075896884dd75ab4e@haiku-os.org> #1013: Remove unused detail sections in Add Printer dialog ---------------------------------+------------------------------------------ Reporter: laplace | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Print | Version: R1 development Platform: All | ---------------------------------+------------------------------------------ The printer driver API does not provide a way to inline printer or transport add-on specific settings in the dialog. Therefore the detail sections should be removed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 10:13:10 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 09:13:10 -0000 Subject: [Haiku-bugs] [Haiku] #993: page fault with interrupts disabled under vmware In-Reply-To: <045.036e39ab3cd6263b189f36d722fd317d@haiku-os.org> References: <045.036e39ab3cd6263b189f36d722fd317d@haiku-os.org> Message-ID: <054.edc07d2aa9e362f0658819c01718c8f6@haiku-os.org> #993: page fault with interrupts disabled under vmware ------------------------------+--------------------------------------------- Reporter: jackburton | Owner: marcusoverhagen Type: bug | Status: closed Priority: critical | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: fixed | Platform: All ------------------------------+--------------------------------------------- Changes (by jackburton): * status: reopened => closed * resolution: => fixed Comment: I'll close this bug as it no longer applies. I've tried to reproduce it again with newer revisions, but failed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 10:16:41 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 09:16:41 -0000 Subject: [Haiku-bugs] [Haiku] #974: colored menus issues In-Reply-To: <040.9adfcbc9713bbe595d15465033d4cf7f@haiku-os.org> References: <040.9adfcbc9713bbe595d15465033d4cf7f@haiku-os.org> Message-ID: <049.c49ea304829404a57314bc210a013b7a@haiku-os.org> #974: colored menus issues ---------------------------------+------------------------------------------ Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by jackburton): * owner: axeld => jackburton * component: Kits/Application Kit => Kits/Interface Kit * summary: [application_kit] colored menus issues => colored menus issues -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 15:46:19 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 14:46:19 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.ee8dbdbbe5ef1b9f06875ba515c8664c@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Since it happens only on real hardware here, I'll share the configuration: it's a laptop, AMD Sempron 2600+, 512 Mb Ram (64 taken by the onboard graphic adapter, an unsupported sis chipset). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 16:39:08 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 15:39:08 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.0a8a017d81e7cfb436db98d4b0585c7a@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Axel, I see that in bfs_free_cookie() we ReadLock() the inode, but since we mess with the index, shouldn't we WriteLock() instead ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 16:41:53 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 15:41:53 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.5c5849424c132ecee52f1185eb290336@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): BTW I could just reproduce on qemu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 17:08:01 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 16:08:01 -0000 Subject: [Haiku-bugs] [Haiku] #1008: Page Setup / Print Setup fails to open In-Reply-To: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> References: <042.b59f896d79794b8594e68d71536148ed@haiku-os.org> Message-ID: <051.39119d1fcb707854a2143867cda27524@haiku-os.org> #1008: Page Setup / Print Setup fails to open -------------------------+-------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: - Printing | Version: R1 development Resolution: fixed | Platform: All -------------------------+-------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r20074. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 19:43:37 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 18:43:37 -0000 Subject: [Haiku-bugs] [Haiku] #681: [build system] garbage in Long Description attribute In-Reply-To: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> References: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> Message-ID: <049.f34ed2a3337895d3fa427aa4a2ea1b33@haiku-os.org> #681: [build system] garbage in Long Description attribute ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Old description: > Many apps in /bin folder, garbage in Long Description attribute. > See for example "alert" or "screen_blanker". > This only happens if compiled from BeOS. > If compiled from linux everything ok. New description: Many apps in /bin folder, garbage in Long Description attribute. See for example "alert" or "screen_blanker". This only happens if compiled from BeOS. If compiled from linux everything ok. Comment (by bonefish): An executable/library can have an application and a system version info. Both are stored together in the same attribute and/or resource (BEOS:APP_VERSION). Thus, if present at all both have to be present. The BAppFileInfo API (and using it the setversion program), however, allows to set them individually. When the attribute and resource are not yet present, BAppFileInfo is supposed to clear the respectively other version info if only one version info is set. This happens a lot when building a Haiku image, since the build system uses setversion to set the system version info for each generated executable/library, and most of them don't have resource file defining an application version info. In fact most of them don't have a resource file at all. What makes the mentioned files special is that they *do* have a resource file, but this resource file uncommonly doesn't define an application version info. My guess is, that this constellation (existing resources, but no version info) triggers a BAppFileInfo bug that causes garbage in the application version info. For the R5 build the setversion build tool uses R5's libbe, while under Linux, a stripped down Haiku libbe is used. R5's setversion suffers from the same problem, BTW. I suppose, we could modify our setversion to check whether a version info was present and if not also write a zero'd out other version info, if only one version info is given. ... or we ignore the problem and build under Linux. :-P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 21:42:10 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 20:42:10 -0000 Subject: [Haiku-bugs] [Haiku] #1009: Window not updated that opens Print Page Setup dialog In-Reply-To: <042.f7e11fa4f903f6ffe890de875eab7ea0@haiku-os.org> References: <042.f7e11fa4f903f6ffe890de875eab7ea0@haiku-os.org> Message-ID: <051.88e359e28c86c5956f4103f01a5d75ef@haiku-os.org> #1009: Window not updated that opens Print Page Setup dialog -------------------------+-------------------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: closed Priority: high | Milestone: R1 Component: - Printing | Version: R1 development Resolution: fixed | Platform: All -------------------------+-------------------------------------------------- Changes (by laplace): * status: new => closed * resolution: => fixed Comment: Fixed in r20075. Took implementation from BAlert.Go() as an example. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 22:20:59 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 21:20:59 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty Message-ID: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> #1014: Pages printed with StyledEdit are empty ------------------------------+--------------------------------------------- Reporter: laplace | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- 1. Open Printers preflet and add a preview printer. 2. Open StyledEdit and enter some text. 3. Select from menu File > Print... 4. Press page setup icon to open the page setup dialog and click OK. 5. Press job setup icon to open the dialog and enter page range from 1 to 1 and click OK. 6. Press OK. The preview window opens, however it is empty. I have not yet examined the problem closely. It seems BPictures are flattened to the spool file, because the file size changes depending on the amount of text in StyledEdit. Also if there is more text that does not fit on a single page, the Preview window allows to navigate to the next page (that is empty as well). So a first guess is, that the recorded pictures can not be flattened/unflattened correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 5 22:23:13 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 21:23:13 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.f18b253e7630dd28d7dfb0014c733bb6@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by laplace): * cc: laplace (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 00:37:09 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 23:37:09 -0000 Subject: [Haiku-bugs] [Haiku] #681: [build system] garbage in Long Description attribute In-Reply-To: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> References: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> Message-ID: <049.65bb3cf5fd8ace44ac9cb8eef5ee39b9@haiku-os.org> #681: [build system] garbage in Long Description attribute ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by axeld): I've changed setversion to clear the other version info, if not existing. Could someone please test? I don't see this bug over here, might have been fixed with Dano. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 00:41:17 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 05 Feb 2007 23:41:17 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.217502141dc69f15be10580a84dc0ff8@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * owner: axeld => jackburton -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 12:33:58 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 11:33:58 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.6fe370add2022af2a3411729651c9357@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Using a writelock in bfs_free_cookie() fixes the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 13:36:55 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 12:36:55 -0000 Subject: [Haiku-bugs] [Haiku] #681: [build system] garbage in Long Description attribute In-Reply-To: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> References: <040.6f1d6f98a08d22b37343441d616575de@haiku-os.org> Message-ID: <049.bab2906ebf58cb8a41950b889c8968fe@haiku-os.org> #681: [build system] garbage in Long Description attribute ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Verified to be fixed for the above files in r20076. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 13:45:36 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 12:45:36 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.d210df8721a738340ca486a5d79ed12d@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): I cannot commit or test anything right now... but I've had a quick look at BPicture, and I think I found the problem: In BPicture::Flatten(), we do: [cut] int32 count = extent->CountPictures(); if (count > 0) { status = stream->Write(&count, sizeof(count)); [cut] And then, in BPicture::Unflatten(), we do: [cut] int32 count = 0; status_t status = stream->Read(&count, sizeof(count)); [cut] We should always write the count in BPicture::Flatten(), even if it is 0, otherwise BPicture::Unflatten() won't work correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 14:00:00 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 13:00:00 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.a0fa65e6e69c23c356125bb4cba0388e@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by laplace): I will test it today. Could it also be a problem, that return value from BDataIO.Write()/Read() is treated as status_t instead of ssize_t, which holds the number of bytes written/read? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 14:21:34 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 13:21:34 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.0b6ad4c726408ccfffd01f22b8ac0f8b@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Replying to [comment:4 laplace]: > I will test it today. > > Could it also be a problem, that return value from BDataIO.Write()/Read() is treated as status_t instead of ssize_t, which holds the number of bytes written/read? > Since it tests for values < B_OK (and not != B_OK), it shouldn't be a problem. BDataIO::Write() returns a negative value on error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 14:25:25 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 13:25:25 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.6329660f70704f459d065e3c9e5b0fc4@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Replying to [comment:5 jackburton]: > > Could it also be a problem, that return value from BDataIO.Write()/Read() is treated as status_t instead of ssize_t, which holds the number of bytes written/read? > > > > Since it tests for values < B_OK (and not != B_OK), it shouldn't be a problem. BDataIO::Write() returns a negative value on error. Actually, you are right. In BPicture::Flatten() it tests also for B_OK: int32 size = extent->Size(); status = stream->Write(&size, sizeof(size)); if (status == B_OK) status = stream->Write(extent->Data(), extent->Size()); So the last line will never be called. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 16:03:59 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 15:03:59 -0000 Subject: [Haiku-bugs] [Haiku] #1006: inconsistent behavior of Revert button in Backgrounds preflet In-Reply-To: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> References: <045.7e92831b2714695290d42a5d96fb4dcf@haiku-os.org> Message-ID: <054.aad9aaf546c92325a5186a2779a944e3@haiku-os.org> #1006: inconsistent behavior of Revert button in Backgrounds preflet ----------------------------------------+----------------------------------- Reporter: wkornewald | Owner: korli Type: bug | Status: new Priority: low | Milestone: R1 Component: - Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Changes (by wkornewald): * cc: wkornewald (added) Old description: > Open the Backgrounds preflet, change something, click Apply. Result: you > can't click on Revert, anymore. New description: Open the Backgrounds preflet, change something, click Apply. Result: you can't click on Revert, anymore. Revert should bring all workspaces back to the state when the application was started. Comment: Revert should bring all workspaces back to the state when the application was started because that is more consistent with the behavior of all other preflets. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 17:31:47 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 16:31:47 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.b2551ac3d841936c768a2e58105b3e56@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): I've fixed the locking issue in r20079, thanks for the note. However, I don't think this can really prevent the bug from happening; at least it doesn't look like the source of the problem. The index inode is of course write locked when updating it, so it should never crash in BPlusTree::SplitNode(). What do you think? How often did you try again? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 17:35:54 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 16:35:54 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.8cfcefb3acb2083574a6c1fa64b26ace@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Replying to [comment:7 axeld]: > However, I don't think this can really prevent the bug from happening; at least it doesn't look like the source of the problem. > The index inode is of course write locked when updating it, so it should never crash in BPlusTree::SplitNode(). > What do you think? How often did you try again? I tried twice, once on real hardware and once on qemu. I can try again later, but before it was happening 100% of the times, on real hardware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 17:41:02 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 16:41:02 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.669db77c6441f8057ddcb221627cd3a7@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Anyone care to fix this? At least I could do it now, if you like :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 17:43:43 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 16:43:43 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.54e1f8dd30042c442241ebe4650584c6@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Replying to [comment:7 axeld]: > Anyone care to fix this? At least I could do it now, if you like :-) Please do :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 22:07:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 21:07:12 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.8576016221f621581607b917d1c03f70@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by laplace): In r20084 Axel has fixed flattening/unflattening BPictures. Unfortunately, this does not fix this bug. Do we have unit tests for flattening/unflattening BPictures so that we can verify that at least these tests work? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 6 22:49:46 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 06 Feb 2007 21:49:46 -0000 Subject: [Haiku-bugs] [Haiku] #1015: BListView invokes on single-click when item is already selected Message-ID: <045.215ceb31bfcfddf6ffa83f56d914c4b5@haiku-os.org> #1015: BListView invokes on single-click when item is already selected -------------------------------------+-------------------------------------- Reporter: wkornewald | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/FileTypes | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- I saw this behavior with the attributes and extensions lists in FileTypes. You select an item and then you can always invoke it with one single click. I don't know if the problem is in input_server, the mouse driver, BListView, or FileTypes. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 10:06:43 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 09:06:43 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.f3d6b75b7089f815259388f72c19b596@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Not yet. I was planning to add some, but at the moment I don't have access to my development machine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 10:35:47 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 09:35:47 -0000 Subject: [Haiku-bugs] [Haiku] #1014: Pages printed with StyledEdit are empty In-Reply-To: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> References: <042.b129cbfc1f9fcab52869037f0388ab6f@haiku-os.org> Message-ID: <051.94564549f5754f469ea3b73c25ea6df3@haiku-os.org> #1014: Pages printed with StyledEdit are empty -------------------------------+-------------------------------------------- Reporter: laplace | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: - User Interface | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by jackburton): Btw I just noticed that the server part of the AS_CREATE_PICTURE and AS_DOWNLOAD_PICTURE handlers (used in BPicture::Flatten()/Unflatten() have some TODOs related to nested BPictures. Worth having a look too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 15:00:10 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 14:00:10 -0000 Subject: [Haiku-bugs] [Haiku] #321: Workspace settings, not affected by "Defaults" or "Revert" buttons In-Reply-To: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> References: <054.cc51dd5e84ef07a2b2235598e4b7558a@haiku-os.org> Message-ID: <063.6d0dcf4acd89d8b86ce0b3416aee21c7@haiku-os.org> #321: Workspace settings, not affected by "Defaults" or "Revert" buttons -----------------------------------+---------------------------------------- Reporter: mattmadia at gmail.com | Owner: wkornewald Type: bug | Status: closed Priority: low | Milestone: R1 Component: - Preferences/Screen | Version: Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * status: assigned => closed * resolution: => fixed Comment: This should be fixed in r20096, but due to R5's and Haiku's limitations you can't test the results, yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 15:26:53 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 14:26:53 -0000 Subject: [Haiku-bugs] [Haiku] #953: BMenuField not starting in sticky mode In-Reply-To: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> References: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> Message-ID: <054.3a79e9564ddfd277841200ea90f67d34@haiku-os.org> #953: BMenuField not starting in sticky mode ---------------------------------+------------------------------------------ Reporter: wkornewald | Owner: jackburton Type: bug | Status: reopened Priority: high | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by wkornewald): * status: closed => reopened * resolution: fixed => Comment: Stefano, could you please have a look? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 18:20:04 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 17:20:04 -0000 Subject: [Haiku-bugs] [Haiku] #979: CD Player app should follow the multimedia application look and feel In-Reply-To: <044.7b3775b8231687100a0a28cdc5932f71@haiku-os.org> References: <044.7b3775b8231687100a0a28cdc5932f71@haiku-os.org> Message-ID: <053.26b59a503dd89d271fa68eb2ce5046b7@haiku-os.org> #979: CD Player app should follow the multimedia application look and feel --------------------------------------+------------------------------------- Reporter: bnickname | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/CDPlayer | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by darkwyrm): * status: new => closed * resolution: => fixed Comment: Fixed in r20104. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 7 23:47:31 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 07 Feb 2007 22:47:31 -0000 Subject: [Haiku-bugs] [Haiku] #53: POP3 SSL addon crashes mail_daemon when connection fails In-Reply-To: <053.00fe6396fbe4adbbdc1c48aae89b523a@haiku-os.org> References: <053.00fe6396fbe4adbbdc1c48aae89b523a@haiku-os.org> Message-ID: <062.7e5a09429859f53ac568e25cb06610ad@haiku-os.org> #53: POP3 SSL addon crashes mail_daemon when connection fails ---------------------------------+------------------------------------------ Reporter: genki at bredband.net | Owner: nathanw at uchicago.edu Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by darkwyrm): * status: new => closed * resolution: => fixed Old description: > Hello, > > This crash happens when the mail_daemon tries to look for new e-mail > but the machine is not connected to the network. > My ISP wasn't working at the time. (I got no IP from the DHCP). > > It seems only POP3 with SSL crashes, the other accounts on > standard POP3 seems fine. > On those accounts I just get an error message (which is > good and correct); "Error while connecting blah blah" > > I'm pretty sure this can be reproduced by disconnecting > your network cable, or switching off your DSL modem(or similar). > > Here is a stack dump: > > loading symbols > segment violation occurred > SSL_pending: > SSL_pending: > +0017 ec7fb2ab: * 08508b movl 0x00000008(%eax), %edx > XXXX at gmail.com:sc > frame retaddr > fd1e4534 ea5d360b POP3Protocol::~POP3Protocol(void) + 0000002f > fd1e4564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + > 000000e0 > fd1e4a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + > 0000007c > fd1e4a5c ec198a39 BLooper::task_looper(void) + 0000043d > fd1e4d28 ec19ae46 BLooper::_task0_(void *) + 00000036 > fd1e4d3c ec06c50d thread_start + 00000039 > XXXXX at gmail.com: > > Another one again: > > loading symbols > segment violation occurred > SSL_shutdown: > SSL_shutdown: > +0015 ec7fc08d: * 00207e83 cmpl $0x00, 0x00000020(%esi) > XXXXX at gmail.com:sc > frame retaddr > fd1a7564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + > 000000e0 > fd1a7a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + > 0000007c > fd1a7a5c ec198a39 BLooper::task_looper(void) + 0000043d > fd1a7d28 ec19ae46 BLooper::_task0_(void *) + 00000036 > fd1a7d3c ec06c50d thread_start + 00000039 > XXXX at gmail.com: New description: Hello, This crash happens when the mail_daemon tries to look for new e-mail but the machine is not connected to the network. My ISP wasn't working at the time. (I got no IP from the DHCP). It seems only POP3 with SSL crashes, the other accounts on standard POP3 seems fine. On those accounts I just get an error message (which is good and correct); "Error while connecting blah blah" I'm pretty sure this can be reproduced by disconnecting your network cable, or switching off your DSL modem(or similar). Here is a stack dump: loading symbols segment violation occurred SSL_pending: SSL_pending: +0017 ec7fb2ab: * 08508b movl 0x00000008(%eax), %edx XXXX at gmail.com:sc frame retaddr fd1e4534 ea5d360b POP3Protocol::~POP3Protocol(void) + 0000002f fd1e4564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + 000000e0 fd1e4a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + 0000007c fd1e4a5c ec198a39 BLooper::task_looper(void) + 0000043d fd1e4d28 ec19ae46 BLooper::_task0_(void *) + 00000036 fd1e4d3c ec06c50d thread_start + 00000039 XXXXX at gmail.com: Another one again: loading symbols segment violation occurred SSL_shutdown: SSL_shutdown: +0015 ec7fc08d: * 00207e83 cmpl $0x00, 0x00000020(%esi) XXXXX at gmail.com:sc frame retaddr fd1a7564 ec768364 BMailChainRunner::MessageReceived(BMessage *) + 000000e0 fd1a7a44 ec19a9c0 BLooper::DispatchMessage(BMessage *, BHandler *) + 0000007c fd1a7a5c ec198a39 BLooper::task_looper(void) + 0000043d fd1a7d28 ec19ae46 BLooper::_task0_(void *) + 00000036 fd1a7d3c ec06c50d thread_start + 00000039 XXXX at gmail.com: Comment: This bug was fixed in r19557 and 19558. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 09:15:00 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 08:15:00 -0000 Subject: [Haiku-bugs] [Haiku] #1003: KDL while expanding a file In-Reply-To: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> References: <045.83894595d74e21eb1ae869a9ed8c4511@haiku-os.org> Message-ID: <054.429ee70d03e5d32ff740a0bdf79906ab@haiku-os.org> #1003: KDL while expanding a file ----------------------------+----------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by jackburton): Ok, I just could reproduce it again. It crashed again in the same function, but the backtrace looks different. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 09:27:03 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 08:27:03 -0000 Subject: [Haiku-bugs] [Haiku] #953: BMenuField not starting in sticky mode In-Reply-To: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> References: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> Message-ID: <054.86ffb9f7f5aefaa593329f2179b32227@haiku-os.org> #953: BMenuField not starting in sticky mode ---------------------------------+------------------------------------------ Reporter: wkornewald | Owner: jackburton Type: bug | Status: reopened Priority: high | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:9 wkornewald]: > Stefano, could you please have a look? Yes but not right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 09:38:41 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 08:38:41 -0000 Subject: [Haiku-bugs] [Haiku] #979: CD Player app should follow the multimedia application look and feel In-Reply-To: <044.7b3775b8231687100a0a28cdc5932f71@haiku-os.org> References: <044.7b3775b8231687100a0a28cdc5932f71@haiku-os.org> Message-ID: <053.15ad218ed9c5ed11bae559307aa06bf0@haiku-os.org> #979: CD Player app should follow the multimedia application look and feel --------------------------------------+------------------------------------- Reporter: bnickname | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/CDPlayer | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Comment (by jackburton): I don't want to be picky, but buttons are still very different from media player... The internal is black, while media player's ones are grey, for example. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 15:41:42 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 14:41:42 -0000 Subject: [Haiku-bugs] [Haiku] #953: BMenuField not starting in sticky mode In-Reply-To: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> References: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> Message-ID: <054.208f7508a29534f981a6e5eb3aee938a@haiku-os.org> #953: BMenuField not starting in sticky mode ---------------------------------+------------------------------------------ Reporter: wkornewald | Owner: jackburton Type: bug | Status: reopened Priority: high | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by wkornewald): Thanks! When I have the time I'll try to find the problem, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 16:14:01 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 15:14:01 -0000 Subject: [Haiku-bugs] [Haiku] #953: BMenuField not starting in sticky mode In-Reply-To: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> References: <045.0fbc351eef10fb813a87fb82c436405e@haiku-os.org> Message-ID: <054.cc6fc92710b7a03f634cb3cf5a1ea6cb@haiku-os.org> #953: BMenuField not starting in sticky mode ---------------------------------+------------------------------------------ Reporter: wkornewald | Owner: jackburton Type: bug | Status: reopened Priority: high | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by jackburton): Replying to [comment:11 wkornewald]: > Thanks! When I have the time I'll try to find the problem, too. Actually I'm pretty sure I know where the problem is. The problem is how to implement it without breaking everything else :) And the code is that bad also because of the design of the class. I'm pretty sure be's code was ugly too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 8 18:03:08 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 08 Feb 2007 17:03:08 -0000 Subject: [Haiku-bugs] [Haiku] #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu Message-ID: <040.cea7856498e462da1a60984e5a7d6050@haiku-os.org> #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu ----------------------------------+----------------------------------------- Reporter: el-al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Screen | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- The recently re-located 'Apply' button on the screen prefs panel now partly obscures the Video Format PopUp menu. ATi Radeon display adapter here, which may or may not, account for the fact that the Apply button is over the top of another control on the panel. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 12:56:06 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 11:56:06 -0000 Subject: [Haiku-bugs] [Haiku] #889: [PackageBuilder] crash on File->Open In-Reply-To: <040.d70697311a6b796df957d52a63556a95@haiku-os.org> References: <040.d70697311a6b796df957d52a63556a95@haiku-os.org> Message-ID: <049.a720342c0d1158ff6b618c431e6d92f8@haiku-os.org> #889: [PackageBuilder] crash on File->Open -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jackburton): BeIDE Crashes with the same backtrace. Maybe we aren't binary compatible in some place ? I think we should add some tests to see if we are. Or at least compare the size of our classes with the size of the beos's classes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 12:58:37 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 11:58:37 -0000 Subject: [Haiku-bugs] [Haiku] #945: why not /boot/haiku ? In-Reply-To: <043.1e0085d1d8c1c24cd9bac3c21ff41445@haiku-os.org> References: <043.1e0085d1d8c1c24cd9bac3c21ff41445@haiku-os.org> Message-ID: <052.8025f5ab6fc44f328196d78048f738a9@haiku-os.org> #945: why not /boot/haiku ? --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by jackburton): The Beos r5 development tools needs to be unzipped in /boot, and contains references to "beos/..". So I guess we, at least, should keep a symlink to it, if we rename /boot/beos to /boot/haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 13:09:04 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 12:09:04 -0000 Subject: [Haiku-bugs] [Haiku] #1017: KDL when run the zeta software Message-ID: <044.8dd93557345345190094f89afc1b0952@haiku-os.org> #1017: KDL when run the zeta software -----------------------+---------------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- When I run any application compiled whit Zeta Haiku crashes on KDL -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 13:11:52 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 12:11:52 -0000 Subject: [Haiku-bugs] [Haiku] #1017: KDL when run the zeta software In-Reply-To: <044.8dd93557345345190094f89afc1b0952@haiku-os.org> References: <044.8dd93557345345190094f89afc1b0952@haiku-os.org> Message-ID: <053.f38a9113f6e4b8f50a99f9801956ad5d@haiku-os.org> #1017: KDL when run the zeta software ------------------------+--------------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by atomozero): ops sorry i use r20114 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 13:14:41 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 12:14:41 -0000 Subject: [Haiku-bugs] [Haiku] #998: bootscript crash In-Reply-To: <050.4c86a30160f343787db3d2d16515c117@haiku-os.org> References: <050.4c86a30160f343787db3d2d16515c117@haiku-os.org> Message-ID: <059.f5f45d39e2f9da603b73ecf0aafe50ee@haiku-os.org> #998: bootscript crash ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by jackburton): This doesn't seem to happen anymore, Marcus, can you confirm ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 13:19:58 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 12:19:58 -0000 Subject: [Haiku-bugs] [Haiku] #162: Expander's buttons aren't font sensetive. In-Reply-To: <040.3d98f1a9aeb8cd2da709a8e6f515c569@haiku-os.org> References: <040.3d98f1a9aeb8cd2da709a8e6f515c569@haiku-os.org> Message-ID: <049.af3369fec167817f7e111b812f29c7a3@haiku-os.org> #162: Expander's buttons aren't font sensetive. -----------------------------+---------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications | Version: Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by jackburton): * status: reopened => closed * platform: => All * resolution: => fixed Comment: Fixed in r20119 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 15:29:49 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 14:29:49 -0000 Subject: [Haiku-bugs] [Haiku] #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu In-Reply-To: <040.cea7856498e462da1a60984e5a7d6050@haiku-os.org> References: <040.cea7856498e462da1a60984e5a7d6050@haiku-os.org> Message-ID: <049.ad7e6832aa8cd195d4cc4b4bbf3e9143@haiku-os.org> #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu -----------------------------------+---------------------------------------- Reporter: el-al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Preferences/Screen | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * cc: wkornewald (added) Comment: That must have been my fault. I'll try to fix this, but I don't know when. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 9 15:32:09 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 09 Feb 2007 14:32:09 -0000 Subject: [Haiku-bugs] [Haiku] #945: why not /boot/haiku ? In-Reply-To: <043.1e0085d1d8c1c24cd9bac3c21ff41445@haiku-os.org> References: <043.1e0085d1d8c1c24cd9bac3c21ff41445@haiku-os.org> Message-ID: <052.1549c591340c142f15167370861d1aca@haiku-os.org> #945: why not /boot/haiku ? --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by wkornewald): * priority: normal => low Comment: Why not /boot/os instead of /boot/haiku? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 10 13:44:25 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 10 Feb 2007 12:44:25 -0000 Subject: [Haiku-bugs] [Haiku] #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu In-Reply-To: <040.cea7856498e462da1a60984e5a7d6050@haiku-os.org> References: <040.cea7856498e462da1a60984e5a7d6050@haiku-os.org> Message-ID: <049.e4a259e0e55b86e915595018591712a9@haiku-os.org> #1016: Screen Preflet: 'Apply' button overlaying Video Format Popup menu -----------------------------------+---------------------------------------- Reporter: el-al | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Preferences/Screen | Version: R1 development Resolution: fixed | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * status: new => closed * resolution: => fixed Comment: Fixed in r20122. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 10 18:06:09 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 10 Feb 2007 17:06:09 -0000 Subject: [Haiku-bugs] [Haiku] #986: PS/2 Keyboard doesn't work In-Reply-To: <041.36d0bb3b2e19e80f028c00cc04a2bee4@haiku-os.org> References: <041.36d0bb3b2e19e80f028c00cc04a2bee4@haiku-os.org> Message-ID: <050.b007724d4432b854e07f216663ff788a@haiku-os.org> #986: PS/2 Keyboard doesn't work -----------------------------------+---------------------------------------- Reporter: andybe | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Keyboard/PS2 | Version: R1 development Resolution: invalid | Platform: All -----------------------------------+---------------------------------------- Changes (by wkornewald): * status: assigned => closed * resolution: => invalid Comment: As reported by AndyBe (directly to the Trac email address) this problem doesn't exist in more recent versions of Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 10 19:13:57 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 10 Feb 2007 18:13:57 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) Message-ID: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ---------------------------+------------------------------------------------ Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Booting stops at the boot screen when enabling both cpus. Using only one cpu works. I'm attaching serial logs for one cpu and both cpus. Tested in vmware workstation with r20122. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 11 02:31:30 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 11 Feb 2007 01:31:30 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.50cab397a926f440602c780d7169b808@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by jfreeman): This happens on real hardware, as well, for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 11 11:00:09 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 11 Feb 2007 10:00:09 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.030e4e7263d9ec53936f6e3d90fc54aa@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by mmu_man): I remember hearing that apm was dangerous on SMP... Still, I used to load the apm driver in R5 on a dual celeron (BP6) and it worked fine for powering down. But since it's the last stuff showing up in the log... did you try disabling it ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 11 14:50:15 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 11 Feb 2007 13:50:15 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.0de15d4a65897b62cec776bbe317a6f9@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by ekdahl): Replying to [comment:2 mmu_man]: > I remember hearing that apm was dangerous on SMP... > Still, I used to load the apm driver in R5 on a dual celeron (BP6) and it worked fine for powering down. > But since it's the last stuff showing up in the log... did you try disabling it ? It makes no difference, debug output is exactly the same, so I'm wondering if it really gets disabled. I tried disabling it both in kernel settings file and boot menu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 12 21:09:02 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 12 Feb 2007 20:09:02 -0000 Subject: [Haiku-bugs] [Haiku] #1013: Remove unused detail sections in Add Printer dialog In-Reply-To: <042.d8082f790246383075896884dd75ab4e@haiku-os.org> References: <042.d8082f790246383075896884dd75ab4e@haiku-os.org> Message-ID: <051.47188de0ca8d352a9e54232f50d3983a@haiku-os.org> #1013: Remove unused detail sections in Add Printer dialog ----------------------------------+----------------------------------------- Reporter: laplace | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Preferences/Print | Version: R1 development Resolution: fixed | Platform: All ----------------------------------+----------------------------------------- Changes (by laplace): * status: new => closed * resolution: => fixed Comment: Fixed in r20125. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 13 20:28:00 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 13 Feb 2007 19:28:00 -0000 Subject: [Haiku-bugs] [Haiku] #1019: BeMail should get a new name Message-ID: <043.95d2e802fefc6b9c0b8b774a8bcbd3e4@haiku-os.org> #1019: BeMail should get a new name -----------------------------------+---------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Applications/BeMail | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- BeMail should get a new name. I suggest HaikuMail. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 13 20:34:37 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 13 Feb 2007 19:34:37 -0000 Subject: [Haiku-bugs] [Haiku] #1020: No save alert message for a changed draft mail. Message-ID: <043.966ecbc51091d08f5f0ec099a59402bd@haiku-os.org> #1020: No save alert message for a changed draft mail. -----------------------------------+---------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/BeMail | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- Open BeMail and create a new mail. Fill Fill with foo (or anything you like). Write a line to the body text. Then File => Save as Draft Close BeMail. Go to the Deskbar right click to the mail icon Go Open Draft select foo add a line to the main body text, and Close BeMail (click to the yellow button of the window manager) No save alert message. Open again the foo email the last line you had added is missing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 13 20:40:35 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 13 Feb 2007 19:40:35 -0000 Subject: [Haiku-bugs] [Haiku] #1021: File => Save as Draft is always enable Message-ID: <043.c3ff1b300bb2bd3f01f8cc4c04e79a2e@haiku-os.org> #1021: File => Save as Draft is always enable -----------------------------------+---------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/BeMail | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- File => Save as Draft is always enable, even when there is no changes to the text, or the Subject, or the field. Open BeMail and create a new mail. Fill Fill with bar (or anything you like). Write a line to the body text. Then File => Save as Draft Close BeMail. Open bar with no changes at all File => Save as Draft is always enable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 13 20:56:31 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 13 Feb 2007 19:56:31 -0000 Subject: [Haiku-bugs] [Haiku] #1022: Greek (keyboard) bug for BeMail. Message-ID: <043.b0d6d25dce0985eb06b2692f389c53ae@haiku-os.org> #1022: Greek (keyboard) bug for BeMail. -----------------------------------+---------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/BeMail | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- Open BeMail for new mail. Fill Fill with bar You can write Greek here, as normal, no crash here. Open Preferences => Keymap select Greek keyboard (you are suppose that you want to write Greek:-) After selecting the Greek keymap, you are writing to the body of the mail some greek letters. When you press key for tonos (english ; or raw key 0x45) you go to gdb. If you want to debug, you must type some English instructions into the Terminal, for example "where". So you go to the keymap program to set language to American, when click to American, you go directly to KDL. TODO: writing the kdl message. ps: opening a already composed email with full greek text, there is no crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 14 11:55:27 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 14 Feb 2007 10:55:27 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches on app_server boot Message-ID: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> #1023: Monitor switches on app_server boot -------------------------------------+-------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Then booting Haiku with nVidia GeForce 6200A (AGP, 256Mb DDRII) graphics card installed, monitor switches off then the app_server starts (I guess). And Haiku freezes (it doesn't reboot on Ctrl+Alt+Del hold). All works well then using nVidia GeForce MX440 (AGP, 64Mb, DDR) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 14 11:56:40 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 14 Feb 2007 10:56:40 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.a47cfb530c367acb99aa58c92d4d7ad1@haiku-os.org> #1023: Monitor switches off --------------------------------------+------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by k2s): * summary: Monitor switches on app_server boot => Monitor switches off -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 14 11:59:07 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 14 Feb 2007 10:59:07 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.6696fe2d3d925a7ad3613e83097e1b69@haiku-os.org> #1023: Monitor switches off on app_server start up --------------------------------------+------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by k2s): * summary: Monitor switches off => Monitor switches off on app_server start up -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 14 20:58:15 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 14 Feb 2007 19:58:15 -0000 Subject: [Haiku-bugs] [Haiku] #381: Bad port ID In-Reply-To: <040.673bddbabd232fec0fa896d0b39812f9@haiku-os.org> References: <040.673bddbabd232fec0fa896d0b39812f9@haiku-os.org> Message-ID: <049.355f4aecb0c76c4e170f76d777488f33@haiku-os.org> #381: Bad port ID ----------------------------+----------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by diver): Happens to me again with r20130 under vmware with 128 of RAM after running 10 hours. I tried to launch Clock, but got an error Bad port ID. Then i tried to launch it from terminal and got this error: FATAL: be_roster is not valid. Is the registrar running? Checked for registrar in team monitor and it wasn't there, so yes, it seems the registrar died without any error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 15 07:59:54 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 15 Feb 2007 06:59:54 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.0c2eceefcfa20d45cef55ebd0afab20e@haiku-os.org> #1023: Monitor switches off on app_server start up --------------------------------------+------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by k2s): rev. 20022 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 15 15:01:23 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 15 Feb 2007 14:01:23 -0000 Subject: [Haiku-bugs] [Haiku] #985: IDE DMA problem under VMWare In-Reply-To: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> References: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> Message-ID: <050.302fb6a6c88c9793d026e4ffbe5407bd@haiku-os.org> #985: IDE DMA problem under VMWare ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jonas.kirilla): I've compared syncing a fresh boot of Haiku (rev 20131 and some previous) in VMware Player / Windows XP / 2.4GHz Celeron to the same in Q (Qemu) / MacOS X / 1.4GHz G4, and while Haiku in VMware on the PC is a lot snappier than Haiku in Q on the Mac, syncing takes "normal" time in Q, whereas in VMware Player it takes much, much longer. /bin/idestatus says: Q on Mac: dma_status: dma enabled pio mode: 0 dma mode: 0x00 VMware Player on PC: dma_status: dma disabled after dma failure pio mode: 0 dma mode: 0x00 /bin/ideinfo: Q: FLUSH CACHE: supported FLUSH CACHE EXT: supported VMwarePlayer: FLUSH CACHE: not supported FLUSH CACHE EXT: not supported There may be some other difference to the output of ideinfo that I haven't spotted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 15 20:38:22 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 15 Feb 2007 19:38:22 -0000 Subject: [Haiku-bugs] [Haiku] #985: IDE DMA problem under VMWare In-Reply-To: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> References: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> Message-ID: <050.ba4229b16b19baf126d624d13efed182@haiku-os.org> #985: IDE DMA problem under VMWare ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by diver): * cc: marcusoverhagen (removed) * cc: diver (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 15 20:39:02 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 15 Feb 2007 19:39:02 -0000 Subject: [Haiku-bugs] [Haiku] #985: IDE DMA problem under VMWare In-Reply-To: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> References: <041.510e4714a9e60a918a894dd73be0eefe@haiku-os.org> Message-ID: <050.b6ab4540a324e91b189d7fdaebcaed80@haiku-os.org> #985: IDE DMA problem under VMWare ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by diver): * cc: marcusoverhagen (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 00:28:51 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 15 Feb 2007 23:28:51 -0000 Subject: [Haiku-bugs] [Haiku] #1024: System Freeze When consoled Closes Keyboard FD Message-ID: <043.d3ba067947c9f26bd7937396f6e42696@haiku-os.org> #1024: System Freeze When consoled Closes Keyboard FD ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ With r20135 the problem can be reproduced by running consoled /bin/sh --login in a terminal and "exit" the shell started in consoled. consoled's main thread eventually tries to close the FD for the keyboard ("/dev/keyboard"). At that point the system visually freezes (no more mouse moves, the Deskbar time is not updated). Entering KDL via F12 still worked. Everytime I did that, consoled's keyboard reader thread (performing a read() on the keyboard FD) was in state running. A stack crawl showed it to be in the keyboard driver in keyboard_read() somewhere in the "retry:" endless loop (different locations: mutex_lock()/unlock(), acquire_sem_etc()). At the same time consoled's main thread (performing the close() on the keyboard FD) was shown to be in state ready. A stack trace located it in the keyboard driver in keyboard_close() in delete_sem(). continuing the system and re-entering KDL later did not advance the position of the main thread any further. Tested in VMWare. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 07:31:56 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 16 Feb 2007 06:31:56 -0000 Subject: [Haiku-bugs] [Haiku] #1024: System Freeze When consoled Closes Keyboard FD In-Reply-To: <043.d3ba067947c9f26bd7937396f6e42696@haiku-os.org> References: <043.d3ba067947c9f26bd7937396f6e42696@haiku-os.org> Message-ID: <052.11bb0e3a916e568184fe3cf3c52aac2c@haiku-os.org> #1024: System Freeze When consoled Closes Keyboard FD ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r20140. I'll have a deeper look at the scheduler though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 14:08:32 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 16 Feb 2007 13:08:32 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.0e078067c3d99a38daa1282bbe38acb0@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by mt): Replying to [comment:3 ekdahl]: > It makes no difference, debug output is exactly the same, so I'm wondering if it really gets disabled. I tried disabling it both in kernel settings file and boot menu. Is your boot menu is "Disable Hyper-Threading" ? My Core2Duo machine was so, (C2D does not support HT) I disable supports_hyper_threading() in boot/platform/bios_ia32/smp.cpp (set to always return false) then "disable smp" from boot menu, now run well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 18:40:22 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 16 Feb 2007 17:40:22 -0000 Subject: [Haiku-bugs] [Haiku] #381: Bad port ID In-Reply-To: <040.673bddbabd232fec0fa896d0b39812f9@haiku-os.org> References: <040.673bddbabd232fec0fa896d0b39812f9@haiku-os.org> Message-ID: <049.afd60817b16d0834ec0d8d0d6ba5e048@haiku-os.org> #381: Bad port ID ----------------------------+----------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * cc: axeld (added) Comment: I haven't been able to reproduce the problem yet. The bug #757 method didn't cause any problems. Well, at least not for Haiku. qemu manages to freeze the X server everytime. Under vmware things work like a charm, though. I wouldn't rule out that, as Axel suggested, the problem might be some uncaught C++ exception. In two central places I've added code to catch exceptions and call the debugger(). As of r20145 a registrar crash or debugger() call will always cause a consoled + gdb session to be entered. So it won't go unnoticed anymore (before a single line in the serial debug output was the only indication). If it happens again (and indeed enters gdb) please send the serial debug output. If the registrar really hit a debugger() call, it can be continued by telling gdb to "detach" and then to "quit". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 23:24:01 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 16 Feb 2007 22:24:01 -0000 Subject: [Haiku-bugs] [Haiku] #1025: KDL coping and retriving sizes of directories in FAT disk Message-ID: <042.ff914fe22f4b6cb0c71bd4ebb9c8174f@haiku-os.org> #1025: KDL coping and retriving sizes of directories in FAT disk ------------------------------+--------------------------------------------- Reporter: rdaneel | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Tested in QEMU with a 100 MB (formated with mkdos). Coping/retrieving size of directories leads to KDL. Screenshots are available. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 16 23:27:34 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 16 Feb 2007 22:27:34 -0000 Subject: [Haiku-bugs] [Haiku] #1025: KDL deleting and retriving sizes of directories in FAT disk In-Reply-To: <042.ff914fe22f4b6cb0c71bd4ebb9c8174f@haiku-os.org> References: <042.ff914fe22f4b6cb0c71bd4ebb9c8174f@haiku-os.org> Message-ID: <051.d25409a36016e356aa9b6e789b20ca8c@haiku-os.org> #1025: KDL deleting and retriving sizes of directories in FAT disk -------------------------------+-------------------------------------------- Reporter: rdaneel | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by rdaneel): * summary: KDL coping and retriving sizes of directories in FAT disk => KDL deleting and retriving sizes of directories in FAT disk Comment: Sorry: i was deleting, not coping files when it crashed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 00:43:53 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 17 Feb 2007 23:43:53 -0000 Subject: [Haiku-bugs] [Haiku] #545: Static library dependencies are not (always?) resolved In-Reply-To: <040.4d87f6edfd2e83f46539d216c9ce9c43@haiku-os.org> References: <040.4d87f6edfd2e83f46539d216c9ce9c43@haiku-os.org> Message-ID: <049.eb007662133392ff9eb9676bfd1fc854@haiku-os.org> #545: Static library dependencies are not (always?) resolved ---------------------------+------------------------------------------------ Reporter: axeld | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * platform: => All Old description: > When I change an object in a static library (like memory_manager.c in > src/add-ons/kernel/drivers/graphics/common/), the libgraphicscommon.a is > not > rebuilt when I build a driver (for example radeon.driver or > intel_extreme) that > uses it. New description: When I change an object in a static library (like memory_manager.c in src/add-ons/kernel/drivers/graphics/common/), the libgraphicscommon.a is not rebuilt when I build a driver (for example radeon.driver or intel_extreme) that uses it. Comment: Is there a particular method to reproduce it? With r20147 it works for me at least: {{{ $ jam -q radeon.driver ...patience... ...patience... ...found 2041 target(s)... ...updating 144 target(s)... [...] Link generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver Chmod1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver SetType1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver MimeSet1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver SetVersion1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver ...updated 144 target(s)... $ touch src/add-ons/kernel/drivers/graphics/common/memory_manager.c $ jam -q radeon.driver ...patience... ...patience... ...found 2041 target(s)... ...updating 3 target(s)... Cc generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/common/memory_manager.o Archive generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/common/libgraphicscommon.a Ranlib generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/common/libgraphicscommon.a Link generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver Chmod1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver SetType1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver MimeSet1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver SetVersion1 generated/objects/haiku/x86/release/add- ons/kernel/drivers/graphics/radeon/radeon.driver ...updated 3 target(s)... }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 02:02:53 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 01:02:53 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.3e70974cd76fecb8298d219773f9a96b@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by marcusoverhagen): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 02:02:25 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 01:02:25 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.1597b6214a5ad1d5332813bc0f91d1c8@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by marcusoverhagen): * cc: axeld (added) * owner: axeld => marcusoverhagen * priority: normal => blocker Comment: I have the same problem here with Core 2 Duo E6600. The regression occurred in r20072. I'm going to debug this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 05:17:25 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 04:17:25 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.1847098c86d8ed09eeba9200807d3261@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by geist): i think i fixed it with change 20154. The new cpuid code was writing to the current cpu structure before it was set up on non boot cpus. The solution was to change the ordering of initialization a bit on non boot cpus, which isn't a generally great solution but should work for now. See if it repros on your machine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 21:36:15 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 20:36:15 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.1a8e6115896668eca3daa47fa2813a6e@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by ekdahl): It gets a little bit further now. I've attached the new serial debug output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 21:54:36 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 20:54:36 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.b21ad40172fb20c3c46cca3528d996ab@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by geist): * cc: geist (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 21:54:49 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 20:54:49 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.6309c1c9ecff9f66a6d2dcdc624eb743@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 22:19:41 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 21:19:41 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 Message-ID: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Black screen when Haiku switch to graphical mode after bootscreen. It looks like the wrong graphic mode. Video : nVidia GeForce 6150 (integrated in the motherboard). With resolution 640x480x8 uses incorrect refresh rate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 22:40:58 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 21:40:58 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.d8a40f76c93651d5572a195714aed72e@haiku-os.org> #1023: Monitor switches off on app_server start up --------------------------------------+------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by k2s): More card information: Vendor ID: 0x10de Card ID: 221 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 18 23:58:23 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 22:58:23 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.e353a09040b65804e218591830145a9e@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by ketsuban): * cc: thomas_winwood at oamail.net (added) Comment: Are you sure this is a bug and not just the normal blank screen associated with a change in graphics mode? I've noticed something similar when changing mode with my GeForce FX 5500, but as far as I can tell it's not a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 00:18:37 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 23:18:37 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.7afcf00aa34ab464b2b871f8ebd05a0f@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by k2s): Hm, It seems that this bug is similar to [http://dev.haiku- os.org/ticket/1023 #1023] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 00:31:13 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 18 Feb 2007 23:31:13 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.ea0d4e4f9f59ffc4e8fd3f1f8c5b8b65@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by ketsuban): Ah, I think I understand now. The description isn't terribly clear - should this be marked as a duplicate? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 01:14:00 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 00:14:00 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.f5ad283a2fefae0724c392ea97a4dbfd@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by geist): got another fix for it in 20160. give it a whirl. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 01:59:45 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 00:59:45 -0000 Subject: [Haiku-bugs] [Haiku] #1027: Trash icon sometimes fails to update after clearing it of items Message-ID: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> #1027: Trash icon sometimes fails to update after clearing it of items ------------------------------------+--------------------------------------- Reporter: ketsuban | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: x86 | ------------------------------------+--------------------------------------- Sometimes when clearing the Trash it fails to update the icon. The icon must be rightclicked and then swept over in some way so as to force it to be redrawn in order to restore the correct empty icon. I have been unable to ascertain what causes this to happen. This behaviour was also present in the version of Tracker released with BeOS R5. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 07:51:08 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 06:51:08 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.3363a6f2b6bd37d9e418672889c9409e@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by acca): Monitor does not turn off. It only displays the darkness. Haiku is not stuck because respond consistently to F12 and "reboot". So even in the not KDL falls. I think this is not like # 1023. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 11:15:26 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 10:15:26 -0000 Subject: [Haiku-bugs] [Haiku] #1028: Find crashes tracker when editing query Message-ID: <040.1bbc07d0f43d8f6c5385b748b6009c64@haiku-os.org> #1028: Find crashes tracker when editing query ------------------------------------+--------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: Platform: x86 | ------------------------------------+--------------------------------------- Click on the middle box in find to choose attribute. I type the name contains into the contains box then click the search button. After the list of files appear in tracker, I click on File/Edit Query. A crash occurs. Expected results should be show the find window to change the word or words typed, file type etc. If I leave it at the default "by name" instaed of "by attribute" then type my search word Click search After the list of found files comes up in the tracker Click on File/Edit Query There is no crash in this case. The crash only seems to occur when searching by attribute. After the crash all the icons on the desktop have gone but the deskbar is still showing. I have to "ctrl alt delete" and click restart desktop for them to reapear. This is reproduceable every time. I was testing with r19960 on a Beos partition Here is the trace from a crash: GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) Thread 63 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/libtracker.so...(no debugging symbols found)...done. Loaded symbols for /boot/beos/system/lib/libtracker.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/libqoca.so...done. Loaded symbols for /boot/beos/system/lib/libqoca.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/libtranslation.so...done. Loaded symbols for /boot/beos/system/lib/libtranslation.so Reading symbols from /boot/beos/system/lib/libtextencoding.so...done. Loaded symbols for /boot/beos/system/lib/libtextencoding.so [Switching to team /boot/beos/system/Tracker (63) thread Tracker (63)] 0x00365f04 in BWindow::FindView () from /boot/beos/system/lib/libbe.so (gdb) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 15:21:03 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 14:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.fd90cbc8224f97992aaedf3509aa14cf@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by ketsuban): * cc: thomas_winwood at oamail.net (removed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 15:21:03 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 14:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.fd90cbc8224f97992aaedf3509aa14cf@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Changes (by ketsuban): * cc: thomas_winwood at oamail.net (removed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 19 22:33:51 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 19 Feb 2007 21:33:51 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa Message-ID: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> #1029: Rendering problems with updated mesa -----------------------------+---------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Platform: x86 | -----------------------------+---------------------------------------------- It's like alpha isn't working. Previous version did not show this behavior. See attached screenshot to see what I mean. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 04:15:58 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 03:15:58 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.a0688e75770f6477e5ef0351b17cc348@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tigerdog): Replying to [ticket:1018 ekdahl]: > Booting stops at the boot screen when enabling both cpus. Using only one cpu works. I'm attaching serial logs for one cpu and both cpus. > Tested in vmware workstation with r20122. Happens here on real hardware. ECS mobo, Athlon 64x2 4200+. I have no serial debug capability at the moment. With the 20070218 build, booting stops after displaying features of CPU 1. With multiprocessor support disabled from boot menu, system boots normally. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 04:23:49 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 03:23:49 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.5bb6adafd0bc4c0ab86287c5f4d906e7@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by geist): I fixed it after the 0218 build, try it with a newer one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 09:03:39 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 08:03:39 -0000 Subject: [Haiku-bugs] [Haiku] #1028: Find crashes tracker when editing query In-Reply-To: <040.1bbc07d0f43d8f6c5385b748b6009c64@haiku-os.org> References: <040.1bbc07d0f43d8f6c5385b748b6009c64@haiku-os.org> Message-ID: <049.5e4dbbecbdc77777b18f9d0cad10e2d8@haiku-os.org> #1028: Find crashes tracker when editing query -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by jackburton): Can you provide a backtrace ? (write "bt" in the debugger, then press enter) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 09:22:12 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 08:22:12 -0000 Subject: [Haiku-bugs] [Haiku] #627: Cannot open another copy of the Terminal program In-Reply-To: <052.b3e9d0ab83f55b48a62d762dc909ea2d@haiku-os.org> References: <052.b3e9d0ab83f55b48a62d762dc909ea2d@haiku-os.org> Message-ID: <061.3a4cd88ee9a565b7d0139e36aa11976c@haiku-os.org> #627: Cannot open another copy of the Terminal program --------------------------------+------------------------------------------- Reporter: ajsmale at gmail.com | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - Applications | Version: Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by manette): Still hapening in r20146. Regards. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 09:50:18 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 08:50:18 -0000 Subject: [Haiku-bugs] [Haiku] #1028: Find crashes tracker when editing query In-Reply-To: <040.1bbc07d0f43d8f6c5385b748b6009c64@haiku-os.org> References: <040.1bbc07d0f43d8f6c5385b748b6009c64@haiku-os.org> Message-ID: <049.04d5d7a5420b6bd5ce8594d318f4f1b0@haiku-os.org> #1028: Find crashes tracker when editing query -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by cebif): I have just added a backtrace attachment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 10:11:40 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 09:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa In-Reply-To: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> References: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> Message-ID: <050.15b0d58a2f5286d5ebc17870c7d542b6@haiku-os.org> #1029: Rendering problems with updated mesa ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: x86 ------------------------------+--------------------------------------------- Comment (by korli): I didn't notice this as I tested only with GLTeapot. Could you clear out the test application or the way to reproduce, and also the SVN revision ? Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 11:25:01 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 10:25:01 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa In-Reply-To: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> References: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> Message-ID: <050.bc27a795011d9c5610a76405f4f253ed@haiku-os.org> #1029: Rendering problems with updated mesa ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: x86 ------------------------------+--------------------------------------------- Comment (by ekdahl): Replying to [comment:1 korli]: > I didn't notice this as I tested only with GLTeapot. Could you clear out the test application or the way to reproduce, and also the SVN revision ? Thanks. I'd guess it's r20170, from monday night anyway. The app is a screensaver called Flux from http://www.reallyslick.com (see picture there to see how it should look like). I could send you the port of the screensavers tonight when I get home so you can see for yourself (but beware, they're not finished..). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 11:50:44 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 10:50:44 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.b0fec02a5eba2e8c18af582a7e46a9e3@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by mt): Replying to [comment:13 geist]: > I fixed it after the 0218 build, try it with a newer one. I can't boot my Core2Duo machine with multiprocesser in r20177. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 17:48:49 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 16:48:49 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.4f7fb52cb72f03d49bc2a1488df0ab47@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tigerdog): Replying to [comment:13 geist]: > I fixed it after the 0218 build, try it with a newer one. I tried r20182 from haikuhost.com on real hardware. Still fails unless I disable SMP during boot. Console output (copied by hand - no serial debug here): code32 0xf000, 0x80bc, length 0xc9ea code16 0xf000, length 0x418c data 0xfdf0, length 0x0 CPU1: type 0 family 15 model 11 stepping 1 string AuthenticAMD CPU1: vendor 'AMD' model name "AMD Athlon(tm) 64 x2 Dual Core Processor 4200+' CPU1: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh mmx fxsr sse sse2 ntt sse3 syscall mx mmxest ffxsr long 3dnowext 3dnow I hope this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 20 18:45:42 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 20 Feb 2007 17:45:42 -0000 Subject: [Haiku-bugs] [Haiku] #1030: [BeIDE] crash on File -> New Project.. Message-ID: <038.73e6fecd90415d7345530c6a7189b34d@haiku-os.org> #1030: [BeIDE] crash on File -> New Project.. ----------------------------+----------------------------------------------- Reporter: xed | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Segment violation, running in vmware serial output: vm_soft_fault: va 0x10 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x10, ip 0 x886f7d, write 0, user 1, thread 0xee vm_page_fault: sending team "/boot/apps/BeIDE/BeIDE" 0xdb SIGSEGV, ip 0x886f7d ( "libroot.so_seg0ro" +0x1af7d) debug_server: Thread 238 entered the debugger: Segment violation stack trace, current PC 0x886f7d dcast__C14__si_type_infoRC9type_infoiPvPC9type _infoT3 + 0x49: (0x70102d0c) 0x887c9f __dynamic_cast + 0x4f (0x70102d4c) 0x764111 _FindView__7BWindowl + 0x61 (0x70102d8c) 0x75f59b DispatchMessage__7BWindowP8BMessageP8BHandler + 0xfc3 (0x70102eec) 0x45e145 DispatchMessage__Q28BPrivate10TFilePanelP8BMessageP8BH andler + 0x29 (0x70102f1c) 0x762d30 task_looper__7BWindow + 0x270 (0x70102f7c) 0x6b9aff _task0___7BLooperPv + 0x3f (0x70102fac) 0x88c684 _get_next_team_info + 0x5c (closest symbol) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 08:58:22 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 07:58:22 -0000 Subject: [Haiku-bugs] [Haiku] #242: [Deskbar] Show replicants In-Reply-To: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> References: <040.11e5e29dc8bcef16956273f1f8635774@haiku-os.org> Message-ID: <049.2bf69cce9652b02c77cedae22462922a@haiku-os.org> #242: [Deskbar] Show replicants ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Old description: > You can't uncheck Show replicants option form Deskbar. Tested with > rev16562. New description: You can't uncheck Show replicants option form Deskbar. Tested with r16562. Comment: Fixed in r20188. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 16:40:59 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 15:40:59 -0000 Subject: [Haiku-bugs] [Haiku] #1031: Terminal won't launch Message-ID: <040.de3eff7d91cd8c6029bb09a228f3258f@haiku-os.org> #1031: Terminal won't launch -------------------------------------+-------------------------------------- Reporter: fudel | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Terminal | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Hi there, i know about that: Ticket #944 (closed bug: duplicate) Opened 4 months ago Last modified 4 months ago Terminal won't launch after closing it but i'm trying haiku-os from time to time and i recorded the terminal issue in rev20072 for the first time. it isn't fix in current vmware-image rev20188 :-( one thing works, opening the terminal from the "new" menu entry in terminal. but starting the terminal app from the leaf-menu doesn't work and opening by trying to launch via /beos/apps/terminal doesn't work either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 18:00:10 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 17:00:10 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa In-Reply-To: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> References: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> Message-ID: <050.bff35ba18c7508cedf5573fb285508ed@haiku-os.org> #1029: Rendering problems with updated mesa ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: x86 ------------------------------+--------------------------------------------- Comment (by korli): Replying to [comment:2 ekdahl]: > Replying to [comment:1 korli]: > > I'd guess it's r20170, from monday night anyway. The app is a screensaver called Flux from http://www.reallyslick.com (see picture there to see how it should look like). I could send you the port of the screensavers tonight when I get home so you can see for yourself (but beware, they're not finished..). Please be sure to attach the testcase screensaver to this bug, or provide another testcase (a simple app using GL would be best). Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 19:38:23 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 18:38:23 -0000 Subject: [Haiku-bugs] [Haiku] #1031: Terminal won't launch In-Reply-To: <040.de3eff7d91cd8c6029bb09a228f3258f@haiku-os.org> References: <040.de3eff7d91cd8c6029bb09a228f3258f@haiku-os.org> Message-ID: <049.ce5d6e258fc3c408e4b54042a194fa2e@haiku-os.org> #1031: Terminal won't launch --------------------------------------+------------------------------------- Reporter: fudel | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Terminal | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by jfreeman): Replying to [ticket:1031 fudel]: > Hi there, i know about that: > > Ticket #944 (closed bug: duplicate) > Opened 4 months ago > Last modified 4 months ago > Terminal won't launch after closing it #944 is closed because it's a duplicate of #627, which is still alive and kicking. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 22:23:50 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 21:23:50 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.d3fad6f7f9534cfa5ffc7cffe3509616@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by tigerdog): I've experienced some troubles with the nvidia driver not always restarting the graphics card. The "usebios" flag defaults to "true" and causes the driver to rely on BIOS to restart the card. In my system, I've had to set "usebios false" for graphics to start reliably. It would be interesting to see if this fixes ketsuban's problem. If yes, maybe we should change the default? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 21 23:18:24 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 21 Feb 2007 22:18:24 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.689e822499a4229f948918533cca4502@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by tigerdog): Um, not Ketsuban's issue. My mistake. Problem was reported by acca. Acca, any chance you've tried this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 11:16:58 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 10:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #1031: Terminal won't launch In-Reply-To: <040.de3eff7d91cd8c6029bb09a228f3258f@haiku-os.org> References: <040.de3eff7d91cd8c6029bb09a228f3258f@haiku-os.org> Message-ID: <049.8f51a0e031253b4ab46bf77fafcab2f6@haiku-os.org> #1031: Terminal won't launch --------------------------------------+------------------------------------- Reporter: fudel | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Terminal | Version: R1 development Resolution: duplicate | Platform: x86 --------------------------------------+------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => duplicate Comment: dup of #627 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 14:16:47 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 13:16:47 -0000 Subject: [Haiku-bugs] [Haiku] #1032: BGLView::DirectConnected() badly implemented Message-ID: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> #1032: BGLView::DirectConnected() badly implemented -----------------------------+---------------------------------------------- Reporter: korli | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- BGLView::DirectConnected() seems badly implemented. Several screen savers crash in it. MesaSoftwareRenderer::DirectConnected() is not implemented yet. It could be needed to implement it to fix this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 14:18:47 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 13:18:47 -0000 Subject: [Haiku-bugs] [Haiku] #1032: BGLView::DirectConnected() badly implemented In-Reply-To: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> References: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> Message-ID: <049.ffcae8abc3cd4e7eb6be4f8ca024ebc8@haiku-os.org> #1032: BGLView::DirectConnected() badly implemented ------------------------------+--------------------------------------------- Reporter: korli | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by korli): * cc: phoudoin (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 14:20:09 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 13:20:09 -0000 Subject: [Haiku-bugs] [Haiku] #1032: BGLView::DirectConnected() badly implemented In-Reply-To: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> References: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> Message-ID: <049.d0a03f13f63fa4cc97bc457fa882de5e@haiku-os.org> #1032: BGLView::DirectConnected() badly implemented ------------------------------+--------------------------------------------- Reporter: korli | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by korli): * cc: jackburton (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 19:04:46 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 18:04:46 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.d666dd3ef29bac4670d17859925484be@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by acca): What file enter this line (usebios false)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 21:10:54 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 20:10:54 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.7d1ab517890fedcf42fc960f55954d89@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by marcusoverhagen): http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/system/kernel/smp.c?rev=20200&r1=20160&r2=20200 after that fix, and with scheduler tracing enabled, it booted all the way until it paniced because no boot volume was found (I'm still working on ahci support) but without scheduler tracing, it stops pretty early, but later than before the fix, see http://pastebin.ca/368034 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Feb 22 23:06:29 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 22:06:29 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa In-Reply-To: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> References: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> Message-ID: <050.32cce6ff460e11bc005966223b6601ad@haiku-os.org> #1029: Rendering problems with updated mesa ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: fixed | Platform: x86 ------------------------------+--------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied a fix in r20201. Though I had to add the flag BGL_ALPHA to the BGLView constructor in the screen saver testcase. Please test again with this revision and the additional flag. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 00:09:28 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 23:09:28 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.f188c0da53d89d3260d185b708dda350@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by k2s): /boot/home/config/settings/kernel/drivers/nv.settings -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 00:25:12 2007 From: trac at haiku-os.org (Haiku) Date: Thu, 22 Feb 2007 23:25:12 -0000 Subject: [Haiku-bugs] [Haiku] #1029: Rendering problems with updated mesa In-Reply-To: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> References: <041.9624ef6d4f6255a373d0d2f9af08ed7c@haiku-os.org> Message-ID: <050.93a83c20584576dcd30e7943555b60b5@haiku-os.org> #1029: Rendering problems with updated mesa ------------------------------+--------------------------------------------- Reporter: ekdahl | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: fixed | Platform: x86 ------------------------------+--------------------------------------------- Comment (by ekdahl): Replying to [comment:4 korli]: > Applied a fix in r20201. Though I had to add the flag BGL_ALPHA to the BGLView constructor in the screen saver testcase. Please test again with this revision and the additional flag. Thank you! I actually had BGL_ALPHA there before, but removed it since it made no difference until the latest mesa update. It's working fine now since your fix and I've added the flag again. BTW, do you have any clue as to why the screensavers are crashing when quitting? Been trying to find that for several weeks without much luck.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 09:55:40 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 08:55:40 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.efc01da283b5b6b2c32e9887d34aea04@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by acca): File nv.settings did not exist. His creation and the addition of the line did not solve the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 10:29:00 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 09:29:00 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.cb3bf1fda9c302d74ed06bc10e4b11ba@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by ketsuban): I'm fairly certain this is a duplicate of #1023 - they describe the same symptoms (monitor turning off after mode change during startup) with much the same sort of hardware. Perhaps we need to get Rudolf (or an approved delegate of Rudolf) to take a look at his driver with regard to the 6xxx series of video cards. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 10:29:49 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 09:29:49 -0000 Subject: [Haiku-bugs] [Haiku] #1027: Trash icon sometimes fails to update after clearing it of items In-Reply-To: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> References: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> Message-ID: <052.adec7004c8456145d1338e8804abc1ed@haiku-os.org> #1027: Trash icon sometimes fails to update after clearing it of items -------------------------------------+-------------------------------------- Reporter: ketsuban | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by ketsuban): Okay, I've realised this is a stupid, stupid report caused by me not checking rigorously enough. Could someone close this as not-a-bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 12:20:43 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 11:20:43 -0000 Subject: [Haiku-bugs] [Haiku] #1027: Trash icon sometimes fails to update after clearing it of items In-Reply-To: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> References: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> Message-ID: <052.847f4e1e5590174ef15319d9f2163fe1@haiku-os.org> #1027: Trash icon sometimes fails to update after clearing it of items -------------------------------------+-------------------------------------- Reporter: ketsuban | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: invalid | Platform: x86 -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 12:31:11 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 11:31:11 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.bf9661bd63214bcf1a9570eb480f4579@haiku-os.org> #1023: Monitor switches off on app_server start up --------------------------------------+------------------------------------- Reporter: k2s | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by acca): Perhaps it is true. But I ask you to pay attention to the fact that, in my case, the monitor does not turns off (continues to work in graphical mode), and shows darkness. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 12:31:39 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 11:31:39 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.bbb44a39ad4f501d99c6eeb4f3dd42eb@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 --------------------------------------+------------------------------------- Reporter: acca | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by acca): Perhaps it is true. But I ask you to pay attention to the fact that, in my case, the monitor does not turns off (continues to work in graphical mode), and shows darkness. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 18:20:38 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 17:20:38 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu Message-ID: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu ------------------------------------+--------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- Tracker's context menu's "New" menu items still show 8-bit icons, so here's a patch for review and commit: http://www.kirilla.com/haiku/IconMenuItem.cpp.diff I don't know if the Push/PopState() is necessary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 19:07:09 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 18:07:09 -0000 Subject: [Haiku-bugs] [Haiku] #1034: False positives by BDirectory::Contains() Message-ID: <048.4618d6222ca433e2df144af50ed91859@haiku-os.org> #1034: False positives by BDirectory::Contains() ------------------------------+--------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- In Haiku, if you drag things out of ~/boot/home/config/, e.g. /boot/home/config/fonts, Tracker gives you the erroneous error message (how ironic) "If you move the ''mime settings'' Haiku may not behave properly! Are you sure you want to do this? " Regardless of what you move, the error message is about the 'mime settings'. Tracker / FSUtils.cpp / ConfirmChangeIfWellKnownDirectory() calls StorageKit / Directory.cpp / BDirectory::Contains() which gives a false positive since it can't find beos_mime in B_COMMON_SETTINGS_DIRECTORY. (I think this is what happens.) If you create beos_mime in B_COMMON_SETTINGS_DIRECTORY (/boot/common/config), BDirectory comes to the right conclusion, which is that this folder (/boot/common/config) does not contain the entry that is being moved (/boot/home/config/fonts), whereas if /boot/common/config/beos_mime is missing, it concludes that the one contains the other, which is obviously wrong. I've rewritten BDirectory::Contains() to be more clear: http://www.kirilla.com/haiku/Directory.cpp.diff Tracker's error messages when moving stuff below /boot/home/config seem right now, with my changes, and you can move most things, like /boot/home/config/fonts, without interruptive alerts, but I haven't done any testing beyond that to prove that the code does the right thing in all circumstances. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Feb 23 23:53:29 2007 From: trac at haiku-os.org (Haiku) Date: Fri, 23 Feb 2007 22:53:29 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.c9a972fce83f44b7fcc36efce6e21553@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tigerdog): still seeing the same behavior with r20208, downloaded on 2007-02-22. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 02:50:20 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 01:50:20 -0000 Subject: [Haiku-bugs] [Haiku] #1035: KDL on boot - bfs block allocator Message-ID: <043.a966908411ab69359df60300bb59aba5@haiku-os.org> #1035: KDL on boot - bfs block allocator ---------------------------+------------------------------------------------ Reporter: darkwyrm | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ When I attempt to boot Haiku on real hardware, the I get a KDL even before I get to a blue screen. It has a page fault while interrupts are disabled with a NULL address and EIP. debugger backtrace reveals that the fault occurred in the bfs block allocator thread. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 04:16:47 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 03:16:47 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.ac370f1c7ad679cac5220786d05a8cf1@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by geist): sorry, I'm having a terrible time reproducing this. I recently fired up an old dual athlon MP I had lying around to try to reproduce it, but I'm getting something else that's blocking debugging it. I'm pretty sure some of the smp code is kind of rotted a bit, and i've made it worse before it gets better. If anyone can reproduce it and figure out precisely what the problem is you'll be my hero. I just can't do it here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 04:57:35 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 03:57:35 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.fb87c792ea4ca527401ad64fc4bc06e4@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by axeld): Thanks for the patch! Bug reports like this are the best :-) Unfortunately, I can't commit it, as it will break Tracker's "New" menu on R5. If you have the time to rework it for both builds, I'd appreciate it, but if not, I can do it as well. Just tell me. The Push/PopState() should not be necessary (at least not if it wasn't before), but it shouldn't hurt either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 06:46:56 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 05:46:56 -0000 Subject: [Haiku-bugs] [Haiku] #1034: False positives by BDirectory::Contains() In-Reply-To: <048.4618d6222ca433e2df144af50ed91859@haiku-os.org> References: <048.4618d6222ca433e2df144af50ed91859@haiku-os.org> Message-ID: <057.483625118966fa38300f24ecc87b5def@haiku-os.org> #1034: False positives by BDirectory::Contains() -------------------------------+-------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: fixed | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks for the patch! The problem was caused by BDirectory::Contains() returning true if the directory itself was not initialized, but the entry existed. I've not used your patch directly, but simplified the version in the tree differently; I've kept "result" around, and I think it's even clearer this way, but YMMV. BTW our coding style doesn't like the space between "!" and the following text a lot :-) Fixed in r20221. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 06:52:00 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 05:52:00 -0000 Subject: [Haiku-bugs] [Haiku] #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames In-Reply-To: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> References: <040.025c50821243a0afacfe6ff53fe7166d@haiku-os.org> Message-ID: <049.92492b8dbb504653a373b44ee005a735@haiku-os.org> #910: [Tracker] can't empty trash with cyrillic (at least) characters in filenames -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by axeld): I've downloaded the archive, unzipped it under Haiku directly to the Trash, and deleted them afterwards. Worked just fine. Have you any more insight on how I could reproduce the error you are encountering with the archive you made available? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 13:51:52 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 12:51:52 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.109b3fef3069f1be01946432072ba549@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by jonas.kirilla): Replying to [comment:1 axeld]: > If you have the time to rework it for both builds, > I'd appreciate it, but if not, I can do it as well. > Just tell me. I can do it tomorrow or early next week. I suppose with ifdefs for Haiku/BeOS in the IconMenuItems' constructors bitmap creation (CMAP8/RGB32) and for part of DrawContent(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 15:08:03 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 14:08:03 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.7293346d3cd34adddd4a6e58219cc2ea@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by axeld): That should pretty much be it, yes :-) Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 21:13:02 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 20:13:02 -0000 Subject: [Haiku-bugs] [Haiku] #1001: Vision IRC client crashes on close In-Reply-To: <039.4bc28893bdd3abe902f16e87f5350bdc@haiku-os.org> References: <039.4bc28893bdd3abe902f16e87f5350bdc@haiku-os.org> Message-ID: <048.55f374b89026c91c2c41d54825aa91ac@haiku-os.org> #1001: Vision IRC client crashes on close ------------------------+--------------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Changes (by ketsuban): * platform: All => x86 Comment: I've noticed that on R5 if Vision is unable to connect to a server and is closed the windows all quit cleanly, but the application (and its corresponding entry in the Deskbar) hangs about and must be killed through Ctrl-Alt-Del. Is this related? (I'm using r20255, by the way.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 21:13:40 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 20:13:40 -0000 Subject: [Haiku-bugs] [Haiku] #1001: Vision IRC client crashes on close In-Reply-To: <039.4bc28893bdd3abe902f16e87f5350bdc@haiku-os.org> References: <039.4bc28893bdd3abe902f16e87f5350bdc@haiku-os.org> Message-ID: <048.f15739d9adbfea3e7fc648a99d1073ea@haiku-os.org> #1001: Vision IRC client crashes on close ------------------------+--------------------------------------------------- Reporter: koki | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by ketsuban): Oops, sorry. I typoed; I meant r20225, of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Feb 24 22:38:09 2007 From: trac at haiku-os.org (Haiku) Date: Sat, 24 Feb 2007 21:38:09 -0000 Subject: [Haiku-bugs] [Haiku] #1036: Tracker Doesn't Like Hard Links Message-ID: <043.2063c9e64a289c76edcea5e9f963d139@haiku-os.org> #1036: Tracker Doesn't Like Hard Links ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Platform: All | ------------------------------------+--------------------------------------- Tracker has a few issues with respect to hard links, apparently because it doesn't distinguish between nodes and entries consequently enough. The following observation were made under BeOS R5: * In a Tracker window displaying a directory that contains several entries referring to the same node, only one of those entries is displayed, the others are missing. * Similarly to the first point, a query window displaying entries only lists one entry per node, even if the responsible file system reported more than one entry for the node. * A B_ENTRY_REMOVED live query notification will remove the node (i.e. the one entry displayed for it) from the query window, even if other entries referring to the node did and still do belong to the query result set (and were correctly reported by the responsible file system) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 25 10:44:34 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 25 Feb 2007 09:44:34 -0000 Subject: [Haiku-bugs] [Haiku] #1037: images are not displayed in website forums Message-ID: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> #1037: images are not displayed in website forums ---------------------------+------------------------------------------------ Reporter: austin | Owner: wkornewald Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ Images previously linked to in forum posts, previously visible in both the old system and the new drupal architecture, can no longer be seen. For example, [http://haiku-os.org/community/forum/haiku_idi_gui?page=2 this thread] used to have quite a few images, and now none are visible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 25 13:13:48 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 25 Feb 2007 12:13:48 -0000 Subject: [Haiku-bugs] [Haiku] #1037: images are not displayed in website forums In-Reply-To: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> References: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> Message-ID: <050.400a017999d595278e575c6c7ef17727@haiku-os.org> #1037: images are not displayed in website forums ----------------------------+----------------------------------------------- Reporter: austin | Owner: wkornewald Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by wkornewald): * status: new => closed * resolution: => fixed Comment: Thanks for reporting! I've fixed it (img tags weren't allowed in the forums). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Feb 25 21:31:15 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 25 Feb 2007 20:31:15 -0000 Subject: [Haiku-bugs] [Haiku] #1037: images are not displayed in website forums In-Reply-To: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> References: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> Message-ID: <050.3c5029f457734aefd56f358591898404@haiku-os.org> #1037: images are not displayed in website forums ----------------------------+----------------------------------------------- Reporter: austin | Owner: wkornewald Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by koki): Waldemar, Thanks for taking care of this. :-) I would assume that you made some CSS changes. Would you share with the rest of us the specifics of the change(s) you made? Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 00:42:53 2007 From: trac at haiku-os.org (Haiku) Date: Sun, 25 Feb 2007 23:42:53 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.fca38c470733101f34b41e47668119bf@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by marcusoverhagen): I applied a small cleanup to arch_smp.c and also added volatile to apic access, but this doesn't help. I enabled TRACE in main.c scheduler.cpp and arch_smp.c I did not enable TRACE_TIMER in arch_smp.c Please have a look at the 20231_scheduler_trace.txt - when not enabling tracing in scheduler.cpp, the system stops at INIT : main: done... begin idle loop on cpu 1 - reschedule is never executed on cpu 1 - "inter-cpu interrupt on cpu 1" appears frequently. what does it do? - when enabling TRACE_TIMER in arch_smp.c, reschudule is executed on both cpus - the apic time function only disables interrupts, it this enough? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 02:37:13 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 01:37:13 -0000 Subject: [Haiku-bugs] [Haiku] #1037: images are not displayed in website forums In-Reply-To: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> References: <041.49d1903e4877e562be410c76d0f4c334@haiku-os.org> Message-ID: <050.bdb477b53e686e27a3c27fde636600f8@haiku-os.org> #1037: images are not displayed in website forums ----------------------------+----------------------------------------------- Reporter: austin | Owner: wkornewald Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by wkornewald): Replying to [comment:2 koki]: > Waldemar, > > Thanks for taking care of this. :-) I would assume that you made some CSS changes. Would you share with the rest of us the specifics of the change(s) you made? Thanks! Of course, Jorge. :) I just added "img" to the allowed tags in the HTML filter ("Text with limited HTML" input format). It's in "input formats" in the admin area. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 15:02:45 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 14:02:45 -0000 Subject: [Haiku-bugs] [Haiku] #1038: binutils fails to build on ubuntu linux Message-ID: <045.1e38bd08b17e968aec14c477e2a3ed38@haiku-os.org> #1038: binutils fails to build on ubuntu linux --------------------------+------------------------------------------------- Reporter: jackburton | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- With latest changes, binutils don't build anymore on my system (Ubuntu 6.10). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 15:15:16 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 14:15:16 -0000 Subject: [Haiku-bugs] [Haiku] #1038: binutils fails to build on ubuntu linux In-Reply-To: <045.1e38bd08b17e968aec14c477e2a3ed38@haiku-os.org> References: <045.1e38bd08b17e968aec14c477e2a3ed38@haiku-os.org> Message-ID: <054.6eb796cfb8ee714ad34e680dd242474d@haiku-os.org> #1038: binutils fails to build on ubuntu linux ---------------------------+------------------------------------------------ Reporter: jackburton | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => invalid Comment: Ok, maybe reading the error text would've been best, before filing the bug. Looks like I needed to install makeinfo... weird, though, since I didn't have it installed before, and everything worked anyway... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 19:09:56 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 18:09:56 -0000 Subject: [Haiku-bugs] [Haiku] #1039: App icon - duplicate - slightly overlayed Message-ID: <048.2f75c648d96c884ecd6ba83ccb02ff42@haiku-os.org> #1039: App icon - duplicate - slightly overlayed ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: wkornewald Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ On this page http://haiku-os.org/about/teams/network there's a duplicate of the app icon, slightly overlayed. One of the icons is from the page code, the other one from the style sheet. HTML: {{{

Components

}}} CSS: {{{ .icon-app-medium { background-image: url(icons/app_32.png); } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 19:20:18 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 18:20:18 -0000 Subject: [Haiku-bugs] [Haiku] #1039: App icon - duplicate - slightly overlayed In-Reply-To: <048.2f75c648d96c884ecd6ba83ccb02ff42@haiku-os.org> References: <048.2f75c648d96c884ecd6ba83ccb02ff42@haiku-os.org> Message-ID: <057.1790c42e1ea62cc3bec9882ca30f2c17@haiku-os.org> #1039: App icon - duplicate - slightly overlayed ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: wkornewald Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Website/CMS | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by wkornewald): * status: new => closed * resolution: => fixed Comment: Fixed. Nice catch! It might take a few minutes to update for anonymous users. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 19:38:19 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 18:38:19 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.cfc78358802164ed4e42bd76282ae92b@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by jonas.kirilla): I think I'm done. See attachment: IconMenuItem.cpp.2.diff Axel, feel free to edit as you see fit. I'll take a look at your changes in SVN. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Feb 26 20:28:22 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 19:28:22 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.b9524fa2d0fc10a615654dfdbf8075f5@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by jonas.kirilla): Having had another look at the result, magnified, I think the line "where.y = Frame().top + 2;" should be "where.y = Frame().top + 1;" instead, so there's space below as well as above the icon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 27 00:05:29 2007 From: trac at haiku-os.org (Haiku) Date: Mon, 26 Feb 2007 23:05:29 -0000 Subject: [Haiku-bugs] [Haiku] #1033: 8-bit icons in Tracker's context menu's "New" submenu In-Reply-To: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> References: <048.efb4f421027ba62d1dc9657a4d82388e@haiku-os.org> Message-ID: <057.edc82aebe6fd2563306adddbb4b53e8a@haiku-os.org> #1033: 8-bit icons in Tracker's context menu's "New" submenu -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks! Patch applied in r20240. While I was at it, I've changed the positioning code to duplicate the method used in ModelMenuItem which should work better with larger font sizes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 27 01:03:07 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 27 Feb 2007 00:03:07 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.708fc12f423fc9e747d2ad0f885ca9fb@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by marcusoverhagen): This appears to be the same bug: http://axeld.blogspot.com/2005/10/not- yet.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 27 02:17:09 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 27 Feb 2007 01:17:09 -0000 Subject: [Haiku-bugs] [Haiku] #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) In-Reply-To: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> References: <041.02ee0fbf38663071c526f73ae434354b@haiku-os.org> Message-ID: <050.109f905be665f2ce8d33d946f126f229@haiku-os.org> #1018: Booting on Athlon 64 X2 fails with both cpus enabled (vmware) ----------------------------+----------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by tigerdog): Replying to [comment:20 marcusoverhagen]: > This appears to be the same bug: http://axeld.blogspot.com/2005/10/not- yet.html Maybe yes, maybe no. The real puzzle is that sometime in the recent past (within the last 60 days or so) Haiku '''did''' boot correctly and run on both CPUs of my Athlon 64. Then I stopped downloading nightly builds for a while; now it doesn't work. I'll try to research and find out when things stopped by loading older images if I can find them.''''' -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 27 15:43:23 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 27 Feb 2007 14:43:23 -0000 Subject: [Haiku-bugs] [Haiku] #1027: Trash icon sometimes fails to update after clearing it of items In-Reply-To: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> References: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> Message-ID: <052.11641a6c51cbe58ea3966e450d1ce289@haiku-os.org> #1027: Trash icon sometimes fails to update after clearing it of items -------------------------------------+-------------------------------------- Reporter: ketsuban | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: invalid | Platform: x86 -------------------------------------+-------------------------------------- Comment (by jonas.kirilla): I've seen this for years in BeOS, so I had a quick look at TrashWatcher.cpp. I'm testing the latest Haiku OpenTracker on BeOS/Bone, where I've set BTrashWatcher to run at B_NORMAL_PRIORITY instead of B_LOW_PRIORITY. Just a shot in the dark. Formally, would it be okay for me to reopen this ticket? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Feb 27 16:12:29 2007 From: trac at haiku-os.org (Haiku) Date: Tue, 27 Feb 2007 15:12:29 -0000 Subject: [Haiku-bugs] [Haiku] #1027: Trash icon sometimes fails to update after clearing it of items In-Reply-To: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> References: <043.4a4cd3b616f25da9a2c7259221636787@haiku-os.org> Message-ID: <052.28ec7de4404a6634afa5bdc769a5009a@haiku-os.org> #1027: Trash icon sometimes fails to update after clearing it of items -------------------------------------+-------------------------------------- Reporter: ketsuban | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: invalid | Platform: x86 -------------------------------------+-------------------------------------- Comment (by axeld): If you are experiencing this bug under Haiku, yes, of course. If you only know it from BeOS, then no. Haiku is supposed to deliver node monitor messages in a much more sane and safer way than R5 did. IOW this problem shouldn't exist under Haiku. It's not a problem of the Tracker code, it's a problem of BeOS losing messages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 10:42:35 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 09:42:35 -0000 Subject: [Haiku-bugs] [Haiku] #1036: Tracker Doesn't Like Hard Links In-Reply-To: <043.2063c9e64a289c76edcea5e9f963d139@haiku-os.org> References: <043.2063c9e64a289c76edcea5e9f963d139@haiku-os.org> Message-ID: <052.effc503d2523480eed8286e9819e26b4@haiku-os.org> #1036: Tracker Doesn't Like Hard Links -------------------------------------+-------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - Applications/Tracker | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by mmu_man): I suppose some Pose lists are keyed by node_ref rather than entry_ref because it's faster since it doesn't include a string... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 17:51:57 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 16:51:57 -0000 Subject: [Haiku-bugs] [Haiku] #1040: .pkg-compatible package installer Message-ID: <045.db4ea04cd679a454f9f6ac6dec69bd04@haiku-os.org> #1040: .pkg-compatible package installer ----------------------------+----------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - Applications | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- We need an installer that can handle .pkg files, so Haiku users can install old applications. This should be a simple one-click installer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 17:57:50 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 16:57:50 -0000 Subject: [Haiku-bugs] [Haiku] #1041: UDF attributes support Message-ID: <045.413ad1f3ddae9320b5237f3cbe120e2a@haiku-os.org> #1041: UDF attributes support ------------------------------+--------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/UDF | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Our UDF file system needs support for BFS-like attributes, indexing, and queries. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:05:30 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:05:30 -0000 Subject: [Haiku-bugs] [Haiku] #1042: implement ZeroConf/Bonjour support Message-ID: <045.b49ecdff6c9d4b25292dc0663ec7c114@haiku-os.org> #1042: implement ZeroConf/Bonjour support ----------------------------------+----------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: - Network & Internet | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- We need: * an API that can be used by applications (including a host/service browser) * the possibility to extend the known hosts and services list via an instant messenger, for example * detection of duplicate host names * automatic home network configuration -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:10:46 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:10:46 -0000 Subject: [Haiku-bugs] [Haiku] #1043: add encoding support to our Media Kit Message-ID: <045.20519a0fa708b5dcd6c6fbef988e9c71@haiku-os.org> #1043: add encoding support to our Media Kit ----------------------------+----------------------------------------------- Reporter: wkornewald | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- The current media add-on API only supports decoding media. An API for encoding has to be created that fulfills all modern requirements (i.e., B-frames). Furthermore, the existing encoders should be extended to export their functionality using this API. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:12:41 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:12:41 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support Message-ID: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> #1044: USB OHCI support -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Implement a kernel module for the OHCI protocol. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:27:45 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:27:45 -0000 Subject: [Haiku-bugs] [Haiku] #1045: USB isochronous streams Message-ID: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> #1045: USB isochronous streams -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Our USB stack needs to support isochronous streams. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:28:05 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:28:05 -0000 Subject: [Haiku-bugs] [Haiku] #1045: USB isochronous streams In-Reply-To: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> References: <045.f01a9eeaf20fd6286ea430fadb2fb479@haiku-os.org> Message-ID: <054.d3daf3edfeeb63c1bfe2e903275bb8d1@haiku-os.org> #1045: USB isochronous streams --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by wkornewald): * type: bug => enhancement -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:29:09 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:29:09 -0000 Subject: [Haiku-bugs] [Haiku] #1046: update NTFS to most recent ntfs-3g version Message-ID: <045.2c5fe1afe8a43db03f84354e3268b368@haiku-os.org> #1046: update NTFS to most recent ntfs-3g version -------------------------------+-------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Our version is unstable. The most recent version might even support write access. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:31:07 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:31:07 -0000 Subject: [Haiku-bugs] [Haiku] #1047: add DVD-RAM support to the CD driver Message-ID: <045.cbde426f7a0da2da352b1d4321cdba07@haiku-os.org> #1047: add DVD-RAM support to the CD driver -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- It should be possible to use DVD-RAM media like a hard disk, including write support. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:31:56 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:31:56 -0000 Subject: [Haiku-bugs] [Haiku] #1047: add DVD-RAM support to the CD driver In-Reply-To: <045.cbde426f7a0da2da352b1d4321cdba07@haiku-os.org> References: <045.cbde426f7a0da2da352b1d4321cdba07@haiku-os.org> Message-ID: <054.ad99836d5c5b918ed73ac1c09ed18b5a@haiku-os.org> #1047: add DVD-RAM support to the CD driver --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by wkornewald): Is that an R1 task, at all? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:36:14 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:36:14 -0000 Subject: [Haiku-bugs] [Haiku] #1048: add support for PowerPC Message-ID: <045.582f59dead7bb3ad40ba88dad8de6988@haiku-os.org> #1048: add support for PowerPC -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System | Version: R1 development Platform: PowerPC | -------------------------+-------------------------------------------------- We already have an OpenFirmware boot loader and other kernel support code, but it needs more work to actually boot Haiku. There might also be endianness issues in our code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:40:46 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:40:46 -0000 Subject: [Haiku-bugs] [Haiku] #1049: implement a FireWire stack Message-ID: <045.7b881a001168ff81f9db85a78abc6918@haiku-os.org> #1049: implement a FireWire stack -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- This should include support for DV cams and mass storage. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 18:43:20 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 17:43:20 -0000 Subject: [Haiku-bugs] [Haiku] #1050: implement a WiFi stack Message-ID: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> #1050: implement a WiFi stack -------------------------------------------+-------------------------------- Reporter: wkornewald | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Network Stack Component: - Network & Internet/Wireless | Version: R1 development Platform: All | -------------------------------------------+-------------------------------- We need support for multiple WiFi cards and firmware-provided encryption functions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 19:23:18 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 18:23:18 -0000 Subject: [Haiku-bugs] [Haiku] #1051: Disk Device Manager -- Implement Missing Disk Device Jobs Message-ID: <043.8272c9ee9d35d156fb2ca9da7f22c844@haiku-os.org> #1051: Disk Device Manager -- Implement Missing Disk Device Jobs ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ * Implement the unimplemented KDiskDeviceJobs in src/system/kernel/disk_device_manager/jobs and review the existing ones. * Adjust KDiskDeviceJobFactory accordingly. * Review the interaction of the jobs with KDiskDeviceJobQueue and KDiskDeviceManager. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 19:29:51 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 18:29:51 -0000 Subject: [Haiku-bugs] [Haiku] #1051: Disk Device Manager -- Implement Missing Disk Device Jobs In-Reply-To: <043.8272c9ee9d35d156fb2ca9da7f22c844@haiku-os.org> References: <043.8272c9ee9d35d156fb2ca9da7f22c844@haiku-os.org> Message-ID: <052.8653cf42921e6d0cb82c8857da5dc267@haiku-os.org> #1051: Disk Device Manager -- Implement Missing Disk Device Jobs ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Old description: > * Implement the unimplemented KDiskDeviceJobs in > src/system/kernel/disk_device_manager/jobs and review the existing ones. > > * Adjust KDiskDeviceJobFactory accordingly. > > * Review the interaction of the jobs with KDiskDeviceJobQueue and > KDiskDeviceManager. New description: * Implement the unimplemented KDiskDeviceJobs in src/system/kernel/disk_device_manager/jobs and review the existing ones. * Adjust KDiskDeviceJobFactory accordingly. * Review the interaction of the jobs with KDiskDeviceJobQueue and KDiskDeviceManager. Comment (by wkornewald): Fixed wiki syntax (unfortunately, a space is needed in front of list items). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 19:44:57 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 18:44:57 -0000 Subject: [Haiku-bugs] [Haiku] #1052: Disk Device Manager -- Implement the Notification Mechanism Message-ID: <043.22a9372307491f325800fed7946227a2@haiku-os.org> #1052: Disk Device Manager -- Implement the Notification Mechanism ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ The disk device manager needs to notify userland application of two kinds of events: Changes to disk devices and partitions (added/removed devices, moved/resized/added/delete/initialized/otherwise changed partitions), and progress of disk device jobs. This notification mechanism should also be made available within the kernel. The following tasks have to be performed: * Implement the core of the notification mechanism in src/system/kernel/disk_device_manager. * Implement the required syscalls to provide access to the notification mechanism for the userland API. * Implement the respective parts of the userland API (BDiskDeviceRoster::StartWatching() and related methods). * Provide access to the notification mechanism interface from the kernel. Both asynchronous and synchronous notifications should be supported. In case of disk device jobs it should be possible to synchronously wait for the termination of a disk device job (with/without timeout). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 19:49:27 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 18:49:27 -0000 Subject: [Haiku-bugs] [Haiku] #1053: Write Support in the Intel Partitioning Module Message-ID: <043.39f8e14bdd816d4f0d794bd49c4e7683@haiku-os.org> #1053: Write Support in the Intel Partitioning Module ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ Implement the missing write support in the intel partitioning module (src /add-ons/kernel/partitioning_systems/intel). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 20:06:17 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 19:06:17 -0000 Subject: [Haiku-bugs] [Haiku] #1054: Disk Device API -- Create Disk Device Parameter Editor Add-On Interface Message-ID: <043.cf4d8cc06a0b6273fee550445da44243@haiku-os.org> #1054: Disk Device API -- Create Disk Device Parameter Editor Add-On Interface ------------------------------+--------------------------------------------- Reporter: bonefish | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- An interface for providing a GUI for editing the specific parameters of file/partitioning systems needs to be created: * A class BDiskDeviceParameterEditor, which will be the interface for the disk device API user, needs to be designed, as well as the interface for add-ons providing the implementations of those class. headers/private/storage/DiskScannerAddOn.h and src/kits/storage/DiskScannerAddOn.cpp were used for that purpose in an earlier API version. * The BPartition methods using/returning BDiskDeviceParameterEditor need to be implemented. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 21:53:13 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 20:53:13 -0000 Subject: [Haiku-bugs] [Haiku] #1032: BGLView::DirectConnected() badly implemented In-Reply-To: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> References: <040.ccb7850437604d7dd5992054c909e8cb@haiku-os.org> Message-ID: <049.e515ed4114788b9955b3361b748a4594@haiku-os.org> #1032: BGLView::DirectConnected() badly implemented ------------------------------+--------------------------------------------- Reporter: korli | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by ekdahl): * cc: ekdahl (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 23:10:20 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 22:10:20 -0000 Subject: [Haiku-bugs] [Haiku] #1055: set_signals() crashes in radeon.accelerant after r20251 Message-ID: <046.2088f068de630a9f2eb39c22589e9448@haiku-os.org> #1055: set_signals() crashes in radeon.accelerant after r20251 ---------------------------+------------------------------------------------ Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ After updating to r20251, radeon.accelerant crashes during set_signals() call on boot. I confirmed that rolling back to r20250 resolves the issue. This is on real hardware: PIII 600 w/256mb RAM and Radeon 9250 AGP Serial debug log included is actually from r20252. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 23:16:09 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 22:16:09 -0000 Subject: [Haiku-bugs] [Haiku] #1055: set_signals() crashes in radeon.accelerant after r20251 In-Reply-To: <046.2088f068de630a9f2eb39c22589e9448@haiku-os.org> References: <046.2088f068de630a9f2eb39c22589e9448@haiku-os.org> Message-ID: <055.65a32d6f256532aa48435b53f0f53d22@haiku-os.org> #1055: set_signals() crashes in radeon.accelerant after r20251 ----------------------------+----------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by umccullough): * cc: geist (added) Comment: For clarification, set_signals() is where the gdb stack trace showed failure - but the gdb output isn't in the serial log (is that possible to do?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Feb 28 23:44:00 2007 From: trac at haiku-os.org (Haiku) Date: Wed, 28 Feb 2007 22:44:00 -0000 Subject: [Haiku-bugs] [Haiku] #1043: add encoding support to our Media Kit In-Reply-To: <045.20519a0fa708b5dcd6c6fbef988e9c71@haiku-os.org> References: <045.20519a0fa708b5dcd6c6fbef988e9c71@haiku-os.org> Message-ID: <054.d99c9b8dcebf3efe8cedd1928587a01b@haiku-os.org> #1043: add encoding support to our Media Kit -----------------------------+---------------------------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => -- Ticket URL: Haiku The Haiku operating system.