From trac at haiku-os.org Wed Jul 1 00:09:03 2009 From: trac at haiku-os.org (mt) Date: Tue, 30 Jun 2009 22:09:03 -0000 Subject: [Haiku-bugs] [Haiku] #4050: ATA driver cannot recognize 2nd HDD In-Reply-To: <037.f7621f6c1caeb5ffe6e3fed8f527348a@haiku-os.org> References: <037.f7621f6c1caeb5ffe6e3fed8f527348a@haiku-os.org> Message-ID: <046.54780574ccdf3f49aac441406e0a6310@haiku-os.org> #4050: ATA driver cannot recognize 2nd HDD --------------------------+------------------------------------------------- Reporter: mt | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by mt): Replying to [comment:3 marcusoverhagen]: > Can you please tell me the brand and type number of the harddisks? [[BR]] HDD0: Hitachi HDP725050GLA 500GB[[BR]] HDD1: Hitachi HDS721680PLA 80GB [[BR]][[BR]] I hope this may help you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 02:33:34 2009 From: trac at haiku-os.org (aldeck) Date: Wed, 01 Jul 2009 00:33:34 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.b91ad7424497d8c21ab5730eb80565cd@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: 3914, 4038 | ----------------------------------+----------------------------------------- Comment(by aldeck): Thanks Michael, i tried the different things you suggested (during the last two hours:)), but unfortunately, except a minor redrawing glitch in one of my tests, i didn't encounter the crash. Other ideas? To the ones that witnessed the bug, anything related to what mmlr suggested? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 05:10:48 2009 From: trac at haiku-os.org (someguy) Date: Wed, 01 Jul 2009 03:10:48 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP Message-ID: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- I have an FX5200 with 2 analog outputs and two LDC displays (1280 x 1024). When booted in BeOS R5, both displays operate as expected in dual head mode. When booted in Haiku R31342, one display is black while the other works fine. The dual head configure application (from bebits) does not believe the card is even capable of dual head operation when booted into Haiku. I have a GeForce 8400 GS with one analog and one digital output, and I get the same behavior. I'm very willing to help debug the issue, just let me know what I need to do to help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 05:39:33 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 01 Jul 2009 03:39:33 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.da15b600a3bb7e4e129c4279a63b6b70@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by scottmc): Can you post the output of listdev, that might give some useful info. Also the syslog may be helpful as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 06:31:53 2009 From: trac at haiku-os.org (someguy) Date: Wed, 01 Jul 2009 04:31:53 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.4ba65155c7821d98831aa77d195fa0fc@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by someguy): Here is the listdev output: device Serial bus controller (SMBus) [c|5|0] vendor 8086: Intel Corporation device 2443: 82801BA/BAM SMBus Controller device Serial bus controller (USB Controller, UHCI) [c|3|0] vendor 8086: Intel Corporation device 2442: 82801BA/BAM USB Controller #1 device Mass storage controller (IDE interface) [1|1|80] vendor 8086: Intel Corporation device 244b: 82801BA IDE U100 Controller device Bridge (ISA bridge) [6|1|0] vendor 8086: Intel Corporation device 2440: 82801BA ISA Bridge (LPC) device Input device controller [9|80|0] vendor 1102: Creative Labs device 7002: SB Live! Game Port device Multimedia controller (Multimedia audio controller) [4|1|0] vendor 1102: Creative Labs device 0002: SB Live! EMU10k1 device Network controller (Ethernet controller) [2|0|0] vendor 10b7: 3Com Corporation device 9200: 3c905C-TX/TX-M [Tornado] device Serial bus controller (FireWire (IEEE 1394), OHCI) [c|0|10] vendor 104c: Texas Instruments device 8020: TSB12LV26 IEEE-1394 Controller (Link) device Bridge (PCI bridge, Normal decode) [6|4|0] vendor 8086: Intel Corporation device 244e: 82801 PCI Bridge device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 10de: nVidia Corporation device 0322: NV34 [GeForce FX 5200] device Bridge (PCI bridge, Normal decode) [6|4|0] vendor 8086: Intel Corporation device 1131: 82815 815 Chipset AGP Bridge device Bridge (Host bridge) [6|0|0] vendor 8086: Intel Corporation device 1130: 82815 815 Chipset Host Bridge and Memory Controller Hub -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 07:13:46 2009 From: trac at haiku-os.org (Pete) Date: Wed, 01 Jul 2009 05:13:46 -0000 Subject: [Haiku-bugs] [Haiku] #4053: USB MIDI not recognized Message-ID: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> #4053: USB MIDI not recognized ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Now that usb_midi is in the distributed image, I tried plugging in my M-Audio 'Uno', but it doesn't show up -- either in PatchBay or /dev/midi. (It does appear as /dev/bus/usb/0/0) Looking at syslog, I see the following: {{{ KERN: usb hub 2: port 1: new device connected KERN: usb_midi: init_hardware() Jun 30 2009 15:19:22 KERN: usb_midi: init_driver() Jun 30 2009 15:19:22 KERN: usb_midi: device_added() KERN: usb_midi: vendor ID 0x0763, product ID 0x0150 KERN: usb_midi: interface 0, alt : 0: class 1, subclass 1, protocol 0 KERN: usb_midi: interface 1, alt : 0: class 1, subclass 3, protocol 0 KERN: usb error uhci 0: td (0x020ab5c0) error: status: 0x194007ff; token: 0xffe80369; KERN: usb_midi: set_alt_interface() failed -2147442667 KERN: usb_midi: init_driver() OK KERN: usb_midi: publish_devices() KERN: usb_midi: uninit_driver() }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 09:36:11 2009 From: trac at haiku-os.org (PieterPanman) Date: Wed, 01 Jul 2009 07:36:11 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.69d585bee6338d43057b3b88a81bd296@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: 3914, 4038 | ----------------------------------+----------------------------------------- Comment(by PieterPanman): Unfortunately the laptop I've experienced this bug on is now full with windows and fedora, and I cannot boot Haiku from USB stick (hangs after USB handover I believe). So at the moment I cannot do much to help. I've ordered a larger drive for the laptop, I'll leave some space for Haiku on it. (320G should help :)) My laptop is a compal IFL90, with a santa rosa chipset and core 2 duo processor, always on smp, 2G memory. I've had it intermittently, not always on workspace switching, but most of the time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 10:52:00 2009 From: trac at haiku-os.org (stippi) Date: Wed, 01 Jul 2009 08:52:00 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.c7ad0a6e3b608950649b38351426796e@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): The problem may be something else and maybe it's not very hard to fix. The Dualhead stuff was implemented by encoding some additional options in the flags argument for a screen mode (IIRC). Similarly, the Dualhead configuration utility detected graphics cards which supported the additional flags in some way. I don't remember how that worked. In any case, the Haiku Screen preflet actually inherited some or even all of that code. It's supposed to display more options when it detects a graphics card capable of the dual head configurations. I believe all of this may have not been properly tested when changes were done on the preflet and functinoality may have been lost along the way. So the first thing I'd do is trace through the Haiku Screen preflet code to see why you don't see dual head controls for your card. And once that is figured out, the app_server may need to be adjusted to properly store and restore the screen mode flags where the dual head configuration is encoded. If the Dualhead utility from BeBits contains some additional code for NVidia boards, then IMHO it should be integrated into the Haiku Screen preflet, or the Radeon and NVidia drivers should be changed so support the same API. It's a long time ago that I looked, but I believe this may already be the case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 13:11:53 2009 From: trac at haiku-os.org (aldeck) Date: Wed, 01 Jul 2009 11:11:53 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.238a9142f8d8f970f0b72d0b7b25107b@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: aldeck Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: 3914, 4038 | ----------------------------------+----------------------------------------- Changes (by aldeck): * owner: axeld => aldeck * status: new => assigned Comment: Ok, it's still hard to get it but now i managed to reproduce it a few times when switching workspaces with a folder open of a read-only r5 partition. Not that great but that should be enough to start working on it. Better/simpler test cases are still welcome :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 13:18:16 2009 From: trac at haiku-os.org (axeld) Date: Wed, 01 Jul 2009 11:18:16 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.9132892f9cb3b3ee801ca990bfe56cb7@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: aldeck Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: 3914, 4038 | ----------------------------------+----------------------------------------- Comment(by axeld): I would assume that this is a binary compatibility problem of a changed flattened column format. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 20:37:13 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 01 Jul 2009 18:37:13 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.bb0c4f31035e63e9fd041b424e7757ed@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi guys, I am aware of this problem. Actually, AFAIK, Haiku uses Thomas his method with is entireley different from what I have in my driver and the Dualhead Setup util. Thomas once explained it to me at BG but I still have to have a look at it. Since back then BeOS R5 is phased out more or less, so I think maybe it's time to modify my driver to work like the radeon one as far as is possible. OTOH: Why can old programs nolonger set modes??? It should have worked as far as I know... For instance the GFX benchmark program I use has the same problem: it works OK apart from the modesetting stuff. Apparantly modesetting is not compatible to R5/dano. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 20:49:22 2009 From: trac at haiku-os.org (stippi) Date: Wed, 01 Jul 2009 18:49:22 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.a837cc13d4c6c4fca86a99ca2437b41f@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): Mode setting is not supposed to be broken, so maybe it's something worth looking into before looking at any other issues with this. To be honest, though, I don't want to take the time to do that right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 22:06:25 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 01 Jul 2009 20:06:25 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.3ae9c156e8b60ae56751af3c2678dd16@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): OK, good to know it should indeed work. When I have time I'll probably look since I need dualhead support to test some driver aspects. This will probably be in four weeks or so... ;-) Of course if someone else has time I'd love to see old app modesetting fixed.. Bye! Rudolf. BTW Someguy: GF8xxx and later are not supported by the nvidia driver so dualhead will not work either. (just vesa mode). GF8xxx and later support will come in a new driver I expect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 22:07:55 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 01 Jul 2009 20:07:55 -0000 Subject: [Haiku-bugs] [Haiku] #4053: USB MIDI not recognized In-Reply-To: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> References: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> Message-ID: <048.1cadd624d27eaa616d68d518fe239c32@haiku-os.org> #4053: USB MIDI not recognized ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by mmlr): Can you please add the output of "listusb -v /dev/bus/usb/0/0" here. The device stalls the request to set the alternate interface, which is possibly ok if there aren't any alternates. I don't know the USB midi protocol, it might also be required to set the alternate interface to enable device functions (like in other USB protocols). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 00:16:19 2009 From: trac at haiku-os.org (Pete) Date: Wed, 01 Jul 2009 22:16:19 -0000 Subject: [Haiku-bugs] [Haiku] #4053: USB MIDI not recognized In-Reply-To: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> References: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> Message-ID: <048.9e3274957e31718b4eba86a076d388e7@haiku-os.org> #4053: USB MIDI not recognized ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by Pete): Here's what I get: {{{ [Device /dev/bus/usb/0/0] Class .................. 0x00 Subclass ............... 0x00 Protocol ............... 0x00 Max Endpoint 0 Packet .. 64 USB Version ............ 0x0100 Vendor ID .............. 0x0763 Product ID ............. 0x0150 Product Version ........ 0x0125 Manufacturer String .... " " Product String ......... " " Serial Number .......... "" [Configuration 0] Configuration String . " " [Interface 0] [Alternate 0 active] Class .............. 0x01 Subclass ........... 0x01 Protocol ........... 0x00 Interface String ... "" [Descriptor 0] Type ............. 0x24 Data ............. 01 00 01 09 00 01 01 [Interface 1] [Alternate 0 active] Class .............. 0x01 Subclass ........... 0x03 Protocol ........... 0x00 Interface String ... "" [Endpoint 0] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Input [Endpoint 1] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Output [Descriptor 0] Type ............. 0x24 Data ............. 01 00 01 41 00 [Descriptor 1] Type ............. 0x24 Data ............. 02 01 01 00 [Descriptor 2] Type ............. 0x24 Data ............. 02 02 02 00 [Descriptor 3] Type ............. 0x24 Data ............. 03 01 03 01 02 01 00 [Descriptor 4] Type ............. 0x24 Data ............. 03 02 04 01 01 01 00 [Descriptor 5] Type ............. 0x25 Data ............. 01 01 03 [Descriptor 6] Type ............. 0x25 Data ............. 01 01 01 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 17:12:19 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 01 Jul 2009 15:12:19 -0000 Subject: [Haiku-bugs] [Haiku] #4054: gunzip : does not work as expected Message-ID: <041.259209175623027f70bc67a483860ab8@haiku-os.org> #4054: gunzip : does not work as expected ---------------------------------------------+------------------------------ Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ r31232-gcc2 [[BR]] gunzip does not properly extract it's contents. It appears to simply remove the extension. [[BR]] Tested with [http://dev.haiku-os.org/raw- attachment/ticket/4005/build_jam_j4_0.txt.gz ticket/4005/build_jam_j4_0.txt.gz] The above gz file was confirmed working with FreeBSD gzip 20070711 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 01:18:23 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 01 Jul 2009 23:18:23 -0000 Subject: [Haiku-bugs] [Haiku] #4055: Replicants & Shift+Alt+K (Arrange All?) Message-ID: <041.0df72ee4b5c41086be0569c13afd8fec@haiku-os.org> #4055: Replicants & Shift+Alt+K (Arrange All?) ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- There is an issue with using Desktop replicants and Tracker's ability to re-arrange icons (Shift+Alt+K). When the replicant such as workspaces is covering the upper left hand corner, Shift+Alt+K will properly re-arrange the icons, except a single volume icon. That single volume icon will appear underneath the replicant. If Disks Icon is enabled, the disks icon will appear underneath the replicant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 1 16:38:45 2009 From: trac at haiku-os.org (someguy) Date: Wed, 01 Jul 2009 14:38:45 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.00233ba71acf36f2afd2263a6950f906@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by someguy): I glanced at the screen perflet code and it looks to specifically handle only Radeon graphics cards for multimon support. There's some "danger will Ronbinson" messages to this effect surrounding the multimon.x files as well. I changed Dualhead Setup by commenting out the check for dual head support so that the buttons were active/selectable. It was unable to put the displays in dual head mode (though it certainly tried). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 09:07:24 2009 From: trac at haiku-os.org (axeld) Date: Thu, 02 Jul 2009 07:07:24 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.fdb394996cee47aff9cdd65427f3c85d@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): The hack Thomas introduced for dual head is only a temporary solution that will be removed sooner or later (probably: later :-), so if you want to add support for it, it's not wasted time either). The plan is to make the accelerant API multi-head capable. I wanted to start playing with the intel driver to create an API for this (or maybe just an API extension, if possible). In any case, I think it's more convenient to have only one driver per card, and deal with the multi-head stuff only in the accelerant. Maybe via cloning the accelerant for each head which would allow to pull this off with only minimal API changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 15:36:03 2009 From: trac at haiku-os.org (diver) Date: Thu, 02 Jul 2009 13:36:03 -0000 Subject: [Haiku-bugs] [Haiku] #4056: [app_server] switching workspaces doesn't properly redraw selection Message-ID: <040.abd2038fe35743c8ffdc109459ca8529@haiku-os.org> #4056: [app_server] switching workspaces doesn't properly redraw selection --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Take any open window and make a selection around it on a desktop.[[BR]] Hold your mouse and switch to the second workspace using alt+f2.[[BR]] Tested in vbox using r31364. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 18:10:10 2009 From: trac at haiku-os.org (aldeck) Date: Thu, 02 Jul 2009 16:10:10 -0000 Subject: [Haiku-bugs] [Haiku] #4057: Boot fails, new ATA stack Message-ID: <041.a1f66e71e5d7d7600e39b1c1f089716d@haiku-os.org> #4057: Boot fails, new ATA stack -----------------------+---------------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Boot fails and enters KDL with: {{{ PANIC: did not find any boot partitions! Welcome to KDL... Thread 13 "main2" running on CPU 0 }}} r31372 built with HAIKU_ATA_STACK=1[[BR]] Core 1 duo laptop, PATA hardrive. lspci {{{ 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1) 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 06:00.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 06:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 06:00.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 0a) 06:00.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05) 06:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) }}} hdparm -i /dev/sda {{{ /dev/sda: Model=FUJITSU MHV2120AT PL , FwRev=000000A0, SerialNo= NSA4T5B255HV Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7 * signifies the current active mode }}} screenshots of the syslog follows. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 18:12:19 2009 From: trac at haiku-os.org (aldeck) Date: Thu, 02 Jul 2009 16:12:19 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack Message-ID: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Boot fails and enters KDL with: {{{ PANIC: did not find any boot partitions! Welcome to KDL... Thread 13 "main2" running on CPU 0 }}} r31372 built with HAIKU_ATA_STACK=1[[BR]] Core 1 duo laptop, PATA hardrive. lspci {{{ 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1) 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 06:00.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 06:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 06:00.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 0a) 06:00.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05) 06:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) }}} hdparm -i /dev/sda {{{ /dev/sda: Model=FUJITSU MHV2120AT PL , FwRev=000000A0, SerialNo= NSA4T5B255HV Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7 * signifies the current active mode }}} screenshots of the syslog already uploaded there (i can upload them to trac if prefered):[[BR]] http://haikubeat.free.fr/files/testing/ata_stack -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 18:18:56 2009 From: trac at haiku-os.org (aldeck) Date: Thu, 02 Jul 2009 16:18:56 -0000 Subject: [Haiku-bugs] [Haiku] #4057: Boot fails, new ATA stack In-Reply-To: <041.a1f66e71e5d7d7600e39b1c1f089716d@haiku-os.org> References: <041.a1f66e71e5d7d7600e39b1c1f089716d@haiku-os.org> Message-ID: <050.7d97994a62615840534969b3c4a7e026@haiku-os.org> #4057: Boot fails, new ATA stack ------------------------+--------------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: junk | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => junk Comment: sorry -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 18:36:48 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 02 Jul 2009 16:36:48 -0000 Subject: [Haiku-bugs] [Haiku] #4059: PackageInstaller needs a "Yes to all" button in dialog box Message-ID: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> #4059: PackageInstaller needs a "Yes to all" button in dialog box -------------------------------------------+-------------------------------- Reporter: scottmc | Owner: sil2100 Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------------+-------------------------------- When reinstalling from a pkg file sometimes the files already exist, so you get a dialog box where it asks if you want to overwrite it, and your options are yes, no, and abort. It would be nice to have an option to answer "Yes to all". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 2 22:40:44 2009 From: trac at haiku-os.org (tqh) Date: Thu, 02 Jul 2009 20:40:44 -0000 Subject: [Haiku-bugs] [Haiku] #2801: rtl8169 stops responding after a while In-Reply-To: <038.744bbcb52c02de1c176b8ab052f75ee6@haiku-os.org> References: <038.744bbcb52c02de1c176b8ab052f75ee6@haiku-os.org> Message-ID: <047.9652211066e3d7308bb57155dc64bde4@haiku-os.org> #2801: rtl8169 stops responding after a while -----------------------------+---------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Changes (by tqh): * cc: fredrik.holmqvist@? (added) Comment: I enabled debug in the driver, but all I can see is that writes start to timeout 'rtl8169_write timeout' or similar. Otherwise it's mostly read write read .. and so on. Dunno how to track this down or test this so ideas welcome. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 02:11:47 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 03 Jul 2009 00:11:47 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.c862ebad18d5a869401eb2cff3ca820f@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw -----------------------------------+---------------------------------------- Reporter: PieterPanman | Owner: aldeck Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3914, 4038 -----------------------------------+---------------------------------------- Changes (by aldeck): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31378 It ended up being a single window navigation issue, that would happen only under certain conditions, see commit log.[[BR]] For reference, here is the test case (100% reproducible) that i used after understanding the problem: 1) switch to single window navigation mode.[[BR]] in any folder, add an additional attribute column[[BR]] create a new sub folder[[BR]] navigate immediately into it[[BR]] trigger an invalidation on the column title bar (moving a window over it, or switching workspaces)[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 02:51:46 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 03 Jul 2009 00:51:46 -0000 Subject: [Haiku-bugs] [Haiku] #3828: Icon positioning/selection got screwed up. In-Reply-To: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> References: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> Message-ID: <047.0c74f936558437bb34912a143239e2e5@haiku-os.org> #3828: Icon positioning/selection got screwed up. ----------------------------------+----------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by aldeck): I'm having a look, will assign to me if i get enough clues... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 11:23:03 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 03 Jul 2009 09:23:03 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.8b94c93805720f284c65f842e2a3e9d3@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Axel, For the app_server this would mean handling two heads on one card would be the same as handling two different cards. Correct? That's what I would love to see as well.. :-) A long time ago I already starting pulling things 'apart' in the driver and I still hav e this in the back of my head when doing updates. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 15:38:43 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 03 Jul 2009 13:38:43 -0000 Subject: [Haiku-bugs] [Haiku] #3828: Icon positioning/selection got screwed up. In-Reply-To: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> References: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> Message-ID: <047.ad2bffb08297e12a5c935f3c2d049128@haiku-os.org> #3828: Icon positioning/selection got screwed up. ----------------------------------+----------------------------------------- Reporter: bga | Owner: aldeck Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by aldeck): * owner: stippi => aldeck * status: new => assigned Comment: I added a check to verify that poses in fVSPoseList are indeed always vertically sorted, and confirmed that it gets broken a some point. As it is used to speed up the intersection test, some poses are wrongly excluded from the test. Didn't find a problem in stippi's changes so he might still be innocent ;) Will find out soon hopefully. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 21:09:30 2009 From: trac at haiku-os.org (PieterPanman) Date: Fri, 03 Jul 2009 19:09:30 -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.9f46a8d14ae72311ca00c0c9ea5f3ba8@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by PieterPanman): I used to have the same problem (My integrated 6150 would only show a black screen on both, not turn off the screens). Vesa worked fine. But with the current revision it works fine, so maybe your latest commits fixed something Rudolf :) Bedankt! It does start at 800x600 for the very first time after I built haiku. Don't know if that's normal. Current revision: r31396. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 22:33:40 2009 From: trac at haiku-os.org (Adek336) Date: Fri, 03 Jul 2009 20:33:40 -0000 Subject: [Haiku-bugs] [Haiku] #4060: userguide: minor path correction Message-ID: <042.b61bb59f6db6dcaa11cfeda3609e9c41@haiku-os.org> #4060: userguide: minor path correction -----------------------+---------------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The following fixes a minor path correction trunk/haiku/build/jam -> haiku/trunk/build/jam {{{ Index: docs/userguide/en/installation/install-source-linux.html =================================================================== --- docs/userguide/en/installation/install-source-linux.html (wersja 31397) +++ docs/userguide/en/installation/install-source-linux.html (kopia robocza) @@ -87,7 +87,7 @@

Now you could already start to build RAW or VMWare images. Before we come to that, however, let's have a look at the UserBuildConfig that can be used to customize and automate some things.

-

In trunk/haiku/build/jam/ there's a UserBuildConfig.ReadMe that explains various options. Don't simply rename it and use it as UserBuildConfig!

+

In haiku/trunk/build/jam/ there's a UserBuildConfig.ReadMe that explains various options. Don't simply rename it and use it as UserBuildConfig!

You start by duplicating the UserBuildConfig.sample and removing the .sample suffix to get your UserBuildConfig. From the .ReadMe you can copy interesting parts into your config and customize them there.

    }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 22:58:44 2009 From: trac at haiku-os.org (jprostko) Date: Fri, 03 Jul 2009 20:58:44 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.6b850805b126acfd296cc69736c89430@haiku-os.org> #3690: Copy file to USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by jprostko): * cc: joe.prostko+haiku@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 23:18:31 2009 From: trac at haiku-os.org (Adek336) Date: Fri, 03 Jul 2009 21:18:31 -0000 Subject: [Haiku-bugs] [Haiku] #4061: userguide: minor correction for UserBuildConfig option for keymaps Message-ID: <042.e8fedeb2b74ceaa0dcc4da5d3878e7bc@haiku-os.org> #4061: userguide: minor correction for UserBuildConfig option for keymaps -----------------------+---------------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The following fixes the instruction on choosing a keymap through UserBuildConfig: {{{ Index: docs/userguide/en/installation/install-source-linux.html =================================================================== --- docs/userguide/en/installation/install-source-linux.html (wersja 31397) +++ docs/userguide/en/installation/install-source-linux.html (kopia robocza) @@ -112,7 +112,7 @@ 
    # Add symlink/file (timezone and keymap settings) to the image.
  AddSymlinkToHaikuImage home config settings
         : /boot/system/etc/timezones/Europe/Paris : timezone ;
 -AddFilesToHaikuImage home config settings : German
 +AddFilesToHaikuImage home config settings : German
         : Key_map ;

  1. The build process can be fine tuned until it fits your needs. You could create your own folder haiku/trunk/user_data/ and put files there that are then copied or unzipped into the image. Zipping is important when dealing with Haiku files and their attributes, because zipping them up will preserve them on non-BFS partitions.
    For example:

    }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 3 23:32:33 2009 From: trac at haiku-os.org (zooey) Date: Fri, 03 Jul 2009 21:32:33 -0000 Subject: [Haiku-bugs] [Haiku] #3137: Updated bison 2.4 package appears to not correctly generate ftpd's ftpcmd.c In-Reply-To: <044.17a5c552f2d096d4215aefd1a0fb6d13@haiku-os.org> References: <044.17a5c552f2d096d4215aefd1a0fb6d13@haiku-os.org> Message-ID: <053.c13a65485453ad034a533e3daab6f665@haiku-os.org> #3137: Updated bison 2.4 package appears to not correctly generate ftpd's ftpcmd.c ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3156 ---------------------------+------------------------------------------------ Changes (by zooey): * status: new => closed * resolution: => fixed Comment: Fixed in r31401 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 4 10:51:09 2009 From: trac at haiku-os.org (excaliber) Date: Sat, 04 Jul 2009 08:51:09 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.cdc5e0309f954b2cdeac9dfb2720edb3@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by excaliber): I have a similar problem with a GeForce 6200 AGP. It has one digital and one analog output. With r31402 on first boot with both displays connected, after the boot screen the analog output turns off and the digital is black with an out of range error. With one display connected (digital or analog) the nvidia driver loads and works properly. Rebooting and connecting the second display again, the analog turns off like before and the digital now uses the vesa driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 06:02:50 2009 From: trac at haiku-os.org (leavengood) Date: Sun, 05 Jul 2009 04:02:50 -0000 Subject: [Haiku-bugs] [Haiku] #4062: Switcher does not always switch workspaces when a Tracker window is selected in the list Message-ID: <045.2f4f169be24f396522a20d862b56e2c6@haiku-os.org> #4062: Switcher does not always switch workspaces when a Tracker window is selected in the list ----------------------------------+----------------------------------------- Reporter: leavengood | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- If there is a Tracker window in another workspace and it is selected in the list, many times Switcher will not change to that workspace. The simplest way to reproduce is to have a single Tracker window in another workspace and try to switch to it. Having a couple Tracker windows seems to fix the problem, sometimes. It is quite inconsistent so I assume it is a bug. I don't know if somehow the Desktop window is screwing things up for Tracker, because other apps do not seem to have this problem. Also when the other window is selected and the workspace is not changed, the Desktop has the focus, hence my suspicion. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 08:38:04 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 05 Jul 2009 06:38:04 -0000 Subject: [Haiku-bugs] [Haiku] #2041: In some cases, __mbrtowc can enter in an infinite loop In-Reply-To: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> References: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> Message-ID: <047.915703001be0ec8dcfe8597308ca4470@haiku-os.org> #2041: In some cases, __mbrtowc can enter in an infinite loop -------------------------------+-------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): Using the wchar fix to build sed-4.2.1 I now get this when I run make check: {{{ ~/sed-4.2.1> make check Making check in lib make[1]: Entering directory `/boot/home/sed-4.2.1/lib' make check-recursive make[2]: Entering directory `/boot/home/sed-4.2.1/lib' make[3]: Entering directory `/boot/home/sed-4.2.1/lib' make[3]: Nothing to be done for `check-am'. make[3]: Leaving directory `/boot/home/sed-4.2.1/lib' make[2]: Leaving directory `/boot/home/sed-4.2.1/lib' make[1]: Leaving directory `/boot/home/sed-4.2.1/lib' Making check in po make[1]: Entering directory `/boot/home/sed-4.2.1/po' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/boot/home/sed-4.2.1/po' Making check in sed make[1]: Entering directory `/boot/home/sed-4.2.1/sed' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/boot/home/sed-4.2.1/sed' Making check in doc make[1]: Entering directory `/boot/home/sed-4.2.1/doc' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/boot/home/sed-4.2.1/doc' Making check in testsuite make[1]: Entering directory `/boot/home/sed-4.2.1/testsuite' make make[2]: Entering directory `/boot/home/sed-4.2.1/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/boot/home/sed-4.2.1/testsuite' make check-TESTS make[2]: Entering directory `/boot/home/sed-4.2.1/testsuite' PASS: appquit PASS: enable PASS: sep PASS: inclib PASS: 8bit PASS: newjis PASS: xabcx PASS: dollar PASS: noeol PASS: noeolw PASS: modulo PASS: numsub PASS: numsub2 PASS: numsub3 PASS: numsub4 PASS: numsub5 PASS: 0range PASS: bkslashes PASS: head PASS: madding PASS: mac-mf PASS: empty PASS: xbxcx PASS: xbxcx3 PASS: recall PASS: recall2 PASS: xemacs PASS: fasts PASS: uniq PASS: manis PASS: khadafy PASS: linecnt PASS: eval PASS: distrib PASS: 8to7 PASS: y-bracket PASS: y-newline PASS: allsub PASS: cv-vars PASS: classes PASS: middle PASS: bsd PASS: stdin PASS: flipcase PASS: insens PASS: subwrite PASS: writeout PASS: readin PASS: insert make[3]: Entering directory `/boot/home/sed-4.2.1/testsuite' echo "LANG=ru_RU.UTF-8" \ " ../sed/sed -f ./utf8-1.sed" \ "< ./utf8-1.inp | LC_ALL=C tr -d \\r > utf8-1.out"; \ LANG=ru_RU.UTF-8 \ ../sed/sed -f ./utf8-1.sed \ < ./utf8-1.inp | LC_ALL=C tr -d \\r > utf8-1.out; \ cmp ./utf8-1.good utf8-1.out && exit 0; \ cmp ./utf8-1.inp utf8-1.out || exit 1; \ locale > utf8-1.info 2>/dev/null || { rm utf8-1.info; :>utf8-1.skip; exit 77; }; \ . utf8-1.info; rm utf8-1.info; \ case "$LC_CTYPE" in \ *UTF-8 | *UTF8 | *utf8 | *utf-8) \ echo " ../sed/sed -f ./utf8-1.sed" \ " < ./utf8-1.inp | LC_ALL=C tr -d \\r > utf8-1.out"; \ ../sed/sed -f ./utf8-1.sed \ < ./utf8-1.inp | LC_ALL=C tr -d \\r > utf8-1.out; \ cmp ./utf8-1.good utf8-1.out && exit 0; \ cmp ./utf8-1.inp utf8-1.out || exit 1 ;; \ *) ;; \ esac; \ :>utf8-1.skip; exit 77 LANG=ru_RU.UTF-8 ../sed/sed -f ./utf8-1.sed < ./utf8-1.inp | LC_ALL=C tr -d \r > utf8-1.out ./utf8-1.good utf8-1.out differ: char 1, line 1 ./utf8-1.inp utf8-1.out differ: char 1, line 1 make[3]: *** [utf8-1] Error 1 make[3]: Leaving directory `/boot/home/sed-4.2.1/testsuite' XFAIL: utf8-1 make[3]: Entering directory `/boot/home/sed-4.2.1/testsuite' echo "LANG=ru_RU.UTF-8" \ " ../sed/sed -f ./utf8-2.sed" \ "< ./utf8-2.inp | LC_ALL=C tr -d \\r > utf8-2.out"; \ LANG=ru_RU.UTF-8 \ ../sed/sed -f ./utf8-2.sed \ < ./utf8-2.inp | LC_ALL=C tr -d \\r > utf8-2.out; \ cmp ./utf8-2.good utf8-2.out && exit 0; \ cmp ./utf8-2.inp utf8-2.out || exit 1; \ locale > utf8-2.info 2>/dev/null || { rm utf8-2.info; :>utf8-2.skip; exit 77; }; \ . utf8-2.info; rm utf8-2.info; \ case "$LC_CTYPE" in \ *UTF-8 | *UTF8 | *utf8 | *utf-8) \ echo " ../sed/sed -f ./utf8-2.sed" \ " < ./utf8-2.inp | LC_ALL=C tr -d \\r > utf8-2.out"; \ ../sed/sed -f ./utf8-2.sed \ < ./utf8-2.inp | LC_ALL=C tr -d \\r > utf8-2.out; \ cmp ./utf8-2.good utf8-2.out && exit 0; \ cmp ./utf8-2.inp utf8-2.out || exit 1 ;; \ *) ;; \ esac; \ :>utf8-2.skip; exit 77 LANG=ru_RU.UTF-8 ../sed/sed -f ./utf8-2.sed < ./utf8-2.inp | LC_ALL=C tr -d \r > utf8-2.out ./utf8-2.good utf8-2.out differ: char 1, line 1 ./utf8-2.inp utf8-2.out differ: char 1, line 1 make[3]: *** [utf8-2] Error 1 make[3]: Leaving directory `/boot/home/sed-4.2.1/testsuite' XFAIL: utf8-2 make[3]: Entering directory `/boot/home/sed-4.2.1/testsuite' echo "LANG=ru_RU.UTF-8" \ " ../sed/sed -f ./utf8-3.sed" \ "< ./utf8-3.inp | LC_ALL=C tr -d \\r > utf8-3.out"; \ LANG=ru_RU.UTF-8 \ ../sed/sed -f ./utf8-3.sed \ < ./utf8-3.inp | LC_ALL=C tr -d \\r > utf8-3.out; \ cmp ./utf8-3.good utf8-3.out && exit 0; \ cmp ./utf8-3.inp utf8-3.out || exit 1; \ locale > utf8-3.info 2>/dev/null || { rm utf8-3.info; :>utf8-3.skip; exit 77; }; \ . utf8-3.info; rm utf8-3.info; \ case "$LC_CTYPE" in \ *UTF-8 | *UTF8 | *utf8 | *utf-8) \ echo " ../sed/sed -f ./utf8-3.sed" \ " < ./utf8-3.inp | LC_ALL=C tr -d \\r > utf8-3.out"; \ ../sed/sed -f ./utf8-3.sed \ < ./utf8-3.inp | LC_ALL=C tr -d \\r > utf8-3.out; \ cmp ./utf8-3.good utf8-3.out && exit 0; \ cmp ./utf8-3.inp utf8-3.out || exit 1 ;; \ *) ;; \ esac; \ :>utf8-3.skip; exit 77 LANG=ru_RU.UTF-8 ../sed/sed -f ./utf8-3.sed < ./utf8-3.inp | LC_ALL=C tr -d \r > utf8-3.out ./utf8-3.good utf8-3.out differ: char 1, line 1 ./utf8-3.inp utf8-3.out differ: char 1, line 1 make[3]: *** [utf8-3] Error 1 make[3]: Leaving directory `/boot/home/sed-4.2.1/testsuite' XFAIL: utf8-3 make[3]: Entering directory `/boot/home/sed-4.2.1/testsuite' echo "LANG=ru_RU.UTF-8" \ " ../sed/sed -f ./utf8-4.sed" \ "< ./utf8-4.inp | LC_ALL=C tr -d \\r > utf8-4.out"; \ LANG=ru_RU.UTF-8 \ ../sed/sed -f ./utf8-4.sed \ < ./utf8-4.inp | LC_ALL=C tr -d \\r > utf8-4.out; \ cmp ./utf8-4.good utf8-4.out && exit 0; \ cmp ./utf8-4.inp utf8-4.out || exit 1; \ locale > utf8-4.info 2>/dev/null || { rm utf8-4.info; :>utf8-4.skip; exit 77; }; \ . utf8-4.info; rm utf8-4.info; \ case "$LC_CTYPE" in \ *UTF-8 | *UTF8 | *utf8 | *utf-8) \ echo " ../sed/sed -f ./utf8-4.sed" \ " < ./utf8-4.inp | LC_ALL=C tr -d \\r > utf8-4.out"; \ ../sed/sed -f ./utf8-4.sed \ < ./utf8-4.inp | LC_ALL=C tr -d \\r > utf8-4.out; \ cmp ./utf8-4.good utf8-4.out && exit 0; \ cmp ./utf8-4.inp utf8-4.out || exit 1 ;; \ *) ;; \ esac; \ :>utf8-4.skip; exit 77 LANG=ru_RU.UTF-8 ../sed/sed -f ./utf8-4.sed < ./utf8-4.inp | LC_ALL=C tr -d \r > utf8-4.out ./utf8-4.good utf8-4.out differ: char 1, line 1 ./utf8-4.inp utf8-4.out differ: char 1, line 1 make[3]: *** [utf8-4] Error 1 make[3]: Leaving directory `/boot/home/sed-4.2.1/testsuite' XFAIL: utf8-4 PASS: badenc PASS: inplace-hold PASS: brackets PASS: help PASS: version PASS: file PASS: quiet PASS: factor PASS: binary3 PASS: binary2 PASS: binary PASS: dc ====================================================== All 65 tests behaved as expected (4 expected failures) ====================================================== make[2]: Leaving directory `/boot/home/sed-4.2.1/testsuite' make[1]: Leaving directory `/boot/home/sed-4.2.1/testsuite' make[1]: Entering directory `/boot/home/sed-4.2.1' make[1]: Leaving directory `/boot/home/sed-4.2.1' ~/sed-4.2.1> }}} So it appears that the wchar fix will take care of the reported failures with sed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 12:52:12 2009 From: trac at haiku-os.org (fano) Date: Sun, 05 Jul 2009 10:52:12 -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.419e01826c88a1f61ea0277d9834a8e3@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by fano): I've not found r31396 version on download... I've tried the last version r31402 nothing "Out of range". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 18:06:02 2009 From: trac at haiku-os.org (idefix) Date: Sun, 05 Jul 2009 16:06:02 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point Message-ID: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Installer calls InstallerInitScript and InstallerFinishScript without escaping the mount point, causing the scripts to fail when the name of the volume has special characters (like a space or parentheses): {{{ /bin/sh: -c: line 1: syntax error near unexpected token `(' /bin/sh: -c: line 1: `/bin/sh /boot/system/boot/InstallerInitScript /installer(test)' ignoring 'var'. 343371756 bytes to read in 9358 files ignoring 'var'. /bin/sh: -c: line 1: syntax error near unexpected token `(' /bin/sh: -c: line 1: `/bin/sh /boot/system/boot/InstallerFinishScript /installer(test)' 327.46 MB written (0.96 MB/s) }}} Consequently, the volume isn't made bootable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 22:43:32 2009 From: trac at haiku-os.org (oco) Date: Sun, 05 Jul 2009 20:43:32 -0000 Subject: [Haiku-bugs] [Haiku] #2041: In some cases, __mbrtowc can enter in an infinite loop In-Reply-To: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> References: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> Message-ID: <047.c8c1f80c343445242f92c5808877e810@haiku-os.org> #2041: In some cases, __mbrtowc can enter in an infinite loop -------------------------------+-------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by oco): The 32bit-wchar_t branch (r31395) also fix the problem while building ruby 1.8. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 5 23:46:14 2009 From: trac at haiku-os.org (oco) Date: Sun, 05 Jul 2009 21:46:14 -0000 Subject: [Haiku-bugs] [Haiku] #4064: [patch]cond_wait always return EAGAIN with an unitialized pthread_cond_t (pthread_cond.c) Message-ID: <038.41dacccbe9163cc4c5a940ad4d12102d@haiku-os.org> #4064: [patch]cond_wait always return EAGAIN with an unitialized pthread_cond_t (pthread_cond.c) -----------------------+---------------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- cond_wait always return EAGAIN with an unitialized pthread_cond_t (pthread_cond.c). This function is used by pthread_cond_wait and pthread_cond_timedwait.[[BR]] I discover the problem while trying to compile current ruby trunk (1.9). miniruby (a reduced version of ruby used in the build process) stop while calling pthread_cond_timedwait. The return value is always EAGAIN. I use r31395 of haiku.[[BR]] After looking at the source code, i think we should check the return value of create_sem instead of cond->sem. This is what is in the first patch.[[BR]] I found similar code in mutex_lock (pthread_mutex.c). Maybe, we should also use atomic_test_and_set to assign cond->sem. This is what is added in the second patch. But, as i am not sure of what i am proposing (i am a newbie with threads), careful revue is needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 03:31:22 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 01:31:22 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.d7648aa1bf8357cc582e4c1037737cff@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Please don't attach zipped text files. That's just annoying to browse. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 03:41:56 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 01:41:56 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.10ca1de1d9d5967554c68ae2aa7246b5@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): As you wish! I had thought that the 488k limit was global, not per-file, sorry. Plain text files attached now. Now, I can't remove the gzipped files; if someone else can, please, do it on my behalf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 03:52:16 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 06 Jul 2009 01:52:16 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.42536e31a14c0772669d173bc6c0bb6b@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): deleted most .gz attachments. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:00:01 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 02:00:01 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.5f97a49d73d3d89a6eca6443c2c917c4@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Holy Cow. For some reason Trac decided to re-pack the original gzipped text files, and I blindly downloaded and reattached them uncompressed without checking. Turns out that Trac gave me gzipped Trac-annotated pages containing an embedded gzipped file totally corrupted, and even the raw- attachment's are gzipped *twice*. That totally tripped me, and since that was over a month ago and only looking at the small (non-)decompressed size I was lead to believe it was unnecessary. But it was not. The thing is, those logs are indeed bigger than 488k, build_jam_j4_1.txt being 1.382KB big and build_jam_j4_2.txt 1.073KB big. That's why I compressed them all. So, I'm very sorry for the annoyance, but it's hardly my fault that Trac has a size limit, and it's *totally* not my fault that it acted up and went nuts as to how those attachments were stored internally. Recapitulating: you have to download the raw-attachment's, gunzip them, *and* gunzip the resulting files to get the plaintext ones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:03:57 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 06 Jul 2009 02:03:57 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.46eef9d2328dba7398cf2b03a8179744@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Replying to [comment:7 meianoite]: > Holy Cow. For some reason Trac decided to re-pack the original gzipped text files, and I blindly downloaded and reattached them uncompressed without checking. No, i believe this is an error in Haiku's gunzip : http://dev.haiku- os.org/ticket/4054 (this is why i left a single .txt.gz file attached on this ticket) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:04:29 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 02:04:29 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.b5279aad877c53b1c225ce0ec6a7e547@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): The problem in the 0th log is fixed in r31415. The problem in the 4th log is a known problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:06:30 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 02:06:30 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.053a6b3f771a3db66d31bb322f6f870f@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Log 3 is the same problem as 4. The logs 1 and 2 are garbage now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:08:15 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 02:08:15 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.72b0439c30b2ceaa9188d89f55629cc1@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:8 mmadia]: > No, i believe this is an error in Haiku's gunzip : http://dev.haiku- os.org/ticket/4054 > (this is why i left a single .txt.gz file attached on this ticket) I don't think so. I'm not running Haiku right now, but Windows, and the gzipped files were unpacked by 7-zip. This makes me quite sure it's is a Trac issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:09:12 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 02:09:12 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.c62268b7055ef9d54237b090dc6fabf2@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:10 bonefish]: > Log 3 is the same problem as 4. The logs 1 and 2 are garbage now. I've reattached them back in their original gzipped form, please download them once more. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:11:51 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 06 Jul 2009 02:11:51 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.14791cf45905e4f8c07b9280ff9bba93@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Replying to [comment:11 meianoite]: > I don't think so. I'm not running Haiku right now, but Windows, and the gzipped files were unpacked by 7-zip. This makes me quite sure it's is a Trac issue. Ok, you're right. In Haiku, I was using Trac to download the file. In FreeBSD, i used `wget http://dev.haiku-os.org/raw- attachment/ticket/4005/build_jam_j4_4.txt.gz`, which worked as expected. Trying that command in Haiku confirmed the issue being in Trac. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:15:17 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 06 Jul 2009 02:15:17 -0000 Subject: [Haiku-bugs] [Haiku] #4054: gunzip : does not work as expected In-Reply-To: <041.259209175623027f70bc67a483860ab8@haiku-os.org> References: <041.259209175623027f70bc67a483860ab8@haiku-os.org> Message-ID: <050.a67eacfb08d6cb7144d49d87cfed627d@haiku-os.org> #4054: gunzip : does not work as expected ----------------------------------------------+----------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by mmadia): * status: new => closed * resolution: => invalid Comment: Turns out, this is an issue in Trac. For more information, see: http://dev .haiku-os.org/ticket/4005#comment:7 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:17:45 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 02:17:45 -0000 Subject: [Haiku-bugs] [Haiku] #4054: gunzip : does not work as expected In-Reply-To: <041.259209175623027f70bc67a483860ab8@haiku-os.org> References: <041.259209175623027f70bc67a483860ab8@haiku-os.org> Message-ID: <050.254642c458c9f0d1900a1b64c708616e@haiku-os.org> #4054: gunzip : does not work as expected ----------------------------------------------+----------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by meianoite): As mentioned on [http://dev.haiku-os.org/ticket/4005#comment:11], the "gzipped" file that Trac gave me was a XHTML file with the contents of the gzipped file interspersed with the table Trac generates to syntax- highlight and linenumber source code files. In other words, it was totally garbled beyond recovery, as it probably interpreted some bytes as UTF or what have you and modified the resulting encoding. Downloading the raw-attachment gave me something I had to gunzip *twice* in order to produce the original file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:20:08 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 02:20:08 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.dfe63ab514c68219ed7dd428ce90fb96@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): mmadia, while you are at it, could you please remove the attachments not marked as (proper)? Thanks :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:37:23 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 02:37:23 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.59d2083568d36d466d502059a7f68d26@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): The problem in log 1 is fixed in r31416 (unless there are more dependencies between timezone files). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 04:42:11 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 02:42:11 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.78bfb7b71fcd94a36e39cfaf1bff3357@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Log 2 shows the same problem as 3 and 4, which is the same as in #1976. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 05:29:15 2009 From: trac at haiku-os.org (leavengood) Date: Mon, 06 Jul 2009 03:29:15 -0000 Subject: [Haiku-bugs] [Haiku] #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character Message-ID: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character ---------------------------+------------------------------------------------ Reporter: leavengood | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I discovered this when trying to log keys while debugging the Twitcher. Whenever I would output the left arrow key (cast to a char) in the syslog, tail would quit. Opening the syslog in vim I found that a special character was being printed (^\) and when I put that inside a test file (attached) I found it would cause tail, head, cat and grep to quit (and probably anything else that reads input from a file in the terminal.) To test simply "head -n 3 tailquit.txt" to see it work and then "head -n 4 tailquit.txt" to see head quit. The same test file does not cause problems on Linux. I am filing this under Kernel since I assume it has something to do with the tty emulation. If I am wrong please simply reassign to the correct place. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 08:32:43 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 06 Jul 2009 06:32:43 -0000 Subject: [Haiku-bugs] [Haiku] #4066: FAT-Error Message-ID: <042.2fb40b6e7c6766169ef861ef6c688cad@haiku-os.org> #4066: FAT-Error ------------------------------+--------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- I have mounted a USB-Stick read/write in gcc4 build of r31391 from friday and copied some log files for another bugreport to the stick. Then I want to check the files with less, but I got the error in the screenshot. This was on real hardware (EeePC 4G). The vfat-Filessystem was checked with dosfsck from Linux before mounting in Haiku and was OK. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 10:19:43 2009 From: trac at haiku-os.org (axeld) Date: Mon, 06 Jul 2009 08:19:43 -0000 Subject: [Haiku-bugs] [Haiku] #4054: gunzip : does not work as expected In-Reply-To: <041.259209175623027f70bc67a483860ab8@haiku-os.org> References: <041.259209175623027f70bc67a483860ab8@haiku-os.org> Message-ID: <050.d35bf702082a0af5e13824367308ed8f@haiku-os.org> #4054: gunzip : does not work as expected ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: closed => reopened * resolution: invalid => * component: Applications/Command Line Tools => Website/Trac -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 12:33:56 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 10:33:56 -0000 Subject: [Haiku-bugs] [Haiku] #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character In-Reply-To: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> References: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> Message-ID: <054.c54d37dac3368c30f45c25a646ea283c@haiku-os.org> #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character -------------------------+-------------------------------------------------- Reporter: leavengood | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * component: System/Kernel => Drivers/TTY -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 13:00:44 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 11:00:44 -0000 Subject: [Haiku-bugs] [Haiku] #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character In-Reply-To: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> References: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> Message-ID: <054.6f12413cea855e97c0530106d472c234@haiku-os.org> #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character -------------------------+-------------------------------------------------- Reporter: leavengood | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by bonefish): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 13:38:21 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 11:38:21 -0000 Subject: [Haiku-bugs] [Haiku] #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character In-Reply-To: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> References: <045.7b3c7c19f367a4c4d21608da15e97798@haiku-os.org> Message-ID: <054.8b58b78a0bb62663a8eebd883220ecaf@haiku-os.org> #4065: tail, head, cat, grep (and probably more) quit when an input file has a certain special character --------------------------+------------------------------------------------- Reporter: leavengood | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: duplicate | Blockedby: 2409 Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => duplicate * blockedby: => 2409 Comment: Dup of #2409. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 13:40:09 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 11:40:09 -0000 Subject: [Haiku-bugs] [Haiku] #2409: [Terminal] "cat /dev/random" exits after first screen of random data In-Reply-To: <040.af41cabaa7003e9f4df4dc2678ba3242@haiku-os.org> References: <040.af41cabaa7003e9f4df4dc2678ba3242@haiku-os.org> Message-ID: <049.90d281e0b34b119f5c805f39cb63946b@haiku-os.org> #2409: [Terminal] "cat /dev/random" exits after first screen of random data ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 4065 ------------------------------------+--------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r31417. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 14:26:20 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 12:26:20 -0000 Subject: [Haiku-bugs] [Haiku] #1976: Installing Development package failes In-Reply-To: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> References: <044.1be3b03a867ca3f718f12b5ae151f762@haiku-os.org> Message-ID: <053.d9db2f907dbd0f98c0b92eadde202c96@haiku-os.org> #1976: Installing Development package failes ---------------------------+------------------------------------------------ Reporter: plfiorini | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r31419. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 14:27:32 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 12:27:32 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work In-Reply-To: <044.e15562365ab509331da1342399b929be@haiku-os.org> References: <044.e15562365ab509331da1342399b929be@haiku-os.org> Message-ID: <053.d77a8445e19e068a3bc7937f9eaaf9e2@haiku-os.org> #4005: Higher job count parallel builds (jam -j 4 for example) don't work ---------------------------+------------------------------------------------ Reporter: meianoite | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: The script corruption issues are fixed in r31419. In case you find a new problem, please open a new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 17:53:29 2009 From: trac at haiku-os.org (jprostko) Date: Mon, 06 Jul 2009 15:53:29 -0000 Subject: [Haiku-bugs] [Haiku] #4066: FAT-Error In-Reply-To: <042.2fb40b6e7c6766169ef861ef6c688cad@haiku-os.org> References: <042.2fb40b6e7c6766169ef861ef6c688cad@haiku-os.org> Message-ID: <051.0904e843b082a6dddc30916f2120c6f4@haiku-os.org> #4066: FAT-Error ------------------------------+--------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by jprostko): I think this is a dupe of #3690. In any case, I had the same problem, and naturally thrashed my FAT32 drive while having the lovely idea of typing "continue" over and over while in KDL. Fortunately I only lost some of my data when Windows later ran CHKDSK upon reboot. Naturally, only the data I actually cared about got all messed up though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 18:13:36 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 06 Jul 2009 16:13:36 -0000 Subject: [Haiku-bugs] [Haiku] #4066: FAT-Error In-Reply-To: <042.2fb40b6e7c6766169ef861ef6c688cad@haiku-os.org> References: <042.2fb40b6e7c6766169ef861ef6c688cad@haiku-os.org> Message-ID: <051.ab61518c32b528d42c7a742e3f5ce93c@haiku-os.org> #4066: FAT-Error -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Resolution: duplicate | Blockedby: 3690 Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3690 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 19:33:53 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 06 Jul 2009 17:33:53 -0000 Subject: [Haiku-bugs] [Haiku] #4061: userguide: minor correction for UserBuildConfig option for keymaps In-Reply-To: <042.e8fedeb2b74ceaa0dcc4da5d3878e7bc@haiku-os.org> References: <042.e8fedeb2b74ceaa0dcc4da5d3878e7bc@haiku-os.org> Message-ID: <051.0770717e22c238411c6edd74bab64f34@haiku-os.org> #4061: userguide: minor correction for UserBuildConfig option for keymaps ------------------------+--------------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by humdinger): * status: new => closed * resolution: => fixed Comment: Applied with r31428. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 19:34:19 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 06 Jul 2009 17:34:19 -0000 Subject: [Haiku-bugs] [Haiku] #4060: userguide: minor path correction In-Reply-To: <042.b61bb59f6db6dcaa11cfeda3609e9c41@haiku-os.org> References: <042.b61bb59f6db6dcaa11cfeda3609e9c41@haiku-os.org> Message-ID: <051.c18a105ae62426b11399b2cd3602238c@haiku-os.org> #4060: userguide: minor path correction ------------------------+--------------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by humdinger): * status: new => closed * resolution: => fixed Comment: Applied with r31428. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 20:46:19 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 06 Jul 2009 18:46:19 -0000 Subject: [Haiku-bugs] [Haiku] #4067: Kinesis USB Keyboard is removed after first key is pressed. Message-ID: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> #4067: Kinesis USB Keyboard is removed after first key is pressed. -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- r31375-x86gcc2 native. A Kinesis USB keyboard (model: KB500USB-blk, serial: 82179ub) does not work as expected. After booting Haiku and waiting for syslog to stop growing, I'll plug in the keyboard. Shortly after that, the keyboard will go non-responsive, typically with the last pressed key auto-repeating. The auto-repeat is very odd, it seems to stick with the initial window, even if focus is given to another program. output of listdev and listusb -v are attached. relevant snippet of syslog: {{{ KERN: usb hub 7: port 3: new device connected KERN: usb ehci 1: fullspeed device connected, giving up port ownership KERN: usb hub 2: port 3: new device connected KERN: usb hub 13: port 1: new device connected KERN: usb hub 7: port 3: device removed KERN: void AddOnManager::MessageReceived(BMessage *) what: NMP_ Last message repeated 1 time KERN: error when KB_SET_KEY_REPEAT_RATE, fd:12 KERN: error when KB_SET_KEY_REPEAT_DELAY, fd:-1 MMADIA: syslog stops growing. after pressing a single key, the next few lines display. KERN: usb hub 13: port 1: device removed KERN: usb hub 13: KERN: port 1 disabled KERN: usb hub 13: port 1 is not suspended KERN: void AddOnManager::MessageReceived(BMessage *) what: NMP_ MMADIA: At this point, the keyboard is non-responsive }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 23:44:47 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 21:44:47 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules Message-ID: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Trivial patch to enable timestamping so the optional packages aren't re- downloaded unnecessarily depending on the jam invocation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 6 23:54:22 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 21:54:22 -0000 Subject: [Haiku-bugs] [Haiku] #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker Message-ID: <043.0ad44e7691ab39ada41f72d23b60b5dc@haiku-os.org> #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker ---------------------------------------------+------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Pressing just a modifier doesn't quit the screen blanker. The same holds for any key combo that doesn't generate a KeyDown(). E.g. one can switch workspaces with the screen blanker happily continuing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:08:52 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 22:08:52 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.c24e8ea9908564466b74db320758c7db@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Okay, that doesn't work. According to the wget manual, "Use of -O is not intended to mean simply "use the name file instead of the one in the URL;" rather, it is analogous to shell redirect- ion: wget -O file http://foo is intended to work like wget -O - http://foo > file; file will be truncated immediately, and all downloaded content will be written there. For this reason, -N (for timestamp-checking) is not supported in combination with -O: since file is always newly created, it will always have a very new timestamp. A warning will be issued if this combination is used." I'm not at all familiar with the intricacies of Jam, but iteems like parenthesis aren't being used for subshell invocation like in sh, but for variable substitution. I hope backticks still work in this situation. Would it be valid if we did something like: actions DownloadFile1 { pushd `pwd` cd `dirname $(1)` wget - $(URL) popd } ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:15:34 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 22:15:34 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.f752b80497e664b7d29aea9ed4864b58@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Argh. WikiFormatting. actions DownloadFile1 { pushd {{{`pwd`}}} cd {{{`dirname $(1)`}}} wget -N $(URL) popd } -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:33:16 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 22:33:16 -0000 Subject: [Haiku-bugs] [Haiku] #4070: jam -aqj8 failed for r31430 Message-ID: <044.fd0a07ffa980c66f264509e0ec77eeeb@haiku-os.org> #4070: jam -aqj8 failed for r31430 --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Invocation was: {{{ $ sh -c 'for targets in 2 4; do cd generated.gcc$targets; rm -rf build_packages objects tmp *alternative* build/*cache; cd ..; done' $ svn up At revision 31430. $ cd generated.gcc2 $ ( date; jam -aqj8 @disk; date ) |& tee j8.log }}} And the log is attached. Circa 2MB uncompressed, so it had to be zipped. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:36:19 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 22:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.3ddf4b34bbdccdbfa5e7c5d657d34ac8@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): I don't get the point of this ticket. Please elaborate. Regarding formatting, just enclose code blocks in tripple braces (!{{{ ... }}}). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:46:37 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 22:46:37 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.0e063e477aebb41ebe08e1b8cb965414@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:3 bonefish]: > I don't get the point of this ticket. Please elaborate. First and foremost, it's an enhancement ticket, not a bug report. Maybe what I find to be "enhanced" behaviour is actually considered undesirable by you or other developers, but my rationale is as follows: If you invoje jam with the -a option, it will re-download packages unconditionally. Since I had to do it quite a number of times today because of what became #4070 (to check that I wasn't messing up somewhere else), I thought it would be better for both the servers' bandwidth, and my monthly download limit, if those files weren't redownloaded in case they were identical. Ideally the build system would invoke a port of the to-become Haiku packaging system to check for new versions of packages along with a more robust check of md5/sha1 signatures, and download remote packages only when they differ from the local copy, but I figured that for the time being the timestamping option of wget would suffice. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 00:54:21 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 22:54:21 -0000 Subject: [Haiku-bugs] [Haiku] #4070: jam -aqj8 failed for r31430 In-Reply-To: <044.fd0a07ffa980c66f264509e0ec77eeeb@haiku-os.org> References: <044.fd0a07ffa980c66f264509e0ec77eeeb@haiku-os.org> Message-ID: <053.f46b79db8b40117dc286a9148943bb3a@haiku-os.org> #4070: jam -aqj8 failed for r31430 ---------------------------+------------------------------------------------ Reporter: meianoite | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r31434. BTW, if you find more instances where a generated header doesn't exist yet when a dependent source is compiled, a full log is really not necessary. The error message plus the actions output and error message will suffice completely. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 01:10:05 2009 From: trac at haiku-os.org (meianoite) Date: Mon, 06 Jul 2009 23:10:05 -0000 Subject: [Haiku-bugs] [Haiku] #4070: jam -aqj8 failed for r31430 In-Reply-To: <044.fd0a07ffa980c66f264509e0ec77eeeb@haiku-os.org> References: <044.fd0a07ffa980c66f264509e0ec77eeeb@haiku-os.org> Message-ID: <053.24122952f08840ef075d16e4c0acf044@haiku-os.org> #4070: jam -aqj8 failed for r31430 ---------------------------+------------------------------------------------ Reporter: meianoite | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by meianoite): Oh. Sorry. I tried to search for "error:" to no avail, so I thought the error would be somewhere else on the build system. Now I backtraced the error log, found that bash didn't compile because of trap.o, and that trap.o failed because of builtext.h, and found the relevant error messages that you mentioned. And figured that jam's error message looks like "...failed ". I promise to produce more succinct logs next time ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 01:34:40 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 06 Jul 2009 23:34:40 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.efdb21fd0c6abb780239f30534aa0cd5@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Replying to [comment:4 meianoite]: > Replying to [comment:3 bonefish]: > > I don't get the point of this ticket. Please elaborate. > > First and foremost, it's an enhancement ticket, not a bug report. Maybe what I find to be "enhanced" behaviour is actually considered undesirable by you or other developers, but my rationale is as follows: > > If you invoje jam with the -a option, it will re-download packages unconditionally. Since I had to do it quite a number of times today because of what became #4070 (to check that I wasn't messing up somewhere else), I thought it would be better for both the servers' bandwidth, and my monthly download limit, if those files weren't redownloaded in case they were identical. Mmh, I don't think I've ever built an image with "-a". I usually just remove the "objects" directory and built normally, which also has the advantage of removing all the files that the build system doesn't know about anymore. > Ideally the build system would invoke a port of the to-become Haiku packaging system to check for new versions of packages along with a more robust check of md5/sha1 signatures, and download remote packages only when they differ from the local copy, but I figured that for the time being the timestamping option of wget would suffice. Actually the files at the URLs are not intended to change. If a new version of a package is built, it gets a new (unique) name and OptionalPackages is adjusted accordingly. The point is that the build system is supposed to define the the contents of the image, not "third parties" swapping optional package files behind the scenes. So IMO the timestamp change is superfluous. Either we decide not to let the build system update downloads ever -- then the files could simply be marked NoUpdate -- or we are fine with "-a" updating them (which is consistent behavior) and tell people not to build jam with "-a", if they don't want that to happen. Regarding your patch. pushd/popd are superfluous, since actions are run in separate shells anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 02:05:34 2009 From: trac at haiku-os.org (umccullough) Date: Tue, 07 Jul 2009 00:05:34 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.bb180420b69f6a990296dd0e2667f6bf@haiku-os.org> #4068: Enable wget timestamping for file download jamrules --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by umccullough): FWIW, you could also modify your UserBuildConfig such that optional packages are only included when using a build profile {{{ jam -aq }}} followed by your: {{{ jam -q @disk }}} where @disk is defined with the optional packages in a conditional block based on the profilename. Furthermore, you could define a build profile that intentionally excludes them. I don't know, it seems like it's not that big of a deal, and easily worked around if desired. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 03:16:56 2009 From: trac at haiku-os.org (meianoite) Date: Tue, 07 Jul 2009 01:16:56 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.e878ab2c291237c5d110fe0acf403619@haiku-os.org> #4068: Enable wget timestamping for file download jamrules ---------------------------+------------------------------------------------ Reporter: meianoite | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by meianoite): * status: new => closed * resolution: => invalid Comment: Replying to [comment:5 bonefish]: > Mmh, I don't think I've ever built an image with "-a". I usually just remove the "objects" directory and built normally, which also has the advantage of removing all the files that the build system doesn't know about anymore. Hmm... Good point. What about the build/*cache files? Does it matter if I leave them there or erase them? I figure jam -a recreates those. > Actually the files at the URLs are not intended to change. If a new version of a package is built, it gets a new (unique) name and OptionalPackages is adjusted accordingly. Well, yeah, but has the side-effect of leaving old packages behind on the download directory. > The point is that the build system is supposed to define the the contents of the image, not "third parties" swapping optional package files behind the scenes. So IMO the timestamp change is superfluous. Either we decide not to let the build system update downloads ever -- then the files could simply be marked NoUpdate -- or we are fine with "-a" updating them (which is consistent behavior) and tell people not to build jam with "-a", if they don't want that to happen. I think I like the NoUpdate option better. We're then consistent with rebuilding everything the build system *generates*, while leaving what it *imports* alone. > Regarding your patch. pushd/popd are superfluous, since actions are run in separate shells anyway. I wouldn't count that as a patch, actually :) Just pseudocode. I have no idea if invoking a subshell via backticks would work. Anyway, it's still necessary to cd into the downloads directory when invoking wget with -N, but I figure it's more robust to cd into $(HAIKU_DOWNLOAD_DIR) anyway. Replying to [comment:6 umccullough]: > FWIW, you could also modify your UserBuildConfig such that optional packages are only included when using a build profile where @disk is defined with the optional packages in a conditional block based on the profilename. > > Furthermore, you could define a build profile that intentionally excludes them. > > I don't know, it seems like it's not that big of a deal, and easily worked around if desired. Hey, this is just brilliant! Thanks! :D Closing as invalid since I too find this to be the best solution to my problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 03:54:16 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 07 Jul 2009 01:54:16 -0000 Subject: [Haiku-bugs] [Haiku] #4071: AppServer crash: HDA Driver + Restarting Media Services + playing with Media Preflet Message-ID: <041.4e49cac45572d0824c54c45fc6590ab3@haiku-os.org> #4071: AppServer crash: HDA Driver + Restarting Media Services + playing with Media Preflet -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- r31435-x86gcc2 native. Recently switched to a different AMD box, contains one of the recognized and non-audio producing HDA chipsets. After restarting Media Services via the Media preflet, clicking on any of the nodes in the left most panel(correct term?) will result in a large white box displaying on the main view. Repeatedly switching nodes will cause that white region to grow many times the size of the screen. Eventually, this will lead to a gdb in app_server. I was able to reproduce this twice. {{{ device Multimedia controller (Audio device) [4|3|0] vendor 10de: nVidia Corporation device 03f0: MCP61 High Definition Audio }}} screenshot of gdb attached. I'm uncertain which component this should be -- preferences/media, drivers/audio/hda, or servers/app_server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 03:56:19 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 07 Jul 2009 01:56:19 -0000 Subject: [Haiku-bugs] [Haiku] #4068: Enable wget timestamping for file download jamrules In-Reply-To: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> References: <044.87861abb7ae015800f7fc7bf34c6c2c7@haiku-os.org> Message-ID: <053.1569173b85e36d6731ea1602a2b0bc8f@haiku-os.org> #4068: Enable wget timestamping for file download jamrules ---------------------------+------------------------------------------------ Reporter: meianoite | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:7 meianoite]: > Replying to [comment:5 bonefish]: > > Mmh, I don't think I've ever built an image with "-a". I usually just remove the "objects" directory and built normally, which also has the advantage of removing all the files that the build system doesn't know about anymore. > > Hmm... Good point. What about the build/*cache files? Does it matter if I leave them there or erase them? I figure jam -a recreates those. They contain information obtained from header scanning and from reading the jamfiles. Unless you've messed with timestamps (or your system time), there's no need to remove them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 07:36:30 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 07 Jul 2009 05:36:30 -0000 Subject: [Haiku-bugs] [Haiku] #3142: cvs program malfunction In-Reply-To: <042.0aa59fe80615cb0dbacd9ada6ce1819f@haiku-os.org> References: <042.0aa59fe80615cb0dbacd9ada6ce1819f@haiku-os.org> Message-ID: <051.ce829e9a3798ab948aed843f71eefd79@haiku-os.org> #3142: cvs program malfunction -----------------------+---------------------------------------------------- Reporter: bhaible | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): I no longer see this error with a new build of cvs with the wchar fix in place. Leave open until the wchar fix is moved into trunk. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 08:56:42 2009 From: trac at haiku-os.org (jahaiku) Date: Tue, 07 Jul 2009 06:56:42 -0000 Subject: [Haiku-bugs] [Haiku] #4072: HDA audio sounds worse Message-ID: <042.4089cdf4258cd6641a6941a4b554f705@haiku-os.org> #4072: HDA audio sounds worse -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- This is a gcc4 build of r31391 on EeePC 4G.[[BR]] I have attached output of listdev and syslog which is full of HDA- Messages.[[BR]] [[BR]] If I play music files and specially if a tone if held some time this tone sounds rattling, distorted, a bit like a robot and a little unclean. [[BR]] I have tested this with differend sound formats (WAV/MP3) and files, but not all sound like this. Perhaps this has s.th. to do with the dynamic or the frequency spectrum of the Soundsamples and sometimes the HDA is internally overamplifyed through wrong initalisation?!?[[BR]][[BR]] I have tested the same files with the newest Knoppix on this EeePC and there the sound is OK. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 09:01:03 2009 From: trac at haiku-os.org (jahaiku) Date: Tue, 07 Jul 2009 07:01:03 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.b3d3999dde813614e6bb3504228c0d77@haiku-os.org> #3690: Copy file to USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Changes (by jahaiku): * cc: Jens.Arm@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 11:47:11 2009 From: trac at haiku-os.org (axeld) Date: Tue, 07 Jul 2009 09:47:11 -0000 Subject: [Haiku-bugs] [Haiku] #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker In-Reply-To: <043.0ad44e7691ab39ada41f72d23b60b5dc@haiku-os.org> References: <043.0ad44e7691ab39ada41f72d23b60b5dc@haiku-os.org> Message-ID: <052.257149c0e67dab0043f150b3b7909f25@haiku-os.org> #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker ---------------------------------------------+------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by axeld): * status: new => assigned Comment: That probably happened when Ryan moved quitting the screen blanker to the application. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 11:52:50 2009 From: trac at haiku-os.org (axeld) Date: Tue, 07 Jul 2009 09:52:50 -0000 Subject: [Haiku-bugs] [Haiku] #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker In-Reply-To: <043.0ad44e7691ab39ada41f72d23b60b5dc@haiku-os.org> References: <043.0ad44e7691ab39ada41f72d23b60b5dc@haiku-os.org> Message-ID: <052.01d2bff8ed317af283290b0a58aa5813@haiku-os.org> #4069: [screen_blanker] Keys/Key Combos that Don't Generate a KeyDown() Don't Quit the Blanker ----------------------------------------------+----------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Indeed, r29488 is to blame. Anyway, fixed in r31441. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 13:56:25 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 07 Jul 2009 11:56:25 -0000 Subject: [Haiku-bugs] [Haiku] #4073: BFilePanel : Randomly, Volume Icons are missing. Message-ID: <041.5cb4eccfb9a31061794e271f17cf6679@haiku-os.org> #4073: BFilePanel : Randomly, Volume Icons are missing. ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- This has been seen for quite some time. Sometimes when a BFilePanel is opened, the volume icons will not display. In order for them to display a subfolder -- Home or Trash will need to be entered and then exited. Applies to both Volume Icons and Disks Icon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 16:20:04 2009 From: trac at haiku-os.org (idefix) Date: Tue, 07 Jul 2009 14:20:04 -0000 Subject: [Haiku-bugs] [Haiku] #3540: Twitcher leaks pressed Tab-key to previously activated window In-Reply-To: <041.382c202e7251b3e22b4f4fb5694d00f1@haiku-os.org> References: <041.382c202e7251b3e22b4f4fb5694d00f1@haiku-os.org> Message-ID: <050.ee4bf34087dda0fdfaee3e172db8a0e4@haiku-os.org> #3540: Twitcher leaks pressed Tab-key to previously activated window ----------------------------------+----------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by idefix): Changeset [31407] fixed this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 16:39:16 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 07 Jul 2009 14:39:16 -0000 Subject: [Haiku-bugs] [Haiku] #3540: Twitcher leaks pressed Tab-key to previously activated window In-Reply-To: <041.382c202e7251b3e22b4f4fb5694d00f1@haiku-os.org> References: <041.382c202e7251b3e22b4f4fb5694d00f1@haiku-os.org> Message-ID: <050.68be900bbbecb8525a93f248722735dc@haiku-os.org> #3540: Twitcher leaks pressed Tab-key to previously activated window -----------------------------------+---------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: thanks for the update -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 20:49:25 2009 From: trac at haiku-os.org (Luposian) Date: Tue, 07 Jul 2009 18:49:25 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 Message-ID: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Using this monitor and either an AGP GeForce 2 or GeForce 3 video card (VGA output), Haiku offers no option for the 1440x900 native resolution of this monitor. However, I know Haiku is capable of this native resolution, because using another system with a PCIe GeForce 6200 card and the DVI output (DVI input on the monitor), Haiku allows me to select 1440x900 on this same monitor with no problem. I have not yet tried the VGA output on that card, however. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 20:50:15 2009 From: trac at haiku-os.org (meianoite) Date: Tue, 07 Jul 2009 18:50:15 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume Message-ID: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume -------------------------------+-------------------------------------------- Reporter: meianoite | Owner: 3dEyes Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- System is gcc2 r31444 with rebuilt toolchain at the same revision. Probably related to the recent wchar_t changes, since NTFS uses Unicode for names. Reproducible every time. I'm considering this critical despite the NTFS add-on being optional because I can't see any Windows multi-booting user not enabling it. Steps to reproduce: enable gpl addons (and maybe 3rd party, I don't know where the ntfs-3g add-on is located). Boot Haiku, attempt to mount a NTFS volume, as read-only even. First symptom appears before the mounting per se: the volume names aren't shown anymore, with Tracker showing a placeholder "NTFS Volume" label instead. Second symptom is that, well, it KDLs, with the following message: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0x0, ip 0x800ea66b Welcome to Kernel Debugging Land... Thread 160 "TrashWatcher" running on CPU 3 }}} Screenshots of stack trace are attached, sorry for the CRT noise. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 21:31:37 2009 From: trac at haiku-os.org (idefix) Date: Tue, 07 Jul 2009 19:31:37 -0000 Subject: [Haiku-bugs] [Haiku] #4076: [patch] Change tab order in Expander-window Message-ID: <041.13afc2971ded0fdb81003e8cc83a2bf7@haiku-os.org> #4076: [patch] Change tab order in Expander-window -----------------------------------+---------------------------------------- Reporter: idefix | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Expander | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- The tab order in Expander is a little bit strange:[[Image(taborder- old.png)]] [attachment:expandertaborder.patch Attached patch] changes the order to be the same as BeOS' Expander:[[Image(taborder-new.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 22:13:17 2009 From: trac at haiku-os.org (monni) Date: Tue, 07 Jul 2009 20:13:17 -0000 Subject: [Haiku-bugs] [Haiku] #4077: [patch] fix wrong variable in h2generic debug output Message-ID: <040.5fe2dc30f2e5ea147cddf704ca576b3f@haiku-os.org> #4077: [patch] fix wrong variable in h2generic debug output -------------------------------+-------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- in init code h2generic shows NULL pointer even on success -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 23:09:15 2009 From: trac at haiku-os.org (Pete) Date: Tue, 07 Jul 2009 21:09:15 -0000 Subject: [Haiku-bugs] [Haiku] #4053: USB MIDI not recognized In-Reply-To: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> References: <039.f45ca5c1dca5eb2ff5063d3c574fbcb7@haiku-os.org> Message-ID: <048.8cc281a581276499f5a66d7990b6af2a@haiku-os.org> #4053: USB MIDI not recognized ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by Pete): Update: I switched to the Midisport 2x2 that is normally attached to my Ubuntu machine, and find that this does ''not'' stall on the set- alt_interface call, and the '/dev/midi/usb' entry gets created. (Both this and the Uno work equally well under Ubuntu.) PatchBay, however, still did not see any ports when I plugged the Midisport in. Then I finally read the midi_server docs, and saw that the server only looks for /dev/midi devices at boot-up!!(!) I guess someone wasn't thinking of USB and hotplugging when that decision was made... This needs fixing at some point, otherwise users will be very confused (like me!). When the device was connected before booting, PatchBay finally saw the ports, but unfortunately there is still no actual MIDI input available when I attach my keyboard. Looking at syslog, I see a continual loop: {{{ usb_midi_callback() report 00 00 00 00 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 23:13:39 2009 From: trac at haiku-os.org (idefix) Date: Tue, 07 Jul 2009 21:13:39 -0000 Subject: [Haiku-bugs] [Haiku] #1468: Zoom button in window decorator tab renders wrong in some cases In-Reply-To: <045.b2e6d87a9ed548ff55c1aaf46454c26c@haiku-os.org> References: <045.b2e6d87a9ed548ff55c1aaf46454c26c@haiku-os.org> Message-ID: <054.4fd5697b93781d54329356a618acbce7@haiku-os.org> #1468: Zoom button in window decorator tab renders wrong in some cases --------------------------------+------------------------------------------- Reporter: leavengood | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by idefix): I cannot reproduce this anymore since the new look [changeset:28951 was implemented]. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 23:18:45 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 07 Jul 2009 21:18:45 -0000 Subject: [Haiku-bugs] [Haiku] #1468: Zoom button in window decorator tab renders wrong in some cases In-Reply-To: <045.b2e6d87a9ed548ff55c1aaf46454c26c@haiku-os.org> References: <045.b2e6d87a9ed548ff55c1aaf46454c26c@haiku-os.org> Message-ID: <054.55e22954a0db2140a478a9aabe56a71e@haiku-os.org> #1468: Zoom button in window decorator tab renders wrong in some cases ---------------------------------+------------------------------------------ Reporter: leavengood | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by leavengood): * status: new => closed * resolution: => fixed Comment: OK then I'll mark it as fixed. Thanks for checking idefix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 23:23:28 2009 From: trac at haiku-os.org (idefix) Date: Tue, 07 Jul 2009 21:23:28 -0000 Subject: [Haiku-bugs] [Haiku] #4078: Tabs are rendered wrong when glyph hinting is off Message-ID: <041.00b707a0e19e53a01de26073c2faf306@haiku-os.org> #4078: Tabs are rendered wrong when glyph hinting is off --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- When glyph hinting is on, tabs are rendered correctly:[[Image(hintingon- firsttab.png)]][[Image(hintingon-secondtab.png)]] When glyph hinting is off, tabs are not correctly rendered:[[Image (hintingoff-firsttab.png)]][[Image(hintingoff-secondtab.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 7 23:46:02 2009 From: trac at haiku-os.org (oruizdorantes) Date: Tue, 07 Jul 2009 21:46:02 -0000 Subject: [Haiku-bugs] [Haiku] #4077: [patch] fix wrong variable in h2generic debug output In-Reply-To: <040.5fe2dc30f2e5ea147cddf704ca576b3f@haiku-os.org> References: <040.5fe2dc30f2e5ea147cddf704ca576b3f@haiku-os.org> Message-ID: <049.1674cadf038c1179063c76756d5c923e@haiku-os.org> #4077: [patch] fix wrong variable in h2generic debug output --------------------------------+------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by oruizdorantes): * status: new => closed * resolution: => fixed Comment: Thanks Monni, Applied in r31449 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 00:46:37 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 07 Jul 2009 22:46:37 -0000 Subject: [Haiku-bugs] [Haiku] #4073: BFilePanel : Randomly, Volume Icons are missing. In-Reply-To: <041.5cb4eccfb9a31061794e271f17cf6679@haiku-os.org> References: <041.5cb4eccfb9a31061794e271f17cf6679@haiku-os.org> Message-ID: <050.2bde2929b6306a11c8a2f8a6f27303cf@haiku-os.org> #4073: BFilePanel : Randomly, Volume Icons are missing. ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by anevilyak): * owner: axeld => anevilyak * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 01:34:09 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 07 Jul 2009 23:34:09 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.0db3dbd8dcfd3eeca32677b0d19e9596@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): This one can be closed, it was fixed with r30915. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 01:41:18 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 07 Jul 2009 23:41:18 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.9b52023d041ce8100e649d052f7c1781@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions ------------------------+--------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 07:21:05 2009 From: trac at haiku-os.org (Luposian) Date: Wed, 08 Jul 2009 05:21:05 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.10f1d42029fb7530e5c808940335ca33@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Luposian): I just added my syslog, to help find what is preventing native resolution discovery in Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 10:15:34 2009 From: trac at haiku-os.org (jahaiku) Date: Wed, 08 Jul 2009 08:15:34 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume In-Reply-To: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> References: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> Message-ID: <053.522fae44e3c2f0cc1c81b475f33206d4@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume -------------------------------+-------------------------------------------- Reporter: meianoite | Owner: 3dEyes Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Changes (by jahaiku): * cc: Jens.Arm@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 10:42:17 2009 From: trac at haiku-os.org (axeld) Date: Wed, 08 Jul 2009 08:42:17 -0000 Subject: [Haiku-bugs] [Haiku] #4078: Tabs are rendered wrong when glyph hinting is off In-Reply-To: <041.00b707a0e19e53a01de26073c2faf306@haiku-os.org> References: <041.00b707a0e19e53a01de26073c2faf306@haiku-os.org> Message-ID: <050.2ca772034d6af019c896bb4f274a0587@haiku-os.org> #4078: Tabs are rendered wrong when glyph hinting is off --------------------------------+------------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 17:24:47 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 15:24:47 -0000 Subject: [Haiku-bugs] [Haiku] #4079: Freezing 1or2 shapes with 1or2 paths fails Message-ID: <044.18ebd1e9dc28122f6887110d1ec67fb7@haiku-os.org> #4079: Freezing 1or2 shapes with 1or2 paths fails ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31444. Here are two scenarios where freezing a shape fails. First scenario: 2 Shapes sharing 1 path: 1. Create a shape with a path and a style. 2. Select the path and add a couple of points. 3. Create a second shape and use the same path. 2. Move/resize/rotate the 2nd shape a bit. 3. Select "Shape | Freeze Transformation". Now, the path should snap to the selected shape's new position/size/orientation. It doesn't. Instead the shape snaps to the original path's position.[[BR]] If there's an issue, because the path is shared with another shape, the command to "Freeze Transformation" should be disabled. Second scenario: 1 Shape from 2 paths: 1. Create a shape with a path and a style. 2. Select the path and add a couple of points. 2. Create another path. 2. Select this second path and add a couple of points. 2. Move/resize/rotate the shape a bit. 3. Select "Shape | Freeze Transformation". Now, the paths should snap to the shape's new position/size/orientation. Instead only the second path snaps to the new location, the shape snaps to the original first path's position.[[BR]] So for example, if you created the second path inside the first path, creating a hole in the shape, the hole stays put, while the rest of the shape snaps back to the original first path's location. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 17:49:35 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 15:49:35 -0000 Subject: [Haiku-bugs] [Haiku] #4079: Freezing 1or2 shapes with 1or2 paths fails In-Reply-To: <044.18ebd1e9dc28122f6887110d1ec67fb7@haiku-os.org> References: <044.18ebd1e9dc28122f6887110d1ec67fb7@haiku-os.org> Message-ID: <053.541b0e57722b3f83a80e69e9e43477fc@haiku-os.org> #4079: Freezing 1or2 shapes with 1or2 paths fails ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Description changed by humdinger: Old description: > This is r31444. > > Here are two scenarios where freezing a shape fails. > > First scenario: 2 Shapes sharing 1 path: > > 1. Create a shape with a path and a style. > 2. Select the path and add a couple of points. > 3. Create a second shape and use the same path. > 2. Move/resize/rotate the 2nd shape a bit. > 3. Select "Shape | Freeze Transformation". > > Now, the path should snap to the selected shape's new > position/size/orientation. It doesn't. Instead the shape snaps to the > original path's position.[[BR]] > If there's an issue, because the path is shared with another shape, the > command to "Freeze Transformation" should be disabled. > > Second scenario: 1 Shape from 2 paths: > > 1. Create a shape with a path and a style. > 2. Select the path and add a couple of points. > 2. Create another path. > 2. Select this second path and add a couple of points. > 2. Move/resize/rotate the shape a bit. > 3. Select "Shape | Freeze Transformation". > > Now, the paths should snap to the shape's new position/size/orientation. > Instead only the second path snaps to the new location, the shape snaps > to the original first path's position.[[BR]] > So for example, if you created the second path inside the first path, > creating a hole in the shape, the hole stays put, while the rest of the > shape snaps back to the original first path's location. New description: This is r31444. [Messed up numbering and formatting before.][[BR]] Here are two scenarios where freezing a shape fails. First scenario: 2 Shapes sharing 1 path: 1. Create a shape with a path and a style.[[BR]] 2. Select the path and add a couple of points.[[BR]] 3. Create a second shape and use the same path.[[BR]] 4. Move/resize/rotate the 2nd shape a bit.[[BR]] 5. Select "Shape | Freeze Transformation".[[BR]] Now, the path should snap to the selected shape's new position/size/orientation. It doesn't. Instead the shape snaps to the original path's position.[[BR]] If there's an issue, because the path is shared with another shape, the command to "Freeze Transformation" should be disabled. Second scenario: 1 Shape from 2 paths: 1. Create a shape with a path and a style.[[BR]] 2. Select the path and add a couple of points.[[BR]] 3. Create another path.[[BR]] 4. Select this second path and add a couple of points.[[BR]] 5. Move/resize/rotate the shape a bit.[[BR]] 6. Select "Shape | Freeze Transformation".[[BR]] Now, the paths should snap to the shape's new position/size/orientation. Instead only the second path snaps to the new location, the shape snaps to the original first path's position.[[BR]] So for example, if you created the second path inside the first path, creating a hole in the shape, the hole stays put, while the rest of the shape snaps back to the original first path's location. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 17:55:58 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 15:55:58 -0000 Subject: [Haiku-bugs] [Haiku] #4080: Disable/Implement path property "Rounding" Message-ID: <044.382717922a2cc31f3719b5ed498a8b1c@haiku-os.org> #4080: Disable/Implement path property "Rounding" ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31444. When Stippi recently answered a few questions on I-O-M's usage, it turned out that some features aren't yet (completely) implemented. These features should probably be disabled until they are finished. From http://www.freelists.org/post/haiku/IconOMatic-questions,6 on "Rounding": "That one is very much an unfinished feature. Once it's ready, it's supposed to work like font hinting. It currently rounds the coordinates of vector paths to integer pixels, but that is a very dumb way to do it, plus it does that after the transformers have been applied, but it needs to do that before while additionally taking transformer related stuff into account.[[BR]] Like special preprocessing of the vector paths so that the coordinates end up on integer pixel locations. It's not rocket sience, but not trivial either." -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 17:59:17 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 15:59:17 -0000 Subject: [Haiku-bugs] [Haiku] #4081: Wrong shortcut label in context menu (easy) Message-ID: <044.d4fa99be0f5be6bf6b28db8de1ed02e1@haiku-os.org> #4081: Wrong shortcut label in context menu (easy) ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31444. The shortcut in the context menu to delete a path-point is wrong. It's ALT+A which is also used for "Select All...". It should be the "DEL" key. Also the "Transform" item in the same context menu should get a "T" as shortcut label. BTW, if you directly right-click in a point, and it isn't selected already, only the command "Select All" is available. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 18:02:30 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 16:02:30 -0000 Subject: [Haiku-bugs] [Haiku] #4082: Disable/Implement transformer "Transformation" and "Perspective" Message-ID: <044.c1678087317522c63479ce60487d10e7@haiku-os.org> #4082: Disable/Implement transformer "Transformation" and "Perspective" ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31444. When Stippi recently answered a few questions on I-O-M's usage, it turned out that some features aren't yet (completely) implemented. These features should probably be disabled until they are finished. See http://www.freelists.org/post/haiku/IconOMatic-questions,1 .[[BR]] "Transformation" isn't really useful as is and "Perspective" isn't implemented at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 18:08:04 2009 From: trac at haiku-os.org (humdinger) Date: Wed, 08 Jul 2009 16:08:04 -0000 Subject: [Haiku-bugs] [Haiku] #4083: Rename some menu strings (easy) Message-ID: <044.fd00425ef89636ff9d9c3bc07d1bec10@haiku-os.org> #4083: Rename some menu strings (easy) ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31444. I'm not a native speaker, but IMO the "Property" view/menu should actually be named "Properties". Just like with "Options" or "Settings". I considered providing a patch, but "Property" is used elsewhere besides that menu and I didn't want to mess things up... :) Because a circle path is added right away (no panel to enter the number of segments, for example) the ellipses at the end of "Add Circle..." can be removed (until that feature is implemented). IMO opinion "File | Append..." fits more to text files where you add more text to the end. I suggest to rename this function to "File | Insert..." or simply "File | Add...". Maybe it's just a matter of taste. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 19:42:34 2009 From: trac at haiku-os.org (Hubert) Date: Wed, 08 Jul 2009 17:42:34 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.636ea244c68f82d0a0f3f79cedfa4a16@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by Hubert): I have the same: r31462 [[BR]][http://dev.haiku-os.org/attachment/ticket/3922/listdev listdev] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 19:46:37 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 08 Jul 2009 17:46:37 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.45cc8d2e4fc8485056320f2e84ce1825@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Replying to [comment:1 Hubert]: > I have the same: r31462 > [[BR]][http://dev.haiku-os.org/attachment/ticket/3922/listdev listdev] Hubert can you try reverting to r31459? Michael Weirauch and myself are not able to boot r31460. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 20:37:36 2009 From: trac at haiku-os.org (Hubert) Date: Wed, 08 Jul 2009 18:37:36 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.3eb8110ea7ce1a90d7046025325e9973@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by Hubert): ok. one moment please -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 21:28:36 2009 From: trac at haiku-os.org (augiedoggie) Date: Wed, 08 Jul 2009 19:28:36 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.aec8113b48cefd50a7fc2c86996f3d6a@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by augiedoggie): r31460 keeps me from booting as well. I applied the diff in reverse and all is well now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 21:33:14 2009 From: trac at haiku-os.org (Hubert) Date: Wed, 08 Jul 2009 19:33:14 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.1c272da6dc85c4452b7cb4a5cce91f4a@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by Hubert): r31459 booting correctly -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 21:37:37 2009 From: trac at haiku-os.org (Hubert) Date: Wed, 08 Jul 2009 19:37:37 -0000 Subject: [Haiku-bugs] [Haiku] #4084: Lack 1440x900 resolutoion Message-ID: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> #4084: Lack 1440x900 resolutoion -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- In r31459 I don't see 1440x900 resolution, native for my LCD. Why? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 22:28:01 2009 From: trac at haiku-os.org (sil2100) Date: Wed, 08 Jul 2009 20:28:01 -0000 Subject: [Haiku-bugs] [Haiku] #4059: PackageInstaller needs a "Yes to all" button in dialog box In-Reply-To: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> References: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> Message-ID: <051.2fc8d38ffa962c4bf23426221d352415@haiku-os.org> #4059: PackageInstaller needs a "Yes to all" button in dialog box -------------------------------------------+-------------------------------- Reporter: scottmc | Owner: sil2100 Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------------+-------------------------------- Changes (by sil2100): * cc: sil2100@? (added) * status: new => assigned Comment: Indeed, I will take care of it ASAP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 8 23:15:42 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 08 Jul 2009 21:15:42 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.467444848eecdbcdbea1e726bcbe08ac@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by marcusoverhagen): should be fixed in r31463, please test -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 00:58:03 2009 From: trac at haiku-os.org (Luposian) Date: Wed, 08 Jul 2009 22:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.cbc3c6c3e57e670cba71d069e958751f@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Luposian): Apparently, a missing "nvidia.settings" file is/was the culprit. Why was it not part of the GCC4 build? Also, I had to set "force_ws" to true, in order for my monitor's native resolution to be correctly identified and made available to select. The question I have, though, is... when the VESA setting file keeps popping up (when/after using with the Screen preflet?), does that mean I'm still operating in VESA mode or am I in true nVidia accelerated mode? I can't tell. How *can* I tell for certain? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 00:59:22 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 08 Jul 2009 22:59:22 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.8336476a5b81034b8ae2a33ac848d917@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by umccullough): It's not a required file. Likely there's a non-default setting in the file you grabbed that changed the behavior. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 01:00:44 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 08 Jul 2009 23:00:44 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.8a35c2d6c21d88b63af3bec3d8503e04@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by umccullough): You can tell what accelerant the app_server is using the following command from a terminal: {{{ listimage | grep accel }}} Which will list out all binaries loaded in memory that have the string: "accel" in their name. All current accelerants end in .accelerant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 01:09:01 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 08 Jul 2009 23:09:01 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.8ee4a3fea20e1e5859e0ac02ad53c504@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by anevilyak): Replying to [comment:2 Luposian]: > The question I have, though, is... when the VESA setting file keeps popping up (when/after using with the Screen preflet?), does that mean I'm still operating in VESA mode or am I in true nVidia accelerated mode? I can't tell. How *can* I tell for certain? If you have the drop down to adjust the refresh rate in the Screen prefs, you're using the nvidia driver (or some other accelerated driver). If not, you're using VESA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 01:23:19 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 08 Jul 2009 23:23:19 -0000 Subject: [Haiku-bugs] [Haiku] #4073: BFilePanel : Randomly, Volume Icons are missing. In-Reply-To: <041.5cb4eccfb9a31061794e271f17cf6679@haiku-os.org> References: <041.5cb4eccfb9a31061794e271f17cf6679@haiku-os.org> Message-ID: <050.1cba59a97a6ab797621139336788f0ff@haiku-os.org> #4073: BFilePanel : Randomly, Volume Icons are missing. -----------------------------------+---------------------------------------- Reporter: mmadia | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31472. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 05:04:33 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 09 Jul 2009 03:04:33 -0000 Subject: [Haiku-bugs] [Haiku] #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip Message-ID: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The new package of [http://haiku-files.org/files/optional- packages/libtool-2.2.6a-x86-gcc2-2009-07-05.zip libtool-2.2.6a-x86-gcc2-2009-07-05.zip] has line 251: {{{ : ${SED="/boot/common/bin/sed"} }}} The older package [http://haiku-files.org/files/optional- packages/libtool-2.2.6a-gcc2-2008-11-09.zip libtool-2.2.6a- gcc2-2008-11-09.zip] has line 255: {{{ : ${SED="/bin/sed"} }}} With the new libtoolize, certain programs, such as pkg-config-0.23 fail to be updated with `libtoolize --force --copy` because it's looking for the binary in the wrong place. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 06:01:26 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 09 Jul 2009 04:01:26 -0000 Subject: [Haiku-bugs] [Haiku] #3965: DriveSetup: reversed behavior for (un)mounted volumes (was: reversed behavior for (un)mounted volumes) In-Reply-To: <041.1f61470f2a8f1e568f6e8116f3c1b5b4@haiku-os.org> References: <041.1f61470f2a8f1e568f6e8116f3c1b5b4@haiku-os.org> Message-ID: <050.38c0980b38838de7a80a0cbf4633919b@haiku-os.org> #3965: DriveSetup: reversed behavior for (un)mounted volumes -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 06:01:06 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 09 Jul 2009 04:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #3965: reversed behavior for (un)mounted volumes In-Reply-To: <041.1f61470f2a8f1e568f6e8116f3c1b5b4@haiku-os.org> References: <041.1f61470f2a8f1e568f6e8116f3c1b5b4@haiku-os.org> Message-ID: <050.ca3e4663cda2c4f3eb654e67a7e20e48@haiku-os.org> #3965: reversed behavior for (un)mounted volumes -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by mmadia): Still seeing this very frequently. It seems that the only way for me to correct the behavior is to use DriveSetup to Partition->MountAll, Rescan, Use Tracker to unmount all Volumes (except boot), Use DriveSetup to Rescan, and then finally Initialize. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 06:12:21 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 09 Jul 2009 04:12:21 -0000 Subject: [Haiku-bugs] [Haiku] #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip In-Reply-To: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> References: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> Message-ID: <050.76f1f0b8205a68a4391b3050036f4e77@haiku-os.org> #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Description changed by mmadia: Old description: > The new package of [http://haiku-files.org/files/optional- > packages/libtool-2.2.6a-x86-gcc2-2009-07-05.zip > libtool-2.2.6a-x86-gcc2-2009-07-05.zip] has line 251: > {{{ > : ${SED="/boot/common/bin/sed"} > }}} > > The older package [http://haiku-files.org/files/optional- > packages/libtool-2.2.6a-gcc2-2008-11-09.zip libtool-2.2.6a- > gcc2-2008-11-09.zip] has line 255: > {{{ > : ${SED="/bin/sed"} > }}} > > With the new libtoolize, certain programs, such as pkg-config-0.23 fail > to be updated with `libtoolize --force --copy` because it's looking for > the binary in the wrong place. New description: The new package of [http://haiku-files.org/files/optional- packages/libtool-2.2.6a-x86-gcc2-2009-07-05.zip libtool-2.2.6a-x86-gcc2-2009-07-05.zip] has line 251: {{{ : ${SED="/boot/common/bin/sed"} }}} The older package [http://haiku-files.org/files/optional- packages/libtool-2.2.6a-gcc2-2008-11-09.zip libtool-2.2.6a- gcc2-2008-11-09.zip] has line 255: {{{ : ${SED="/bin/sed"} }}} With the new libtoolize, certain programs, such as pkg-config-0.23 fail to be updated with `libtoolize --force --copy` because it's looking for the binary in the wrong place. edit: to sum up, the issue is that the new libtoolize is configured to use /boot/common/bin/sed and in a default `jam -q @alpha-raw` image, there is no /boot/common/bin/sed -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 06:23:01 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 09 Jul 2009 04:23:01 -0000 Subject: [Haiku-bugs] [Haiku] #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip In-Reply-To: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> References: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> Message-ID: <050.001c6fa75accf4d9edf88006e452a36c@haiku-os.org> #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): this probaly happened when i build libtool with a newer sed in /boot/common rather than the one that comes with haiku. So there's two paths to fixing this one, either a new libtool package is needed pointing to the current sed, but then the current sed needs to be updated for the wchar fix. Or sed can be removed from haiku's tree and moved to an optional package... So this one might be tied to #3230. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 07:49:16 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 09 Jul 2009 05:49:16 -0000 Subject: [Haiku-bugs] [Haiku] #4086: [patch] OptionalPackages : Expat, Python, P7Zip Message-ID: <041.9f66d118cd649b8769e9f3d0436d2442@haiku-os.org> #4086: [patch] OptionalPackages : Expat, Python, P7Zip --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- The current version of Subversion requires expat, which is not included in the archive. This patch adds "Expat" as an optional package and as a dependency of "Subversion". In addition, this patch updates a few other packages for the wchar related changes: Python and P7zip (gcc2 and gcc4) note: patch untested, though filenames of archives were proof-read. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 10:40:28 2009 From: trac at haiku-os.org (aldeck) Date: Thu, 09 Jul 2009 08:40:28 -0000 Subject: [Haiku-bugs] [Haiku] #4058: Boot fails, new ATA stack In-Reply-To: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> References: <041.80baf0320e11494d3dd20f9dd3ca327a@haiku-os.org> Message-ID: <050.b623200a3ec777bc6982ae2f5178a222@haiku-os.org> #4058: Boot fails, new ATA stack --------------------------+------------------------------------------------- Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by aldeck): Still there, but that's expected since i believe it's a different problem (ie: those recent comments are not related to this ticket). The ticket is about switching to the new ATA stack (the IDE stack was working on that same machine). The problem was there before r31460. cf: http://www.freelists.org/post/haiku-development/Filesystem-corruption- and-Alpha1,47 in reply to: http://www.freelists.org/post/haiku-development/Filesystem- corruption-and-Alpha1,38 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 12:47:15 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Thu, 09 Jul 2009 10:47:15 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox Message-ID: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- [http://www.zoolib.org ZooLib] is a C++ cross-platform application framework. It is close to supporting Haiku, but I find that building it often crashes the system, when I run Haiku under VirtualBox on my Fedora 10 Xeon box. Possibly this is actually a bug in VirtualBox; if I can I'll try running Haiku under KVM and VMware. I have seen this problem with several different versions of both Haiku and of VirtualBox. Presently I'm using the GCC 2.95.3 build of Haiku r31471 and VirtualBox 3.0.0. ZooLib's SourceForge project has both Subversion and CVS repositories. The Subversion code isn't building yet; I've been preparing a release from the older CVS code. To fetch the CVS sources: $ cvs -z3 -d:pserver:anonymous at zoolib.cvs.sourceforge.net:/cvsroot/zoolib checkout -P zoolib Delete or rename zoolib/src/platform/beos/TLS.h - it conflicts with the file of the same name that comes with Haiku. cd into zoolib/samples/buttonmessage/buttonmessage_build_be and type "make". After compiling a few files, either Haiku will freeze or VirtualBox will report that the guest has crashed. If you reboot Haiku and try the make again, gcc will report that some of the object files are in an unrecognized format. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 13:21:59 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Thu, 09 Jul 2009 11:21:59 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.00d9b0b866e8e238e1a4cdadc8b4e649@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): The crash also occurs with the GCC4 build of r31471. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 19:39:09 2009 From: trac at haiku-os.org (atmartens) Date: Thu, 09 Jul 2009 17:39:09 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow Message-ID: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Hello, I am new to Haiku, and just built and installed it to a partition. When I boot into Haiku, I make it to the desktop quickly. However, the system then becomes extremely slow. -the mouse responds, but with a lot of lag -I can't type text into the terminal window -the desktop items do not respond (and sometimes don't even appear) However, I can bring up the F12 debugger and run commands there. I've tried to see if I could extract anything useful from it but am not sure I have. I did get a vm_page_fault twice: {{{ panic: vm_page_fault: unhandled page fault in kernel space at 0x48, ip 0x844c798d }}} I also got the same error with ip 0x844f498d Two other times I got a different error: {{{ could not read block 1573588: bytesRead: -1, error: Device timeout }}} I also got the same error on block 1573420 Since this is my first time using the system I can't tell if those errors are related to my problem or not. I can also give some hardware specs if needed; I built my computer just over a year ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 19:58:37 2009 From: trac at haiku-os.org (stippi) Date: Thu, 09 Jul 2009 17:58:37 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.b87ea0e1164f905ade806a392749102a@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): It sounds very much like you are suffering from an interrupt storm. In the kernel debugger, you can use the "ints" command to get a listing. There should not be an interrupt line with thousands of unhandled interrupts. From there, you can also see which driver registered a handler. Best is probably to post the ints output here and maybe someone knows what could be done about it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 20:12:16 2009 From: trac at haiku-os.org (zooey) Date: Thu, 09 Jul 2009 18:12:16 -0000 Subject: [Haiku-bugs] [Haiku] #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip In-Reply-To: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> References: <041.e6232e54c226075905c523329ceefdaf@haiku-os.org> Message-ID: <050.45ad503f860d9a272696ff3026c28c91@haiku-os.org> #4085: Error with libtool-2.2.6a-x86-gcc2-2009-07-05.zip ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => fixed Comment: In r31486, libtools has been reverted to the older version, as I can't see the point of adding an sed optional package when haiku already provides one (in /bin). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 20:17:44 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Thu, 09 Jul 2009 18:17:44 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.07aa440aef21084baafc948823ac5df9@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): That Fedora 10 box has a 2.5 GHz Core 2 Quad Xeon e5420 on a Supermicro X7DWA-N motherboard. The board is socketed for two CPUs but I just have one installed presently. I'm using the x86_64 build of VirtualBox. I will try it on my MacBook Pro this evening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 20:27:16 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 09 Jul 2009 18:27:16 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.7dbdf3bb9c7b68e90316eb4ab6e96196@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by scottmc): Here's what I get on real hardware (AMD Geode 500MHz, been running for 47 days 18 hours and still not crashed) with gcc2 and Haiku r30665: {{{ ~/develop/zoolib/samples/buttonmessage/buttonmessage_build_be> make g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../samples/buttonmessage/buttonmessage_src/BMApp.cpp -o objects- debug/BMApp.o g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../samples/buttonmessage/buttonmessage_src/BMButtonWindow.cpp -o objects-debug/BMButtonWindow.o g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../samples/buttonmessage/buttonmessage_src/BMDisplayWindow.cpp -o objects-debug/BMDisplayWindow.o g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../samples/buttonmessage/buttonmessage_src/BMMain.cpp -o objects- debug/BMMain.o g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../samples/buttonmessage/buttonmessage_src/MessageButtonPane.cpp -o objects-debug/MessageButtonPane.o g++ -I../../../samples/buttonmessage/buttonmessage_src -I./ -I../../../src/_deprecated -I../../../src/asset -I../../../src/compat -I../../../src/config -I../../../src/config_choices -I../../../src/file -I../../../src/foundation -I../../../src/graphics -I../../../src/net -I../../../src/platform/beos -I../../../src/platform/macos -I../../../src/platform/posix -I../../../src/platform/win32 -I../../../src/printing -I../../../src/stream -I../../../src/text -I../../../src/thread -I../../../src/uicore -I../../../src/uiextra -pipe -D_REENTRANT -g -DDEBUG -c ../../../src/foundation/ZUnicode.cpp -o objects-debug/ZUnicode.o /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:326: explicit instantiation of `struct ZUnicode::Functions_CountCU_T' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:58: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:327: explicit instantiation of `struct ZUnicode::Functions_CountCU_T' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:71: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:328: explicit instantiation of `struct ZUnicode::Functions_CountCU_T' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:84: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:330: explicit instantiation of `struct ZUnicode::Functions_CountCU_T' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:97: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:331: explicit instantiation of `struct ZUnicode::Functions_CountCU_T<__wchar_t *>' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:110: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:332: explicit instantiation of `struct ZUnicode::Functions_CountCU_T' after /boot/home/develop/zoolib/src/foundation/ZUnicodePriv.h:123: explicit specialization here /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:343: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:344: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:345: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:347: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:348: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T<__wchar_t *>' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:349: duplicate explicit instantiation of `struct ZUnicode::Functions_Count_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:360: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:361: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:362: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:364: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:365: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T<__wchar_t *,__wchar_t>' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:366: duplicate explicit instantiation of `struct ZUnicode::Functions_Read_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:373: duplicate explicit instantiation of `struct ZUnicode::Functions_Write_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:374: duplicate explicit instantiation of `struct ZUnicode::Functions_Write_T<__wchar_t *,__wchar_t>' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:375: duplicate explicit instantiation of `struct ZUnicode::Functions_Write_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:386: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:387: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:388: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:390: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:391: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T<__wchar_t *>' /boot/home/develop/zoolib/src/foundation/ZUnicode.cpp:392: duplicate explicit instantiation of `struct ZUnicode::Functions_Convert_T' make: *** [objects-debug/ZUnicode.o] Error 1 ~/develop/zoolib/samples/buttonmessage/buttonmessage_build_be> }}} It errors out but didn't crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 21:40:04 2009 From: trac at haiku-os.org (umccullough) Date: Thu, 09 Jul 2009 19:40:04 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.bf3e7333d995a8845ddabbe298f68c43@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by umccullough): Crashes while compiling on VirtualBox are somewhat common from what I've heard. I've also had people tell me VBox crashes with guru meditation quite frequently while attempting to compile on it. Often times, I've found that compiling the same software on real hardware yields no crash. Not sure what to suggest though :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 21:52:42 2009 From: trac at haiku-os.org (atmartens) Date: Thu, 09 Jul 2009 19:52:42 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.5d2a97b6649b0ae4b1fe013c97160313@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by atmartens): {{{ linux:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller [8086:29e0] (rev 01) 00:01.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host- Primary PCI Express Bridge [8086:29e1] (rev 01) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 02) 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) 00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 SATA RAID Controller [8086:2822] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 01:00.0 VGA compatible controller [0300]: nVidia Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) 02:00.0 IDE interface [0101]: JMicron Technologies, Inc. JMB368 IDE controller [197b:2368] 03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller [11ab:4364] (rev 12) 05:02.0 Multimedia audio controller [0401]: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller [1412:1712] (rev 02) 05:03.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller [1106:3044] (rev c0) }}} ---- So I did some more investigating and here is what I found (excerpt): {{{ int 3, enabled 3, handled 4239954, unhandled 0 hda:_ZL21hda_interrupt_handlerP14hda_controller (0x844ee99f), data 0x844f46c0 oss:ossintr (0x851373e0), data 0x810a40cc ahci:_ZN14AHCIController9InterruptEPv (0x805ba55a), data 0x80fb6bf4 }}} There are a lot of handled interrupts, and that number increases rather quickly (good guess, stippi!). So at first glance I thought maybe the BIOS hard drive settings are involved. I changed my hard drive from AHCI mode to IDE mode. This time, the boot sequence didn't finish, and it gave me a different error message (I forgot to write it down, can always get it again if need be). It said something along the line that there were no interrupts, or they were disabled, I forget. Going back to AHCI mode allows for the boot sequence to finish but gives me all those interrupts. In a perhaps related note, I have had issues using Linux's realtime kernel. Specifically, one of my two cores gets pegged on hardware interrupts (as seen by ''top''), and after a few hours the system hangs. Switching to IDE mode makes no difference. The regular Linux kernel works fine, though, as does Windows. I have the latest BIOS version, and otherwise have no reason to suspect general hardware issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 21:56:25 2009 From: trac at haiku-os.org (umccullough) Date: Thu, 09 Jul 2009 19:56:25 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.d350beb2c275f00b3147905304378e42@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by umccullough): You appear to have OpenSound installed, and it's probably trying to access the same HDA hardware as Haiku's built-in HDA driver. You should never install OpenSound if existing drivers already support your hardware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 22:04:17 2009 From: trac at haiku-os.org (atmartens) Date: Thu, 09 Jul 2009 20:04:17 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.3df1200b2d9a9d16c61450ca6cad77dd@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by atmartens): Yes, I can confirm that removing OpenSound from my build profile resolved the issue. However, I do recommend then that you remove OpenSound from the default @disk build profile, someone else is bound to make the same mistake. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 22:09:21 2009 From: trac at haiku-os.org (umccullough) Date: Thu, 09 Jul 2009 20:09:21 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.4e0b6f6b80a02c2cd92e3a82658bd75c@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by umccullough): AFAIK, There's no "default" @disk profile - unless you're referring to either UserBuildConfig.ReadMe, or UserBuildConfig.sample. The @alpha* profiles do not contain OpenSound, but do contain the optional packages that are currently recommended for the (not-yet-released) Haiku alpha build. http://dev.haiku-os.org/browser/haiku/trunk/build/jam/ReleaseBuildProfiles If you're looking for a good "base" system, I would use these as a guideline. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 9 22:16:52 2009 From: trac at haiku-os.org (atmartens) Date: Thu, 09 Jul 2009 20:16:52 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.6f698c8a18232fdb47362210a2da03eb@haiku-os.org> #4088: System is slow -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by atmartens): Yes, I was referring to the ".sample" file. I will take a look at those. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 00:24:37 2009 From: trac at haiku-os.org (stippi) Date: Thu, 09 Jul 2009 22:24:37 -0000 Subject: [Haiku-bugs] [Haiku] #4088: System is slow In-Reply-To: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> References: <044.ff35cd218bbd45bbf8d33206cb9d038b@haiku-os.org> Message-ID: <053.441f9e35b56dbd84e36b8d453e944f89@haiku-os.org> #4088: System is slow ------------------------+--------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: I could close this as yet another duplicate of our device manager problem with BeOS style drivers not being prevented to access the same device... was it #5 or something? :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 02:13:41 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 10 Jul 2009 00:13:41 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.11cbc0cad39e9ed3d3fed18b585777eb@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by mmlr): Replying to [comment:4 umccullough]: > Crashes while compiling on VirtualBox are somewhat common from what I've heard. I've also had people tell me VBox crashes with guru meditation quite frequently while attempting to compile on it. > > Often times, I've found that compiling the same software on real hardware yields no crash. I'm not convinced that this really is a VBox problem. It is known that compiling some projects will reset the system on real hardware. Like compiling GCC on GCC4 Haiku does trigger that sometimes, but I've also seen it by building Haiku itself. A system reset is essentially impossible to debug when you have no clue how to reproduce it or where to start from. If this problem is indeed the same problem as with the system resets, and there is a reproducible testcase as well as an environment where you can work from, this would be a great candidate to track down this issue. Is there any information that VBox outputs that could be used as a starting point to debug this? I don't have a system around that would run VBox, so I can't test this myself right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 03:04:24 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Fri, 10 Jul 2009 01:04:24 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.3a27967d8ad6699dd7e54f588f0e30e1@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): It might be that ZooLib provides more of a stress-test than most sourcebases, because some of its source files are very long and involved. The usual C++ practice is to put just one class in a source/header pair, but many of ZooLib's modules have dozens of classes in them, and lots of really nasty implementation code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 02:47:51 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Fri, 10 Jul 2009 00:47:51 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.0fb926196d109b32ffd413deb725483e@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): scottmc, all those errors are some problem that GCC 2.95.3 has with tricky template code. I got it to build OK with GCC 4 - I just had to keep rebooting - but am still working on the 2.95.3 support. mmlr, when I get the Guru Meditation dialog, it offers to keep the guest loaded so that it can be examined with debugging tools. But it also warns that doing so is difficult. Back to you soon on my MacBook Pro testing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 03:51:26 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 10 Jul 2009 01:51:26 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.ca9e819ed3cb7d264eb745c1e062a348@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by mmlr): For reference, can you provide the configuration for the VM you're running this in, i.e. amount of RAM and such? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 03:56:58 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Fri, 10 Jul 2009 01:56:58 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.c67c71110abc59a07e36f2a5b5474e71@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): With VirtualBox 2.2.4 on a Core Duo (not Core 2 Duo) MacBook Pro running Mac OS X 10.5.7, Haiku r31471 GCC4 hung while building ButtonMessage, but r31471 GCC 2.95.3 didn't hang. I only tried each build once. The 2.95.3 compile didn't actually complete because of that problem with tricky templates. But I did "make -k" so it would compile all the other sources despite the failure. I will try next with VirtualBox 3.0.0. Sometimes Haiku crashes during boot in VirtualBox on my MacBook Pro, but I think that's a different bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 16:20:39 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 10 Jul 2009 14:20:39 -0000 Subject: [Haiku-bugs] [Haiku] #2431: [Tracker] missing shortcuts for icon views (easy) In-Reply-To: <040.2e127df1e18833e975e18d72f4908b4a@haiku-os.org> References: <040.2e127df1e18833e975e18d72f4908b4a@haiku-os.org> Message-ID: <049.fc30fff45ae42652287c9010c5808da6@haiku-os.org> #2431: [Tracker] missing shortcuts for icon views (easy) -----------------------------------+---------------------------------------- Reporter: diver | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: new => closed * resolution: => fixed Comment: closing, the enhancement has been implemented, issues mentioned in the last comments (if they still exist) should be (or are already) taken care in other tickets. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 18:43:21 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 10 Jul 2009 16:43:21 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color Message-ID: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- What about the possibility for the user to change the color of windows per window so that's a lot faster for the eye to find windows when working repeatedly with a large set of windows/workspaces. Color vision processing begins at a very early level in the visual system (even within the retina) and it's a shame that current desktop interfaces prefer to use colors for beauty and branding instead of actual meaning and usability. This goes against themes and the mono color windows, but that might also end up beautiful (and distinctive) if for example you're given a set of harmonized colors. In my understanding, this shouldn't be too hard to implement and test, as there is a quite similar mechanism for the per window tab position. Ability to tag folders in Tracker with colors would be the logical next step :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 19:32:42 2009 From: trac at haiku-os.org (humdinger) Date: Fri, 10 Jul 2009 17:32:42 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color In-Reply-To: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> References: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> Message-ID: <050.e6ce413ce67ffd7b926f935711290e35@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by humdinger): As long as it's optional...[[BR]] I'd propose making window borders/tabs colour drop aware. No big context menus or anything like that. It's important to only slightly tint the windows or you'll lose the distinction of the active window. One thing I always miss is what I used Windowshade for under BeOS: have the _whole_ active window (tabs+border) yellowed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 19:54:37 2009 From: trac at haiku-os.org (aldeck) Date: Fri, 10 Jul 2009 17:54:37 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color In-Reply-To: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> References: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> Message-ID: <050.cef5d97c2be2b3dbffe9f683d784a162@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by aldeck): Replying to [comment:1 humdinger]: > As long as it's optional...[[BR]] Yes that's the idea, just like moving tabs. Color drop is a good idea, and i agree with your other points too :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 20:04:11 2009 From: trac at haiku-os.org (humdinger) Date: Fri, 10 Jul 2009 18:04:11 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color In-Reply-To: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> References: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> Message-ID: <050.2dd7c0adada13ff2e67d6c43e8e97f88@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by humdinger): Also, there would have to be a setting in the Appearance preferences to quickly reset the default colours (i.e. removing all attributes). Maybe this whole thing should be done when rethinking the Appearance panel. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 20:37:23 2009 From: trac at haiku-os.org (diver) Date: Fri, 10 Jul 2009 18:37:23 -0000 Subject: [Haiku-bugs] [Haiku] #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel In-Reply-To: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> References: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> Message-ID: <049.59eae74884a8c4addc82947e6defa865@haiku-os.org> #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel --------------------------------+------------------------------------------- Reporter: diver | Owner: leavengood Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: New volume UI broke this feature. I would like to see it back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 20:38:17 2009 From: trac at haiku-os.org (diver) Date: Fri, 10 Jul 2009 18:38:17 -0000 Subject: [Haiku-bugs] [Haiku] #2323: [Media] volume control should react on scrolling up/down events (easy) In-Reply-To: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> References: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> Message-ID: <049.bc1830b9ca5af212ffcc43b1ec5cf188@haiku-os.org> #2323: [Media] volume control should react on scrolling up/down events (easy) --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: New volume UI broke this feature. I would like to see it back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 20:38:50 2009 From: trac at haiku-os.org (diver) Date: Fri, 10 Jul 2009 18:38:50 -0000 Subject: [Haiku-bugs] [Haiku] #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel In-Reply-To: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> References: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> Message-ID: <049.ff22f400dc7f7bbd47347c5efdb8fa5b@haiku-os.org> #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel --------------------------------+------------------------------------------- Reporter: diver | Owner: leavengood Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by diver): Sorry, wrong ticket. See #2323. Please close it again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 10 20:43:15 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 10 Jul 2009 18:43:15 -0000 Subject: [Haiku-bugs] [Haiku] #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel In-Reply-To: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> References: <040.dc724c4fe949d294a2d0f093964b14fe@haiku-os.org> Message-ID: <049.5aed4bf99040ff6ada5575a3a6e6f47d@haiku-os.org> #3577: [Media] volume deskbar replicant should allow dragging volume slider using a mouse wheel --------------------------------+------------------------------------------- Reporter: diver | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by anevilyak): * status: reopened => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 01:17:54 2009 From: trac at haiku-os.org (leavengood) Date: Fri, 10 Jul 2009 23:17:54 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color In-Reply-To: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> References: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> Message-ID: <050.93c161aaefdf5026fbd039ca778531f5@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by leavengood): A first step would be to make the window border's color editable. As far as I can see it is currently not editable. I also agree that the Appearances preflet needs some work. But in general I agree that color is important for visual identification (though I think shape might be more important, see my recent email about Haiku icons.) Both the general proposal and the color droppable borders and tabs sounds interesting to me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 02:07:04 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Sat, 11 Jul 2009 00:07:04 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.4b2076c5d48e538104fe7ffd0e2925a7@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): With VirtualBox 3.0.0 on my MacBook Pro, r31471 GCC4 hung during the build both times I tried it. r31471 didn't have any problems the first time I tried it, but the second time an alert appeared saying g++ had crashed, then when I dismissed the alert the build continued for about a second and then I got that Guru Meditation message saying the guest had crashed. mmlr, on my Mac I have these configurations for my VirtualBox guests - I'll post the Linux configs in a little while: r31471 GCC 2.95.3 OS Type: Other/Unknown Base Memory: 256 MB Processors: 1 Boot Order: Floppy, CD-ROM, Hard Disk VT-x/AMD-v: Enabled (But I'm not sure my Core Duo CPU actually has the feature) Nested Paging: Disabled Video Memory: 32 MB 3D Accelleration: Enabled Remote Display Server: Disabled Hard Disk: Haiku on IDE Primary Master (ie not SATA) Host Audio Driver: Core Audio Controller: ICH 97 Network: Intel Pro 1000 MT Desktop (NAT) Serial Ports: Disabled USB Device Filters: 0 (0 Active) Shared Folders: None r31471 GCC 4 OS Type: Other/Unknown Base Memory: 256 MB Processors: 1 Boot Order: Floppy, CD-ROM, Hard Disk VT-x/AMD-v: Enabled (But I'm not sure my Core Duo CPU actually has the feature) Nested Paging: Disabled Video Memory: 6 MB 3D Accelleration: Disabled Remote Display Server: Disabled Hard Disk: Haiku on IDE Primary Master (ie not SATA) Host Audio Driver: Core Audio Controller: ICH 97 Network: Intel Pro 1000 MT Desktop (NAT) Serial Ports: Disabled USB Device Filters: 0 (0 Active) Shared Folders: None My MacBook Pro is a 1.83 GHz first-generation model. It has a Core Duo CPU, not Core 2 Duo. It is just 32-bit, and I don't think that the CPU actually has Intel VT-x. My memory is hazy, but it seems to me that some early version of VirtualBox complained when I tried to boot a guest with VT-x enabled. Back to you this evening on the Linux configs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 02:07:49 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Sat, 11 Jul 2009 00:07:49 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.0257f1e7bc80d67eed06355c2052fa48@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): Oopsy... sorry I didn't realize the line breaks wouldn't be preserved. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 05:50:24 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 11 Jul 2009 03:50:24 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.ff5632518f82315bb5a66913b3012127@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by mmlr): That's about what I expected. If you give the VM 512MB RAM to run with it'll work. While there certainly are bugs in VirtualBox as well, this really looks more like a problem with low memory situations on Haiku's side to me. I can reproduce your issue by compiling most anything in VBox with little enough memory, I'll try to wrap my head around it, but it's not really easy to find a point to start here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 10:50:12 2009 From: trac at haiku-os.org (stippi) Date: Sat, 11 Jul 2009 08:50:12 -0000 Subject: [Haiku-bugs] [Haiku] #4089: Per window tab/border color In-Reply-To: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> References: <041.7a6d952a674685e352fea01b359ccb9f@haiku-os.org> Message-ID: <050.7f162cc373397b58796821b0ee60755c@haiku-os.org> #4089: Per window tab/border color -------------------------+-------------------------------------------------- Reporter: aldeck | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by stippi): The proposal definitely sounds interesting. In terms of implementation, it would be super easy, since each Decorator instance in the app_server has the colors as members. So it would be easy to change them per instance. The only problem could be the decor buttons, since those are cached globally, I believe. But for that case, one could just add the color to the hash value used for lookup, if that's not already the case. As for the feature itself, I believe the assertion to only allow subtle color variations in order to keep active windows distinctive is somewhat flawed. I think the stronger the allowed color difference, the more the effect is explored/utilized. That of course has indeed the problem that active windows are less visible. Maybe make the distinction by using either the whole frame colored (active window) or the tab only (inactive window). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 11:11:40 2009 From: trac at haiku-os.org (MichaelCrawford) Date: Sat, 11 Jul 2009 09:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox In-Reply-To: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> References: <050.98de9a40aa9516b96661197b36f3fc91@haiku-os.org> Message-ID: <059.400a8820867c63be0b6f584b5f63d0b9@haiku-os.org> #4087: Building ZooLib ButtonMessage sample crashes Haiku when run under VirtualBox -----------------------------+---------------------------------------------- Reporter: MichaelCrawford | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by MichaelCrawford): mmlr, both of my Linux guests had 512 MB in my initial tests. I tried the GCC4 build just now with more memory. I got crashes with 1024 and 2048 MB, but with 4096 MB I was able to build several times with no crashes. Note that the r31471 build is distributed with virtual memory disabled. I'll try enabling it and giving it lots of swap space in a little while. If the problem is memory stress, it would make sense to write a test tool that just uses up lots of memory in a repeatible way. Quite likely the problem Haiku has with the ZooLib build is that some of its source files are quite large and complex, so g++'s symbol tables would take up a lot of memory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 14:13:11 2009 From: trac at haiku-os.org (czeidler) Date: Sat, 11 Jul 2009 12:13:11 -0000 Subject: [Haiku-bugs] [Haiku] #4090: Terminal adds key codes (arrow, home, end...) when searching the history Message-ID: <043.696231d99009cf3a029b3715aba677df@haiku-os.org> #4090: Terminal adds key codes (arrow, home, end...) when searching the history -----------------------+---------------------------------------------------- Reporter: czeidler | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When searching in the history (control + r) and then press a arrow, home, end key some characters (looks like the key code) are added to the search result! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 16:24:33 2009 From: trac at haiku-os.org (laplace) Date: Sat, 11 Jul 2009 14:24:33 -0000 Subject: [Haiku-bugs] [Haiku] #2935: Print preview colors In-Reply-To: <041.98e2fbd224e095eb470d2c9ffc140b58@haiku-os.org> References: <041.98e2fbd224e095eb470d2c9ffc140b58@haiku-os.org> Message-ID: <050.53760d5213e7e02cc48cc27c819bb355@haiku-os.org> #2935: Print preview colors -----------------------+---------------------------------------------------- Reporter: miqlas | Owner: julun Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Printing | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------+---------------------------------------------------- Changes (by laplace): * status: new => closed * resolution: => fixed Comment: Fixed in r31519. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 16:49:19 2009 From: trac at haiku-os.org (Hubert) Date: Sat, 11 Jul 2009 14:49:19 -0000 Subject: [Haiku-bugs] [Haiku] #4084: Lack 1440x900 resolutoion In-Reply-To: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> References: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> Message-ID: <050.5246d658ed9fd63d900410adadffd4a7@haiku-os.org> #4084: Lack 1440x900 resolutoion -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Hubert): Strange. In r. r31517(gcc2/ggc4) I have 1440x900 but lack 1400x1050 or 1680x1200 etc. which were in r31459(gcc4/gcc2) to choice. [[BR]][http://dev.haiku-os.org/attachment/ticket/3922/listdev listdev] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 19:29:59 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 11 Jul 2009 17:29:59 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam Message-ID: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Didn't paste stuff between triple brackets because Trac would generate an enormous single line on the GCC output. Sorry for the accidental wikiformatting, like underlined DEFINE words. Generated dir was clean except for the build, downloads and cross-tools dirs. @all target is verbatim Ingo's suggestion on the mailing list for a target that doesn't produce an image. ---- jam -aqj8 @all ---- In file included from /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:41:[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/include/y.tab.h:1: parse.h: No such file or directory[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c: In function `make_command_string_internal':[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: `AND_AND' undeclared (first use in this function)[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: (Each undeclared identifier is reported only once[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: for each function it appears in.)[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:240: `OR_OR' undeclared (first use in this function)[[BR]][[BR]] /usr/home/andre/devel/Haiku/trunk/generated.gcc2/cross-tools/bin/i586-pc- haiku-gcc -O -Wno-trigraphs -Wpointer-arith -Wcast-align -Wno-multichar -pipe -nostdinc -DHAVE_CONFIG_H -DPROGRAM='"bash"' -DSHELL -DCONF_MACHTYPE='"i586-pc-haiku"' -DCONF_HOSTTYPE='"i586"' -DCONF_VENDOR='"pc"' -DCONF_OSTYPE='"beos"' -c "/usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c" -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DBOOT_ARCHIVE_IMAGE_OFFSET=300 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I/usr/home/andre/devel/Haiku/trunk/build/user_config_headers -I/usr/home/andre/devel/Haiku/trunk/build/config_headers -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/common/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/freebsd/x86/common/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash -I- -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/include -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/lib -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash -I/usr/home/andre/devel/Haiku/trunk/headers/cpp -I/usr/home/andre/devel/Haiku/trunk/headers/build/gcc-2.95.3 -I/usr/home/andre/devel/Haiku/trunk/headers -I/usr/home/andre/devel/Haiku/trunk/headers/posix -I/usr/home/andre/devel/Haiku/trunk/headers/gnu -I/usr/home/andre/devel/Haiku/trunk/headers/glibc -I/usr/home/andre/devel/Haiku/trunk/headers/os -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/file_system -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/graphics -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/input_server -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/registrar -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/screen_saver -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/tracker -I/usr/home/andre/devel/Haiku/trunk/headers/os/app -I/usr/home/andre/devel/Haiku/trunk/headers/os/device -I/usr/home/andre/devel/Haiku/trunk/headers/os/drivers -I/usr/home/andre/devel/Haiku/trunk/headers/os/game -I/usr/home/andre/devel/Haiku/trunk/headers/os/interface -I/usr/home/andre/devel/Haiku/trunk/headers/os/kernel -I/usr/home/andre/devel/Haiku/trunk/headers/os/media -I/usr/home/andre/devel/Haiku/trunk/headers/os/mail -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi2 -I/usr/home/andre/devel/Haiku/trunk/headers/os/net -I/usr/home/andre/devel/Haiku/trunk/headers/os/opengl -I/usr/home/andre/devel/Haiku/trunk/headers/os/storage -I/usr/home/andre/devel/Haiku/trunk/headers/os/support -I/usr/home/andre/devel/Haiku/trunk/headers/os/translation -I/usr/home/andre/devel/Haiku/trunk/headers/private/. -o "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/print_cmd.o" ;[[BR]][[BR]] ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/print_cmd.o ... ---- MkBuiltinsExt1 /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtext.h /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtins.c[[BR]] Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o[[BR]] i586-pc-haiku-gcc: /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtins.c: No such file or directory[[BR]] i586-pc-haiku-gcc: No input files[[BR]][[BR]] /usr/home/andre/devel/Haiku/trunk/generated.gcc2/cross-tools/bin/i586-pc- haiku-gcc -O -Wno-trigraphs -Wpointer-arith -Wcast-align -Wno-multichar -pipe -nostdinc -DHAVE_CONFIG_H -DSHELL -c "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtins.c" -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DBOOT_ARCHIVE_IMAGE_OFFSET=300 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I/usr/home/andre/devel/Haiku/trunk/build/user_config_headers -I/usr/home/andre/devel/Haiku/trunk/build/config_headers -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/freebsd/x86/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins -I- -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/.. -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../include -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../lib -I/usr/home/andre/devel/Haiku/trunk/headers/cpp -I/usr/home/andre/devel/Haiku/trunk/headers/build/gcc-2.95.3 -I/usr/home/andre/devel/Haiku/trunk/headers -I/usr/home/andre/devel/Haiku/trunk/headers/posix -I/usr/home/andre/devel/Haiku/trunk/headers/gnu -I/usr/home/andre/devel/Haiku/trunk/headers/glibc -I/usr/home/andre/devel/Haiku/trunk/headers/os -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/file_system -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/graphics -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/input_server -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/registrar -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/screen_saver -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/tracker -I/usr/home/andre/devel/Haiku/trunk/headers/os/app -I/usr/home/andre/devel/Haiku/trunk/headers/os/device -I/usr/home/andre/devel/Haiku/trunk/headers/os/drivers -I/usr/home/andre/devel/Haiku/trunk/headers/os/game -I/usr/home/andre/devel/Haiku/trunk/headers/os/interface -I/usr/home/andre/devel/Haiku/trunk/headers/os/kernel -I/usr/home/andre/devel/Haiku/trunk/headers/os/media -I/usr/home/andre/devel/Haiku/trunk/headers/os/mail -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi2 -I/usr/home/andre/devel/Haiku/trunk/headers/os/net -I/usr/home/andre/devel/Haiku/trunk/headers/os/opengl -I/usr/home/andre/devel/Haiku/trunk/headers/os/storage -I/usr/home/andre/devel/Haiku/trunk/headers/os/support -I/usr/home/andre/devel/Haiku/trunk/headers/os/translation -I/usr/home/andre/devel/Haiku/trunk/headers/private/. -o "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o" ;[[BR]][[BR]] ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o ... ---- Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/exit.o[[BR]] MkBuiltinsComp1 /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/help.c[[BR]] MkBuiltinsComp1 /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/history.c[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/exit.def: In function `exit_or_logout':[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/exit.def:99: `jobs_builtin' undeclared (first use in this function)[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/exit.def:99: (Each undeclared identifier is reported only once[[BR]] /usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/exit.def:99: for each function it appears in.)[[BR]] Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/hash.o[[BR]] Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/help.o[[BR]] Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/history.o[[BR]][[BR]] /usr/home/andre/devel/Haiku/trunk/generated.gcc2/cross-tools/bin/i586-pc- haiku-gcc -O -Wno-trigraphs -Wpointer-arith -Wcast-align -Wno-multichar -pipe -nostdinc -DHAVE_CONFIG_H -DSHELL -c "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/exit.c" -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DBOOT_ARCHIVE_IMAGE_OFFSET=300 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I/usr/home/andre/devel/Haiku/trunk/build/user_config_headers -I/usr/home/andre/devel/Haiku/trunk/build/config_headers -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/freebsd/x86/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins -I- -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/.. -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../include -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../lib -I/usr/home/andre/devel/Haiku/trunk/headers/cpp -I/usr/home/andre/devel/Haiku/trunk/headers/build/gcc-2.95.3 -I/usr/home/andre/devel/Haiku/trunk/headers -I/usr/home/andre/devel/Haiku/trunk/headers/posix -I/usr/home/andre/devel/Haiku/trunk/headers/gnu -I/usr/home/andre/devel/Haiku/trunk/headers/glibc -I/usr/home/andre/devel/Haiku/trunk/headers/os -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/file_system -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/graphics -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/input_server -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/registrar -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/screen_saver -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/tracker -I/usr/home/andre/devel/Haiku/trunk/headers/os/app -I/usr/home/andre/devel/Haiku/trunk/headers/os/device -I/usr/home/andre/devel/Haiku/trunk/headers/os/drivers -I/usr/home/andre/devel/Haiku/trunk/headers/os/game -I/usr/home/andre/devel/Haiku/trunk/headers/os/interface -I/usr/home/andre/devel/Haiku/trunk/headers/os/kernel -I/usr/home/andre/devel/Haiku/trunk/headers/os/media -I/usr/home/andre/devel/Haiku/trunk/headers/os/mail -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi2 -I/usr/home/andre/devel/Haiku/trunk/headers/os/net -I/usr/home/andre/devel/Haiku/trunk/headers/os/opengl -I/usr/home/andre/devel/Haiku/trunk/headers/os/storage -I/usr/home/andre/devel/Haiku/trunk/headers/os/support -I/usr/home/andre/devel/Haiku/trunk/headers/os/translation -I/usr/home/andre/devel/Haiku/trunk/headers/private/. -o "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/exit.o" ; [[BR]][[BR]] ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/exit.o ... ---- ...failed updating 3 target(s)...[[BR]] ...skipped 2 target(s)...[[BR]] ...updated 9442 target(s)...[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 20:14:51 2009 From: trac at haiku-os.org (Hubert) Date: Sat, 11 Jul 2009 18:14:51 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.4947323543a5a06e9993d18285ef3072@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by Hubert): * cc: HubertNG@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:08:20 2009 From: trac at haiku-os.org (modeenf) Date: Sat, 11 Jul 2009 20:08:20 -0000 Subject: [Haiku-bugs] [Haiku] #3099: BePDF KDLs on exit In-Reply-To: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> References: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> Message-ID: <050.6290e95dfdbc4b299d0b54472717597c@haiku-os.org> #3099: BePDF KDLs on exit --------------------------+------------------------------------------------- Reporter: kvdman | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: 3588 | --------------------------+------------------------------------------------- Comment(by modeenf): I tested to start and close BePDF in r31406 and I hade no problem.Can I close this one? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:14:42 2009 From: trac at haiku-os.org (modeenf) Date: Sat, 11 Jul 2009 20:14:42 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 In-Reply-To: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> References: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> Message-ID: <047.4048362f080c314b97aaea4cf3114d75@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 --------------------------+------------------------------------------------- Reporter: oco | Owner: modeenf Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:34:06 2009 From: trac at haiku-os.org (Luposian) Date: Sat, 11 Jul 2009 20:34:06 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.912c18f29e7e123c9e74edb5a8982a11@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Luposian): Replying to [comment:3 umccullough]: > It's not a required file. Likely there's a non-default setting in the file you grabbed that changed the behavior. "It's not a required file.", yet it was a file *I* required, to get my monitor's native resolution detected and made available. And, the behavior it changed was that my monitor's native resolution wasn't detected before... but now it is. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:36:46 2009 From: trac at haiku-os.org (fano) Date: Sat, 11 Jul 2009 20:36:46 -0000 Subject: [Haiku-bugs] [Haiku] #3732: Renaming files: selection without suffix In-Reply-To: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> References: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> Message-ID: <053.5843badaba2f0e70ba2fbd5be4f6f545@haiku-os.org> #3732: Renaming files: selection without suffix ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by fano): Maybe I do a lot simple but you can't search for the characters that are after the last point? That is if the file name is "the.zuccabubu.brothers.last.song.mp3" if Traker search the last point it knows when stop (.mp3 is the extension)... a simple strrchr() can do the trick! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:40:29 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 11 Jul 2009 20:40:29 -0000 Subject: [Haiku-bugs] [Haiku] #3732: Renaming files: selection without suffix In-Reply-To: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> References: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> Message-ID: <053.2f8949dcafe91877877daf2a3116fbff@haiku-os.org> #3732: Renaming files: selection without suffix ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by mmadia): Couldn't this be better handled by [http://dev.osdrawer.net/projects/show/pecorename PecoRename]? The code has been released as MIT and is hosted at OSDrawer. I'd be more than willing grant access to anyone willing to work on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:41:10 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 11 Jul 2009 20:41:10 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.1234ad4dd406e2f99562c2b96fe62c67@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): The first and the third problem are fixed in r31523 respectively r31524. The second one is a bit weird, since jam seems to know that builtins.o depends on builtins.c. "jam -dd" says so at least: {{{ Depends "builtins.o" : "builtins.c" ; }}} So it shouldn't try to make builtins.o before builtins.c has been made. Anyway, I've built bash a few times with "-j8" and didn't get anymore errors. Please give the new revision a whirl. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 22:43:10 2009 From: trac at haiku-os.org (modeenf) Date: Sat, 11 Jul 2009 20:43:10 -0000 Subject: [Haiku-bugs] [Haiku] #2162: Vmware screen resolution 800x600 slows down the system In-Reply-To: <042.295c2a48ae30d9e40a238430d7e5e3da@haiku-os.org> References: <042.295c2a48ae30d9e40a238430d7e5e3da@haiku-os.org> Message-ID: <051.ac39d7a916d595d088d99e6cd8a02aa9@haiku-os.org> #2162: Vmware screen resolution 800x600 slows down the system ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by modeenf): * status: new => closed * resolution: => fixed Comment: Tested in in r31471. Tested 1024x764 -> 800x600 and back, think that the vesa driver fixed this, closing this one. Open it if the problem still exists. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 23:15:37 2009 From: trac at haiku-os.org (fano) Date: Sat, 11 Jul 2009 21:15:37 -0000 Subject: [Haiku-bugs] [Haiku] #2985: ProcessController preselected button In-Reply-To: <041.34e9686bb951caad7a7568c15b698828@haiku-os.org> References: <041.34e9686bb951caad7a7568c15b698828@haiku-os.org> Message-ID: <050.06cadbb075b7d659778ea651f553ee20@haiku-os.org> #2985: ProcessController preselected button --------------------------+------------------------------------------------- Reporter: miqlas | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by fano): Or Maybe the "Kernel Team" and others - if any - system vital processes, too must be protected in some way... I mean if you kill it/them Haiku is dead too, right? I think there no safe cause to kill "Kernel Team" or other vital process... Haiku is not Windows in which if the system goes crazy I must kill explorer! I think some processes can e show but not killed... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 23:38:14 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 11 Jul 2009 21:38:14 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.f3578d068dc214824a26ae812bdba821@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:1 bonefish]: > Anyway, I've built bash a few times with "-j8" and didn't get anymore errors. Please give the new revision a whirl. Building right now. Considering that all the build system bugs I reported lately are Bash- related and also related to remaking its own build system to use jam, isn't it more trouble than it's worth? I mean, can't we, for imported software, simply invoke make in a subshell or something? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 11 23:51:12 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 11 Jul 2009 21:51:12 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.632d22b4bdd5e125a346fa4d05aa8517@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Replying to [comment:2 meianoite]: > Considering that all the build system bugs I reported lately are Bash- related and also related to remaking its own build system to use jam, isn't it more trouble than it's worth? I mean, can't we, for imported software, simply invoke make in a subshell or something? The build system of most imported software is autotools + make based. This is something I *so* don't want to integrate in our build system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 00:17:24 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 11 Jul 2009 22:17:24 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.950900d6beb9c774263bf5512ee7875e@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by umccullough): Please understand... my point was simple: it shouldn't be required. The reason it worked is because the file contains non-standard options to manipulate the driver in ways that can't be anticipated automatically. Ultimately, the proper solution would be to fix the driver to detect the situation which required manual tweaking of the settings file. The reason the file is not included by default is because it should not be needed unless the driver is having issues doing the "right thing" without manual intervention. Clearly there is an issue with your particular hardware and monitor that prevents the driver from automatically detecting your resolution. Tou should probably put a # in front of each value in the nvidia.settings and restart until you find the one setting that breaks it again, that would be the most helpful for rudolf to determine what the actual issue is. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 00:18:59 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 11 Jul 2009 22:18:59 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.d0e2c8e11aa6c4ef032fe5da1574db34@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:3 bonefish]: > The build system of most imported software is autotools + make based. This is something I *so* don't want to integrate in our build system. Well, such pain is yours to feel :) r31524: {{{ In file included from /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:41: /usr/home/andre/devel/Haiku/trunk/src/bin/bash/include/y.tab.h:1: parse.h: No such file or directory /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c: In function `make_command_string_internal': /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: `AND_AND' undeclared (first use in this function) /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: (Each undeclared identifier is reported only once /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:234: for each function it appears in.) /usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c:240: `OR_OR' undeclared (first use in this function) As /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/kits/opengl/mesa/x86_xform4.o As /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/kits/opengl/mesa/x86_cliptest.o As /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/kits/opengl/mesa/mmx_blend.o /usr/home/andre/devel/Haiku/trunk/generated.gcc2/cross-tools/bin/i586-pc- haiku-gcc -O -Wno-trigraphs -Wpointer-arith -Wcast-align -Wno-multichar -pipe -nostdinc -DHAVE_CONFIG_H -DPROGRAM='"bash"' -DSHELL -DCONF_MACHTYPE='"i586-pc-haiku"' -DCONF_HOSTTYPE='"i586"' -DCONF_VENDOR='"pc"' -DCONF_OSTYPE='"beos"' -c "/usr/home/andre/devel/Haiku/trunk/src/bin/bash/print_cmd.c" -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DBOOT_ARCHIVE_IMAGE_OFFSET=300 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I/usr/home/andre/devel/Haiku/trunk/build/user_config_headers -I/usr/home/andre/devel/Haiku/trunk/build/config_headers -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/common/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/freebsd/x86/common/bin/bash -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash -I- -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/include -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/lib -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash -I/usr/home/andre/devel/Haiku/trunk/headers/cpp -I/usr/home/andre/devel/Haiku/trunk/headers/build/gcc-2.95.3 -I/usr/home/andre/devel/Haiku/trunk/headers -I/usr/home/andre/devel/Haiku/trunk/headers/posix -I/usr/home/andre/devel/Haiku/trunk/headers/gnu -I/usr/home/andre/devel/Haiku/trunk/headers/glibc -I/usr/home/andre/devel/Haiku/trunk/headers/os -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/file_system -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/graphics -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/input_server -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/registrar -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/screen_saver -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/tracker -I/usr/home/andre/devel/Haiku/trunk/headers/os/app -I/usr/home/andre/devel/Haiku/trunk/headers/os/device -I/usr/home/andre/devel/Haiku/trunk/headers/os/drivers -I/usr/home/andre/devel/Haiku/trunk/headers/os/game -I/usr/home/andre/devel/Haiku/trunk/headers/os/interface -I/usr/home/andre/devel/Haiku/trunk/headers/os/kernel -I/usr/home/andre/devel/Haiku/trunk/headers/os/media -I/usr/home/andre/devel/Haiku/trunk/headers/os/mail -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi2 -I/usr/home/andre/devel/Haiku/trunk/headers/os/net -I/usr/home/andre/devel/Haiku/trunk/headers/os/opengl -I/usr/home/andre/devel/Haiku/trunk/headers/os/storage -I/usr/home/andre/devel/Haiku/trunk/headers/os/support -I/usr/home/andre/devel/Haiku/trunk/headers/os/translation -I/usr/home/andre/devel/Haiku/trunk/headers/private/. -o "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/print_cmd.o" ; ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/print_cmd.o ... }}} Our friend print_cmd again, and again failing on y.tab.h, now for a different reason. Lovely insertion of Mesa being assembled because of the parallel build :) ---- {{{ Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o i586-pc-haiku-gcc: /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtins.c: No such file or directory i586-pc-haiku-gcc: No input files /usr/home/andre/devel/Haiku/trunk/generated.gcc2/cross-tools/bin/i586-pc- haiku-gcc -O -Wno-trigraphs -Wpointer-arith -Wcast-align -Wno-multichar -pipe -nostdinc -DHAVE_CONFIG_H -DSHELL -c "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins/builtins.c" -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -DBOOT_ARCHIVE_IMAGE_OFFSET=300 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I/usr/home/andre/devel/Haiku/trunk/build/user_config_headers -I/usr/home/andre/devel/Haiku/trunk/build/config_headers -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/freebsd/x86/common/bin/bash/builtins -I/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/builtins -I- -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/.. -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../include -I/usr/home/andre/devel/Haiku/trunk/src/bin/bash/builtins/../lib -I/usr/home/andre/devel/Haiku/trunk/headers/cpp -I/usr/home/andre/devel/Haiku/trunk/headers/build/gcc-2.95.3 -I/usr/home/andre/devel/Haiku/trunk/headers -I/usr/home/andre/devel/Haiku/trunk/headers/posix -I/usr/home/andre/devel/Haiku/trunk/headers/gnu -I/usr/home/andre/devel/Haiku/trunk/headers/glibc -I/usr/home/andre/devel/Haiku/trunk/headers/os -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/file_system -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/graphics -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/input_server -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/registrar -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/screen_saver -I/usr/home/andre/devel/Haiku/trunk/headers/os/add-ons/tracker -I/usr/home/andre/devel/Haiku/trunk/headers/os/app -I/usr/home/andre/devel/Haiku/trunk/headers/os/device -I/usr/home/andre/devel/Haiku/trunk/headers/os/drivers -I/usr/home/andre/devel/Haiku/trunk/headers/os/game -I/usr/home/andre/devel/Haiku/trunk/headers/os/interface -I/usr/home/andre/devel/Haiku/trunk/headers/os/kernel -I/usr/home/andre/devel/Haiku/trunk/headers/os/media -I/usr/home/andre/devel/Haiku/trunk/headers/os/mail -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi -I/usr/home/andre/devel/Haiku/trunk/headers/os/midi2 -I/usr/home/andre/devel/Haiku/trunk/headers/os/net -I/usr/home/andre/devel/Haiku/trunk/headers/os/opengl -I/usr/home/andre/devel/Haiku/trunk/headers/os/storage -I/usr/home/andre/devel/Haiku/trunk/headers/os/support -I/usr/home/andre/devel/Haiku/trunk/headers/os/translation -I/usr/home/andre/devel/Haiku/trunk/headers/private/. -o "/usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o" ; ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o ... }}} Well, builtins.c again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 00:21:10 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 11 Jul 2009 22:21:10 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.71c621906755de13bf377048b42d18e5@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:4 meianoite]: > Our friend print_cmd again, and again failing on y.tab.h, now for a different reason. Same reason, actually! O_O -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 00:24:02 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 11 Jul 2009 22:24:02 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.46be4fc1ab4b5da4f14d6a443b6f6ec8@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:5 meianoite]: > Same reason, actually! O_O For good measure: {{{ > svn info Path: . URL: http://svn.berlios.de/svnroot/repos/haiku/haiku/trunk Repository Root: http://svn.berlios.de/svnroot/repos/haiku Repository UUID: a95241bf-73f2-0310-859d-f6bbb57e9c96 Revision: 31524 Node Kind: directory Schedule: normal Last Changed Author: bonefish Last Changed Rev: 31524 Last Changed Date: 2009-07-11 17:27:44 -0300 (Sat, 11 Jul 2009) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 01:00:48 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 11 Jul 2009 23:00:48 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.c6af86d839e74656cb0c95b84ede7706@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): The dependencies look OK for both cases, so I'd consider this a jam bug. Under Haiku I couldn't reproduce it (two cores only, though). Am I assuming correctly that your build platform is FreeBSD? Would be interesting, if this can be reproduced on Linux, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 02:07:22 2009 From: trac at haiku-os.org (Luposian) Date: Sun, 12 Jul 2009 00:07:22 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.8c6e6684718adad7afe44e312198f616@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Luposian): Replying to [comment:8 umccullough]: > Please understand... my point was simple: it shouldn't be required. The reason it worked is because the file contains non-standard options to manipulate the driver in ways that can't be anticipated automatically. > > Ultimately, the proper solution would be to fix the driver to detect the situation which required manual tweaking of the settings file. > > The reason the file is not included by default is because it should not be needed unless the driver is having issues doing the "right thing" without manual intervention. Clearly there is an issue with your particular hardware and monitor that prevents the driver from automatically detecting your resolution. > > Tou should probably put a # in front of each value in the nvidia.settings and restart until you find the one setting that breaks it again, that would be the most helpful for rudolf to determine what the actual issue is. The only thing in that file that I needed to change, in order to make my monitor's native resolution (1440x900) seen and available, was to change "force_ws" to true. Nothing else made any difference, as the *resolution* was the only issue. The funny thing is, the syslog shows that the native resolution is right there all along... but Haiku never makes it available without the file and "force_ws" being set to true. I don't understand that. Why can't the file just be left and, if there is a display issue, it can be (hopefully) fixed by adjusting the "nvidia.settings" file? The same for every other graphics card settings file. If the file is to be removed, then why not have an "Other display options" button somewhere in "Screen", that offers you every possible display settings combination that isn't normally available. Maybe make it so that you have to hold down Shift or something to make it appear (or to ungrey it, as it's normally greyed out), to click on it and access the other options. That way it's not messed with accidentally. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 04:13:02 2009 From: trac at haiku-os.org (umccullough) Date: Sun, 12 Jul 2009 02:13:02 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.35fe2c5d00f79e7030b933dfa83a501f@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by umccullough): Interestingly, force_ws is set to false in the settings file in subversion, so you must have manually edited to make it work anyway... In any case, as you can see from the tickets already here: http://dev.haiku-os.org/search?q=force_ws&noquickjump=1&ticket=on The use of that setting is sometimes problematic as well. Rudolf is already adding EDID support to the driver to have it detect the resolutions automatically (perhaps the EDID info is what you're seeing the syslog when the vesa driver queries the card for monitor resolutions). In any case, perhaps attaching a syslog to this ticket would even help more, since you seem to already have viewed it and determined that there is useful information there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 04:27:28 2009 From: trac at haiku-os.org (leavengood) Date: Sun, 12 Jul 2009 02:27:28 -0000 Subject: [Haiku-bugs] [Haiku] #3418: media_server crashes at startup with rev291524 In-Reply-To: <049.bcc3d626f305bbc546d3875a25e2a69f@haiku-os.org> References: <049.bcc3d626f305bbc546d3875a25e2a69f@haiku-os.org> Message-ID: <058.303bf041422458d0da16b4299615cc8d@haiku-os.org> #3418: media_server crashes at startup with rev291524 ----------------------------------+----------------------------------------- Reporter: the ringmaster | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by leavengood): I am getting this error on r31524 after updating everything for the 32-bit wchar_t change. Also this is on GCC 2. Whenever I try to run the media_server the above error comes up and I see this in the serial log: bfs: bfs_access:1428: Operation not allowed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 04:44:50 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 12 Jul 2009 02:44:50 -0000 Subject: [Haiku-bugs] [Haiku] #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled Message-ID: <044.188d895a987b0891b018b8f7673c6721@haiku-os.org> #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ With either of the block cache tracing options enabled, userlandfs fails to link its library due to not finding the trace entry symbols. This should probably be reworked to not include tracing when not building the objects for the kernel. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 04:53:04 2009 From: trac at haiku-os.org (kvdman) Date: Sun, 12 Jul 2009 02:53:04 -0000 Subject: [Haiku-bugs] [Haiku] #3099: BePDF KDLs on exit In-Reply-To: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> References: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> Message-ID: <050.863bf960171d9caaa5076274f9b0c366@haiku-os.org> #3099: BePDF KDLs on exit --------------------------+------------------------------------------------- Reporter: kvdman | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: 3588 | --------------------------+------------------------------------------------- Comment(by kvdman): Seems resolved, please do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 05:47:17 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 12 Jul 2009 03:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled In-Reply-To: <044.188d895a987b0891b018b8f7673c6721@haiku-os.org> References: <044.188d895a987b0891b018b8f7673c6721@haiku-os.org> Message-ID: <053.857af659ad52368b3bef461456cf89cf@haiku-os.org> #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: bonefish => anevilyak * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 05:47:48 2009 From: trac at haiku-os.org (leavengood) Date: Sun, 12 Jul 2009 03:47:48 -0000 Subject: [Haiku-bugs] [Haiku] #3418: media_server crashes at startup with rev291524 In-Reply-To: <049.bcc3d626f305bbc546d3875a25e2a69f@haiku-os.org> References: <049.bcc3d626f305bbc546d3875a25e2a69f@haiku-os.org> Message-ID: <058.5b72005ac566d31f6306bc278cd25b6b@haiku-os.org> #3418: media_server crashes at startup with rev291524 ----------------------------------+----------------------------------------- Reporter: the ringmaster | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by leavengood): On second thought, it seems this problem was probably due to my not completely deleting all old files before rebuilding ("jam clean" did not do the job.) So ignore my previous comment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 05:53:06 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 12 Jul 2009 03:53:06 -0000 Subject: [Haiku-bugs] [Haiku] #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled In-Reply-To: <044.188d895a987b0891b018b8f7673c6721@haiku-os.org> References: <044.188d895a987b0891b018b8f7673c6721@haiku-os.org> Message-ID: <053.da7f10e7849c06bb2cd871d08f0bfcab@haiku-os.org> #4092: UserlandFS not buildable with block cache / block cache transaction tracing enabled ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31525 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 06:46:29 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 12 Jul 2009 04:46:29 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.9cb842e322d6a69d1f725a28c23c22fd@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:7 bonefish]: > The dependencies look OK for both cases, so I'd consider this a jam bug. Some revisions ago I couldn't trigger this either, remember? Those are always timing-dependent, but I manage to reproduce this quite easily now. I just have to call a parallel jam and do a "make -j8 index" on /usr/ports to generate a lot of disk activity. But I don't think this is a jam bug at all. I don't really understand how Jam generates its dependency trees, but after some investigation I found that parse.h is generated by the Yacc1 rule being applied to parse.y: {{{ Yacc1 /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.c /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.h }}} which expands to: {{{ bison -d -o /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.c /usr/home/andre/devel/Haiku/trunk/src/bin/bash/parse.y [ -f /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.c.h ] && mv /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.c.h /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/common/bin/bash/parse.h || true }}} but nowhere is parse.h declared dependent on parse.y. So it's very probable Jam simply launched the shell that compiles print_cmd.c independently. Does this make sense to you? Replying to [comment:7 bonefish]: > Under Haiku I couldn't reproduce it (two cores only, though). Am I assuming correctly that your build platform is FreeBSD? Would be interesting, if this can be reproduced on Linux, too. Yes, my build platform is FreeBSD, and I have no space left to install Linux, unless I nuke the Haiku partition. Or if I could install the Linux userland under the FreeBSD Linuxolator. Anyway, if my suspicion above turns out correct, this is a mute point and I can happily keep my HD Linux-free. :D (it was a profound dislike for the mess that are the various Linux distros that I got involved with BeOS to begin with!) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 08:30:03 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 12 Jul 2009 06:30:03 -0000 Subject: [Haiku-bugs] [Haiku] #3732: Renaming files: selection without suffix In-Reply-To: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> References: <044.16762095da9d055ecbc3f8db41b6492d@haiku-os.org> Message-ID: <053.5e835c88f2127414e5ba2dfe5649e312@haiku-os.org> #3732: Renaming files: selection without suffix ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by humdinger): @fano: I'm not sure I understand you 100%. But you can't just always exclude the last string after a "." when a filename is selected for renaming. Most Haiku-originating files don't have a suffix. Doing that would only select "the" of a file "the.dot". Nope, Tracker would have to check the filetype, get the possible suffixes for it, and compare them to the filename. @mmadia: While I would be terribly happy to have a working PecoRename for Haiku, I don't think it would replace Tracker's quick rename function when you deal with a single file. This enhancement would just improve its usability. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 09:21:21 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 07:21:21 -0000 Subject: [Haiku-bugs] [Haiku] #3099: BePDF KDLs on exit In-Reply-To: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> References: <041.580fdd342b20daf90efedf5330e23972@haiku-os.org> Message-ID: <050.436888b6c3cdcf7956a7b4356be6f01c@haiku-os.org> #3099: BePDF KDLs on exit ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: laplace Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3588 ---------------------------+------------------------------------------------ Changes (by modeenf): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:20:15 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:20:15 -0000 Subject: [Haiku-bugs] [Haiku] #2314: [ProcessController] double clicking it will restart Deskbar. In-Reply-To: <040.2c98aa85a09378ba5140be14d3b4c723@haiku-os.org> References: <040.2c98aa85a09378ba5140be14d3b4c723@haiku-os.org> Message-ID: <049.328f8254a5bfcba187c7ed6d48eff5ec@haiku-os.org> #2314: [ProcessController] double clicking it will restart Deskbar. --------------------------+------------------------------------------------- Reporter: diver | Owner: modeenf Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:20:46 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:20:46 -0000 Subject: [Haiku-bugs] [Haiku] #2329: [bootman] starts at one position and then suddenly jumps to another (easy) In-Reply-To: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> References: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> Message-ID: <049.8395398c39e25c1dacd891e56f2407f6@haiku-os.org> #2329: [bootman] starts at one position and then suddenly jumps to another (easy) --------------------------+------------------------------------------------- Reporter: diver | Owner: modeenf Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:21:29 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:21:29 -0000 Subject: [Haiku-bugs] [Haiku] #2830: Change item name "Get Info" In-Reply-To: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> References: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> Message-ID: <053.f776be0292d4eddadef03374687cadac@haiku-os.org> #2830: Change item name "Get Info" ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: modeenf Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by modeenf): * owner: axeld => modeenf * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:21:57 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:21:57 -0000 Subject: [Haiku-bugs] [Haiku] #2937: In Icon-O-Matic at start the drawing zone is not centered. In-Reply-To: <041.9316e7c0fb100a4e8d8bf5c4938284f3@haiku-os.org> References: <041.9316e7c0fb100a4e8d8bf5c4938284f3@haiku-os.org> Message-ID: <050.6ffa84e51e3c5761e40bc7b88c89a8c8@haiku-os.org> #2937: In Icon-O-Matic at start the drawing zone is not centered. ---------------------------------------+------------------------------------ Reporter: miqlas | Owner: modeenf Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------------------+------------------------------------ Changes (by modeenf): * owner: stippi => modeenf * status: new => assigned Old description: > In Icon-O-Matic at start the drawing zone is not centered. New description: In Icon-O-Matic at start the drawing zone is not centered. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:22:58 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:22:58 -0000 Subject: [Haiku-bugs] [Haiku] #2970: Adamation personalStudio 1.5 trial don't work on Haiku 28283 In-Reply-To: <041.8668950d60707410349c6c93761e1a82@haiku-os.org> References: <041.8668950d60707410349c6c93761e1a82@haiku-os.org> Message-ID: <050.72a10dd4251bd99a020b348bbcb7711f@haiku-os.org> #2970: Adamation personalStudio 1.5 trial don't work on Haiku 28283 --------------------------+------------------------------------------------- Reporter: miqlas | Owner: modeenf Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:23:44 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:23:44 -0000 Subject: [Haiku-bugs] [Haiku] #2985: ProcessController preselected button In-Reply-To: <041.34e9686bb951caad7a7568c15b698828@haiku-os.org> References: <041.34e9686bb951caad7a7568c15b698828@haiku-os.org> Message-ID: <050.e509599de65574d13e233fe2bc3384f5@haiku-os.org> #2985: ProcessController preselected button --------------------------+------------------------------------------------- Reporter: miqlas | Owner: modeenf Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:24:19 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:24:19 -0000 Subject: [Haiku-bugs] [Haiku] #4043: [mouse preferences] Focus follow mouse dialog too short In-Reply-To: <039.1bb8b624bb623fb347ae6c1ab44ce846@haiku-os.org> References: <039.1bb8b624bb623fb347ae6c1ab44ce846@haiku-os.org> Message-ID: <048.05601df694fa9d502fa4cff83445f269@haiku-os.org> #4043: [mouse preferences] Focus follow mouse dialog too short -------------------------------+-------------------------------------------- Reporter: togs | Owner: modeenf Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by modeenf): * owner: axeld => modeenf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:30:51 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:30:51 -0000 Subject: [Haiku-bugs] [Haiku] #3320: [CodyCam] display alert in a video view In-Reply-To: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> References: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> Message-ID: <049.affd9d570f5606bd73ff49c0edae2302@haiku-os.org> #3320: [CodyCam] display alert in a video view -----------------------------------+---------------------------------------- Reporter: diver | Owner: modeenf Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CodyCam | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by modeenf): * owner: mmu_man => modeenf -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 11:40:57 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 09:40:57 -0000 Subject: [Haiku-bugs] [Haiku] #2329: [bootman] starts at one position and then suddenly jumps to another (easy) In-Reply-To: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> References: <040.1fde538fbbd8afa61a1a87d59f256131@haiku-os.org> Message-ID: <049.729ac3cb69537d8e53f381ccc74b587b@haiku-os.org> #2329: [bootman] starts at one position and then suddenly jumps to another (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: modeenf Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by modeenf): * status: assigned => closed * resolution: => invalid Comment: Tested in r31406. Can't reproduce this one now. Closing it. As I don't know if it was fixed in bootman or fixed by "accident" some where else, I'll set it to invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 15:50:27 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 13:50:27 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 In-Reply-To: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> References: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> Message-ID: <047.08f85ba484782151363e16327f24df83@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 ---------------------------+------------------------------------------------ Reporter: oco | Owner: modeenf Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by modeenf): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31240 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 16:53:22 2009 From: trac at haiku-os.org (stippi) Date: Sun, 12 Jul 2009 14:53:22 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 In-Reply-To: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> References: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> Message-ID: <047.dbadf1d613f959ef393db454d1d43f44@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 ---------------------------+------------------------------------------------ Reporter: oco | Owner: modeenf Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Just a note... I don't know if you used Olivier's patch or not, but if you did, please make sure to always mention the patch supplier in the commit message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 17:15:52 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 12 Jul 2009 15:15:52 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.5e5c15b6db079532dd683f6705485870@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Replying to [comment:8 meianoite]: > Replying to [comment:7 bonefish]: > > The dependencies look OK for both cases, so I'd consider this a jam bug. > > Some revisions ago I couldn't trigger this either, remember? Those are always timing-dependent, but I manage to reproduce this quite easily now. I just have to call a parallel jam and do a "make -j8 index" on /usr/ports to generate a lot of disk activity. But I don't think this is a jam bug at all. I don't really understand how Jam generates its dependency trees, but after some investigation I found that parse.h is generated by the Yacc1 rule being applied to parse.y: [...] > but nowhere is parse.h declared dependent on parse.y. You are mistaken. The Yacc rule establishes that dependency. > So it's very probable Jam simply launched the shell that compiles print_cmd.c independently. Does this make sense to you? Nope. As I wrote, I checked the dependencies jam knows of ("jam -dd") and they look OK. If jam nevertheless executes the actions for dependent targets out of order respectively starts the actions for the dependent target before those for the dependency have finished, it's obviously a bug in jam. Or in the job management functionality it uses (mainly wait()). > Replying to [comment:7 bonefish]: > > Under Haiku I couldn't reproduce it (two cores only, though). Am I assuming correctly that your build platform is FreeBSD? Would be interesting, if this can be reproduced on Linux, too. I tried a few runs under Linux (still with 2 cores only) and bash was always built successfully. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 18:27:17 2009 From: trac at haiku-os.org (modeenf) Date: Sun, 12 Jul 2009 16:27:17 -0000 Subject: [Haiku-bugs] [Haiku] #2547: A little patch to compile BeServed under Visual Studio 2008 In-Reply-To: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> References: <038.05817936aa53894970ac3420639ae9ba@haiku-os.org> Message-ID: <047.4d91af77074bdd10fb35132f15a03589@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 ---------------------------+------------------------------------------------ Reporter: oco | Owner: modeenf Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by modeenf): I usually do but now I wasn't as clear as should have. Sorry Olivier -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 21:18:04 2009 From: trac at haiku-os.org (aldeck) Date: Sun, 12 Jul 2009 19:18:04 -0000 Subject: [Haiku-bugs] [Haiku] #3929: Strange desktop icon behavior In-Reply-To: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> References: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> Message-ID: <051.553a3b29158c53478ea09cb9d8fe6d86@haiku-os.org> #3929: Strange desktop icon behavior ----------------------------------+----------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by aldeck): I've seen this one quite often in the past two weeks while working on Tracker (ie: starting/quiting (ok... crashing) tracker a lot). I assumed it was something with my current changes and hadn't noticed this ticket. But i'm pretty sure it's a recent bug, i'll have a look next time i see it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 22:07:39 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 12 Jul 2009 20:07:39 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.88abe1498fcd9fc5e286a2efc73e487e@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:9 bonefish]: > I tried a few runs under Linux (still with 2 cores only) and bash was always built successfully. I can only make it happen once or twice out of 10 attempts if I build bash in isolation. Which again confirms that this is timing-based. But I'm yet to have it succeed if I build the whole of Haiku the way I've described. I've determined that producing the background disk noise isn't even necessary, but I don't know if that is related to me upping things a notch to j16: {{{ rm -rf objects/ build_packages/ tmp/ build/*cache ; jam -aqj16 @all |& tee j16.log }}} The redirection is tcsh syntax. Building with an added -dd argument indeed shows the correct dependency chaining, but it fails nonetheless. And generates a huge log that compresses to over 700k with bzip2 --best, 760k with 7z "ultra" settings. Now, for an interesting tidbit: I'm able to trigger at least the builtins.c error even using cpuset to limit the CPUs jam was allowed to use to 2, which was confirmed by monitoring with htop. But for this to succeed (er, fail) I have to produce the disk activity with "make -j8 index" on /usr/ports. {{{ > rm -rf objects/ build_packages/ tmp/ build/*cache ; sudo cpuset -c -l 0-1 -- sudo -u andre jam -aqj16 @all |& tee j16-2.log }}} {{{ > egrep "(failed|skipped)" j16-2.log ...failed Cc /usr/home/andre/devel/Haiku/trunk/generated.gcc2/objects/haiku/x86/release/bin/bash/builtins/builtins.o ... ...skipped libbuiltins.a for lack of libbuiltins.a(builtins.o)... ...skipped bash for lack of libbuiltins.a... ...failed updating 1 target(s)... ...skipped 2 target(s)... }}} Jam bug or build system bug, it's still not a desirable situation, specially with Haiku build clusters in the horizon ;) I understand that you have a limitation on making it happen on a dual-core machine, and we're getting nowhere until you can put your finger straight on the problem. Would you like to try debugging it straight on my machine? Send a public RSA key my way and I'll create a user for you pronto. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 22:26:05 2009 From: trac at haiku-os.org (Luposian) Date: Sun, 12 Jul 2009 20:26:05 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.f8b843080747ea1bd524e35e2fb7f77c@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Luposian): Replying to [comment:10 umccullough]: > Interestingly, force_ws is set to false in the settings file in subversion, so you must have manually edited to make it work anyway... > > In any case, as you can see from the tickets already here: > > http://dev.haiku-os.org/search?q=force_ws&noquickjump=1&ticket=on > > The use of that setting is sometimes problematic as well. Rudolf is already adding EDID support to the driver to have it detect the resolutions automatically (perhaps the EDID info is what you're seeing the syslog when the vesa driver queries the card for monitor resolutions). > > In any case, perhaps attaching a syslog to this ticket would even help more, since you seem to already have viewed it and determined that there is useful information there. I also tried turning everything off (using the # symbol) in the settings file and activating (removing the #) each one and then rebooting. Nothing, but NOTHING made any difference in finding my monitor's native resolution, until I activated "force_ws" and made it true. Then Haiku found my monitor's native resolution. Funny thing is... why does Screen create a VESA file with the 1440x900 at 60Hz (native resolution), when I'm supposedly not using Vesa mode? It creates this file, whether or not I have "nvidia.settings" installed/enabled or not. It was said by "anevilyak", that if I can change refresh rates (which I can, even from the very beginning), then I am supposedly NOT in Vesa mode. Yet, Screen creates a file called "Vesa" with the resolution/refresh rate in it. This doesn't make any sense! Are you suggesting that I should include a 2nd Syslog file, in addition to the one I already put in this ticket? I can do that, if you think it will help, but I doubt it will say anything different... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 23:34:26 2009 From: trac at haiku-os.org (stippi) Date: Sun, 12 Jul 2009 21:34:26 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.85327f67d5ae4c5fedd12bd62aff27e3@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): It didn't make sense to you maybe before you read what I am going to write next... :-) The vesa settings file is indeed created by the Screen preflet, which is for the purpose to get your Monitor into the correct resolution as early as possible, which is during boot, when the Haiku boot icons are displayed, until the kernel has detected your file system and loaded drivers. During this time, Haiku (and any other operating system) use the VESA mode. The point is that the resolution switch happens as early as possible, so it looks better than, say, Windows, which displays the logo in one resolution and then switches to a different resolution when the Desktop shows. It's for making a smoother impression during booting. That's all. If you can pick a screen refresh rate, then yes, you are using the nvidea driver, not the vesa driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 12 23:57:27 2009 From: trac at haiku-os.org (korli) Date: Sun, 12 Jul 2009 21:57:27 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.b8ab6e642a2e316af76dd1658bf6a60b@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31532. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 00:05:53 2009 From: trac at haiku-os.org (korli) Date: Sun, 12 Jul 2009 22:05:53 -0000 Subject: [Haiku-bugs] [Haiku] #4076: [patch] Change tab order in Expander-window In-Reply-To: <041.13afc2971ded0fdb81003e8cc83a2bf7@haiku-os.org> References: <041.13afc2971ded0fdb81003e8cc83a2bf7@haiku-os.org> Message-ID: <050.a1b859eb776c9ac38d6c568b729d8957@haiku-os.org> #4076: [patch] Change tab order in Expander-window ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Expander | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r31533. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 00:16:09 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 12 Jul 2009 22:16:09 -0000 Subject: [Haiku-bugs] [Haiku] #4093: Stack and Tile group is not all grouped to same layer Message-ID: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> #4093: Stack and Tile group is not all grouped to same layer -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When grouping windows with the stack and tile patch, not all windows in the group are set to the same level. If another window is dragged over the group some of the window tabs may go above the window while others may be hidden behind it. I would expect then to all be on the same layer (ie all above or all below the new window). See attached screen in case I'm not explaining this right. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 00:16:30 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 12 Jul 2009 22:16:30 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.789d6426054e9e5acee2a24c94395c7b@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Thanks for the offer, but this problem seem to be on jam's side and, since I plan to rewrite jam in the not so distant future, I'm not particularly inclined to debug it. If you're interested in looking into it, execunix.c is where the job execution happens and where I would start to track the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 01:01:05 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 12 Jul 2009 23:01:05 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.2cfdbc46792168bc3fc501d7086e1917@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by meianoite): Replying to [comment:11 bonefish]: > Thanks for the offer, but this problem seem to be on jam's side and, since I plan to rewrite jam in the not so distant future, I'm not particularly inclined to debug it. Sounds interesting. What are your plans? Reimplement it from scratch while keeping the Jamfile syntax? Using C++ or some other language more amenable to text parsing? > If you're interested in looking into it, execunix.c is where the job execution happens and where I would start to track the problem. Thanks, but I think I'll pass :P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 02:36:05 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 13 Jul 2009 00:36:05 -0000 Subject: [Haiku-bugs] [Haiku] #4094: FilePanel: File Name is Selected Back to Front Message-ID: <043.e0043a4b76d8ed55b1f0e6a77ad8a722@haiku-os.org> #4094: FilePanel: File Name is Selected Back to Front ------------------------------+--------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- The text in the file name text field of file panel is selected back to front when selecting an entry. I.e the anchor is at the end of the text, the caret at the start, so that when so that characters at the end cannot be deselected via Shift-Left, only characters at the beginning can be deselected via Shift-Right. This is inconsistent with other text fields whose text is auto-selected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 08:43:35 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 13 Jul 2009 06:43:35 -0000 Subject: [Haiku-bugs] [Haiku] #4072: HDA audio sounds worse In-Reply-To: <042.4089cdf4258cd6641a6941a4b554f705@haiku-os.org> References: <042.4089cdf4258cd6641a6941a4b554f705@haiku-os.org> Message-ID: <051.f3a0c0c76a87b0e1b36943a5fa407001@haiku-os.org> #4072: HDA audio sounds worse -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by jahaiku): I have retested with an AcerAspireOne and there the sound is OK.[[BR]] So it must be related to the HDA-Chip used in the EeePC. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 09:01:56 2009 From: trac at haiku-os.org (korli) Date: Mon, 13 Jul 2009 07:01:56 -0000 Subject: [Haiku-bugs] [Haiku] #2323: [Media] volume control should react on scrolling up/down events (easy) In-Reply-To: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> References: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> Message-ID: <049.7a8c87ad35329f0ceae25482bc756da2@haiku-os.org> #2323: [Media] volume control should react on scrolling up/down events (easy) --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by korli): I tested yesterday and it was working nicely. Could you check on your side please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 11:02:56 2009 From: trac at haiku-os.org (axeld) Date: Mon, 13 Jul 2009 09:02:56 -0000 Subject: [Haiku-bugs] [Haiku] #2830: Change item name "Get Info" In-Reply-To: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> References: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> Message-ID: <053.ef10764d3499fcbfbe97ead119e59ec2@haiku-os.org> #2830: Change item name "Get Info" ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: modeenf Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by axeld): It's actually a stupid idea to put it at the end of the (relatively long) menu, as this makes a very long for one of the items you use more often than others. At least I'm always annoyed on other platforms, and I wouldn't like to see Haiku copying bad behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 11:19:21 2009 From: trac at haiku-os.org (modeenf) Date: Mon, 13 Jul 2009 09:19:21 -0000 Subject: [Haiku-bugs] [Haiku] #2830: Change item name "Get Info" In-Reply-To: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> References: <044.b4713d81442793bfcc23c7da4eb51285@haiku-os.org> Message-ID: <053.6f6f4c435e4fdd48f14887817e2f9596@haiku-os.org> #2830: Change item name "Get Info" ----------------------------------+----------------------------------------- Reporter: humdinger | Owner: modeenf Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by modeenf): I'm for removing "Get" but no more now until we have some sort of GUI guidelines and that probably after R1. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 12:12:28 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 13 Jul 2009 10:12:28 -0000 Subject: [Haiku-bugs] [Haiku] #3142: cvs program malfunction In-Reply-To: <042.0aa59fe80615cb0dbacd9ada6ce1819f@haiku-os.org> References: <042.0aa59fe80615cb0dbacd9ada6ce1819f@haiku-os.org> Message-ID: <051.057ba4d0dc46cd83f0a46afb624bf28a@haiku-os.org> #3142: cvs program malfunction -----------------------+---------------------------------------------------- Reporter: bhaible | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): This ticket can be closed now as the wchar fix is in trunk and the cvs optional package has been updated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 12:25:09 2009 From: trac at haiku-os.org (diver) Date: Mon, 13 Jul 2009 10:25:09 -0000 Subject: [Haiku-bugs] [Haiku] #2323: [Media] volume control should react on scrolling up/down events (easy) In-Reply-To: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> References: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> Message-ID: <049.c40d7eae16134acdb0f1d981113c95b3@haiku-os.org> #2323: [Media] volume control should react on scrolling up/down events (easy) --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by diver): If I drop volume replicant to desktop and scroll over it - it works. But scrolling over volume icon in Deskbar doesn't work. Tested in vbox with r31534. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 12:26:43 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 13 Jul 2009 10:26:43 -0000 Subject: [Haiku-bugs] [Haiku] #2041: In some cases, __mbrtowc can enter in an infinite loop In-Reply-To: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> References: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> Message-ID: <047.cb44e0b599b5ebd1866d8265117885ef@haiku-os.org> #2041: In some cases, __mbrtowc can enter in an infinite loop -------------------------------+-------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): This ticket can be closed now that the wchar32 fix has been moved to trunk. The attached test case gives this output: {{{ ~> mbrtowc_test 4, 4 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 mjw... in while 1 9 ~> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 13:39:26 2009 From: trac at haiku-os.org (zooey) Date: Mon, 13 Jul 2009 11:39:26 -0000 Subject: [Haiku-bugs] [Haiku] #2041: In some cases, __mbrtowc can enter in an infinite loop In-Reply-To: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> References: <038.70db48c479fe886ace2210d9e551705c@haiku-os.org> Message-ID: <047.4c51e39c48942a475853c4135ac7f669@haiku-os.org> #2041: In some cases, __mbrtowc can enter in an infinite loop --------------------------------+------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => fixed Comment: closing, since the problem has been fixed by the wchar_t changes. oco and scottmc: thanks for the feedback! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 19:28:10 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 13 Jul 2009 17:28:10 -0000 Subject: [Haiku-bugs] [Haiku] #215: Problem with special characters In-Reply-To: <052.6fd4f08dc6b441c4b11934f69b5de084@haiku-os.org> References: <052.6fd4f08dc6b441c4b11934f69b5de084@haiku-os.org> Message-ID: <061.a4c712cb7007c483f0acb43d347f6134@haiku-os.org> #215: Problem with special characters ------------------------------------+--------------------------------------- Reporter: fekdahl@? | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: 1855 Platform: All | Blocking: 3047 ------------------------------------+--------------------------------------- Comment(by scottmc): Can someone recheck this one now that wchar fix is in place? Does it have any effect? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 20:07:30 2009 From: trac at haiku-os.org (ekdahl) Date: Mon, 13 Jul 2009 18:07:30 -0000 Subject: [Haiku-bugs] [Haiku] #215: Problem with special characters In-Reply-To: <052.6fd4f08dc6b441c4b11934f69b5de084@haiku-os.org> References: <052.6fd4f08dc6b441c4b11934f69b5de084@haiku-os.org> Message-ID: <061.1ceae5b178ff5ac77472bd2fc668684a@haiku-os.org> #215: Problem with special characters ------------------------------------+--------------------------------------- Reporter: fekdahl@? | Owner: jackburton Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: 1855 Platform: All | Blocking: 3047 ------------------------------------+--------------------------------------- Comment(by ekdahl): I checked right after the merging with trunk, and the problem is still there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 21:05:34 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 13 Jul 2009 19:05:34 -0000 Subject: [Haiku-bugs] [Haiku] #4094: FilePanel: File Name is Selected Back to Front In-Reply-To: <043.e0043a4b76d8ed55b1f0e6a77ad8a722@haiku-os.org> References: <043.e0043a4b76d8ed55b1f0e6a77ad8a722@haiku-os.org> Message-ID: <052.78e592c3bfd5472a6a21a7a4ac5f9cdc@haiku-os.org> #4094: FilePanel: File Name is Selected Back to Front ------------------------------+--------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by bonefish): Renaming entries in Tracker (in both icon and list mode) works the same, which is equally annoying. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 21:08:34 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 13 Jul 2009 19:08:34 -0000 Subject: [Haiku-bugs] [Haiku] #4094: FilePanel: File Name is Selected Back to Front In-Reply-To: <043.e0043a4b76d8ed55b1f0e6a77ad8a722@haiku-os.org> References: <043.e0043a4b76d8ed55b1f0e6a77ad8a722@haiku-os.org> Message-ID: <052.cf047a89a6cae53301b07b45b32c0bdc@haiku-os.org> #4094: FilePanel: File Name is Selected Back to Front ----------------------------------+----------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by anevilyak): * component: Kits/Storage Kit => Applications/Tracker Comment: most likely in BPoseView then. Switching component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 22:06:47 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 13 Jul 2009 20:06:47 -0000 Subject: [Haiku-bugs] [Haiku] #2137: BeScreenCapture program is not functional In-Reply-To: <043.06465f14b94fce6d5a533c780ac357b2@haiku-os.org> References: <043.06465f14b94fce6d5a533c780ac357b2@haiku-os.org> Message-ID: <052.e615eafffbee64c4d7a1232ba6120a75@haiku-os.org> #2137: BeScreenCapture program is not functional ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 1043 Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => duplicate * blockedby: => 1043 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 22:49:36 2009 From: trac at haiku-os.org (modeenf) Date: Mon, 13 Jul 2009 20:49:36 -0000 Subject: [Haiku-bugs] [Haiku] #3320: [CodyCam] display alert in a video view In-Reply-To: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> References: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> Message-ID: <049.ea9a7a6581b6c506dc693f4c73047901@haiku-os.org> #3320: [CodyCam] display alert in a video view -----------------------------------+---------------------------------------- Reporter: diver | Owner: modeenf Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CodyCam | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by modeenf): Apparently you already don't need to have a webcam to start playing with CodyCam, after the message you can play with CodyCam. There are some text at the bottom that says "waiting.." I would like to close this one any rejections? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 22:53:52 2009 From: trac at haiku-os.org (stippi) Date: Mon, 13 Jul 2009 20:53:52 -0000 Subject: [Haiku-bugs] [Haiku] #1307: [MediaPlayer] jumping on screen In-Reply-To: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> References: <040.d78f5030e9cf4e660b14da1d3ff4ab0d@haiku-os.org> Message-ID: <049.006348e983a6b318e2583b3f272ac01d@haiku-os.org> #1307: [MediaPlayer] jumping on screen ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: I thought about this some the other day, and I realized what actually caused the problem. The window frame size/position used to be adjusted in MoveBy() and ResizeBy() - sending the app_server relative values. If the real window position/size inside the app_server got seriously out of sync with the client side, because messages piled up, it would cause the behavior described in this ticket. Some time ago (I think) Axel changed that so the commands to the app_server are based on the absolute values (moved the implementation to MoveTo() and ResizeTo()). That made it more robust and actually also solved this ticket. What still happens is that when the MediaPlayer window is very large, you can see it lagging behind, because mouse messages pile up as before. However, no jumping around on the screen anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 23:01:14 2009 From: trac at haiku-os.org (stippi) Date: Mon, 13 Jul 2009 21:01:14 -0000 Subject: [Haiku-bugs] [Haiku] #3628: MediaPlayer : Alt+M, Weird mouse clicks=Alt+B, Alt+C In-Reply-To: <041.0ac4840cf8ec7e7434084c5a1537377a@haiku-os.org> References: <041.0ac4840cf8ec7e7434084c5a1537377a@haiku-os.org> Message-ID: <050.fff3a3ac65c1d02ea34701872cc17b9e@haiku-os.org> #3628: MediaPlayer : Alt+M, Weird mouse clicks=Alt+B,Alt+C ---------------------------------------+------------------------------------ Reporter: mmadia | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: This one happened for other reasons. The VideoView would reset the mouse position, to prevent the screen saver to go off. There were two bugs with that, which I fixed some time ago. First, it would set the mouse even if a button was pressed. Second, it would use it's own coordinate system instead of the screen space, which then caused the mouse to move. Because of the way how the context menu works in MediaPlayer, this could end up selecting a menu item in the context menu, but so quickly that one never saw it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 13 23:07:06 2009 From: trac at haiku-os.org (stippi) Date: Mon, 13 Jul 2009 21:07:06 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.5b7b10ad805fb389a0a535f635d29990@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: assigned => closed * version: => R1 development * resolution: => fixed Comment: I am with Michael that the jumping off screen was actually a dup of #1307. That being said, I think the jumping on screen in WindowActivated() can be a little irritating. I may have a look. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 00:18:31 2009 From: trac at haiku-os.org (korli) Date: Mon, 13 Jul 2009 22:18:31 -0000 Subject: [Haiku-bugs] [Haiku] #1552: Mesa bug when starting Blender 2.1.1 In-Reply-To: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> References: <041.72efe2da2bc0d857a4152fbe2e39a798@haiku-os.org> Message-ID: <050.fbe0fbc353f151004bb6fc8588011b31@haiku-os.org> #1552: Mesa bug when starting Blender 2.1.1 -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/OpenGL Kit | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by korli): blender2.11-beos-5.0-i386.zip seems to work a bit now. Could still be buggy though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 06:39:25 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 14 Jul 2009 04:39:25 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.1fd7cdbb7e35df87c633f0c927fc671e@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by leavengood): Replying to [comment:13 stippi]: > I am with Michael that the jumping off screen was actually a dup of #1307. That being said, I think the jumping on screen in WindowActivated() can be a little irritating. I may have a look. Since I originally added it, I have taken that code out as of r31551. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 08:46:00 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 14 Jul 2009 06:46:00 -0000 Subject: [Haiku-bugs] [Haiku] #4095: Twitcher window can be hidden at times Message-ID: <045.d492e3ccac88f944006bbe01c8de08b7@haiku-os.org> #4095: Twitcher window can be hidden at times ----------------------------------+----------------------------------------- Reporter: leavengood | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I tried to fix this by setting the feel of the TSwitcherWindow class to B_FLOATING_ALL_WINDOW_FEEL, but that did not fix the problem. To reproduce, simply move any app window toward the center of the screen, move over to the Deskbar, open it's menu, then Ctrl-Tab to the other app (leaving the Deskbar menu open.) Then press and hold Ctrl-Tab and you will see that the Twitcher window is hidden by the app window. See attached screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 08:55:17 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 14 Jul 2009 06:55:17 -0000 Subject: [Haiku-bugs] [Haiku] #4095: Twitcher window can be hidden at times In-Reply-To: <045.d492e3ccac88f944006bbe01c8de08b7@haiku-os.org> References: <045.d492e3ccac88f944006bbe01c8de08b7@haiku-os.org> Message-ID: <054.e4fcc7a4bfd6ae1c6a493ab058c2287d@haiku-os.org> #4095: Twitcher window can be hidden at times ----------------------------------+----------------------------------------- Reporter: leavengood | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by leavengood): Trac didn't show the screenshot without the png extension, hence the two attachments. For whatever reason I cannot see how (or don't have the permission) to delete the bad one... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 11:15:44 2009 From: trac at haiku-os.org (axeld) Date: Tue, 14 Jul 2009 09:15:44 -0000 Subject: [Haiku-bugs] [Haiku] #4095: Twitcher window can be hidden at times In-Reply-To: <045.d492e3ccac88f944006bbe01c8de08b7@haiku-os.org> References: <045.d492e3ccac88f944006bbe01c8de08b7@haiku-os.org> Message-ID: <054.6ba2ca0ababc9a9e983c006cb7b7da8f@haiku-os.org> #4095: Twitcher window can be hidden at times --------------------------------+------------------------------------------- Reporter: leavengood | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * component: Applications/Deskbar => Servers/app_server Comment: You can delete attachments while showing them, ie. there is a "Delete Attachment" button at the end of the attachment view. I deleted the attachment now, at least :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 11:17:09 2009 From: trac at haiku-os.org (axeld) Date: Tue, 14 Jul 2009 09:17:09 -0000 Subject: [Haiku-bugs] [Haiku] #4093: Stack and Tile group is not all grouped to same layer In-Reply-To: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> References: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> Message-ID: <051.7f916d4da4b79900bd8b72ca3a602952@haiku-os.org> #4093: Stack and Tile group is not all grouped to same layer --------------------------------+------------------------------------------- Reporter: scottmc | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: axeld => nobody * component: - General => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 11:25:34 2009 From: trac at haiku-os.org (stippi) Date: Tue, 14 Jul 2009 09:25:34 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.e3bb92871a4c12731398b9b288456a27@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by stippi): Something similar could still be useful. At least I would want the MediaPlayer to shrink to fit the screen if the video is very large. For example, my vacation clips are 1920x1080 and my screen is 1920x1200, and then some of MediaPlayer window is out of bounds... with your code in place, it would at least center itself. :-) But what probably doesn't make sense anymore is the repositioning on activation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 12:10:55 2009 From: trac at haiku-os.org (axeld) Date: Tue, 14 Jul 2009 10:10:55 -0000 Subject: [Haiku-bugs] [Haiku] #4093: Stack and Tile group is not all grouped to same layer In-Reply-To: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> References: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> Message-ID: <051.37adb1162b49948fced0039a524239bd@haiku-os.org> #4093: Stack and Tile group is not all grouped to same layer --------------------------------+------------------------------------------- Reporter: scottmc | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): I'm not sure it's a good idea to put error reports to externally maintained patches here; I'm inclined to close this as invalid. Other opinions? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 15:56:50 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 14 Jul 2009 13:56:50 -0000 Subject: [Haiku-bugs] [Haiku] #4096: Artwork for Additional Backgrounds Message-ID: <041.e5df55c0a00acae211a3446506f8c8f6@haiku-os.org> #4096: Artwork for Additional Backgrounds -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- These are all variations of 'HAIKU logo - welcome'. The wonderbrush file includes all of the varied backgrounds as additional layers. For convenience, see aggregate_view.png, which is a screenshot of the variations. All files are attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 16:15:16 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 14 Jul 2009 14:15:16 -0000 Subject: [Haiku-bugs] [Haiku] #4097: Haiku logo: Inconsistencies with shading. Message-ID: <041.378115a6f13b6c130d69fea82bf9fbba@haiku-os.org> #4097: Haiku logo: Inconsistencies with shading. -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- In the artwork folder, some verisons of the Haiku logo have different locations for the shading on the green leaf. Shading on bottom: {{{ HAIKU alpha logo - white on blue - big HAIKU logo - black on white - tiny.png HAIKU logo - website - everything HAIKU logo - website - logo HAIKU logo - website - navigaion HAIKU logo - white on blue - big HAIKU logo - white on blue - big.png HAIKU logo - white on blue - medium HAIKU logo - white on blue - medium.png HAIKU logo - white on blue - normal HAIKU logo - white on blue - normal.png HAIKU logo - white on blue - tiny HAIKU logo - white on blue - tiny.png HAIKU logo - white on transparent - big.png HAIKU logo - white on transparent - small.png HAIKU logo - white on transparent - tiny.png }}} Shading on top: {{{ HAIKU logo - black on transparent - big.png HAIKU logo - black on transparent - tiny.png HAIKU logo - black on white - big HAIKU logo - black on white - big.png HAIKU logo - black on white - normal HAIKU logo - black on white - normal.png HAIKU logo - black on white - tiny HAIKU logo - website HAIKU logo - website.png HAIKU logo - welcome }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 16:33:54 2009 From: trac at haiku-os.org (stippi) Date: Tue, 14 Jul 2009 14:33:54 -0000 Subject: [Haiku-bugs] [Haiku] #4097: Haiku logo: Inconsistencies with shading. In-Reply-To: <041.378115a6f13b6c130d69fea82bf9fbba@haiku-os.org> References: <041.378115a6f13b6c130d69fea82bf9fbba@haiku-os.org> Message-ID: <050.faf742e0f3b92cb2023473ac97bdfaf8@haiku-os.org> #4097: Haiku logo: Inconsistencies with shading. ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: This was done on purpose to give better contrast for the dark on light versions. The shadow of the leaf will make sure that there is contrast at the bottom, while the darker gradient at the top gives more contrast against the light background. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 19:30:20 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 14 Jul 2009 17:30:20 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.9758b2a7d623d8258c8b92b7d7a9407b@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by leavengood): Well feel free to resurrect my code in a more appropiate place, if you think it is useful. Like I said in the commit I still think that code is nice looking :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 19:31:07 2009 From: trac at haiku-os.org (korli) Date: Tue, 14 Jul 2009 17:31:07 -0000 Subject: [Haiku-bugs] [Haiku] #3360: [InstallCD] Should show the shutting-down dialog when restarting In-Reply-To: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> References: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> Message-ID: <051.bb7c0c1faca1babf9ae0bdc59e54f12a@haiku-os.org> #3360: [InstallCD] Should show the shutting-down dialog when restarting ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by korli): The boot cd script ends with the following command: /bin/shutdown -r -q -d 10 It directly asks the kernel to shutdown instead of using the registrar. As only the registrar shows the shutting down dialog, no dialog is shown when restarting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 21:02:17 2009 From: trac at haiku-os.org (modeenf) Date: Tue, 14 Jul 2009 19:02:17 -0000 Subject: [Haiku-bugs] [Haiku] #2314: [ProcessController] double clicking it will restart Deskbar. In-Reply-To: <040.2c98aa85a09378ba5140be14d3b4c723@haiku-os.org> References: <040.2c98aa85a09378ba5140be14d3b4c723@haiku-os.org> Message-ID: <049.2154e91a0d9c76ab6ae6823495e24815@haiku-os.org> #2314: [ProcessController] double clicking it will restart Deskbar. ---------------------------+------------------------------------------------ Reporter: diver | Owner: modeenf Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by modeenf): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31526 , updated in r31566. Will now not install if already in deskbar, also telling you that this are the case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 22:49:39 2009 From: trac at haiku-os.org (stippi) Date: Tue, 14 Jul 2009 20:49:39 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.6c5cac4dc351cd2b1fc16a3a6be68ffb@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by stippi): I came up with something... the screen frame check is now only done when the current clip changes such that the video size changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 14 22:52:25 2009 From: trac at haiku-os.org (stippi) Date: Tue, 14 Jul 2009 20:52:25 -0000 Subject: [Haiku-bugs] [Haiku] #676: Click ing on video picture and dragging Mediaplayer dissapears off screen In-Reply-To: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> References: <053.a703f724e7fbc0872773522ab0870c4d@haiku-os.org> Message-ID: <062.a1967cd5efbb8052c329039120b77e29@haiku-os.org> #676: Click ing on video picture and dragging Mediaplayer dissapears off screen ---------------------------------------+------------------------------------ Reporter: kutspam@? | Owner: leavengood Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Comment(by stippi): Looking at your patch again, I see that I came up with almost the identical code, but before I run that, I also check if the window is actually larger than the screen in any dimension and scale it down. But... it still means your code lives on. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 03:18:36 2009 From: trac at haiku-os.org (bga) Date: Wed, 15 Jul 2009 01:18:36 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume In-Reply-To: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> References: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> Message-ID: <053.bec328c4162d086b5dd86df7adac9ddd@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume -------------------------------+-------------------------------------------- Reporter: meianoite | Owner: 3dEyes Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): I can confirm this. it seems the entire libntfs is broken as I managed to change the code to make the partitions mountable but, after that, I get no real data from the partitions (not even directory listings). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 05:41:37 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 15 Jul 2009 03:41:37 -0000 Subject: [Haiku-bugs] [Haiku] #2477: Haiku's bootman doesn't show the same partitions as BeOS's In-Reply-To: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> References: <041.d5ac2516d13e6ad022f9af1b024d4727@haiku-os.org> Message-ID: <050.05fccce24727f2d43fd8069c803c4585@haiku-os.org> #2477: Haiku's bootman doesn't show the same partitions as BeOS's --------------------------+------------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by umccullough): * cc: umccullough (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 05:41:46 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 15 Jul 2009 03:41:46 -0000 Subject: [Haiku-bugs] [Haiku] #3443: Bootman should allow users to select which drive to install the MBR to. In-Reply-To: <044.b2ca604868505a8f475cfd1ab4d386f7@haiku-os.org> References: <044.b2ca604868505a8f475cfd1ab4d386f7@haiku-os.org> Message-ID: <053.9bb0c6009f4ba876f854444affd4d65f@haiku-os.org> #3443: Bootman should allow users to select which drive to install the MBR to. --------------------------+------------------------------------------------- Reporter: kallisti5 | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by umccullough): * cc: umccullough (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 05:42:15 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 15 Jul 2009 03:42:15 -0000 Subject: [Haiku-bugs] [Haiku] #3545: bootman : implement multi-drive support In-Reply-To: <041.e4f1cdaf23228d7071eff3ca71d38f00@haiku-os.org> References: <041.e4f1cdaf23228d7071eff3ca71d38f00@haiku-os.org> Message-ID: <050.16d47584c81e0f6d9a28ce26a1f568cf@haiku-os.org> #3545: bootman : implement multi-drive support ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by umccullough): * cc: umccullough (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 06:11:45 2009 From: trac at haiku-os.org (augiedoggie) Date: Wed, 15 Jul 2009 04:11:45 -0000 Subject: [Haiku-bugs] [Haiku] #4098: crashed app consumes all cpu when disable_debugger is used Message-ID: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> #4098: crashed app consumes all cpu when disable_debugger is used ---------------------------+------------------------------------------------ Reporter: augiedoggie | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Starting with r29302 an app which crashes after having called disable_debugger() causes the system to consume all cpu time. The attached sample code is an excerpt from the CMake test suite which expects the app to crash and return control to the parent. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 11:16:35 2009 From: trac at haiku-os.org (axeld) Date: Wed, 15 Jul 2009 09:16:35 -0000 Subject: [Haiku-bugs] [Haiku] #2323: [Media] volume control should react on scrolling up/down events (easy) In-Reply-To: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> References: <040.bbe0bf675907a00c9c078dccc4692d48@haiku-os.org> Message-ID: <049.da3372249c86fd702ecb2a2422a65f74@haiku-os.org> #2323: [Media] volume control should react on scrolling up/down events (easy) --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: It hasn't been the new UI that broke this, but the (recent) fix for bug #4002 in r31322. Also, since something broke this, you should open a bug report for this, and not reopen an old enhancement ticket. Anyway, regression fixed in r31582. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 11:21:23 2009 From: trac at haiku-os.org (axeld) Date: Wed, 15 Jul 2009 09:21:23 -0000 Subject: [Haiku-bugs] [Haiku] #3360: [InstallCD] Should show the shutting-down dialog when restarting In-Reply-To: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> References: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> Message-ID: <051.b4e188e9f57abeba6eaec2fb0d7c4c3f@haiku-os.org> #3360: [InstallCD] Should show the shutting-down dialog when restarting ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by axeld): The -a option would bring up the requester. I don't think a timeout is a good idea for this kind of things, as the user might not have selected Haiku as the primary OS to boot (so when he comes back after starting the install, one cannot tell whether or not the installation succeeded at all). Maybe a installer related message text would be better, too, which could be easily done by using the "alert" tool instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 12:18:26 2009 From: trac at haiku-os.org (korli) Date: Wed, 15 Jul 2009 10:18:26 -0000 Subject: [Haiku-bugs] [Haiku] #3360: [InstallCD] Should show the shutting-down dialog when restarting In-Reply-To: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> References: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> Message-ID: <051.29706fd0b4c54b3823256ecdf5c2fec9@haiku-os.org> #3360: [InstallCD] Should show the shutting-down dialog when restarting ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by korli): The -a option isn't taken into account when using the -q option. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 12:59:04 2009 From: trac at haiku-os.org (axeld) Date: Wed, 15 Jul 2009 10:59:04 -0000 Subject: [Haiku-bugs] [Haiku] #4098: crashed app consumes all cpu when disable_debugger is used In-Reply-To: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> References: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> Message-ID: <055.9dced4f37ca02b83c6aa1d5c3f776b99@haiku-os.org> #4098: crashed app consumes all cpu when disable_debugger is used ---------------------------+------------------------------------------------ Reporter: augiedoggie | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * owner: axeld => bonefish -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 13:04:12 2009 From: trac at haiku-os.org (axeld) Date: Wed, 15 Jul 2009 11:04:12 -0000 Subject: [Haiku-bugs] [Haiku] #3360: [InstallCD] Should show the shutting-down dialog when restarting In-Reply-To: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> References: <042.414a5800061e1ce9cf2227d7ad4c99dc@haiku-os.org> Message-ID: <051.d9e7a163de7895e17c27bc1330170661@haiku-os.org> #3360: [InstallCD] Should show the shutting-down dialog when restarting ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by axeld): Why -q anyway? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 13:37:23 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 15 Jul 2009 11:37:23 -0000 Subject: [Haiku-bugs] [Haiku] #4098: crashed app consumes all cpu when disable_debugger is used In-Reply-To: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> References: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> Message-ID: <055.2b30397e0c1c82d30bdb571d25cac801@haiku-os.org> #4098: crashed app consumes all cpu when disable_debugger is used ----------------------------+----------------------------------------------- Reporter: augiedoggie | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r31584. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 16:18:09 2009 From: trac at haiku-os.org (bbjimmy) Date: Wed, 15 Jul 2009 14:18:09 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file In-Reply-To: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> References: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> Message-ID: <051.f4cba62e71355a995ed5866dc264f12a@haiku-os.org> #3882: system freezes opening file ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by bbjimmy): This can no longer be reproduced. please close the ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 16:35:06 2009 From: trac at haiku-os.org (bga) Date: Wed, 15 Jul 2009 14:35:06 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume In-Reply-To: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> References: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> Message-ID: <053.62b11da82245fd3200757d8b97d3b81d@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume -------------------------------+-------------------------------------------- Reporter: meianoite | Owner: bga Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Changes (by bga): * owner: 3dEyes => bga * status: new => assigned Comment: It seems ntfslib expects wide chars to be 16 bits. Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 16:37:35 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 15 Jul 2009 14:37:35 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume In-Reply-To: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> References: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> Message-ID: <053.735dce3090c9ccf7d56e37374c91d52a@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume -------------------------------+-------------------------------------------- Reporter: meianoite | Owner: bga Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Comment(by anevilyak): That actually makes sense, afaik NTFS encodes entry names using UTF-16 on disk. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 17:04:14 2009 From: trac at haiku-os.org (axeld) Date: Wed, 15 Jul 2009 15:04:14 -0000 Subject: [Haiku-bugs] [Haiku] #3352: getcwd fails python's POSIX test In-Reply-To: <042.28af2510862bec73d1b5367662839476@haiku-os.org> References: <042.28af2510862bec73d1b5367662839476@haiku-os.org> Message-ID: <051.4b6735f4f455c576b69d35b6a4d961a2@haiku-os.org> #3352: getcwd fails python's POSIX test -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by axeld): This is how to run the test (by scottmc on the dev list): If you build Haiku with python added as an optional package you can run this test: cd /boot/common/lib/python2.6/test its called test_posix.py, so just run "python test_posix.py" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 15 17:39:47 2009 From: trac at haiku-os.org (bga) Date: Wed, 15 Jul 2009 15:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #4075: Panic in r31444 when mounting a NTFS volume In-Reply-To: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> References: <044.63f77896bae802d7ed1274d53006aef6@haiku-os.org> Message-ID: <053.c4dad99100645ae078e5c0fb90acc740@haiku-os.org> #4075: Panic in r31444 when mounting a NTFS volume --------------------------------+------------------------------------------- Reporter: meianoite | Owner: bga Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: File Systems/NTFS | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by bga): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31589. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 07:22:29 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 16 Jul 2009 05:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #4098: crashed app consumes all cpu when disable_debugger is used In-Reply-To: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> References: <046.40bd949d0b632235acda763c721da5d8@haiku-os.org> Message-ID: <055.9bc85d3790271c2be4e81f1747dcdf6e@haiku-os.org> #4098: crashed app consumes all cpu when disable_debugger is used ----------------------------+----------------------------------------------- Reporter: augiedoggie | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by scottmc): Just to confirm, this fix took care of the CMake dashboard failure we've been seeing the last few months. CMake is now passing all 107 tests. http://www.cdash.org/CDash/buildSummary.php?buildid=379567 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 14:32:32 2009 From: trac at haiku-os.org (idefix) Date: Thu, 16 Jul 2009 12:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.7e411675d09dda06ed4794507a5425f3@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by idefix): * status: closed => reopened * resolution: fixed => Comment: Unfortunately, it is not, because the error is in the code that's calling the scripts. I've made [attachment:installer.patch a patch] that should fix this bug, but I'm not sure it's the preferred way.[[BR]] (Note: I've not been able to test this patch, because of [http://haiku.pastebin.com/m58c40c2 a build problem] I'm experiencing.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 14:48:09 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 16 Jul 2009 12:48:09 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.84140e6d6c253cae0b20a649c8e0d1f4@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by anevilyak): Replying to [comment:2 idefix]: > (Note: I've not been able to test this patch, because of [http://haiku.pastebin.com/m58c40c2 a build problem] I'm experiencing.) That actually looks like your copy of gensyscallinfos.cpp is corrupt. Can you try deleting src/tools/gensyscalls/gensyscallinfos.cpp and re-svn upping it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 15:33:28 2009 From: trac at haiku-os.org (idefix) Date: Thu, 16 Jul 2009 13:33:28 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.c8aef2f2a6e8711ad4285c20652afc02@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:3 anevilyak]: > That actually looks like your copy of gensyscallinfos.cpp is corrupt. Can you try deleting src/tools/gensyscalls/gensyscallinfos.cpp and re-svn upping it? Unfortunately, that didn't help: {{{ /Build/Haiku> rm src/tools/gensyscalls/gensyscallinfos.cpp /Build/Haiku> svn update src/tools/gensyscalls/ Restored 'src/tools/gensyscalls/gensyscallinfos.cpp' At revision 31604. /Build/Haiku> cd src/apps/installer/ /Build/Haiku/src/apps/installer> jam -q ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...found 7410 target(s)... ...updating 642 target(s)... C++ ../../../generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos.o Link ../../../generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos Chmod1 ../../../generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos GenSyscallInfos1 ../../../generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp Unexpected end of input. ../../../generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos ../../../generated/objects/haiku/x86/common/tools/gensyscalls/syscalls.h.pp.parsable ../../../generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ...failed GenSyscallInfos1 ../../../generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ... ...skipped gensyscalls_infos.o for lack of gensyscalls_infos.cpp... ...skipped gensyscalls for lack of gensyscalls_infos.o... ...skipped syscalls.S.inc for lack of gensyscalls... ...skipped syscalls.o for lack of syscalls.S.inc... ...skipped os_main.o for lack of syscalls.o... ...skipped libroot.so for lack of os_main.o... ...skipped libbe.so for lack of libroot.so... ...skipped Installer for lack of libbe.so... ...failed updating 1 target(s)... ...skipped 8 target(s)... ...updated 2 target(s)... /Build/Haiku/src/apps/installer> }}} Maybe the gensyscallinfos.cpp-file inside the .svn-folder is corrupt?[[BR]] I will try to remove the whole gensyscalls-folder and let svn update it with a fresh copy from the server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 15:43:16 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 16 Jul 2009 13:43:16 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.46eaaf828b7ae8f9f1a9f0cda4dcdb38@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by anevilyak): That folder just contains the tool and rules for it. It generates a few files on the fly by using output from others such as headers/private/system/syscalls.h. It's possible one of its input files is corrupt somewhere as well...are you building on Haiku itself by any chance? If so, you may have hit one of the BFS problems and might want to run checkfs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 15:47:38 2009 From: trac at haiku-os.org (stippi) Date: Thu, 16 Jul 2009 13:47:38 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.cc40fd1ab9f085859a721121c7c00dcd@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Applied in r31607. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 15:59:35 2009 From: trac at haiku-os.org (idefix) Date: Thu, 16 Jul 2009 13:59:35 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.67e8601cf2dc3f03a8c04cca2058ce4e@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:5 anevilyak]: > [...]are you building on Haiku itself by any chance? If so, you may have hit one of the BFS problems and might want to run checkfs. Yes, I'm building on Haiku.[[BR]] One of the first things I do when I hit an error like that is run checkfs, but it couldn't find anything: {{{ ~> checkfs /Build/ checked 108537 nodes, 0 blocks not allocated, 0 blocks already set, 0 blocks could be freed files 86679 directories 21858 attributes 0 attr. dirs 0 indices 0 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 16:07:20 2009 From: trac at haiku-os.org (idefix) Date: Thu, 16 Jul 2009 14:07:20 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.6e8bc5408b08ae967225a8a0c1c99cef@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:6 stippi]: > Applied in r31607. Thanks a lot! Thanks! [[BR]] If I can't get my build problem fixed, I'll test this change when a new VMware image has been created. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 16 21:32:55 2009 From: trac at haiku-os.org (Hubert) Date: Thu, 16 Jul 2009 19:32:55 -0000 Subject: [Haiku-bugs] [Haiku] #4084: Lack 1440x900 resolutoion In-Reply-To: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> References: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> Message-ID: <050.85589d303aa2b5f625c89269bf3d670f@haiku-os.org> #4084: Lack 1440x900 resolutoion -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by Hubert): I tested r31607 (gcc4/gcc2 hybrid): it has not 1440x900, only 1400x1050, 1280x1024 etc. and I tested r31598 gcc2 with haiku-files.org: I have 1440x900 but this is a max resolution in Haiku - In earlier versions I had all resolutions to choice. Rudolf what is goes on? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 16:46:26 2009 From: trac at haiku-os.org (idefix) Date: Fri, 17 Jul 2009 14:46:26 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.2b8efa44805477ceedb987173c539239@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by idefix): * status: closed => reopened * resolution: fixed => Comment: I have tested it with r31610 and I hate to tell you, but we're not there yet.[[BR]] Fortunately, I have created [attachment:installerfinishscript.patch a patch] that will fix this bug for good. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 17:28:57 2009 From: trac at haiku-os.org (stippi) Date: Fri, 17 Jul 2009 15:28:57 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.5be5c04c533ba1538fb6a7e8d3f84767@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Ok, thanks a lot, applied in r31620. Again, I have not tested it myself, but I presume you have. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 19:40:39 2009 From: trac at haiku-os.org (axeld) Date: Fri, 17 Jul 2009 17:40:39 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file In-Reply-To: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> References: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> Message-ID: <051.91fca1f3817c56130d6bf87ff1c94f54@haiku-os.org> #3882: system freezes opening file -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 20:41:22 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 17 Jul 2009 18:41:22 -0000 Subject: [Haiku-bugs] [Haiku] #4099: Screenshot -d option crashes Message-ID: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> #4099: Screenshot -d option crashes -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- If you run Screenshot from the command line using the -d option without setting -d = to something the apps will crash. Perhaps provide a fallback default will fix it? Also the -d option doesn't seem to work right, I would expect Screenshot -d=10 -s would take a screenshot after 10 seconds, but it takes one right away. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 20:45:05 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 17 Jul 2009 18:45:05 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it Message-ID: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- When taking screenshot, sometimes it's useful to have the Screenshot app hidden from showing up in the deskbar. Also this option would be nice to have available from the command line for scripting as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 20:47:17 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 17 Jul 2009 18:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.4f096cff95fa5b44b27acde5d663e823@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by anevilyak): * owner: axeld => julun * component: - General => Applications/Screenshot -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 20:47:58 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 17 Jul 2009 18:47:58 -0000 Subject: [Haiku-bugs] [Haiku] #4099: Screenshot -d option crashes In-Reply-To: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> References: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> Message-ID: <051.c312483fffc69fc51a4ff80cff5ab93f@haiku-os.org> #4099: Screenshot -d option crashes -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by anevilyak): * owner: axeld => julun * component: - General => Applications/Screenshot -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 23:00:33 2009 From: trac at haiku-os.org (leavengood) Date: Fri, 17 Jul 2009 21:00:33 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.c5d3db30bceac09ba307677e48d00449@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by leavengood): I definitely agree with this, but there is a problem because AFAIK, the B_BACKGROUND_APP flag (which keeps the app from showing in the Deskbar) is set as a resource and cannot be changed at runtime. Since sometimes we want to run the Screenshot app like a normal application (to set options in the GUI), it doesn't make sense to have B_BACKGROUND_APP set permanently. Of course I could be wrong, and even if I am right, this could be a new feature in Haiku to change the app_info at runtime (at least this property.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 23:12:59 2009 From: trac at haiku-os.org (leavengood) Date: Fri, 17 Jul 2009 21:12:59 -0000 Subject: [Haiku-bugs] [Haiku] #4099: Screenshot -d option crashes In-Reply-To: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> References: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> Message-ID: <051.486da31af572c10e26e268d0417aa1bf@haiku-os.org> #4099: Screenshot -d option crashes -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: leavengood Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by leavengood): * owner: julun => leavengood Comment: I'll take care of this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 23:24:52 2009 From: trac at haiku-os.org (axeld) Date: Fri, 17 Jul 2009 21:24:52 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.37dc0c9e1f773693214734523c78c396@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): Indeed, the application flags cannot be changed at runtime. This is something that could be changed, of course, but I'm not sure it's really needed. At least in this case, the Screenshot application doesn't really work like I would like it to work; it pretty much works like Ubuntu's screenshot app, though. I would find useful if the UI pops up only *after* the screenshot has been made. It could remember where to put the mouse cursor, it could remember the active window when it made the screenshot, and make all those options changeable for the current screenshot. That would simplify that thing, and would make it much better to use IMO. For that, the tool that makes the screenshot could be a simple command line utility, that optionally runs the Screenshot application, and gives that one all the info it needs. Only if you run the Screenshot application manually, the application could work similar to what it does now (but could also still quit itself, and run the screenshot command line utility for the shot itself in order to be hidden from the Deskbar menu). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 23:26:47 2009 From: trac at haiku-os.org (axeld) Date: Fri, 17 Jul 2009 21:26:47 -0000 Subject: [Haiku-bugs] [Haiku] #4099: Screenshot -d option crashes In-Reply-To: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> References: <042.27c1fbb0d80d6e9c3ebeab6e94a0f5c3@haiku-os.org> Message-ID: <051.d3e4acfd836833b0f0a7eab554f834a4@haiku-os.org> #4099: Screenshot -d option crashes -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: leavengood Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): BTW Scott, could you always try to guess the correct component for your bug reports? Even if a developer disagrees with you later on, it's still better than to leave it at "General", as you could be right sometimes (this case at least is pretty clear). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 17 23:35:12 2009 From: trac at haiku-os.org (leavengood) Date: Fri, 17 Jul 2009 21:35:12 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.17096024862c3008787b9f212505cdb5@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by leavengood): Replying to [comment:3 axeld]: > > At least in this case, the Screenshot application doesn't really work like I would like it to work; it pretty much works like Ubuntu's screenshot app, though. I would find useful if the UI pops up only *after* the screenshot has been made. But that is what it does now...*scratches head* > It could remember where to put the mouse cursor, it could remember the active window when it made the screenshot, and make all those options changeable for the current screenshot. That would simplify that thing, and would make it much better to use IMO. You would have to elaborate on this, because I'm not sure what you mean. Do you mean the options would include a list of windows on the screen and you choose which one to make active before the screenshot is taken? Also do you really need to restore the mouse position? > For that, the tool that makes the screenshot could be a simple command line utility, that optionally runs the Screenshot application, and gives that one all the info it needs. Only if you run the Screenshot application manually, the application could work similar to what it does now (but could also still quit itself, and run the screenshot command line utility for the shot itself in order to be hidden from the Deskbar menu). That sounds sort of complicated and circular (the command-line utility calls the app and the app calls the command-line utility), but overall it sounds like it would be better. I'd have to think about it though. Unless Julun is around and wants to tackle all this himself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 10:29:46 2009 From: trac at haiku-os.org (monni) Date: Sat, 18 Jul 2009 08:29:46 -0000 Subject: [Haiku-bugs] [Haiku] #4101: nVidia CK804 OHCI USB controller detects only 1 connected device Message-ID: <040.473d654cbea9412a79fb85c1f328844a@haiku-os.org> #4101: nVidia CK804 OHCI USB controller detects only 1 connected device -------------------------+-------------------------------------------------- Reporter: monni | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Revision: 31621 / gcc4 When I boot with EHCI driver removed, Haiku does only show USB mouse connected even though I have Bluetooth dongle connected. Power led on dongle doesn't get lit. If I boot with EHCI driver still in place, power led on dongle works correctly but there is no other activity on that port and Bluetooth driver soft-locks when trying to initialize. Removing the dongle resumes "normal" operation of software. With USB tracing enabled syslog doesn't say anything about device insertion or status change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 11:18:12 2009 From: trac at haiku-os.org (julun) Date: Sat, 18 Jul 2009 09:18:12 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.568d66406cff09536609242cca3edec4@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by julun): Replying to [comment:4 leavengood]: > Replying to [comment:3 axeld]: > > > > At least in this case, the Screenshot application doesn't really work like I would like it to work; it pretty much works like Ubuntu's screenshot app, though. I would find useful if the UI pops up only *after* the screenshot has been made. > > But that is what it does now...*scratches head* > > > It could remember where to put the mouse cursor, it could remember the active window when it made the screenshot, and make all those options changeable for the current screenshot. That would simplify that thing, and would make it much better to use IMO. > > You would have to elaborate on this, because I'm not sure what you mean. Do you mean the options would include a list of windows on the screen and you choose which one to make active before the screenshot is taken? Also do you really need to restore the mouse position? > > > For that, the tool that makes the screenshot could be a simple command line utility, that optionally runs the Screenshot application, and gives that one all the info it needs. Only if you run the Screenshot application manually, the application could work similar to what it does now (but could also still quit itself, and run the screenshot command line utility for the shot itself in order to be hidden from the Deskbar menu). > > That sounds sort of complicated and circular (the command-line utility calls the app and the app calls the command-line utility), but overall it sounds like it would be better. I'd have to think about it though. > > Unless Julun is around and wants to tackle all this himself. [[BR]] I won't find the time to rewrite the tool in the next few month, so if there is some space left beside the browser project, just go ahead. --Karsten -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 11:37:11 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 18 Jul 2009 09:37:11 -0000 Subject: [Haiku-bugs] [Haiku] #4102: Linebreaks in Trac Message-ID: <044.65527a5012065a9f041841b50927f649@haiku-os.org> #4102: Linebreaks in Trac --------------------------+------------------------------------------------- Reporter: humdinger | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- One thing that keeps bothering me and had fooled many a bugreporter in the past: A new paragraph is recognized by an empty line, but a linebreak isn't detected and has to be explicitely be set with a [ [BR] ] (w/ the spaces). Couldn't we train Trac to recognize a linebreak?[[BR]] Doesn't OSDrawer also use Trac? It works over there... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 16:46:49 2009 From: trac at haiku-os.org (cyberguijarro) Date: Sat, 18 Jul 2009 14:46:49 -0000 Subject: [Haiku-bugs] [Haiku] #3651: Possible CharacterMap enhancements (easy) In-Reply-To: <044.28d50f6b6c97bdc90cb67ef486991747@haiku-os.org> References: <044.28d50f6b6c97bdc90cb67ef486991747@haiku-os.org> Message-ID: <053.8a1fccdcdada99bdf0ed1eb838f0058f@haiku-os.org> #3651: Possible CharacterMap enhancements (easy) ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by cyberguijarro): Hi! this sounds quite boring but actually a nice task to start getting involved in the project. Let me see what I can do ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 17:53:22 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 18 Jul 2009 15:53:22 -0000 Subject: [Haiku-bugs] [Haiku] #4102: Linebreaks in Trac In-Reply-To: <044.65527a5012065a9f041841b50927f649@haiku-os.org> References: <044.65527a5012065a9f041841b50927f649@haiku-os.org> Message-ID: <053.cf6a0114a1a0625d7ee633d263cbd17c@haiku-os.org> #4102: Linebreaks in Trac --------------------------+------------------------------------------------- Reporter: humdinger | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by scottmc): OSDrawer doesn't use trac, but HaikuPorts does. We run into this issue a lot, to get around it try using the triple brackets around the text http://dev.haiku-os.org/wiki/WikiFormatting {{{ Then you'll often run into the other issue of the text being too long for the current line and triggering the left/right scroll bars. }}} In general this is a trac issue, you might search and see if this type of issue has already but requested on trac's trac: (click the little trac logo at the bottom on the page) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 18:20:15 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 18 Jul 2009 16:20:15 -0000 Subject: [Haiku-bugs] [Haiku] #4102: Linebreaks in Trac In-Reply-To: <044.65527a5012065a9f041841b50927f649@haiku-os.org> References: <044.65527a5012065a9f041841b50927f649@haiku-os.org> Message-ID: <053.8090c6e0b38cc29396828a30d96c6c17@haiku-os.org> #4102: Linebreaks in Trac ---------------------------+------------------------------------------------ Reporter: humdinger | Owner: haiku-web Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by humdinger): * status: new => closed * resolution: => invalid Comment: Looks like the suggestion was denied 3 years ago: http://trac.edgewall.org/ticket/3277 "The second proposition (to treat a line break in the wiki edit area as a carriage return) would break existing wiki syntax, if not removing a very useful editing feature." Oh well... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 18:59:05 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 18 Jul 2009 16:59:05 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working Message-ID: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> #4103: cddb not working -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This was on r31621, here's a syslog snip from a removed/insertion of an audio cd: {{{ KERN: Media removed from /dev/disk/atapi/1/master/raw KERN: Media changed from /dev/disk/atapi/1/master/raw KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/1/master/raw) KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1 KERN: intel: ep_std_ops(0x2) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(8, 1: 0, 549216256, 2048) KERN: check_sense: Illegal request KERN: cd_read(): request.Wait() returned: General system error KERN: returned: -1 KERN: trying: file_systems/bfs/v1 KERN: check_sense: Illegal request KERN: cd_read(): request.Wait() returned: General system error KERN: returned: -1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: raw_command: KERN: returned: 0.699 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 04:28.30) KERN: 02. 04:30.30 (length 03:05.47) KERN: 03. 07:36.02 (length 03:29.15) KERN: 04. 11:05.17 (length 03:44.08) KERN: 05. 14:49.25 (length 04:35.12) KERN: 06. 19:24.37 (length 03:34.48) KERN: 07. 22:59.10 (length 06:38.35) KERN: 08. 29:37.45 (length 03:22.05) KERN: 09. 32:59.50 (length 04:33.05) KERN: 10. 37:32.55 (length 04:23.42) KERN: 11. 41:56.22 (length 04:14.68) KERN: 12. 46:11.15 (length 04:09.15) KERN: 13. 50:20.30 (length 03:46.17) KERN: 14. 54:06.47 (length 05:31.00) KERN: returned: 0.8 KERN: trying: file_systems/ext2/v1 KERN: check_sense: Illegal request KERN: cd_read(): request.Wait() returned: General system error KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: check_sense: Illegal request KERN: cd_read(): request.Wait() returned: General system error KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(8, 0x81079360) KERN: check_sense: Illegal request KERN: cd_read(): request.Wait() returned: General system error KERN: returned: -1 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/userlandfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 KERN: scanning with: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 04:28.30) KERN: 02. 04:30.30 (length 03:05.47) KERN: 03. 07:36.02 (length 03:29.15) KERN: 04. 11:05.17 (length 03:44.08) KERN: 05. 14:49.25 (length 04:35.12) KERN: 06. 19:24.37 (length 03:34.48) KERN: 07. 22:59.10 (length 06:38.35) KERN: 08. 29:37.45 (length 03:22.05) KERN: 09. 32:59.50 (length 04:33.05) KERN: 10. 37:32.55 (length 04:23.42) KERN: 11. 41:56.22 (length 04:14.68) KERN: 12. 46:11.15 (length 04:09.15) KERN: 13. 50:20.30 (length 03:46.17) KERN: 14. 54:06.47 (length 05:31.00) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 18:59:22 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 18 Jul 2009 16:59:22 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.829997014a1d878446d6ed4b99c7e14b@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by scottmc): * owner: axeld => bga * component: - General => File Systems/cdda -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 20:43:39 2009 From: trac at haiku-os.org (bga) Date: Sat, 18 Jul 2009 18:43:39 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.6a5edc00cebd3420e773635b10615787@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): Wat do you mean by "not working"? The syslog you posted only shows cdda-fs related stuff (which seems to be working) and not cddb_daemon stuff. Can you be more specific on what is happening and what you expected to happen? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 20:52:38 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 18 Jul 2009 18:52:38 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.954febb15ac54d8e2ce32ba59cf001a8@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): I expected the Audio CD label to change to the Album name, and the track xx.wav pseudo files to be renamed to the song names. This worked ok as recently as a week or so ago, but now that I'd like to try using it, it's not working. Wasn't sure if I did something to my build environment so I confirmed that someone else on IRC saw they same thing and they did. The cddb daemon shows up in the teams list, is there a way to see what's it's doing? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 18 21:12:29 2009 From: trac at haiku-os.org (leavengood) Date: Sat, 18 Jul 2009 19:12:29 -0000 Subject: [Haiku-bugs] [Haiku] #4104: Occasional debugger call from Observable class destructor when Icon-O-Matic is quit Message-ID: <045.62afb4c4a34a455d442483906f35f6e7@haiku-os.org> #4104: Occasional debugger call from Observable class destructor when Icon-O-Matic is quit ---------------------------------------+------------------------------------ Reporter: leavengood | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ I have been using Icon-O-Matic a lot lately and I have been seeing periodically. Sometimes when IOM is quit, the crash dialog comes up. The stacktrace indicates the problem is from a debugger call: {{{ 228: DEBUGGER: Observable::~Observable() - 1 observers still watching, first: 12PathListItem debug_server: Thread 228 entered the debugger: Debugger call: `Observable::~Observable() - 1 observers still watching, first: 12PathListItem ' stack trace, current PC 0xffff0114 : (0x7ffee6fc) 0x28e127 _._10Observable + 0x83 (0x7ffee83c) 0x27481d _._10IconObject + 0x6d (0x7ffee87c) 0x25bd2e _._Q38BPrivate4Icon10VectorPath + 0xca (0x7ffeeabc) 0x29aa26 Release__13Referenceable + 0x42 (0x7ffeeaec) 0x2caa43 _._19UnassignPathCommand + 0x3b (0x7ffeeb1c) 0x2767ae Clear__12CommandStack + 0x8a (0x7ffeeb5c) 0x27422e MakeEmpty__8Documentb + 0x26 (0x7ffeeb8c) 0x2d7896 _MakeIconEmpty__13IconEditorApp + 0xaa (0x7ffeebcc) 0x2d6a54 MessageReceived__13IconEditorAppP8BMessage + 0x98 (0x7ffeecac) 0x3ee8eb DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b (0x7ffeecdc) 0x3e5025 DispatchMessage__12BApplicationP8BMessageP8BHandler + 0x405 (0x7ffeeecc) 0x3f0259 task_looper__7BLooper + 0x211 (0x7ffeef0c) 0x3e3791 Run__12BApplication + 0x75 (0x7ffeef4c) 0x2da09a main + 0x6e (0x7ffeef7c) 0x25478b _start + 0x5b (0x7ffeefac) 0x105b1a runtime_loader + 0x14a }}} So for whatever reason a PathListItem is not being removed from the Observer list before the Observable is destroyed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 00:49:06 2009 From: trac at haiku-os.org (bga) Date: Sat, 18 Jul 2009 22:49:06 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.9d2eb95120735e5144b17ce586a7f4d4@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): Quit cddb_daemon through Process Controller. Start it manually from the terminal (/boot/system/servers/cddb_daemon). Insert and mount audio CD. Paste any output in the terminal here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 00:59:55 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 18 Jul 2009 22:59:55 -0000 Subject: [Haiku-bugs] [Haiku] #4101: nVidia CK804 OHCI USB controller detects only 1 connected device In-Reply-To: <040.473d654cbea9412a79fb85c1f328844a@haiku-os.org> References: <040.473d654cbea9412a79fb85c1f328844a@haiku-os.org> Message-ID: <049.1dcf99b2935aec12a2529cf3dbde5c81@haiku-os.org> #4101: nVidia CK804 OHCI USB controller detects only 1 connected device -------------------------+-------------------------------------------------- Reporter: monni | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): Please attach a full syslog. This info doesn't help really, as I don't happen to have said hardware. There are numerous reasons for this description to match, but I guess you already invalidated most of them. For one, it's possible that said port is EHCI only. Then it's always possible that it's a hardware fault on said port/controller. It's also possible that the device does only work in USB 2.0 mode. You can verify most of that by plugging in the different devices at different ports. Please tell what you've already tried. Also what output do you get when the "soft-lock" happens? What exactly do you mean by "soft-lock"? If you are able to, please also check with a gcc2 build to verify that there's no problem with how the driver is compiled (similar effects have been seen with the radeon driver for example). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 02:50:28 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 19 Jul 2009 00:50:28 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.b6701fd832da9997625f738ebbcacf72@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): Tried it a few times, inserting and mounting/unmounting, with each mount I got a new "Skipping device with id #, starting with 7 then 8 and then 9. Here's the output with 3 insert cycles, starting with "Skipping device with id 9". {{{ ~> /boot/system/servers/cddb_daemon CDDB Daemon for Haiku v1.0.0 started. Checking currently mounted volumes ... Skipping device with id 1. Skipping device with id 2. Skipping device with id 3. Skipping device with id 9. Checking complete. Listening for device mounts. Skipping device with id 10. Skipping device with id 11. Skipping device with id 12. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 10:14:28 2009 From: trac at haiku-os.org (monni) Date: Sun, 19 Jul 2009 08:14:28 -0000 Subject: [Haiku-bugs] [Haiku] #4101: nVidia CK804 OHCI USB controller detects only 1 connected device In-Reply-To: <040.473d654cbea9412a79fb85c1f328844a@haiku-os.org> References: <040.473d654cbea9412a79fb85c1f328844a@haiku-os.org> Message-ID: <049.1b53feb0d259cd4cd3a77061dacc78a0@haiku-os.org> #4101: nVidia CK804 OHCI USB controller detects only 1 connected device -------------------------+-------------------------------------------------- Reporter: monni | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by monni): Added syslogs with just non-working devices... I tried... 1. replacing USB mouse with PS/2 mouse 2. removing ehci, disabling it in BIOS 3. removing ehci and usb_disk (uses EHCI) 4. booting with just internal card reader, plugging in dongle when already running 5. booting with internal card reader, bluetooth dongle, USB DVB-T tuner, USB mouse 6. booting with internal card reader, bluetooth dongle, USB mouse 7. booting with internal card reader, bluetooth dongle, PS/2 mouse I can't compile same build with gcc2, because this machine is 64-bit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 13:27:36 2009 From: trac at haiku-os.org (axeld) Date: Sun, 19 Jul 2009 11:27:36 -0000 Subject: [Haiku-bugs] [Haiku] #4100: Screenshot shows in the deskbar, add option to hide it In-Reply-To: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> References: <042.fbe7dd4d7728c8a007d7393423e7b5ca@haiku-os.org> Message-ID: <051.cac2739f36cbcd57e7a3c9a7e36f5b85@haiku-os.org> #4100: Screenshot shows in the deskbar, add option to hide it -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: julun Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): Replying to [comment:4 leavengood]: > But that is what it does now...*scratches head* I guess I could have made that clearer :-) > You would have to elaborate on this, because I'm not sure what you mean. Do you mean the options would include a list of windows on the screen and you choose which one to make active before the screenshot is taken? Also do you really need to restore the mouse position? Right now, there is a strange "Options" page (that isn't really about options, mostly), and one that actually has something to do with the screenshot made. I would merge the two panels into one, with two different modes depending on whether the Screenshot application was launched, or the Print-Screen key was pressed. When you press the key, the window should come up (after the shot has been taken), and you should then still be able to select if the whole shot should be saved, or only the (then) active window. Same thing for the inclusion of the mouse cursor at that time. There is no reason to not be able to change these settings afterwards, and it's a lot more convenient to do so after the fact. The screenshot preview should actually show what's saved then (ie. the window only, etc.). Also, I would make it an option to suppress the window completely, and generally show it to the user. If you just launch the Screenshot application, it should not show a screenshot preview, because there is none yet. Instead, the delayed screenshot option should be displayed (but not with a simple BTextControl, a slider (or +/- buttons) would be way more convenient here), along with the "Take shot" button. There should not be this strange duality of the panels; they don't go along with each other well, and don't have much to do with each other, either, ATM. > That sounds sort of complicated and circular (the command-line utility calls the app and the app calls the command-line utility), but overall it sounds like it would be better. I'd have to think about it though. It's definitely circular, but it's not *that* complicated and would get the job done, at least :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 14:08:53 2009 From: trac at haiku-os.org (bga) Date: Sun, 19 Jul 2009 12:08:53 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.44a3ab37ed3d55e88058fcd20bb1144f@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): Devices will be skipped in the following cases: 1 - CD filesystem is not cdda-fs. 2 - The CD:do_lookup attribute is false (this means that you manually changed some track names) or it can not be read. 3 - The CD:cddbid attribute can not be read. 4 - The CD:toc attribute can not be read. Based on that, do the following: 1 - Make sure the cd is really an audio CD. Can you actually mount it and, say, copy audio tracks to the desktop? Please paste the output of mountvolume -l here. 2 - Paste the output of catattr CD:do_lookup /[AudioCDMountPoint] ([AudioCDmountPoint] should most likely be "Audio CD"). 3 - Same as 2 but for the CD:cddbid attribute. 4 - Same as 2 and 3 but for the CD:toc attribute. Note that the most likely thing that happened is that you manually tried to edit the Audio CD title or Track names before trying to use cddb_daemon to identify the CD. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 19 18:02:11 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 19 Jul 2009 16:02:11 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.cf4ae2a123a04070ed624ed6e55b4ea6@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): I know the CD is getting mounted as I'm able to copy the psuedo wav files to the local harddrive and then encode them to flac, mp3, ogg etc, they're just not getting renamed. {{{ ~> mountvolume -l Volume File System Size Mounted At (Device) -------------------------------------------------------------------------------------------- Ext2 File System 55.9G /unnamed volume (ata/1/master/0) Haiku Be File System 46.6G /boot (ata/1/master/1_0) Haiku-Files Be File System 44.2G /Haiku-Files (ata/1/master/1_1) Audio CD CDDA File System 374.6M /Audio CD (atapi/0/master/raw) ~> }}} This seems to be where things aren't working as expected: {{{ ~> catattr CD:do_loopup "Audio CD" catattr: file "Audio CD", attribute "CD:do_loopup": No such file or directory ~> catattr CD:cddbid "Audio CD" catattr: file "Audio CD", attribute "CD:cddbid": No such file or directory ~> catattr CD:toc "Audio CD" catattr: file "Audio CD", attribute "CD:toc": No such file or directory }}} I understand that CD Player does it's own cddb lookup, and that is working ok, gives the right info and all. So I assume that they network part must be ok. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 08:54:07 2009 From: trac at haiku-os.org (VinDuv) Date: Mon, 20 Jul 2009 06:54:07 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.f50a31a53ff257a4dfa296cbf142d8a4@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by VinDuv): Use "/Audio CD" instead of just "Audio CD" ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 13:09:35 2009 From: trac at haiku-os.org (bga) Date: Mon, 20 Jul 2009 11:09:35 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.55a4df6a0b71c8f52e894fde667aa753@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): Yes, follow VinDuv's suggestion. :) You want to check the attributes if the Audio CD mount point so unless you are already at the root dir ("/"), you need to use /Audio\ CD. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 13:14:21 2009 From: trac at haiku-os.org (bga) Date: Mon, 20 Jul 2009 11:14:21 -0000 Subject: [Haiku-bugs] [Haiku] #2930: The Mail Daemon can't use SSL in default in pre-alpha1 In-Reply-To: <041.8a0ee09e1012ee753211a91e7c7b4136@haiku-os.org> References: <041.8a0ee09e1012ee753211a91e7c7b4136@haiku-os.org> Message-ID: <050.870b75d532e7e89f62af32afd2233923@haiku-os.org> #2930: The Mail Daemon can't use SSL in default in pre-alpha1 ----------------------------------+----------------------------------------- Reporter: miqlas | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by bga): * status: assigned => closed * resolution: => fixed Comment: Marking this as fixed. I also fixed the gmail address issue in a CL that I do not remember right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 13:31:42 2009 From: trac at haiku-os.org (bga) Date: Mon, 20 Jul 2009 11:31:42 -0000 Subject: [Haiku-bugs] [Haiku] #2133: /boot/home/mail/in directory is created a bit late In-Reply-To: <043.4cd04a1580619b613378deb8276e39df@haiku-os.org> References: <043.4cd04a1580619b613378deb8276e39df@haiku-os.org> Message-ID: <052.eb887ae0cabc8873810d165ac10505f6@haiku-os.org> #2133: /boot/home/mail/in directory is created a bit late -------------------------------+-------------------------------------------- Reporter: kaoutsis | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Mail | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by bga): * status: assigned => closed * resolution: => fixed Comment: This was actually a spurious error reporting as the directory is created (just a bit later). Fixed in r31650. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 14:24:47 2009 From: trac at haiku-os.org (mt) Date: Mon, 20 Jul 2009 12:24:47 -0000 Subject: [Haiku-bugs] [Haiku] #4105: r31649 (gcc4/gcc2 mode) can't work Message-ID: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> #4105: r31649 (gcc4/gcc2 mode) can't work -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- I clean build and install r31649 in gcc4/gcc2 hybrid mode, but system can't work.[[BR]] After start up, ProcessController hangs, keyboard won't work (mouse can work), no disk on Tracker's mount menu etc. Tested on real hardware, buildtools r31443. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 14:45:46 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 20 Jul 2009 12:45:46 -0000 Subject: [Haiku-bugs] [Haiku] #4105: r31649 (gcc4/gcc2 mode) can't work In-Reply-To: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> References: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> Message-ID: <046.f09743e5f30ac990ac1906412c870999@haiku-os.org> #4105: r31649 (gcc4/gcc2 mode) can't work -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by anevilyak): A little more information about your hardware would probably be helpful here. Also, has it ever worked? If so, can you narrow down exactly what revision it started misbehaving at? Does taking out your USB stick make any difference? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 15:14:32 2009 From: trac at haiku-os.org (mt) Date: Mon, 20 Jul 2009 13:14:32 -0000 Subject: [Haiku-bugs] [Haiku] #4105: r31649 (gcc4/gcc2 mode) can't work In-Reply-To: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> References: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> Message-ID: <046.107b55c618a89b2b1cf632d9bedd633e@haiku-os.org> #4105: r31649 (gcc4/gcc2 mode) can't work -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by mt): Replying to [comment:1 anevilyak]: > A little more information about your hardware would probably be helpful here. Also, has it ever worked? If so, can you narrow down exactly what revision it started misbehaving at? Does taking out your USB stick make any difference? [[BR]] Hardware is same in Ticket #4050, so please see listdev.txt in Ticket #4050.[[BR]] Perhaps system works with r31622 ? (It works surely in r31388. ) [[BR]] Taking out USB stick does not make differences. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 21:19:27 2009 From: trac at haiku-os.org (bga) Date: Mon, 20 Jul 2009 19:19:27 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.c50db38fe97c61f4aca9d421d774038b@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): BTW, a listattr /Audio\ CD would also help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 22:18:40 2009 From: trac at haiku-os.org (zooey) Date: Mon, 20 Jul 2009 20:18:40 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page Message-ID: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> #4106: mmap() doesn't zero the last page ---------------------------+------------------------------------------------ Reporter: zooey | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ According to POSIX, mmap() is supposed to fill the area in the last page that is not "covered" by the mapped file with zeros. Our mmap does not do this, which causes gcc's fixincl program to crash, as it relies on these zeros to be there in order to invoke strlen(). If there's no zero in the "empty" area of the last page, strlen will try to access the following page and segfault. The current implementation seems to just read the corresponding BFS block(s) until all pages have been filled, as fixincl always crashes with the same file, but will not crash on a copy of that file (which obviously happens to have a trailing zero somewhere). This is with r31642. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 23:13:14 2009 From: trac at haiku-os.org (Pete) Date: Mon, 20 Jul 2009 21:13:14 -0000 Subject: [Haiku-bugs] [Haiku] #4107: KDL in usb_midi Message-ID: <039.6e3c973f26c46e285d174a037cdb06fa@haiku-os.org> #4107: KDL in usb_midi ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------+------------------------------------------------------ While trying to find out why usb_midi is not working (properly) with my M-Audio UNO, I was adding dprintf statements to track what was failing. I suddenly started going into KDL when I plugged in the UNO, and I've established that it is a particular dprintf in the 'usb_midi_added' function that triggers this. The KDL itself, though, happens in the 'midi_usb_callback', when it hits a '0xcccccccc' pointer. If the dprintf is commented out, that pointer becomes valid. To avoid the KDL, I added an abort-check for the bad pointer so I can get a record in syslog. Also, the original code to 'set_alt_interface' has been modified so that it isn't called for the UNO, because that stalls if it is. I will try to attach relevant files, but as I'm new to this (:-/) I'll include some excerpts here. First, a diff of the changes I made to the original usb_midi.c: {{{ 193,195d192 < DPRINTF_INFO ((MY_ID "in callback: my_dev = %p endpoint = %p (base %p)\n", < my_dev, my_dev->ept, *(void **)my_dev)); < if (my_dev->ept == 0xcccccccc) return; /* prevent KDL */ 217d213 < int alt; 236a233 > int alt; 265c262 < if(alt && (st = usb->set_alt_interface(dev, intf)) != B_OK) { --- > if((st = usb->set_alt_interface(dev, intf)) != B_OK) { 269c266 < --- > 280,281d276 < DPRINTF_INFO ((MY_ID "my_dev = %p interface endpoint = %p\n", < my_dev, &intf->endpoint [0])); 294d288 < DPRINTF_INFO ((MY_ID "queueing bulk xfer ep 0\n")); }}} Here's the section of syslog if that final DPRINTF_INFO is present: {{{ KERN: usb hub 2: port 0: new device connected KERN: usb_midi: init_hardware() Jul 17 2009 14:36:17 KERN: usb_midi: init_driver() Jul 17 2009 14:36:17 KERN: usb_midi: device_added() KERN: usb_midi: vendor ID 0x0763, product ID 0x0150 KERN: usb_midi: interface 0, alt : 0: class 1, subclass 1, protocol 0 KERN: usb_midi: interface 1, alt : 0: class 1, subclass 3, protocol 0 KERN: usb_midi: my_dev = 0x81004bb8 interface endpoint = 0x80ed3bf0 KERN: usb_midi: queueing bulk xfer ep 0 KERN: usb error uhci 0: td (0x0208a980) error: status: 0x18400003; token: 0x006803e1; KERN: usb_midi: midi_usb_callback() KERN: usb_midi: bus status -2147442667 KERN: usb_midi: in callback: my_dev = 0x81004bb8 endpoint = 0xcccccccc (base 0xcccccccc) KERN: usb_midi: added midi/usb/0 KERN: usb_midi: init_driver() OK KERN: usb_midi: publish_devices() KERN: usb_midi: publishing midi/usb/0 KERN: usb_midi: find_device(midi/usb/0) }}} and this is the syslog if it is commented out: {{{ KERN: usb hub 2: port 0: new device connected KERN: usb_midi: init_hardware() Jul 17 2009 14:30:46 KERN: usb_midi: init_driver() Jul 17 2009 14:30:46 KERN: usb_midi: device_added() KERN: usb_midi: vendor ID 0x0763, product ID 0x0150 KERN: usb_midi: interface 0, alt : 0: class 1, subclass 1, protocol 0 KERN: usb_midi: interface 1, alt : 0: class 1, subclass 3, protocol 0 KERN: usb_midi: my_dev = 0x873b8258 interface endpoint = 0x80ed39b0 KERN: usb_midi: added midi/usb/0 KERN: usb error uhci 0: td (0x0208a300) error: status: 0x18400003; token: 0x006802e1; KERN: usb_midi: midi_usb_callback() KERN: usb_midi: bus status -2147442667 KERN: usb_midi: init_driver() OK KERN: usb_midi: in callback: my_dev = 0x873b8258 endpoint = 0x80ed39b0 (base 0x00000000) KERN: usb_midi: publish_devices() KERN: usb_midi: publishing midi/usb/0 KERN: usb_midi: find_device(midi/usb/0) }}} Two things may be relevant in the above. One, there is always a uhci error (that I haven't got to look at yet -- uhci is still a black box -- but the UNO '''partially''' works if it doesn't KDL, even though it still shows a stall), and two, the order of execution seems different in the two cases. (The 'base' value printout isn't shown in the diff, but is just the first longword in the structure; it also differs, but this doesn't indicate that the whole structure is uninitialized. I did a later check of other values in the structure and they seem to be initialized correctly.) I suspect a race condition may be the root cause. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 20 23:33:24 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 20 Jul 2009 21:33:24 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.1fb4ba33fb74c5f71f465339509b0aa6@haiku-os.org> #4106: mmap() doesn't zero the last page ---------------------------+------------------------------------------------ Reporter: zooey | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): BFS (respectively any FS) isn't reponsible for clearing the unused part of the last page. At least that was the idea. ATM VMVnodeCache::Read() (the VM subsystem's interface to mapped files) clears the respective memory, but the file cache (respectively the VFS functions it uses) doesn't as far as I can see. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 00:15:28 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 20 Jul 2009 22:15:28 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() Message-ID: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Already reported privately but noting here for reference: If a program is contained entirely within main(), the debugger doesn't pull the source file and instead opts for showing disassembly. Adding even a single other function definition/call causes it to find the source properly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 00:27:04 2009 From: trac at haiku-os.org (mt) Date: Mon, 20 Jul 2009 22:27:04 -0000 Subject: [Haiku-bugs] [Haiku] #4105: r31649 (gcc4/gcc2 mode) can't work In-Reply-To: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> References: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> Message-ID: <046.f117f2346aafa464e815eaa257adc066@haiku-os.org> #4105: r31649 (gcc4/gcc2 mode) can't work -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by mt): Tested r31660, system seems to work except keyboard. (ProcessController and Tracker's mount menu works.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 00:52:47 2009 From: trac at haiku-os.org (bga) Date: Mon, 20 Jul 2009 22:52:47 -0000 Subject: [Haiku-bugs] [Haiku] #4109: Syslog duplicate message suppression seems to be eating more messages than it should. Message-ID: <038.5251afce6885a2b9459da314a5d360d1@haiku-os.org> #4109: Syslog duplicate message suppression seems to be eating more messages than it should. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/syslog_daemon | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- I was starting to track down a bug related to query update messages being lost and I started it by checking the syslog for any suspicious messages. Here is the relevant part of what I saw: {{{ 2009-07-20 19:45:33 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 0) 2009-07-20 19:45:37 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 0) 2009-07-20 19:45:45 DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 1) 2009-07-20 19:45:46 KERN: bfs: bfs_open_dir:1550: Invalid Argument 2009-07-20 19:45:47 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 1) 2009-07-20 19:45:47 KERN: Last message repeated 2577 times. 2009-07-20 19:45:51 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 1) 2009-07-20 19:45:59 DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 2) 2009-07-20 19:46:01 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 2) 2009-07-20 19:46:05 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 2) }}} The interesting line is the "Last message repeated 2577 times". if you look at the syslog it seems to be saying that the message above it was repeated this many times but it was obviously not it. This message was a result of deleting 2577 emails at once from Tracker so it seems the syslog not only ate the repeated messages but also at the first message that it should show (which I am pretty sure is "port full" or something like that). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 01:54:28 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 20 Jul 2009 23:54:28 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() In-Reply-To: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> References: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> Message-ID: <053.bcecd5c046cdf95620fa41537af919a4@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by bonefish): * status: new => assigned Comment: Already started looking into it. Being the fearless adventurer that I am I tried debugging Debugger with itself, but (so far) have run into two problems that have prevented me to actually do that. Well, in fact one user stupidity that took quite a bit of time to track down (Debugger is "single launch", so one can't debug the same executable) and one bug that I'm currently in the process of understanding. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 03:49:31 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 21 Jul 2009 01:49:31 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() In-Reply-To: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> References: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> Message-ID: <053.2ee683b7f99f81c0b5ba097e30a25f8a@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): Fixed in r31664. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 03:50:13 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 21 Jul 2009 01:50:13 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() In-Reply-To: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> References: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> Message-ID: <053.ce5ec208ab2b80549cfa27e668ba251f@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() ------------------------------------+--------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 03:58:52 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 21 Jul 2009 01:58:52 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() In-Reply-To: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> References: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> Message-ID: <053.09b153165664402607433ef198f90d99@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() ------------------------------------+--------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by anevilyak): I'm curious, based off the diff, why is it that only the simple main() case tripped across that bug? Or are there other circumstances that would have exposed it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:03:24 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 21 Jul 2009 02:03:24 -0000 Subject: [Haiku-bugs] [Haiku] #4110: Debugger: Selection Issues in Source Code View Message-ID: <043.0896e78bdd0eff626e78b46e65a4202f@haiku-os.org> #4110: Debugger: Selection Issues in Source Code View -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- r31658, gcc4 Selection in the source code view has several issues: - Sometimes the selection doesn't begin until the mouse has been dragged several characters or even lines. - In some situations the selection is off one or more characters (i.e. when copying the selection, text at a different position is copied). - Sometimes lines cannot be selected up to the last character. Might be related to the handling of tabs in the code. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:08:55 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 21 Jul 2009 02:08:55 -0000 Subject: [Haiku-bugs] [Haiku] #4110: Debugger: Selection Issues in Source Code View In-Reply-To: <043.0896e78bdd0eff626e78b46e65a4202f@haiku-os.org> References: <043.0896e78bdd0eff626e78b46e65a4202f@haiku-os.org> Message-ID: <052.5b365a8aed0b0ac13bcb8b4890a4b28d@haiku-os.org> #4110: Debugger: Selection Issues in Source Code View -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: new => assigned Comment: Working on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:10:37 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 21 Jul 2009 02:10:37 -0000 Subject: [Haiku-bugs] [Haiku] #4107: KDL in usb_midi In-Reply-To: <039.6e3c973f26c46e285d174a037cdb06fa@haiku-os.org> References: <039.6e3c973f26c46e285d174a037cdb06fa@haiku-os.org> Message-ID: <048.dc95564c4ead372e0269cace7c841386@haiku-os.org> #4107: KDL in usb_midi ----------------------+----------------------------------------------------- Reporter: Pete | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------+----------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Fixed in r31666. The callback wasn't called because of the queue_bulk() call. Instead it was triggered by the queue_request() call that didn't really make sense as it was. If that request would return early enough, i.e. before the other code finished setting the endpoint data, it would lead to this crash. Adding the debug output managed to do that in your case. About the set_alternate_interface(): If it isn't required by the specs to explicitly set an alternate, the call should simply be removed. Configuring the device will cause the default alternate to be selected anyway. If it is required, you could simply check for and ignore the stall case, as this simply means that the device doesn't support this call/request/function in the context of all the request based calls (set_feature, clear_feature, get_status, get_descriptor, send_request, queue_request and set_configuration). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:19:54 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 21 Jul 2009 02:19:54 -0000 Subject: [Haiku-bugs] [Haiku] #4109: Syslog duplicate message suppression seems to be eating more messages than it should. In-Reply-To: <038.5251afce6885a2b9459da314a5d360d1@haiku-os.org> References: <038.5251afce6885a2b9459da314a5d360d1@haiku-os.org> Message-ID: <047.6dece9aff511f6ca0449ae9e6d41ecd6@haiku-os.org> #4109: Syslog duplicate message suppression seems to be eating more messages than it should. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/syslog_daemon | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by mmlr): This looks perfectly valid to me. The repeated line in this case is: {{{ 2009-07-20 19:45:46 KERN: bfs: bfs_open_dir:1550: Invalid Argument 2009-07-20 19:45:47 KERN: Last message repeated 2577 times. }}} Note that the DHCP messages aren't written by the kernel, they are inserted by the net_server using the syslog() command. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:21:12 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 21 Jul 2009 02:21:12 -0000 Subject: [Haiku-bugs] [Haiku] #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() In-Reply-To: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> References: <044.eb540e7ae438abe1c1767ab43239e5cc@haiku-os.org> Message-ID: <053.fdceb2d68f28c9e97b12c8fbc55b0975@haiku-os.org> #4108: Debugger doesn't correctly handle retrieving source file for a program consisting only of main() ------------------------------------+--------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by bonefish): Replying to [comment:4 anevilyak]: > I'm curious, based off the diff, why is it that only the simple main() case tripped across that bug? Or are there other circumstances that would have exposed it? To save memory the FileManager maps paths found in the debug info to local paths for files only when the leaf name of the file doesn't match. Otherwise (i.e. the usual case), it only stores the path for the parent directory and creates the path for the file on the fly. When a file is first encountered the obvious (identity) path mapping is tried. If that works the ancestor directories are also mapped implicitly. In this case the direct parent directory of the file (and thus the file itself) simply didn't get a mapped path, when the file was first looked up (which happens for each function in that source file). The second time it worked correctly, since some ancestor directory's path was already mapped. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:38:31 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 21 Jul 2009 02:38:31 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.2437dea4652876e647b7763fec9f2f21@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): ~> catattr /Audio\ CD usage: catattr [--raw|-r] attr_name file1 [file2...] ~> catattr -r "CD:cddbid" /Audio\ CD e~> catattr "CD:cddbid" /Audio\ CD /Audio CD : uint32 : 1695153416 ~> catattr "CD:cddbid" /Audio\ CD /Audio CD : uint32 : 1695153416 ~> catattr "CD:do_lookup" /Audio\ CD /Audio CD : bool : 0 ~> catattr "CD:toc" /Audio\ CD /Audio CD : raw_data : 0x000000: 00 4a 01 08 00 10 01 00 00 00 02 20 00 10 02 00 '.J..............' 0x000010: 00 04 3b 21 00 10 03 00 00 08 28 0a 00 10 04 00 '..;!......(.....' 0x000020: 00 0e 20 21 00 10 05 00 00 16 23 21 00 10 06 00 '...!......#!....' 0x000030: 00 1b 0e 19 00 10 07 00 00 1f 3b 26 00 10 08 00 '..........;&....' 0x000040: 00 23 1f 0a 00 10 aa 00 00 2a 27 26 '.#.......*'& ' ~> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 04:38:53 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 21 Jul 2009 02:38:53 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.7a5f657fec10d6eadd124027f53c9861@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): {{{ ~> catattr /Audio\ CD usage: catattr [--raw|-r] attr_name file1 [file2...] ~> catattr -r "CD:cddbid" /Audio\ CD e~> catattr "CD:cddbid" /Audio\ CD /Audio CD : uint32 : 1695153416 ~> catattr "CD:cddbid" /Audio\ CD /Audio CD : uint32 : 1695153416 ~> catattr "CD:do_lookup" /Audio\ CD /Audio CD : bool : 0 ~> catattr "CD:toc" /Audio\ CD /Audio CD : raw_data : 0x000000: 00 4a 01 08 00 10 01 00 00 00 02 20 00 10 02 00 '.J..............' 0x000010: 00 04 3b 21 00 10 03 00 00 08 28 0a 00 10 04 00 '..;!......(.....' 0x000020: 00 0e 20 21 00 10 05 00 00 16 23 21 00 10 06 00 '...!......#!....' 0x000030: 00 1b 0e 19 00 10 07 00 00 1f 3b 26 00 10 08 00 '..........;&....' 0x000040: 00 23 1f 0a 00 10 aa 00 00 2a 27 26 '.#.......*'& ' ~> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 07:34:53 2009 From: trac at haiku-os.org (kaliber) Date: Tue, 21 Jul 2009 05:34:53 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.2f67a864892fd9c17fa0b3a14ceaf959@haiku-os.org> #4106: mmap() doesn't zero the last page ---------------------------+------------------------------------------------ Reporter: zooey | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by kaliber): * cc: grzegorz.dabrowski@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 12:12:33 2009 From: trac at haiku-os.org (axeld) Date: Tue, 21 Jul 2009 10:12:33 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.f89b1d4d7c7bd7ad9640c1a1e2a20b48@haiku-os.org> #4106: mmap() doesn't zero the last page ---------------------------+------------------------------------------------ Reporter: zooey | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 12:18:13 2009 From: trac at haiku-os.org (axeld) Date: Tue, 21 Jul 2009 10:18:13 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.f4ad724cc0f2a25a4c76f25abe1f32c1@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31669. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 14:26:12 2009 From: trac at haiku-os.org (mt) Date: Tue, 21 Jul 2009 12:26:12 -0000 Subject: [Haiku-bugs] [Haiku] #4105: r31649 (gcc4/gcc2 mode) can't work In-Reply-To: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> References: <037.bd1a2ea77506fe899ccb5e5a27067a98@haiku-os.org> Message-ID: <046.a9daacb0b835dd6a8be90c5ef60843ce@haiku-os.org> #4105: r31649 (gcc4/gcc2 mode) can't work -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by mt): r31669 seems to work fine. So this issue may be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 14:49:27 2009 From: trac at haiku-os.org (bga) Date: Tue, 21 Jul 2009 12:49:27 -0000 Subject: [Haiku-bugs] [Haiku] #4109: Syslog duplicate message suppression seems to be eating more messages than it should. In-Reply-To: <038.5251afce6885a2b9459da314a5d360d1@haiku-os.org> References: <038.5251afce6885a2b9459da314a5d360d1@haiku-os.org> Message-ID: <047.765044191d899185d400410251b4ef14@haiku-os.org> #4109: Syslog duplicate message suppression seems to be eating more messages than it should. ------------------------------------+--------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/syslog_daemon | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bga): * status: new => closed * resolution: => invalid Comment: Makes sense, but this is confusing. Anyway, closing as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 14:59:12 2009 From: trac at haiku-os.org (bga) Date: Tue, 21 Jul 2009 12:59:12 -0000 Subject: [Haiku-bugs] [Haiku] #4103: cddb not working In-Reply-To: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> References: <042.b23f929ea5df9388d3c24be2e0c5cab2@haiku-os.org> Message-ID: <051.8d58f1758ceea40e71c8baeba7b1eadd@haiku-os.org> #4103: cddb not working -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bga): There you go. The relevant result is this: {{{ catattr "CD:do_lookup" /Audio\ CD /Audio CD : bool : 0 }}} This indicates that CD:do_lookup is set to 0. This means that you either manually edited some track names or the CD title at some point or that the CD has CD-Text (which seems unlikelly as it was not used). Proving this is easy: {{{ 1 - Unmount CD. 2 - Open Terminal and "cd /boot/home/config/settings/cdda". 3 - "rm 6509fd08" (this file name is 1695153416 converted to hexadecimal). 4 - Mount CD. cddb_daemon, if it is running, should look your CD up. To be sure you may, before mounting the CD quitting cddb_daemon with ProcessController and then starting it manually in the terminal to check its output. }}} Let me know if it worked. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 16:06:51 2009 From: trac at haiku-os.org (idefix) Date: Tue, 21 Jul 2009 14:06:51 -0000 Subject: [Haiku-bugs] [Haiku] #4063: Installer calls its scripts without escaping the mount point In-Reply-To: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> References: <041.ab7cf511c4ee5ad272ae80b8fc9c2c40@haiku-os.org> Message-ID: <050.53da8bdbdd6aef451daae8e2e6c9852b@haiku-os.org> #4063: Installer calls its scripts without escaping the mount point -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:5 anevilyak]: > That folder just contains the tool and rules for it. It generates a few files on the fly by using output from others such as headers/private/system/syscalls.h. It's possible one of its input files is corrupt somewhere as well...are you building on Haiku itself by any chance? If so, you may have hit one of the BFS problems and might want to run checkfs. Well, I have done a complete checkout of Haiku's sourcefiles, but it still errors at the same point... I'm beginning to suspect the build-environment (Haiku under VMware), but I have no other environment to build Haiku on. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 23:17:11 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 21 Jul 2009 21:17:11 -0000 Subject: [Haiku-bugs] [Haiku] #4111: Indicator that threads are currently at a breakpoint / suspended in the debugger Message-ID: <044.d1dc52f46c16c8c6843d45a979269cbb@haiku-os.org> #4111: Indicator that threads are currently at a breakpoint / suspended in the debugger -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: bonefish Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- It might be nice for the thread list to indicate if a thread is currently sitting in debug mode due to a breakpoint or otherwise manually having been broken into, especially if it's possible for multiple threads to hit the same breakpoint. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 21 23:41:52 2009 From: trac at haiku-os.org (bga) Date: Tue, 21 Jul 2009 21:41:52 -0000 Subject: [Haiku-bugs] [Haiku] #4112: Thread exit seems to not be correctly handled. Message-ID: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> #4112: Thread exit seems to not be correctly handled. -----------------------------------+---------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- I have this program that has a main thread that sits waiting for connections. When it receives a connection it spawns 2 threads. During the lifetime of the program, one of those threads can die but the second one would still be running but the thread list view on Debugger removes the entry related to the thread that died but the other thread entry is emptied out (i.e. it is there but only as a blank line). because of this it is not possible to debug this other thread anymore after the first one died. I can provide the source code if needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 22 00:53:50 2009 From: trac at haiku-os.org (atomozero) Date: Tue, 21 Jul 2009 22:53:50 -0000 Subject: [Haiku-bugs] [Haiku] #4033: New acpi embedded controller driver block boot In-Reply-To: <044.1201dbdb25145186a0ddc76052c96f9c@haiku-os.org> References: <044.1201dbdb25145186a0ddc76052c96f9c@haiku-os.org> Message-ID: <053.bafd5e293223336944152c6289a9f423@haiku-os.org> #4033: New acpi embedded controller driver block boot -----------------------+---------------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by atomozero): now all work :) thxx czeidler!! http://dev.haiku-os.org/changeset/31679 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 14:46:18 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 12:46:18 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable Message-ID: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- mbtowc() returns 0 for ASCII char input. This is only allowed in case that the input string points to a null character, but it happens for any ASCII char. There seem to be other bugs in mwtomb() and in wcwidth(), but I did not yet inverstigate in them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 15:14:54 2009 From: trac at haiku-os.org (zooey) Date: Thu, 23 Jul 2009 13:14:54 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.088feedaa9c35ea838b4909efe7e3410@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by zooey): * owner: axeld => zooey * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 15:41:24 2009 From: trac at haiku-os.org (zooey) Date: Thu, 23 Jul 2009 13:41:24 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.7ea47e04872c1146a42019dc804fd98a@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by zooey): I have tried, but failed to reproduce any error. The testmb.c test program of glibc invokes mbtowc() and that seems to work just fine. Could you please post an invocation of mbtowc() that fails for you? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 15:57:58 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 13:57:58 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.c2d08dbaca456a60ca27f36021be47fb@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): Where is this program? Could you tell me why this test program works for you? The program that does work is the command line editor from bsh See ftp://ftp.berlios.de/pub/schily/schily-dist-pre2.tar.bz2 the code is in the file bsh/inputc.c and this code was written according to the POSIX standard and works on any other OS I was able to test until now: Solaris, Linux, HP-UX, Mac OS X...... The behavior seen with the mbtowc() from Haiku (returning 0 although the string input points to a valid 7 bit ASCII character) is not permitted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 16:08:50 2009 From: trac at haiku-os.org (zooey) Date: Thu, 23 Jul 2009 14:08:50 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.71abf9a51fee5fb188c1d2958468af00@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by zooey): I have attached testmb.c to this ticket. Which revision have you used when you noticed the problem? I am asking because we have changed our wchar_t type in r31443 (from short to int). If you haven't updated beyond that, please do so (and make sure to update your buildtools, too). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 16:33:32 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 14:33:32 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.ffe6c81f647829e2f8b5c6fd3b48d6cf@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): Thank you for forwarding the test program! The test program is not correct: 1) calling mbtowc(%wc, &c, MB_CUR_MAX) is illegal as there is no valid string in the second parameter. 2) The test program does not set up a locale. This does never apply to correct software that uses wide chars. You need to first call something like: if (setlocale(LC_ALL, "") == NULL) error("Bad locale in inital environment.\n"); -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 17:15:25 2009 From: trac at haiku-os.org (zooey) Date: Thu, 23 Jul 2009 15:15:25 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.0fb020425397bb6ccbc0a831109c313f@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by zooey): Replying to [comment:5 schily]: > Thank you for forwarding the test program! > > The test program is not correct: > > 1) calling mbtowc(%wc, &c, MB_CUR_MAX) is illegal as there is no valid string > in the second parameter. POSIX doesn't say anything about that parameter being a valid c-string, but I adjusted it anyway ... > > 2) The test program does not set up a locale. This does never apply to > correct software that uses wide chars. You need to first call something like: > > if (setlocale(LC_ALL, "") == NULL) > error("Bad locale in inital environment.\n"); ... adding that doesn't change anything either: testmb.c runs through without failure for me. So, - which revision of haiku are you using? - which revision of haiku's buildtools are you using? - does testmb.c work for you? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 17:32:15 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 23 Jul 2009 15:32:15 -0000 Subject: [Haiku-bugs] [Haiku] #4112: Thread exit seems to not be correctly handled. In-Reply-To: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> References: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> Message-ID: <047.0b4224b069c019c4a7ad45dec74e2395@haiku-os.org> #4112: Thread exit seems to not be correctly handled. -----------------------------------+---------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): A sample to reproduces the problem would be appreciated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 17:42:25 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 15:42:25 -0000 Subject: [Haiku-bugs] [Haiku] #4112: Thread exit seems to not be correctly handled. In-Reply-To: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> References: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> Message-ID: <047.e9f25efb7f3339e134dc35e4a8fcda27@haiku-os.org> #4112: Thread exit seems to not be correctly handled. -----------------------------------+---------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bga): Code added. Don't pay too much attention to it as it is simply a proof of concept and has at least one major bug (which is intentional, I was testing how the debug would react to crashes) which is the fact that when the thread exists it closes the BNetEndpoint and deletes it and the ping thread tries to send a packet through it. Anyway, compile it with "gcc -O0 -g test.cpp -lbnetapi", start it with the debugger and in a different termonal do "telnet 127.0.0.1 8080" then use ^] to enter command mode (in the telnet session) and type quit to close the session. At this point, what I described will happen. BTW, I am impressed by how far the Debugger is. Congratulations. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 17:43:49 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 15:43:49 -0000 Subject: [Haiku-bugs] [Haiku] #4112: Thread exit seems to not be correctly handled. In-Reply-To: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> References: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> Message-ID: <047.0e5c856d28fc2ff2dc5b94db41c6ceb2@haiku-os.org> #4112: Thread exit seems to not be correctly handled. -----------------------------------+---------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bga): Hmmmm... It seems the caret (control) character is special for Trac. I meant to say CTRL + ] to enter command mode. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 17:54:53 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 15:54:53 -0000 Subject: [Haiku-bugs] [Haiku] #3751: Redrawing problems. In-Reply-To: <038.0e233409b5195ef2817f5e39fca6e403@haiku-os.org> References: <038.0e233409b5195ef2817f5e39fca6e403@haiku-os.org> Message-ID: <047.735e9c1e631b6201434a39f99c2c2601@haiku-os.org> #3751: Redrawing problems. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by bga): It looks like if you wait enough, bugs sort themselves alone. I just did a clean Haiku install (I do those every other week) and Soundplay is not showing any redrawing problems whatsoever. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 18:47:10 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 23 Jul 2009 16:47:10 -0000 Subject: [Haiku-bugs] [Haiku] #4112: Thread exit seems to not be correctly handled. In-Reply-To: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> References: <038.37f99edd2223154b4d7c51829500df42@haiku-os.org> Message-ID: <047.3f74bb390c7c3409f17ecc691741d3e8@haiku-os.org> #4112: Thread exit seems to not be correctly handled. -----------------------------------+---------------------------------------- Reporter: bga | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): If it helps, I see a similar problem when the app being debugged exits, i.e. if I start up Vision in the debugger, have it connect to a network and then exit, the threads view has a bunch of empty phantom rows after the app is gone (and also as the threads go away). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 19:02:22 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 17:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). Message-ID: <038.223c45b51c7685bee85dbb4b5834ae78@haiku-os.org> #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). --------------------------------------+------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Summary says it all. An excerpt from the video can be taken from here: http://www.bug-br.org.br/BeOSDemoVideo.mpg (4 Mb). Loading it in MediaPlayer results in the Audio Track being played but there is no video. The video track is detected tough and File Info shows it as MPEG1 Video (libavcodec mpeg1video). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 19:06:09 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 17:06:09 -0000 Subject: [Haiku-bugs] [Haiku] #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). In-Reply-To: <038.223c45b51c7685bee85dbb4b5834ae78@haiku-os.org> References: <038.223c45b51c7685bee85dbb4b5834ae78@haiku-os.org> Message-ID: <047.af88bef7d21c659ff95a1493fecbfb26@haiku-os.org> #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). --------------------------------------+------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by bga): BTW, the excerpt i posted starts witha black screen and stays like that up to the middle of the video. The first thing that shows is the old Be logo. Just mentioning so whoever looks into it does not end up thinking the bacl video at the start is a bug or something. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 19:13:33 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 17:13:33 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.72eb74dd5a0ef6be8ed4d76a8bf986fb@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): I just tested the program test,b.c and as expected, it works on Solaris and it fails on Haiku: mbstowcs FAILED! wcstombs FAILED! mblen 1 FAILED! conversion to wide failed, result: 0 Test FAILED! BTW: am using the latest version which is r31644 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 19:16:41 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 23 Jul 2009 17:16:41 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.f6ed48b9696f0fa857e1b6373c43fca7@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by anevilyak): Did you update your build tools before building that version? It sounds like you're using a cross compiler toolchain that hasn't been updated with the wchar_t changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 19:22:24 2009 From: trac at haiku-os.org (zooey) Date: Thu, 23 Jul 2009 17:22:24 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.35526b9139ed3789fde323320086f7b0@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by zooey): * status: closed => reopened * resolution: fixed => Comment: Reopening, since the problem is still present. I'm going to attach a little test program, which exposes the bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 20:17:11 2009 From: trac at haiku-os.org (czeidler) Date: Thu, 23 Jul 2009 18:17:11 -0000 Subject: [Haiku-bugs] [Haiku] #4033: New acpi embedded controller driver block boot In-Reply-To: <044.1201dbdb25145186a0ddc76052c96f9c@haiku-os.org> References: <044.1201dbdb25145186a0ddc76052c96f9c@haiku-os.org> Message-ID: <053.5a7c243abc45cf939822af807925b59f@haiku-os.org> #4033: New acpi embedded controller driver block boot ------------------------+--------------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by czeidler): * status: new => closed * resolution: => fixed Comment: Ok fine then I close the ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 21:28:24 2009 From: trac at haiku-os.org (kallisti5) Date: Thu, 23 Jul 2009 19:28:24 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. Message-ID: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ When booting the Haiku PPC Kernel a: boot_arch_elf_relocate_rela(): Failed to relocate entry index error is presented for a split second before returning to the PPC bootloader. The Failed to relocate error comes from kernel/arch/ppc/arch_elf.cpp I am working on getting the *exact* message now by inserting a temporary while(1) after the error condition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 21:56:34 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 19:56:34 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.7be4b7775cb7b29803671d540899c0d1@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): Do you like to tell me that you deliver a non-working GCC together with Haiku? Anyway, the autoconf results tell me that sizeof(L'a') is 4 as well as sizeof(wchar_t). In addition, the specific problem cannot be a rsult of such size problems as the function mbtowc() cannot know about this and the incorrect return value is a result from interpreting the input string that is an array of 8 bit chars. As mentioned before, I asume that the internal tables used by glibc are set up incorrectly. Another problem is that Haiku does not set any if the LC_* or LANG environment variables and an application thus would in a POSIX compliant anvironment asume the "C" locale which could be either "ISO-646" or "ISO-8859-1" coding. As the problem is easy to reproduce even with your small test program, it should be easy to fix.... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 21:58:06 2009 From: trac at haiku-os.org (kallisti5) Date: Thu, 23 Jul 2009 19:58:06 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.df9c7ce94d443417a7a5e55da508684f@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): boot_arch_elf_relocate_rela(): Failed to relocate entry index 1339, rel type 1, offset 0x8017a568, sym 0xe30, addend 0x0 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:00:52 2009 From: trac at haiku-os.org (idefix) Date: Thu, 23 Jul 2009 20:00:52 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. Message-ID: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. --------------------------+------------------------------------------------- Reporter: idefix | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Recently, I'm unable to build libroot.so on Haiku. It always stops at the following error: {{{ MkDir1 generated/objects/haiku/x86/common/system/libroot/os MkDir1 generated/objects/haiku_host/x86/release/tools/gensyscalls MkDir1 generated/objects/haiku/x86/common/tools/gensyscalls PreprocessSyscalls generated/objects/haiku/x86/common/tools/gensyscalls/syscalls.h.pp C++ generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscalls.o C++ generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos.o Link generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos Chmod1 generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos PreprocessSyscalls generated/objects/haiku/x86/common/tools/gensyscalls/syscalls.h.pp.parsable GenSyscallInfos1 generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp Unexpected end of input. generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos generated/objects/haiku/x86/common/tools/gensyscalls/syscalls.h.pp.parsable generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ...failed GenSyscallInfos1 generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ... ...skipped gensyscalls_infos.o for lack of gensyscalls_infos.cpp... ...skipped gensyscalls for lack of gensyscalls_infos.o... ...skipped syscalls.S.inc for lack of gensyscalls... ...skipped syscalls.o for lack of syscalls.S.inc... ...skipped os_main.o for lack of syscalls.o... ...skipped libroot.so for lack of os_main.o... ...failed updating 1 target(s)... ...skipped 6 target(s)... ...updated 128 target(s)... }}} I'm experiencing this error in both of my build-environments: Haiku running in VMware and Haiku running on real hardware. Both of them using the gcc2 nightly builds from [http://haiku-files.org/ haiku-files.org]. In both cases, I checked out a full tree before building. Steps to reproduce in VMware: - Start an Haiku VMware environment with 2 virtual disks: an Haiku gcc2 VMware image from [http://haiku-files.org/vm/ haiku-files.org] and a 4 GB empty disk - Boot into the Haiku image and initialise the 4 GB disk with a block size of 1024 and no index - Checkout the Haiku tree to the 4 GB disk - Run configure and then build libroot.so You should get the same build output as in [attachment:builderror.txt this file]. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:02:08 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 23 Jul 2009 20:02:08 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.f2256c478d7b083d21082983e1ff5257@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by anevilyak): Replying to [comment:9 schily]: > Do you like to tell me that you deliver a non-working GCC together with > Haiku? This isn't about the version that comes a development package in Haiku. It's about the one used to build the system itself. As you haven't specified where your copy of Haiku comes from, I assume you're cross compiling it yourself. If so, you would have needed to svn update your copy of the buildtools/trunk subdir and rerun ./configure --build-cross- tools(-gcc4), as otherwise the libs would be out of sync with the headers and/or compiler builtins. > Anyway, the autoconf results tell me that sizeof(L'a') is 4 > as well as sizeof(wchar_t). In addition, the specific problem Which is irrelevant since within Haiku it's getting that from the compiler optional package which has nothing to do with which one you used to build the system. > As the problem is easy to reproduce even with your small test program, > it should be easy to fix.... Except we can't reproduce it, otherwise these questions wouldn't be getting asked. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:07:06 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 20:07:06 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.7fd6b4cc19ae945662ea9868e3c1d50e@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): Do you like to tell me that you cannot reproduce the problem using: haiku-pre-alpha-r31644-raw.zip For me it is reproducable with two different installations. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:07:48 2009 From: trac at haiku-os.org (andreasf) Date: Thu, 23 Jul 2009 20:07:48 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.249ac75c8e09fbe70eb11406cf2de45a@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) Comment: This could explain some weird Mono behavior I encountered... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:09:39 2009 From: trac at haiku-os.org (andreasf) Date: Thu, 23 Jul 2009 20:09:39 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.dcc0daf00c1eb76c0bdbf309108de8e8@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:16:13 2009 From: trac at haiku-os.org (bga) Date: Thu, 23 Jul 2009 20:16:13 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.732d81e40db2520754621449d7f2326f@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by bga): Could it be that the build tools in the build factory were not updated after the change to wchar? schilly, any chance you could try compiling Haiku yourself to test this? I can't reproduce this bug either on my instalarion (r31711). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:22:06 2009 From: trac at haiku-os.org (schily) Date: Thu, 23 Jul 2009 20:22:06 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.306fca20b328e28a3440e080ba705be9@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): I did compile and run testmb.c on an installation that is based on the HD image from: haiku-pre-alpha-r31644-raw.zip If you do the same, you must get the same error as I get. If it does not fail for you, please tell me what specific things you do in order to prevent the failure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 23 22:52:30 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 23 Jul 2009 20:52:30 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.2f7550e5a9a91e43abfa2a720c34a73e@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by anevilyak): Replying to [comment:14 schily]: > I did compile and run testmb.c on an installation > that is based on the HD image from: > > haiku-pre-alpha-r31644-raw.zip That would be the missing piece of the puzzle, and indicates that the build factory was never updated with the newer toolchain. Most of us are using Haiku installations that were built directly on our own systems with all the needed updates. Have sent an email to the maintainer of that build factory. Until he gets around to updating that, the only way you'll work around this is by building Haiku yourself. In any case, on a correctly built system: {{{ ~> uname -a Haiku leviathan 1 r31713 Jul 23 2009 07:36:06 BePC Haiku ~> gcc --version gcc (GCC) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ~> ./testmb wide value: 0x0078 Test succeeded. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 01:22:14 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 23 Jul 2009 23:22:14 -0000 Subject: [Haiku-bugs] [Haiku] #4110: Debugger: Selection Issues in Source Code View In-Reply-To: <043.0896e78bdd0eff626e78b46e65a4202f@haiku-os.org> References: <043.0896e78bdd0eff626e78b46e65a4202f@haiku-os.org> Message-ID: <052.6e5adef074651fcc84c33fd09c57abe8@haiku-os.org> #4110: Debugger: Selection Issues in Source Code View ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Debugger | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31724. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 05:47:33 2009 From: trac at haiku-os.org (bbjimmy) Date: Fri, 24 Jul 2009 03:47:33 -0000 Subject: [Haiku-bugs] [Haiku] #4117: gensyscalls_infos.cpp building haiku within haiku gcc 2.93 Message-ID: <042.f5e0f2dcea40078e811d987dccc65eee@haiku-os.org> #4117: gensyscalls_infos.cpp building haiku within haiku gcc 2.93 --------------------------+------------------------------------------------- Reporter: bbjimmy | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- GenSyscallInfos1 generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp Unexpected end of input. generated/objects/haiku_host/x86/release/tools/gensyscalls/gensyscallinfos generated/objects/haiku/x86/common/tools/gensyscalls/syscalls.h.pp.parsable generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ...failed GenSyscallInfos1 generated/objects/haiku/x86/common/tools/gensyscalls/gensyscalls_infos.cpp ... ...skipped gensyscalls_infos.o for lack of gensyscalls_infos.cpp... ...skipped gensyscalls for lack of gensyscalls_infos.o... ...skipped syscall_dispatcher.h for lack of gensyscalls... ...skipped syscalls.o for lack of syscalls.cpp... ...skipped kernel_core.o for lack of syscalls.o... ...skipped kernel.so for lack of kernel_core.o... ...skipped pci for lack of kernel.so... ...skipped haiku.image-copy-files-dummy-system/add- ons/kernel/bus_managers for lack of pci... ...skipped haiku.image for lack of haiku.image-copy-files... ...failed updating 1 target(s)... ...skipped 9 target(s)... ...updated 38 target(s)... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 09:09:37 2009 From: trac at haiku-os.org (umccullough) Date: Fri, 24 Jul 2009 07:09:37 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.f42b5365c24f92282e4747a816dc30a4@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by umccullough): Has anyone notified Phil yet? AFAIK, he doesn't follow the bug list. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 09:10:37 2009 From: trac at haiku-os.org (jackburton) Date: Fri, 24 Jul 2009 07:10:37 -0000 Subject: [Haiku-bugs] [Haiku] #4117: gensyscalls_infos.cpp building haiku within haiku gcc 2.93 In-Reply-To: <042.f5e0f2dcea40078e811d987dccc65eee@haiku-os.org> References: <042.f5e0f2dcea40078e811d987dccc65eee@haiku-os.org> Message-ID: <051.e1813f9fb6627104ab8dbc410d2951ef@haiku-os.org> #4117: gensyscalls_infos.cpp building haiku within haiku gcc 2.93 ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: duplicate | Blockedby: 4116 Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => duplicate * blockedby: => 4116 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 10:10:58 2009 From: trac at haiku-os.org (stippi) Date: Fri, 24 Jul 2009 08:10:58 -0000 Subject: [Haiku-bugs] [Haiku] #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). In-Reply-To: <038.223c45b51c7685bee85dbb4b5834ae78@haiku-os.org> References: <038.223c45b51c7685bee85dbb4b5834ae78@haiku-os.org> Message-ID: <047.5de62b18b76c2e412f7f11c6dc2fdbbf@haiku-os.org> #4114: MediaPlayer/Media Kit does not show video for BeOS Demo Video (MPEG). ---------------------------------------+------------------------------------ Reporter: bga | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for the clip, made this easy enough! Fixed in r31729. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 10:56:42 2009 From: trac at haiku-os.org (axeld) Date: Fri, 24 Jul 2009 08:56:42 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.e456b0348d04502e15dbd0f18f44157b@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: reopened => new Comment: This is actually a different bug with the same outcome, though; it should only affect the truncation case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 10:56:55 2009 From: trac at haiku-os.org (axeld) Date: Fri, 24 Jul 2009 08:56:55 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.acd5252c0b954ce433118644b04ffb4a@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 11:19:52 2009 From: trac at haiku-os.org (axeld) Date: Fri, 24 Jul 2009 09:19:52 -0000 Subject: [Haiku-bugs] [Haiku] #4106: mmap() doesn't zero the last page In-Reply-To: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> References: <040.6af9621c9e41a772bd756c20de84839c@haiku-os.org> Message-ID: <049.6ab94e12e8e5834110ded0b94ac3320b@haiku-os.org> #4106: mmap() doesn't zero the last page ----------------------------+----------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31732, and thanks for the test app! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 14:01:43 2009 From: trac at haiku-os.org (diver) Date: Fri, 24 Jul 2009 12:01:43 -0000 Subject: [Haiku-bugs] [Haiku] #4118: [app_server] crash in BTextControl::ResolveSpecifier Message-ID: <040.a1c3c4f3cdc17e02b50903384aaacd30@haiku-os.org> #4118: [app_server] crash in BTextControl::ResolveSpecifier --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I was downloading a file and when it finished I tried to quit firefox (Alt+w) and got a crash. r31713 in virtualbox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 14:02:48 2009 From: trac at haiku-os.org (diver) Date: Fri, 24 Jul 2009 12:02:48 -0000 Subject: [Haiku-bugs] [Haiku] #4118: [app_server] crash in BTextControl::ResolveSpecifier In-Reply-To: <040.a1c3c4f3cdc17e02b50903384aaacd30@haiku-os.org> References: <040.a1c3c4f3cdc17e02b50903384aaacd30@haiku-os.org> Message-ID: <049.8ba7eaff4b22ba56f9971c4252abfa0f@haiku-os.org> #4118: [app_server] crash in BTextControl::ResolveSpecifier --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by diver): backtrace attached -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 14:08:27 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 24 Jul 2009 12:08:27 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. In-Reply-To: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> References: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> Message-ID: <050.4a700c4cf910e07a3f21756eabcd43e9@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. --------------------------+------------------------------------------------- Reporter: idefix | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: 4113 | Platform: All Blocking: 4117 | --------------------------+------------------------------------------------- Changes (by bonefish): * blockedby: => 4113 Comment: I'd guess that this is a dup of #4113 and will disappear as soon as the build factory uses the correct build tools. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 14:43:18 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 12:43:18 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.222bd135bba87b90e39bbdbd46d71e10@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 4116 | -----------------------+---------------------------------------------------- Comment(by anevilyak): Replying to [comment:16 umccullough]: > Has anyone notified Phil yet? AFAIK, he doesn't follow the bug list. Yes, I notified Phil, I was under the impression he was working on updating them, but he never gave me confirmation that he was finished with that yet. Will see what's going on (or you can if you see him before me). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 15:29:28 2009 From: trac at haiku-os.org (bbjimmy) Date: Fri, 24 Jul 2009 13:29:28 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.0bca63cc16ea46dbb070c37f34925f3d@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 4116 | -----------------------+---------------------------------------------------- Changes (by bbjimmy): * cc: black.belt.jimmy@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 15:33:17 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 13:33:17 -0000 Subject: [Haiku-bugs] [Haiku] #4119: Occasional incorrect behavior from Invalidate() Message-ID: <044.d3dbe78071a63efc6ec2acd1309d7680@haiku-os.org> #4119: Occasional incorrect behavior from Invalidate() --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- In the Debugger's textview component I've been observing some odd behavior where Invalidate() sometimes appears to be ignored. To be exact I'm using the BRegion version of Invalidate(), and the best I can describe it is, while selecting text, if the selection region is small (i.e. a few characters/words), the redraw requested does not appear to happen, though for instance switching workspaces and back will show that the region is indeed correct as at that point the selection is drawn where expected. However, once the region is made large enough, by say selecting several lines worth, it suddenly Invalidates correctly, and then continues to do so afterwards regardless of size. Adding a Sync() after the Invalidate() call causes the expected correct behavior in all cases but AFAIK this shouldn't be necessary (c.f. mailing list discussion re r31724). Note that the Sync() is currently present in the source tree, so you will need to comment it out in order to view this behavior (src/apps/debugger/gui/team_window/SourceView.cpp line 1109). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 15:38:33 2009 From: trac at haiku-os.org (axeld) Date: Fri, 24 Jul 2009 13:38:33 -0000 Subject: [Haiku-bugs] [Haiku] #4118: [app_server] crash in BTextControl::ResolveSpecifier In-Reply-To: <040.a1c3c4f3cdc17e02b50903384aaacd30@haiku-os.org> References: <040.a1c3c4f3cdc17e02b50903384aaacd30@haiku-os.org> Message-ID: <049.b7ffb09d66a8cb6866b454290e1be003@haiku-os.org> #4118: [app_server] crash in BTextControl::ResolveSpecifier --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): The backtrace is useless, unfortunately; the app_server never uses BTextControls. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 16:29:00 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 24 Jul 2009 14:29:00 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.12fda9b4a89b37283b9c7a6f85714d49@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): err... think I found where the error is coming from... src/tests/system/boot/loader/platform_misc.cpp: extern "C" status_t boot_arch_elf_relocate_rel(struct preloaded_image *image, struct Elf32_Rel *rel, int rel_len) { return B_ERROR; } extern "C" status_t boot_arch_elf_relocate_rela(struct preloaded_image *image, struct Elf32_Rela *rel, int rel_len) { return B_ERROR; } This looks incomplete... right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 16:37:25 2009 From: trac at haiku-os.org (axeld) Date: Fri, 24 Jul 2009 14:37:25 -0000 Subject: [Haiku-bugs] [Haiku] #4119: Occasional incorrect behavior from Invalidate() In-Reply-To: <044.d3dbe78071a63efc6ec2acd1309d7680@haiku-os.org> References: <044.d3dbe78071a63efc6ec2acd1309d7680@haiku-os.org> Message-ID: <053.2bc6608fdd7f157eca59fc7894e04da9@haiku-os.org> #4119: Occasional incorrect behavior from Invalidate() --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: axeld => stippi * component: Kits/Interface Kit => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 17:31:45 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 24 Jul 2009 15:31:45 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.6a901e1e4d2e1b353db6a35f1d0a24d4@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): Please ignore the above comment. Nothing wrong there. Turning on CHATTY in src/system/kernel/arch/ppc/arch_elf.cpp and adding some additional CHATTY text. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 17:45:13 2009 From: trac at haiku-os.org (stippi) Date: Fri, 24 Jul 2009 15:45:13 -0000 Subject: [Haiku-bugs] [Haiku] #4119: Occasional incorrect behavior from Invalidate() In-Reply-To: <044.d3dbe78071a63efc6ec2acd1309d7680@haiku-os.org> References: <044.d3dbe78071a63efc6ec2acd1309d7680@haiku-os.org> Message-ID: <053.dd95816895e904e152abee77afeea82d@haiku-os.org> #4119: Occasional incorrect behavior from Invalidate() ---------------------------------+------------------------------------------ Reporter: anevilyak | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31734. Intermediate solution by turning off a troublesome optimization. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 17:58:00 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 24 Jul 2009 15:58:00 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.dae3e0df0f9a4112bb45ae4030610140@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): After some trial and error I figured out the following: On my PPC PowerBook Lombard: kernel/arch/ppc/arch_elf.cpp is not getting used. kernel/arch/m68k/arch_elf.cpp is getting used. This is where the error is coming from. I am working on enabling chatty in the m68k code.. is this right? Should kernel/arch/m68k be used? If the m68k directory is correct.. what is the PPC directory in the source tree for? --Alex -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:02:52 2009 From: trac at haiku-os.org (humdinger) Date: Fri, 24 Jul 2009 16:02:52 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views Message-ID: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r31560. I originally reported these two (related?) bugs to ArmyKnifes bugtracker: * [http://dev.osdrawer.net/issues/show/283 Bug #283][[BR]] * [http://dev.osdrawer.net/issues/show/286 Bug #286] Jonas discovered the same issues with DataTranslations and FileTypes preferences, it's also seen in ScreenSaver and Sounds: If you select all items in a list with ALT+A right/left clicking or ALT+left clicking into the list has weird effects. Also, selecting more items via SHIFT+CursorUP/DOWN doesn't work as expected:[[BR]] 1. Select an entry in the middle.[[BR]] 2. Hold down SHIFT and move down with CURSOR-DOWN twice[[BR]] --> 3 entries are selected.[[BR]] 3. Keep holding SHIFT and move one up with CURSOR-UP[[BR]] --> The last selected entry should get unselected, but isn't.[[BR]] (The actual ArmyKnife bug is a bit different, but maybe related, see bug 283 linked above.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:03:23 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 16:03:23 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.da64ca3b8ccb61591cca0b256e87b666@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: axeld => mmu_man Comment: That is most definitely incorrect, and implies an error in the Jamfiles somewhere. M68K is as its name implies, code specific to the Motorola 680x0 CPUs (specifically Atari Falcon), and as such is fundamentally incompatible with the PPC port. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:15:05 2009 From: trac at haiku-os.org (humdinger) Date: Fri, 24 Jul 2009 16:15:05 -0000 Subject: [Haiku-bugs] [Haiku] #4121: A link to WikiFormatting Message-ID: <044.455a06047e607a23c7c6997373b61c46@haiku-os.org> #4121: A link to WikiFormatting --------------------------+------------------------------------------------- Reporter: humdinger | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- I often struggle to remember Trac's Wiki magic.[[BR]] How about a nice little link to http://dev.haiku- os.org/wiki/WikiFormatting in the NewTicket form? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:16:31 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 16:16:31 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.bea640c86770b2a259ddceb0cf515751@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by anevilyak): * owner: axeld => anevilyak Comment: I'm almost certainly to blame for that one...will look into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:29:31 2009 From: trac at haiku-os.org (idefix) Date: Fri, 24 Jul 2009 16:29:31 -0000 Subject: [Haiku-bugs] [Haiku] #4121: A link to WikiFormatting In-Reply-To: <044.455a06047e607a23c7c6997373b61c46@haiku-os.org> References: <044.455a06047e607a23c7c6997373b61c46@haiku-os.org> Message-ID: <053.da18cfa9fb910eef5495c7c14fcbf32b@haiku-os.org> #4121: A link to WikiFormatting --------------------------+------------------------------------------------- Reporter: humdinger | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by idefix): I second that. I always find it strange that there is a link when you comment on a ticket, but not when you create a new ticket. BTW: It seems [http://trac.edgewall.org/ticket/8390 Ulrich] agrees with us. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:45:47 2009 From: trac at haiku-os.org (idefix) Date: Fri, 24 Jul 2009 16:45:47 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. In-Reply-To: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> References: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> Message-ID: <050.fceb7cce309284bc695f5cf01c95c49d@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. --------------------------+------------------------------------------------- Reporter: idefix | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: 4113 | Platform: All Blocking: 4117 | --------------------------+------------------------------------------------- Comment(by idefix): It looks like Phil updated the Build Factory: the r31728 image got past the point of error without an error. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 18:52:29 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 16:52:29 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.45aa95799d17b1b0abbc583017fec007@haiku-os.org> #4113: mbtowc() is unusable -----------------------+---------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 4116 | -----------------------+---------------------------------------------------- Comment(by anevilyak): Please try again with http://haiku-files.org/raw/haiku-pre-alpha- gcc4-r31728-raw.zip . -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 19:35:38 2009 From: trac at haiku-os.org (stippi) Date: Fri, 24 Jul 2009 17:35:38 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.7bd182af3e497f33447b9cb9bfa4b0a6@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): Shame on me for not reporting this myself, but I've seen this for ages in WonderBrush, that must have been way earlier than your BListView refactoring and fixes. IIRC, BListView caches the first and last selected index. It's most likely something to do with that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 19:38:23 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 17:38:23 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.357c99a84170ae9e66d6637c60f8a0c9@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Replying to [comment:2 stippi]: > Shame on me for not reporting this myself, but I've seen this for ages in WonderBrush, that must have been way earlier than your BListView refactoring and fixes. Will deal with it regardless, I'm at least quite familiar with BListView's code at this point :) Thanks for the heads up in any event. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 19:42:59 2009 From: trac at haiku-os.org (idefix) Date: Fri, 24 Jul 2009 17:42:59 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. In-Reply-To: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> References: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> Message-ID: <050.d12139b0658791d0ec72970b639e01be@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. --------------------------+------------------------------------------------- Reporter: idefix | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: 4113 | Platform: All Blocking: 4117 | --------------------------+------------------------------------------------- Comment(by idefix): ...And it just finished building libroot.so without any errors! :) This ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 19:46:53 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 17:46:53 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. In-Reply-To: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> References: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> Message-ID: <050.14951ab0cfdcaa6135f01c5ab534d96f@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. --------------------------+------------------------------------------------- Reporter: idefix | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: 4113 | Platform: All Blocking: 4117 | --------------------------+------------------------------------------------- Comment(by anevilyak): Will do as soon as we have confirmation that #4113 is resolved as well. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 20:09:35 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 24 Jul 2009 18:09:35 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.34132c7ea6393888101fee2df3e789fd@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): It seems there is a bug in the Jamfile and changing a source file and rebuilding without cleaning will not include the changes in the new haiku- image. We are in fact running kernel/arch/ppc/ vs m68k. please ignore my previous comment. (man I wish there was an edit option in trac for users) I am attaching a patch which lets the boot continue further and provides some context around the issue. (the patch ppcarch_elf_forcerelocate.patch is NOT a fix, but simply shows the issue better) I will post the results here shortly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 20:46:06 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 24 Jul 2009 18:46:06 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.e192d14eb54ef055a33b26d96cc55ee8@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): ok, here is what happens. When the failure to relocate entry happens, vlErr is set to -2147478780 each time. {{{ Here are the last of the "Failed to relocate entry index X type X" messages... Entry Type 1346 21 1347 1 1348 21 1349 1 1350 21 7002 1 7003 21 7004 1 7005 21 7006 1 7007 21 7008 1 7009 21 7010 1 7011 21 7012 1 7013 21 9087 21 Kernel entry at: 0x8007b7c8 Kernel stack top: 0x80004000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 21:13:31 2009 From: trac at haiku-os.org (tqh) Date: Fri, 24 Jul 2009 19:13:31 -0000 Subject: [Haiku-bugs] [Haiku] #4122: Copying huge dirs to image fails in populating image. Message-ID: <038.1525fbe9dd6b8c713144e38cd5cb7046@haiku-os.org> #4122: Copying huge dirs to image fails in populating image. --------------------------+------------------------------------------------- Reporter: tqh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Adding mozilla source to image, fails with weird errors: {{{ BuildHaikuImage1 /dev/sda3 /dev/sda3 Creating image ... Writing boot code to "/dev/sda3" (partition offset: 120006835200 bytes, start offset = 0) ... Populating image ... could not create mutexError: Unexpected end of fs_shell reply. Was still expecting 4 bytes Error: Failed to open connection to FS shell: Connection refused Error: Failed to open connection to FS shell: Connection refused Error: Failed to open connection to FS shell: Connection refused Error: Failed to open connection to FS shell: Connection refused ... ... }}} I build from xubuntu-x64, sda3 is a 60GB partition and the added line to UserBuildConfig that fails the build below: {{{ CopyDirectoryToHaikuImage home : /home/frho/projects/mozilla : : -L ; }}} Removing it causes the build to succeed and I have another similar line for a smaller dir that doesn't cause this. The mozilla dir was created by: {{{ export CVSROOT=:pserver:anonymous at cvs-mirror.mozilla.org:/cvsroot export MOZ_CO_PROJECT=browser cvs co -r MOZILLA_1_8_BRANCH mozilla/client.mk cd mozilla make -f client.mk checkout }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 21:26:53 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 19:26:53 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.7b1aa758e63c1f17ab7ecaccdd454109@haiku-os.org> #4113: mbtowc() is unusable ------------------------+--------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 4116 ------------------------+--------------------------------------------------- Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Confirmed fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 21:27:12 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 24 Jul 2009 19:27:12 -0000 Subject: [Haiku-bugs] [Haiku] #4116: Unable to build libroot.so: Unexpected end of input. In-Reply-To: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> References: <041.49719b3fdc46b97d7b63c1ffd27c3885@haiku-os.org> Message-ID: <050.3748619e3b0c8672a4522d814460e8a3@haiku-os.org> #4116: Unable to build libroot.so: Unexpected end of input. ---------------------------+------------------------------------------------ Reporter: idefix | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: 4113 Platform: All | Blocking: 4117 ---------------------------+------------------------------------------------ Changes (by anevilyak): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 22:23:04 2009 From: trac at haiku-os.org (tqh) Date: Fri, 24 Jul 2009 20:23:04 -0000 Subject: [Haiku-bugs] [Haiku] #4122: Copying huge dirs to image fails in populating image. In-Reply-To: <038.1525fbe9dd6b8c713144e38cd5cb7046@haiku-os.org> References: <038.1525fbe9dd6b8c713144e38cd5cb7046@haiku-os.org> Message-ID: <047.6da13f122c0ddd555c073ccb2909be69@haiku-os.org> #4122: Copying huge dirs to image fails in populating image. --------------------------+------------------------------------------------- Reporter: tqh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by tqh): From Monni on IRC: {{{ fs_shell should be able to copy about 40960 files without bailing out... http://dev.haiku- os.org/browser/haiku/trunk/src/build/libroot/sem.cpp#L19 ... each file in copy process uses one semaphore }}} Number of files: {{{ mozilla$ find ./ -type f | wc -l 40457 }}} So I guess it's that limit I hit, dunno if it's worth fixing. I can copy over just a zip instead. Unzipping in build gives same kind of failure btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 22:27:16 2009 From: trac at haiku-os.org (kaliber) Date: Fri, 24 Jul 2009 20:27:16 -0000 Subject: [Haiku-bugs] [Haiku] #4122: Copying huge dirs to image fails in populating image. In-Reply-To: <038.1525fbe9dd6b8c713144e38cd5cb7046@haiku-os.org> References: <038.1525fbe9dd6b8c713144e38cd5cb7046@haiku-os.org> Message-ID: <047.67ebed91a0ee39d6e8515b66d0174f16@haiku-os.org> #4122: Copying huge dirs to image fails in populating image. --------------------------+------------------------------------------------- Reporter: tqh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by kaliber): Looks like that 40k semaphores is not enough - http://dev.haiku- os.org/changeset/26816 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 24 22:49:56 2009 From: trac at haiku-os.org (mmu_man) Date: Fri, 24 Jul 2009 20:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.9cf0691b64bf1f3e426c653b93424f08@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Changes (by mmu_man): * status: new => assigned Comment: The error is: 0x80001304: Symbol not found -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 10:55:22 2009 From: trac at haiku-os.org (cyberguijarro) Date: Sat, 25 Jul 2009 08:55:22 -0000 Subject: [Haiku-bugs] [Haiku] #3651: Possible CharacterMap enhancements (easy) In-Reply-To: <044.28d50f6b6c97bdc90cb67ef486991747@haiku-os.org> References: <044.28d50f6b6c97bdc90cb67ef486991747@haiku-os.org> Message-ID: <053.22a5e107a411dde5bc30df3fd2a1a058@haiku-os.org> #3651: Possible CharacterMap enhancements (easy) ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Changes (by cyberguijarro): * cc: cyberguijarro@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 11:44:13 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 09:44:13 -0000 Subject: [Haiku-bugs] [Haiku] #3863: Canceling shutdown blames application In-Reply-To: <048.35b694c21fefeda8bc767842f01818d0@haiku-os.org> References: <048.35b694c21fefeda8bc767842f01818d0@haiku-os.org> Message-ID: <057.d1d1d7e9efecee4e80097950ee87104e@haiku-os.org> #3863: Canceling shutdown blames application -------------------------------+-------------------------------------------- Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by idefix): I have created [attachment:registrar.patch a patch] that will fix this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 12:52:39 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 10:52:39 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume Message-ID: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- When you have a illegal volume name like `installer/test`, it gets validated to `installer-test`.[[BR]] But when DriveSetup initialises the volume, it doesn't use the validated name, but the pre-validated one: [[Image(DriveSetupError.png)]] Attached [attachment:drivesetup.patch patch] fixes this behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 13:08:17 2009 From: trac at haiku-os.org (diver) Date: Sat, 25 Jul 2009 11:08:17 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.71d1bb0ffc251a320ad6745bd5c240b3@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by diver): While you at it there is an extra space in the alert string:[[BR]] {{{ Initialization of the partition__"test" failed. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 13:11:06 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 11:11:06 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.6c5ad192d07928d5084795a8c20fa531@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): I just noticed a double space in the error dialog text, which [attachment:drivesetupspace.patch this patch] will fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 13:12:29 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 11:12:29 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.111f0fdd40c8d319ad91b15a4fd8d334@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:1 diver]: > While you at it there is an extra space in the alert string:[[BR]] > {{{ > Initialization of the partition__"test" failed. > }}} Yeah, I noticed that too. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 16:20:59 2009 From: trac at haiku-os.org (kallisti5) Date: Sat, 25 Jul 2009 14:20:59 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.2a2a98bc7ec5be53801965f0c1c697ec@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): The boot process is getting hung up right after the "Kernel stack top" message. Looking through the sources this is where we jump to the kernel which has now been copied into memory. mmu_man, Where are you getting the Symbol not found message from? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 18:44:19 2009 From: trac at haiku-os.org (stippi) Date: Sat, 25 Jul 2009 16:44:19 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.9ef02af2e5fe294de3aa51d4c6359c56@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => assigned Comment: Thanks for the patches, will apply them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 19:16:30 2009 From: trac at haiku-os.org (diver) Date: Sat, 25 Jul 2009 17:16:30 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.35ff48208570d14000e21a7bb3b3f6d2@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by diver): Stippi, should I open another bug described in the last two screenshots? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 19:34:30 2009 From: trac at haiku-os.org (stippi) Date: Sat, 25 Jul 2009 17:34:30 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.8adef2e9b33387d7d1e27c41c2b7319b@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): No, it's ok to keep it in this ticket I guess. Do you mean the problem is that DriveSetup should force you to enter a name? (I think it should.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 20:07:49 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 18:07:49 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.dc465810ecdc59b407d44fadc0dad2c9@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): Or it could assign a default name like `Unnamed`; that's how [source:/haiku/trunk/src/bin/mkfs/main.cpp#L138 mkfs] does it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 20:12:27 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 18:12:27 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.d605c9a7a2a7718b66b7415131d3fa74@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): BTW: I have another patch coming to fix DriveSetups handling of a volume name with a space in it. I was thinking of opening another ticket for this patch, but I could also attach it to this one if you keep it open for the bug described by diver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 21:12:50 2009 From: trac at haiku-os.org (stippi) Date: Sat, 25 Jul 2009 19:12:50 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.7c910476cf090eb0161b8479179a4aad@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): Actually, Bryce could maybe also handle this, since he is working on DriveSetup anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jul 25 21:17:20 2009 From: trac at haiku-os.org (idefix) Date: Sat, 25 Jul 2009 19:17:20 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.43db6d263be1a33df0fce1d5e495a276@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): Well, this [attachment:bfsaddon.patch patch] will fix the volume-name- contains-spaces-bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 04:22:29 2009 From: trac at haiku-os.org (kallisti5) Date: Sun, 26 Jul 2009 02:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.c7a0a02a30b7886ed2e5d62b8f97fd1a@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): Quick note... Tried the same image on a G4 quicksilver PPC and got the exact same error and result. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:04:20 2009 From: trac at haiku-os.org (korli) Date: Sun, 26 Jul 2009 12:04:20 -0000 Subject: [Haiku-bugs] [Haiku] #1352: echo24 driver: no support for 24 bit and 96kHz sample rate In-Reply-To: <041.c9096c1dcca27e57347bcbeb5d8a0930@haiku-os.org> References: <041.c9096c1dcca27e57347bcbeb5d8a0930@haiku-os.org> Message-ID: <050.2a0ad98b832341d0e4fbebfdf0717c5f@haiku-os.org> #1352: echo24 driver: no support for 24 bit and 96kHz sample rate ----------------------------+----------------------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31760. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:06:18 2009 From: trac at haiku-os.org (korli) Date: Sun, 26 Jul 2009 12:06:18 -0000 Subject: [Haiku-bugs] [Haiku] #3053: echo24 driver; recording only 16 bit, 44.1kHz (R5), 16 bit, 44.1,48kHz (Haiku) + buggy In-Reply-To: <041.2c6cdcc87c90a0b0ea6760bd197da61c@haiku-os.org> References: <041.2c6cdcc87c90a0b0ea6760bd197da61c@haiku-os.org> Message-ID: <050.e9e784e7ecf041d6594afe341825dc52@haiku-os.org> #3053: echo24 driver; recording only 16 bit, 44.1kHz (R5), 16 bit, 44.1,48kHz (Haiku) + buggy ---------------------------+------------------------------------------------ Reporter: nutela | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by korli): If serial output is disabled, clicks shouldn't appear. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:09:28 2009 From: trac at haiku-os.org (korli) Date: Sun, 26 Jul 2009 12:09:28 -0000 Subject: [Haiku-bugs] [Haiku] #3323: [SoundRecorder] Divide error In-Reply-To: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> References: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> Message-ID: <049.b4dfc4ed999ec3942053fa9cc787359a@haiku-os.org> #3323: [SoundRecorder] Divide error ----------------------------------------+----------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------------+----------------------------------- Comment(by korli): Is it still reproducible ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:11:47 2009 From: trac at haiku-os.org (korli) Date: Sun, 26 Jul 2009 12:11:47 -0000 Subject: [Haiku-bugs] [Haiku] #2962: clicking rec button in Soundrecorder crashes it, only with 24 bit input In-Reply-To: <041.7926194ef4616f9c918821d5bbfd31a5@haiku-os.org> References: <041.7926194ef4616f9c918821d5bbfd31a5@haiku-os.org> Message-ID: <050.5d9f3c0a783c3b2f456795e22f795641@haiku-os.org> #2962: clicking rec button in Soundrecorder crashes it, only with 24 bit input -----------------------------------------+---------------------------------- Reporter: nutela | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------------------+---------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31760 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:26:10 2009 From: trac at haiku-os.org (diver) Date: Sun, 26 Jul 2009 12:26:10 -0000 Subject: [Haiku-bugs] [Haiku] #4124: [app_server] crash in EventDispatcher::_AddTokens () Message-ID: <040.d86b2f76747ba2adcb67e7d725f1ba79@haiku-os.org> #4124: [app_server] crash in EventDispatcher::_AddTokens () --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I tried to reproduce #3323 and got a crash.[[BR]] backtrace included as attachment[[BR]] r31761 in Virtualbox. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:28:18 2009 From: trac at haiku-os.org (diver) Date: Sun, 26 Jul 2009 12:28:18 -0000 Subject: [Haiku-bugs] [Haiku] #3323: [SoundRecorder] Divide error In-Reply-To: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> References: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> Message-ID: <049.e58b05ebc5324858fe6b117a7755916d@haiku-os.org> #3323: [SoundRecorder] Divide error ----------------------------------------+----------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------------+----------------------------------- Comment(by diver): Still crashes. r31761 in virtualbox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 14:50:43 2009 From: trac at haiku-os.org (diver) Date: Sun, 26 Jul 2009 12:50:43 -0000 Subject: [Haiku-bugs] [Haiku] #3323: [SoundRecorder] Divide error In-Reply-To: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> References: <040.6b49d818d73bf30679c8c0b0a63d2e0d@haiku-os.org> Message-ID: <049.88da8dfb44045317ab402f9002813c3f@haiku-os.org> #3323: [SoundRecorder] Divide error ----------------------------------------+----------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------------+----------------------------------- Comment(by diver): r31765 fixed this crash, but there are still several problems with record button and OS reaction on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 16:23:06 2009 From: trac at haiku-os.org (schily) Date: Sun, 26 Jul 2009 14:23:06 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.4ffb40b2ed822c4646c3597accb3454d@haiku-os.org> #4113: mbtowc() is unusable ------------------------+--------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 4116 ------------------------+--------------------------------------------------- Comment(by schily): OK, it now works with the gcc4 version -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 16:31:52 2009 From: trac at haiku-os.org (schily) Date: Sun, 26 Jul 2009 14:31:52 -0000 Subject: [Haiku-bugs] [Haiku] #3412: stdio library code dishonors BUFSIZ for setbuf() In-Reply-To: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> References: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> Message-ID: <050.058809fe0cfc1abe5cc3b5b4c6e26360@haiku-os.org> #3412: stdio library code dishonors BUFSIZ for setbuf() -----------------------+---------------------------------------------------- Reporter: schily | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by schily): Even with haiku-pre-alpha-gcc4-r31728-raw.zip BUFSIZE is not honored and the stdio code in libc overwrites the buffer resulting in a core dump. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 17:18:18 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 15:18:18 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder In-Reply-To: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> References: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> Message-ID: <050.45668a3c2230e0c100fbfc3cafd34eb7@haiku-os.org> #3859: Files disappear, always the same folder ----------------------------+----------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: File Systems/BFS => System/Kernel Comment: There are obvious corruption problems on this disk (which are probably already tracked in another ticket), however, the missing files were caused by an over-active fix_dirents() in vfs.cpp which has been fixed in r31775. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 17:29:34 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 26 Jul 2009 15:29:34 -0000 Subject: [Haiku-bugs] [Haiku] #3412: stdio library code dishonors BUFSIZ for setbuf() In-Reply-To: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> References: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> Message-ID: <050.d8e7bc613b65dcb0ce295c0c1b9d0fdc@haiku-os.org> #3412: stdio library code dishonors BUFSIZ for setbuf() ------------------------+--------------------------------------------------- Reporter: schily | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r31776. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:27:33 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:27:33 -0000 Subject: [Haiku-bugs] [Haiku] #4034: BFS partition became read-only In-Reply-To: <041.fd6d44ddc05477bb95a6a87853e353df@haiku-os.org> References: <041.fd6d44ddc05477bb95a6a87853e353df@haiku-os.org> Message-ID: <050.06bbd8e619a066068303347333bbf14e@haiku-os.org> #4034: BFS partition became read-only -------------------------------+-------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Since the syslog mentions double indirect blocks, I'm closing this one as I fixed a serious error there in r31767. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:29:10 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:29:10 -0000 Subject: [Haiku-bugs] [Haiku] #3808: Copying or creating large files causes General System Error In-Reply-To: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> References: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> Message-ID: <049.81730ff41a3bb65b5ba5d0430ce3fee4@haiku-os.org> #3808: Copying or creating large files causes General System Error -------------------------------+-------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This is probably related to the problems of double indirect blocks I fixed in r31767. In any case, there isn't enough information to assume anything else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:30:07 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:30:07 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build In-Reply-To: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> References: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> Message-ID: <049.76c22d03fe76b51a946e6ce3b1355d6f@haiku-os.org> #3932: BFS corrupted during very large project build -------------------------------+-------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: duplicate | Blockedby: 3150 Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 3150 Comment: As this info is not really helpful, I'll just regard it as a duplicate of #3150. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:30:34 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:30:34 -0000 Subject: [Haiku-bugs] [Haiku] #4011: BFS-Errors if trash is emptied In-Reply-To: <042.d409952ec97f9da409da22d25794d6db@haiku-os.org> References: <042.d409952ec97f9da409da22d25794d6db@haiku-os.org> Message-ID: <051.2fa7e28772411cfd085abe2a145d0a35@haiku-os.org> #4011: BFS-Errors if trash is emptied -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: duplicate | Blockedby: 3150 Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 3150 Comment: You obviously managed to corrupt your BFS disk (ie. you ran into some Haiku bug). Since this ticket does not contain any helpful information that distinct it from other tickets, I'll close it as a duplicate of #3150. Please note that the "checkfs" utility should now be able to solve these problems (since r31775). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:32:14 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:32:14 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.65513876832b44d0f38d0c76792f9f8c@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit -------------------------------+-------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Since this one hasn't been seen again, and I couldn't find anything suspicious by proof-reading the code, I'm now closing this as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:33:29 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:33:29 -0000 Subject: [Haiku-bugs] [Haiku] #4037: Tracker crash post-initialization In-Reply-To: <038.43ea1e4769efbd07f9578b1063c0f9fc@haiku-os.org> References: <038.43ea1e4769efbd07f9578b1063c0f9fc@haiku-os.org> Message-ID: <047.c3ba595a08e0f927f14f3998389b14d0@haiku-os.org> #4037: Tracker crash post-initialization ----------------------------------+----------------------------------------- Reporter: dvh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by axeld): * component: File Systems/BFS => Applications/Tracker -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 18:47:45 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 16:47:45 -0000 Subject: [Haiku-bugs] [Haiku] #4037: Tracker crash post-initialization In-Reply-To: <038.43ea1e4769efbd07f9578b1063c0f9fc@haiku-os.org> References: <038.43ea1e4769efbd07f9578b1063c0f9fc@haiku-os.org> Message-ID: <047.a3be91eb7185e0b70e23583a5e1ccf1c@haiku-os.org> #4037: Tracker crash post-initialization -----------------------------------+---------------------------------------- Reporter: dvh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: It looks like something might be wrong with your MIME database, BContainerWindow::AddMimeMenu() did not check whether or not the MIME type was valid, and there was at least one invocation where this was not checked either. In any case, the MIME type could become messed up if you build Haiku under Linux without using xattr support (but there is already a ticket for that somewhere). The crash itself should be fixed in r31777. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 19:27:57 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 17:27:57 -0000 Subject: [Haiku-bugs] [Haiku] #4045: mkfs ignores noindex option first time when no argument is supplied In-Reply-To: <041.6b2069907d184b5735c82139e02b5d1f@haiku-os.org> References: <041.6b2069907d184b5735c82139e02b5d1f@haiku-os.org> Message-ID: <050.b1c474df965c16a24a7376c503054a1f@haiku-os.org> #4045: mkfs ignores noindex option first time when no argument is supplied ----------------------------+----------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: File Systems/BFS => System/Kernel Comment: Fixed in r31779. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 19:28:57 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 17:28:57 -0000 Subject: [Haiku-bugs] [Haiku] #2490: File version as on VMS (DEC VAX) In-Reply-To: <038.05578fbde91413a4e84bcb8f3eaaa7cc@haiku-os.org> References: <038.05578fbde91413a4e84bcb8f3eaaa7cc@haiku-os.org> Message-ID: <047.8ca6bdcdfe3a4c231729b5419269ddd9@haiku-os.org> #2490: File version as on VMS (DEC VAX) ------------------------------+--------------------------------------------- Reporter: FSV | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Component: File Systems/BFS | Version: Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => low -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 19:31:29 2009 From: trac at haiku-os.org (bbjimmy) Date: Sun, 26 Jul 2009 17:31:29 -0000 Subject: [Haiku-bugs] [Haiku] #4113: mbtowc() is unusable In-Reply-To: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> References: <041.28c5a7234011f31ac5aa51b0fdda9f46@haiku-os.org> Message-ID: <050.8a09b66453d3785b9307bcb7daab285d@haiku-os.org> #4113: mbtowc() is unusable ------------------------+--------------------------------------------------- Reporter: schily | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 4116 ------------------------+--------------------------------------------------- Comment(by bbjimmy): fixes the gensyscalls issue using gcc2. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 19:38:34 2009 From: trac at haiku-os.org (axeld) Date: Sun, 26 Jul 2009 17:38:34 -0000 Subject: [Haiku-bugs] [Haiku] #1242: Inode::WriteAttribute() does not work correctly for small_data items In-Reply-To: <040.5254c83612dad72aa5d51f880c2a9681@haiku-os.org> References: <040.5254c83612dad72aa5d51f880c2a9681@haiku-os.org> Message-ID: <049.dac02716b368b3bec8cb85cb7864199c@haiku-os.org> #1242: Inode::WriteAttribute() does not work correctly for small_data items ------------------------------+--------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Indeed, r31313 improved the situation considerably, but there are still remaining problems that warrant to keep this ticket open. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 22:55:04 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 26 Jul 2009 20:55:04 -0000 Subject: [Haiku-bugs] [Haiku] #4084: Lack 1440x900 resolutoion In-Reply-To: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> References: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> Message-ID: <050.463aac79479e2455fe03399b3f7fa323@haiku-os.org> #4084: Lack 1440x900 resolutoion -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, (back from holiday) Since three weeks the driver asks the monitor for it's specs, and it nolonger offers (most) non-compatible modes. Can you place the file nvidia.settings in your home/config/settings/kernel/drivers folder, enable full logging, and upload the resulting logfile here? Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 23:14:06 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 26 Jul 2009 21:14:06 -0000 Subject: [Haiku-bugs] [Haiku] #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 In-Reply-To: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> References: <043.94a9d8fd87bf5a7def568413b7b90456@haiku-os.org> Message-ID: <052.bc8ac421c7ee3d9dbbd97405a90c75cc@haiku-os.org> #4074: eMachines 19" WS LCD monitor native resolution not avail. using AGP Geforce 2/3 -------------------------------------+-------------------------------------- Reporter: Luposian | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, Ticket #4084 might be the same problem. Apparantly something goes wrong with autodetection of the capabilities of your monitor. Please upload a logfile from the driver. Please use a default nvidia.settings file with only the line 'full logging' enabled, otherwise I won't get all the correct info maybe. So your monitor won't startup in the native resolution. For your info: the driver is actually working OK (apart from the missing modeline that is). force_ws is indeed a emergency option to get what you want because the driver somehow misbehaves, your gfx card misbehaves or your monitor misbehaves. nvidia.settings in not required unless troubleshooting, or some hardware was incorrectly manufactured (bios faults might be an issue for instance). It might be that on windows it behaves OK after all, but then again, I don't have all info that nvidia has, so I can't workaround all errors. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jul 26 23:14:53 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 26 Jul 2009 21:14:53 -0000 Subject: [Haiku-bugs] [Haiku] #4084: Lack 1440x900 resolutoion In-Reply-To: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> References: <041.cd6c43eeba19a20b979ea71328fb6e99@haiku-os.org> Message-ID: <050.aa27f40234ecb5e605cbaef3f9dc42f5@haiku-os.org> #4084: Lack 1440x900 resolutoion -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, seems bug #4074 might be the same problem... Still, please upload a logfile! Thanks, Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 00:18:45 2009 From: trac at haiku-os.org (brecht) Date: Sun, 26 Jul 2009 22:18:45 -0000 Subject: [Haiku-bugs] [Haiku] #4125: [userlandfs] NULL device is translated to '//' Message-ID: <041.04836bffb71abf987b2f417734d7c985@haiku-os.org> #4125: [userlandfs] NULL device is translated to '//' --------------------------+------------------------------------------------- Reporter: brecht | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- UserlandFS passes '//' as the device to the FS when no device has been specified when mounting it. source:haiku/trunk/src/add- ons/kernel/file_systems/userlandfs/server/UserlandRequestHandler.cpp at 29872#L233 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 03:40:40 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 27 Jul 2009 01:40:40 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards In-Reply-To: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> References: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> Message-ID: <048.30793172441688e5c081209ceb919c3e@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3573, 3936 -----------------------------------+---------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Full generic HID support is finally added in r31790. Please report bugs with that new implementation in bug reports. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 03:41:27 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 27 Jul 2009 01:41:27 -0000 Subject: [Haiku-bugs] [Haiku] #2955: using multiple USB HIDs not possible, USB input devices stop working In-Reply-To: <041.b8215043ff83d47c88b4fc90910cf677@haiku-os.org> References: <041.b8215043ff83d47c88b4fc90910cf677@haiku-os.org> Message-ID: <050.103794c791e8b14194caa3cac4a1b238@haiku-os.org> #2955: using multiple USB HIDs not possible, USB input devices stop working -------------------------------+-------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Comment(by mmlr): Please check with the reworked usb_hid driver in r31790 and up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 08:27:09 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 27 Jul 2009 06:27:09 -0000 Subject: [Haiku-bugs] [Haiku] #4011: BFS-Errors if trash is emptied In-Reply-To: <042.d409952ec97f9da409da22d25794d6db@haiku-os.org> References: <042.d409952ec97f9da409da22d25794d6db@haiku-os.org> Message-ID: <051.7a69e720759b2c5b21568873005c3320@haiku-os.org> #4011: BFS-Errors if trash is emptied -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: duplicate | Blockedby: 3150 Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by jahaiku): Replying to [comment:1 axeld]: > You obviously managed to corrupt your BFS disk (ie. you ran into some Haiku bug). Since this ticket does not contain any helpful information that distinct it from other tickets, I'll close it as a duplicate of #3150. Only for info: As I remember this was a fresh install and then creating and deleting a little (Textfile with some bytes) file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 08:33:28 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 27 Jul 2009 06:33:28 -0000 Subject: [Haiku-bugs] [Haiku] #4126: Additional Package: nano Message-ID: <042.3fe5e4b547528dda4c5575367acfa2aa@haiku-os.org> #4126: Additional Package: nano -----------------------+---------------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I have installed the additional package Nano on a recent gcc4 build. But when I try to start it I get the following error:[[BR]] Error opening terminal: xterm. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 14:12:27 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 12:12:27 -0000 Subject: [Haiku-bugs] [Haiku] #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window Message-ID: <040.c884610af89068fa558501c97f7d319e@haiku-os.org> #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Open Home floder from Desktop[[BR]] Press Ctrl+Alt+H to hide this window[[BR]] Go to Deskbar->Tracker[[BR]] Screenshot attached[[BR]] Tested in r31799 in virtualbox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 14:17:02 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 12:17:02 -0000 Subject: [Haiku-bugs] [Haiku] #2499: [Keymap] Hotkeys doesn't work with Russian keymap In-Reply-To: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> References: <040.4a4540d7ef968b4ed625f4c273a0ed47@haiku-os.org> Message-ID: <049.80306a5f26367dece677bd32107f09f6@haiku-os.org> #2499: [Keymap] Hotkeys doesn't work with Russian keymap -----------------------------------+---------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Filters | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): Anything else I could try? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 14:19:57 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 12:19:57 -0000 Subject: [Haiku-bugs] [Haiku] #4128: [Tracker] CountView display question marks when using context search with russian keymap Message-ID: <040.dd3fdb54d2c7f5d6890ca852a6b152bf@haiku-os.org> #4128: [Tracker] CountView display question marks when using context search with russian keymap ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- CountView area in Tracker window shows question marks when I try to use context search (type ahead?)[[BR]] Screenshot attached[[BR]] Tested in r31799 in virtualbox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 14:52:43 2009 From: trac at haiku-os.org (idefix) Date: Mon, 27 Jul 2009 12:52:43 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.7d3cda4c2d8bdd6fcf72fb7793a66f6c@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): Replying to [comment:7 idefix]: > Or it could assign a default name like `Unnamed`; that's how [source:/haiku/trunk/src/bin/mkfs/main.cpp#L138 mkfs] does it. [attachment:drivesetupunnamedvolume.patch This patch] makes DriveSetup do it the same way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 15:28:28 2009 From: trac at haiku-os.org (axeld) Date: Mon, 27 Jul 2009 13:28:28 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.231610b9a312abf1a5c5efc8b3e620c0@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: closed => reopened * resolution: invalid => * component: File Systems/BFS => System/Kernel Comment: That's a nice coincidence: after 11 months of silence, and after having closed this bug just yesterday, Michael ran into it just today. Investigating... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 15:46:23 2009 From: trac at haiku-os.org (bga) Date: Mon, 27 Jul 2009 13:46:23 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.81168ef6954d3dd68d93569c6dc08054@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): Hi Axel. Just some criticism I hope you take constructively: You have been closing bugs based on the fact that no one else reported any more occurrences of it and, as this just showed, this is not a good idea. A bug should only be closed if you can pinpoint what fixed it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:18:29 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 14:18:29 -0000 Subject: [Haiku-bugs] [Haiku] #4083: Rename some menu strings (easy) In-Reply-To: <044.fd00425ef89636ff9d9c3bc07d1bec10@haiku-os.org> References: <044.fd00425ef89636ff9d9c3bc07d1bec10@haiku-os.org> Message-ID: <053.b0c1981de1387bb858ac788bd49d2160@haiku-os.org> #4083: Rename some menu strings (easy) ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: In r31805, I kept "File | Append...", since I still think it's the most fitting. The shapes, paths and styles are appended at the end of the existing lists after all. The ellipsis were cleaned up in the File and Path menu. Property wasn't so bad, since it was supposed to form a sentence with the menu items, but maybe Properties is indeed better, so I changed it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:23:33 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 14:23:33 -0000 Subject: [Haiku-bugs] [Haiku] #4082: Disable/Implement transformer "Transformation" and "Perspective" In-Reply-To: <044.c1678087317522c63479ce60487d10e7@haiku-os.org> References: <044.c1678087317522c63479ce60487d10e7@haiku-os.org> Message-ID: <053.4e23a6b744bef41d4c0f69c7c94043cb@haiku-os.org> #4082: Disable/Implement transformer "Transformation" and "Perspective" ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r31807. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:23:44 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 14:23:44 -0000 Subject: [Haiku-bugs] [Haiku] #4129: [Workspaces] there is no need to show name of itself in replicant mode Message-ID: <040.7667d5a70c53f5f70d60ecf2722634d3@haiku-os.org> #4129: [Workspaces] there is no need to show name of itself in replicant mode -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- There is no need to show name of itself in Workspaces (replicant mode).[[BR]] See screenshot -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:36:17 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 14:36:17 -0000 Subject: [Haiku-bugs] [Haiku] #4081: Wrong shortcut label in context menu (easy) In-Reply-To: <044.d4fa99be0f5be6bf6b28db8de1ed02e1@haiku-os.org> References: <044.d4fa99be0f5be6bf6b28db8de1ed02e1@haiku-os.org> Message-ID: <053.d203a4cd0f7f17d604c205c6ab373529@haiku-os.org> #4081: Wrong shortcut label in context menu (easy) ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r31808. Only the "DEL" cannot currently be displayed as shortcut key in a BMenu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:40:17 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 14:40:17 -0000 Subject: [Haiku-bugs] [Haiku] #4080: Disable/Implement path property "Rounding" In-Reply-To: <044.382717922a2cc31f3719b5ed498a8b1c@haiku-os.org> References: <044.382717922a2cc31f3719b5ed498a8b1c@haiku-os.org> Message-ID: <053.fe6a355b55bb655a8e6147653dcdde81@haiku-os.org> #4080: Disable/Implement path property "Rounding" ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r31810. (Property is not displayed for the time being.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 16:43:29 2009 From: trac at haiku-os.org (axeld) Date: Mon, 27 Jul 2009 14:43:29 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.827f3378130e9d32d0fbcf5e1aa32539@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): Problem potentially fixed in r31809, at least the dead lock should be gone. If that bug decides to show up in another 11 months, we can just reopen it again, I guess :-) To bga: yes and no: first, I have closed bugs that did not distinct themselves from other, similar bugs, and did not contain any useful information. Then, I am closing bugs like this one (and will continue to do so) that happened once, but no one can reproduce this; there is no reason to keep those bugs open, it doesn't help anyone. But if a problem happens again, one can just reopen that ticket, no harm done. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 17:10:20 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 15:10:20 -0000 Subject: [Haiku-bugs] [Haiku] #4129: [Workspaces] there is no need to show name of itself in replicant mode In-Reply-To: <040.7667d5a70c53f5f70d60ecf2722634d3@haiku-os.org> References: <040.7667d5a70c53f5f70d60ecf2722634d3@haiku-os.org> Message-ID: <049.c07984eeef0e81bc2defe1552788fcc6@haiku-os.org> #4129: [Workspaces] there is no need to show name of itself in replicant mode --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: This is impossible. You must have turned off the border, which is different from true "replicant mode". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 17:22:37 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 15:22:37 -0000 Subject: [Haiku-bugs] [Haiku] #4129: [Workspaces] there is no need to show name of itself in replicant mode In-Reply-To: <040.7667d5a70c53f5f70d60ecf2722634d3@haiku-os.org> References: <040.7667d5a70c53f5f70d60ecf2722634d3@haiku-os.org> Message-ID: <049.4e35e2d85a769a42c1f54f3b11c2bbf1@haiku-os.org> #4129: [Workspaces] there is no need to show name of itself in replicant mode --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by diver): Ah, yeah, that's right, maybe it should not show it's name at all? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 17:42:09 2009 From: trac at haiku-os.org (axeld) Date: Mon, 27 Jul 2009 15:42:09 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.3cd1506c0885a9cfc0e585666776b421@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 18:13:09 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 16:13:09 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.d0a7d84170a42d2f1c64a82be152fd3d@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): To be honest, I think an alert requesting the user to enter a name may be a better solution. I think Bryce is even working on this already, but he is not on the Trac notification list, IIRC. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 18:23:04 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 16:23:04 -0000 Subject: [Haiku-bugs] [Haiku] #4130: [Tracker] crash in Model::StatChanged () Message-ID: <040.4c2354d150b815fa1ff9b8bf2acd61cf@haiku-os.org> #4130: [Tracker] crash in Model::StatChanged () ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I tried to zip Desktop folder using: {{{ zip -yr Desktop.zip Desktop/ }}} I have an opened query window for "zip"[[BR]] As soon as i executed this command tracker crashed.[[BR]] See screenshot[[BR]] r31814 in virtualbox -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 18:26:08 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 16:26:08 -0000 Subject: [Haiku-bugs] [Haiku] #3749: Tab drawing issue In-Reply-To: <048.adb208f924d195856c93d656fc2a88eb@haiku-os.org> References: <048.adb208f924d195856c93d656fc2a88eb@haiku-os.org> Message-ID: <057.08eedcb435be982ca5837cfe198b9e13@haiku-os.org> #3749: Tab drawing issue ---------------------------------+------------------------------------------ Reporter: jonas.kirilla | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31821. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 18:39:47 2009 From: trac at haiku-os.org (bga) Date: Mon, 27 Jul 2009 16:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.590f418bcf947cec0e6f6cf33102289b@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ----------------------------+----------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bga): I am not talking about duplicate bugs or bugs with no information whatsoever. I am talking about bugs (like this one) that you closed based solely on "no one reported it anymore". Bugs serve as documentation of problems that happened and that may happen again. That's why I think closing bugs based on the assumption that it fixed itself is wrong. But whatever. And, BTW, keeping the bug around also does not do any harm and, even better, serves a purpose. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 19:09:04 2009 From: trac at haiku-os.org (idefix) Date: Mon, 27 Jul 2009 17:09:04 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.3b14429d6113d83a0b468037786c9439@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): If you go that way, I would suggest to disable the `Initialize` button when the `Name` field is empty (see [attachment:DriveSetupError.png first screenshot]).[[BR]] The user is already shown quite a lot of alerts when initialising a volume. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:07:41 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 18:07:41 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.2e3568c474b028bcebdae1f901f0fab5@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): Ah yes, I think that's indeed the conclusion that Ingo and Bryce arrived at as well, IIRC. Sounds good to me. Still, I believe Bryce is already working on that one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:15:07 2009 From: trac at haiku-os.org (idefix) Date: Mon, 27 Jul 2009 18:15:07 -0000 Subject: [Haiku-bugs] [Haiku] #4123: [patch] DriveSetup doesn't use validated name when initialising volume In-Reply-To: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> References: <041.4da0880b83e4cf564029c3ab945239d2@haiku-os.org> Message-ID: <050.abf7e0660d61c34f90748aef5eee3c5b@haiku-os.org> #4123: [patch] DriveSetup doesn't use validated name when initialising volume -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by idefix): Well, we'll see what he comes up with then... :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:31:09 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 18:31:09 -0000 Subject: [Haiku-bugs] [Haiku] #4131: [Workspaces] add Quit and About box to right click menu Message-ID: <040.851f8e747afb1a19a927514797eed1da@haiku-os.org> #4131: [Workspaces] add Quit and About box to right click menu -------------------------------------+-------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Current Workspaces replicant lacks some obvious things like Quit and About box to right click menu -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:47:30 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 18:47:30 -0000 Subject: [Haiku-bugs] [Haiku] #4132: [Deskbar] shelf width have space only for 3 icons Message-ID: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> #4132: [Deskbar] shelf width have space only for 3 icons ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Currently deskbar' shelf have spase only for 3 icons, but have more space which is wasted. If you enable "24 Hour clock" settings 4 icons could take it place in one row.[[BR]]See screenshot:[[BR]] [[Image(before.png)]][[BR]] [[Image(after.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:47:45 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 18:47:45 -0000 Subject: [Haiku-bugs] [Haiku] #4133: [Deskbar] shelf width have space only for 3 icons Message-ID: <040.d4276eef91e88410343ec07b2596cde7@haiku-os.org> #4133: [Deskbar] shelf width have space only for 3 icons -------------------------+-------------------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Currently deskbar' shelf have spase only for 3 icons, but have more space which is wasted. If you enable "24 Hour clock" settings 4 icons could take it place in one row.[[BR]]See screenshot:[[BR]] [[Image(before.png)]][[BR]] [[Image(after.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:48:27 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 18:48:27 -0000 Subject: [Haiku-bugs] [Haiku] #4133: [Deskbar] shelf width have space only for 3 icons In-Reply-To: <040.d4276eef91e88410343ec07b2596cde7@haiku-os.org> References: <040.d4276eef91e88410343ec07b2596cde7@haiku-os.org> Message-ID: <049.fcfbadb9d8bba742b23d63b11dc551e1@haiku-os.org> #4133: [Deskbar] shelf width have space only for 3 icons ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by diver): * component: - General => Applications/Deskbar -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 20:49:56 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 27 Jul 2009 18:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #4132: [Deskbar] shelf width have space only for 3 icons In-Reply-To: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> References: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> Message-ID: <049.60a8cd822f9a6a0ea865adec77e0f0af@haiku-os.org> #4132: [Deskbar] shelf width have space only for 3 icons -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: duplicate | Blockedby: 4133 Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate * blockedby: => 4133 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 21:11:37 2009 From: trac at haiku-os.org (sil2100) Date: Mon, 27 Jul 2009 19:11:37 -0000 Subject: [Haiku-bugs] [Haiku] #4059: PackageInstaller needs a "Yes to all" button in dialog box In-Reply-To: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> References: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> Message-ID: <051.fac820ffae46bef64ee038ee6eae8c65@haiku-os.org> #4059: PackageInstaller needs a "Yes to all" button in dialog box -------------------------------------------+-------------------------------- Reporter: scottmc | Owner: sil2100 Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------------+-------------------------------- Comment(by sil2100): I am sorry this took so long. I made this patch a few days ago, but the tracker was down, and I had to leave for a trip later that day. But I finally found a place to connect to. This patch does the thing in mention a bit differently. Since the maximum number of buttons in a BAlarm is 3, I couldn't add a 'Yes to all' button - it's not really a good idea anyway, since the number of buttons would make the alarm less readable. Instead, when a conflict appears, a second dialog box appears asking the user if the PackageInstaller should remember the previous choice for all conflicts in the future. Right now the installer will ask only once, but a 'Ask later' button is possible - although I can't find as much use to such thing, it would probably just unnecessarily bloat the alert. I also exported the user asking mechanism to the View instead of the inner structures. This way seems much better. Tested on r31688. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 21:22:17 2009 From: trac at haiku-os.org (diver) Date: Mon, 27 Jul 2009 19:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #4134: [Deskbar] it should not be possibe to maximize deskbar Message-ID: <040.78ab27780175ba996bc22ae6b1f5e324@haiku-os.org> #4134: [Deskbar] it should not be possibe to maximize deskbar ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Press leaf menu and then press Ctrl+Alt+Z -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 22:50:33 2009 From: trac at haiku-os.org (axeld) Date: Mon, 27 Jul 2009 20:50:33 -0000 Subject: [Haiku-bugs] [Haiku] #4134: [Deskbar] it should not be possibe to maximize deskbar In-Reply-To: <040.78ab27780175ba996bc22ae6b1f5e324@haiku-os.org> References: <040.78ab27780175ba996bc22ae6b1f5e324@haiku-os.org> Message-ID: <049.feb1dcfee4c4b7259f3036cf59ae8f54@haiku-os.org> #4134: [Deskbar] it should not be possibe to maximize deskbar -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r31828, though I did not look into the freeze problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jul 27 23:03:14 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 27 Jul 2009 21:03:14 -0000 Subject: [Haiku-bugs] [Haiku] #4067: Kinesis USB Keyboard is removed after first key is pressed. In-Reply-To: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> References: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> Message-ID: <050.dbb09f7e5ce75357ea6c1d431e536850@haiku-os.org> #4067: Kinesis USB Keyboard is removed after first key is pressed. -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): Can you please retest with the reworked usb_hid driver? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 00:29:25 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 27 Jul 2009 22:29:25 -0000 Subject: [Haiku-bugs] [Haiku] #2876: [BePDF] Help menu options don't work In-Reply-To: <042.09d16878f35f3cc088379d2b8ff6bff4@haiku-os.org> References: <042.09d16878f35f3cc088379d2b8ff6bff4@haiku-os.org> Message-ID: <051.26615230dd966bb22894110b53d7773f@haiku-os.org> #2876: [BePDF] Help menu options don't work -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): This appears to be working ok now, so this ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 00:56:36 2009 From: trac at haiku-os.org (stippi) Date: Mon, 27 Jul 2009 22:56:36 -0000 Subject: [Haiku-bugs] [Haiku] #4059: PackageInstaller needs a "Yes to all" button in dialog box In-Reply-To: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> References: <042.0d8f9cb9958898159f9581acd47f2489@haiku-os.org> Message-ID: <051.c7fd7b921d967b96327c95c450990524@haiku-os.org> #4059: PackageInstaller needs a "Yes to all" button in dialog box -------------------------------------------+-------------------------------- Reporter: scottmc | Owner: sil2100 Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------------+-------------------------------- Comment(by stippi): The patch looks pretty nice to me, although I have not actually looked for any bugs. You have commit access, right? ;-) My suggestions for improvements would be two things: 1) You should never use wording in the UI that makes the computer into a person ("Should I remove the file..."). Instead, use passive language like "Should the file be removed...". That sounds much more professional. 2) Maybe "fCurrentPolicy" is not the best name. Policy for what? Perhaps "fCurrentItemExistsPolicy" would be better. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 04:19:54 2009 From: trac at haiku-os.org (umccullough) Date: Tue, 28 Jul 2009 02:19:54 -0000 Subject: [Haiku-bugs] [Haiku] #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick Message-ID: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick -------------------------+-------------------------------------------------- Reporter: umccullough | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- During a recent purchase of various brand USB sticks for test-booting Haiku from, I ran into a specific model that fails after the rocket icon lights up. The model in question is a Kingston DataTraveler G2 4gb stick. I did however have no problems with a Kingston DataTraveler 4gb stick (not a G2), which booted just fine. I don't know the technical difference between these models. This was tested with Haiku gcc2 r31794 using the alpha image but with the ATA bus_manager swapped in. As mentioned above, it gets to the rocket icon which lights up, but it crashes before the boot screen disappears. Serial log attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 04:22:56 2009 From: trac at haiku-os.org (umccullough) Date: Tue, 28 Jul 2009 02:22:56 -0000 Subject: [Haiku-bugs] [Haiku] #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick In-Reply-To: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> References: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> Message-ID: <055.48db2375f0591a2f1f8b0c0ff09bf5cb@haiku-os.org> #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick -------------------------+-------------------------------------------------- Reporter: umccullough | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): The device that doesn't work is listed here: http://www.kingston.com/flash/dtig2.asp Howevever, the following device does work: http://www.kingston.com/flash/datatraveler.asp -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 04:29:30 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Tue, 28 Jul 2009 02:29:30 -0000 Subject: [Haiku-bugs] [Haiku] #2081: Change in mount status not picked up In-Reply-To: <043.f1c3dd9d94ee1a4a6daf648c36b92668@haiku-os.org> References: <043.f1c3dd9d94ee1a4a6daf648c36b92668@haiku-os.org> Message-ID: <052.75c0f1b82c2e15475a2e2294f8ced0af@haiku-os.org> #2081: Change in mount status not picked up -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by jonas.kirilla): Volumes mounted e.g. via Tracker while DriveSetup is running are now (in r31644) picked up when doing a rescan. DriveSetup would benefit from keeping a BVolumeRoster around, listening to mounts/unmounts and perhaps simply doing a rescan for such events (or something more specific). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 05:02:12 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Tue, 28 Jul 2009 03:02:12 -0000 Subject: [Haiku-bugs] [Haiku] #4136: DriveSetup: Partition menu options enabled in reverse order Message-ID: <048.6d1da9107873eedc00babd4b36342c01@haiku-os.org> #4136: DriveSetup: Partition menu options enabled in reverse order -------------------------------------+-------------------------------------- Reporter: jonas.kirilla | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- I think some routine that enables/disables DriveSetup's Partition menu items has the order of the partitions reversed. (in r31644) I have 4 primary partitions equally sized on a 40GB disk. All 4 partitions are BFS and healthy AFAIK. BeOS, Bkp1, Bkp2, Haiku (/boot) I would expect DriveSetup's Partition menu to have options initialize, delete and mount -disabled- for the boot partition (4), and enabled for the other three (unmounted) partitions. I don't expect but do see these options enabled for the current Haiku boot partition (4) and disabled for the unmounted BeOS partition (1). Mounting partition (2) enables option to unmount partition (3). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 05:29:23 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 28 Jul 2009 03:29:23 -0000 Subject: [Haiku-bugs] [Haiku] #4136: DriveSetup: Partition menu options enabled in reverse order In-Reply-To: <048.6d1da9107873eedc00babd4b36342c01@haiku-os.org> References: <048.6d1da9107873eedc00babd4b36342c01@haiku-os.org> Message-ID: <057.efdb7632348c882dfcdd32c6c94874eb@haiku-os.org> #4136: DriveSetup: Partition menu options enabled in reverse order --------------------------------------+------------------------------------- Reporter: jonas.kirilla | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => duplicate Comment: dupe of #3965 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 08:26:54 2009 From: trac at haiku-os.org (GeneralMaximus) Date: Tue, 28 Jul 2009 06:26:54 -0000 Subject: [Haiku-bugs] [Haiku] #4137: Running checkfs on (Possibly) Corrupted BFS Partition Crashes Haiku Message-ID: <049.8e09bd2f11eb02489dd625be288e148b@haiku-os.org> #4137: Running checkfs on (Possibly) Corrupted BFS Partition Crashes Haiku ------------------------------+--------------------------------------------- Reporter: GeneralMaximus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Running checkfs on a (possibly) damaged BeFS partition results in KDL. Here is the KDL output: * http://www.flickr.com/photos/general_maximus/3752026415/sizes/l/ * http://www.flickr.com/photos/general_maximus/3752816402/sizes/l/ Revision 31728, built on July 24. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 09:37:46 2009 From: trac at haiku-os.org (korli) Date: Tue, 28 Jul 2009 07:37:46 -0000 Subject: [Haiku-bugs] [Haiku] #2876: [BePDF] Help menu options don't work In-Reply-To: <042.09d16878f35f3cc088379d2b8ff6bff4@haiku-os.org> References: <042.09d16878f35f3cc088379d2b8ff6bff4@haiku-os.org> Message-ID: <051.81440fd330e26221013a2383a9ad40ec@haiku-os.org> #2876: [BePDF] Help menu options don't work ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 09:43:16 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 28 Jul 2009 07:43:16 -0000 Subject: [Haiku-bugs] [Haiku] #4067: Kinesis USB Keyboard is removed after first key is pressed. In-Reply-To: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> References: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> Message-ID: <050.2b765495c42c8b2fdff4b2c6e9b0cff6@haiku-os.org> #4067: Kinesis USB Keyboard is removed after first key is pressed. -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmadia): Replying to [comment:1 mmlr]: > Can you please retest with the reworked usb_hid driver? Still persistent at r31839. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 12:51:09 2009 From: trac at haiku-os.org (diver) Date: Tue, 28 Jul 2009 10:51:09 -0000 Subject: [Haiku-bugs] [Haiku] #4138: [Tracker] some text doesn't fit in fnd panel Message-ID: <040.04b3a4b3b52edf761ac46c08a501f877@haiku-os.org> #4138: [Tracker] some text doesn't fit in fnd panel ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- "Include Trash" label and "Remove" button text doesn't fit in fnd panel [[BR]] r31840 in virtualbox [[Image(Find panel.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 12:56:24 2009 From: trac at haiku-os.org (diver) Date: Tue, 28 Jul 2009 10:56:24 -0000 Subject: [Haiku-bugs] [Haiku] #4139: [Interface kit] Tab looks wrong in JPEG2000 translator Message-ID: <040.361c96f5b04fc81d9781b7f32e3b1b90@haiku-os.org> #4139: [Interface kit] Tab looks wrong in JPEG2000 translator --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- r31840 in virtualbox[[BR]] [[Image(Tab.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 13:01:41 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 11:01:41 -0000 Subject: [Haiku-bugs] [Haiku] #2782: implement sticky windows In-Reply-To: <042.38a576130fb59003013719adda791fa4@haiku-os.org> References: <042.38a576130fb59003013719adda791fa4@haiku-os.org> Message-ID: <051.83ecce7f15592920737f2475f7d6bb12@haiku-os.org> #2782: implement sticky windows ----------------------------+----------------------------------------------- Reporter: Adek336 | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by stippi): Applied the screen edge patch with modifications in r31841. Sorry it took so long, the patch was very well done! I implemented some automatic behavior with timeouts that resolved some TODOs in the patch and made it unnecessary (hopefully) to configure anything. Since the ticket is also about snapping to window borders, I keep it open, since the patch "only" snaps to screen edges. (Nice improvement in itself!) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 13:06:18 2009 From: trac at haiku-os.org (diver) Date: Tue, 28 Jul 2009 11:06:18 -0000 Subject: [Haiku-bugs] [Haiku] #4140: [app_server] crash in AppServer::ClientTeam Message-ID: <040.20c95ed79b5730dfdeb8ad4313a53ae2@haiku-os.org> #4140: [app_server] crash in AppServer::ClientTeam --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- I started all apps in Leaf menu->Preferences and started to close them quickly after they all have been loaded and got a crash.[[BR]] This is r31840 in virtualbox[[BR]] [[Image(app_server.png]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 13:08:50 2009 From: trac at haiku-os.org (diver) Date: Tue, 28 Jul 2009 11:08:50 -0000 Subject: [Haiku-bugs] [Haiku] #4140: [app_server] crash in AppServer::ClientTeam In-Reply-To: <040.20c95ed79b5730dfdeb8ad4313a53ae2@haiku-os.org> References: <040.20c95ed79b5730dfdeb8ad4313a53ae2@haiku-os.org> Message-ID: <049.1d07c59552efbbe0aa677540744c7803@haiku-os.org> #4140: [app_server] crash in AppServer::ClientTeam --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by diver): Ah damn, it seems I forgot close bracket in [[Image(app_server.png]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 14:33:04 2009 From: trac at haiku-os.org (axeld) Date: Tue, 28 Jul 2009 12:33:04 -0000 Subject: [Haiku-bugs] [Haiku] #4137: Running checkfs on (Possibly) Corrupted BFS Partition Crashes Haiku In-Reply-To: <049.8e09bd2f11eb02489dd625be288e148b@haiku-os.org> References: <049.8e09bd2f11eb02489dd625be288e148b@haiku-os.org> Message-ID: <058.af6a63bc88f7a49dff1d356ca01b0ac7@haiku-os.org> #4137: Running checkfs on (Possibly) Corrupted BFS Partition Crashes Haiku -------------------------------+-------------------------------------------- Reporter: GeneralMaximus | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This has already been fixed a few days ago in r31749 - please always make sure to retest with a recent release, but thanks for the report. On a general note, though, please attach images to the bug tracker, and don't use external links. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 14:45:31 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 12:45:31 -0000 Subject: [Haiku-bugs] [Haiku] #2945: BGradient draws junk when endpoints are not fully defined In-Reply-To: <041.942c72e158dcac5ffebbd465530870cb@haiku-os.org> References: <041.942c72e158dcac5ffebbd465530870cb@haiku-os.org> Message-ID: <050.0639971ffc21a86ea2d710c6d526660d@haiku-os.org> #2945: BGradient draws junk when endpoints are not fully defined --------------------------------+------------------------------------------- Reporter: sdeken | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 14:47:44 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 12:47:44 -0000 Subject: [Haiku-bugs] [Haiku] #2946: BGradient does not support alpha transparency In-Reply-To: <041.77bc8d518d5049dc8ef4c1b8db0cb709@haiku-os.org> References: <041.77bc8d518d5049dc8ef4c1b8db0cb709@haiku-os.org> Message-ID: <050.dc85294e79234735c3de21aee65ab1c8@haiku-os.org> #2946: BGradient does not support alpha transparency --------------------------------+------------------------------------------- Reporter: sdeken | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stippi): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 14:47:54 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 12:47:54 -0000 Subject: [Haiku-bugs] [Haiku] #2945: BGradient draws junk when endpoints are not fully defined In-Reply-To: <041.942c72e158dcac5ffebbd465530870cb@haiku-os.org> References: <041.942c72e158dcac5ffebbd465530870cb@haiku-os.org> Message-ID: <050.d607fa1349cd9abc360049722bea96c3@haiku-os.org> #2945: BGradient draws junk when endpoints are not fully defined --------------------------------+------------------------------------------- Reporter: sdeken | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stippi): * status: assigned => new -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 15:37:28 2009 From: trac at haiku-os.org (schily) Date: Tue, 28 Jul 2009 13:37:28 -0000 Subject: [Haiku-bugs] [Haiku] #3412: stdio library code dishonors BUFSIZ for setbuf() In-Reply-To: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> References: <041.2ddad190572344d42a15861a98af13b7@haiku-os.org> Message-ID: <050.2e7830ff1d549ca375a36d6c56354444@haiku-os.org> #3412: stdio library code dishonors BUFSIZ for setbuf() ------------------------+--------------------------------------------------- Reporter: schily | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by schily): OK, the bug seems to be fixed now. The program that did dump core no longer fails. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 16:08:12 2009 From: trac at haiku-os.org (VinDuv) Date: Tue, 28 Jul 2009 14:08:12 -0000 Subject: [Haiku-bugs] [Haiku] #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them Message-ID: <041.4ef5ee2335b484b94285bb5550d470ce@haiku-os.org> #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them -----------------------+---------------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This is r31843. When trying to create a symlink on a filesystem that does not support them (i.e. the fs_create_symlink hook is NULL), EROFS is returned. It should probably return B_UNSUPPORTED instead. {{{ /fatfs> ln -s somefile somelink ln: creating symbolic link `somelink': Read-only file system }}} http://dev.haiku- os.org/browser/haiku/trunk/src/system/kernel/fs/vfs.cpp#L5944 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 18:48:09 2009 From: trac at haiku-os.org (idefix) Date: Tue, 28 Jul 2009 16:48:09 -0000 Subject: [Haiku-bugs] [Haiku] #4142: [patch] Source menu looks different than target menu Message-ID: <041.92a47226808c47730bc118e0aed42a6a@haiku-os.org> #4142: [patch] Source menu looks different than target menu ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Changeset [31803] made the source menu look more like the target menu, but they're not exactly the same yet; the source menu shows the `/dev` path, while the target menu doesn't show it:[[BR]] [[Image(Installerbefore.png)]] [attachment:installersourcemenu.patch This patch] makes both menu's look exactly the same:[[BR]] [[Image(Installerafter.png)]][[BR]] I also noticed that the `SRC_PARTITION` constant is in abbreviated form, while `TARGET_PARTITION` isn't. [attachment:installersrcpartition.patch The second patch] will change `SRC_PARTITION` to `SOURCE_PARTITION`. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 19:00:18 2009 From: trac at haiku-os.org (idefix) Date: Tue, 28 Jul 2009 17:00:18 -0000 Subject: [Haiku-bugs] [Haiku] #4142: [patch] Source menu looks different from target menu (was: [patch] Source menu looks different than target menu) In-Reply-To: <041.92a47226808c47730bc118e0aed42a6a@haiku-os.org> References: <041.92a47226808c47730bc118e0aed42a6a@haiku-os.org> Message-ID: <050.b77319306cfe2a39a77d817bb65b5764@haiku-os.org> #4142: [patch] Source menu looks different from target menu ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 19:36:44 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 17:36:44 -0000 Subject: [Haiku-bugs] [Haiku] #4142: [patch] Source menu looks different from target menu In-Reply-To: <041.92a47226808c47730bc118e0aed42a6a@haiku-os.org> References: <041.92a47226808c47730bc118e0aed42a6a@haiku-os.org> Message-ID: <050.187c52cfce3182c8d81157dde2160f6f@haiku-os.org> #4142: [patch] Source menu looks different from target menu -------------------------------------+-------------------------------------- Reporter: idefix | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks a lot! Applied in r31854. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 20:29:45 2009 From: trac at haiku-os.org (tqh) Date: Tue, 28 Jul 2009 18:29:45 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on Message-ID: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on -------------------------+-------------------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- revision 31838 crashes at Desktop with Pagefault in AddonMonitor. See screenshot. r31837 and earlier works fine. Stack trace as image. Note, my usb is a bit problematic with usb sticks and other things too, so I might need to look into that. Still, it worked before. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 20:56:00 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 28 Jul 2009 18:56:00 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.9d7d7e2b203756490fd045b3b8246521@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on ----------------------------------+----------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by mmlr): * component: Drivers/USB => Drivers/Keyboard/USB Comment: Actually the stack trace is missing from that image. I assume you're using the auto_stack_trace kernel debugger add-on which sometimes exhibits that problem. If you would be able to get a full stack trace that would be most helpful. Can you provide info about the kind of keyboard that you have attached to that machine? Does it have special keys at all or is it a more simple model? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 22:24:47 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 28 Jul 2009 20:24:47 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK Message-ID: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- In the Bebook, this function is described: status_t SetMode(display_mode* mode, bool makeDefault = false); It does not work in Haiku: the call is never made to the accelerant. What does work in Haiku is this (which is used in Haiku's screen preflet): SetMode(workspace, &mode, false); This problem exists for a long period of time now, upto/including R31786. Newer ones are not tested. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 22:40:19 2009 From: trac at haiku-os.org (idefix) Date: Tue, 28 Jul 2009 20:40:19 -0000 Subject: [Haiku-bugs] [Haiku] #4145: KDLs screen paging overwrites first two lines of subsequent pages Message-ID: <041.c475a59df6c0ad4ef4959ec3380742a2@haiku-os.org> #4145: KDLs screen paging overwrites first two lines of subsequent pages ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ When you get into the KDL you'll be greeted with the following screen:[[BR]] [[Image(KDL1.png)]][[BR]] Requesting help, gets you the first help-page:[[BR]] [[Image(KDL2.png)]][[BR]] You'll notice the two blank lines after the first row overwriting the `Welcome...` and `Thread...` rows. The `kdebug>` prompt is not overwritten however. The next page doesn't continue after the two blank lines, but right after the first line (notice that this page has not been fully written to the screen yet):[[BR]] [[Image(KDL3.png)]][[BR]] When the page has been fully written, the two blank lines now cover the first two lines of this new page as indicated by the red bounding rectangle:[[BR]] [[Image(KDL4.png)]][[BR]] From then on, every page has it's first two lines overwritten by the two blank lines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 22:50:58 2009 From: trac at haiku-os.org (VinDuv) Date: Tue, 28 Jul 2009 20:50:58 -0000 Subject: [Haiku-bugs] [Haiku] #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them In-Reply-To: <041.4ef5ee2335b484b94285bb5550d470ce@haiku-os.org> References: <041.4ef5ee2335b484b94285bb5550d470ce@haiku-os.org> Message-ID: <050.e923d46d1b4a8d9cadac1f0425bd56b2@haiku-os.org> #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them --------------------------+------------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by VinDuv): * component: - General => File Systems Comment: Sorry, forgot to set the component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 23:07:08 2009 From: trac at haiku-os.org (tqh) Date: Tue, 28 Jul 2009 21:07:08 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.8552e03046182cf8ddf903b00a11530c@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on ----------------------------------+----------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by tqh): Probably should have done so in the first place. I have a usb mouse (wireless) and a usb keyboard connected to a usb hub, which in turn is connected to the PC. The usb-keyboard is a cheap noname brand, but has sleep, hibernate and power button (never checked if they work in any OS). lsusb in Linux suggest usb to ps/2 converter. Attaching info from lsusb -v. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 23:25:07 2009 From: trac at haiku-os.org (stippi) Date: Tue, 28 Jul 2009 21:25:07 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.ff51dffb1b2a1631fc0d93cd0d427231@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Could you please check with r31864? It should have fixed the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 23:32:27 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 28 Jul 2009 21:32:27 -0000 Subject: [Haiku-bugs] [Haiku] #4145: KDLs screen paging overwrites first two lines of subsequent pages In-Reply-To: <041.c475a59df6c0ad4ef4959ec3380742a2@haiku-os.org> References: <041.c475a59df6c0ad4ef4959ec3380742a2@haiku-os.org> Message-ID: <050.734610f459e9ddb48ef32cf7d49dc116@haiku-os.org> #4145: KDLs screen paging overwrites first two lines of subsequent pages ----------------------------+----------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Yep, annoyed me a few times already. Fixed in r31865. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 23:53:20 2009 From: trac at haiku-os.org (jackburton) Date: Tue, 28 Jul 2009 21:53:20 -0000 Subject: [Haiku-bugs] [Haiku] #4139: [Interface kit] Tab looks wrong in JPEG2000 translator In-Reply-To: <040.361c96f5b04fc81d9781b7f32e3b1b90@haiku-os.org> References: <040.361c96f5b04fc81d9781b7f32e3b1b90@haiku-os.org> Message-ID: <049.40075df0182cdee0dcde2b4a71c78f1e@haiku-os.org> #4139: [Interface kit] Tab looks wrong in JPEG2000 translator --------------------------------+------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by jackburton): * owner: axeld => jackburton Comment: That's because the jpeg2000 translator use its own version of a BTabView. The jpeg translator does the same. I fixed the latter in r31871, and will take care of this one in the next days. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jul 28 23:53:30 2009 From: trac at haiku-os.org (jackburton) Date: Tue, 28 Jul 2009 21:53:30 -0000 Subject: [Haiku-bugs] [Haiku] #4139: [Interface kit] Tab looks wrong in JPEG2000 translator In-Reply-To: <040.361c96f5b04fc81d9781b7f32e3b1b90@haiku-os.org> References: <040.361c96f5b04fc81d9781b7f32e3b1b90@haiku-os.org> Message-ID: <049.7c2a4375631d2e82b1a467f143a783ca@haiku-os.org> #4139: [Interface kit] Tab looks wrong in JPEG2000 translator --------------------------------+------------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by jackburton): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 00:00:39 2009 From: trac at haiku-os.org (jackburton) Date: Tue, 28 Jul 2009 22:00:39 -0000 Subject: [Haiku-bugs] [Haiku] #3044: [JPEG2000] shows an alert if it can't find his settings (easy) In-Reply-To: <040.e63ef2d76f917ef1ec08bf5febbb34f6@haiku-os.org> References: <040.e63ef2d76f917ef1ec08bf5febbb34f6@haiku-os.org> Message-ID: <049.2b2de64b91e0f8a3edf83ba28b9d7f12@haiku-os.org> #3044: [JPEG2000] shows an alert if it can't find his settings (easy) ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Replying to [comment:9 richy_rich]: Applied in r31873. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 00:19:38 2009 From: trac at haiku-os.org (atmartens) Date: Tue, 28 Jul 2009 22:19:38 -0000 Subject: [Haiku-bugs] [Haiku] #3796: The preference panel CPUFrequency don't show the Frequency In-Reply-To: <044.338df5ec94aaf99c85052b630b6d384c@haiku-os.org> References: <044.338df5ec94aaf99c85052b630b6d384c@haiku-os.org> Message-ID: <053.2784a52bc1cdf0ad65616f03c2a99f05@haiku-os.org> #3796: The preference panel CPUFrequency don't show the Frequency -----------------------+---------------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by atmartens): I get a question mark "?" in my CPU frequency in the preferences applet. My processor is an Intel E8500. I looked at the frequency.h file in add- ons/kernel/drivers/power/enhanced_speedstep/ and found the following comment, maybe this is why (emphasis mine)? Frequency (MHz) and voltage (mV) settings. Data from the Intel Pentium M Processor Datasheet (Order Number 252612), Table 5. Dothan processors have multiple VID#s with different settings for each VID#. '''Since we can't uniquely identify this info without undisclosed methods from Intel, we can't support newer processors with this table method.''' If ACPI Px states are supported, we get info from them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 00:52:37 2009 From: trac at haiku-os.org (korli) Date: Tue, 28 Jul 2009 22:52:37 -0000 Subject: [Haiku-bugs] [Haiku] #3366: [SoundRecorder] no need in first 2px white row in ScopeView In-Reply-To: <040.76768112eac5532f732b066c849211bb@haiku-os.org> References: <040.76768112eac5532f732b066c849211bb@haiku-os.org> Message-ID: <049.ab340acfc77c202f88d5bc74cb8b120a@haiku-os.org> #3366: [SoundRecorder] no need in first 2px white row in ScopeView -----------------------------------------+---------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------------+---------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Hopefully fixed in r31876. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:01:55 2009 From: trac at haiku-os.org (atmartens) Date: Tue, 28 Jul 2009 23:01:55 -0000 Subject: [Haiku-bugs] [Haiku] #4146: Magnify doesn't resize nicely Message-ID: <044.630fbd1d48bf0519a533ce42136083d1@haiku-os.org> #4146: Magnify doesn't resize nicely -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- If you make the magnify program small enough, the text runs too far outside the window, and the option button covers some of the text. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:06:27 2009 From: trac at haiku-os.org (atmartens) Date: Tue, 28 Jul 2009 23:06:27 -0000 Subject: [Haiku-bugs] [Haiku] #4147: Magnify app crashes Message-ID: <044.bc777c0bda210a663293eda774239d6b@haiku-os.org> #4147: Magnify app crashes -----------------------+---------------------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I was playing with the magnifying application and it crashed on me after a right-click. Here is a backtrace: {{{ #0 0x0020b204 in TMagnify::MouseDown () #1 0x0036c2d0 in BWindow::DispatchMessage () from /boot/system/lib/libbe.so #2 0x00368ad3 in BWindow::task_looper () from /boot/system/lib/libbe.so #3 0x002ba904 in BLooper::_task0_ () from /boot/system/lib/libbe.so #4 0x0062f08d in thread_entry () from /boot/system/lib/libroot.so #5 0x78074fec in ?? () }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:12:22 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 28 Jul 2009 23:12:22 -0000 Subject: [Haiku-bugs] [Haiku] #4147: Magnify app crashes In-Reply-To: <044.bc777c0bda210a663293eda774239d6b@haiku-os.org> References: <044.bc777c0bda210a663293eda774239d6b@haiku-os.org> Message-ID: <053.f690984605eb49a6580f0e3ce6363966@haiku-os.org> #4147: Magnify app crashes ----------------------------------+----------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Magnify | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by anevilyak): * component: - General => Applications/Magnify -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:12:43 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 28 Jul 2009 23:12:43 -0000 Subject: [Haiku-bugs] [Haiku] #4146: Magnify doesn't resize nicely In-Reply-To: <044.630fbd1d48bf0519a533ce42136083d1@haiku-os.org> References: <044.630fbd1d48bf0519a533ce42136083d1@haiku-os.org> Message-ID: <053.9bd20274d1b14484131a57d9fa556b64@haiku-os.org> #4146: Magnify doesn't resize nicely ----------------------------------+----------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Magnify | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by anevilyak): * component: - General => Applications/Magnify -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:20:02 2009 From: trac at haiku-os.org (atmartens) Date: Tue, 28 Jul 2009 23:20:02 -0000 Subject: [Haiku-bugs] [Haiku] #4147: Magnify app crashes In-Reply-To: <044.bc777c0bda210a663293eda774239d6b@haiku-os.org> References: <044.bc777c0bda210a663293eda774239d6b@haiku-os.org> Message-ID: <053.a37a53799e813ec96380c0db0cbcdc54@haiku-os.org> #4147: Magnify app crashes ----------------------------------+----------------------------------------- Reporter: atmartens | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Magnify | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by atmartens): The only problem is I can't seem to reproduce the bug. I'll keep at it. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 01:43:06 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 28 Jul 2009 23:43:06 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.fc2695b3d0de8b18d2cde39f1a8a5836@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by anevilyak): * status: new => assigned Comment: The first problem is mostly due to allowing alt+a to have an effect in a list view that's in single selection mode in the first place (i.e. Data Translations / File Types). Investigating the second. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 03:42:13 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 29 Jul 2009 01:42:13 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.948eb138612dc042941e956b57e446f8@haiku-os.org> #4120: Selection weirdness in list views --------------------------------+------------------------------------------- Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): The Alt+a + select problem should be fixed in r31889. Those particular views should not have been accepting select all in the first place since they were in single selection mode, and as such the view wasn't in the correct mode to update the indices for multiple selections properly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 04:00:51 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 29 Jul 2009 02:00:51 -0000 Subject: [Haiku-bugs] [Haiku] #4120: Selection weirdness in list views In-Reply-To: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> References: <044.c251df13f303e24d23816250539fe9ee@haiku-os.org> Message-ID: <053.77e58eb8c4d7eede32167f7a64465ef3@haiku-os.org> #4120: Selection weirdness in list views ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Should be fixed in r31890. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 08:07:33 2009 From: trac at haiku-os.org (peyren) Date: Wed, 29 Jul 2009 06:07:33 -0000 Subject: [Haiku-bugs] [Haiku] #4148: Font setting is not saved correctly after system restart Message-ID: <041.795ebb4947bcc0964536012d58c595fb@haiku-os.org> #4148: Font setting is not saved correctly after system restart ------------------------------------+--------------------------------------- Reporter: peyren | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------------+--------------------------------------- Change of 'Plain font' and 'Bold font' setting at Preference->Fonts is not saved. How to reproduce: 1. go to Preference->Fonts 2. change 'Plain font' from 'DejaVu Sans Book' to 'DejaVu Sans Condensed' 3. restart the system 4. check Fonts setting again. 'Plain font' will still be 'DejaVu Sans Book'. Same procedure can be applied for 'Bold font' setting. However, 'Fixed font' and 'Menu font' settings are saved correctly. Tested in Virtual box and qemu with r31835-gcc4 (and some former versions). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 08:21:09 2009 From: trac at haiku-os.org (peyren) Date: Wed, 29 Jul 2009 06:21:09 -0000 Subject: [Haiku-bugs] [Haiku] #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot Message-ID: <041.2b4973da5127fda954fd0de9915ff092@haiku-os.org> #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot ------------------------------------+--------------------------------------- Reporter: peyren | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------------+--------------------------------------- If you change 'Fixed font' setting to 'DejaVu Sans Mono Bold' and restart system, the system will crash during boot process. How to reproduce:[[BR]] 1. go to Preferences->Fonts[[BR]] 2. change 'Fixed font' to 'DejaVu Sans Mono Bold'[[BR]] 3. restart the system[[BR]] 4. system will crash during boot process.[[BR]] [[BR]] Tested in VirtualBox with r31876-gcc4. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 09:55:26 2009 From: trac at haiku-os.org (aldeck) Date: Wed, 29 Jul 2009 07:55:26 -0000 Subject: [Haiku-bugs] [Haiku] #1635: Gl Teapot Bad Rendering On Window Size Expand In-Reply-To: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> References: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> Message-ID: <049.e473c5d502b5cd1005082c9d80cc7e9e@haiku-os.org> #1635: Gl Teapot Bad Rendering On Window Size Expand --------------------------------+------------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by aldeck): Might have been fixed in the mean time. At least i can't reproduce here. Korli can you confirm? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 10:03:25 2009 From: trac at haiku-os.org (diver) Date: Wed, 29 Jul 2009 08:03:25 -0000 Subject: [Haiku-bugs] [Haiku] #4140: [app_server] crash in AppServer::ClientTeam In-Reply-To: <040.20c95ed79b5730dfdeb8ad4313a53ae2@haiku-os.org> References: <040.20c95ed79b5730dfdeb8ad4313a53ae2@haiku-os.org> Message-ID: <049.4a33423367c52d3c3df0af57a7b70e24@haiku-os.org> #4140: [app_server] crash in AppServer::ClientTeam --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by diver): First backtrace[[BR]] [[Image(app_server.png)]][[BR]]And I just get another crash in r31894[[BR]] [[Image(app_server2.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 10:18:21 2009 From: trac at haiku-os.org (aldeck) Date: Wed, 29 Jul 2009 08:18:21 -0000 Subject: [Haiku-bugs] [Haiku] #4150: SetViewBitmap background image / wallpaper shows redraw artifacts in tile mode. Message-ID: <041.0fdd1aa46de28f5efe937fe2ce296a46@haiku-os.org> #4150: SetViewBitmap background image / wallpaper shows redraw artifacts in tile mode. --------------------------------+------------------------------------------- Reporter: aldeck | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Set a desktop background in tile mode, moving a window over a tile seam leaves redrawing artifacts (1 pixel wide). Briefly looked at the code and it looks like a rounding error in app_server (BRect -> IntRect). Not sure if the fix should be client side though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 11:39:51 2009 From: trac at haiku-os.org (phoudoin) Date: Wed, 29 Jul 2009 09:39:51 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown Message-ID: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- With acpi enabled, acpi_battery driver loaded, PowerStatus replicant installed in Deskbar and "Extended Battery Info" window opened, a shutdown/restart command lead to Deskbar crashing in ExtendedInfoWindow's _loop0(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 11:52:41 2009 From: trac at haiku-os.org (phoudoin) Date: Wed, 29 Jul 2009 09:52:41 -0000 Subject: [Haiku-bugs] [Haiku] #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures Message-ID: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures ----------------------+----------------------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------+----------------------------------------------------- While acpi_battery is loaded and watched (by PowerStatus, for example), several ACPI exceptions about GlobalLock access failures are traced in syslog, without other visible consequence. Could be sign of a deeper (or evil?! ;-) ) problem in ACPI, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 12:15:25 2009 From: trac at haiku-os.org (phoudoin) Date: Wed, 29 Jul 2009 10:15:25 -0000 Subject: [Haiku-bugs] [Haiku] #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures In-Reply-To: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> References: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> Message-ID: <052.d6d989fa36fb21913d8144c1ea245575@haiku-os.org> #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures ----------------------+----------------------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------+----------------------------------------------------- Comment(by phoudoin): That's under a fresh r31835 gcc2 alpha image, on a Samsung NC10 netbook. I will attach a syslog dump as soon as: 1. the Marvell Yukon 88E8040 PHY link is correctly handled to send it over network (ticket creation really soon now), or 2. I will successfully install Atheros proof-of-concept wifi driver to send it over network, or 3. I could save it to a fat-formatted usb key without be thrown into KDL by an assert on cluster != 0 in fat.c (see #3690) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 12:17:38 2009 From: trac at haiku-os.org (phoudoin) Date: Wed, 29 Jul 2009 10:17:38 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown In-Reply-To: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> References: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> Message-ID: <052.740417cf86e600897fbc3f2f4b17a3f9@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by phoudoin): That's under a fresh r31835 gcc2 alpha image, on a Samsung NC10 netbook. I'll attach a backtrace dump as soon as possible, if required too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 13:18:11 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 29 Jul 2009 11:18:11 -0000 Subject: [Haiku-bugs] [Haiku] #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot In-Reply-To: <041.2b4973da5127fda954fd0de9915ff092@haiku-os.org> References: <041.2b4973da5127fda954fd0de9915ff092@haiku-os.org> Message-ID: <050.24e354c76e27f9d5ff4fced04a8f3845@haiku-os.org> #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot -------------------------------------+-------------------------------------- Reporter: peyren | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Appearance | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: This one is fixed in r31901. Will investigate why those fonts aren't found next. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 13:18:43 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 29 Jul 2009 11:18:43 -0000 Subject: [Haiku-bugs] [Haiku] #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot In-Reply-To: <041.2b4973da5127fda954fd0de9915ff092@haiku-os.org> References: <041.2b4973da5127fda954fd0de9915ff092@haiku-os.org> Message-ID: <050.535fd4c71951a257640c606152faa92f@haiku-os.org> #4149: Change of 'Fixed font' to 'DejaVu Sans Mono Bold' causes system crash during boot ---------------------------------+------------------------------------------ Reporter: peyren | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by mmlr): * component: Preferences/Appearance => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 14:14:35 2009 From: trac at haiku-os.org (korli) Date: Wed, 29 Jul 2009 12:14:35 -0000 Subject: [Haiku-bugs] [Haiku] #1635: Gl Teapot Bad Rendering On Window Size Expand In-Reply-To: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> References: <040.05fc50751c0cc12a35be6f78a2912f52@haiku-os.org> Message-ID: <049.70d6facc1985351e1127b2d9c1ba6089@haiku-os.org> #1635: Gl Teapot Bad Rendering On Window Size Expand ---------------------------------+------------------------------------------ Reporter: cebif | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed Comment: I think it should be fixed by r31412. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 14:57:29 2009 From: trac at haiku-os.org (idefix) Date: Wed, 29 Jul 2009 12:57:29 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button Message-ID: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- When you press the `stop` button while Installer is collecting the copy information, it won't stop until it's finished collecting. It should immediately stop, just like it does when copying files. Steps to reproduce: - Press the `Begin` button; Installer begins collecting copy information - Press the `Stop` button; a windows pops up asking if you're sure - Press that window's `Stop` button - You'll notice that Installer continues collecting copy information. Pressing the `Stop` button again has no effect and you'll have to wait for Installer to finish collecting before it gets back to the main screen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 14:58:35 2009 From: trac at haiku-os.org (phoudoin) Date: Wed, 29 Jul 2009 12:58:35 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown In-Reply-To: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> References: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> Message-ID: <052.7667d493c549d34552a15c0cd402d2cc@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by phoudoin): * priority: normal => high -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:04:42 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 29 Jul 2009 13:04:42 -0000 Subject: [Haiku-bugs] [Haiku] #4148: Font setting is not saved correctly after system restart In-Reply-To: <041.795ebb4947bcc0964536012d58c595fb@haiku-os.org> References: <041.795ebb4947bcc0964536012d58c595fb@haiku-os.org> Message-ID: <050.ebb124b5e2724827e9668a456b893c19@haiku-os.org> #4148: Font setting is not saved correctly after system restart ---------------------------------+------------------------------------------ Reporter: peyren | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => fixed * component: Preferences/Appearance => Servers/app_server Comment: Fixed in r31904. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:05:12 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 13:05:12 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.aa05f6a418bd9e251a91505107ac6eb9@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): If you want to have a look, the stopping is done via a BLocker, IIRC. What the CopyEngine does with regards to this lock during the actual copy process needs to be replicated to the recursive collection of information. The problem may be that this slows down the collection somewhat, which ideally is fast as possible. Usually, users want to install, not stop, so one may implement a fix which degrades the usual case. I am undecided. Maybe the check for the lock wouldn't be so bad, since usually the file data is not in the cache, so the waiting times for the I/O are much worse than the check for the lock everywhere. It's probably ok to check only when entering a new directory, not for each file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:16:04 2009 From: trac at haiku-os.org (idefix) Date: Wed, 29 Jul 2009 13:16:04 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.dcdbbeaaeea47e71735286c7ad239fa7@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by idefix): Replying to [comment:1 stippi]: > If you want to have a look, the stopping is done via a BLocker, IIRC. What the CopyEngine does with regards to this lock during the actual copy process needs to be replicated to the recursive collection of information. Yes, I got that far by reading the source code. Unfortunately, at the moment, I don't understand enough of BLocker to implement it in the collecting process. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:24:35 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 13:24:35 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.79874d19363ba33eccd1c4e67635049b@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): The trick is that it's safe to call Lock() on a deleted BLocker. In that case, Lock() fails. So these lines: {{{ AutoLocker lock(locker); if (locker != NULL && !lock.IsLocked()) { // We are supposed to quit return B_CANCELED; } }}} Make the copy process stop. You could just add this before entering a new directory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:40:07 2009 From: trac at haiku-os.org (emitrax) Date: Wed, 29 Jul 2009 13:40:07 -0000 Subject: [Haiku-bugs] [Haiku] #4154: [Tracker]: Find result window won't update its title Message-ID: <042.7757840262d6dd663cb90d5254f13e48@haiku-os.org> #4154: [Tracker]: Find result window won't update its title ----------------------------------+----------------------------------------- Reporter: emitrax | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Alt + f Enter a keyword and start a search Edit the search with different keywords New result window will have old keywords as title, while user would expect new keywords. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:41:35 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 13:41:35 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.299f31bb373b31761fb7e40883ea9353@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Changes (by stippi): * owner: korli => stippi Comment: Actually, forget that. It's of course not safe to call Lock() on a deleted BLocker. I must be getting old, and Installer is broken in this respect! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:44:24 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 13:44:24 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.e57210c0aca7c702d8d2cd820557ba4d@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button ------------------------------------+--------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): I think what should happen is that the BLocker should be replaced by a semaphore ID, though the mechanism would be absolutely similar. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 15:52:05 2009 From: trac at haiku-os.org (emitrax) Date: Wed, 29 Jul 2009 13:52:05 -0000 Subject: [Haiku-bugs] [Haiku] #2118: Bash Upgrade In-Reply-To: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> References: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> Message-ID: <051.c01eab11f61c3d6b136d7b46f198f2f6@haiku-os.org> #2118: Bash Upgrade ---------------------------------------------+------------------------------ Reporter: emitrax | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by emitrax): IIRC the show stopper for this one was lack of wchar support, which should be in place now? Sorry but I've been very busy to follow everything. Last night I wanted to test BFS with a few scripts, but ran into a few problems, like I ran out of memory and couldn't launch any other program from the shell. And I had to end it (the bash) and restart it. I didn't even bother to investigate as I'm sure its related to the version of bash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 17:06:42 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 15:06:42 -0000 Subject: [Haiku-bugs] [Haiku] #4153: Installer doesn't stop collecting copy information when user pressed stop button In-Reply-To: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> References: <041.b40653165acb8ef7d213a8dd264b4559@haiku-os.org> Message-ID: <050.d5af4e53fbc85d4550f3a9d73dbd7210@haiku-os.org> #4153: Installer doesn't stop collecting copy information when user pressed stop button -------------------------------------+-------------------------------------- Reporter: idefix | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r31912. Turns out I wasn't quite so senile... the previous mechanism was based on the idea that you could delete a *locked* BLocker, which would make a thread which blocked on the locked BLocker get B_BAD_SEM as result for it's locking request. The new mechanism is more straight forward and doesn't have a race condition that the previous code needed to take into account. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 18:04:19 2009 From: trac at haiku-os.org (zooey) Date: Wed, 29 Jul 2009 16:04:19 -0000 Subject: [Haiku-bugs] [Haiku] #3308: Possible floating point failures in IEEE 754 tests In-Reply-To: <042.c678ed2b992fdb50f53485f9b7f8d349@haiku-os.org> References: <042.c678ed2b992fdb50f53485f9b7f8d349@haiku-os.org> Message-ID: <051.745307d5c5ca8ddc5c0e7e6e2e91b701@haiku-os.org> #3308: Possible floating point failures in IEEE 754 tests --------------------------------+------------------------------------------- Reporter: scottmc | Owner: zooey Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31919. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 18:27:42 2009 From: trac at haiku-os.org (maxime.simon) Date: Wed, 29 Jul 2009 16:27:42 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. Message-ID: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- In Haiku, I got this issue when compiling DumpRenderTree. ( a tool to test the rendering of our WebKit port ). The command was {{{ jam -j2 DumpRenderTree }}} The ASSERT which failed and the backtrace are in the screenshot as attachment. Note: I made a checkfs of my two drives, but I still got the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 18:58:48 2009 From: trac at haiku-os.org (maxime.simon) Date: Wed, 29 Jul 2009 16:58:48 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.9f5c28579a0f1b473e38569a5e7df0ad@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by maxime.simon): I tried with other targets (still in WebKit), and using {{{ jam -j2 foobar }}}. It failed again. So I tried with {{{ jam -q foobar }}} and I didn't get any PANIC: ASSERT FAILED. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 19:33:53 2009 From: trac at haiku-os.org (zooey) Date: Wed, 29 Jul 2009 17:33:53 -0000 Subject: [Haiku-bugs] [Haiku] #4031: missing strtof() In-Reply-To: <042.accf004aeef5d22998f1376142073225@haiku-os.org> References: <042.accf004aeef5d22998f1376142073225@haiku-os.org> Message-ID: <051.1fde3bd32512b3ff33d0625d8a6b2a70@haiku-os.org> #4031: missing strtof() --------------------------------+------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => fixed Comment: Fixed in r31926. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 19:38:50 2009 From: trac at haiku-os.org (zooey) Date: Wed, 29 Jul 2009 17:38:50 -0000 Subject: [Haiku-bugs] [Haiku] #3593: strtod doesn't support "INF" input In-Reply-To: <042.cc826bf976486fa02ed203176ab878b2@haiku-os.org> References: <042.cc826bf976486fa02ed203176ab878b2@haiku-os.org> Message-ID: <051.37a380d4fd3e335a2bf97e1e3f56fb90@haiku-os.org> #3593: strtod doesn't support "INF" input --------------------------------+------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => fixed Comment: Fixed in r31919, by using the strod()-implementation from glibc, which already lived in our repo. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 19:52:54 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 29 Jul 2009 17:52:54 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.871bf0e324c90d680c516bb08842adb5@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Hi Stephan, The good news is Setmode is now executed. However: the flags are not all 'transparantly' used as BeOS does. The officially unused flags are filtered on Haiku, while BeOS handles all bits. The behaviour on Haiku is that it seems Setmode only accesses the accelerant if the mode differs from the already set one. If only (unknown)flags are different it won't call the accelerant, nor will it save them for the next boot. The app_server dedraws the screen however as a 'proof' Setmode is actually called from the app. Can it be proposemode also is not transparant for all flags? The setmode command with the workspace argument seems to react the same as the 'normal' setmode command: so in that sense setmode is now fixed. Anyhow: I am talking about the flags since the Matrox and nVidia drivers use these flags for dualhead and TVout support. It would be handy if that would be possible on Haiku, saves me some time rewriting the driver for the Haiku screen preflet at this time.. Please let me know if the flags will be modified to behave like BeOS or not. :-) Bye and thanks for the quick response!! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 20:01:36 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 29 Jul 2009 18:01:36 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.fcc9148723b456d28b7f7c74f5b825a6@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there someguy, Please also see ticket #4052 for status updates on dualhead support/bebits dualhead setup program working. Dualhead setup now partially works, and you can set dualhead if you select another resolution first and then switch back to the one you want, while enabling dualhead. Over here I now have two screens on for the first time on Haiku :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 20:03:14 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 29 Jul 2009 18:03:14 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.dfd6b24a352218f2c8ae9d3d86446a54@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hmm, I am axperiencing a deja-vu ;-) I mean ticket #4144.. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 20:04:03 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 29 Jul 2009 18:04:03 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.78f957bc8895eb14c6f67bf80c7ccdeb@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Bug #4052 is 'the same' as this one BTW. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 20:44:44 2009 From: trac at haiku-os.org (stippi) Date: Wed, 29 Jul 2009 18:44:44 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.74f735cd7d0252fa9b373d9a32a8f414@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Rudolf, may I encourage you to look into app_server to get this fixed yourself? It seems everyone is busy with something else, and Haiku development usually works this way. I know from experience that one can be reluctant to dig into other peoples code to get something accomplished, but it's most often the only way in the end. Otherwise you have to wait for "somebody" to get around to code this for you, but "somebody" may not even have the facilities to test the changes properly or know what to look out for. For example, I have only one screen, and I don't even have a setup with a driver that supports dual screen at the moment. Don't be afraid of app_server code, it's seen a few iterations of rewrites and refactoring. It should be fairly clean and at least be easy to follow the code so you know where the changes should go, and in this particular case, all you have to fix is the proper storage of some flags value. You probably have this going in an hour or two. The classes you want to look at are: * ServerApp (get's the screen mode change command) * Desktop and VirtualScreen (know the current screen mode) * AccelerantHWInterface (calls into the accelerant) * DesktopSettings (for persistency) Hope this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 21:04:35 2009 From: trac at haiku-os.org (axeld) Date: Wed, 29 Jul 2009 19:04:35 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.4df6040f169b6d62aac297249c9e947d@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Are you building Haiku yourself and recently changed some kernel debug settings? Or only updated parts of Haiku? The code in question looks perfectly fine, and if this would be an actual bug, everyone should run into it all the time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 21:17:18 2009 From: trac at haiku-os.org (maxime.simon) Date: Wed, 29 Jul 2009 19:17:18 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.bedb73661ef912e6514fa2ce25c3193d@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by maxime.simon): I'm building Haiku myself, but I didn't hit anything in the kernel debug settings.[[BR]] In fact I got the issue on Haiku, when using {{{ jam -j2 }}}. If the issue was from my file system, when making a checkfs I should get some warnings about corrupted data, isn't it?[[BR]] I restarted the compilation 3 times, with different targets (but in the same directory) and 3 times I got the issue. But the last building using the same flag didn't send me to the KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 21:46:06 2009 From: trac at haiku-os.org (zooey) Date: Wed, 29 Jul 2009 19:46:06 -0000 Subject: [Haiku-bugs] [Haiku] #3460: redundant redeclarations In-Reply-To: <042.e0cc5d5d93b92518e6d5e1463881fb31@haiku-os.org> References: <042.e0cc5d5d93b92518e6d5e1463881fb31@haiku-os.org> Message-ID: <051.d8093c4dd33ee37108017bcf590fffcf@haiku-os.org> #3460: redundant redeclarations ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => fixed Comment: Fixed in r31938. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:12:25 2009 From: trac at haiku-os.org (Blub) Date: Wed, 29 Jul 2009 20:12:25 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.7dafcd4fe4fdc8fd9b1df0b07d6fa778@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on ----------------------------------+----------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by Blub): attached a diff which should fix the problem [] is executed before the preceeding dereferencing * parentheses fixed the problem runs fine again here :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:15:49 2009 From: trac at haiku-os.org (idefix) Date: Wed, 29 Jul 2009 20:15:49 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command Message-ID: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- When you issue the same command multiple times after each other in the Terminal, they all get written to `.bash_history`. This is extremely frustrating when you move up in the history with the `up-arrow` key. I would like to see this changed; just as changeset:30953 did for the history in KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:18:54 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 29 Jul 2009 20:18:54 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.cb5199bf5679cef4b8b1f5b7477d4ce3@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): This could probably be considered a duplicate of ticket #2118 ... this is builtin bash behavior that's been changed in more recent versions of bash, at least based on my linux install here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:26:06 2009 From: trac at haiku-os.org (pulkomandy) Date: Wed, 29 Jul 2009 20:26:06 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.5401c8e396e71268f193372bd515caff@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by pulkomandy): seen in my .bashrc in debian: # don't put duplicate lines in the history. See bash(1) for more options # don't overwrite GNU Midnight Commander's setting of `ignorespace'. export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups # ... or force ignoredups and ignorespace export HISTCONTROL=ignoreboth Should this work ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:39:25 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 29 Jul 2009 20:39:25 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.5655258c3948bdb43db135478f190cc7@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on ----------------------------------+----------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by mmlr): Nice catch definitely! Applied in r31940. Please verify so this one can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:44:55 2009 From: trac at haiku-os.org (idefix) Date: Wed, 29 Jul 2009 20:44:55 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.75fa6ebed34cd2764a658fd468351c96@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by idefix): Replying to [comment:2 pulkomandy]: > Should this work ? Yes, I issued `export HISTCONTROL=ignoredups` on the command line and it now behaves as I would like it to. I would like to see this behaviour the default; but if it's the default in more recent versions of bash (as [comment:1 anevilyak] pointed out), this ticket might as well be closed as duplicate of ticket:2118. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:47:39 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 29 Jul 2009 20:47:39 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.37f6a7fed21936c3a65a50f5e0520cb2@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Replying to [comment:3 idefix]: > I would like to see this behaviour the default; but if it's the default in more recent versions of bash (as [comment:1 anevilyak] pointed out), this ticket might as well be closed as duplicate of ticket:2118. Based off pulkomandy's information, I'm actually no longer certain if that's a default or something this particular distro put into the default bashrc, which we could certainly do in Haiku as well in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 22:54:28 2009 From: trac at haiku-os.org (idefix) Date: Wed, 29 Jul 2009 20:54:28 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.b8891ecf8377151cb8bf67ed25a374db@haiku-os.org> #4156: Don't write command to history when it's the same as previous command -----------------------------------+---------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by idefix): Yes, please. Apparently, even [https://bugs.launchpad.net/ubuntu/+source/bash/+bug/66539 Ubuntu] is doing it. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jul 29 23:39:17 2009 From: trac at haiku-os.org (axeld) Date: Wed, 29 Jul 2009 21:39:17 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.24ea4fef19060e69bc3e2f6a55c6375d@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Nah, I suspected a build problem, but I just ran into this thing, too. I don't really understand how this problem can occur, but r31944 fixes a recently introduced bug that should be responsible for it. I'll do some more testing tonight, and if I can't reproduce it anymore, I'll close it as fixed for now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 00:21:28 2009 From: trac at haiku-os.org (kallisti5) Date: Wed, 29 Jul 2009 22:21:28 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.56ae780d4c98d9529f7ce3aa2574a3b1@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): ok, used readelf was able to extract a listing of the missing relocations as per the offsets in the errors. Magic fingers! {{{ 8017b3b0 000e3201 R_PPC_ADDR32 00000000 _Z18_user_atomic_set64 + 0 8018d208 000e3215 R_PPC_JMP_SLOT 00000000 _Z18_user_atomic_set64 + 0 8017b3b8 0009ef01 R_PPC_ADDR32 00000000 _Z27_user_atomic_test_ + 0 8018c340 0009ef15 R_PPC_JMP_SLOT 00000000 _Z27_user_atomic_test_ + 0 8017b3c0 000ae201 R_PPC_ADDR32 00000000 _Z18_user_atomic_add64 + 0 8018c6f0 000ae215 R_PPC_JMP_SLOT 00000000 _Z18_user_atomic_add64 + 0 8017b3c8 0000d301 R_PPC_ADDR32 00000000 _Z18_user_atomic_and64 + 0 8018a428 0000d315 R_PPC_JMP_SLOT 00000000 _Z18_user_atomic_and64 + 0 8017b3d0 0008cc01 R_PPC_ADDR32 00000000 _Z17_user_atomic_or64P + 0 8018bf08 0008cc15 R_PPC_JMP_SLOT 00000000 _Z17_user_atomic_or64P + 0 8017b3d8 00063501 R_PPC_ADDR32 00000000 _Z18_user_atomic_get64 + 0 8018b640 00063515 R_PPC_JMP_SLOT 00000000 _Z18_user_atomic_get64 + 0 8018d1c0 000e0d15 R_PPC_JMP_SLOT 00000000 arch_cpu_init_percpu + 0 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 00:26:57 2009 From: trac at haiku-os.org (kallisti5) Date: Wed, 29 Jul 2009 22:26:57 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.e5c92818fccb026e193c3afaa738104f@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): arch_cpu_init_percpu is defined in the following files {{{ src/system/kernel/arch/m68k/arch_cpu.cpp:arch_cpu_init_percpu(kernel_args *args, int curr_cpu) src/system/kernel/arch/x86/arch_cpu.cpp:arch_cpu_init_percpu(kernel_args *args, int cpu) }}} oh look! function not defined for ppc! For now a function which returns 0 should be enough until multi cpu support is added for PPC -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 00:45:26 2009 From: trac at haiku-os.org (kallisti5) Date: Wed, 29 Jul 2009 22:45:26 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.55eca48410519e1ffa61560bdb13b8fe@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): adding patch to add arch_cpu_init_percpu to ppc code. This patch also cleans up the my previous isync patch that fixes the PPC bootloader not starting. attachment: isyncmissingcpuinit.diff -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 00:52:48 2009 From: trac at haiku-os.org (axeld) Date: Wed, 29 Jul 2009 22:52:48 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.60e248f9410b6f5b67ceb35fe023188a@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. ------------------------------+--------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => blocker * milestone: R1 => R1/alpha1 Comment: Just ran into it again, this one must be new. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 01:50:51 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 29 Jul 2009 23:50:51 -0000 Subject: [Haiku-bugs] [Haiku] #4156: Don't write command to history when it's the same as previous command In-Reply-To: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> References: <041.e951bc02c9659bbb01fd4768c91fc3a2@haiku-os.org> Message-ID: <050.9cb02fdb81c2a5420a2cd8b756ff5bef@haiku-os.org> #4156: Don't write command to history when it's the same as previous command ------------------------------------+--------------------------------------- Reporter: idefix | Owner: jackburton Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Done in r31953. Thanks for all the research! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 02:07:36 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Jul 2009 00:07:36 -0000 Subject: [Haiku-bugs] [Haiku] #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. In-Reply-To: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> References: <047.0368d2655fb54be1057bdf2efa433085@haiku-os.org> Message-ID: <056.42a5882134439d3c8e2d86ff92258eec@haiku-os.org> #4155: ASSERT FAILED in bfs/Inode.h:178 when building source code. -------------------------------+-------------------------------------------- Reporter: maxime.simon | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r31952 - this caused another bug, though, which was fixed in r31954. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 02:07:39 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 00:07:39 -0000 Subject: [Haiku-bugs] [Haiku] #4157: File Descriptor Disconnect Handling Broken Message-ID: <043.39a92049702c664d8191bc7fa258e690@haiku-os.org> #4157: File Descriptor Disconnect Handling Broken ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ The disconnect handling for file descriptors has several issues: - Disconnected file_descriptors are leaked (put_fd() sets the ref_count to -1). - There are race conditions, particularly in put_fd(). - Disconnected file descriptors can be dup()ed and copied on fork(), messing with the mangled ref_count. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 02:45:10 2009 From: trac at haiku-os.org (PieterPanman) Date: Thu, 30 Jul 2009 00:45:10 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.906feb7d61fd8dbe574f36008edb9cb1@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by PieterPanman): Yeah, I'm still alive :) Attached two screenshots to keep you in the loop. I've implemented both basic "sort by" modes, so you can now sort either by connection or by category. The display of the data will be done in a nicer looking way (either using the GridLayout, or a ColumnListView ala sounds preferences). I cleaned up the code a bit and it's now using the layout manager properly. After I've finished my todo list of basic Device functionality (and added USB support) I'll offer it to be included in the haiku tree, if it is deemed good enough. Then I'm sure it can be improved more with some changes to the actual Device Manager (for example, automatically refresh on hw changes, showing drivers used, device paths published etc). For those of you interested, the source and executable are here: (only for haiku) http://www.panman.eu/haiku/devices.zip -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 03:09:21 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 01:09:21 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 Message-ID: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ With a current version I get a panic very early in the boot process such that I can't even invoke the kernel debugger. I see this on serial: {{{ Welcome to kernel debugger output! Haiku revision: 31957 CPU 0: type 0 family 15 extended_family 0 model 11 extended_model 2 stepping 1, string 'AuthenticAMD' CPU 0: vendor 'AMD' model name 'AMD Athlon(tm) 64 X2 Dual Core Processor 3800+' CPU 0: features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh mmx fxsr sse sse2 htt sse3 syscall nx mmxext ffxsr long 3dnowext 3dnow heap_add_area: area -1 added to small heap 0x81191000 - usable range 0x8119e000 - 0x81991000 heap_add_area: area -1 added to medium heap 0x81991000 - usable range 0x81992000 - 0x81e5d000 heap_add_area: area -1 added to large heap 0x81e5dccc - usable range 0x81e5f000 - 0x82191000 slab: init base 0x82191000 + 0x4000 PANIC: page fault, but interrupts were disabled. Touching address 0x0000000c from eip 0x80074d41 Welcome to Kernel Debugging Land... Thread 0 "" running on CPU 0 }}} Offhand the only revision I see today that could be a potential culprit is r31941, binary searching now to verify if that is indeed the culprit or not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 03:09:44 2009 From: trac at haiku-os.org (kallisti5) Date: Thu, 30 Jul 2009 01:09:44 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.e234f7cb126386d4dfd9a617e3af5363@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): just a quick note, after the patch above we now get one less failed to relocate entry error (the arch_cpu_init_percpu one) and the kernel drops back to the openfirmware prompt. I think the atomic_set,test,etc errors are because the Kernel is having trouble accessing the functions in libroot/os/arch/ppc/atomic.S -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 03:21:45 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 30 Jul 2009 01:21:45 -0000 Subject: [Haiku-bugs] [Haiku] #4055: Replicants & Shift+Alt+K (Arrange All?) In-Reply-To: <041.0df72ee4b5c41086be0569c13afd8fec@haiku-os.org> References: <041.0df72ee4b5c41086be0569c13afd8fec@haiku-os.org> Message-ID: <050.8d872614661e73d67d4ff5f77dcac2f7@haiku-os.org> #4055: Replicants & Shift+Alt+K (Arrange All?) ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Description changed by mmadia: Old description: > There is an issue with using Desktop replicants and Tracker's ability to > re-arrange icons (Shift+Alt+K). When the replicant such as workspaces is > covering the upper left hand corner, Shift+Alt+K will properly re-arrange > the icons, except a single volume icon. That single volume icon will > appear underneath the replicant. If Disks Icon is enabled, the disks icon > will appear underneath the replicant. New description: There is an issue with using Desktop replicants and Tracker's ability to re-arrange icons (Shift+Alt+K). When the replicant such as workspaces is covering the upper left hand corner, Shift+Alt+K will properly re-arrange the icons, except a single volume icon. That single volume icon will appear underneath the replicant. Update: Turns out it's not the Disks Icon, but the first alphabetical icon. Occurs when the Disks Icon is disabled & enabled. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 04:15:30 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 02:15:30 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.fd5f841ed8e43b78c6b72d690f148b9d@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Confirmed that it still boots at r31940, checking r31941 now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 04:38:06 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 02:38:06 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.d55f4bbd4eb90525c970f1ad2cbebcaa@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: axeld => bonefish Comment: The culprit is in fact r31942. If it helps, I have 1GB of RAM and a 200MB trace buffer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 06:18:05 2009 From: trac at haiku-os.org (someguy) Date: Thu, 30 Jul 2009 04:18:05 -0000 Subject: [Haiku-bugs] [Haiku] #4052: Dual head video not working with GeForce FX5200 AGP In-Reply-To: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> References: <042.002c924e310416b52f53e9e50f4ff70d@haiku-os.org> Message-ID: <051.9c73a100f580cf27d99ba517dc779d5c@haiku-os.org> #4052: Dual head video not working with GeForce FX5200 AGP -------------------------------------+-------------------------------------- Reporter: someguy | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by someguy): This is great! I got it to work by just using dual head setup on 31876. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 06:33:30 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 04:33:30 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.54c5e9f6d086e49f806eecbceeeb2cdb@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Further info: reducing the trace buffer to 20MB has the same result ; disabling tracing entirely however results in a bootable system. Anything I can do to help narrow this down? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 08:20:07 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 30 Jul 2009 06:20:07 -0000 Subject: [Haiku-bugs] [Haiku] #4159: Python regression test test_socket.py fails Message-ID: <042.4eb75f6fd0edef570031a71c1dc9f09f@haiku-os.org> #4159: Python regression test test_socket.py fails --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- To test build Haiku with the Python OptionalPackage enabled, and then run /boot/common/lib/python2.6/test>python test_socket.py Test output is attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 09:06:45 2009 From: trac at haiku-os.org (emitrax) Date: Thu, 30 Jul 2009 07:06:45 -0000 Subject: [Haiku-bugs] [Haiku] #4157: File Descriptor Disconnect Handling Broken In-Reply-To: <043.39a92049702c664d8191bc7fa258e690@haiku-os.org> References: <043.39a92049702c664d8191bc7fa258e690@haiku-os.org> Message-ID: <052.80bee7d97172fdb71dca18f0a58dc6f1@haiku-os.org> #4157: File Descriptor Disconnect Handling Broken ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by emitrax): Could this be the cause of what I've experienced in bug #2381 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 09:25:24 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 07:25:24 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown In-Reply-To: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> References: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> Message-ID: <052.bcdc7c4b7e7a6e718183ad0ecf679b83@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by phoudoin): The crash is not systematic: sometime it does, sometime shutdown process stop Deskbar gracefully. Could be a race condition, but I didn't check yet with SMP support disabled... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 10:25:38 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 30 Jul 2009 08:25:38 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.e69e0bf4e5edbdc871cbedf2a9cb3b05@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Hi Stephan, Thanks for your confidence in me :-) So. I plan to comment out this line since it's incompatible to BeOS: BScreen::SetMode(): Screen::SetMode(const display_mode& mode, bool makeDefault) line: current.flags = mode.flags should not be there. If all is right, SetMode is only issued by the app_server upon workspace switches if and when the modes differ: even if only by a flag! If a mode differs even by a single bit the accelerant _should_ be called to handle this. If you don't object, I'll kill that line above. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 12:07:04 2009 From: trac at haiku-os.org (tqh) Date: Thu, 30 Jul 2009 10:07:04 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.fb82d9ab50a2592ead2af0a854a398cc@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on ----------------------------------+----------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by tqh): Confirming fixed. Impressive find, did you debug or just proofread :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 12:42:20 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 30 Jul 2009 10:42:20 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.f863f078fe6138c1a39e0e79ded21b4e@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Stephan, About persistency: the error sits in VirtualScreen.cpp: mode.flags are not saved in StoreConfiguration(). Also AddScreen() does not retreive the flags (of course). It should, and it should issue the (Be) Setmode(mode, persistency) function, after it itself setup the entire mode, instead of only the pieces. I _could_ modify this to do that, but I am not confident I won't detroy something, or maybe I need to also adjust stuff in other files I don't know about?? I'd be more in piece of mind if you or someone else who really knows what he's doing would do that instead.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:11:40 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 30 Jul 2009 11:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on In-Reply-To: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> References: <038.facadc98e142511eec0a8447275acc0d@haiku-os.org> Message-ID: <047.5a93a100bee13d8d68d9deb2cf5e0d39@haiku-os.org> #4143: usb_hid: Pagefault in AddonMonitor on boot, r31838 and on -----------------------------------+---------------------------------------- Reporter: tqh | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback, closing as fixed by r31940. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:16:27 2009 From: trac at haiku-os.org (stippi) Date: Thu, 30 Jul 2009 11:16:27 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.c6f5fab365963011f9989f9b84c59425@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by stippi): I've tried it and I think it's really nice already! How about we include this as it is and you continue to work on it? Something not being 100% finished has never been a reason to exclude it from Haiku, has it? :-) Now I am going to have a look at the source... you did follow the guides lines closely, did you? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:24:17 2009 From: trac at haiku-os.org (PieterPanman) Date: Thu, 30 Jul 2009 11:24:17 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.db569dd6ab0b36013f446f322e0b454f@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by PieterPanman): You can look, but I didn't particularly follow the style guidelines yet, just some common sense stuff. Keep in mind it is a WIP. I will clean it up soon, but if you see any glaring error, feel free to point it out. If you do look at it, I was wondering why the bottom scrollbar always has a small drag button. I would expect it to grow as you make the ScrollView bigger. I have to say I'm really liking the layout manager, but we're severely lacking documentation for it. How about adding doxygen to it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:27:21 2009 From: trac at haiku-os.org (stippi) Date: Thu, 30 Jul 2009 11:27:21 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.e8395c24d65e75fcd4397f13407bb341@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by stippi): The code looks pretty good, but it could definitely follow our style guide yet more closely. It would be great if you could read the style guide again and adjust a few aspects of the code accordingly. It's just that we are trying hard to have everything in the repo be consistent, especially when checking in new code. Thanks a lot for your work, it's very much appreciated, I wanted to be able to use such an app very much, and your plans for it (especially the reporting features, according to the docs) are also very nice! As for your question, the BOutlineListview and BScrollView do have layout friendly constructors, I saw you don't use them, but maybe the problem you saw has another reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:30:29 2009 From: trac at haiku-os.org (stippi) Date: Thu, 30 Jul 2009 11:30:29 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.6ab31381365cd95bb372fdf205dffac4@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Hm, but I think you know what you are doing. If you don't feel confident in commiting the fix, you could at least attach a patch here. If you cannot see any regressions in your testing after doing these changes, but stuff that didn't work before suddenly works, then it's an improvement, no? :-D -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:35:37 2009 From: trac at haiku-os.org (PieterPanman) Date: Thu, 30 Jul 2009 11:35:37 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.a6da04becfa67e7a10ada487f9859043@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by PieterPanman): Thanks for your feedback. I understand and I'll apply it more thoroughly. Will also try the layout friendly constructors, see if that helps. FYI, I have a todo list on top op Devices.cpp. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:37:27 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 11:37:27 -0000 Subject: [Haiku-bugs] [Haiku] #4157: File Descriptor Disconnect Handling Broken In-Reply-To: <043.39a92049702c664d8191bc7fa258e690@haiku-os.org> References: <043.39a92049702c664d8191bc7fa258e690@haiku-os.org> Message-ID: <052.5795da9aec268dc5b14da984597b015f@haiku-os.org> #4157: File Descriptor Disconnect Handling Broken ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:1 emitrax]: > Could this be the cause of what I've experienced in bug #2381 ? #2381 has been closed as user error (leaking FDs). It doesn't have anything to do with this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:42:02 2009 From: trac at haiku-os.org (PieterPanman) Date: Thu, 30 Jul 2009 11:42:02 -0000 Subject: [Haiku-bugs] [Haiku] #3185: Device Manager Application In-Reply-To: <047.c214c8172ca1609b656435425f478704@haiku-os.org> References: <047.c214c8172ca1609b656435425f478704@haiku-os.org> Message-ID: <056.e2e018f1a034bd999311a1271f9c14d4@haiku-os.org> #3185: Device Manager Application ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Devices | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by PieterPanman): That should have been Device.cpp. Btw, you can access it on my svn. Compiling is a little tricky as you need to have a built haiku tree for the PCI dev id header file. Will be solved as soon as I integrate it into Haiku's tree and jam. {{{ co svn://svn.panman.eu/devicemanager/trunk devices }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 13:57:45 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 11:57:45 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.22aa12c957f795640ad0efbfb0caf5ea@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): I believe the kernel debugger should be usable. You just don't get on- screen output. I.e. you can type on the machine and get the output via serial output. A stack trace would be very much appreciated. If it doesn't work please attach an objdump of the function hit by the eip. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 14:00:01 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 12:00:01 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.cc2fd95cc95c430b9d2643c6df01ea64@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Forgot to ask: Does this happen on the first boot or only on reboots? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 14:34:16 2009 From: trac at haiku-os.org (nielx) Date: Thu, 30 Jul 2009 12:34:16 -0000 Subject: [Haiku-bugs] [Haiku] #4132: [Deskbar] shelf width have space only for 3 icons In-Reply-To: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> References: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> Message-ID: <049.35ff02463f4c50e7f6e6dea72614862d@haiku-os.org> #4132: [Deskbar] shelf width have space only for 3 icons -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: duplicate | Blockedby: 4133 Platform: All | Blocking: -----------------------------------+---------------------------------------- Old description: > Currently deskbar' shelf have spase only for 3 icons, but have more space > which is wasted. If you enable "24 Hour clock" settings 4 icons could > take it place in one row.[[BR]]See screenshot:[[BR]] > [[Image(before.png)]][[BR]] > [[Image(after.png)]] New description: Currently deskbar' shelf have spase only for 3 icons, but have more space which is wasted. If you enable "24 Hour clock" settings 4 icons could take it place in one row.[[BR]]See screenshot:[[BR]] [[BR]] -- Comment(by nielx): Note: removed screenshots from the text as they don't seem to be here (and they keep popping up the error log). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 14:50:09 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 12:50:09 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.6874d6a8038b8bfd84a79556e491449e@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Replying to [comment:5 bonefish]: > Forgot to ask: Does this happen on the first boot or only on reboots? That was on first boot, building with tracing enabled right now to get you the requested backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:06:06 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 13:06:06 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.dc294126963df4e6d5a9ffb7178a36f0@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Keyboard input to the kernel debugger does indeed work, but it recognizes none of its commands at this point: {{{ kdebug> bt Unknown command "bt". Enter "help" to get a list of all supported commands. kdebug> sc Unknown command "sc". Enter "help" to get a list of all supported commands. kdebug> help Unknown command "help". Enter "help" to get a list of all supported commands. }}} Assuming I did so correctly, objdump: {{{ [rene at leviathan ~/devel/haiku/generated- gcc4/objects/haiku/x86/release/system/kernel]$ objdump -d --start- address=0x80074e09 ./kernel_x86 | less ./kernel_x86: file format elf32-i386-freebsd Disassembly of section .text: 80074e09 <_ZL14allocate_entrymt+0x14>: 80074e09: 83 78 0c 00 cmpl $0x0,0xc(%eax) 80074e0d: 0f 84 4b 01 00 00 je 80074f5e <_ZL14allocate_entrymt+0x169> 80074e13: 85 db test %ebx,%ebx 80074e15: 0f 84 43 01 00 00 je 80074f5e <_ZL14allocate_entrymt+0x169> 80074e1b: 81 fb fb ff 00 00 cmp $0xfffb,%ebx 80074e21: 0f 87 37 01 00 00 ja 80074f5e <_ZL14allocate_entrymt+0x169> 80074e27: e9 41 01 00 00 jmp 80074f6d <_ZL14allocate_entrymt+0x178> 80074e2c: 9c pushf 80074e2d: 58 pop %eax 80074e2e: fa cli 80074e2f: c1 e8 09 shr $0x9,%eax 80074e32: 83 e0 01 and $0x1,%eax 80074e35: 89 45 ec mov %eax,0xffffffec(%ebp) 80074e38: 83 ec 0c sub $0xc,%esp 80074e3b: ff 75 e4 pushl 0xffffffe4(%ebp) 80074e3e: e8 80 fd fd ff call 80054bc3 80074e43: c6 45 eb 01 movb $0x1,0xffffffeb(%ebp) 80074e47: 83 c4 10 add $0x10,%esp 80074e4a: 8d 43 03 lea 0x3(%ebx),%eax 80074e4d: c1 e8 02 shr $0x2,%eax 80074e50: 89 45 f0 mov %eax,0xfffffff0(%ebp) 80074e53: 89 c7 mov %eax,%edi 80074e55: 47 inc %edi 80074e56: a1 f0 56 13 80 mov 0x801356f0,%eax 80074e5b: 8d 14 bd 00 00 00 00 lea 0x0(,%edi,4),%edx 80074e62: 03 50 0c add 0xc(%eax),%edx 80074e65: 8b 40 04 mov 0x4(%eax),%eax 80074e68: 05 00 00 40 01 add $0x1400000,%eax 80074e6d: 39 c2 cmp %eax,%edx 80074e6f: 77 0f ja 80074e80 <_ZL14allocate_entrymt+0x8b> 80074e71: eb 63 jmp 80074ed6 <_ZL14allocate_entrymt+0xe1> 80074e73: e8 ff f9 ff ff call 80074877 <_ZL16free_first_entryv> 80074e78: 84 c0 test %al,%al 80074e7a: 0f 84 a2 00 00 00 je 80074f22 <_ZL14allocate_entrymt+0x12d> 80074e80: a1 f0 56 13 80 mov 0x801356f0,%eax 80074e85: 8b 50 0c mov 0xc(%eax),%edx 80074e88: 39 50 08 cmp %edx,0x8(%eax) 80074e8b: 77 e6 ja 80074e73 <_ZL14allocate_entrymt+0x7e> 80074e8d: 39 50 04 cmp %edx,0x4(%eax) 80074e90: 0f 84 f3 00 00 00 je 80074f89 <_ZL14allocate_entrymt+0x194> 80074e96: e8 dc f9 ff ff call 80074877 <_ZL16free_first_entryv> 80074e9b: 84 c0 test %al,%al 80074e9d: 0f 85 e6 00 00 00 jne 80074f89 <_ZL14allocate_entrymt+0x194> 80074ea3: eb 7d jmp 80074f22 <_ZL14allocate_entrymt+0x12d> 80074ea5: 66 81 22 00 c0 andw $0xc000,(%edx) 80074eaa: 8a 42 03 mov 0x3(%edx),%al 80074ead: 83 e0 0f and $0xf,%eax 80074eb0: 83 c8 10 or $0x10,%eax 80074eb3: 88 42 03 mov %al,0x3(%edx) 80074eb6: 8b 4b 04 mov 0x4(%ebx),%ecx 80074eb9: 89 4b 0c mov %ecx,0xc(%ebx) 80074ebc: 89 c8 mov %ecx,%eax 80074ebe: 29 d0 sub %edx,%eax 80074ec0: 89 c2 mov %eax,%edx 80074ec2: c1 e2 0c shl $0xc,%edx 80074ec5: 81 e2 00 c0 ff 0f and $0xfffc000,%edx 80074ecb: 8b 01 mov (%ecx),%eax 80074ecd: 25 ff 3f 00 f0 and $0xf0003fff,%eax 80074ed2: 09 d0 or %edx,%eax 80074ed4: 89 01 mov %eax,(%ecx) 80074ed6: a1 f0 56 13 80 mov 0x801356f0,%eax 80074edb: 8b 50 08 mov 0x8(%eax),%edx 80074ede: 8b 40 0c mov 0xc(%eax),%eax 80074ee1: 39 c2 cmp %eax,%edx 80074ee3: 0f 86 b2 00 00 00 jbe 80074f9b <_ZL14allocate_entrymt+0x1a6> 80074ee9: 29 c2 sub %eax,%edx 80074eeb: 89 d3 mov %edx,%ebx 80074eed: c1 fb 02 sar $0x2,%ebx 80074ef0: 39 df cmp %ebx,%edi 80074ef2: 0f 86 a3 00 00 00 jbe 80074f9b <_ZL14allocate_entrymt+0x1a6> 80074ef8: a1 f0 56 13 80 mov 0x801356f0,%eax 80074efd: 8b 40 08 mov 0x8(%eax),%eax 80074f00: 8b 00 mov (%eax),%eax 80074f02: 89 c6 mov %eax,%esi 80074f04: 81 e6 ff 3f 00 00 and $0x3fff,%esi 80074f0a: e8 68 f9 ff ff call 80074877 <_ZL16free_first_entryv> 80074f0f: 84 c0 test %al,%al 80074f11: 74 0f je 80074f22 <_ZL14allocate_entrymt+0x12d> 80074f13: 89 f0 mov %esi,%eax 80074f15: 25 ff ff 00 00 and $0xffff,%eax 80074f1a: 01 c3 add %eax,%ebx 80074f1c: 39 df cmp %ebx,%edi 80074f1e: 77 d8 ja 80074ef8 <_ZL14allocate_entrymt+0x103> 80074f20: eb 79 jmp 80074f9b <_ZL14allocate_entrymt+0x1a6> 80074f22: bb 00 00 00 00 mov $0x0,%ebx 80074f27: eb 03 jmp 80074f2c <_ZL14allocate_entrymt+0x137> 80074f29: ff 46 10 incl 0x10(%esi) 80074f2c: 83 7d e4 00 cmpl $0x0,0xffffffe4(%ebp) 80074f30: 74 31 je 80074f63 <_ZL14allocate_entrymt+0x16e> 80074f32: 80 7d eb 00 cmpb $0x0,0xffffffeb(%ebp) 80074f36: 74 2b je 80074f63 <_ZL14allocate_entrymt+0x16e> 80074f38: 83 ec 0c sub $0xc,%esp 80074f3b: ff 75 e4 pushl 0xffffffe4(%ebp) 80074f3e: e8 7f f8 fd ff call 800547c2 80074f43: 83 c4 10 add $0x10,%esp 80074f46: 8b 45 ec mov 0xffffffec(%ebp),%eax 80074f49: f7 d8 neg %eax 80074f4b: 25 00 02 00 00 and $0x200,%eax 80074f50: 9c pushf 80074f51: 5a pop %edx 80074f52: 81 e2 ff fd ff ff and $0xfffffdff,%edx 80074f58: 09 c2 or %eax,%edx 80074f5a: 52 push %edx 80074f5b: 9d popf 80074f5c: eb 05 jmp 80074f63 <_ZL14allocate_entrymt+0x16e> 80074f5e: bb 00 00 00 00 mov $0x0,%ebx 80074f63: 89 d8 mov %ebx,%eax 80074f65: 8d 65 f4 lea 0xfffffff4(%ebp),%esp 80074f68: 5b pop %ebx 80074f69: 5e pop %esi 80074f6a: 5f pop %edi 80074f6b: 5d pop %ebp 80074f6c: c3 ret 80074f6d: 83 c0 1c add $0x1c,%eax 80074f70: 89 45 e4 mov %eax,0xffffffe4(%ebp) 80074f73: 0f 85 b3 fe ff ff jne 80074e2c <_ZL14allocate_entrymt+0x37> 80074f79: c6 45 eb 00 movb $0x0,0xffffffeb(%ebp) 80074f7d: c7 45 ec 00 00 00 00 movl $0x0,0xffffffec(%ebp) 80074f84: e9 c1 fe ff ff jmp 80074e4a <_ZL14allocate_entrymt+0x55> 80074f89: 8b 1d f0 56 13 80 mov 0x801356f0,%ebx 80074f8f: 8b 53 0c mov 0xc(%ebx),%edx 80074f92: 3b 53 04 cmp 0x4(%ebx),%edx 80074f95: 0f 85 0a ff ff ff jne 80074ea5 <_ZL14allocate_entrymt+0xb0> 80074f9b: 8b 35 f0 56 13 80 mov 0x801356f0,%esi 80074fa1: 8b 5e 0c mov 0xc(%esi),%ebx 80074fa4: 8b 4d f0 mov 0xfffffff0(%ebp),%ecx 80074fa7: 81 e1 ff 3f 00 00 and $0x3fff,%ecx 80074fad: 8b 03 mov (%ebx),%eax 80074faf: 25 00 c0 ff ff and $0xffffc000,%eax 80074fb4: 09 c8 or %ecx,%eax 80074fb6: 66 89 03 mov %ax,(%ebx) 80074fb9: 8a 55 e2 mov 0xffffffe2(%ebp),%dl 80074fbc: c1 e2 04 shl $0x4,%edx 80074fbf: 8a 43 03 mov 0x3(%ebx),%al 80074fc2: 83 e0 0f and $0xf,%eax 80074fc5: 09 d0 or %edx,%eax 80074fc7: 88 43 03 mov %al,0x3(%ebx) 80074fca: 8b 55 f0 mov 0xfffffff0(%ebp),%edx 80074fcd: c1 e2 02 shl $0x2,%edx 80074fd0: 03 56 0c add 0xc(%esi),%edx 80074fd3: 89 56 0c mov %edx,0xc(%esi) 80074fd6: 81 e1 ff 3f 00 00 and $0x3fff,%ecx 80074fdc: c1 e1 0e shl $0xe,%ecx 80074fdf: 8b 02 mov (%edx),%eax 80074fe1: 25 ff 3f 00 f0 and $0xf0003fff,%eax 80074fe6: 09 c8 or %ecx,%eax 80074fe8: 89 02 mov %eax,(%edx) 80074fea: f6 45 e2 04 testb $0x4,0xffffffe2(%ebp) 80074fee: 0f 84 35 ff ff ff je 80074f29 <_ZL14allocate_entrymt+0x134> 80074ff4: e9 33 ff ff ff jmp 80074f2c <_ZL14allocate_entrymt+0x137> }}} If necessary, I can attach a zipped copy of the relevant kernel_x86 binary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:10:02 2009 From: trac at haiku-os.org (nielx) Date: Thu, 30 Jul 2009 13:10:02 -0000 Subject: [Haiku-bugs] [Haiku] #4132: [Deskbar] shelf width have space only for 3 icons In-Reply-To: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> References: <040.294439492f55944b898b729c0388eeb4@haiku-os.org> Message-ID: <049.9535aba2965b2f9f98490960bcfadadc@haiku-os.org> #4132: [Deskbar] shelf width have space only for 3 icons -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: duplicate | Blockedby: 4133 Platform: All | Blocking: -----------------------------------+---------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:23:58 2009 From: trac at haiku-os.org (arigayas) Date: Thu, 30 Jul 2009 13:23:58 -0000 Subject: [Haiku-bugs] [Haiku] #3380: missing screenmodes when second screen is attached In-Reply-To: <041.01c171ee280ac68eb24c0d24616849bc@haiku-os.org> References: <041.01c171ee280ac68eb24c0d24616849bc@haiku-os.org> Message-ID: <050.607484d94ef73ebdfcdfe05e7150a9fb@haiku-os.org> #3380: missing screenmodes when second screen is attached -------------------------------------+-------------------------------------- Reporter: brecht | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by arigayas): * cc: arigayas@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:40:33 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 13:40:33 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31957 In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.9c5451a78f5bd990979e65d7682d0ab3@haiku-os.org> #4158: Unable to boot with r31957 ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Grr....too early in the morning. Here's the beginning of the function in question: {{{ 80074df5 <_ZL14allocate_entrymt>: 80074df5: 55 push %ebp 80074df6: 89 e5 mov %esp,%ebp 80074df8: 57 push %edi 80074df9: 56 push %esi 80074dfa: 53 push %ebx 80074dfb: 83 ec 1c sub $0x1c,%esp 80074dfe: 89 c3 mov %eax,%ebx 80074e00: 66 89 55 e2 mov %dx,0xffffffe2(%ebp) 80074e04: a1 f0 56 13 80 mov 0x801356f0,%eax }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:42:59 2009 From: trac at haiku-os.org (korli) Date: Thu, 30 Jul 2009 13:42:59 -0000 Subject: [Haiku-bugs] [Haiku] #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures In-Reply-To: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> References: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> Message-ID: <052.626d43c6cafeb857b23925c0d88f13f8@haiku-os.org> #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures ----------------------+----------------------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------+----------------------------------------------------- Comment(by korli): Replying to [comment:1 phoudoin]: > 1. the Marvell Yukon 88E8040 PHY link is correctly handled to send it over network (ticket creation really soon now), or Another option is using a supported usb ethernet key, if there is an available usb slot. I do this myself since my internal e1000 network card doesn't work anymore in Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:44:06 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 13:44:06 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled (was: Unable to boot with r31957) In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.b54e9d866ba2a89368fc705402127a7b@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:44:53 2009 From: trac at haiku-os.org (Blub) Date: Thu, 30 Jul 2009 13:44:53 -0000 Subject: [Haiku-bugs] [Haiku] #4160: printf fails with wide-strings Message-ID: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> #4160: printf fails with wide-strings -------------------------------+-------------------------------------------- Reporter: Blub | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- when printf is calld with %ls it hits the assertion: src/system/libroot/posix/glibc/wcsmbs/wcsrtombs.c:94:__wcsrtombs:data.__outbuf[-1] == '\0' and fails steps to reproduce: make a hello world program using printf("%ls\n", L"Hello World"); -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:46:27 2009 From: trac at haiku-os.org (zooey) Date: Thu, 30 Jul 2009 13:46:27 -0000 Subject: [Haiku-bugs] [Haiku] #4160: printf fails with wide-strings In-Reply-To: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> References: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> Message-ID: <048.47152745fd7704693ba7d714dcab7e33@haiku-os.org> #4160: printf fails with wide-strings -------------------------------+-------------------------------------------- Reporter: Blub | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by zooey): * owner: axeld => zooey * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:50:56 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 13:50:56 -0000 Subject: [Haiku-bugs] [Haiku] #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures In-Reply-To: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> References: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> Message-ID: <052.d20f96e782fcd5807c1d6318a6e1483e@haiku-os.org> #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures ----------------------+----------------------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------+----------------------------------------------------- Comment(by phoudoin): > Another option is using a supported usb ethernet key, > if there is an available usb slot. I do this myself > since my internal e1000 network card doesn't work anymore in Haiku. Unfortunatly, I've managed to bought the D-Link USB ethernet adapter which, bad luck, is not based on Pegasus chip :-\ Instead, I found a 4th solution: save to a bfs usb key, and mount it on my desktop Haiku machine on which network works fine. I should check if the fat KDL is part of R1 alpha blockers. Otherwise, any joe testing alpha will crash it as soon as he'll start to save some stuff on his usb stick - fat formatted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 15:57:15 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 13:57:15 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.8f11cc52e1d21d125a80cb64ca2802b2@haiku-os.org> #3690: Copy file to USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Changes (by phoudoin): * priority: normal => critical * milestone: R1 => R1/alpha1 Comment: Moved to critical for R1 alpha. John Doe will try to save some data on his usb stick. Let's not ruin his Haiku first experiences with losing his data. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:00:29 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 14:00:29 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.d98b0ed5f6a91744d7436466afc0250d@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): The matching eip would help. At least the one in the description doesn't fit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:04:42 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 14:04:42 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to a FAT USB flash drive causes KDL (was: Copy file to USB flash drive causes KDL) In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.a482d8d8612359200946a4ac5ac69972@haiku-os.org> #3690: Copy file to a FAT USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:04:58 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 14:04:58 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to a FAT USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.d640a4f66e3a8bdf0632a1be3587d7b1@haiku-os.org> #3690: Copy file to a FAT USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Description changed by phoudoin: Old description: > Drag and drop a zipfile to my Toshiba 2Gb flash drive and the following > crash message appears: > > PANIC: ASSERT FAILED (src/add-ons/kernel/file_systems/fat/fat.c: 380) > cluster != 0 > > I tired this with the flash drive formatted for both FAT and FAT32 and > got the same results. New description: Drag and drop a zipfile to my Toshiba 2Gb flash drive and the following crash message appears: PANIC: ASSERT FAILED (src/add-ons/kernel/file_systems/fat/fat.c: 380) cluster != 0 I tried this with the flash drive formatted for both FAT and FAT32 and got the same results. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:05:51 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 14:05:51 -0000 Subject: [Haiku-bugs] [Haiku] #3690: KDL when copying data to a FAT USB flash drive (was: Copy file to a FAT USB flash drive causes KDL) In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.d28df15141305e6a7c0b048785fb9c5e@haiku-os.org> #3690: KDL when copying data to a FAT USB flash drive ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:07:34 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 14:07:34 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.089d4025aca49674708c24eada93f0eb@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Sorry, for that particular binary/KDL combo the eip was 0x80074e09. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:14:30 2009 From: trac at haiku-os.org (zooey) Date: Thu, 30 Jul 2009 14:14:30 -0000 Subject: [Haiku-bugs] [Haiku] #4160: printf fails with wide-strings In-Reply-To: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> References: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> Message-ID: <048.5a73f703cd0113f8e0fd97adc09fbaf1@haiku-os.org> #4160: printf fails with wide-strings -------------------------------+-------------------------------------------- Reporter: Blub | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by zooey): I have checked with current gcc2- and gcc4-images and it just works. So which revision have you been testing with? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:29:53 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 14:29:53 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.6a5fb9e91bb99275281fa5b6408586fb@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => assigned Comment: We can reproduce the problem on stippi's machine. Looking into it... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 16:33:08 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 14:33:08 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.82a973f1222132908f1aa1aec00cd4ee@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Cool, please let me know if any other information from my machine would help :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 17:12:50 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 30 Jul 2009 15:12:50 -0000 Subject: [Haiku-bugs] [Haiku] #4158: Unable to boot with r31942+ with kernel tracing enabled In-Reply-To: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> References: <044.0bb859e982bf12f48944d6afde4e6bd0@haiku-os.org> Message-ID: <053.e28b68bd21c103dfe0a8084023e8281a@haiku-os.org> #4158: Unable to boot with r31942+ with kernel tracing enabled ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31973. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 17:33:33 2009 From: trac at haiku-os.org (Blub) Date: Thu, 30 Jul 2009 15:33:33 -0000 Subject: [Haiku-bugs] [Haiku] #4160: printf fails with wide-strings In-Reply-To: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> References: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> Message-ID: <048.9875251d1671ff553d30f4ecfe90ef64@haiku-os.org> #4160: printf fails with wide-strings -------------------------------+-------------------------------------------- Reporter: Blub | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by Blub): didn't realize there have been updates to the building toolchain sorry, can be closed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 17:34:52 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Jul 2009 15:34:52 -0000 Subject: [Haiku-bugs] [Haiku] #4160: printf fails with wide-strings In-Reply-To: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> References: <039.894f221ff36a66d1041a8240204883c5@haiku-os.org> Message-ID: <048.b06d113063eafaf9a8b5e2864486b47b@haiku-os.org> #4160: printf fails with wide-strings --------------------------------+------------------------------------------- Reporter: Blub | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by anevilyak): * status: assigned => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 17:52:21 2009 From: trac at haiku-os.org (umccullough) Date: Thu, 30 Jul 2009 15:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick In-Reply-To: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> References: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> Message-ID: <055.658a4cba350533105f07461e17728000@haiku-os.org> #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick -------------------------+-------------------------------------------------- Reporter: umccullough | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): FWIW, the same stick causes KDLs when i try to use it on an already- running Haiku instance (booted from HD). No time ATM, but I can provide more serial debug info shortly. Is there anything in particular that would help in this case? I have tried this same stick on several different machines and they all seem to experience errors. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 18:24:47 2009 From: trac at haiku-os.org (andreasf) Date: Thu, 30 Jul 2009 16:24:47 -0000 Subject: [Haiku-bugs] [Haiku] #4159: Python regression test test_socket.py fails In-Reply-To: <042.4eb75f6fd0edef570031a71c1dc9f09f@haiku-os.org> References: <042.4eb75f6fd0edef570031a71c1dc9f09f@haiku-os.org> Message-ID: <051.4dac867a65fd8c8bcb2e694358fe0e2b@haiku-os.org> #4159: Python regression test test_socket.py fails --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:02:25 2009 From: trac at haiku-os.org (VinDuv) Date: Thu, 30 Jul 2009 17:02:25 -0000 Subject: [Haiku-bugs] [Haiku] #3690: KDL when copying data to a FAT USB flash drive In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.ca544b02bfd4435799563113359e623c@haiku-os.org> #3690: KDL when copying data to a FAT USB flash drive ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Comment(by VinDuv): This bug seems to have been fixed with the latest fatfs changes. I was able to copy the entire Haiku system/ folder to an USB key without any issues.[[BR]] Can someone confirm this ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:12:55 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Jul 2009 17:12:55 -0000 Subject: [Haiku-bugs] [Haiku] #3383: [enhancement] Workspaces : user definable orientation In-Reply-To: <041.64820673ec7275f54f4186fe250f9020@haiku-os.org> References: <041.64820673ec7275f54f4186fe250f9020@haiku-os.org> Message-ID: <050.7fa4aef3c8ce14f852b2121c00ec7966@haiku-os.org> #3383: [enhancement] Workspaces : user definable orientation --------------------------------------+------------------------------------- Reporter: mmadia | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: There can only be a single orientation system wide, but this one can now be changed via the "Screen" preferences application. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:14:49 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Jul 2009 17:14:49 -0000 Subject: [Haiku-bugs] [Haiku] #3690: KDL when copying data to a FAT USB flash drive In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.6791afb373a50bc28f35340ca1bdc9b6@haiku-os.org> #3690: KDL when copying data to a FAT USB flash drive ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Comment(by axeld): The bug disappeared for me to, but I don't know what is responsible for this; my FAT changes aren't to blame for this AFAICT. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:18:13 2009 From: trac at haiku-os.org (emitrax) Date: Thu, 30 Jul 2009 17:18:13 -0000 Subject: [Haiku-bugs] [Haiku] #4093: Stack and Tile group is not all grouped to same layer In-Reply-To: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> References: <042.418d5e6141115b1ffd91eda132213116@haiku-os.org> Message-ID: <051.e9b73e740802f3087a4814f5433137ba@haiku-os.org> #4093: Stack and Tile group is not all grouped to same layer --------------------------------+------------------------------------------- Reporter: scottmc | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by emitrax): Replying to [comment:2 axeld]: > I'm not sure it's a good idea to put error reports to externally maintained patches here; I'm inclined to close this as invalid. Other opinions? I agree with you. But I'm also wondering why this feature hasn't been added to Haiku yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:38:58 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 30 Jul 2009 17:38:58 -0000 Subject: [Haiku-bugs] [Haiku] #4144: BScreen::SetMode() not working OK In-Reply-To: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> References: <042.871a60fa4e1ac2ec70e94636475d53a9@haiku-os.org> Message-ID: <051.ebb2fc6a889c724efb90b122b27af840@haiku-os.org> #4144: BScreen::SetMode() not working OK -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Ok, ok. You've convinced me. I'll give it a try, test it, and commit it. Next week. After all, if my style isn't very nice (or something), you can always correct me.. :) Thanks again! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:47:18 2009 From: trac at haiku-os.org (czeidler) Date: Thu, 30 Jul 2009 17:47:18 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown In-Reply-To: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> References: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> Message-ID: <052.379df57c435bb0683d9fd50f4dc24474@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by czeidler): Thank I think I missed a lock... I don't see it on my machine anymore. Same on yours? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 19:55:42 2009 From: trac at haiku-os.org (czeidler) Date: Thu, 30 Jul 2009 17:55:42 -0000 Subject: [Haiku-bugs] [Haiku] #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures In-Reply-To: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> References: <043.35751723ced9a59a72db4f0fbb868fc5@haiku-os.org> Message-ID: <052.4a25e5f836e05dd61f5a6cb102303c14@haiku-os.org> #4152: acpi_battery: throw ACPI exceptions about GlobalLock acquisition/release failures ----------------------+----------------------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------+----------------------------------------------------- Comment(by czeidler): Sadly I have no acpi global lock on my notbook and don't see this message. Maybe you can look into it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 20:29:24 2009 From: trac at haiku-os.org (czeidler) Date: Thu, 30 Jul 2009 18:29:24 -0000 Subject: [Haiku-bugs] [Haiku] #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown In-Reply-To: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> References: <043.567db1a8a6823c4300b87cae60381691@haiku-os.org> Message-ID: <052.2d0c198a56c582f3f28f074058d49c42@haiku-os.org> #4151: Deskbar crash at shutdown/restart in PowerStatus replicant when Battery Info window is shown ----------------------------------+----------------------------------------- Reporter: phoudoin | Owner: czeidler Type: bug | Status: new Priority: high | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by czeidler): Ok I think its still there, looking into it... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 22:05:05 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 30 Jul 2009 20:05:05 -0000 Subject: [Haiku-bugs] [Haiku] #4067: Kinesis USB Keyboard is removed after first key is pressed. In-Reply-To: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> References: <041.8a8baaefb5f7eed5900c23f7d3d0e64d@haiku-os.org> Message-ID: <050.eeebc0f0ed3ddbb4b228ce5819739329@haiku-os.org> #4067: Kinesis USB Keyboard is removed after first key is pressed. -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmadia): Attached a syslog from r31990-x86gcc2. Still persistant. syslog snippet {{{ KERN: usb hub 7: port 3: new device connected KERN: usb ehci 1: KERN: fullspeed device connected, giving up port ownership KERN: usb hub 2: port 3: new device connected KERN: usb hub 19: port 1: new device connected KERN: usb hub 7: port 3: device removed KERN: usb_hid: no handlers for hid device KERN: void AddOnManager::MessageReceived(BMessage *) what: NMP_ Last message repeated 1 time KERN: usb error ohci 0: td error: 0x00000003 KERN: usb_hid: error waiting for report: Device check-sum error KERN: usb hub 2: port 3: device removed KERN: usb hub 2: KERN: port 3 disabled KERN: void AddOnManager::MessageReceived(BMessage *) what: NMP_ KERN: register_domain(9, unix) KERN: heap_add_area: area 4746 added to large heap 0x81c57ccc - usable range 0x88001000 - 0x88400000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jul 30 22:49:13 2009 From: trac at haiku-os.org (kallisti5) Date: Thu, 30 Jul 2009 20:49:13 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.aebfad1bd1af7cce3442fb67d8314d92@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): {{{ alex at linux:~/develop/haiku/generated/objects/haiku/ppc/release/system/kernel$ readelf -s kernel_ppc | grep "UND" 0: 00000000 0 NOTYPE LOCAL DEFAULT UND 211: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_and64PVx 1589: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_get64PVx 2252: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z17_user_atomic_or64PVxx 2543: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z27_user_atomic_test_and 2786: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_add64PVx 3634: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_set64PVx 0: 00000000 0 NOTYPE LOCAL DEFAULT UND 2042: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_and64PVx 3420: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_get64PVx 4083: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z17_user_atomic_or64PVxx 4374: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z27_user_atomic_test_and 4617: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_add64PVx 5465: 00000000 0 NOTYPE GLOBAL DEFAULT UND _Z18_user_atomic_set64PVx }}} I think these are coming from src/system/kernel/arch/ppc/arch_atomic.c arch_atomic defines int64's on 32-bit platforms. Looking into commenting them out for now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 00:17:13 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 22:17:13 -0000 Subject: [Haiku-bugs] [Haiku] #3690: KDL when copying data to a FAT USB flash drive In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.9387cf75b4cd8ce186c8f3bf7d57ee92@haiku-os.org> #3690: KDL when copying data to a FAT USB flash drive ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Comment(by phoudoin): Last time I see it I was running a r31835 installed by Installer from a (r31835, obsiouvly) LiveUSB image donwloaded from haiku-files.org. I'll tried with a more recent revision ASAP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 00:24:53 2009 From: trac at haiku-os.org (phoudoin) Date: Thu, 30 Jul 2009 22:24:53 -0000 Subject: [Haiku-bugs] [Haiku] #3690: KDL when copying data to a FAT USB flash drive In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.62c3d99670557d833d42c29dbf746553@haiku-os.org> #3690: KDL when copying data to a FAT USB flash drive ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: 4066 | ------------------------------+--------------------------------------------- Comment(by phoudoin): How ironic if I've just installed exactly the previous revision before this bug were fixed... I'm still at work but I can't hardly wait to check! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 00:42:23 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Thu, 30 Jul 2009 22:42:23 -0000 Subject: [Haiku-bugs] [Haiku] #4161: Haiku CD can't find harddisk Message-ID: <048.d170d9999535b9651dbb082091858bcb@haiku-os.org> #4161: Haiku CD can't find harddisk ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Installer and DriveSetup can't find any partitions or devices apart from the single ATAPI device it booted from - on hardware BeOS and Haiku have been working for years, intel 845 chipset, with a 40GB ide disk 2-4 years old. I don't think there's anything wrong with the CD, which I built, but who knows. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 00:46:58 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Thu, 30 Jul 2009 22:46:58 -0000 Subject: [Haiku-bugs] [Haiku] #4161: Haiku CD can't find harddisk In-Reply-To: <048.d170d9999535b9651dbb082091858bcb@haiku-os.org> References: <048.d170d9999535b9651dbb082091858bcb@haiku-os.org> Message-ID: <057.df4a458cc44dba87abd7a1f835c4a077@haiku-os.org> #4161: Haiku CD can't find harddisk ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Description changed by jonas.kirilla: Old description: > Installer and DriveSetup can't find any partitions or devices apart from > the single ATAPI device it booted from - on hardware BeOS and Haiku have > been working for years, intel 845 chipset, with a 40GB ide disk 2-4 years > old. > > I don't think there's anything wrong with the CD, which I built, but who > knows. New description: Installer and DriveSetup can't find any partitions or devices apart from the single ATAPI device it booted from - on hardware BeOS and Haiku have been working for years, intel 845 chipset, with a 40GB ide disk 2-4 years old. I don't think there's anything wrong with the CD, which I built, but who knows. Haiku r31990. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 01:13:19 2009 From: trac at haiku-os.org (kallisti5) Date: Thu, 30 Jul 2009 23:13:19 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.0d024b5182707cb942ee4c57fcbdde98@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): Ingo pointed out that this was due to a missing extern "C" statement in headers/private/kernel/user_atomic.h This fixes the undefined user_atomic errors! The *final* attached contains lots of good PPC fixes and gets rid of all of the relocation errors. We still get choked when jumping to the kernel but at least we get the kernel in memory properly now. After checking in the attached ppc-isync-relocation-final.diff patch this TRAC should be resolved. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 02:41:19 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 00:41:19 -0000 Subject: [Haiku-bugs] [Haiku] #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them In-Reply-To: <041.4ef5ee2335b484b94285bb5550d470ce@haiku-os.org> References: <041.4ef5ee2335b484b94285bb5550d470ce@haiku-os.org> Message-ID: <050.be954e5da7334047d2baf6ba953d03ff@haiku-os.org> #4141: Incorrect error returned when creating symlinks on a filesystem that does not support them ----------------------------+----------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: File Systems => System/Kernel Comment: Fixed in r32004. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 08:39:09 2009 From: trac at haiku-os.org (arigayas) Date: Fri, 31 Jul 2009 06:39:09 -0000 Subject: [Haiku-bugs] [Haiku] #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick In-Reply-To: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> References: <046.c37ee06c26af59fcc5e89885d936b114@haiku-os.org> Message-ID: <055.4b82c58bc629bd8369531ad3a3e973ea@haiku-os.org> #4135: KDL booting from USB Kingston DataTraveler G2 4gb stick -------------------------+-------------------------------------------------- Reporter: umccullough | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by arigayas): * cc: arigayas@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 08:43:00 2009 From: trac at haiku-os.org (arigayas) Date: Fri, 31 Jul 2009 06:43:00 -0000 Subject: [Haiku-bugs] [Haiku] #3501: DPMS only turns off one monitor in a dualhead setup. In-Reply-To: <040.034b9d96edaeb5b762d366526d4f6340@haiku-os.org> References: <040.034b9d96edaeb5b762d366526d4f6340@haiku-os.org> Message-ID: <049.ac035b7b38847524b820d91324f4cb41@haiku-os.org> #3501: DPMS only turns off one monitor in a dualhead setup. -------------------------------------+-------------------------------------- Reporter: adamk | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by arigayas): * cc: arigayas@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 10:26:08 2009 From: trac at haiku-os.org (mmu_man) Date: Fri, 31 Jul 2009 08:26:08 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.31bd24a09df28771d4b94613fd3b3708@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by mmu_man): Do we still need this #ifdef on _BOOT_MODE now ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 11:18:02 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 09:18:02 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox Message-ID: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I just did a binary search to find out why haiku turns off even before 1st icon.[[BR]]So r32000 boots fine and r32001 is to blame. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 12:45:04 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 10:45:04 -0000 Subject: [Haiku-bugs] [Haiku] #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window In-Reply-To: <040.c884610af89068fa558501c97f7d319e@haiku-os.org> References: <040.c884610af89068fa558501c97f7d319e@haiku-os.org> Message-ID: <049.1d810d5eb91f53f049ab4958e6a64e6a@haiku-os.org> #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Ctrl-Alt-H hides the application, not the window; Ctrl-Alt-M minimizes a single window. Anyway, the problem should be fixed in r31012, although I'm not sure about the consequences yet (couldn't find anything harmful yet). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 14:01:49 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 12:01:49 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.d814a4cf58bd8e98e8f0c28e4c9f7533@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Works fine over here; it must be something at your end that's broken. Furthermore, r32001 does not have any influence on the early boot procedure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 14:03:33 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 12:03:33 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.c1a34f3554d9665166efe94a0aa4a8b2@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): This is with VirtualBox 3.0.2, and a GCC2 r31012, btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 14:15:35 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 12:15:35 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.9185f8dd5de32603401b9c639ada3b74@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): VirtualBox 2.1.4 and a GCC2 over here. Maybe I should try to rm -rf generated folder? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 14:30:54 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 31 Jul 2009 12:30:54 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.abfa371164665a95cc44ce0bab4f1123@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): I vote to leave it in. What happens is on the first missing relocation we return an error instantly throwing us back to the bootloader and causing the end user to not see the error message. With the _BOOT_MODE def in there we will try and push on if it is the kernel booting showing all the relocation errors and then freeze up when trying to jump into the kernel. Missing relocation errors still may occur in the future and this is a handy way to fish them out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 14:38:41 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 31 Jul 2009 12:38:41 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.a02d148c9c38698df352f9adf8a0ebda@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): also a quick note on those sync commands, they always have to be called prior to and sometimes after those context changes. Since you always have to do it we might as well avoid bugs and do them in the assembly vs the c. If we call isync/sync multiple times on accident somewhere no harm will come of it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 15:13:11 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 13:13:11 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.90ea36546606cbd8b4431a221c486856@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by diver): * status: closed => reopened * resolution: invalid => Comment: I've rm'ed generated, rebuilt gcc and then rebuilt entire tree.[[BR]] Haiku still turns off in VirtualBox 2.1.4[[BR]] But the same image works in VirtualBox 3.0.2[[BR]] So r32001 indeed blocks VirtualBox 2.1.4, but I would like to still use this old version as anything more recent than 2.1.4 lags badly when moving windows in Haiku and major performance issues.[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 15:14:44 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 13:14:44 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.53edce1469ff1fd4f0935e7ea005c282@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): accidentally reopened it -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 15:15:41 2009 From: trac at haiku-os.org (mmu_man) Date: Fri, 31 Jul 2009 13:15:41 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.2ddd2b734a0a9b5d74b796ca9df13f63@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by mmu_man): Well it should panic when getting an error from relocate_foo(). Skipping errors and hoping for the kernel to crash (which might not be obviously right at boot, depending on which sym is missing), is not really clean. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 15:24:38 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 13:24:38 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.7bcdd6d9e1184308e3c2210b6f9b8423@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): Added serial output -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 15:45:27 2009 From: trac at haiku-os.org (kallisti5) Date: Fri, 31 Jul 2009 13:45:27 -0000 Subject: [Haiku-bugs] [Haiku] #4115: Failed to relocate error when attempting to boot PPC kernel. In-Reply-To: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> References: <044.55ee1d8c568130db70328cf0913ca02d@haiku-os.org> Message-ID: <053.7a0d549e4624681c9d3639ebd2de63dd@haiku-os.org> #4115: Failed to relocate error when attempting to boot PPC kernel. ---------------------------+------------------------------------------------ Reporter: kallisti5 | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: PowerPC Blocking: | ---------------------------+------------------------------------------------ Comment(by kallisti5): Good point. A panic would be ideal.. or maybe set some kind of $panic = true thing while relocating then after everything is relocated trigger the panic if something wasn't right? For now feel free to remove the _BOOT_MODE bit as its not required and not the most important part of this fix. Thanks! -- Alex -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 16:19:04 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 14:19:04 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.f8fbed46503ca558a96f7af3770913ce@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): This could be a bug in Haiku indeed, but it would only be indirectly be related to r32001 (ie. image sizes, ...). I'm leaving it open for now, maybe someone some day wants to look into it :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 16:30:18 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 14:30:18 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.fbf48c819ef4cd373c77f081843efc08@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): That's too bad, all of my 3 PC are running VirtualBox 2.1.4 for testing haiku, so this is a showstopper for me :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 16:30:54 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 14:30:54 -0000 Subject: [Haiku-bugs] [Haiku] #4138: [Tracker] some text doesn't fit in fnd panel In-Reply-To: <040.04b3a4b3b52edf761ac46c08a501f877@haiku-os.org> References: <040.04b3a4b3b52edf761ac46c08a501f877@haiku-os.org> Message-ID: <049.2d062f111e6f321b37fe176460d525b1@haiku-os.org> #4138: [Tracker] some text doesn't fit in fnd panel -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r32022. The panel isn't font sensitive yet, though, and needs a serious redesign, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 16:34:48 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 14:34:48 -0000 Subject: [Haiku-bugs] [Haiku] #4091: r31522 build breakage on parallel jam In-Reply-To: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> References: <044.f0866d323ab08238a53c61e3b5884504@haiku-os.org> Message-ID: <053.26e8c81a3ebc6ad587c3cbc4d1eb4181@haiku-os.org> #4091: r31522 build breakage on parallel jam --------------------------+------------------------------------------------- Reporter: meianoite | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by axeld): * milestone: R1/alpha1 => Unscheduled Comment: I don't see why this should be an alpha blocker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:17:26 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 15:17:26 -0000 Subject: [Haiku-bugs] [Haiku] #2754: DiskProbe on the main disk brings system to a halt In-Reply-To: <040.ae0328adf41ae2e733b7658e4bec734b@haiku-os.org> References: <040.ae0328adf41ae2e733b7658e4bec734b@haiku-os.org> Message-ID: <049.15af9e2134f8ef5c3ab840cb875b8a45@haiku-os.org> #2754: DiskProbe on the main disk brings system to a halt ----------------------------+----------------------------------------------- Reporter: axeld | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Not reproducible anymore, must have been fixed or worked-around in the mean time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:19:29 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 15:19:29 -0000 Subject: [Haiku-bugs] [Haiku] #2273: [runtime_loader] double clicking it leads to problems In-Reply-To: <040.0751f733a1ff9f8944c298bce34adefe@haiku-os.org> References: <040.0751f733a1ff9f8944c298bce34adefe@haiku-os.org> Message-ID: <049.d31e39bc80c37f8fb578730903d916b2@haiku-os.org> #2273: [runtime_loader] double clicking it leads to problems ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Not reproducible anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:22:45 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 15:22:45 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.cb19e57a4d71a73df790bdfc988d9fb2@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): I've tested the following versions {{{ VirtualBox-2.0.0_36011_fedora8-1.i386.rpm VirtualBox-2.0.2_36488_fedora8-1.i386.rpm VirtualBox-2.0.4_38406_fedora8-1.i386.rpm VirtualBox-2.0.6_39765_fedora8-1.i386.rpm VirtualBox-2.0.8_44071_fedora8-1.i386.rpm VirtualBox-2.1.0_41146_fedora7-1.i386.rpm VirtualBox-2.1.2_41885_fedora8-1.i386.rpm VirtualBox-2.1.4_42893_fedora8-1.i386.rpm VirtualBox-2.2.0_45846_fedora8-1.i386.rpm VirtualBox-2.2.2_46594_fedora8-1.i386.rpm VirtualBox-2.2.4_47978_fedora8-1.i386.rpm VirtualBox-3.0.0_49315_fedora8-1.i386.rpm VirtualBox-3.0.2_49928_fedora8-1.i386.rpm }}} And the only version that don't crash is 3.0.2. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:23:34 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 15:23:34 -0000 Subject: [Haiku-bugs] [Haiku] #156: syslog is corrupted In-Reply-To: <050.87a7f007f82c5221df346c4250f3f137@haiku-os.org> References: <050.87a7f007f82c5221df346c4250f3f137@haiku-os.org> Message-ID: <059.89f190a15a62a7b6285b85692be05f9f@haiku-os.org> #156: syslog is corrupted ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 2732 ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * version: => R1 development * resolution: => fixed Comment: I guess this one can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:25:38 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 15:25:38 -0000 Subject: [Haiku-bugs] [Haiku] #1072: Write an HDA audio driver and add-on In-Reply-To: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> References: <040.a10117f1ecafcc52de483402ae8e415f@haiku-os.org> Message-ID: <049.de31f2654b84fb8d36995d6a1c4aa2ac@haiku-os.org> #1072: Write an HDA audio driver and add-on --------------------------------+------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3193 --------------------------------+------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: In any case, we do have a HD audio driver since quite some time, so I'm closing this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 17:34:38 2009 From: trac at haiku-os.org (axeld) Date: Fri, 31 Jul 2009 15:34:38 -0000 Subject: [Haiku-bugs] [Haiku] #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window In-Reply-To: <040.c884610af89068fa558501c97f7d319e@haiku-os.org> References: <040.c884610af89068fa558501c97f7d319e@haiku-os.org> Message-ID: <049.c40420ea53207fb72a2bfd6cc008174c@haiku-os.org> #4127: [Deskbar] shows "Tracker Status" if you hide tracker's window -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: closed => reopened * resolution: fixed => Comment: This caused indeed a problem with how CL-Amp opens its windows (they are minimized first, and shown afterwards). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 18:47:35 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 16:47:35 -0000 Subject: [Haiku-bugs] [Haiku] #4162: [kernel] r32001 broke booting in virtualbox In-Reply-To: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> References: <040.12db3b6a37b2a044f06bb5e639355d41@haiku-os.org> Message-ID: <049.637e1dbb7613e1d8351ec5f81c021ff8@haiku-os.org> #4162: [kernel] r32001 broke booting in virtualbox ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): It looks like I could workaround speed issue with this {{{ VBoxManage setextradata global "GUI/RenderMode" sdl }}} See http://www.virtualbox.de/ticket/3900 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 19:13:29 2009 From: trac at haiku-os.org (tokyo6pm) Date: Fri, 31 Jul 2009 17:13:29 -0000 Subject: [Haiku-bugs] [Haiku] #4163: Radeon Xpress 200M does not work correctly Message-ID: <043.18086e08665b9bd748a2eadc5e80648d@haiku-os.org> #4163: Radeon Xpress 200M does not work correctly -------------------------------------+-------------------------------------- Reporter: tokyo6pm | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- I have laptop (MSI S420) with Radeon Xpress 200M. When i boot Haiku with radeon driver, i get strange image on my screen. Vesa driver works fine, but does not support native resolution (1280x768). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 21:29:31 2009 From: trac at haiku-os.org (Blub) Date: Fri, 31 Jul 2009 19:29:31 -0000 Subject: [Haiku-bugs] [Haiku] #4164: assertion fails in malloc (rev 31961) Message-ID: <039.bc3c3935e6baa0ee32c0d5fb7ae70981@haiku-os.org> #4164: assertion fails in malloc (rev 31961) -------------------------------+-------------------------------------------- Reporter: Blub | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- I just hit an assertion in malloc() :( Adding a screenshot with some info printed in gdb, and the assertion (where you can see the file+line) Unfortunately I cannot provide a small testcase, I'll try reproducing it with simple code, but I doubt I'll have much luck -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 21:52:21 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Fri, 31 Jul 2009 19:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #4165: Support-aiding Haiku runtime data request application and web integration Message-ID: <048.afbc9be0441b90a3d1fbb032a648552c@haiku-os.org> #4165: Support-aiding Haiku runtime data request application and web integration ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: haiku-web Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Learning to provide the right info in bug reports (or to ask for it) isn't difficult, but it's likely to take a few exchanges per new user. So here's an idea to improve bug reporting and user-to-user support (on IRC or web forums). I suggest creating a Haiku application to allow person A, needing information on person B's Haiku installation, to select the desired information sources (e.g. syslog, listdev, ..) by ticking a set of checkboxes, and have a file (or link to a file) created, which could be shared with person B. Person B would receive the file, "run" it, have some output and be able to upload, email it or take it to another Haiku box, say with a working net connection. This hinges on the ease of creating and sharing such a file, and on the ease of getting it, using it and returning the requested info. Ideally the creation of the request-files would be possible also directly in Trac. (Developer would press button "Request runtime info", tick relevant checkboxes, and have the file created and linked in the same bug report.) The request-file could contain an email address or Trac report number, to offer the user to email the data or upload it to the bug tracker. The application and its request files could also be used pro-actively by experienced bug reporters to volonteer the right information, up front. The request file could be as simple as a bash script, but web-delivered bash scripts don't run by simply opening them, and from a security point of view passing bash scripts over the internet begs to be abused. Instead I suggest a more limited file format. Text based for easy inspection. With its own MIME type and a dedicated filename extension, e.g. .haikusupport. While webservers do supply a MIME type, the extension is more reliable, and will make Haiku recognize the file's type immediately, which is important here. The output would preferrably be a single file when saved and transferred manually. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 22:20:48 2009 From: trac at haiku-os.org (pulkomandy) Date: Fri, 31 Jul 2009 20:20:48 -0000 Subject: [Haiku-bugs] [Haiku] #4165: Support-aiding Haiku runtime data request application and web integration In-Reply-To: <048.afbc9be0441b90a3d1fbb032a648552c@haiku-os.org> References: <048.afbc9be0441b90a3d1fbb032a648552c@haiku-os.org> Message-ID: <057.a9e2411a1245fe99d1d4665138c4d371@haiku-os.org> #4165: Support-aiding Haiku runtime data request application and web integration ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: haiku-web Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Website/Trac | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by pulkomandy): Debian has a tool called reportbug that allow you to fill in all the needed info for a good bug report then send it to their bugtracker by mail. It may be interesting to have a look at it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 22:44:46 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 20:44:46 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.37f73ba3363f8e594702263e9ed06cf3@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): I can reproduce it in r32034.[[BR]] For this I have to ssh to ubuntu and run midnight commander[[BR]] I have to resize terminal several times (20 times or more) to crash it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 22:47:34 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 20:47:34 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.e7f1e03ba9c743decbc0cc850727a888@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): ProcessController still show that ssh connection, is it on purpose, or I should open another bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 22:49:19 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 20:49:19 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.594a052433fe105e60b3e747e29793d5@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): running cat /dev/random will crash it much faster -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 22:52:56 2009 From: trac at haiku-os.org (diver) Date: Fri, 31 Jul 2009 20:52:56 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.a6865b526a9c919f76d76781726378c4@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): Added another backtrace, one more bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 23:20:32 2009 From: trac at haiku-os.org (bga) Date: Fri, 31 Jul 2009 21:20:32 -0000 Subject: [Haiku-bugs] [Haiku] #4166: Recent changes to video modes seem to have removed some modes. Message-ID: <038.9f0de4d21d34649b3e8bc6e994c2757e@haiku-os.org> #4166: Recent changes to video modes seem to have removed some modes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- My desktop computer is connected to a Samsung Syncmaster 22" monitor with a native resolution of 1680x1050. As I am using the VESA driver ad my video card BIOS does not seem to export widescreen modes, I was using 1440x1050 as my resolution. I just updated haiku to r32034 and, now, I can only set 1280x1024 as the maximum resolution. Interesting enough, going to the boot menu and selecting a video mode to use does show 1440x1050 but selecting it has no effect (it ends up in 1280x1024 after boot). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 23:23:37 2009 From: trac at haiku-os.org (Blub) Date: Fri, 31 Jul 2009 21:23:37 -0000 Subject: [Haiku-bugs] [Haiku] #4164: assertion fails in malloc (rev 31961) In-Reply-To: <039.bc3c3935e6baa0ee32c0d5fb7ae70981@haiku-os.org> References: <039.bc3c3935e6baa0ee32c0d5fb7ae70981@haiku-os.org> Message-ID: <048.55df70b4606ceba7d1bdde12bf89c920@haiku-os.org> #4164: assertion fails in malloc (rev 31961) -------------------------------+-------------------------------------------- Reporter: Blub | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by Blub): seems like it was a double-free corruption, but I cannot really confirm that since I couldn't find the place where it actually happened. I have a testcase where I was able to successfully double-free some data without any errors or assertion faults coming up, so I guess the errors occur some time too late. After changing the data-layout of the program it didn't crash anymore (actually it is now optimized better since it doesn't fragment the memory as much) I guess I'm just too used to glibc's huge and frightening "double free corruption" error message. However, when I double-freed on purpose in my testcase (sometimes it did actually cause a crash) then it has always been a different assertion. (and it's always been the same different assertions) Maybe if I have time to read through the malloc code I can add a check for double-free corruptions (if until then it's not already made). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 23:27:06 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Fri, 31 Jul 2009 21:27:06 -0000 Subject: [Haiku-bugs] [Haiku] #4166: Recent changes to video modes seem to have removed some modes. In-Reply-To: <038.9f0de4d21d34649b3e8bc6e994c2757e@haiku-os.org> References: <038.9f0de4d21d34649b3e8bc6e994c2757e@haiku-os.org> Message-ID: <047.8be969e79c1035fda16d41793b9ffc0b@haiku-os.org> #4166: Recent changes to video modes seem to have removed some modes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by jonas.kirilla): * cc: jonas@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jul 31 23:40:00 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Fri, 31 Jul 2009 21:40:00 -0000 Subject: [Haiku-bugs] [Haiku] #4166: Recent changes to video modes seem to have removed some modes. In-Reply-To: <038.9f0de4d21d34649b3e8bc6e994c2757e@haiku-os.org> References: <038.9f0de4d21d34649b3e8bc6e994c2757e@haiku-os.org> Message-ID: <047.e7997cd4bec9210fb68146ed3696532b@haiku-os.org> #4166: Recent changes to video modes seem to have removed some modes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by jonas.kirilla): I'm in a similar situation, except that my graphics were native before but are now vesa. I have a widescreen monitor capable of 1920x1200 (16:10) with a supported ATI card (which likewise does not export any widescreen modes) which can drive the monitor at full resolution in Linux but does not in Haiku. (Never worked.) Instead Haiku falls back to vesa in recent revisions. (No refresh rate option in Screen. Vesa accelerant in use. Max resolution 1600x1200 IIRC.) And thus loosing a few resolution options, in Screen. -- Ticket URL: Haiku The Haiku operating system.