From trac at haiku-os.org Mon Jun 1 00:43:06 2009 From: trac at haiku-os.org (diver) Date: Sun, 31 May 2009 22:43:06 -0000 Subject: [Haiku-bugs] [Haiku] #3399: The system reboots while running jam -q on the haiku trunk. In-Reply-To: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> References: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> Message-ID: <051.63e451ca7d98190eb9150fe86bc9ada2@haiku-os.org> #3399: The system reboots while running jam -q on the haiku trunk. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by diver): * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 01:44:56 2009 From: trac at haiku-os.org (augiedoggie) Date: Sun, 31 May 2009 23:44:56 -0000 Subject: [Haiku-bugs] [Haiku] #3986: problem with ls command (symlink traversal bug?) In-Reply-To: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> References: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> Message-ID: <055.31ee965fb1bc7843d11817e9520a6fa5@haiku-os.org> #3986: problem with ls command (symlink traversal bug?) -------------------------+-------------------------------------------------- Reporter: augiedoggie | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by augiedoggie): This also happens with other commands. Examples: {{{ ~> listattr /boot/develop/tools/gnupro/COPYING listattr: initialization failed for "/boot/develop/tools/gnupro/COPYING": Not a directory ~> listres /boot/develop/tools/gnupro/COPYING listres: opening resources failed for "/boot/develop/tools/gnupro/COPYING": I/O error ~> rm /boot/develop/tools/gnupro/COPYING rm: cannot remove '/boot/develop/tools/gnupro/COPYING': Not a directory ~> }}} This was tested with real hardware at r30935 and with an alpha image from haiku-files at r30933 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 02:29:15 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 01 Jun 2009 00:29:15 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 In-Reply-To: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> References: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> Message-ID: <049.4d3e8a73ed27a27307dd8115d5bdf857@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by haiqu): Fixed. Changed the following in fpc/rtl/haiku/ostypes: {{{ (* This is the BeOS stat struct and Haiku version differs as at r30830 stat = packed record dev:longint; {"device" that this file resides on} ino:int64; {this file's inode #, unique per device} st_mode:dword; {mode bits (rwx for user, group, etc)} nlink:longint; {number of hard links to this file} uid:dword; {user id of the owner of this file} gid:dword; {group id of the owner of this file} st_size:int64; {size of this file (in bytes)} rdev:longint; {device type (not used)} blksize:longint; {preferref block size for i/o} atime:longint; {last access time} st_mtime:longint; {last modification time} ctime:longint; {last change time, not creation time} crtime:longint; {creation time} end; *) stat = packed record st_dev:longint; {"device" that this file resides on} st_ino:int64; {this file's inode #, unique per device} st_mode:dword; {mode bits (rwx for user, group, etc)} st_nlink:longint; {number of hard links to this file} st_uid:dword; {user id of the owner of this file} st_gid:dword; {group id of the owner of this file} st_size:int64; {size of this file (in bytes)} st_rdev:longint; {device type (not used)} st_blksize:longint; {preferref block size for i/o} st_atime:timespec; {last access time} st_mtime:timespec; {last modification time} st_ctime:timespec; {last change time, not creation time} st_crtime:timespec; {creation time} st_type:dword; {attribute/index type} st_blocks:int64; {number of blocks allocated for object} end; TStat = stat; pStat = ^stat; }}} Also needed to do a few patches in rtl/unix/sysutils.pp and rtl/unix/dos.pp like so: {{{ {$ifdef haiku} Result:=UnixToWinAge(info.st_mtime.tv_sec); {$else} Result:=UnixToWinAge(info.st_mtime); {$endif} }}} It's all good now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 12:46:35 2009 From: trac at haiku-os.org (idefix) Date: Mon, 01 Jun 2009 10:46:35 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.b9901f647f69ccb70ff148060394d597@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | 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:4 haiqu]: > OK, that needs clarifying. If I go into DriveSetup and try to initialize that partition, the option is greyed out. I had no such problem with Partition 3 but, if you look at the first snapshot you can see that it's still narked in the partition table as type 06 (fat16, dos 3.31) [...] I think this is the cause of the problem:[[BR]] Apparently Installer only looks at the partition table and sees a fat16 partition, which has a maximum size of 2 GB.[[BR]] Tracker, on the other hand looks at the information inside this partition and sees a fat32 formatted one, which can be larger than 2 GB. So it reports the correct partition size. I suspect that changing the type of this partition in the partition table to fat32 would solve your problems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 12:49:29 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 01 Jun 2009 10:49:29 -0000 Subject: [Haiku-bugs] [Haiku] #3986: problem with ls command (symlink traversal bug?) In-Reply-To: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> References: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> Message-ID: <055.c353736f92d94169df8b799d5d8786ba@haiku-os.org> #3986: problem with ls command (symlink traversal bug?) -------------------------+-------------------------------------------------- Reporter: augiedoggie | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 12:57:56 2009 From: trac at haiku-os.org (diver) Date: Mon, 01 Jun 2009 10:57:56 -0000 Subject: [Haiku-bugs] [Haiku] #3987: [Tracker] crash in BView::_CheckLock Message-ID: <040.b6de57f28ef42500fd22442a1da1e7eb@haiku-os.org> #3987: [Tracker] crash in BView::_CheckLock ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I observed a crash when I tried to "Get info" of Haiku volume on desktop.[[BR]] I noticed that there is a delay in 2 seconds now before Info windows is shown.[[BR]] Tested with r30934 in vbox 2.0.2. Could be related to r30894. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 13:12:34 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 01 Jun 2009 11:12:34 -0000 Subject: [Haiku-bugs] [Haiku] #3986: problem with ls command (symlink traversal bug?) In-Reply-To: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> References: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> Message-ID: <055.fc1d739c8a458510a88e3306a2051d11@haiku-os.org> #3986: problem with ls command (symlink traversal bug?) --------------------------+------------------------------------------------- Reporter: augiedoggie | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30937. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 13:15:36 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 01 Jun 2009 11:15:36 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 In-Reply-To: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> References: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> Message-ID: <049.3915b7be6a2b4924d9010ceadad767f2@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 13:36:57 2009 From: trac at haiku-os.org (andreasf) Date: Mon, 01 Jun 2009 11:36:57 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.000aa56786a468686a05aae4d2db58eb@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by andreasf): * status: closed => reopened * resolution: fixed => Comment: Unfortunately this fix broke the original `git svn info` code path by not extracting the correct piece of information like from `svn info`. Patch coming up shortly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 15:08:04 2009 From: trac at haiku-os.org (andreasf) Date: Mon, 01 Jun 2009 13:08:04 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.ced5abd39a108f9023288be5bbbfedad@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by andreasf): When git-svn was in fact usable, the whole `svn info`-like output was stored in {{{$revision}}}. The final {{{if}}} doesn't check for a sane numeric value, and no revision information was displayed in AboutSystem. The attached patch reunifies svn and git-svn to share the postprocessing (`grep`, `awk`). If both fail, {{{$revision}}} should be empty, triggering Ingo's {{{if}}} and my pure git fallback. Failing that as well, {{{$revision}}} should be empty once again and thus set to {{{0}}}, still fixing #2860. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 15:24:10 2009 From: trac at haiku-os.org (franxico) Date: Mon, 01 Jun 2009 13:24:10 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.f4da959436ebef4c9a1ad1be9ee934a9@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by franxico): Is there any other info I could give? Otherwise, what can we do for the moment to avoid this problem (without having to disconnect the hardware)? Thanks -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 15:57:30 2009 From: trac at haiku-os.org (mr.Noisy) Date: Mon, 01 Jun 2009 13:57:30 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 Message-ID: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Received a KDL on boot using my Core 2 Duo (dual core) using haiku gcc4 r30911 raw image. Haiku is booting from flash drive. Disabling Machine specs: Core 2 Duo E8400 on ASUS P5KPL-AM w/2gb RAM and 500gb SATA w/SATA DVD-RW drive. Keyboard and mouse are PS/2. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 16:09:06 2009 From: trac at haiku-os.org (mr.Noisy) Date: Mon, 01 Jun 2009 14:09:06 -0000 Subject: [Haiku-bugs] [Haiku] #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed Message-ID: <043.92194c43c26b1f704f6ee442e62f188a@haiku-os.org> #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed -------------------------------------+-------------------------------------- Reporter: mr.Noisy | Owner: rudolfc Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Windows driver automatically reduces fan speed, reducing noise and power consumption. Could you do something like this in Haiku? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 16:24:37 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 01 Jun 2009 14:24:37 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.93db209b3e83b2ef620ff2fd6ab2199e@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by anevilyak): Is this a prebuilt image downloaded from haiku-files, or are you building it yourself? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 21:11:53 2009 From: trac at haiku-os.org (idefix) Date: Mon, 01 Jun 2009 19:11:53 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.db9e7a470a85660fe4e919d6f9ec26c3@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS ------------------------------+--------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by idefix): I can't reproduce this in VMware, so it has to do something with my hardware. I will try some earlier revisions to find out when the problem started. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 22:08:07 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 01 Jun 2009 20:08:07 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.74f0d24de60c0a4b2ab7d39e4ab5ae52@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, I am hoping the I2C buses now work on your card. Could you upload a new logfile from revision 30938 or later? Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 22:50:26 2009 From: trac at haiku-os.org (siarzhuk) Date: Mon, 01 Jun 2009 20:50:26 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.930f47bb6e2978282f45f2016a123d9c@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by siarzhuk): Replying to [comment:2 mmlr]: > It's one of the two standard ide bus_manager crashes. There should be a bug report about that one already, but I seem to be unable to find it right now. Do you mean #2488? I'm in contact with this guy (Serge Filippov AKA FSV) - I asked him to try to disable DVD drive for testing. He also use usb flash drive to boot Haiku and receive almost the same crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 22:50:47 2009 From: trac at haiku-os.org (siarzhuk) Date: Mon, 01 Jun 2009 20:50:47 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.e9715d6e8d98956a1dd0c7c85d56e96d@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 23:08:54 2009 From: trac at haiku-os.org (idefix) Date: Mon, 01 Jun 2009 21:08:54 -0000 Subject: [Haiku-bugs] [Haiku] #3985: ActivityMonitor crashes when adding view under stressed system (was: ActivityMonitor crashes when adding view with keyboard) In-Reply-To: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> References: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> Message-ID: <050.ec8d910dffe3924aab42568a560280f7@haiku-os.org> #3985: ActivityMonitor crashes when adding view under stressed system ------------------------------------------+--------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------------+--------------------------------- Comment(by idefix): I investigated this further and it doesn't matter if the view is added with the mouse or the keyboard. What you do need is Haiku running in VMware on a slow computer (PII @ 400MHz) and the time interval set to a low value (less than 100ms), causing the processor to be fully utilised by ActivityMonitor. It will then reliably crash every time you add a view. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 23:48:13 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 01 Jun 2009 21:48:13 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.767e5286a794005f0aa8c9e1af8fb454@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 ------------------------+--------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 3134 Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3134 Comment: I actually meant #3134, which was reported by the same person as this one. All three are the same though, so I'll close two of them as duplicate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 23:48:38 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 01 Jun 2009 21:48:38 -0000 Subject: [Haiku-bugs] [Haiku] #2488: Crash: Kernel Debug on... In-Reply-To: <038.44eb62f4ba371ff204b386dd7e75c46c@haiku-os.org> References: <038.44eb62f4ba371ff204b386dd7e75c46c@haiku-os.org> Message-ID: <047.ece33519c3efdbe28cf597ea1ca22b57@haiku-os.org> #2488: Crash: Kernel Debug on... ----------------------------+----------------------------------------------- Reporter: FSV | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: Resolution: duplicate | Blockedby: 3134 Platform: x64 | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3134 Comment: Closing as duplicate of #3134 as that one has more info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 00:58:26 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 01 Jun 2009 22:58:26 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilde) Key requires a double keypress to be displayed In-Reply-To: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> References: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> Message-ID: <051.a17c3c816e549d495af43b11227f4daf@haiku-os.org> #2241: ~ (tilde) Key requires a double keypress to be displayed -----------------------+---------------------------------------------------- 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 has changed recently (i'm guessing in builds after r30700 or so?), now you only need to press the ~ key once to have it register, but it doesn't get displayed until another key is pressed. Pressing it twice will give you ~~. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 01:05:22 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 01 Jun 2009 23:05:22 -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.2e3f12bbaa7ef642be0df85c6cdb6a7d@haiku-os.org> #1072: Write an HDA audio driver and add-on -------------------------------+-------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: x86 Blocking: 3193 | -------------------------------+-------------------------------------------- Comment(by scottmc): Replying to [comment:25 scottmc]: > Sound is now working on my nvidia based laptop now (Compaq cq50-215nr). Nice work! > It used to work on my cq50-215nr, but hasn't for the last month or two. Media prefs show that it's detected, but I get no sound. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 01:07:34 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 01 Jun 2009 23:07:34 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilde) Key requires a double keypress to be displayed In-Reply-To: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> References: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> Message-ID: <051.64ce9e1a8cd686fddeae4b4853620b3f@haiku-os.org> #2241: ~ (tilde) Key requires a double keypress to be displayed -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by bonefish): Tilde is a dead key in the US-International layout, so this should be the expected behavior. Unless I miss something, the ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 01:13:25 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 01 Jun 2009 23:13:25 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.d3fde09542c5612bbcaaacdbe368d4b6@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ 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): Is there any particular set of kernel tracing options I could enable that might provide extra info for this particular case? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 01:46:22 2009 From: trac at haiku-os.org (diver) Date: Mon, 01 Jun 2009 23:46:22 -0000 Subject: [Haiku-bugs] [Haiku] #3990: [network] localhost resolves to wrong ip Message-ID: <040.41a76d9b195d085ea9ecf0281f0d2506@haiku-os.org> #3990: [network] localhost resolves to wrong ip --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- {{{ ping localhost PING localhost (1.0.0.127): 56 data bytes }}} Tested with r30941 on vbox 2.0.2 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 02:54:06 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 00:54:06 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.4df3f8c8b3815ece84cde41ea991aa88@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): I'm reporting a fault with the 4th partition, so having the 3rd partition set as type 06 shouldn't affect anything. I'm also aware that there are manual ways of fixing the situation, but Haiku needs to be able to set this up itself. The 4th partition is type 0c (FAT32) already, so this can't be the issue. Faults as I see them: 1. DriveSetup didn't change the partition type for the 3rd partition's table entry when I initialized it as BFS. This doesn't affect it, the partition works fine. 2. Installer isn't seeing the 4th partition as the right size. 3. DriveSetup won't allow initialization of the 4th partition. Note that in all preceding comments I was using (as they say in BASIC) OPTION BASE 1 when referring to partition numbering. They are numbered from 0 to 3 within the system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 04:07:50 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 02 Jun 2009 02:07:50 -0000 Subject: [Haiku-bugs] [Haiku] #3990: [network] localhost resolves to wrong ip In-Reply-To: <040.41a76d9b195d085ea9ecf0281f0d2506@haiku-os.org> References: <040.41a76d9b195d085ea9ecf0281f0d2506@haiku-os.org> Message-ID: <049.3a7ce854cda923a729defeb20a76e147@haiku-os.org> #3990: [network] localhost resolves to wrong ip --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Hm...looks correct for me in 30934, will update shortly and see if I can duplicate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 17:21:48 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 01 Jun 2009 15:21:48 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.bd324a50def77af5f961d2b1e892dc77@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): Replying to [comment:6 franxico]: > Is there any other info I could give? Basically I would need access to a machine having that problem to really be able to investigate. Sadly all of my hardware (7 machines) do not exhibit that problem, so I'm pretty much clueless. > Otherwise, what can we do for the moment to avoid this problem (without having to disconnect the hardware)? Thanks Not really. You could try flipping BIOS options. Usually stuff like this is related to legacy emulation. But as you stated your BIOS options are severely limited, so there's not too much you can do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 17:28:32 2009 From: trac at haiku-os.org (mr.Noisy) Date: Mon, 01 Jun 2009 15:28:32 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.d9201776a6a2474187f1e9d1a98325cc@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mr.Noisy): Is a a prebuilt image downloaded from haiku-files. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 1 17:19:11 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 01 Jun 2009 15:19:11 -0000 Subject: [Haiku-bugs] [Haiku] #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 In-Reply-To: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> References: <043.4263732f47dd0e2f8f0736974c17c178@haiku-os.org> Message-ID: <052.63c18de72f58aa75714fdbab8633f1d5@haiku-os.org> #3988: PANIC: page fault but interrupts were disabled. Touching address 0xccccccd0 from eip 0x0004f171 -----------------------+---------------------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mmlr): It's one of the two standard ide bus_manager crashes. There should be a bug report about that one already, but I seem to be unable to find it right now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 10:12:41 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 02 Jun 2009 08:12:41 -0000 Subject: [Haiku-bugs] [Haiku] #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed In-Reply-To: <043.92194c43c26b1f704f6ee442e62f188a@haiku-os.org> References: <043.92194c43c26b1f704f6ee442e62f188a@haiku-os.org> Message-ID: <052.6d3b5030888cdf7405b0077beaa9cf5e@haiku-os.org> #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed -------------------------------------+-------------------------------------- Reporter: mr.Noisy | Owner: rudolfc Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): We don't have a nVidia driver for the GF8 and later series yet. (It exists, but does nothing yet: dev still has to be started on this). Once we have a driver, we can probably (hopefully) lower the fan rotational speed indeed. the program nvclock (for windows and linux) has code in it to set the rotational speed for a number of cards, maybe for yours as well. Such code could be implemented in our driver to be. The GF8 and later cards currently run in VESA mode on haiku. The only downsides of that currently are: - noisy fan (apparantly ;-) - no refreshrate settings acceleration currently isn't used by the app_server anyway, and setting modes (resolution/colordepth) can be done these days using VESA mode on the fly. Hope this info is enough for now. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 11:52:05 2009 From: trac at haiku-os.org (idefix) Date: Tue, 02 Jun 2009 09:52:05 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.3f39b14ee4729bcb3801031e89ac3df3@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | 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:6 haiqu]: > I'm reporting a fault with the 4th partition, so having the 3rd partition set as type 06 shouldn't affect anything. Sorry, I misread that one. >I'm also aware that there are manual ways of fixing the situation, but Haiku needs to be able to set this up itself. But if you manually change this partition type from 06 to EB? Will Installer then see the 4th partition as the right size and will DriveSetup allow initialisation? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 14:47:07 2009 From: trac at haiku-os.org (jahaiku) Date: Tue, 02 Jun 2009 12:47:07 -0000 Subject: [Haiku-bugs] [Haiku] #3938: SegFault at unmount of USB-Stick In-Reply-To: <042.898092470d7406deb5168041f7350951@haiku-os.org> References: <042.898092470d7406deb5168041f7350951@haiku-os.org> Message-ID: <051.981141afdfb27592220ce15e5b31620f@haiku-os.org> #3938: SegFault at unmount of USB-Stick ---------------------------+------------------------------------------------ Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by jahaiku): Replying to [ticket:3938 jahaiku]: > If I unmount a mounted USB-Stick in Tracker over the right mouse menu I get the attached SegFault. > This is version from Friday from haiku-files. I have retried, in the hope the error is gone, with the gcc4 build from 29.5 on EeePC and I get exactly the same error, again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 14:51:11 2009 From: trac at haiku-os.org (richienyhus) Date: Tue, 02 Jun 2009 12:51:11 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.a893d4551a78b1d4eb100c021fb1ef46@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): ^ From r30941 GCC4 The motherboard only has a VGA connector on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 15:07:44 2009 From: trac at haiku-os.org (michael.weirauch) Date: Tue, 02 Jun 2009 13:07:44 -0000 Subject: [Haiku-bugs] [Haiku] #3938: SegFault at unmount of USB-Stick In-Reply-To: <042.898092470d7406deb5168041f7350951@haiku-os.org> References: <042.898092470d7406deb5168041f7350951@haiku-os.org> Message-ID: <051.0ea286275732a09be680b5a18e0021d8@haiku-os.org> #3938: SegFault at unmount of USB-Stick ---------------------------+------------------------------------------------ Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by michael.weirauch): Looks like dup of #3962 and #3964 . -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 15:44:50 2009 From: trac at haiku-os.org (stippi) Date: Tue, 02 Jun 2009 13:44:50 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.03253c6c91b4bf271b5e158a1327322b@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by stippi): * milestone: R1 => R1/alpha1 Comment: For me, this is always reproducable. But I have no time currently to look into it, or to binary search the revision that caused this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 21:05:10 2009 From: trac at haiku-os.org (michael.weirauch) Date: Tue, 02 Jun 2009 19:05:10 -0000 Subject: [Haiku-bugs] [Haiku] #3991: random_file_actions: runs fail when disabling block cache Message-ID: <051.f3737c84aada1b4a699c2948615a2902@haiku-os.org> #3991: random_file_actions: runs fail when disabling block cache ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- r30944; ata-bm; acpi; Running '''random_file_actions''' without block cache (-n), I get a reproduceable error: {{{ random_file_actions -m256000 -f20 -d10 -r2000 -vna }}} {{{ 189 truncate "./random_file_temp/file-13" generated: 0000 00000000 00000000 0e000000 0c000e00 ................ generated: 0010 10001200 14001600 18001a00 1c001e00 ............... generated: 0020 20002200 24002600 28002a00 2c002e00 .".$.&.(.*.,... generated: 0030 30003200 34003600 38003a00 3c003e00 0.2.4.6.8.:.<.>. generated: 0040 40004200 44004600 48004a00 4c004e00 @.B.D.F.H.J.L.N. generated: 0050 50005200 54005600 58005a00 5c005e00 P.R.T.V.X.Z.\.^. generated: 0060 60006200 64006600 68006a00 6c006e00 `.b.d.f.h.j.l.n. generated: 0070 70007200 74007600 78007a00 7c007e00 p.r.t.v.x.z.|.~. generated: 0080 80008200 84008600 88008a00 8c008e00 ................ generated: 0090 90009200 94009600 98009a00 9c009e00 ................ generated: 00a0 a000a200 a400a600 a800aa00 ac00ae00 ................ generated: 00b0 b000b200 b400b600 b800ba00 bc00be00 ................ generated: 00c0 c000c200 c400c600 c800ca00 cc00ce00 ................ generated: 00d0 d000d200 d400d600 d800da00 dc00de00 ................ generated: 00e0 e000e200 e400e600 e800ea00 ec00ee00 ................ generated: 00f0 f000f200 f400f600 f800fa00 fc00fe00 ................ read: 0000 00000000 00000000 08000000 0c000e00 ................ read: 0010 10001200 14001600 18001a00 1c001e00 ............... read: 0020 20002200 24002600 28002a00 2c002e00 .".$.&.(.*.,... read: 0030 30003200 34003600 38003a00 3c003e00 0.2.4.6.8.:.<.>. read: 0040 40004200 44004600 48004a00 4c004e00 @.B.D.F.H.J.L.N. read: 0050 50005200 54005600 58005a00 5c005e00 P.R.T.V.X.Z.\.^. read: 0060 60006200 64006600 68006a00 6c006e00 `.b.d.f.h.j.l.n. read: 0070 70007200 74007600 78007a00 7c007e00 p.r.t.v.x.z.|.~. read: 0080 80008200 84008600 88008a00 8c008e00 ................ read: 0090 90009200 94009600 98009a00 9c009e00 ................ read: 00a0 a000a200 a400a600 a800aa00 ac00ae00 ................ read: 00b0 b000b200 b400b600 b800ba00 bc00be00 ................ read: 00c0 c000c200 c400c600 c800ca00 cc00ce00 ................ read: 00d0 d000d200 d400d600 d800da00 dc00de00 ................ read: 00e0 e000e200 e400e600 e800ea00 ec00ee00 ................ read: 00f0 f000f200 f400f600 f800fa00 fc00fe00 ................ random_file_actions: block at 0 differ in "./random_file_temp/file-13"! }}} Running the same command without disabling the block cache, {{{ random_file_actions -m256000 -f20 -d10 -r2000 -va }}} the runs complete successfully. Repeating this in a tic-toc manner, always yields the same. W/o block cache, failure, with block cache, ok. PS: Just tested on a second partition and it yielded the same result as above. Then wen't on to test on my main dev partition and got the following which looks a bit different: {{{ 153 replace "./random_file_temp/file-56" contents write 203303 bytes generated: 0000 00000000 00000000 33000000 0c000e00 ........3....... generated: 0010 10001200 14001600 18001a00 1c001e00 ............... generated: 0020 20002200 24002600 28002a00 2c002e00 .".$.&.(.*.,... generated: 0030 30003200 34003600 38003a00 3c003e00 0.2.4.6.8.:.<.>. generated: 0040 40004200 44004600 48004a00 4c004e00 @.B.D.F.H.J.L.N. generated: 0050 50005200 54005600 58005a00 5c005e00 P.R.T.V.X.Z.\.^. generated: 0060 60006200 64006600 68006a00 6c006e00 `.b.d.f.h.j.l.n. generated: 0070 70007200 74007600 78007a00 7c007e00 p.r.t.v.x.z.|.~. generated: 0080 80008200 84008600 88008a00 8c008e00 ................ generated: 0090 90009200 94009600 98009a00 9c009e00 ................ generated: 00a0 a000a200 a400a600 a800aa00 ac00ae00 ................ generated: 00b0 b000b200 b400b600 b800ba00 bc00be00 ................ generated: 00c0 c000c200 c400c600 c800ca00 cc00ce00 ................ generated: 00d0 d000d200 d400d600 d800da00 dc00de00 ................ generated: 00e0 e000e200 e400e600 e800ea00 ec00ee00 ................ generated: 00f0 f000f200 f400f600 f800fa00 fc00fe00 ................ read: 0000 00500000 00000000 24000000 0c500e50 .P......$....P.P read: 0010 10501250 14501650 18501a50 1c501e50 .P.P.P.P.P.P.PP read: 0020 20502250 24502650 28502a50 2c502e50 P"P$P&P(P*P,P.P read: 0030 30503250 34503650 38503a50 3c503e50 0P2P4P6P8P:P

P read: 0040 40504250 44504650 48504a50 4c504e50 @PBPDPFPHPJPLPNP read: 0050 50505250 54505650 58505a50 5c505e50 PPRPTPVPXPZP\P^P read: 0060 60506250 64506650 68506a50 6c506e50 `PbPdPfPhPjPlPnP read: 0070 70507250 74507650 78507a50 7c507e50 pPrPtPvPxPzP|P~P read: 0080 80508250 84508650 88508a50 8c508e50 .P.P.P.P.P.P.P.P read: 0090 90509250 94509650 98509a50 9c509e50 .P.P.P.P.P.P.P.P read: 00a0 a050a250 a450a650 a850aa50 ac50ae50 .P.P.P.P.P.P.P.P read: 00b0 b050b250 b450b650 b850ba50 bc50be50 .P.P.P.P.P.P.P.P read: 00c0 c050c250 c450c650 c850ca50 cc50ce50 .P.P.P.P.P.P.P.P read: 00d0 d050d250 d450d650 d850da50 dc50de50 .P.P.P.P.P.P.P.P read: 00e0 e050e250 e450e650 e850ea50 ec50ee50 .P.P.P.P.P.P.P.P read: 00f0 f050f250 f450f650 f850fa50 fc50fe50 .P.P.P.P.P.P.P.P random_file_actions: block at 0 differ in "./random_file_temp/dir-48/file-50"! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 22:24:42 2009 From: trac at haiku-os.org (korli) Date: Tue, 02 Jun 2009 20:24:42 -0000 Subject: [Haiku-bugs] [Haiku] #3750: Missing posix math rounding functions In-Reply-To: <041.90f24cd0ace737934257dad87dfbb2e0@haiku-os.org> References: <041.90f24cd0ace737934257dad87dfbb2e0@haiku-os.org> Message-ID: <050.12ffe415fda873a886ca5af27cfc71fc@haiku-os.org> #3750: Missing posix math rounding functions --------------------------------+------------------------------------------- Reporter: ekdahl | 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 korli): * status: new => closed * resolution: => fixed Comment: Fixed in r30945 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 22:35:14 2009 From: trac at haiku-os.org (korli) Date: Tue, 02 Jun 2009 20:35:14 -0000 Subject: [Haiku-bugs] [Haiku] #3792: OpenSSH still puts license into /boot/beos/etc/license In-Reply-To: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> References: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> Message-ID: <053.a0e43ca93cac4268afaaaf13c7b10376@haiku-os.org> #3792: OpenSSH still puts license into /boot/beos/etc/license -------------------------+-------------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by korli): It seems to be in /boot/common/data/licenses/. Can we close the ticket ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 2 22:44:33 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 02 Jun 2009 20:44:33 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.c951a7c9dbd0aa74ee796d8ebdc6d697@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Aha, I see! I hope you don't mind to upload another log, now from revision 30946 or later? There's a third I2C bus that might just work.. Thanks in advance :-) Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 00:29:44 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 02 Jun 2009 22:29:44 -0000 Subject: [Haiku-bugs] [Haiku] #3792: OpenSSH still puts license into /boot/beos/etc/license In-Reply-To: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> References: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> Message-ID: <053.910a3866d1326f920cfa3c3911a4da0d@haiku-os.org> #3792: OpenSSH still puts license into /boot/beos/etc/license -------------------------+-------------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): correct, close it, this was fixed in r30915 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 00:55:35 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 22:55:35 -0000 Subject: [Haiku-bugs] [Haiku] #3992: Zip-O-Matic includes files from Trash bin Message-ID: <040.e038e43eb063fd3cf321a231e853bf04@haiku-os.org> #3992: Zip-O-Matic includes files from Trash bin ----------------------------------+----------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- When packaging the Free Pascal Compiler today I was using a spare empty partition to set out all the files to be included. Some of them needed to be in the Home directory, because that's where the compiler looks for configuration information if it isn't in the current directory. When I zipped up the package I noticed the file was much larger than the last build, and on investiagtion discovered that Zip-O-Matic had included the hidden directory ~/Desktop/Trash and all its contents. I've listed this under Applications/Tracker even though it's an add-on because Zip-O-Matic doesn't seem to have its own entry. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:29:25 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:29:25 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.fc0bdd79b2f06f739ff026e6e0b9e9ab@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): Once again, the partition type 06 is on the 3rd partition's main partition table entry, so changing that doesn't affect the problem. I did try doing that early on, btw. The 4th partition's entry correctly shows type 0c (FAT32). Haiku does see it as 18.1GB (see first snapshot) so the problem here is localized to the Installer application only. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:31:46 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:31:46 -0000 Subject: [Haiku-bugs] [Haiku] #3699: Web Excel PCI modem not detected In-Reply-To: <040.b5618305d67c315d1235f52da934b7d0@haiku-os.org> References: <040.b5618305d67c315d1235f52da934b7d0@haiku-os.org> Message-ID: <049.75da92e101c38b1f8bd146324cff760d@haiku-os.org> #3699: Web Excel PCI modem not detected ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by haiqu): I think this one can be killed off. My PCI modem was zorched in a thunderstorm, and anyhow it would never have work in Haiku 'cause it's a winmodem. So pretty-much irrelevant now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:35:08 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:35:08 -0000 Subject: [Haiku-bugs] [Haiku] #3778: Bootstrapping Haiku from BeOS now requires a boot floppy image In-Reply-To: <040.13bd32c49839c3e565c7f75270e26fb1@haiku-os.org> References: <040.13bd32c49839c3e565c7f75270e26fb1@haiku-os.org> Message-ID: <049.2a85c5d5f555907a1ddef7348bbffe40@haiku-os.org> #3778: Bootstrapping Haiku from BeOS now requires a boot floppy image -------------------------+-------------------------------------------------- Reporter: haiqu | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by haiqu): FYI I tried building and using makebootabletiny from BeOS and the partition didn't boot. It's still looking for the wrong file and in the wrong location. If I'd built it from Haiku it probably would have worked, but this report is about bootstrapping into a new system so that option wouldn't be available. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:38:40 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:38:40 -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.a84ad16cc34fe5b9ec2bba450854e003@haiku-os.org> #3808: Copying or creating large files causes General System Error ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by haiqu): Haven't had a problem with this since changing to a faster computer. My previous development box was a Duron 800 and evidently Haiku runs out of puff on that. Using the Athlon 64 3000+ it just works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:41:47 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:41:47 -0000 Subject: [Haiku-bugs] [Haiku] #3904: "Save MBR" option pointless during CD install In-Reply-To: <040.5a4ee4866917546d06c56b3155180306@haiku-os.org> References: <040.5a4ee4866917546d06c56b3155180306@haiku-os.org> Message-ID: <049.4c1b364da39f67577362bcd37c48a2e2@haiku-os.org> #3904: "Save MBR" option pointless during CD install ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): Looks like this issue was fixed, report should be closed now. There is a related issue where the installer reports that a drive contains data and issues a warning even when empty. It's seeing the Home directory, so this probably needs to be checked by the installer too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 01:42:53 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 02 Jun 2009 23:42:53 -0000 Subject: [Haiku-bugs] [Haiku] #3923: Web links in Thunderbird email client no longer work when clicked In-Reply-To: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> References: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> Message-ID: <049.dbdfad76d3e9728b9be25154b9c3d01c@haiku-os.org> #3923: Web links in Thunderbird email client no longer work when clicked --------------------+------------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------+------------------------------------------------------- Comment(by haiqu): Seems to work consistently between upgrade installations now. Close please. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:03:43 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 03 Jun 2009 00:03:43 -0000 Subject: [Haiku-bugs] [Haiku] #3938: SegFault at unmount of USB-Stick In-Reply-To: <042.898092470d7406deb5168041f7350951@haiku-os.org> References: <042.898092470d7406deb5168041f7350951@haiku-os.org> Message-ID: <051.0ab71d52fd9dec76ff7b391dfe504c8e@haiku-os.org> #3938: SegFault at unmount of USB-Stick ----------------------------+----------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3964 Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3964 Comment: Consolidating duplicates. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:04:29 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 03 Jun 2009 00:04:29 -0000 Subject: [Haiku-bugs] [Haiku] #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount In-Reply-To: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> References: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> Message-ID: <060.3356b5b5b4c0856fe0e77da6bdea33ae@haiku-os.org> #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount -------------------------------+-------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3964 Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3964 Comment: Consolidating duplicates. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:04:55 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 00:04:55 -0000 Subject: [Haiku-bugs] [Haiku] #2597: PANIC: page fault, but interrupts were disabled. Touching address 0x6e697478 from eip 0x80042f08 In-Reply-To: <044.0a50f04f250c875b734e7af31f02acad@haiku-os.org> References: <044.0a50f04f250c875b734e7af31f02acad@haiku-os.org> Message-ID: <053.970e084d4542899cf0cb01321f866ec7@haiku-os.org> #2597: PANIC: page fault, but interrupts were disabled. Touching address 0x6e697478 from eip 0x80042f08 ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Closing this one as I haven't encountered it again since last comment close to a year ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:10:21 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 03 Jun 2009 00:10:21 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a In-Reply-To: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> References: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> Message-ID: <049.47a9e0708dcec73f901cfe8ad189853c@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 3983 Platform: All | Blocking: 3938, 3962 ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3983 Comment: OK, closing this one as well, as a duplicate of #3983 as this holds the most accessible information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:16:19 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 00:16:19 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a In-Reply-To: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> References: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> Message-ID: <049.575c42a11fd1e8cb393a9d625685bcca@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Blockedby: 3983 Platform: All | Blocking: 3938, 3962 ------------------------+--------------------------------------------------- Comment(by anevilyak): Interesting, it didn't even occur to me that this one might be related when looking for existing bugs before filing #3983. Nice catch. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:44:02 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 03 Jun 2009 00:44:02 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.da5461fe2f434c6c1ff5547870d7fc4b@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by mmlr): But the question is how big that FAT32 filesystem actually is. The partition table is pretty much meaningless for Haiku except to discover the start of partitions. What DriveSetup and Installer show may very well differ, as they are not intended to show you the same data. DriveSetup will show you the partition information as it's recorded in the MBR. Installer on the other hand will show you filesystem information of the filesystems contained in the partitions. It's valid for you to have a 10GB partition and only put a filesystem on the first hundred megabytes. That would happen when you'd dd a Haiku image on top of a partition for example. In that case DriveSetup would show the 10GB partition and Installer the BFS size of the image. From what I gather, is it possible that the partition as stored in the MBR is simply bigger than the actual drive? And Windows created a 2.1GB FAT32 fs in it as that's the space really left? This could also explain why DriveSetup doesn't allow you to initialize the partition, as it regards it as invalid? The partition type field in the MBR is completely disregarded BTW. And DriveSetup doesn't currently modify the MBR at all. As it (or more correctly the disk device manager backend it uses) doesn't yet do partitioning at all, it never touches the MBR. So it's expected that initializing a partition doesn't change the partition type code. The field is not relevant to Haiku as it probes the partitions for the different filesystems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:52:27 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 00:52:27 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.288a976ffbc94b3fdafd4474b903d3a6@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): Attached serial log with devfs tracing enabled. I can't see any obvious culprits in there myself right now, but I don't really know the devfs that well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 02:57:02 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 03 Jun 2009 00:57:02 -0000 Subject: [Haiku-bugs] [Haiku] #3778: Bootstrapping Haiku from BeOS now requires a boot floppy image In-Reply-To: <040.13bd32c49839c3e565c7f75270e26fb1@haiku-os.org> References: <040.13bd32c49839c3e565c7f75270e26fb1@haiku-os.org> Message-ID: <049.816e1628111e577f86d8db4f8d7ef3a1@haiku-os.org> #3778: Bootstrapping Haiku from BeOS now requires a boot floppy image -------------------------+-------------------------------------------------- Reporter: haiqu | Owner: haiku-web Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): Replying to [comment:7 haiqu]: > FYI I tried building and using makebootabletiny from BeOS and the partition didn't boot. It's still looking for the wrong file and in the wrong location. If I'd built it from Haiku it probably would have worked, but this report is about bootstrapping into a new system so that option wouldn't be available. makebootabletiny does nothing more than change the partition offset - it doesn't set the path, which is why I suggested dd'ing the entire first block of a haiku IMAGE to your partition and then running makebootabletiny on it...but anyhow, i'm sure you'll find more creative ways. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 06:04:34 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 04:04:34 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.632a52e5a983a0489b5aeab4a19c11ff@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): Still working on binary searching what revision caused this...I've managed to narrow it to somewhere between 30500 and 30770 so far, working on narrowing it down further. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 06:20:51 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 04:20:51 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.09d5098288fc7685d424ad92362f038a@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): Make that between r30700 and r30770. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 07:36:34 2009 From: trac at haiku-os.org (jahaiku) Date: Wed, 03 Jun 2009 05:36:34 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.5e0b2dbaa9e2894fa31a465427f16ca8@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Changes (by jahaiku): * cc: Jens.Arm@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 09:03:29 2009 From: trac at haiku-os.org (stippi) Date: Wed, 03 Jun 2009 07:03:29 -0000 Subject: [Haiku-bugs] [Haiku] #3792: OpenSSH still puts license into /boot/beos/etc/license In-Reply-To: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> References: <044.e3817d7e662274efdeb0e3f004f4f799@haiku-os.org> Message-ID: <053.c127b12a5201a8d4715e2c53d931d57f@haiku-os.org> #3792: OpenSSH still puts license into /boot/beos/etc/license --------------------------+------------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 09:13:40 2009 From: trac at haiku-os.org (axeld) Date: Wed, 03 Jun 2009 07:13:40 -0000 Subject: [Haiku-bugs] [Haiku] #3699: Web Excel PCI modem not detected In-Reply-To: <040.b5618305d67c315d1235f52da934b7d0@haiku-os.org> References: <040.b5618305d67c315d1235f52da934b7d0@haiku-os.org> Message-ID: <049.cbdbf47204743d36673c1d9ee66cf261@haiku-os.org> #3699: Web Excel PCI modem not detected ----------------------------+----------------------------------------------- Reporter: haiqu | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Thanks for the note! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 09:14:03 2009 From: trac at haiku-os.org (stippi) Date: Wed, 03 Jun 2009 07:14:03 -0000 Subject: [Haiku-bugs] [Haiku] #3923: Web links in Thunderbird email client no longer work when clicked In-Reply-To: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> References: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> Message-ID: <049.8e1dc0bf7652c7cca517e3d60aab81f8@haiku-os.org> #3923: Web links in Thunderbird email client no longer work when clicked ---------------------+------------------------------------------------------ Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------+------------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 09:24:07 2009 From: trac at haiku-os.org (axeld) Date: Wed, 03 Jun 2009 07:24:07 -0000 Subject: [Haiku-bugs] [Haiku] #3992: Zip-O-Matic includes files from Trash bin In-Reply-To: <040.e038e43eb063fd3cf321a231e853bf04@haiku-os.org> References: <040.e038e43eb063fd3cf321a231e853bf04@haiku-os.org> Message-ID: <049.538b240b145e674e0c209b4fd51154ff@haiku-os.org> #3992: Zip-O-Matic includes files from Trash bin ----------------------------------+----------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by axeld): This is indeed very unintuitive right now. However, the solution we're aiming for is to make the "Desktop" directory always visible. Once this is done, this ticket can be closed as well -- so the component is just right, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 09:26:10 2009 From: trac at haiku-os.org (axeld) Date: Wed, 03 Jun 2009 07:26:10 -0000 Subject: [Haiku-bugs] [Haiku] #3991: random_file_actions: runs fail when disabling block cache In-Reply-To: <051.f3737c84aada1b4a699c2948615a2902@haiku-os.org> References: <051.f3737c84aada1b4a699c2948615a2902@haiku-os.org> Message-ID: <060.c731189d2aef001de0e866105dfcc60e@haiku-os.org> #3991: random_file_actions: runs fail when disabling block cache ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => critical * status: new => assigned * milestone: R1 => R1/alpha1 Comment: Oh, that sounds perfect! I'll look into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 10:28:27 2009 From: trac at haiku-os.org (jahaiku) Date: Wed, 03 Jun 2009 08:28:27 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.7627502589c912b15f5c517c227c5df4@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by jahaiku): This is just a guess, but it could be around r30726 (axeld: * Instead of deleting the device directly, we now only remove it from its ...) 3 weeks ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 11:26:54 2009 From: trac at haiku-os.org (axeld) Date: Wed, 03 Jun 2009 09:26:54 -0000 Subject: [Haiku-bugs] [Haiku] #3980: [patch] Keyboard shortcut icon for Apple keyboards In-Reply-To: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> References: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> Message-ID: <050.2e7352063bac51dd82d700864d580369@haiku-os.org> #3980: [patch] Keyboard shortcut icon for Apple keyboards --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): Just a few comments: the B_COMMAND_IS_* constants should not be public or used at all, since we already have modifier constants that can do the job. I don't like the "/Mac OS" addition in Keymaps, and would just remove it again - the check now looks wrong, too, as it will detect Windows/Haiku mode now incorrectly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 14:23:26 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 12:23:26 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.cfb562a1e1fb43c6dd07e1a75fcfea7e@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): Replying to [comment:14 jahaiku]: > This is just a guess, but it could be around r30726 (axeld: * Instead of deleting the device directly, we now only remove it from its ...) 3 weeks ago. Looks quite likely, at least r30726 also exhibits the problem, testing one or two more revisions to make sure it's in fact the culprit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 14:27:54 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 12:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.42b0253813d1c8b99b5fc1f94f4cf1a5@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): r30726 confirmed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 14:28:46 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 12:28:46 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.3d06c9b31156a35d93d2568b93053307@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: bonefish => axeld -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 14:29:17 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 12:29:17 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.cd03e340538e8a18b143c18b08f31bcc@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Comment(by anevilyak): Will see if I can have a look after work unless you get to it first Axel :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 20:15:27 2009 From: trac at haiku-os.org (axeld) Date: Wed, 03 Jun 2009 18:15:27 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilde) Key requires a double keypress to be displayed In-Reply-To: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> References: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> Message-ID: <051.407cbb389e339012209feac6ce5d6590@haiku-os.org> #2241: ~ (tilde) Key requires a double keypress to be displayed ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 3 23:14:26 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 21:14:26 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.8e8edbd6839bb441c8b99609511421f7@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: axeld => anevilyak * status: new => assigned Comment: Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 00:02:50 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 03 Jun 2009 22:02:50 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.5ac5eb6b15d9165da1de398a361efd55@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: anevilyak => axeld * status: assigned => new Comment: The problem seems to be the change on line 256 of devfs.cpp: {{{ 255 // pass the call through to the underlying device 256 vnode->stream.u.dev.device->Removed(); }}} Removed() winds up getting called on eject, which results in the raw device deleting itself, hence the 0xdeadbeef above. What I'm uncertain about is how to determine when we should and should not be calling Removed(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 00:35:17 2009 From: trac at haiku-os.org (luroh) Date: Wed, 03 Jun 2009 22:35:17 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.bbcae8f3c478f763409db21e3010d92c@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3964 | ---------------------------+------------------------------------------------ Changes (by luroh): * cc: lurohh@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 00:52:12 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 03 Jun 2009 22:52:12 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.44ef32991f8f27e5e9c1dcc92504e460@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): The drive is 74.6GB and the partitions are: 19.2GB, 19.2GB, 18.1GB and 18.1GB - DriveSetup does show these values. The first two partitions were dd'ed (with HDClone) to the raw drive and the remainder was then partitioned in two equal parts. No unused space anywhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 08:59:11 2009 From: trac at haiku-os.org (mr.Noisy) Date: Thu, 04 Jun 2009 06:59:11 -0000 Subject: [Haiku-bugs] [Haiku] #3993: Icons arranging in Tracker Message-ID: <043.2af35cd918e5fa878ccf1eaa2caee94d@haiku-os.org> #3993: Icons arranging in Tracker ----------------------------------+----------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Often I look at the contents of folders in icon mode. I do not like that Tracker arranges the icons of files and folders are not on the grid, but depending on the length of their names. So I always use Cleanup (Alt- Shift-K). It may be convenient to add Autocleanup, or add the option of forced arrange icons on the grid? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 09:20:12 2009 From: trac at haiku-os.org (mr.Noisy) Date: Thu, 04 Jun 2009 07:20:12 -0000 Subject: [Haiku-bugs] [Haiku] #3993: Icon arranging in Tracker (was: Icons arranging in Tracker) In-Reply-To: <043.2af35cd918e5fa878ccf1eaa2caee94d@haiku-os.org> References: <043.2af35cd918e5fa878ccf1eaa2caee94d@haiku-os.org> Message-ID: <052.83278e0fb8c6920cf82789b62fffc871@haiku-os.org> #3993: Icon arranging in Tracker ----------------------------------+----------------------------------------- Reporter: mr.Noisy | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 14:29:50 2009 From: trac at haiku-os.org (axeld) Date: Thu, 04 Jun 2009 12:29:50 -0000 Subject: [Haiku-bugs] [Haiku] #3991: random_file_actions: runs fail when disabling block cache In-Reply-To: <051.f3737c84aada1b4a699c2948615a2902@haiku-os.org> References: <051.f3737c84aada1b4a699c2948615a2902@haiku-os.org> Message-ID: <060.88a0c1c4f9201486cfcafcdf154fcd3a@haiku-os.org> #3991: random_file_actions: runs fail when disabling block cache -------------------------------+-------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed * component: File Systems/BFS => System/Kernel Comment: Took a while to hunt it down, but it's fixed in r30960. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 15:16:45 2009 From: trac at haiku-os.org (haiqu) Date: Thu, 04 Jun 2009 13:16:45 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 Message-ID: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> #3994: Installation fails at r30960 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Just did my usual `svn up` and CD burn for the day. Installation fails at `demangle` with the message: Error: is a directory It doesn't say what exactly is a directory, so I assume the name is blank. Worked fine at r30946 yesterday. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 15:22:17 2009 From: trac at haiku-os.org (haiqu) Date: Thu, 04 Jun 2009 13:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.61ac60f577d99f752a6cec21f255f0e9@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by haiqu): Checked this further by renaming the vesa driver and confirmed that the system is actually loading te nVidia driver. Apprently the nVidia driver is only set up for a single head, and that there's some issue with displaying the splash screen at 1024 x 768. My newer machine has an S3 Unichrome Pro onboard and that works fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 15:29:06 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 04 Jun 2009 13:29:06 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.bc184e87e322a33f39d2d119dad8f3a0@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by anevilyak): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 16:00:33 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 04 Jun 2009 14:00:33 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.223402ce7c1f18adc1d5dba12ee0c25c@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => duplicate * component: Build System => Applications/Installer * blockedby: => 3978 Comment: First of all: '''Please refrain from setting the component to Build System unless it is a problem that happens while running configure or jam! ''' The offending directory is {{{/system/add-ons/kernel/debugger/demangle}}}. Apparently the installer doesn't remove anything which is in the way. Closing as dup of #3978. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 16:01:50 2009 From: trac at haiku-os.org (FSV) Date: Thu, 04 Jun 2009 14:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #3134: KDL (page daemon) when booting on Lenovo S9 In-Reply-To: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> References: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> Message-ID: <053.78e02d4dfdc7e1f20198b8ec204c3a42@haiku-os.org> #3134: KDL (page daemon) when booting on Lenovo S9 --------------------------+------------------------------------------------- Reporter: mr. Noisy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: Blockedby: | Platform: x86 Blocking: 2488, 3988 | --------------------------+------------------------------------------------- Comment(by FSV): I have this error too: PANIC: page fault, but interrupts were disabled. Touching address 0xccccccd8 from eip 0x8004ed91 Changing in BIOS SATA mode from IDE to AHCI was resolved this problem on my system: Core2Duo E4500 / 2 GB RAM / Asus P5B (P965, ICH8) / Radeon X1950Pro / 2 SATA HDD / PATA DVD+RW -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 17:04:56 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 04 Jun 2009 15:04:56 -0000 Subject: [Haiku-bugs] [Haiku] #1063: Update avcodec plugin to a recent ffmpeg; sync with fixes done on FFDecoder and merge. In-Reply-To: <042.40125eaa39e34c59ed3644b9f260be15@haiku-os.org> References: <042.40125eaa39e34c59ed3644b9f260be15@haiku-os.org> Message-ID: <051.326991fc9e26fc1b8ada8e9e3c5438df@haiku-os.org> #1063: Update avcodec plugin to a recent ffmpeg; sync with fixes done on FFDecoder and merge. -----------------------------------+---------------------------------------- Reporter: mmu_man | Owner: mmu_man Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmadia): * status: assigned => closed * resolution: => fixed Comment: quoting scottmc from a personal email: Matt, do you have rights to be able to close tickets? 1063 can be closed as fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 4 23:13:42 2009 From: trac at haiku-os.org (axeld) Date: Thu, 04 Jun 2009 21:13:42 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.6b9eea865f8bfbaa83abe3ba73cb8ba6@haiku-os.org> #3983: KDL when ejecting not mounted CD ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3964 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks Rene, should be fixed with r30961. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 01:43:42 2009 From: trac at haiku-os.org (haiqu) Date: Thu, 04 Jun 2009 23:43:42 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.efc7f42fb11dc1c7ad5604c4f154bb07@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by haiqu): Actually it's a different issue. This time a directory was in the way where a file was going to be placed, c.f. a link in #3978. And btw, since you apparently disagree with my choice of settings, perhaps you could suggest a more relevant one. The Installer works fine, and that's the only other related component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 01:49:00 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 04 Jun 2009 23:49:00 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.7f1f008ed1c853061c89f13d45196e1b@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by anevilyak): Except the Installer doesn't work fine, since it's precisely the component that's failing to correctly detect the presence of a conflicting filesystem object, so yes it's very much a duplicate of #3978, and yes it's the correct component. The build system has nothing whatsoever to do with this problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 04:11:53 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 02:11:53 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.f05b60ecc986e742e064fdd2382d7388@haiku-os.org> #3983: KDL when ejecting not mounted CD ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3964 ----------------------------+----------------------------------------------- Comment(by anevilyak): Confirmed, thanks Axel! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 04:18:46 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 02:18:46 -0000 Subject: [Haiku-bugs] [Haiku] #3687: app_server crash while moving Firefox between workspaces In-Reply-To: <044.1936da52413870ba2a5cbc401da9d00e@haiku-os.org> References: <044.1936da52413870ba2a5cbc401da9d00e@haiku-os.org> Message-ID: <053.c816f217259959c088240b67fb66ba63@haiku-os.org> #3687: app_server crash while moving Firefox between workspaces --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Haven't encountered this any more in probably a month and a half. I don't recall seeing an obvious change that would have had an impact though. Should I close for now and reopen if I see it again? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 07:24:49 2009 From: trac at haiku-os.org (mr.Noisy) Date: Fri, 05 Jun 2009 05:24:49 -0000 Subject: [Haiku-bugs] [Haiku] #3134: KDL (page daemon) when booting on Lenovo S9 In-Reply-To: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> References: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> Message-ID: <053.7d300fe38960fb9619833889d0dc901f@haiku-os.org> #3134: KDL (page daemon) when booting on Lenovo S9 --------------------------+------------------------------------------------- Reporter: mr. Noisy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: Blockedby: | Platform: x86 Blocking: 2488, 3988 | --------------------------+------------------------------------------------- Comment(by mr.Noisy): In my case, this change also solves the problem, but after that the hard disk is not detected by BIOS. Certainly Windows does not boot after that. Hauku couldn't find it in DriveSetup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 07:39:32 2009 From: trac at haiku-os.org (mr.Noisy) Date: Fri, 05 Jun 2009 05:39:32 -0000 Subject: [Haiku-bugs] [Haiku] #3134: KDL (page daemon) when booting on Lenovo S9 In-Reply-To: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> References: <044.a66fcc781ce1156d94e1604333f57a88@haiku-os.org> Message-ID: <053.23f2d95566334628ad3c5d2503de9402@haiku-os.org> #3134: KDL (page daemon) when booting on Lenovo S9 --------------------------+------------------------------------------------- Reporter: mr. Noisy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: Blockedby: | Platform: x86 Blocking: 2488, 3988 | --------------------------+------------------------------------------------- Comment(by mr.Noisy): It concerns the computer described in #3988. Not Lenovo S9. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 07:41:35 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 05 Jun 2009 05:41:35 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working Message-ID: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ The last nightly build was on 2nd june. Please can you reenable the builds and trigger a new one. And there are no reiserfs and ntfs on the build images. Some time ago these fs where on the images. Can you please add them again? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 08:08:14 2009 From: trac at haiku-os.org (kaliber) Date: Fri, 05 Jun 2009 06:08:14 -0000 Subject: [Haiku-bugs] [Haiku] #2696: unimplemented functions In-Reply-To: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> References: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> Message-ID: <051.3251d0d65cbd594fbeec476add7f0f8c@haiku-os.org> #2696: unimplemented functions -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: 2564 | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by kaliber): Here is updated report (r30960). It covers everything except compatibility headers (bsd): {{{ stdio.h: _ftell (_IO_ftell) math.h: gammaf_r (__ieee754_gammaf_r) gamma_r (__ieee754_gamma_r) lgammal (__ieee754_lgammal_r) search.h: hcreate hdestroy hsearch iconv.h: iconv (libiconv) iconv_close (libiconv_close) iconv_open (libiconv_open) dirent.h: seekdir telldir setjmp.h: _setjmp (setjmp) wchar.h: wcsftime }}} Please close the ticket #2702 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 09:16:24 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 07:16:24 -0000 Subject: [Haiku-bugs] [Haiku] #2702: unimplemented functions part 2 In-Reply-To: <042.7d86314140b2ef37dd855cfebc10849b@haiku-os.org> References: <042.7d86314140b2ef37dd855cfebc10849b@haiku-os.org> Message-ID: <051.77319c5fefed58aabf651cfd4fb86881@haiku-os.org> #2702: unimplemented functions part 2 --------------------------------+------------------------------------------- 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 axeld): * status: new => closed * resolution: => fixed Comment: The remaining functions are tracked in #2696 now again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 09:39:21 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 07:39:21 -0000 Subject: [Haiku-bugs] [Haiku] #3990: [network] localhost resolves to wrong ip In-Reply-To: <040.41a76d9b195d085ea9ecf0281f0d2506@haiku-os.org> References: <040.41a76d9b195d085ea9ecf0281f0d2506@haiku-os.org> Message-ID: <049.653801041dfd25b1796e3abda8c56e1c@haiku-os.org> #3990: [network] localhost resolves to wrong ip ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30964. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 09:47:48 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 07:47:48 -0000 Subject: [Haiku-bugs] [Haiku] #3976: Remove Menu preference In-Reply-To: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> References: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> Message-ID: <053.7a040c7dfd77c479b4a0ef1e8ae68ab6@haiku-os.org> #3976: Remove Menu preference ------------------------------+--------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Removed in r30965. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 09:47:55 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 07:47:55 -0000 Subject: [Haiku-bugs] [Haiku] #3976: Remove Menu preference In-Reply-To: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> References: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> Message-ID: <053.487060b575403136164c4b799dcfba1a@haiku-os.org> #3976: Remove Menu preference -------------------------------+-------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 09:55:13 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 07:55:13 -0000 Subject: [Haiku-bugs] [Haiku] #3985: ActivityMonitor crashes when adding view under stressed system In-Reply-To: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> References: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> Message-ID: <050.14642767061f1ef2d3855c1316c05cc6@haiku-os.org> #3985: ActivityMonitor crashes when adding view under stressed system ------------------------------------------+--------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------------+--------------------------------- Changes (by axeld): * status: new => assigned Comment: I can reproduce this problem when I run a high priority CPU hog while adding the view, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 10:11:15 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 08:11:15 -0000 Subject: [Haiku-bugs] [Haiku] #3687: app_server crash while moving Firefox between workspaces In-Reply-To: <044.1936da52413870ba2a5cbc401da9d00e@haiku-os.org> References: <044.1936da52413870ba2a5cbc401da9d00e@haiku-os.org> Message-ID: <053.15ce5b173aecefbb69e8b86ead994f66@haiku-os.org> #3687: app_server crash while moving Firefox between workspaces ---------------------------------+------------------------------------------ Reporter: anevilyak | 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 axeld): * status: new => closed * resolution: => fixed Comment: I guess we could do that - around BeGeistert, you could crash the app_server easily. While I don't remember seeing any fixes in this area, it seems the bug is no longer there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 10:21:16 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 08:21:16 -0000 Subject: [Haiku-bugs] [Haiku] #3985: ActivityMonitor crashes when adding view under stressed system In-Reply-To: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> References: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> Message-ID: <050.ab70e868ea6da41b18acf40628fc560d@haiku-os.org> #3985: ActivityMonitor crashes when adding view under stressed system -------------------------------------------+-------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------------+-------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30967. Looks like the layout engine needs a deeper look, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 10:28:03 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 05 Jun 2009 08:28:03 -0000 Subject: [Haiku-bugs] [Haiku] #3996: New ATI Mach64 compile error Message-ID: <042.1b804ad49eabe332367b8ec97f317ddc@haiku-os.org> #3996: New ATI Mach64 compile error ------------------------------+--------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I try to compile the new ATI mach64 driver with gcc4 linux crosscompiler and I get the following error: C++ generated/objects/haiku/x86/release/add-ons/accelerants/ati/mode.o src/add-ons/accelerants/ati/mode.cpp: In function 'status_t GetModeList(display_mode*)': src/add-ons/accelerants/ati/mode.cpp:351: error: 'memcpy' was not declared in this scope src/add-ons/accelerants/ati/mode.cpp: In function 'status_t GetEdidInfo(void*, size_t, uint32*)': src/add-ons/accelerants/ati/mode.cpp:447: error: 'memcpy' was not declared in this scope -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 10:44:47 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 05 Jun 2009 08:44:47 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.72a61e2228cc7a66551e437580a6ed0d@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by jahaiku): Replying to [ticket:3995 jahaiku]: > The last nightly build was on 2nd june. > > Please can you reenable the builds and > trigger a new one. > > And there are no reiserfs and ntfs on the build images. Some time ago > these fs where on the images. Can you please add them again? Perhaps this is the problem: AppendToContainerCopyFilesScript haiku.image-copy-files-dummy- optional/system/add-ons/input_server/methods AddDirectoryToContainerCopyFilesScript system/data/licenses/-/data/system/data/licenses InitScript1 generated/haiku.image-unzip-files ...skipped haiku.image for lack of haiku.image-copy-files... ...failed updating 1 target(s)... ...skipped 3 target(s)... ...updated 270 target(s)... At this "jam" or "jam haiku-image" fails for me in a gcc4 linuxcrosscompile -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 10:53:00 2009 From: trac at haiku-os.org (stippi) Date: Fri, 05 Jun 2009 08:53:00 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.7d26fca9e38991b2c3b33d1776415f26@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by stippi): Yes, it is in fact the Installer which needs to be fixed. I broke this when I changed the copy routine. When clobbering regular files, or when the directory layout does not change, overwriting worked, but I didn't test with stuff "in the way" like in these situations. I did wonder if I should completely purge the system folder, I think this would be cleaner, since it should not contain user modifications. Obviously in this mode it should not purge the home folder, but maybe "develop" is another good candidate to be purged. Maybe a requester could simply ask the user, which may also leave a better feeling about what exactly is going on when installing to an existing partition without initializing it first. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 11:06:26 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 09:06:26 -0000 Subject: [Haiku-bugs] [Haiku] #3954: mkfs reports wrong volume as initialised In-Reply-To: <041.e6505b06a9b7b0e9e4bc82430911cb7e@haiku-os.org> References: <041.e6505b06a9b7b0e9e4bc82430911cb7e@haiku-os.org> Message-ID: <050.52abc80c4f67167d26e2f4c62df861a8@haiku-os.org> #3954: mkfs reports wrong volume as initialised ----------------------------------------------+----------------------------- Reporter: idefix | 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: new => closed * resolution: => fixed Comment: Fixed in r30970. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 11:25:56 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 05 Jun 2009 09:25:56 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.bf33a688ffd3e74ade449e89af8540b4@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by jahaiku): Replying to [comment:1 jahaiku]: > Replying to [ticket:3995 jahaiku]: > > The last nightly build was on 2nd june. > > > > Please can you reenable the builds and > > trigger a new one. > > > > And there are no reiserfs and ntfs on the build images. Some time ago > > these fs where on the images. Can you please add them again? > > > Perhaps this is the problem: > > AppendToContainerCopyFilesScript haiku.image-copy-files- dummy-optional/system/add-ons/input_server/methods > > AddDirectoryToContainerCopyFilesScript system/data/licenses/-/data/system/data/licenses > > InitScript1 generated/haiku.image-unzip-files > > ...skipped haiku.image for lack of haiku.image-copy-files... > > ...failed updating 1 target(s)... > > ...skipped 3 target(s)... > > ...updated 270 target(s)... > > > At this "jam" or "jam haiku-image" fails for me in a gcc4 linuxcrosscompile Looks like the real problem is the failure of the ATI driver build (my other ticket) if compiled with "jam -q". So perhaps this ticket can be closed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 11:40:22 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 05 Jun 2009 09:40:22 -0000 Subject: [Haiku-bugs] [Haiku] #3996: New ATI Mach64 compile error In-Reply-To: <042.1b804ad49eabe332367b8ec97f317ddc@haiku-os.org> References: <042.1b804ad49eabe332367b8ec97f317ddc@haiku-os.org> Message-ID: <051.8da6c3cfdee93446f7fa36c9ede2d568@haiku-os.org> #3996: New ATI Mach64 compile error ------------------------------+--------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by jahaiku): Replying to [ticket:3996 jahaiku]: > I try to compile the new ATI mach64 driver with gcc4 linux crosscompiler and I get the following error: > > C++ generated/objects/haiku/x86/release/add-ons/accelerants/ati/mode.o > > src/add-ons/accelerants/ati/mode.cpp: In function 'status_t GetModeList(display_mode*)': > > src/add-ons/accelerants/ati/mode.cpp:351: error: 'memcpy' was not declared in this scope > > src/add-ons/accelerants/ati/mode.cpp: In function 'status_t GetEdidInfo(void*, size_t, uint32*)': > > src/add-ons/accelerants/ati/mode.cpp:447: error: 'memcpy' was not declared in this scope If I include "string.h" at the beginning of mode.cpp compilation works, but is this the correct way? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 11:50:09 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 09:50:09 -0000 Subject: [Haiku-bugs] [Haiku] #3671: mountvolume can't unmount a volume In-Reply-To: <041.92d74d583a810ec31be4dc156a254ba8@haiku-os.org> References: <041.92d74d583a810ec31be4dc156a254ba8@haiku-os.org> Message-ID: <050.bacc926067b53f45edad643b1a2b3ed5@haiku-os.org> #3671: mountvolume can't unmount a volume ----------------------------------------------+----------------------------- Reporter: idefix | 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: new => closed * resolution: => fixed Comment: Fixed in r30972. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 11:56:50 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 09:56:50 -0000 Subject: [Haiku-bugs] [Haiku] #3754: [PATCH] Done TODO In Mouse Preflet In-Reply-To: <041.c18d2b723432cfa4d17bb675c0d5301f@haiku-os.org> References: <041.c18d2b723432cfa4d17bb675c0d5301f@haiku-os.org> Message-ID: <050.673ed02ca4c6bf4d6fadeb0c591805c6@haiku-os.org> #3754: [PATCH] Done TODO In Mouse Preflet -------------------------------+-------------------------------------------- Reporter: stpere | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by axeld): Philippe, don't you want to commit this one? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 12:06:44 2009 From: trac at haiku-os.org (mt) Date: Fri, 05 Jun 2009 10:06:44 -0000 Subject: [Haiku-bugs] [Haiku] #3997: Subversion 1.6.2 from Optionalpackage fails to start Message-ID: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> #3997: Subversion 1.6.2 from Optionalpackage fails to start -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Subversion 1.6.2 from Optionalpackage fails to start. (Tested in r30957) {{{ Welcome to the Haiku shell. ~> svn runtime_loader: /boot/common/lib/libneon.so.27.1.4: Could not resolve symbol 'libiconv_set_relocation_prefix' resolve symbol "libiconv_set_relocation_prefix" returned: -2147478780 runtime_loader: /boot/common/lib/libneon.so.27.1.4: Troubles relocating: Symbol not found ~> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 12:35:16 2009 From: trac at haiku-os.org (stippi) Date: Fri, 05 Jun 2009 10:35:16 -0000 Subject: [Haiku-bugs] [Haiku] #3997: Subversion 1.6.2 from Optionalpackage fails to start In-Reply-To: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> References: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> Message-ID: <046.b0afe4d5141bc3f3cb22585bcfea1cde@haiku-os.org> #3997: Subversion 1.6.2 from Optionalpackage fails to start -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Please provide more information what versions of libiconv.so you have installed in which places. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 13:34:54 2009 From: trac at haiku-os.org (mt) Date: Fri, 05 Jun 2009 11:34:54 -0000 Subject: [Haiku-bugs] [Haiku] #3997: Subversion 1.6.2 from Optionalpackage fails to start In-Reply-To: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> References: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> Message-ID: <046.c8224e860170a283105b5ebbea402a5b@haiku-os.org> #3997: Subversion 1.6.2 from Optionalpackage fails to start -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mt): Replying to [comment:1 stippi]: > Please provide more information what versions of libiconv.so you have installed in which places. Thanks! It seems two version of libiconv installed on my system. {{{ ~> ls -l /boot/common/lib/libiconv* -rw-r--r-- 1 baron root 918 Jun 4 21:47 /boot/common/lib/libiconv.la lrwxrwxrwx 1 baron root 17 Jun 4 21:47 /boot/common/lib/libiconv.so -> libiconv.so.2.5.0 lrwxrwxrwx 1 baron root 17 Jun 4 21:47 /boot/common/lib/libiconv.so.2 -> libiconv.so.2.5.0 -rw-r--r-- 1 baron root 1124586 Jun 4 21:47 /boot/common/lib/libiconv.so.2.5.0 ~> ls -l /boot/system/lib/libiconv* -rwxr-xr-x 1 baron root 1043075 Jun 4 21:47 /boot/system/lib/libiconv.so ~> }}} I clean build r30957 gcc4/gcc2 hybrid mode with Optinalpackage (Development, subversion etc..). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 14:14:00 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 05 Jun 2009 12:14:00 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.d2d8eb655b88407fe1085bac2be123e0@haiku-os.org> #3978: Update install from CD fails at r30914 ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: x86 Blocking: 3994 | ------------------------------------+--------------------------------------- Comment(by bonefish): Replying to stippi's comment in #3978. {{{system/}}} is definitely safe to be removed completely, since the user has no business changing anything there. And save for the current ABI link I also don't see a reason why anything in {{{develop/}}} would be changed either. For everything else things are somewhat complicated. One can't really decide on a per-file basis. E.g. if an optional package was updated, we shouldn't leave over files from the older version just because they don't exit in the new one. This is really a package management issue and I don't suppose we can solve it before actually implementing a package management solution. For the time being the installer could generate an installation log/DB listing all files/directories/symlinks it has created (with checksums for file contents and attributes). On the next run it would first remove all untouched objects before starting the installation, maybe also offering a dialog where the user can choose which of the changed ones shall be overwritten, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 14:33:39 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 12:33:39 -0000 Subject: [Haiku-bugs] [Haiku] #3996: New ATI Mach64 compile error In-Reply-To: <042.1b804ad49eabe332367b8ec97f317ddc@haiku-os.org> References: <042.1b804ad49eabe332367b8ec97f317ddc@haiku-os.org> Message-ID: <051.5a45eb87083872d15e7d852d1d9c1627@haiku-os.org> #3996: New ATI Mach64 compile error -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Correct indeed. Fixed in r30973. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 14:53:18 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 05 Jun 2009 12:53:18 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.1f2832a3b453d0534a5c28d617bd12d5@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by mmadia): ''And there are no reiserfs and ntfs on the build images. Some time ago these fs where on the images. Can you please add them again?'' The images provided by Haiku should not contain these drivers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 15:15:13 2009 From: trac at haiku-os.org (stippi) Date: Fri, 05 Jun 2009 13:15:13 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.b796b470fa4322c87a9b4613e201e0ef@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by stippi): Really? I thought those were part of the image since a long time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 15:16:40 2009 From: trac at haiku-os.org (dlmcpaul) Date: Fri, 05 Jun 2009 13:16:40 -0000 Subject: [Haiku-bugs] [Haiku] #3998: Failure to boot if vitrual memory set to more than available space Message-ID: <043.8158645f35e22bf69b3b46fa276ea7a9@haiku-os.org> #3998: Failure to boot if vitrual memory set to more than available space ---------------------------+------------------------------------------------ Reporter: dlmcpaul | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ If the virtual memory setting is greater than the amount of space available on disk then haiku stops booting. If there is not enough space for the swap file then it should be reduced or virtual memory turned off. Failing to boot should not be an option. How to reproduce: Increase Virtual Memory to > available disk space and reboot. experience behaviour: Haiku fails to boot expected behaviour: Haiku boots with reduced swap space. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 15:19:48 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 13:19:48 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.85baa4b3869061eed1548d91536b84b1@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by anevilyak): Replying to [comment:4 stippi]: > Really? I thought those were part of the image since a long time. If they were, then that was a very bad mistake, since both of those filesystem drivers are GPLed, and as such we cannot enable them in a default build we distribute. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 15:31:37 2009 From: trac at haiku-os.org (bga) Date: Fri, 05 Jun 2009 13:31:37 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.50defff0fe129f9ec03389ed462ba7de@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by bga): I don't think this is correct. First because the sources are available to anyone. Second because our license is GPL compatible anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 15:33:59 2009 From: trac at haiku-os.org (bga) Date: Fri, 05 Jun 2009 13:33:59 -0000 Subject: [Haiku-bugs] [Haiku] #3995: Nightly builds not working In-Reply-To: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> References: <042.598e0ea2c1ea0af338acf48ff283ff37@haiku-os.org> Message-ID: <051.cd157c0a81e6129d28b5f5392932b3d1@haiku-os.org> #3995: Nightly builds not working ---------------------+------------------------------------------------------ Reporter: jahaiku | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by bga): And third, even if the above was not true, Haiku does not depend on any of those to build/run. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 16:21:19 2009 From: trac at haiku-os.org (axeld) Date: Fri, 05 Jun 2009 14:21:19 -0000 Subject: [Haiku-bugs] [Haiku] #3998: Failure to boot if vitrual memory set to more than available space In-Reply-To: <043.8158645f35e22bf69b3b46fa276ea7a9@haiku-os.org> References: <043.8158645f35e22bf69b3b46fa276ea7a9@haiku-os.org> Message-ID: <052.e228ed7b813a8c614f473f7f116d3c5d@haiku-os.org> #3998: Failure to boot if vitrual memory set to more than available space ---------------------------+------------------------------------------------ Reporter: dlmcpaul | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by axeld): I can't reproduce this over here. Booting always works fine. Can you please provide syslog from a working run, and from one that doesn't boot? (a photo of the last two pages off on screen debug output would be great from the latter) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 16:53:23 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 05 Jun 2009 14:53:23 -0000 Subject: [Haiku-bugs] [Haiku] #2696: unimplemented functions In-Reply-To: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> References: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> Message-ID: <051.aa47e5249ac9e91c69b14e70ed3bf49e@haiku-os.org> #2696: unimplemented functions -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: 2564 | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): Replying to [comment:5 scottmc]: > This one is blocking [http://ports.haiku-files.org/ticket/70 HaikuPorts Ticket #70], which affects building the CVS version of CVS. So until the libio.h functions are implemented we won't have a Haiku native CVS. Good news is that the BeOS CVS has been working ok as far as I can tell. HaikuPorts ticket 70 has been closed as fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 17:29:03 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 05 Jun 2009 15:29:03 -0000 Subject: [Haiku-bugs] [Haiku] #3997: Subversion 1.6.2 from Optionalpackage fails to start In-Reply-To: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> References: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> Message-ID: <046.795123895cec1d025afedb9e056dbe4f@haiku-os.org> #3997: Subversion 1.6.2 from Optionalpackage fails to start -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by bonefish): The problem does indeed occur on the gcc4/gcc2 hybrid build only. The runtime loader does search the /system/lib/gcc2 directory before /boot/common/lib (since svn is a gcc2 build) and therefore finds the wrong libiconv.so (version 1.12 instead of 1.13). Creating a /boot/common/lib/gcc2/ and linking the ../libiconv.so there, solves the issue. I see two problems: - libneon's dependency is "libiconv.so", although it correctly should be "libiconv.so.2". At least that's the soname of the correct one. - The libiconv.so generated by the build system is not properly versioned. Though that might break things again. I don't get libiconv's naming scheme -- supposedly 1.13 is only a minor version update, so it would be "libiconv.so.2", too. Besides fixing those two issues, I guess OptionalPackages has to add symlinks as the one above for hybrid builds. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 21:47:16 2009 From: trac at haiku-os.org (meianoite) Date: Fri, 05 Jun 2009 19:47:16 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as uhci driver tries to take ownership Message-ID: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> #3999: Boot hangs (with a twist) as uhci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When I boot Haiku, the bootloader hangs on the third icon indefinitely. The first time I saw this I intended to reboot and enable the onscreen debug console, but for some reason I hit the power button instead of the reset one. And the boot continued!! Puzzled, I rebooted, enabled the debug console, hit "p" to disable paging, and arrived at the text shown on the two attached pictures. "before" shows the kernel hung at the "usb ohci -1: smm is in control of the host controller" message. "after" shows what happens immediately after I hit the power button. Syslog with timestamps is attached as well. But it's from a different session, as when I boot with onscreen debugging Haiku will hang on a black screen at the very end of the boot instead of going to the desktop (and that I tried using a FAT-formatted USB stick, but it KDL'd when I copied the syslog to it). Notice that for some unknown (to me) reason, the timestamps are within the same second, instead of being apart by the several minutes I waited between taking both screenshots (and hitting the power button, consequently). For example, JPEG EXIF data shows the "before" picture was taken at 16h18m44s, and the "after" picture at 16h21m18s. I guess what is timestamped is the buffer, and not the message itself. Also attached is the output from dmesg from a verbose boot of FreeBSD on the same machine. Hope it helps. I can of course change any compilation options to help debug this. The image is build on FreeBSD, but I've built Haiku on Haiku proper (yay!) and the same symptom shows. Makes no difference if I'm booting from a USB stick or from the hard drive (syslog is from a HD boot). The motherboard BIOS is flashed to the latest version found on Asus' site. I have *no* idea why ACPI is showing _ASUS_ **Notebook** as the vendor identifier, as this is straight from Asus, flashed scratch with bootblock rewriting, ESCD cleared, CMOS cleared and everything I could think of to make it as pristine as possible, and not any modded/hacked BIOS. I tried both with USB peripherals attached or detached; made no difference. Also tried inserting and removing peripherals while the boot is hung, no difference as well. There's one peripheral I couldn't detach, which is the RTL8187 WLAN interface that's build in on the motherboard; it connects straight to a special, internal USB header. I hope it's not the culprit, but still, only Haiku refuses to boot/requires hitting the power button in the middle of the boot process to continue loading, so... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 22:42:13 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 05 Jun 2009 20:42:13 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.37a0d150282f8741accd728372ffaf14@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by haiqu): Stippi, Asking the user is the option I'd prefer. Especially since purging the develop folder would clobber the GCC compiler (which I refuse to relocate, there wasn't any point to that) and my Pascal compiler. But I disagree that it was a fault with the installer. The person who made changes that required directories to be removed didn't liaise with you about it before blundering ahead. On more than one occasion. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 22:57:15 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 05 Jun 2009 20:57:15 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.02aa806faf319e58fba58e1075549e3f@haiku-os.org> #3978: Update install from CD fails at r30914 ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: x86 Blocking: 3994 | ------------------------------------+--------------------------------------- Comment(by haiqu): An install system that takes control of changes to whole second-level directories isn't something I'd want to use. I agree (and current policy confirms) that changes to /boot/system by the user shouldn't be preserved. However /boot/develop has traditionally been where tools live and messing with that may have consequences. As an example I have BeIDE in there, also Free Pascal is now in /boot/develop/tools A more fine-grained approach would be preferred. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 23:00:24 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 21:00:24 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.aa843357cc763d99f7e269ea541fe5d2@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by anevilyak): Replying to [comment:5 haiqu]: > But I disagree that it was a fault with the installer. The person who made changes that required directories to be removed didn't liaise with you about it before blundering ahead. On more than one occasion. > That might actually be a concern when we have releases to install between. Frankly I doubt anyone other than you cares if the installer doesn't gracefully handle going from one bleeding edge SVN revision to another. Going from Haiku 1.0 to Haiku 1.1 is however a different story. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 23:10:40 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 05 Jun 2009 21:10:40 -0000 Subject: [Haiku-bugs] [Haiku] #4000: Haiku fails to compile buildtools for other GCC Message-ID: <041.4a83adb6e944cdbefb6bd7c5133eaced@haiku-os.org> #4000: Haiku fails to compile buildtools for other GCC --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- r30928. Tried building x86gcc4 from within x86gcc2. {{{ /builder/haiku> svn update buildtools haiku At revision 30976. Updated to revision 30976. /generated/x86gcc4-crossbuilt> ../../builder/haiku/haiku/configure --build-cross-tools-gcc4 x86 ../../builder/haiku/buildtools/ }}} Full output is included in the attachment. Here's some of the more obvious errors/issues: {{{ checking the maximum length of command line arguments... expr: syntax error expr: syntax error }}} {{{ gcc -c -DHAVE_CONFIG_H -O2 -I. -I/builder/haiku/buildtools/binutils/libiberty/../include -W -Wall -Wwrite-strings -Wstrict-prototypes -pedantic /builder/haiku/buildtools/binutils/libiberty/pex-unix.c -o pex-unix.o /builder/haiku/buildtools/binutils/libiberty/pex-unix.c: In function `pex_child_error': /builder/haiku/buildtools/binutils/libiberty/pex-unix.c:352: warning: `noreturn' function does return }}} {{{ /bin/sh ./libtool --tag=CC --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -O2 -o libbfd.la -rpath /generated/x86gcc4-crossbuilt/cross-tools/lib -release `cat libtool- soversion` archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo opncls.lo reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo compress.lo `cat ofiles` -lz ./libtool: line 7380: test: : integer expression expected ./libtool: line 7380: test: : integer expression expected libtool: link: using piecewise archive linking... ./libtool: line 7401: test: : integer expression expected }}} {{{ make[3]: Leaving directory `/generated/x86gcc4-crossbuilt/cross-tools- build/binutils/libiberty/testsuite' /bin/sh /builder/haiku/buildtools/binutils/libiberty/../mkinstalldirs /generated/x86gcc4-crossbuilt/cross-tools/lib/`gcc -O2 -print-multi-os- directory` gcc: unrecognized option `-print-multi-os-directory' gcc: No input files /bin/install -c -m 644 ./libiberty.a /generated/x86gcc4-crossbuilt/cross- tools/lib/`gcc -O2 -print-multi-os-directory`/./libiberty.an gcc: unrecognized option `-print-multi-os-directory' gcc: No input files ( cd /generated/x86gcc4-crossbuilt/cross-tools/lib/`gcc -O2 -print-multi- os-directory` ; chmod 644 ./libiberty.an ;ranlib ./libiberty.an ) gcc: unrecognized option `-print-multi-os-directory' gcc: No input files mv -f /generated/x86gcc4-crossbuilt/cross-tools/lib/`gcc -O2 -print-multi- os-directory`/./libiberty.an /generated/x86gcc4-crossbuilt/cross- tools/lib/`gcc -O2 -print-multi-os-directory`/./libiberty.a gcc: unrecognized option `-print-multi-os-directory' gcc: No input files gcc: unrecognized option `-print-multi-os-directory' gcc: No input files }}} {{{ checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 *** This configuration is not supported in the following subdirectories: target-libmudflap target-libgomp target-libiberty (Any other directories should still work fine.) *** --with-headers is only supported when cross compiling /generated/x86gcc4-crossbuilt> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 23:26:30 2009 From: trac at haiku-os.org (stpere) Date: Fri, 05 Jun 2009 21:26:30 -0000 Subject: [Haiku-bugs] [Haiku] #3754: [PATCH] Done TODO In Mouse Preflet In-Reply-To: <041.c18d2b723432cfa4d17bb675c0d5301f@haiku-os.org> References: <041.c18d2b723432cfa4d17bb675c0d5301f@haiku-os.org> Message-ID: <050.8c8b06df87cf28194ac0afc6e56949c0@haiku-os.org> #3754: [PATCH] Done TODO In Mouse Preflet --------------------------------+------------------------------------------- Reporter: stpere | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by stpere): * status: new => closed * resolution: => fixed Comment: Commited in r30977! Thanks for the reminder. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 5 23:40:25 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 05 Jun 2009 21:40:25 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.d5f68f5c3598f452c378883cfef09c51@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): Spent some time yesterday checking some values for the partition size in the 4th partition's FAT32 Volume Boot Record. This theoretically lives at offset 0x13 for any drive with less than 64k sectors and at 0x20 for larger drives, although in practice is always written to 0x20 for FAT32 partitons. The values match those in the MBR which leads me to the conclusion that the Installer is probably accessing a different struct for the FAT32 records than the one used elsewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 00:45:28 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 05 Jun 2009 22:45:28 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.959b748c2477f04083e3a0618432f380@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by haiqu): You're quite right, of course. Je suis un vieux b?tard d?sagr?able. However, it may surprise you to review just how close we are to that release, and it behooves the developers to get into the right mindset earlier rather than later. The situation will become intolerable when there are more than 100 Haiku users. And I do think that might actually happen if we had less broken versions. ;^] Robert -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 01:04:17 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 05 Jun 2009 23:04:17 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.3336c59d188b8a9b21d76943d5b30774@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by anevilyak): I'm not very surprised at all, I've been running it more or less exclusively on one of my boxes for close to a year now. Nevertheless, my point about it being unrealistic to expect the installer to cope with upgrading between any two random SVN revisions stands, and I might also note, my experiences with beta testing OSes from various commercial companies indicate no one else bothers to support this either. At least every time I've been in an OS beta testing program it was quite explicitly suggested to reformat between builds rather than attempting the usual setup upgrade. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 01:21:19 2009 From: trac at haiku-os.org (Pete) Date: Fri, 05 Jun 2009 23:21:19 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive Message-ID: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ On a ThinkPad 570E laptop running r30629, trying to play an MP3 through MediaPlayer produces no sound (though it appears to play and the VU meter is active). The Deskbar Volume Control is entirely red, and the knob remains at '38dB' (it can be moved, but always returns to that value). I've tried reloading OpenSound -- even recompiling from current sources -- with no effect. Under an earlier revision (29462) sound works... sometimes. (I understand this is a known bug, though I can't find it in the Tracker.) The Volume slider works in this revision, though. The sound chip appears to be a Crystal CS4614, reported (in Media Preferences) as "CS4280" in the working version, and "CS461x" in the one that doesn't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 03:16:02 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 06 Jun 2009 01:16:02 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as uhci driver tries to take ownership In-Reply-To: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> References: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> Message-ID: <053.bf74a53e698e8da641000ec3741f61bd@haiku-os.org> #3999: Boot hangs (with a twist) as uhci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mmlr): It's not entirely surprising actually. It's not a problem of UHCI though, as you don't have UHCI controllers at all ;-) I think it's also not a problem in OHCI though. It cannot really do other than it does. What I'd find more likely is that it's because of ACPI enabling/expecting IO-APIC interrupt routing while we don't do that yet. In that case generating an interrupt (by hitting the power-button ACPI is signaled) it could unjam whatever loop it was in, waiting for interrupts. Does it work when you have ACPI disabled? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 03:16:31 2009 From: trac at haiku-os.org (agildehaus) Date: Sat, 06 Jun 2009 01:16:31 -0000 Subject: [Haiku-bugs] [Haiku] #1876: Media preferences, clicking on some checkboxes switches back to first tab In-Reply-To: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> References: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> Message-ID: <050.f0c50449d80c689d550bc5444f80dedd@haiku-os.org> #1876: Media preferences, clicking on some checkboxes switches back to first tab ---------------------------+------------------------------------------------ Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by agildehaus): This is an issue I would also like to see addressed. Completely confused me when I first came across it. There's really no reason for the tab switch. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 03:21:04 2009 From: trac at haiku-os.org (agildehaus) Date: Sat, 06 Jun 2009 01:21:04 -0000 Subject: [Haiku-bugs] [Haiku] #4002: volume control replicant does not function after reboot Message-ID: <045.cfae979f67b38eb1f5b7d326d6eeeca5@haiku-os.org> #4002: volume control replicant does not function after reboot ----------------------------+----------------------------------------------- Reporter: agildehaus | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- A working volume control replicant placed on the desktop does not function after a reboot; all controls are disabled and the text "No Mixer" is displayed. I might tackle this one myself as I want to start contributing patches, but I'd welcome someone to beat me to it :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 03:47:26 2009 From: trac at haiku-os.org (jprostko) Date: Sat, 06 Jun 2009 01:47:26 -0000 Subject: [Haiku-bugs] [Haiku] #4003: GCC4 build break when building at -O1 Message-ID: <043.d20de27aebeea6c5644ffd33adad5e37@haiku-os.org> #4003: GCC4 build break when building at -O1 --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- With trying to build Haiku with -O1 (set via BuildSetup) with GCC 4.3.3, the Bluetooth kit fails to compile with the following error: C++ /boot/home/haiku/trunk/generated- gcc-4.3.3/objects/haiku/x86/release/kits/bluetooth/ConnectionIncoming.o Link /boot/home/haiku/trunk/generated- gcc-4.3.3/objects/haiku/x86/release/kits/bluetooth/libbluetooth.so /boot/home/haiku/trunk/generated- gcc-4.3.3/objects/haiku/x86/release/kits/bluetooth/ConnectionIncoming.o: In function `__static_initialization_and_destruction_0(int, int)': ConnectionIncoming.cpp:(.text+0x3c): undefined reference to `std::ios_base::Init::Init()' ConnectionIncoming.cpp:(.text+0x5c): undefined reference to `std::ios_base::Init::~Init()' collect2: ld returned 1 exit status This is remedied by adding a $(TARGET_LIBSTDC++) to the src/kits/bluetooth/Jamfile. I initially found this out, as the native Haiku GCC 4.4 I am working with encountered the same problem, but at -O2. The GCC 4.4 port encounters similar issues at -O1 in two more files. These are src/bin/locale/Jamfile and src/apps/cdplayer/Jamfile . They both need $(TARGET_LIBSTDC++) added to them as well. Those could probably be ignored for now, but there's no harm fixing those files now as far as I can tell. Actually, on the haiku-commits' list, there was an issue raised about r30573 and there needing to be a $(TARGET_LIBSTDC++) added to the locale Jamfile. I am pretty sure this wasn't a mere coincidence to the break I noted on my 4.4 Haiku build. By the way, GCC 2.95.3 has none of these issues, as I tested it as well. Also, if it was relevant, the last time I attempted this was at r30953 of Haiku. Attached is one file that addresses all issues. I realize we may not want to touch the locale and cdplayer jamfiles until we actually use 4.4 officially (I'll see about getting that in the tree when 4.4.1 comes out later this month, if everyone's cool with that), so proceed as you see fit. It'd be good to at least get the bluetooth Jamfile fix applied though, as it is relevant to GCC 4.3.3. By the way, I saw quite a few Jamfiles in the tree that exceed 80 characters across, but I edited these to make sure they are only 80 across. I'm not sure if the coding guidelines apply to the Jamfiles or not, but I assumed they did. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 03:56:22 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 06 Jun 2009 01:56:22 -0000 Subject: [Haiku-bugs] [Haiku] #1876: Media preferences, clicking on some checkboxes switches back to first tab In-Reply-To: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> References: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> Message-ID: <050.3993c4595e2faa029577b88998485a3f@haiku-os.org> #1876: Media preferences, clicking on some checkboxes switches back to first tab ---------------------------+------------------------------------------------ Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): The problem is with the way that it's done currently, the mixer generates a new parameter web when its settings are changed, since as mentioned previously some of those settings cause more options to appear/disappear. As a consequence when the new parameter web is put in place, the old is in effect destroyed and the new put in place. In other words, the reason you see a tab switch is because the TabView/Settings panel you clicked the checkbox in no longer exists, a freshly created one was put in place which knows nothing about where you were previously. Right now I see no easy way to change that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 04:43:56 2009 From: trac at haiku-os.org (Pete) Date: Sat, 06 Jun 2009 02:43:56 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.b44589462b14fb05bfa083a9ab572930@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by Pete): Addendum: Realizing that there's an 'osstest' app, I tried that (after killing media_addon_server), and it generates good sound. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 05:32:32 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 06 Jun 2009 03:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.dbebc2678b779a128bfae8a9d746b624@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by haiqu): Perhaps when we - like Microsoft - have 10 million beta testers, we can afford to annoy a few of them. OTOH Haiku needs all the users it can get. My fondest memory of beta testing was on Netscape 2.x where every comment was regarded as valuable input. As for reformatting between installs, that's a bit extreme. Unless you have to kill off a registry, of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 05:48:29 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 06 Jun 2009 03:48:29 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.7bedb46fdde43ec1cd95b20d3816e376@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by mmadia): Rob, you need to re-acquaint yourself with our [http://dev.haiku- os.org/wiki/BugTrackerEtiquette BugTrackerEtiquette] You have repeatedly broken numerous of the rules put forth. From re- opening tickets that were marked closed-->invalid, only to have them re- closed. To personally insulting contributors to the project. To insisting the developers are responsible for user errors. To adding comments that have little or nothing to do with the ticket. This ticket was marked Closed-->duplicate over a day ago and you still feel a need to comment on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 06:52:31 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 06 Jun 2009 04:52:31 -0000 Subject: [Haiku-bugs] [Haiku] #3994: Installation fails at r30960 In-Reply-To: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> References: <040.1c6a4cd52fe98394dea03ce32e556002@haiku-os.org> Message-ID: <049.f39ca9fbb774388ea0c3689a990fbe38@haiku-os.org> #3994: Installation fails at r30960 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: duplicate | Blockedby: 3978 Platform: x86 | Blocking: -------------------------------------+-------------------------------------- Comment(by haiqu): And you already know what I think of *your* opinion. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 08:11:51 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 06 Jun 2009 06:11:51 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as ohci driver tries to take ownership (was: Boot hangs (with a twist) as uhci driver tries to take ownership) In-Reply-To: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> References: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> Message-ID: <053.1cc3459dfaee3a24a82f1f24430d3bff@haiku-os.org> #3999: Boot hangs (with a twist) as ohci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 08:32:42 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 06 Jun 2009 06:32:42 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as ohci driver tries to take ownership In-Reply-To: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> References: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> Message-ID: <053.375f8a6d185dc82e57637906e99445b9@haiku-os.org> #3999: Boot hangs (with a twist) as ohci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by meianoite): Doh, sorry, sure it was "ohci" and not "uhci". Changed the title of the ticket accordingly. Rebooting with ACPI disabled did nothing. Removing the "ohci" driver did allow the boot to continue without requiring me to hit the power button, though! But at the end of the boot I couldn't use neither keyboards nor mice, USB or PS/2. Another thing that doesn't work is a USB mouse that I have here. Really strange. Attached now are syslogs of booting without the "ohci" driver and booting back with the "ohci" driver in place and with the USB mouse attached, but unable to be used. Might shed a light on the cause of those issues. Of course, I'm still available for compiling with any debugging options you'd like me to. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 08:52:12 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 06 Jun 2009 06:52:12 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as ohci driver tries to take ownership In-Reply-To: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> References: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> Message-ID: <053.7fc7ec07b105be8937bca53eb4e4eb63@haiku-os.org> #3999: Boot hangs (with a twist) as ohci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by meianoite): By the way, this is what FreeBSD has to say when I plug the USB mouse: ugen0.3: at usbus0 ums0: on usbus0 ums0: 5 buttons and [XYZ] coordinates ID=17 An educated guess is that the relevant line on the Haiku syslog (the one I just attached) regarding this mouse is: 2009-06-06 06:33:12 KERN: usb_hid: unsupported device type 0x01090c05 In this case, it's just usb_hid not getting the device type (doh), and nothing related to the problem at hand. Still, it would be nice to support this mouse :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 11:04:06 2009 From: trac at haiku-os.org (axeld) Date: Sat, 06 Jun 2009 09:04:06 -0000 Subject: [Haiku-bugs] [Haiku] #1876: Media preferences, clicking on some checkboxes switches back to first tab In-Reply-To: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> References: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> Message-ID: <050.085bc191b243796d805ecfb7f4d48745@haiku-os.org> #1876: Media preferences, clicking on some checkboxes switches back to first tab ---------------------------+------------------------------------------------ Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by axeld): A BParameterGroup has a name, and the panel could just remember the current one, and try to make it active again after changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 11:45:41 2009 From: trac at haiku-os.org (rossi) Date: Sat, 06 Jun 2009 09:45:41 -0000 Subject: [Haiku-bugs] [Haiku] #3397: Screen: cannot set screen modes anymore In-Reply-To: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> References: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> Message-ID: <049.af866183b55b77d6d936ef653b850a9b@haiku-os.org> #3397: Screen: cannot set screen modes anymore --------------------------------------------+------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------------+------------------------------- Comment(by rossi): I don't know what changed, but I forgot this bug and just used screen preferences to set this resolution after a week of working on the built-in laptop display and it works again. therefore I cannot say, which revision fixed this bug, but it seems fixed latest in 30935 ;-) Should be closed as fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 11:53:45 2009 From: trac at haiku-os.org (stippi) Date: Sat, 06 Jun 2009 09:53:45 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.323aee73ba72adccfe8c9930931e2acd@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by stippi): So what happens if you delete {{{/boot/system/add- ons/kernel/drivers/bin/hda}}}? Does OpenSound work then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 11:58:53 2009 From: trac at haiku-os.org (stippi) Date: Sat, 06 Jun 2009 09:58:53 -0000 Subject: [Haiku-bugs] [Haiku] #4002: volume control replicant does not function after reboot In-Reply-To: <045.cfae979f67b38eb1f5b7d326d6eeeca5@haiku-os.org> References: <045.cfae979f67b38eb1f5b7d326d6eeeca5@haiku-os.org> Message-ID: <054.56a3cfb09d6e4c497c20524e60b8e964@haiku-os.org> #4002: volume control replicant does not function after reboot ----------------------------+----------------------------------------------- Reporter: agildehaus | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by stippi): If you restart Tracker (open a Terminal, type '''hey Tracker quit''', type '''/system/Tracker &'''), does the replicant suddenly work? If so it sounds like the timing between launching Tracker and media_server during boot could be the problem. Then you just need to add "polling" to the replicant. In another words, it would recheck the availability of the BMediaRoster from time to time until it is there. You could do this for example with a BMessageRunner that sends a message about every 2 seconds which causes the replicant to re-run the code that connects to the media_server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 12:35:44 2009 From: trac at haiku-os.org (stippi) Date: Sat, 06 Jun 2009 10:35:44 -0000 Subject: [Haiku-bugs] [Haiku] #4003: GCC4 build break when building at -O1 In-Reply-To: <043.d20de27aebeea6c5644ffd33adad5e37@haiku-os.org> References: <043.d20de27aebeea6c5644ffd33adad5e37@haiku-os.org> Message-ID: <052.8fc5b0e44401ee6036a8a97c998863e3@haiku-os.org> #4003: GCC4 build break when building at -O1 ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Applied in r30979. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 12:36:54 2009 From: trac at haiku-os.org (stippi) Date: Sat, 06 Jun 2009 10:36:54 -0000 Subject: [Haiku-bugs] [Haiku] #3397: Screen: cannot set screen modes anymore In-Reply-To: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> References: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> Message-ID: <049.c86443efa9e722757a052523ea7242de@haiku-os.org> #3397: Screen: cannot set screen modes anymore --------------------------------------------+------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------------+------------------------------- Comment(by stippi): This may still be a problem, depending on some factors which have not yet revealed themselves... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 12:38:28 2009 From: trac at haiku-os.org (stippi) Date: Sat, 06 Jun 2009 10:38:28 -0000 Subject: [Haiku-bugs] [Haiku] #4003: GCC4 build break when building at -O1 In-Reply-To: <043.d20de27aebeea6c5644ffd33adad5e37@haiku-os.org> References: <043.d20de27aebeea6c5644ffd33adad5e37@haiku-os.org> Message-ID: <052.78c0cf9fe9b367305eec616ae68a11b2@haiku-os.org> #4003: GCC4 build break when building at -O1 ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Forgot to mention... yes, it's definitely correct to fix Jamfiles for the chars/line limit, too! Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 12:42:37 2009 From: trac at haiku-os.org (rossi) Date: Sat, 06 Jun 2009 10:42:37 -0000 Subject: [Haiku-bugs] [Haiku] #3397: Screen: cannot set screen modes anymore In-Reply-To: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> References: <040.97ebe593be723fffddb20fb2c6dadd64@haiku-os.org> Message-ID: <049.a14e873b88d7de502059b87aeff18a9b@haiku-os.org> #3397: Screen: cannot set screen modes anymore --------------------------------------------+------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------------+------------------------------- Comment(by rossi): Should those some factors reveal themselves, I'll give those factors the honor of loud crying in another comment to this ticket ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 14:39:05 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 06 Jun 2009 12:39:05 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.96e3b5004b0b99a13565a37a2c2b27d4@haiku-os.org> #2643: Black screen when DVI connected -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) Comment: Hi Rudolf, Unfortunately for some reason I did not receive a mail notification for your comment, so I apologize for my late reply as well. I had noticed your recent commits and re-tried a couple of times, including DVI connected before cold booting, then building Haiku under Linux and rebooting into Haiku, without luck. I had this line in my {{{UserBuildConfig}}}: {{{ AddFilesToHaikuImage home config settings kernel drivers : $(HAIKU_TOP)/src/add-ons/kernel/drivers/graphics/nvidia/nvidia.settings ; }}} Your settings file was unmodified - not sure whether that "programs the panel" or not. VGA-only does work fine with that file in place. My GeForce FX 5700LE (Leadtek LR2984) card has three different connectors: VGA, S-VHS and DVI. So I cannot connect the non-working DVI connector to the VGA connector or vice versa, they were always identical. (Connecting the DVI monitor via VGA connector did work, the monitor also works on other machines via DVI.) The DVI panel, when connected, was powered but black whereas the VGA screen went black and powered off after a while. That is, after the rocket icon lighted up. Before, they showed the same image. This is reproducible, VGA never worked when DVI is connected. Where do I get a vesa settings file, where do I put it? Thanks for investigating, Andreas -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 16:13:24 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 06 Jun 2009 14:13:24 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.afc427a001a79cb2d303cdc25806b3fb@haiku-os.org> #2643: Black screen when DVI connected -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): I just tried with this patch {{{ diff --git a/src/add-ons/kernel/drivers/graphics/nvidia/nvidia.settings b/src/add-ons/kernel/drivers/graphics/nvidia/nvidia.settings index 8474fd7..35482a2 100644 --- a/src/add-ons/kernel/drivers/graphics/nvidia/nvidia.settings +++ b/src/add-ons/kernel/drivers/graphics/nvidia/nvidia.settings @@ -26,7 +26,7 @@ block_acc false # if true disables the acceleration engine # WARNING: tweak alert! modify stuff below on your own risk... unhide_fw false # if true 'unhide' cards AGP fastwrite support on cards that hide it -pgm_panel false # if false don't program DVI and laptop panel pixelclocks (refreshrates) +pgm_panel true # if false don't program DVI and laptop panel pixelclocks (refreshrates) vga_on_tv false # if true enables VGA output on the head outputting to TV #gpu_clk 150 # in Mhz, (tries to) override default GPU clockspeed (be carefull!!!) #ram_clk 150 # in Mhz, (tries to) override default cardRAM clockspeed (be carefull!!!) }}} and it did not make a change. I found an Apple DVI-to-VGA converter and was able to boot Haiku with two VGA screens connected this way. The desktop image was displayed on the original VGA screen, the other one went black, with no option to mirror or extend the desktop. Am I correct to assume that it's simply not yet implemented in Haiku? If I connect via the DVI-to-VGA adapter only, the desktop is displayed correctly on that screen. So no issue with the connector apparently, more a DVI-specific issue here, at r30978. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 17:02:52 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 06 Jun 2009 15:02:52 -0000 Subject: [Haiku-bugs] [Haiku] #1876: Media preferences, clicking on some checkboxes switches back to first tab In-Reply-To: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> References: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> Message-ID: <050.9e2e616c9163c2251728a3ef102eb1bc@haiku-os.org> #1876: Media preferences, clicking on some checkboxes switches back to first tab ---------------------------+------------------------------------------------ Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): I thought I posted an update to this last night, but apparently not: the real problem is that some of the parameter change notifications from the media server aren't being reacted to appropriately. From a quick glance I assume this needs to be happening in BMediaTheme but I may be wrong. The current mechanism of forcing the whole web to be rebuilt is an intentional hack to work around that (cf. src/add-ons/media/media- addons/mixer/AudioMixer.cpp line 1642). Your way would work, certainly, but it still leaves a hack in place that hides the real problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 18:27:36 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sat, 06 Jun 2009 16:27:36 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 Message-ID: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ I have Intel DG33FB motherboard with Core2 Duo E6750 CPU and 2GB of RAM. Chipset is G33 Express with ICH9DH south bridge. The machine has four hard drives: 2 IDE drives on single IDE channel and 2 SATA drives. I've installed Haiku r30980 on the first primary partition of the slave IDE drive and on the first primary partition of the second SATA drive (SATA port 2). In both cases Haiku hangs at the 5th icon when SATA controller is in AHCI mode, and at the 4th icon when SATA is configured as IDE. Playing with safe mode options gave nothing. Serial debug logs for each 4 cases are attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 18:52:46 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 06 Jun 2009 16:52:46 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.7535ec2aaf59f9c0041c1a8fe8853497@haiku-os.org> #2643: Black screen when DVI connected -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): When I connected the other monitor via VGA it runs at 1024x768 while its native resolution is 1280x1024. If on first boot with that monitor I select fail-safe video mode, in Screen preferences set the resolution to 1280x1024 and reboot, then suddenly the DVI screen works as expected! So the issue is the combination of DVI and a non-native resolution. Unfortunately I don't have a very usable workaround yet... I tried creating a simple {{{/boot/home/config/settings/kernel/drivers/vesa}}} file {{{ mode 1280 1024 32 }}} to set this resolution for each build, but it doesn't have the same effect as manually setting the resolution in VESA mode. Neither has unzipping the {{{/boot/home/config/Screen_data}}} file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:07:05 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 06 Jun 2009 17:07:05 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.35d5dd26144b018d9a04bbfc8c3f2a40@haiku-os.org> #2643: Black screen when DVI connected -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): The key to making it work was (unzipping) the {{{/boot/home/config/settings/system/app_server/workspaces}}} file! It now shows the correct resolution on first boot with DVI. I'll see which attempts from the above ({{{nvidia.settings}}}, {{{vesa}}}, {{{Screen_data}}}) I can drop while still making it work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:12:53 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 17:12:53 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 In-Reply-To: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> References: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> Message-ID: <057.ed77e7c06592ce47ade0c6132b312e3f@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by umccullough): FWIW, Standard Haiku builds don't boot properly on my G33-based ICH9 machine either. When I switch the bus_manager from "ide" to "ata", however, it does boot fine (I don't have to fiddle with any BIOS modes either). If you're building your own images, try adding this to your UserBuildConfig: HAIKU_ATA_STACK = 1 ; mind the spacing, that's important. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:17:32 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 17:17:32 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 In-Reply-To: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> References: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> Message-ID: <057.498203b6019e7da8ab417acc3eedd951@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by umccullough): I should also note that in my case, I tend to get some long timeouts as Haiku is enumerating the partitions on my disk (sometimes a couple minutes), so if you have a lot of drives/partitions, you might give it some extra time. In my case, I believe it's related to a known-issue with Seagate/Maxtor drives like mine, and the disk hangs at certain times no matter what OS I use... I'm about to throw it in the trash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:25:04 2009 From: trac at haiku-os.org (meanwhile) Date: Sat, 06 Jun 2009 17:25:04 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.2029f74003a913bcce746c6e4475e03c@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by meanwhile): * cc: Meanwhile@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:32:31 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 06 Jun 2009 17:32:31 -0000 Subject: [Haiku-bugs] [Haiku] #3056: Haiku could use a power management framework In-Reply-To: <042.9121ae8569409436f6f7d01a9f8d4f88@haiku-os.org> References: <042.9121ae8569409436f6f7d01a9f8d4f88@haiku-os.org> Message-ID: <051.a7afc3dcef9196d6ee94c24834393adc@haiku-os.org> #3056: Haiku could use a power management framework -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: leavengood Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): Just saw this on the SDL-dev mailing list today from one of their lead devs, they are adding power management detection to SDL's 1.3 branch: http://lists.libsdl.org/pipermail/sdl-libsdl.org/2009-June/070800.html This might help give a scope of things that ours should include. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 19:36:49 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 06 Jun 2009 17:36:49 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) (was: Black screen when DVI connected) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.13f4840e7952f5d1513f672725069f7c@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): Long story short: As a workaround it's sufficient to provide the {{{workspaces}}} settings file. The absence of the {{{vesa}}} file makes the splash screen display at 1024x768, but the desktop comes up okay at 1280x1024. The {{{pgm_panel}}} option and {{{Screen_data}}} file are irrelevant. Sorry for the monologue. The Nvidia driver not supporting non-native resolution over DVI is still unsolved, so please keep the bug open, unless there is a duplicate already. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 20:42:23 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sat, 06 Jun 2009 18:42:23 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 In-Reply-To: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> References: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> Message-ID: <057.9698594533c5fd5e04a7cd2ba98f0983@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by e_barsukowski): I know about this issue, but my hdds are not affected by it (they are Samsung, WD and very old 60GB Maxtor). Other OSes (FreeBSD and Solaris) boot with no delays. By the way, don't throw away your drive. Seagate released firmware upgrades to deal with the issue. I've successfully repaired one Seagate drive at my work. I'll try switching the bus_manager and will report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 20:53:55 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 06 Jun 2009 18:53:55 -0000 Subject: [Haiku-bugs] [Haiku] #4005: Higher job count parallel builds (jam -j 4 for example) don't work Message-ID: <044.e15562365ab509331da1342399b929be@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: | --------------------------+------------------------------------------------- When doing a "jam -j4" to build the image from scratch I receive a lot of missing targets, and end up having to repeat the build command 2+ times more to have it finally complete. And I'm not really sure the final image is sane, as there are errors regarding the copy of some files, and there's no sure-fire way of knowing it anyway, but I'll try comparing md5sums of the generated objects from one build and the other and see if I can filter out changes that are only related to hardcoding timestamps. Building with "jam -j2" works, though, as plenty of devs are known to use this. I guess the order of building and the dependencies between targets isn't fully fleshed out on our jamfiles. I'm under the strong impression that this is known already, but I've searched Trac all over and haven't found a single ticket related to this; anyway, it's not anything critical, so I'm filing this one as "enhancement". Still, doing such parallel build under Haiku itself is fantastic to test the IO subsystem, the scheduler, and to demo how Haiku will be able to decode 8+ streams of video, build itself, and not drop a single frame in the process ;) Build logs attached; same build, each an additional run of "jam -q -j4" (5 runs in total) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 22:05:26 2009 From: trac at haiku-os.org (Pete) Date: Sat, 06 Jun 2009 20:05:26 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.73b0b98322affe3b75ccbe76a80b116f@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by Pete): Nope -- removing hda (well actually renaming it and removing the link in .../multi) has no effect. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 22:21:37 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 20:21:37 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.74be0c79edb7f6db3bbbab66568dbcbf@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by umccullough): I don't think renaming a driver doesn't prevent it from loading... it needs to be moved out of the drivers/bin I think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 22:22:16 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 20:22:16 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.bfd66344314f9a42763094b4ab74c44c@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by umccullough): Let me try that again: I don't think renaming a driver prevents it from loading... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 23:37:44 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 21:37:44 -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.367f077dfd79d133a8f8dd70d0204e86@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 umccullough): Has been issues suspected with even -j2 as noted in the following tickets: #1116, #1976, #2572 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 23:38:39 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 06 Jun 2009 21:38:39 -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.6f8008298eed177f8795c2876e9346b8@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 umccullough): Replying to [comment:1 umccullough]: > Has been issues suspected with even -j2 as noted in the following tickets: #1116, #1976, #2572 Whoops, that last one should have been #2776 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 23:42:22 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 06 Jun 2009 21:42: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.0ae3a69b4ade2c9076c72f41079af2d1@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): Kind of hard to spot those when they contain no mention to "jam" on the summaries :) Many thanks for your diligent search! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 6 23:52:13 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sat, 06 Jun 2009 21:52:13 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 In-Reply-To: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> References: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> Message-ID: <057.b89216d5496150bec77d4e52edff02c6@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by e_barsukowski): After setting HAIKU_ATA_STACK = 1 ; in UserBuildConfig Haiku completely refused to recognize my IDE drives (many messages "ata 0 error: timeout waiting for interrupt" and no partitions found). After I detached both IDE drives from the system Haiku hanged at the message "allocate_commpage_entry(". I think it is the same place where it froze before, but at that time it printed only the letter "a" on the last line. So, 1) 'ata' bus_manager works worse than 'ide' on my system, 2) now it seems to be not the bug in disk driver, but in kernel; it is similar to bug #1711, but I can't see the whole debug message because the system freezes before it can print the message to the end. After rebuilding Haiku with the old bus_manager I'll try to find out more information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 00:08:15 2009 From: trac at haiku-os.org (Pete) Date: Sat, 06 Jun 2009 22:08:15 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.d316f767a3c2098dd43f7a0d57a8de38@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by Pete): Hmm. My understanding would be that the kernel scans the various '/boot/system/add-ons/kernel/drivers/dev/*' directories to link to actual drivers in '.../bin', so if the link doesn't exist, the add-on in bin isn't seen. In any case, I went back and moved the hda binary right off to a non-system folder in another partition. Same no-difference. (Rebooting included, of course...) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 08:51:46 2009 From: trac at haiku-os.org (agildehaus) Date: Sun, 07 Jun 2009 06:51:46 -0000 Subject: [Haiku-bugs] [Haiku] #4006: panic: vm_page_fault when initializing USB stick with DriveSetup Message-ID: <045.79f246f04708c6a07c988114a75826bd@haiku-os.org> #4006: panic: vm_page_fault when initializing USB stick with DriveSetup ------------------------+--------------------------------------------------- Reporter: agildehaus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- r30941; gcc2; running on virtualbox 2.2.4 I ran into this KDL when attempting to initialize a BFS partition on a USB stick with DriveSetup. Occurs with 100% reproducibility. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 12:49:34 2009 From: trac at haiku-os.org (axeld) Date: Sun, 07 Jun 2009 10:49:34 -0000 Subject: [Haiku-bugs] [Haiku] #4006: panic: vm_page_fault when initializing USB stick with DriveSetup In-Reply-To: <045.79f246f04708c6a07c988114a75826bd@haiku-os.org> References: <045.79f246f04708c6a07c988114a75826bd@haiku-os.org> Message-ID: <054.b241d381d0e2ceb4f71d6597b8394b0f@haiku-os.org> #4006: panic: vm_page_fault when initializing USB stick with DriveSetup ---------------------------+------------------------------------------------ Reporter: agildehaus | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * priority: normal => critical * component: - General => System/Kernel -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 12:51:02 2009 From: trac at haiku-os.org (axeld) Date: Sun, 07 Jun 2009 10:51:02 -0000 Subject: [Haiku-bugs] [Haiku] #1876: Media preferences, clicking on some checkboxes switches back to first tab In-Reply-To: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> References: <041.42b3343fa32b9c77d4f76b397e81d3ad@haiku-os.org> Message-ID: <050.1e5bcf059bbbc723685d1b331907e264@haiku-os.org> #1876: Media preferences, clicking on some checkboxes switches back to first tab ---------------------------+------------------------------------------------ Reporter: aldeck | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by axeld): Oh, good point. When a parameter web is changed, a certain notification is sent, and obviously ignored in the default BMediaTheme. So yes, it would be preferred to fix this the right way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 14:56:44 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 07 Jun 2009 12:56:44 -0000 Subject: [Haiku-bugs] [Haiku] #3997: Subversion 1.6.2 from Optionalpackage fails to start In-Reply-To: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> References: <037.4f417a524b636ce5caea4f792c75b89c@haiku-os.org> Message-ID: <046.ac2f7d1533370bfb328741a2ecc4ea72@haiku-os.org> #3997: Subversion 1.6.2 from Optionalpackage fails to start -----------------------+---------------------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new 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 Sun Jun 7 15:21:19 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sun, 07 Jun 2009 13:21:19 -0000 Subject: [Haiku-bugs] [Haiku] #4004: Haiku booting hangs at the 5th icon on Intel ICH9 In-Reply-To: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> References: <048.6fa5c1cdb1c3384f8e67676f758db4f7@haiku-os.org> Message-ID: <057.1da1dee1e9a6913433c5e5d5692a580d@haiku-os.org> #4004: Haiku booting hangs at the 5th icon on Intel ICH9 ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by e_barsukowski): After a bit testing I found out the following. 1) When SATA controller is configured in AHCI mode the system hangs at the 5th icon half typing the message "allocate_commpa" or "allocate_commpage_entr" or other variants on serial debug. After disabling SMP (either in BIOS or via safe mode options) I finally get {{{ <...> ahci: AHCIPort::ResetPort port 4, deviceBusy 0, forceDeviceReset 0 ahci: AHCIPort::PostReset port 4 ahci: device signature 0xeb140101 (ATAPI) allocate_commpage_entry(4, 34) -> 0xffff0118 PANIC: Fatal exception "Machine-Check Exception" occurred! Error code: 0x0 Welcome to Kernel Debugging Land... Thread 12 "main2" running on CPU 0 kdebug> }}} This is bug #1711, so I'll post there. 2) When SATA IDE emulation enabled the system hangs at the 4th icon with message "More than 99% interrupts of vector 11 are unhandled". Here's the end of the debug log: {{{ KDiskDeviceManager::_AddDiskSystem() done: No error number of disk systems: 5 KDiskDeviceManager::_Scan(/dev/disk) PCI-IDE: Controller in native mode: cmd 0x4448, ctrl 0x4466, irq 11 PCI-IDE: init channel... PCI-IDE: channel index 0 PCI-IDE: bus master base 0x4410 PCI-IDE: init channel done IDE: scan_device_worker: bus 0x80fb5a5c, device-number 0 IDE: create_device: bus 0x80fb5a5c, device-number 0 IDE: setup_device_links: bus 0x80fb5a5c, device 0x817cb740 IDE: scan_device_int: device 0x817cb740, atapi 0 IDE: scan_device_int: waiting 100ms... More than 99% interrupts of vector 11 are unhandled Last message repeated 129 times. PANIC: Keyboard Requested Halt Welcome to Kernel Debugging Land... Thread 13 "main2" running on CPU 0 kdebug> ints int 1, enabled 1, handled 0, unhandled 0, ACTIVE kernel_x86:debug_keyboard_interrupt (0x800d4510), data 0x00000000 int 9, enabled 2, handled 0, unhandled 0 ehci:InterruptHandler__4EHCIPv (0x805f8db4), data 0x80fbf660 uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe2a8 int 10, enabled 2, handled 0, unhandled 0 uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe6a4 uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe000 int 11, enabled 5, handled 1, unhandled 1309353 ide_adapter:ide_adapter_inthand (0x80619b38), data 0x80fc5000 ehci:InterruptHandler__4EHCIPv (0x805f8db4), data 0x80fbf880 uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe550 uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe3fc uhci:InterruptHandler__4UHCIPv (0x80757d00), data 0x80fbe154 int 219, enabled 1, handled 5182, unhandled 0 kernel_x86:apic_timer_interrupt (0x800ddb20), data 0x00000000 int 221, enabled 1, handled 1108, unhandled 0 kernel_x86:i386_ici_interrupt (0x800d620c), data 0x00000000 int 222, enabled 1, handled 0, unhandled 0 kernel_x86:i386_smp_error_interrupt (0x800d6244), data 0x00000000 int 223, enabled 1, handled 0, unhandled 0 kernel_x86:i386_spurious_interrupt (0x800d6238), data 0x00000000 kdebug> }}} Removing both uhci and ehci drivers or disabling USB controller in BIOS helps: the boot process ends up at the first issue (allocate_commpage_entry). This seems to be IRQ sharing conflict between ide and usb drivers. Should I change the ticket header accordingly? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 15:30:37 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sun, 07 Jun 2009 13:30:37 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.9c0233ade9d8d7a8d4725085c5afcc96@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by e_barsukowski): * status: closed => reopened * resolution: fixed => Comment: I still have this issue in r30890. My system has Intel DG33FB motherboard based on G33 chipset, Core2 Duo E6750 CPU and 2GB of RAM. Haiku hangs at the 5th icon half typing the message "allocate_commpa" or "allocate_commpage_entr" or other variations on serial debug. After disabling SMP (either in BIOS or via safe mode options) I finally get {{{ <...> ahci: AHCIPort::ResetPort port 4, deviceBusy 0, forceDeviceReset 0 ahci: AHCIPort::PostReset port 4 ahci: device signature 0xeb140101 (ATAPI) allocate_commpage_entry(4, 34) -> 0xffff0118 PANIC: Fatal exception "Machine-Check Exception" occurred! Error code: 0x0 Welcome to Kernel Debugging Land... Thread 12 "main2" running on CPU 0 kdebug> }}} The KDL prompt appears only on serial debug but not on the screen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 19:16:20 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 07 Jun 2009 17:16:20 -0000 Subject: [Haiku-bugs] [Haiku] #4007: Tracker crash: BColumnTitle::Draw / BString Message-ID: <043.c05af40dfb6282c0f399990b0d53d303@haiku-os.org> #4007: Tracker crash: BColumnTitle::Draw / BString ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Backtrace: {{{ GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 335 caused an exception: Segment violation Reading symbols from /boot/system/runtime_loader...done. Loaded symbols for /boot/system/runtime_loader Reading symbols from /boot/system/lib/libbe.so...done. Loaded symbols for /boot/system/lib/libbe.so Reading symbols from /boot/system/lib/libtracker.so...done. Loaded symbols for /boot/system/lib/libtracker.so Reading symbols from /boot/system/lib/libroot.so...done. Loaded symbols for /boot/system/lib/libroot.so Reading symbols from /boot/system/lib/libtranslation.so...done. Loaded symbols for /boot/system/lib/libtranslation.so Reading symbols from /boot/system/lib/libtextencoding.so...done. Loaded symbols for /boot/system/lib/libtextencoding.so Reading symbols from /boot/system/lib/libiconv.so...done. Loaded symbols for /boot/system/lib/libiconv.so Reading symbols from /boot/system/add- ons/Translators/BMPTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/BMPTranslator Reading symbols from /boot/system/add- ons/Translators/EXRTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/EXRTranslator Reading symbols from /boot/system/lib/libilmimf.so...done. Loaded symbols for /boot/system/lib/libilmimf.so Reading symbols from /boot/system/lib/libz.so...done. Loaded symbols for /boot/system/lib/libz.so Reading symbols from /boot/system/add- ons/Translators/GIFTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/GIFTranslator Reading symbols from /boot/system/add- ons/Translators/JPEG2000Translator...done. Loaded symbols for /boot/system/add-ons/Translators/JPEG2000Translator Reading symbols from /boot/system/add- ons/Translators/JPEGTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/JPEGTranslator Reading symbols from /boot/system/add- ons/Translators/PCXTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PCXTranslator Reading symbols from /boot/system/add- ons/Translators/PNGTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PNGTranslator Reading symbols from /boot/system/add- ons/Translators/PPMTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PPMTranslator Reading symbols from /boot/system/add- ons/Translators/RAWTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/RAWTranslator Reading symbols from /boot/system/add-ons/Translators/RTF- Translator...done. Loaded symbols for /boot/system/add-ons/Translators/RTF-Translator Reading symbols from /boot/system/add- ons/Translators/SGITranslator...done. Loaded symbols for /boot/system/add-ons/Translators/SGITranslator Reading symbols from /boot/system/add- ons/Translators/STXTTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/STXTTranslator Reading symbols from /boot/system/add- ons/Translators/TGATranslator...done. Loaded symbols for /boot/system/add-ons/Translators/TGATranslator Reading symbols from /boot/system/add- ons/Translators/TIFFTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/TIFFTranslator Reading symbols from /boot/system/add- ons/Translators/WonderBrushTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/WonderBrushTranslator [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/system/Tracker (87) thread w>libiconv (335)] 0x003bafe8 in BString::BString () from /boot/system/lib/libbe.so (gdb) bt #0 0x003bafe8 in BString::BString () from /boot/system/lib/libbe.so #1 0x005af9af in BPrivate::BColumnTitle::Draw () from /boot/system/lib/libtracker.so #2 0x005b08d0 in BPrivate::BTitleView::Draw () from /boot/system/lib/libtracker.so #3 0x005b1810 in BPrivate::BTitleView::Draw () from /boot/system/lib/libtracker.so #4 0x0036524c in BView::_Draw () from /boot/system/lib/libbe.so #5 0x0036e9f4 in BWindow::DispatchMessage () from /boot/system/lib/libbe.so #6 0x0036aecd in BWindow::task_looper () from /boot/system/lib/libbe.so #7 0x002bfc50 in BLooper::_task0_ () from /boot/system/lib/libbe.so #8 0x00638c15 in thread_entry () from /boot/system/lib/libroot.so #9 0x701c5fec in ?? () (gdb) }}} {{{libiconv}}} above was the name of the folder. It's a one-time crash for now, don't know how to reproduce, sorry. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 21:50:20 2009 From: trac at haiku-os.org (michael.weirauch) Date: Sun, 07 Jun 2009 19:50:20 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.85ff55f3e6f11429781f1b81645f4182@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): r30981; ide-bm; acpi; scheduler-affine; Following the recent "Scheduler"-thread on the mailing list, commenting the {{{asm("hlt");}}} in {{{x86/arch_cpu.cpp#arch_cpu_idle()}}} or replacing it by a {{{asm("nop");}}} results in the system to '''not''' freeze during or after compilation runs, or other I/O intense tasks. System is up for more then two hours including compilations, svn up's and surfing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 22:09:05 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 07 Jun 2009 20:09:05 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.8039a6f8146b4cda2da3c3330d0fbd3c@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 23:04:50 2009 From: trac at haiku-os.org (stippi) Date: Sun, 07 Jun 2009 21:04:50 -0000 Subject: [Haiku-bugs] [Haiku] #4008: TGA and WonderBrush Translator corrupt memory. Message-ID: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> #4008: TGA and WonderBrush Translator corrupt memory. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------+------------------------------------------ When importing media files into Clockwerk, the presence of either one of these Translators will cause crashes later on. Clockwerk tries to detect files as bitmaps first, then as media files. Luckily, it is reproducible 100% as soon as the first media file is dropped on the clip list. Will look into it ASAP, if no one beats me to it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 23:08:04 2009 From: trac at haiku-os.org (stippi) Date: Sun, 07 Jun 2009 21:08:04 -0000 Subject: [Haiku-bugs] [Haiku] #4008: Detecting bitmaps with enough Translators will corrupt memory. (was: TGA and WonderBrush Translator corrupt memory.) In-Reply-To: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> References: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> Message-ID: <050.2f8cf3105ab1e51b28b93631c1815d0a@haiku-os.org> #4008: Detecting bitmaps with enough Translators will corrupt memory. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------+------------------------------------------ Description changed by stippi: Old description: > When importing media files into Clockwerk, the presence of either one of > these Translators will cause crashes later on. Clockwerk tries to detect > files as bitmaps first, then as media files. Luckily, it is reproducible > 100% as soon as the first media file is dropped on the clip list. Will > look into it ASAP, if no one beats me to it. New description: When importing media files into Clockwerk, the presence of more than 13 Translators will cause crashes later on. Clockwerk tries to detect files as bitmaps first, then as media files. Luckily, it is reproducible 100% as soon as the first media file is dropped on the clip list. Will look into it ASAP, if no one beats me to it. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 7 23:10:38 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 07 Jun 2009 21:10:38 -0000 Subject: [Haiku-bugs] [Haiku] #4007: Tracker crash: BColumnTitle::Draw / BString In-Reply-To: <043.c05af40dfb6282c0f399990b0d53d303@haiku-os.org> References: <043.c05af40dfb6282c0f399990b0d53d303@haiku-os.org> Message-ID: <052.c213634aed80f9628136eabe116b4324@haiku-os.org> #4007: Tracker crash: BColumnTitle::Draw / BString ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Comment(by andreasf): Should've mentioned this was at r30980. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 08:43:06 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 08 Jun 2009 06:43:06 -0000 Subject: [Haiku-bugs] [Haiku] #4009: Flags shown by df are wrong when NTFS is mounted Message-ID: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> #4009: Flags shown by df are wrong when NTFS is mounted -------------------------------+-------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- This is on real hardware, gcc4 and new ATA and build from friday evening. It doesn't matter if you mount the NTFS RO or RW, on "df -a" you see for both: {{{ /128M ntfs 125.0M 121.7M -AM-P-W /dev/disk/usb/0/0/0 }}} But the mounted NTFS is RO if mounted RO and RW if mounted RW.[[BR]] Only the flags shown by "df" are wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 09:00:27 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 08 Jun 2009 07:00:27 -0000 Subject: [Haiku-bugs] [Haiku] #4010: USB-Stick not working with Haiku Message-ID: <042.d6ecf45502f6dbe058f14dd74f7b7965@haiku-os.org> #4010: USB-Stick not working with Haiku -------------------------+-------------------------------------------------- Reporter: jahaiku | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- This is on real hardware, gcc4 and new ATA from friday evening. I have a 256MB-USB-Stick which is not working, if I connect it to Haiku. Tested with many different USB-Chips (1.1/2.0) and the behaviour is always the same. Message in syslog: {{{ KERN: usb hub 2: port 0: new device connected KERN: usb hub 31: port 0: new device connected }}} Message from listusb: {{{ [Device /dev/bus/usb/0/0/0] Class .................. 0x00 Subclass ............... 0x00 Protocol ............... 0x00 Max Endpoint 0 Packet .. 64 USB Version ............ 0x0200 Vendor ID .............. 0x067b Product ID ............. 0x2517 Product Version ........ 0x0001 Manufacturer String .... "USB 2.0 Flash Disk" Product String ......... "USB Mass Storage Device" Serial Number .......... "" [Configuration 0] Configuration String . "" [Interface 0] [Alternate 0 active] Class .............. 0x08 Subclass ........... 0x05 Protocol ........... 0x50 Interface String ... "" [Endpoint 0] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Output [Endpoint 1] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Input [Device /dev/bus/usb/0/0/hub] Class .................. 0x09 Subclass ............... 0x00 Protocol ............... 0x00 Max Endpoint 0 Packet .. 64 USB Version ............ 0x0200 Vendor ID .............. 0x067b Product ID ............. 0x2515 Product Version ........ 0x0001 Manufacturer String .... "" Product String ......... "" Serial Number .......... "" [Configuration 0] Configuration String . "" [Interface 0] [Alternate 0 active] Class .............. 0x09 Subclass ........... 0x00 Protocol ........... 0x00 Interface String ... "" [Endpoint 0] MaxPacketSize .... 1 Interval ......... 12 Type ............. Interrupt Direction ........ Input [Descriptor 0] Type ............. 0x29 Data ............. 01 0d 00 32 64 02 ff [Device /dev/bus/usb/0/hub] Class .................. 0x09 Subclass ............... 0x00 Protocol ............... 0x00 Max Endpoint 0 Packet .. 64 USB Version ............ 0x0110 Vendor ID .............. 0x0000 Product ID ............. 0x0000 Product Version ........ 0x0110 Manufacturer String .... "HAIKU Inc." Product String ......... "UHCI RootHub" Serial Number .......... "" [Configuration 0] Configuration String . "" [Interface 0] [Alternate 0 active] Class .............. 0x09 Subclass ........... 0x00 Protocol ........... 0x00 Interface String ... "" [Endpoint 0] MaxPacketSize .... 8 Interval ......... 255 Type ............. Interrupt Direction ........ Input [Descriptor 0] Type ............. 0x29 Data ............. 02 00 00 00 00 00 ff }}} Linux-Kernel-Message, if I connect the Stick to Kernel 2.6.29: {{{ usb 1-5: new high speed USB device using ehci_hcd and address 4 usb 1-5: New USB device found, idVendor=067b, idProduct=2515 usb 1-5: New USB device strings: Mfr=1, Product=3, SerialNumber=0 usb 1-5: Product: USB Embedded Hub usb 1-5: Manufacturer: USB 2.0 Flash Disk usb 1-5: configuration #1 chosen from 1 choice hub 1-5:1.0: USB hub found hub 1-5:1.0: 1 port detected usb 1-5.1: new high speed USB device using ehci_hcd and address 5 usb 1-5.1: New USB device found, idVendor=067b, idProduct=2517 usb 1-5.1: New USB device strings: Mfr=1, Product=4, SerialNumber=0 usb 1-5.1: Product: USB Mass Storage Device usb 1-5.1: Manufacturer: USB 2.0 Flash Disk usb 1-5.1: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning scsi 3:0:0:0: Direct-Access USB 2.0 Flash Disk PROL PQ: 0 ANSI: 0 CCS sd 3:0:0:0: [sdb] 512000 512-byte hardware sectors: (262 MB/250 MiB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 00 06 00 00 sd 3:0:0:0: [sdb] Assuming drive cache: write through sd 3:0:0:0: [sdb] 512000 512-byte hardware sectors: (262 MB/250 MiB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 00 06 00 00 sd 3:0:0:0: [sdb] Assuming drive cache: write through sdb: unknown partition table sd 3:0:0:0: [sdb] Attached SCSI removable disk sd 3:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 09:11:55 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 08 Jun 2009 07:11:55 -0000 Subject: [Haiku-bugs] [Haiku] #4011: BFS-Errors if trash is emptied Message-ID: <042.d409952ec97f9da409da22d25794d6db@haiku-os.org> #4011: BFS-Errors if trash is emptied ------------------------------+--------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- This is gcc4 and new ATA build from friday evening on real hardware.[[BR]][[BR]] If I empty the trash with files in it, I see the following BFS-Error in syslog: {{{ KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 1572866 is already deleted! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 10:55:20 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 08:55:20 -0000 Subject: [Haiku-bugs] [Haiku] #4009: Flags shown by df are wrong when NTFS is mounted In-Reply-To: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> References: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> Message-ID: <051.ad3bd6351560e549a469fe2d9e016fdb@haiku-os.org> #4009: Flags shown by df are wrong when NTFS is mounted --------------------------------+------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Should be fixed in r30996. Now that I've seen the code, be careful when using this file system read/write - deleting files seems to be dangerous when they are still in use. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 10:58:59 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 08 Jun 2009 08:58:59 -0000 Subject: [Haiku-bugs] [Haiku] #4009: Flags shown by df are wrong when NTFS is mounted In-Reply-To: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> References: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> Message-ID: <051.3c389dd60e8a5015282f6ff5346c36ab@haiku-os.org> #4009: Flags shown by df are wrong when NTFS is mounted --------------------------------+------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by jahaiku): Replying to [comment:1 axeld]: > Should be fixed in r30996. Now that I've seen the code, be careful when using this file system read/write - deleting files seems to be dangerous when they are still in use. Then should I open a ticket for this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:10:29 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 08 Jun 2009 09:10:29 -0000 Subject: [Haiku-bugs] [Haiku] #3976: Remove Menu preference In-Reply-To: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> References: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> Message-ID: <053.cf95435c38990102e0e22ecc4b557c3e@haiku-os.org> #3976: Remove Menu preference -------------------------------+-------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by jahaiku): * status: closed => reopened * resolution: fixed => Comment: Please remove the Menu link from the Preferences-Menu, too. Line 298 in build/jam/HaikuImage file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:29:48 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 09:29:48 -0000 Subject: [Haiku-bugs] [Haiku] #4012: NTFS handles deletions incorrectly Message-ID: <040.77fd470eacb838b4e483178870336857@haiku-os.org> #4012: NTFS handles deletions incorrectly -------------------------------+-------------------------------------------- Reporter: axeld | Owner: 3dEyes Type: bug | Status: new Priority: critical | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- When a file is unlinked/deleted, you must only make it unavailable to the user (ie. it must not appear in file listings anymore, and cannot be opened). However, its space on disk must not be deleted until the kernel no longer needs the file (it will then call fs_remove_vnode()). Until that one is called, an application with an open file handle must still be able to read from that file, and write to that file as if it would still exist. Please check if the file system remains valid when actually doing so - in that case, the priority could be put back to "high". As is, I wouldn't enable read/write for the file system yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:30:51 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 09:30:51 -0000 Subject: [Haiku-bugs] [Haiku] #4009: Flags shown by df are wrong when NTFS is mounted In-Reply-To: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> References: <042.02973c918519f29cca8c6fdcde801a68@haiku-os.org> Message-ID: <051.a904b782b0cbdeb575ad9a92e6641709@haiku-os.org> #4009: Flags shown by df are wrong when NTFS is mounted --------------------------------+------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by axeld): Thanks I already did so (#4012). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:41:15 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 09:41:15 -0000 Subject: [Haiku-bugs] [Haiku] #3976: Remove Menu preference In-Reply-To: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> References: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> Message-ID: <053.9c6fc12c1eacc81b34711ee10f7bcd33@haiku-os.org> #3976: Remove Menu preference -------------------------------+-------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Fixed in r30997. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:55:21 2009 From: trac at haiku-os.org (stippi) Date: Mon, 08 Jun 2009 09:55:21 -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.24193bd3b4d72edec93ecf31825909d9@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by stippi): This one is definitely not fixed. Although I didn't reinitialize the partition, if that's something I should have done. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 11:56:46 2009 From: trac at haiku-os.org (korli) Date: Mon, 08 Jun 2009 09:56:46 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.b9fcfaf5f8bf87fc9db4c66f370e309b@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by korli): Replying to [comment:6 umccullough]: > Let me try that again: > > I don't think renaming a driver prevents it from loading... I usually move a driver to its parent directory to prevent it from loading. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 12:00:43 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 10:00:43 -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.2d94cc1e9fae05af010d0690bf597a3c@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): If checkfs runs through without errors, this should be enough for this error. I guess you still haven't used chkindex of the BFS tools? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 13:33:10 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 08 Jun 2009 11:33:10 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.76addcf21e5ca8bc4642593f40aca5a0@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: reopened => closed * resolution: => fixed Comment: Can you please open a new ticket. The original problem in this ticket has been reported fixed and a "Machine-Check Exception" had not been mentioned in the first place. Also a stack trace would be very helpful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 15:07:42 2009 From: trac at haiku-os.org (axeld) Date: Mon, 08 Jun 2009 13:07:42 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.79f384ddd0e1e4499244ccc8802b6095@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => critical * status: new => closed * resolution: => fixed Comment: Fixed in r30998: the attribute directory of the root directory was ignored by checkfs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 18:16:40 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 08 Jun 2009 16:16:40 -0000 Subject: [Haiku-bugs] [Haiku] #4010: USB-Stick not working with Haiku In-Reply-To: <042.d6ecf45502f6dbe058f14dd74f7b7965@haiku-os.org> References: <042.d6ecf45502f6dbe058f14dd74f7b7965@haiku-os.org> Message-ID: <051.3d6829f775144913ec12c35cc03a2cae@haiku-os.org> #4010: USB-Stick not working with Haiku -------------------------+-------------------------------------------------- Reporter: jahaiku | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): It's using a protocol that we don't support. The thing is that those protocols are not really common anymore. All but the transparent SCSI protocol are discouraged for new products according to Microsoft, so you don't see it often. The priority of supporting it is quite low due to that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 19:11:38 2009 From: trac at haiku-os.org (e_barsukowski) Date: Mon, 08 Jun 2009 17:11:38 -0000 Subject: [Haiku-bugs] [Haiku] #1711: Haiku stops booting at allocate_commpage_entry(4, 34) In-Reply-To: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> References: <039.2d605d85fd03d15830479374a2593081@haiku-os.org> Message-ID: <048.0e69709025ab6efa40a4c29981e4abd2@haiku-os.org> #1711: Haiku stops booting at allocate_commpage_entry(4, 34) ----------------------------+----------------------------------------------- Reporter: euan | Owner: korli Type: bug | Status: closed Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by e_barsukowski): Sorry. I'll open a new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 19:41:52 2009 From: trac at haiku-os.org (e_barsukowski) Date: Mon, 08 Jun 2009 17:41:52 -0000 Subject: [Haiku-bugs] [Haiku] #4013: Haiku booting breaks with "Machine-Check Exception" Message-ID: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> #4013: Haiku booting breaks with "Machine-Check Exception" ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ I try to run Haiku r30998 on real hardware. My machine has Intel DG33FB motherboard based on G33 chipset, Core2 Duo E6750 CPU and 2GB of RAM. Without additional options the boot process hangs at the 5th icon half typing messages like "allocate_commpa" or "allocate_commpage_entr" at the serial debug. Keyboard (PS/2) stops working, so the only way out is hardware reset. Disabling SMP (either in BIOS or via safe mode options) leads to the following message: {{{ <...> trying: file_systems/nfs/v1 returned: -1 trying: file_systems/write_overlay/v1 returned: -1 allocate_commpage_entry(4, 34) -> 0xffff0118 PANIC: Fatal exception "Machine-Check Exception" occurred! Error code: 0x0 Welcome to Kernel Debugging Land... Thread 12 "main2" running on CPU 0 kdebug> }}} The KDL prompt appears only on serial debug but not on the screen. The keyboard seems to work. After I type "sc" and hit Haiku prints some lines at the debug output (there is still nothing on the screen) and freezes. Again nothing but reset helps. Here's the output of "sc": {{{ allocate_commpage_entry(4, 34) -> 0xffff0118 PANIC: Fatal exception "Machine-Check Exception" occurred! Error code: 0x0 Welcome to Kernel Debugging Land... Thread 12 "main2" running on CPU 0 kdebug> sc stack trace for thread 12 "main2" kernel stack: 0x8019c000 to 0x801a0000 frame caller :function + offset 0 8019f908 (+ 48) 80062941 invoke_debugger_command() + 0x0105 1 8019f938 (+ 64) 80062721 invoke_pipe_segment__FP21debugger_command_pipelPc() + 0x0079 2 8019f978 (+ 64) 80062ad4 invoke_debugger_command_pipe() + 0x009c 3 8019f9b8 (+ 48) 800644d0 _ParseCommandPipe__16ExpressionParserRi() + 0x0234 4 8019f9e8 (+ 64) 8006390a EvaluateCommand__16ExpressionParserPCcRi() + 0x02ba 5 8019fa28 (+ 224) 800658e4 evaluate_debug_command() + 0x0080 6 8019fb08 (+ 64) 8006079a kernel_debugger_loop__Fv() + 0x01b6 7 8019fb48 (+ 32) 800616b1 kernel_debugger() + 0x004d 8 8019fb68 (+ 192) 80061659 panic() + 0x0029 9 8019fc28 (+ 64) 800d5470 fatal_exception() + 0x0030 10 8019fc68 (+ 12) 800d8df6 int_bottom() + 0x0036 kernel iframe at 0x8019fc74 (end = 0x8019fcc4) eax 0x8077e000 ebx 0x80f97200 ecx 0xb0 edx 0x0 esi 0xdb edi 0x0 ebp 0x8019fcd4 esp 0x8019fca8 eip 0x8005b390 eflags 0x210086 vector: 0x12, error code: 0x0 11 8019fc74 (+ 96) 8005b390 timer_interrupt() + 0x0000 12 8019fcd4 (+ 48) 8003ed93 int_io_interrupt_handler() + 0x006f 13 8019fd04 (+ 48) 800d5798 hardware_interrupt() + 0x0070 }}} Full debug logs are attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 19:53:07 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 08 Jun 2009 17:53:07 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.6bd01b00506aee219d1b29c74aca7906@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi again, Thanks for your experiments! I've located two issues we have currently. -- One is described in ticket #3850 (don't set non existing VESA modes). While I am yet unsure if the modes are non-existing, or if we are dealing with a nVidia BIOS problem, it's clear that using 8 or 16 bit modes seems always OK, while 32bit mode splashscreens don't display on a number of cards. On some cards because of this failure the desktop won't come up either, since the card's state is messed up and the driver can't correct that currently (in most cases). -- The second problem is that of the 'force widescreen' setting. If you have a non-widescreen monitor, you should set that option to off. otherwise especially DVI connected screens are fed with incorrect setup modelines unless driver in their native resolution. I'm working on this bug by setting up EDID/DDC to get actual specs from the connected screens to better autodetect where the picture needs to go and if we have ws or not. -- With these two bugs known to you, can you retest and see if we hit the 'jackpot'? Thanks! Rudolf. BTW: The driver supports dualhead and TVout (TVout only for cards with brooktree or conexant tv encoder). On BeOS you can issue these modes with the app dualhead setup (bebits). Unfortunately this app doesn't work on Haiku. I think that BeOS is being phased out these days, so I should probably rewrite the interface to work with the haiku prefs app (which in theory can handle these things too, and that works on ATI cards). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 20:01:59 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 08 Jun 2009 18:01:59 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.c031f2f3427a768dd0dfa0dfe752ac47@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | 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, you might be plagued by what I described in ticket #3850. Try 1024x768 mode in depth 16bit or a lower res mode in 32bit color: this should give you your splashscreen, maybe even with the second screen connected. The driver is working I expect (what's your cardID?? so I can check). Stippy is right I think: try using your desktop at 32bit mode, but try the splashscreen at 16bit mode (trick: set the 32bit mode using 'Screen', exit that app, wait a wile, and then manually modify the 'vesa' file in home/settings/kernel/drivers (I think). Change the 32 in 16 there (open with styled edit), then reboot. Please let me know what you find.. :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 20:03:31 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 08 Jun 2009 18:03:31 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.668a55c314b6c3eb6ad60117dfcf24a7@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Ah, that's home/config/settings/kernel/drivers .. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 21:44:25 2009 From: trac at haiku-os.org (andreasf) Date: Mon, 08 Jun 2009 19:44:25 -0000 Subject: [Haiku-bugs] [Haiku] #3914: Tracker crash In-Reply-To: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> References: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> Message-ID: <052.a1cd34b62e108499ff3195deee93254a@haiku-os.org> #3914: Tracker crash ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) * platform: All => x86 Comment: Replying to [comment:1 axeld]: > Without a stack trace, I'm afraid this report is pretty useless. #4007 looks similar and has a stacktrace and revision number. Didn't get notified of your comment, sorry - but wasn't reproducible until now anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 8 22:35:59 2009 From: trac at haiku-os.org (andreasf) Date: Mon, 08 Jun 2009 20:35:59 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.439b957fc006e7a54d97e40d5303dad0@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): Hi, Bingo! I just confirmed it does work with {{{force_ws false}}} - it then shows the desktop fine at 1024x768 at 32bpp, as seen for VGA. This seems independent of the {{{pgm_panel}}} option. Still at r30980. So, I was curious and checked on a widescreen DVI monitor: there, it worked just fine without {{{nvidia.settings}}} file, defaulting to 1024x768 non-native resolution. I then set the resolution to the native 1680x1050, cold-rebooted with the 1280x1024 monitor connected, and then it did come up okay at 1280x1024 without a settings file. (The only thing unexpected was some odd 83.8 Hz refresh rate according to the Screen preflet.) For comparison, after exchanging my 1280x1024 monitor against a 1024x768 one on VGA, the latter still tried to display at 1280x1024 and needed to be set down to its native resolution through Screen preferences. Regarding #3850, it does show the splash screen in nice colours, although I can't say for sure whether it's 32bpp or 16bpp. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 00:08:53 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 08 Jun 2009 22:08:53 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.ae1b0474a84edf2814885a1d7eedb3aa@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by haiqu): Hi Rudolf, Tried changing the vesa config file to 1024 x 768 x 16 (after first selecting 1024 x 768 x 32 in Screen settings) and rebooted. Yes, we have a splash screen. :D I wouldn't know if this is the same problem you reported later, but happy to be able to use a higher resolution now. My only real concern was that if I needed to use Safe Mode I couldn't see it. Thanks. Very useful patch indeed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 00:10:22 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 08 Jun 2009 22:10:22 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.6a74816bce9bc36cfde68e6e62483b29@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by haiqu): Oh yeah, it's a 10de:0171 (NV17 [GeForce4 MX 440]) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 07:39:45 2009 From: trac at haiku-os.org (jahaiku) Date: Tue, 09 Jun 2009 05:39:45 -0000 Subject: [Haiku-bugs] [Haiku] #4012: NTFS handles deletions incorrectly In-Reply-To: <040.77fd470eacb838b4e483178870336857@haiku-os.org> References: <040.77fd470eacb838b4e483178870336857@haiku-os.org> Message-ID: <049.a97b697143aaae6102735914fb57961d@haiku-os.org> #4012: NTFS handles deletions incorrectly -------------------------------+-------------------------------------------- Reporter: axeld | Owner: 3dEyes Type: bug | Status: new Priority: critical | Milestone: R1 Component: File Systems/NTFS | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by jahaiku): * cc: Jens.Arm@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 08:51:08 2009 From: trac at haiku-os.org (JeremyVisser) Date: Tue, 09 Jun 2009 06:51:08 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.17b43bad57ea46ce18c1d19d27f3a6fd@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by JeremyVisser): Sorry - I didn't get notification e-mails either, as they were marked as spam. I don't understand what's going on anymore -- it's way over my head. I'm still willing to test, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 14:06:40 2009 From: trac at haiku-os.org (axeld) Date: Tue, 09 Jun 2009 12:06:40 -0000 Subject: [Haiku-bugs] [Haiku] #4007: Tracker crash: BColumnTitle::Draw / BString In-Reply-To: <043.c05af40dfb6282c0f399990b0d53d303@haiku-os.org> References: <043.c05af40dfb6282c0f399990b0d53d303@haiku-os.org> Message-ID: <052.d837503909e67a2db0ddd582e1603ba9@haiku-os.org> #4007: Tracker crash: BColumnTitle::Draw / BString -----------------------------------+---------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: 3914 Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 3914 Comment: Duplicate of #3914. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 18:58:33 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 09 Jun 2009 16:58:33 -0000 Subject: [Haiku-bugs] [Haiku] #4014: subversion sometimes stalls at the end of a checkout Message-ID: <042.c7820f4d2a293ee884f2413fd497e5cc@haiku-os.org> #4014: subversion sometimes stalls at the end of a checkout -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- With the new subversion-1.6.2 package I get this when trying to checkout Haiku: U headers/private/graphics/vesa/ vesa_info.h U headers/private/graphics/vesa/vesa.h A headers/private/graphics/ati svn: REPORT request failed on '/svnroot/repos/haiku/!svn/vcc/default' svn: REPORT of '/svnroot/repos/haiku/!svn/vcc/default': Could not read response body: connection was closed by server. (http://svn.berlios.de) ~/develop/haiku/trunk> This doesn't always happen, seems to happen more often with larger checkouts, and running svn up usually finishes things up. Not sure if this is an issue with subversion of a symptom of something going on with the network. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 19:52:04 2009 From: trac at haiku-os.org (umccullough) Date: Tue, 09 Jun 2009 17:52:04 -0000 Subject: [Haiku-bugs] [Haiku] #4014: subversion sometimes stalls at the end of a checkout In-Reply-To: <042.c7820f4d2a293ee884f2413fd497e5cc@haiku-os.org> References: <042.c7820f4d2a293ee884f2413fd497e5cc@haiku-os.org> Message-ID: <051.4c477fb7fadeb77f521d91b34e96e4c1@haiku-os.org> #4014: subversion sometimes stalls at the end of a checkout -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by umccullough): I assume basd on the failure path that this was using the http:// protocol for the checkout? Perhaps test with the svn:// protocol to see if you get better results - even on Linux, I have a lot of issues with http:// which seems to die midway through, and also takes longer to get all the sources. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:13:40 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 09 Jun 2009 19:13:40 -0000 Subject: [Haiku-bugs] [Haiku] #4015: cp doesn't copy empty attributes Message-ID: <039.7cdf16ba92aae944f9db38645d69cb96@haiku-os.org> #4015: cp doesn't copy empty attributes ---------------------------------------------+------------------------------ Reporter: mmlr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ The cp command does copy attributes by default, but it doesn't copy empty ones. This is due how the copy_attributes routine is written in the copy backend of cp (src/bin/coreutils/src/copy.c). Comparing the source of copyattr's copy_attributes it is written in a way to ensure that empty attributes are created correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:13:52 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 09 Jun 2009 19:13:52 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.a1c0c832e8dcc8f95e180673dfb4c0e4@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there Jeremy. I've had the same spamming problem here on gmail.. Anyhow, can you test what andreasf just tested with force_ws false? Looking again at the logfiles you provided you have the same problem.. disabling the force_ws option should solve your thing. The first non- working log tried a desktop of 1024x768, the second 1280x1024 which is the native resolution of your screen. Since your screen isn't widescreen, other resolutions won't work since in those other resolutions the driver tries to scale the modes up to your monitor's native modeline, assuming it's a widescreen type. Hence: trouble. Keep me posted! Thanks :-) Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:20:29 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 09 Jun 2009 19:20:29 -0000 Subject: [Haiku-bugs] [Haiku] #3689: No splash screen at boot with nVidia GeForce MX440 In-Reply-To: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> References: <040.d46740e36a12c83a4e066f2fc37087cd@haiku-os.org> Message-ID: <049.25ccf7c77130b7dbaefdc671149c6392@haiku-os.org> #3689: No splash screen at boot with nVidia GeForce MX440 --------------------------------------+------------------------------------- Reporter: haiqu | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => duplicate Comment: Your card is indeed supported (checked ID). Thanks for testing! Closing this ticket as it's a duplicate of #3850. If you don't agree, let me know :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:25:53 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 09 Jun 2009 19:25:53 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.005034a8253fe3fcd2222a0ed01c4694@haiku-os.org> #1023: Monitor switches off on app_server start up -------------------------------------+-------------------------------------- Reporter: k2s | 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! Is this bug still valid? If so, I'd like to look at it and so retesting and more info is needed: if not, I'll close this bug.. Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:39:58 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 09 Jun 2009 19:39:58 -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.735aa33c271f6cfb91e01e8d8889aaee@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 rudolfc): Hi, There are probably at least 3 different problems reported here, so it's hard to nail it I fear. Hopefully (probably) there is one or two that's a duplicate of another bug which might already be solved or known howto work around. Anyhow, I'll give it a shot: BTW acca might have the force_ws true problem: if a DVI non-ws screen is set in a lower resolution than it's native one, it probably displays blackness. Modifying nvidia.settings to read force_ws false solves this. tigerdog: I'd be curious to know what resolution Haiku tried to set (you can see that in the driver logfile if you could grab it), and what the native resolution of your screen is. And: DVI or VGA? fano: hmm, tough one. If you'd have a second machine you'd probably be able to telnet into the machine and tell it to shut down? It's possible that it hangs though in which case that won't work either. Anyhow: testing with more than one screen connected at the time isn't such a good idea to find out what's going wrong. Try one at the time, I prefer not the HDTV, and an analog connection to begin with. Does that work OK? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 21:41:11 2009 From: trac at haiku-os.org (andreasf) Date: Tue, 09 Jun 2009 19:41:11 -0000 Subject: [Haiku-bugs] [Haiku] #4014: subversion sometimes stalls at the end of a checkout In-Reply-To: <042.c7820f4d2a293ee884f2413fd497e5cc@haiku-os.org> References: <042.c7820f4d2a293ee884f2413fd497e5cc@haiku-os.org> Message-ID: <051.27142d65d504a7addd86f52b98414ed6@haiku-os.org> #4014: subversion sometimes stalls at the end of a checkout -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new 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 Tue Jun 9 22:16:27 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 09 Jun 2009 20:16:27 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.bd99dc4de7b672bfc6e269bcbcb56e98@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- 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 there, Just tested on the NV28 without nvidia driver. It turns out the kernel fails to set 1280x1024x32 bit mode, but the vesa accelerant does this correctly. My guess would now be there's a fault in the kernel setting the mode. I'll try to investigate at some point. kernel reports: KERN: crtc: h 1328/1440/1688, v 1025/1028/1066, pixel clock 108000000, refresh 6064 This modeline is the native one reported via EDID, though the refresh of 6064 seems strange. (should be 60Hz) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 22:26:10 2009 From: trac at haiku-os.org (axeld) Date: Tue, 09 Jun 2009 20:26:10 -0000 Subject: [Haiku-bugs] [Haiku] #4015: cp doesn't copy empty attributes In-Reply-To: <039.7cdf16ba92aae944f9db38645d69cb96@haiku-os.org> References: <039.7cdf16ba92aae944f9db38645d69cb96@haiku-os.org> Message-ID: <048.dbbc9b67ee9534c9bba4eeb87d0463da@haiku-os.org> #4015: cp doesn't copy empty attributes ----------------------------------------------+----------------------------- Reporter: mmlr | 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: new => closed * resolution: => fixed Comment: Should be fixed in r31000. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 22:51:59 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 09 Jun 2009 20:51:59 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.4a5ae21eb6cbb79bab754eb313e4c22c@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by haiqu): See also #3689 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 9 23:38:54 2009 From: trac at haiku-os.org (JeremyVisser) Date: Tue, 09 Jun 2009 21:38:54 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.8d303e9ef14eb823c04fae1b56aa7e9b@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by JeremyVisser): Actually, I no longer have that 1280x1024 monitor. I now have a shiny new 1920x1080 (which, I believe, is 16:9) monitor -- will it still have the same symptoms, or if I understand you correctly, are widescreen monitors exempt from this problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 04:56:38 2009 From: trac at haiku-os.org (dlmcpaul) Date: Wed, 10 Jun 2009 02:56:38 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.163a0f0d47efe3f5e910fd75f03dff14@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Changes (by dlmcpaul): * status: new => closed * resolution: => fixed Comment: r31003 and r31004 corrected a number of issues with MSADPCM playback. The BeBeep.wav and BeStartup.wav now play correctly. Please test other wav files and let me know of any issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 13:00:54 2009 From: trac at haiku-os.org (jahaiku) Date: Wed, 10 Jun 2009 11:00:54 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.558912a7c1d52cbba05d8eecbe3dceb0@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Changes (by jahaiku): * cc: Jens.Arm@? (added) * status: closed => reopened * resolution: fixed => Comment: Change not compilable with gcc4 (gcc2 not tested) {{{ C++ generated/objects/haiku/x86/release/add- ons/media/plugins/wav_reader/WavReaderPlugin.o src/add-ons/media/plugins/wav_reader/WavReaderPlugin.cpp: In member function 'virtual status_t WavReader::Sniff(int32*)': src/add-ons/media/plugins/wav_reader/WavReaderPlugin.cpp:174: warning: comparison between signed and unsigned integer expressions src/add-ons/media/plugins/wav_reader/WavReaderPlugin.cpp:182: warning: comparison between signed and unsigned integer expressions src/add-ons/media/plugins/wav_reader/WavReaderPlugin.cpp:215: warning: comparison between signed and unsigned integer expressions src/add-ons/media/plugins/wav_reader/WavReaderPlugin.cpp:305: error: invalid array assignment }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 13:03:32 2009 From: trac at haiku-os.org (axeld) Date: Wed, 10 Jun 2009 11:03:32 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.f74fdba47a84f181d3adc2a6237224cc@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: This is a build problem, and has nothing to do with this bug. Please don't reopen tickets in such a case, but instead complain on the mailing list. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 13:09:01 2009 From: trac at haiku-os.org (jahaiku) Date: Wed, 10 Jun 2009 11:09:01 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.f0521a2776a7afe64af2d63efda0e184@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Comment(by jahaiku): OK, should I use in future the "main development list" or another? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 15:17:50 2009 From: trac at haiku-os.org (axeld) Date: Wed, 10 Jun 2009 13:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.8de247d4d7f14fbf16b5e1196de01614@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Comment(by axeld): That would be the one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 19:11:40 2009 From: trac at haiku-os.org (Pete) Date: Wed, 10 Jun 2009 17:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Wacom locks up system Message-ID: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> #4016: Wacom locks up system -----------------------+---------------------------------------------------- Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I have a Wacom Intuos tablet that I've been using on BeOS R5 for years (wacom_usb driver), but plugging it into my Haiku machine (ThinkPad 570E running r30629) locks it solid -- cursor freezes or disappears. Hitting F12 shows thread "ps2_service" or "scsi_device_service", apparently depending on exactly when the usb was plugged in. The pilot light on the Wacom never lights up unless it's plugged in before boot (but the freeze is about the same either way). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 19:12:35 2009 From: trac at haiku-os.org (Pete) Date: Wed, 10 Jun 2009 17:12:35 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Wacom locks up system In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.dfcf67fc8b21996f291a2410bebc477c@haiku-os.org> #4016: Wacom locks up system ---------------------+------------------------------------------------------ Reporter: Pete | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Changes (by Pete): * component: - General => Drivers -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 10 19:14:32 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 10 Jun 2009 17:14:32 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Wacom locks up system In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.2acb11def38fabe4aa6ff2371e2b736c@haiku-os.org> #4016: Wacom locks up system ---------------------+------------------------------------------------------ Reporter: Pete | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Changes (by anevilyak): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 11 06:19:30 2009 From: trac at haiku-os.org (bbjimmy) Date: Thu, 11 Jun 2009 04:19:30 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.e1b478605553d24a3420530486e8a365@haiku-os.org> #3849: Audio files with distorted sound. -----------------------------------+---------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3984 -----------------------------------+---------------------------------------- Comment(by bbjimmy): Replying to [comment:11 dlmcpaul]: > r31003 and r31004 corrected a number of issues with MSADPCM playback. > > The BeBeep.wav and BeStartup.wav now play correctly. > > Please test other wav files and let me know of any issues. toobad I'm stuck at r20892 untill my main computer is fixed. running on an eeepc with a usb drive. If only I coyuld install on the hard drive, I could then test the fix. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 11 13:57:57 2009 From: trac at haiku-os.org (siarzhuk) Date: Thu, 11 Jun 2009 11:57:57 -0000 Subject: [Haiku-bugs] [Haiku] #1449: implement keymap switching application In-Reply-To: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> References: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> Message-ID: <049.2b283639dd2874e60a4ffed67b112f85@haiku-os.org> #1449: implement keymap switching application ----------------------------------+----------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by siarzhuk): Shouldn't this issue be closed as soon as KeymapSwitcher is available as 3rd party app? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 11 14:12:36 2009 From: trac at haiku-os.org (diver) Date: Thu, 11 Jun 2009 12:12:36 -0000 Subject: [Haiku-bugs] [Haiku] #1449: implement keymap switching application In-Reply-To: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> References: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> Message-ID: <049.fae9c74a6523215a1847eb6646a7b09d@haiku-os.org> #1449: implement keymap switching application ----------------------------------+----------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by diver): I would like to have keymap switcher preinstalled. I think that such functionality is a mandotary for an OS. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 11 14:46:17 2009 From: trac at haiku-os.org (axeld) Date: Thu, 11 Jun 2009 12:46:17 -0000 Subject: [Haiku-bugs] [Haiku] #1449: implement keymap switching application In-Reply-To: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> References: <040.63465193e0d71be4d9e6d72488e8b621@haiku-os.org> Message-ID: <049.b84275e766862b9093ffda4f6681a42d@haiku-os.org> #1449: implement keymap switching application ----------------------------------+----------------------------------------- Reporter: diver | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by axeld): Indeed, this functionality should be added to the Keyboard preferences in the future (which this ticket is about). For now, using the KeymapSwitcher is fine, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 01:51:53 2009 From: trac at haiku-os.org (HaikuBot) Date: Thu, 11 Jun 2009 23:51:53 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. Message-ID: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. ----------------------------------------+----------------------------------- Reporter: HaikuBot | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_addon_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------------+----------------------------------- Always when I shutdown or reboot laptop with Haiku, I getting error(see attachments). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 12:19:18 2009 From: trac at haiku-os.org (korli) Date: Fri, 12 Jun 2009 10:19:18 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.f35fd31458d90ed3c4c84bc4d2fa41f6@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. -----------------------------+---------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Changes (by korli): * owner: marcusoverhagen => mmlr * component: Servers/media_addon_server => Kits/Device Kit Comment: Michael, could you have a look please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 14:35:15 2009 From: trac at haiku-os.org (axeld) Date: Fri, 12 Jun 2009 12:35:15 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.7d06b3b5934a0d08b4b691d8dc02b092@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. -----------------------------+---------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by axeld): I doubt it has anything to do with USB, I would rather assume a problem in the media add-on server recently revealed by stippi's changes. I guess the add-on is unloaded early or something. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 14:50:08 2009 From: trac at haiku-os.org (stippi) Date: Fri, 12 Jun 2009 12:50:08 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.f2b8d76d665b8579b6e52e6e81cce4a5@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. -----------------------------+---------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by stippi): The changes I did have the effect that (reader and decoder) add-ons, which are no longer needed by the application, are indeed free'd. Before, any add-ons that the application actually used (i.e. more than for sniffing) would stay loaded even if a BMediaTrack/BMediaFile is released/deleted. So maybe it's something in that direction. The code in the plugin manager inside of libmedia (I think media_addon_server uses the same code) is very clean and not complex. I would not expect an error to come from there. It does little more than reference counting. I didn't have a close look a the media_addon_server code, though, I don't know if all plugin management there goes through the plugin manager. I did check libmedia, though, and there it's the case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 15:26:50 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 12 Jun 2009 13:26:50 -0000 Subject: [Haiku-bugs] [Haiku] #3641: node/163 has a bad alias In-Reply-To: <041.aa068838d0354511be617433c04a7938@haiku-os.org> References: <041.aa068838d0354511be617433c04a7938@haiku-os.org> Message-ID: <050.0698fa5584446eef98f2ad14df31fc76@haiku-os.org> #3641: node/163 has a bad alias ----------------------+----------------------------------------------------- Reporter: mmadia | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------+----------------------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: seems an alias was setup to redirect http://www.haiku- os.org/documents/dev/getting_the_source_code to http://www.haiku- os.org/documents/dev/getting_and_building_haiku_source_code some time ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 17:16:22 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 12 Jun 2009 15:16:22 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.0583ad756a9506910e5486fba4f1113b@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. -----------------------------+---------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by mmlr): It's a misuse of BUSBRoster. You have to Stop() the roster before deleting it, as it otherwise can't properly call the DeviceRemoved() hook. So before deleting the roster in the WebCamMediaAddOn destructor you simply call fRoster->Stop() first. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 17:20:05 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 12 Jun 2009 15:20:05 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.7b69f5105bb8cb9611bf59eb58433e57@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. ------------------------------+--------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31013. Please reopen if it still exists as I can't test it here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 17:50:58 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 12 Jun 2009 15:50:58 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.5c6521d81f49c766af355d38280e3320@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi Jeremy, Yes, they should be. But I don't mind if you confirm that.. ;-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 20:48:27 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 12 Jun 2009 18:48:27 -0000 Subject: [Haiku-bugs] [Haiku] #4017: media_addon_server error during Shutdown\Reboot. In-Reply-To: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> References: <043.05319245cf7ecfc8ace21cc088384400@haiku-os.org> Message-ID: <052.6640fe5d4a282eab806b5ad134bb8a52@haiku-os.org> #4017: media_addon_server error during Shutdown\Reboot. ------------------------------+--------------------------------------------- Reporter: HaikuBot | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by HaikuBot): Thanks. All fine now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 12 23:56:42 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 12 Jun 2009 21:56:42 -0000 Subject: [Haiku-bugs] [Haiku] #4018: MTRR: Clearing variable MTRRs on boot causes system freeze Message-ID: <039.ae8f99e86d3fe69c312b27cfc7d589e5@haiku-os.org> #4018: MTRR: Clearing variable MTRRs on boot causes system freeze ---------------------------+------------------------------------------------ Reporter: mmlr | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I've recently upgraded my desktop PC to 4GB of RAM. This worked for a few days without problem. After updating the BIOS/Firmware of this machine however, Haiku would hang at boot. I've tracked it down to the MTRR initialization. The system hangs when all variable MTRRs are cleared in generic_init_mtrrs() (http://dev.haiku-os.org/browser/haiku/trunk/src/add- ons/kernel/cpu/x86/generic_x86.cpp#L61) and then caches are re-enabled by clearing the cache-disable bit in cr0 (http://dev.haiku- os.org/browser/haiku/trunk/src/system/kernel/arch/x86/arch_cpu.cpp#L143). The system does not hang if either MTRRs aren't used at all (by hacking the returned count to 0 for example), if MTRRs aren't enabled again at the end of generic_init_mtrrs(), or if the MTRRs aren't cleared in generic_init_mtrrs(). From reading the specs and cross-referencing other implementations it seems that we aren't really supposed to clear whatever has been setup in the MTRRs by the BIOS/Firmware. Instead other systems seem to take the existing MTRR setup as a base and then work with that. What leads me to suspect that clearing is not intended by the specs is that it states in the MTRR examples (Example 10-2 in 10.11.3): "This setup also fulfills the requirement that two register pairs are left for operating system usage." Which could indicate that the other pairs aren't really supposed to be re-set, though it doesn't explicitly state that anywhere. Linux seems to gather all MTRR info from the boot processor first and then syncs the other processors to match if necessary. Otherwise it leaves the existing MTRRs and later extends them as needed or uses free slots for new ranges. My current work-around is to simply skip clearing MTRRs. They are later over-written by Haiku, which doesn't seem to be a problem. It only seems to be a problem when caches are enabled and there are no variable MTRRs programmed at all. Board is an Intel DG33TL with latest BIOS/Firmware, 2.4GHz Core 2 Quad, 4GB of RAM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 03:18:00 2009 From: trac at haiku-os.org (dlmcpaul) Date: Sat, 13 Jun 2009 01:18:00 -0000 Subject: [Haiku-bugs] [Haiku] #1708: Select Play from Sounds prefs freezes system In-Reply-To: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> References: <040.9716a955c37bb81a8054114e37a9c39a@haiku-os.org> Message-ID: <049.7b931542d5b2d312af3becd873e3866d@haiku-os.org> #1708: Select Play from Sounds prefs freezes system ----------------------------+----------------------------------------------- Reporter: el-al | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 2645 ----------------------------+----------------------------------------------- Changes (by dlmcpaul): * cc: dlmcpaul@? (added) * status: new => closed * resolution: => fixed Comment: I cannot reproduce this. Please confirm problem is still valid and close if not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 03:37:56 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 13 Jun 2009 01:37:56 -0000 Subject: [Haiku-bugs] [Haiku] #4018: MTRR: Clearing variable MTRRs on boot causes system freeze In-Reply-To: <039.ae8f99e86d3fe69c312b27cfc7d589e5@haiku-os.org> References: <039.ae8f99e86d3fe69c312b27cfc7d589e5@haiku-os.org> Message-ID: <048.a51f5f6c727b69a794a6c2749d28e635@haiku-os.org> #4018: MTRR: Clearing variable MTRRs on boot causes system freeze ---------------------------+------------------------------------------------ Reporter: mmlr | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: OK, I think I've found the problem. The default MTRR type is set to write- back and then the MTRRs are used to define the uncacheable memory ranges instead of the more traditional other way around. Currently looking into it, may come up with a solution. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 11:57:57 2009 From: trac at haiku-os.org (richienyhus) Date: Sat, 13 Jun 2009 09:57:57 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.486767f0c50cbc58a4a364943944d4e9@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): G'day Sorry for the delay. I added in nvidia.10de_0242_000500.0.3.log by mistake sorry. Cheers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 12:24:06 2009 From: trac at haiku-os.org (richienyhus) Date: Sat, 13 Jun 2009 10:24:06 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.40fbe0b9aa610f11d1ab65702a5671e2@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): I forgot to say this is from r30946 gcc2 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 12:35:16 2009 From: trac at haiku-os.org (richienyhus) Date: Sat, 13 Jun 2009 10:35:16 -0000 Subject: [Haiku-bugs] [Haiku] #3018: Ri-li crashes while starting In-Reply-To: <046.7c1b4d5ad1f5efb2095a03a49404973a@haiku-os.org> References: <046.7c1b4d5ad1f5efb2095a03a49404973a@haiku-os.org> Message-ID: <055.962313b8ad2b2ff4f6f4235218a89463@haiku-os.org> #3018: Ri-li crashes while starting -------------------------+-------------------------------------------------- Reporter: richienyhus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by richienyhus): Well it doesn't end in a debugger these days. Tested on r30946, With SDL-1.2.13-haiku-2 and SDL_mixer-1.2.8-haiku-2 Its has taken awhile for me to get around to retrying this... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 12:54:04 2009 From: trac at haiku-os.org (diver) Date: Sat, 13 Jun 2009 10:54:04 -0000 Subject: [Haiku-bugs] [Haiku] #4019: mime_update.sh still have /boot/beos record Message-ID: <040.6c9471ea3851bb838733ae58ade3c8e4@haiku-os.org> #4019: mime_update.sh still have /boot/beos record -----------------------+---------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- /boot/common/boot/post_install/mime_update.sh still have /boot/beos record -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 13:40:49 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 13 Jun 2009 11:40:49 -0000 Subject: [Haiku-bugs] [Haiku] #4018: MTRR: Clearing variable MTRRs on boot causes system freeze In-Reply-To: <039.ae8f99e86d3fe69c312b27cfc7d589e5@haiku-os.org> References: <039.ae8f99e86d3fe69c312b27cfc7d589e5@haiku-os.org> Message-ID: <048.04a5fbea8f43cbc8dd6d26c3a0415c4a@haiku-os.org> #4018: MTRR: Clearing variable MTRRs on boot causes system freeze ----------------------------+----------------------------------------------- Reporter: mmlr | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Fixed default type setting in r31026 and setup order in r31027. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 13:44:12 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 13 Jun 2009 11:44:12 -0000 Subject: [Haiku-bugs] [Haiku] #4013: Haiku booting breaks with "Machine-Check Exception" In-Reply-To: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> References: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> Message-ID: <057.d90509eb919facf88cdaeb181cdd28d4@haiku-os.org> #4013: Haiku booting breaks with "Machine-Check Exception" ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by mmlr): Can you check if this is fixed at r31027? From where it happens this could very well be an MTRR issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 15:49:22 2009 From: trac at haiku-os.org (fano) Date: Sat, 13 Jun 2009 13:49:22 -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.480a202f53a8460d2e635131a33029a0@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): Rudolf I've tried to boot HAIKU using only VGA to my Sony LCD monitor... something different happens.. after the Sky Rocket the screen is always black but the monitor says "Out of range 80.5 Khz / 100 Hz" particularly that 100 Hz is a very strange values... my native monitor resolution is 1280*1024 at 75 Hz maximum!!! I've booted in safe mode too... and surprise! The GUI is at 12080*1024 in VESA mode! In the screen preference I've a lot more resolution to choose, now (1024*768, 800*600 ecc...). I've tried the trick proposed by tigerdog I've select 1024*768 then rebooted...but after reboot the screen is black (again!) but not "out of range" if I see the monitor OSD is 1024*768 at 60 Hz should be right but it stays black! I've tried to reboot at 1280*1024 but the screen is always black but the screen is at 60 Hz!!! I haven't another PC to telnet to the machine so,again, I don't know if syslogS are complete, but I link it... maybe they're useful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 17:40:35 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 13 Jun 2009 15:40:35 -0000 Subject: [Haiku-bugs] [Haiku] #4020: CharacterMap should use current font in info section Message-ID: <044.dc951a08cde30e6df859facf8780d80f@haiku-os.org> #4020: CharacterMap should use current font in info section ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31031. The info section at the bottom of CharacterMap's window shows the character currently under the mouse pointer and offers its unicode values. Since here, the normal system font is used, some characters that are displayed in the character map of a selected font, are here only rendered as an outline box. I think, at least for the character itself, the same font as in the character map should be used. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 18:37:15 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 13 Jun 2009 16:37:15 -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.1208a2118f49fa6a410ffdd81e31cd4f@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 humdinger): I have one more thing to add, though I don't know if that's how the app is normally used: 8. A drag&dropped character into CharacterMap could scroll to and highlight the according character in the map. You may see a character and be interested in it's mapping, right? I dunno, your call. As always. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 21:28:23 2009 From: trac at haiku-os.org (meianoite) Date: Sat, 13 Jun 2009 19:28:23 -0000 Subject: [Haiku-bugs] [Haiku] #3999: Boot hangs (with a twist) as ohci driver tries to take ownership In-Reply-To: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> References: <044.f3f968229a44a2b8f7c30aa95dd8c270@haiku-os.org> Message-ID: <053.1c2e9b0998bd538453d46125f761c44a@haiku-os.org> #3999: Boot hangs (with a twist) as ohci driver tries to take ownership -----------------------+---------------------------------------------------- Reporter: meianoite | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by meianoite): I just found out that disabling C1E (option AMD CPU C1E Support) on the BIOS allows the boot to proceed. So yes, some interrupt is being missed with C1E turned on. Info on C1E: http://ixbtlabs.com/articles2/intel-thermal- features-2/ehs.html Feel free to repurpose this ticket to the appropriate component/owner if that's the case; still, if ohci is disabled the boot continues as well, and this might hint at the reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 13 21:57:48 2009 From: trac at haiku-os.org (stippi) Date: Sat, 13 Jun 2009 19:57:48 -0000 Subject: [Haiku-bugs] [Haiku] #4021: libmedia.so: we are doomed Message-ID: <041.188da0cd5093aef35e1ac72c9c69cc27@haiku-os.org> #4021: libmedia.so: we are doomed ----------------------------+----------------------------------------------- Reporter: stippi | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- I am currently debugging something else, which makes me launch and crash a media application all the time. This means I am not properly cleaning up the media resources this application allocates. Now I have just triggered src/kits/media/SharedBufferList.cpp:136, and that makes me wonder whether the media_server is properly cleaning up after crashed applications. It should definitely free any resources this application has requested from the server. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 00:08:28 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 13 Jun 2009 22:08:28 -0000 Subject: [Haiku-bugs] [Haiku] #4019: mime_update.sh still have /boot/beos record In-Reply-To: <040.6c9471ea3851bb838733ae58ade3c8e4@haiku-os.org> References: <040.6c9471ea3851bb838733ae58ade3c8e4@haiku-os.org> Message-ID: <049.f5888a48e5410d57562909391f7e4a90@haiku-os.org> #4019: mime_update.sh still have /boot/beos record ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r31037. Thanks for reporting! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 03:14:23 2009 From: trac at haiku-os.org (tigerdog) Date: Sun, 14 Jun 2009 01:14:23 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.6c9e522f1cd034f7df5c057359a61838@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 tigerdog): Fano, you are seeing behavior similar to what I see except that it works for me after the second boot. One possible difference; I'm not using a laptop, I'm using the analog output of my graphics card. Rudolph, to answer your question, I believe when starting out of range, my card is setting to 2048x1536 (not sure of second number) I think this is so because that resolution is invalid for my monitor but DOES show as a choice of "safe mode" video resolution if I go into boot-up options. 1920x1200 (monitor native mode) is not in that list. I hope this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 02:37:22 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 14 Jun 2009 00:37:22 -0000 Subject: [Haiku-bugs] [Haiku] #3427: bad clipping in Media preflet In-Reply-To: <040.d9188e41c6cf656bf939dfc1b09f1d1d@haiku-os.org> References: <040.d9188e41c6cf656bf939dfc1b09f1d1d@haiku-os.org> Message-ID: <049.0e86612534ac84bf8d5c9eeb46c75f52@haiku-os.org> #3427: bad clipping in Media preflet --------------------------------+------------------------------------------- Reporter: luroh | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r31038. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 03:43:15 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 14 Jun 2009 01:43:15 -0000 Subject: [Haiku-bugs] [Haiku] #4008: Detecting bitmaps with enough Translators will corrupt memory. In-Reply-To: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> References: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> Message-ID: <050.8174a20604cdf3746c4b614673b83a89@haiku-os.org> #4008: Detecting bitmaps with enough Translators will corrupt memory. -----------------------------------+---------------------------------------- Reporter: stippi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/runtime_loader | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by bonefish): * component: Add-Ons/Translators => System/runtime_loader * milestone: R1 => R1/alpha1 Comment: Quite likely a runtime loader problem. It maps the segments of a shared object individually, usually letting the kernel choose the base address of the first segment and using B_EXACT_ADDRESS for the second one. That is a problem, since the kernel could pick an address that is fine for the first segment, but which leaves insufficient room for the second segment. Since _kern_map_file() has mmap() semantics, mapping the second segment would just unmap areas that are in the way. In case of the reported problem the victim might be an innocent bitmap. Two suggested changes: - _kern_map_file() should be extended to allow disabling the unmapping feature and the runtime loader should use it that way. - The runtime loader should not map the segments individually, respectively first reserve an address range for all segments. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 06:01:13 2009 From: trac at haiku-os.org (leavengood) Date: Sun, 14 Jun 2009 04:01:13 -0000 Subject: [Haiku-bugs] [Haiku] #3753: The title of an inactive terminal tab isn't updated In-Reply-To: <039.45b129fbc58beb3f22b1723cab9454f3@haiku-os.org> References: <039.45b129fbc58beb3f22b1723cab9454f3@haiku-os.org> Message-ID: <048.03f817ecd79af384308e1ffafd1f7844@haiku-os.org> #3753: The title of an inactive terminal tab isn't updated -----------------------------------+---------------------------------------- Reporter: heto | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by leavengood): I've been researching tabs lately for the browser project and I looked over the BTabView code, and it indeed will stop detaching views if a BCardLayout is present. It just delegates to the card layout to hide and show the views as the tabs are selected. So as Stephan says switching to using layout management (well at least using a card layout) would probably fix this issue. Of course the terminal GUI does some off-by-one manual layout tricks to make the scrollbar look better and I am not sure how that would be affected by using layout management. Guess we will see if and when someone tries. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 09:03:58 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 14 Jun 2009 07:03:58 -0000 Subject: [Haiku-bugs] [Haiku] #4022: Deleted keymaps stay in the panel until it's restarted Message-ID: <044.0f416aa17f88e7128474c3529b040183@haiku-os.org> #4022: Deleted keymaps stay in the panel until it's restarted --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r31031. If you save a customized keymap, it'll appear in the "User" list in the bottom left. If you delete that map while the Keymap panel is still open, the entry will still be there, though not selectable. I guess this calls for node monitoring. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 09:16:03 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 14 Jun 2009 07:16:03 -0000 Subject: [Haiku-bugs] [Haiku] #4023: NumLock and CapsLock don't change keymap correctly Message-ID: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> #4023: NumLock and CapsLock don't change keymap correctly --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r31031. Pressing the NumLock key changes the keymap as expected. But pressing it again, thereby unlocking the num-pad, doesn't change the keymap back. That's only done after another key is pressed. (On my keyboard is a "Pause" key that acts under Haiku just like the NumLock key. Contrary to the above described, this one works as expected...) Pressing the CapsLock key, does not change the keymap as expected. Only after pressing another key it will change. Pressing CapsLock again to unlock then works again as expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 09:26:17 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 14 Jun 2009 07:26:17 -0000 Subject: [Haiku-bugs] [Haiku] #4024: Abbreviate special keys in Keymap panel Message-ID: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> #4024: Abbreviate special keys in Keymap panel --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r31031. You need a horizontally very large Keymap window to display all keys untruncated. I'd propose to use abbreviations where possible: CAPS LOCK -> CAPS NUM LOCK -> NUM CONTROL -> CTRL OPTION -> OPT COMMAND -> COM PAGE ↑ -> PG ↑ PAGE ↓ -> PG ↓ It'd also be a good idea to somehow get rid of the list views to the left. But where to put it...? Below the keymap? Dunno... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 09:31:53 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 14 Jun 2009 07:31:53 -0000 Subject: [Haiku-bugs] [Haiku] #4025: Change Shortcut-Switch to drop-down menu Message-ID: <044.b8e054b54e095792dead89014c3de438@haiku-os.org> #4025: Change Shortcut-Switch to drop-down menu --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r31031. Having a button for switching shortcut keys (ALT<->CTRL) that changes its lable is confusing IMO. I think it's better to use a drop-down menu with "Shortcut Key in Windows/Linux Mode [CTRL-picto]"[[BR]] "Shortcut Key in Haiku Mode [ALT-picto]" That way you have the available option at one glance. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 10:38:49 2009 From: trac at haiku-os.org (e_barsukowski) Date: Sun, 14 Jun 2009 08:38:49 -0000 Subject: [Haiku-bugs] [Haiku] #4013: Haiku booting breaks with "Machine-Check Exception" In-Reply-To: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> References: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> Message-ID: <057.d6d446a8e4555ca2e58d94498c2032e7@haiku-os.org> #4013: Haiku booting breaks with "Machine-Check Exception" ---------------------------+------------------------------------------------ Reporter: e_barsukowski | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by e_barsukowski): I've updated to r31038 and it works! Haiku boots without problems. Thank you! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 12:47:50 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 14 Jun 2009 10:47:50 -0000 Subject: [Haiku-bugs] [Haiku] #4013: Haiku booting breaks with "Machine-Check Exception" In-Reply-To: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> References: <048.a3a4a95b97551dd97f642a1fa45959b1@haiku-os.org> Message-ID: <057.525ea0c5b395cf5c277adc016cebb083@haiku-os.org> #4013: Haiku booting breaks with "Machine-Check Exception" ----------------------------+----------------------------------------------- Reporter: e_barsukowski | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Thanks for the upsate! Fixed as part of recent MTRR changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 13:14:03 2009 From: trac at haiku-os.org (stippi) Date: Sun, 14 Jun 2009 11:14:03 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.e596f9d43c73f36a33ccc24cef6aad13@haiku-os.org> #3978: Update install from CD fails at r30914 -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 3994 -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r31042. However, the Installer will still merge all existing folders besides /system. That will probably give you a mess in /develop. However, you need to know what you are doing anyways, for example installing the Be Developer Tools will overwrite the Haiku headers with BeOS versions. I've seen such a problem the other day. If you want to avoid problems like that, you should backup and then remove/rename existing folders where you need a clean installation as a start. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 13:15:24 2009 From: trac at haiku-os.org (stippi) Date: Sun, 14 Jun 2009 11:15:24 -0000 Subject: [Haiku-bugs] [Haiku] #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" In-Reply-To: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> References: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> Message-ID: <049.598cee2fd012f129b083e06cde46dc19@haiku-os.org> #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: The logo is centered vertically on purpose. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 13:17:16 2009 From: trac at haiku-os.org (stippi) Date: Sun, 14 Jun 2009 11:17:16 -0000 Subject: [Haiku-bugs] [Haiku] #3893: [Installer] "Please Choose Target" menu item is truncated In-Reply-To: <040.d33713ecdd3e8632fa208ee0d40849e6@haiku-os.org> References: <040.d33713ecdd3e8632fa208ee0d40849e6@haiku-os.org> Message-ID: <049.58d5e75b19c81bc78b779ef495984265@haiku-os.org> #3893: [Installer] "Please Choose Target" menu item is truncated ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): It looks fine in the screenshot. What do you mean? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 13:18:56 2009 From: trac at haiku-os.org (stippi) Date: Sun, 14 Jun 2009 11:18:56 -0000 Subject: [Haiku-bugs] [Haiku] #3709: Installer: Add clean install / archive and clean install option In-Reply-To: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> References: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> Message-ID: <049.070951b1c660d6195291572d702fdede@haiku-os.org> #3709: Installer: Add clean install / archive and clean install option ------------------------------------+--------------------------------------- Reporter: rossi | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): In r31042, I implemented that /system is always a clean copy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 13:21:23 2009 From: trac at haiku-os.org (stippi) Date: Sun, 14 Jun 2009 11:21:23 -0000 Subject: [Haiku-bugs] [Haiku] #3672: Installer should reuse DriveSetup's visual partition view In-Reply-To: <048.9be3499a26e8c5add1fbbfba4a1c77ba@haiku-os.org> References: <048.9be3499a26e8c5add1fbbfba4a1c77ba@haiku-os.org> Message-ID: <057.c5eeb3968373cd154043799e39a55413@haiku-os.org> #3672: Installer should reuse DriveSetup's visual partition view ------------------------------------+--------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): The target menu is now much cleaner and DriveSetup is much easier to reach from the Installer, to validate the wanted partition. Is this ticket still valid then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 17:54:00 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 14 Jun 2009 15:54:00 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.b8a782a248c07ccd44d20bb5b1c312ca@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, Thanks! Hmm, still none of your I2C buses work. Strange. At the moment I have no further ideas of how to proceed here :-/ If I think of something I'll report back here.. Bye! Rudolf. BTW: would you have another screen there to test with to see if that works as it should? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 18:15:46 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 14 Jun 2009 16:15:46 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.f58121969930f478887d458893e2b5c3@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 rudolfc): Hmm, If you all have a 4:3 screen and have force_ws disabled now by using a modified nvidia.settings, I think maybe the DAC PLL simply won't lock a calculated frequency for the refresh. I think we should rule that out: i'll upload a modified version of the driver here that won't program the PLL's so you can test that. This means however, that you should make sure that the choosen resolution at boot time is the same as is used for the desktop. If the boot would succeed with this modified driver, then don't change the resolution of your desktop since otherwise the screen would go black again. I'll compile the driver with gcc2 over here. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 20:46:00 2009 From: trac at haiku-os.org (myob) Date: Sun, 14 Jun 2009 18:46:00 -0000 Subject: [Haiku-bugs] [Haiku] #4026: Minor typo in CPUFrequency preflet Message-ID: <039.73809ac49b37d35ebad476fb33c8bd12@haiku-os.org> #4026: Minor typo in CPUFrequency preflet -------------------------+-------------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- "Low Energie" should be "Low Energy". patch attached... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 21:33:38 2009 From: trac at haiku-os.org (GeneralMaximus) Date: Sun, 14 Jun 2009 19:33:38 -0000 Subject: [Haiku-bugs] [Haiku] #4027: [patch] Added CLucene as an OptionalPackage Message-ID: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> #4027: [patch] Added CLucene as an OptionalPackage ----------------------------+----------------------------------------------- Reporter: GeneralMaximus | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------+----------------------------------------------- Added CLucene to the list of OptionalPackages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 22:01:52 2009 From: trac at haiku-os.org (luroh) Date: Sun, 14 Jun 2009 20:01:52 -0000 Subject: [Haiku-bugs] [Haiku] #3427: bad clipping in Media preflet In-Reply-To: <040.d9188e41c6cf656bf939dfc1b09f1d1d@haiku-os.org> References: <040.d9188e41c6cf656bf939dfc1b09f1d1d@haiku-os.org> Message-ID: <049.b53fa03e82ce139c2fdf4890e43ac44d@haiku-os.org> #3427: bad clipping in Media preflet --------------------------------+------------------------------------------- Reporter: luroh | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by luroh): Confirmed, thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 23:03:00 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 14 Jun 2009 21:03:00 -0000 Subject: [Haiku-bugs] [Haiku] #4028: Hybrid GPT/MBR Initial Program Loader Message-ID: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> #4028: Hybrid GPT/MBR Initial Program Loader --------------------------+------------------------------------------------- Reporter: meianoite | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Attached is a 512 byte PMBR boot loader that looks for the UUID of a Haiku GPT partition and boots it, falling back to MBR partitions if said UUID isn't found or if the (primary) GPT is corrupted or non-existent. Its usefulness is in being a generalised IPL that supports both partitioning styles, allowing it to be used transparently and even allowing disks to be converted from one partitioning style to the other with ease, should the need for more partitions or volumes over 2TiB arise (for instance when cloning an older disk to a newer, more capacious one). It also paves the way for Haiku to create and support booting from multiple volumes larger than 2TiB, which we're in the very privileged position of enjoying efficiently in the near future due to BFS. Another use case is taking a disk from a Intel EFI machine, plugging it on a BIOS machine and boot just fine; and vice-versa. As mentioned, if there are valid partitions defined in the MBR, and the primary GPT becomes corrupt, it can fall back to loading the MBR partition with the active flag set, if one is defined. Currently there's no provision for falling back to the GPT copy that lives in the end of the disk, due to the 512 bytes constraint; supporting this would require either some major refactoring of the code or disabling the support for booting from MBR using calls to int13h other than function 4200h, "LBA Read from Disk". It was tested on emulators and on my actual, proper computer. It can load Windows, Haiku and FreeBSD; the number of sectors to load from the partition is adjustable, but beware that int13h 4200h only supports up to 127 (0x7f) sectors, or a loader of almost 64KiB; so don't specify a larger number. This is not checked on the code, again because of space constraints. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 23:05:23 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 14 Jun 2009 21:05:23 -0000 Subject: [Haiku-bugs] [Haiku] #4028: Hybrid GPT/MBR Initial Program Loader In-Reply-To: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> References: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> Message-ID: <053.4bd343375ad190bb1d0e95472d48f12e@haiku-os.org> #4028: Hybrid GPT/MBR Initial Program Loader --------------------------+------------------------------------------------- Reporter: meianoite | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Description changed by meianoite: Old description: > Attached is a 512 byte PMBR boot loader that looks for the UUID of a > Haiku GPT partition and boots it, falling back to MBR partitions if said > UUID isn't found or if the (primary) GPT is corrupted or non-existent. > Its usefulness is in being a generalised IPL that supports both > partitioning styles, allowing it to be used transparently and even > allowing disks to be converted from one partitioning style to the other > with ease, should the need for more partitions or volumes over 2TiB arise > (for instance when cloning an older disk to a newer, more capacious one). > It also paves the way for Haiku to create and support booting from > multiple volumes larger than 2TiB, which we're in the very privileged > position of enjoying efficiently in the near future due to BFS. Another > use case is taking a disk from a Intel EFI machine, plugging it on a BIOS > machine and boot just fine; and vice-versa. > As mentioned, if there are valid partitions defined in the MBR, > and the primary GPT becomes corrupt, it can fall back to loading the MBR > partition with the active flag set, if one is defined. > Currently there's no provision for falling back to the GPT copy > that lives in the end of the disk, due to the 512 bytes constraint; > supporting this would require either some major refactoring of the code > or disabling the support for booting from MBR using calls to int13h other > than function 4200h, "LBA Read from Disk". > > It was tested on emulators and on my actual, proper computer. It > can load Windows, Haiku and FreeBSD; the number of sectors to load from > the partition is adjustable, but beware that int13h 4200h only supports > up to 127 (0x7f) sectors, or a loader of almost 64KiB; so don't specify a > larger number. This is not checked on the code, again because of space > constraints. New description: Attached is a 512 byte PMBR boot loader that looks for the UUID of a Haiku GPT partition and boots it, falling back to MBR partitions if said UUID isn't found or if the (primary) GPT is corrupted or non-existent. Its usefulness is in being a generalised IPL that supports both partitioning styles, allowing it to be used transparently and even allowing disks to be converted from one partitioning style to the other with ease, should the need for more partitions or volumes over 2TiB arise (for instance when cloning an older disk to a newer, more capacious one). It also paves the way for Haiku to create and support booting from multiple volumes larger than 2TiB, which we're in the very privileged position of enjoying efficiently in the near future due to BFS. Another use case is taking a disk from a Intel EFI machine, plugging it on a BIOS machine and boot just fine; and vice-versa. As mentioned, if there are valid partitions defined in the MBR, and the primary GPT becomes corrupt, it can fall back to loading the MBR partition with the active flag set, if one is defined. Currently there's no provision for falling back to the GPT copy that lives in the end of the disk, due to the 512 bytes constraint; supporting this would require either some major refactoring of the code or disabling the support for booting from MBR using calls to int13h other than function 4200h, "LBA Read from Disk". It was tested on emulators and on my actual, proper computer. It can load Windows, Haiku and FreeBSD; the number of sectors to load from the partition is adjustable, but beware that int13h 4200h only supports up to 127 (0x7f) sectors, or a loader of almost 64KiB; so don't specify a larger number. This is not checked on the code, again because of space constraints. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 14 23:21:38 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 14 Jun 2009 21:21:38 -0000 Subject: [Haiku-bugs] [Haiku] #4028: Hybrid GPT/MBR Initial Program Loader In-Reply-To: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> References: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> Message-ID: <053.c3cf3961e6cdea1138f987ed68e48a4b@haiku-os.org> #4028: Hybrid GPT/MBR Initial Program Loader --------------------------+------------------------------------------------- Reporter: meianoite | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems | 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 Sun Jun 14 23:33:16 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 14 Jun 2009 21:33:16 -0000 Subject: [Haiku-bugs] [Haiku] #1429: Icons for some of the servers use old style. In-Reply-To: <042.1555660311752b958e3000bceb70de58@haiku-os.org> References: <042.1555660311752b958e3000bceb70de58@haiku-os.org> Message-ID: <051.a4db8a8b6e5cf20e578182319b9f6c73@haiku-os.org> #1429: Icons for some of the servers use old style. ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by scottmc): The idea icon has now been updated. I have attached a couple more screenshots showing some of the few icons that still need updating... CortexAddOnHost and spamdbm which are in the system/bin folder, and app_server, midi_server, and print_server in the servers folder. Also cddb_daemon, fake_app_server and net_server are using the default app icon, bonus points for adding specific icons any of those. ;) Anyone spot any others that are old style? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 00:02:23 2009 From: trac at haiku-os.org (meianoite) Date: Sun, 14 Jun 2009 22:02:23 -0000 Subject: [Haiku-bugs] [Haiku] #4028: Hybrid GPT/MBR Initial Program Loader In-Reply-To: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> References: <044.d237cba059fc119ecb8631bcc2abee76@haiku-os.org> Message-ID: <053.f57b170a553328ee1e7eb5613ce4e865@haiku-os.org> #4028: Hybrid GPT/MBR Initial Program Loader --------------------------+------------------------------------------------- Reporter: meianoite | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Description changed by meianoite: Old description: > Attached is a 512 byte PMBR boot loader that looks for the UUID of a > Haiku GPT partition and boots it, falling back to MBR partitions if said > UUID isn't found or if the (primary) GPT is corrupted or non-existent. > > Its usefulness is in being a generalised IPL that supports both > partitioning styles, allowing it to be used transparently and even > allowing disks to be converted from one partitioning style to the other > with ease, should the need for more partitions or volumes over 2TiB arise > (for instance when cloning an older disk to a newer, more capacious one). > > It also paves the way for Haiku to create and support booting from > multiple volumes larger than 2TiB, which we're in the very privileged > position of enjoying efficiently in the near future due to BFS. Another > use case is taking a disk from a Intel EFI machine, plugging it on a BIOS > machine and boot just fine; and vice-versa. > > As mentioned, if there are valid partitions defined in the MBR, and the > primary GPT becomes corrupt, it can fall back to loading the MBR > partition with the active flag set, if one is defined. > > Currently there's no provision for falling back to the GPT copy that > lives in the end of the disk, due to the 512 bytes constraint; supporting > this would require either some major refactoring of the code or disabling > the support for booting from MBR using calls to int13h other than > function 4200h, "LBA Read from Disk". > > It was tested on emulators and on my actual, proper computer. It can load > Windows, Haiku and FreeBSD; the number of sectors to load from the > partition is adjustable, but beware that int13h 4200h only supports up to > 127 (0x7f) sectors, or a loader of almost 64KiB; so don't specify a > larger number. This is not checked on the code, again because of space > constraints. New description: Attached is a 512 byte PMBR boot loader that looks for the UUID of a Haiku GPT partition and boots it, falling back to MBR partitions if said UUID isn't found or if the (primary) GPT is corrupted or non-existent. Its usefulness is in being a generalised IPL that supports both partitioning styles, allowing it to be used transparently and even allowing disks to be converted from one partitioning style to the other with ease, should the need for more partitions or volumes over 2TiB arise (for instance when cloning an older disk to a newer, more capacious one). It also paves the way for Haiku to create and support booting from multiple volumes larger than 2TiB, which we're in the very privileged position of enjoying efficiently in the near future due to BFS. Another use case is taking a disk from a Intel EFI machine, plugging it on a BIOS machine and boot just fine; and vice-versa. As mentioned, if there are valid partitions defined in the MBR, and the primary GPT becomes corrupt, it can fall back to loading the MBR partition with the active flag set, if one is defined. Currently there's no provision for falling back to the GPT copy that lives in the end of the disk, due to the 512 bytes constraint; supporting this would require either some major refactoring of the code or disabling the support for booting from MBR using calls to int13h other than function 4200h, "LBA Read from Disk". It was tested on emulators and on my actual, proper computer. Loading Windows, Haiku and FreeBSD was tested (UUID must be changed accordingly, of course); for the GPT boot, the number of sectors to load from the partition is adjustable (needed by FreeBSD's "gptloader" on a freebsd-boot UUID partition), probably needed by Haiku as well since stage1 is 2 sectors big), but beware that int13h 4200h only supports up to 127 (0x7f) sectors, or a loader of almost 64KiB; so don't specify a larger number. This is not checked on the code, again because of space constraints. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 01:01:50 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 14 Jun 2009 23:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #4029: pthread_cancel() not yet implemented Message-ID: <042.7aacb771bc14955107f1d1961a9d72bb@haiku-os.org> #4029: pthread_cancel() not yet implemented -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When running a recently porting app called ironically enough "axel" we get a message after a download completes saying that pthread_cancel() not yet implemented. I see that it's marked as a TODO in the code.[[BR]] http://ports.haiku-files.org/wiki/net-misc/axel/2.4/1[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 02:10:54 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 15 Jun 2009 00:10:54 -0000 Subject: [Haiku-bugs] [Haiku] #4027: [patch] Added CLucene as an OptionalPackage In-Reply-To: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> References: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> Message-ID: <058.ef31e89f19e9b66c3c7e94372d61b189@haiku-os.org> #4027: [patch] Added CLucene as an OptionalPackage ----------------------------+----------------------------------------------- Reporter: GeneralMaximus | Owner: anevilyak Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------+----------------------------------------------- Changes (by anevilyak): * owner: bonefish => anevilyak -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 02:13:50 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 15 Jun 2009 00:13:50 -0000 Subject: [Haiku-bugs] [Haiku] #4027: [patch] Added CLucene as an OptionalPackage In-Reply-To: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> References: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> Message-ID: <058.383a9c2c70627aae873f5d8c9bf29588@haiku-os.org> #4027: [patch] Added CLucene as an OptionalPackage -----------------------------+---------------------------------------------- Reporter: GeneralMaximus | Owner: anevilyak Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------+---------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Applied in r30155, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 02:14:10 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 15 Jun 2009 00:14:10 -0000 Subject: [Haiku-bugs] [Haiku] #4027: [patch] Added CLucene as an OptionalPackage In-Reply-To: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> References: <049.caeea579a2408d89c99b312b9a0e0635@haiku-os.org> Message-ID: <058.a7ae83a7c124496289647697d983ae67@haiku-os.org> #4027: [patch] Added CLucene as an OptionalPackage -----------------------------+---------------------------------------------- Reporter: GeneralMaximus | Owner: anevilyak Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------+---------------------------------------------- Comment(by anevilyak): That should've of course been r31055... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 10:03:51 2009 From: trac at haiku-os.org (axeld) Date: Mon, 15 Jun 2009 08:03:51 -0000 Subject: [Haiku-bugs] [Haiku] #4025: Change Shortcut-Switch to drop-down menu In-Reply-To: <044.b8e054b54e095792dead89014c3de438@haiku-os.org> References: <044.b8e054b54e095792dead89014c3de438@haiku-os.org> Message-ID: <053.04653f0c234369ee77a7473e0f866449@haiku-os.org> #4025: Change Shortcut-Switch to drop-down menu ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Depending on your keymap, there is neither a Haiku nor a Windows/Linux mode - but you can still switch the shortcut key. In any case, a drop-down menu cannot solve this. Other ideas are welcome, of course :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 10:07:05 2009 From: trac at haiku-os.org (axeld) Date: Mon, 15 Jun 2009 08:07:05 -0000 Subject: [Haiku-bugs] [Haiku] #4024: Abbreviate special keys in Keymap panel In-Reply-To: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> References: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> Message-ID: <053.b40e2510faf775d8311c1b3ea523c1f8@haiku-os.org> #4024: Abbreviate special keys in Keymap panel --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): You're obviously not a friend of wide windows ;-) The current state of Keymap is only a transitional one, anyway, even if the stuff on the right is in a good shape to stay (besides the dead key handling, that is). Other than that, the plan is to merge the stuff from Keyboard, multiple keyboard support, and a keymap switcher, as well defining system wide shortcuts into one keyboard panel. In any way, having defined abbreviations is a good idea. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 11:34:05 2009 From: trac at haiku-os.org (titer) Date: Mon, 15 Jun 2009 09:34:05 -0000 Subject: [Haiku-bugs] [Haiku] #4029: pthread_cancel() not yet implemented In-Reply-To: <042.7aacb771bc14955107f1d1961a9d72bb@haiku-os.org> References: <042.7aacb771bc14955107f1d1961a9d72bb@haiku-os.org> Message-ID: <051.9c55fa5f52d2d2aafe06bc1ffd509c1d@haiku-os.org> #4029: pthread_cancel() not yet implemented -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by titer): * cc: eric.petit@? (added) Comment: pthread_cancel will also be required for VLC >= 1.0.0 - adding myself to watchers -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 12:42:02 2009 From: trac at haiku-os.org (axeld) Date: Mon, 15 Jun 2009 10:42:02 -0000 Subject: [Haiku-bugs] [Haiku] #4029: pthread_cancel() not yet implemented In-Reply-To: <042.7aacb771bc14955107f1d1961a9d72bb@haiku-os.org> References: <042.7aacb771bc14955107f1d1961a9d72bb@haiku-os.org> Message-ID: <051.965ccdfc9841fd8796db46045975ee8b@haiku-os.org> #4029: pthread_cancel() not yet implemented -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => high * component: - General => System/libroot.so -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 12:51:52 2009 From: trac at haiku-os.org (axeld) Date: Mon, 15 Jun 2009 10:51:52 -0000 Subject: [Haiku-bugs] [Haiku] #4026: Minor typo in CPUFrequency preflet In-Reply-To: <039.73809ac49b37d35ebad476fb33c8bd12@haiku-os.org> References: <039.73809ac49b37d35ebad476fb33c8bd12@haiku-os.org> Message-ID: <048.07417f7fa114b343dbc04578a065fb87@haiku-os.org> #4026: Minor typo in CPUFrequency preflet --------------------------+------------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks, fixed in r31058. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 14:43:43 2009 From: trac at haiku-os.org (axeld) Date: Mon, 15 Jun 2009 12:43:43 -0000 Subject: [Haiku-bugs] [Haiku] #4023: NumLock and CapsLock don't change keymap correctly In-Reply-To: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> References: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> Message-ID: <053.c4ca7f1e60e482e5a0007265ba992dff@haiku-os.org> #4023: NumLock and CapsLock don't change keymap correctly --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): I cannot reproduce this with VMware at least. On what hardware are you testing? And is this a USB keyboard? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 15:43:32 2009 From: trac at haiku-os.org (zooey) Date: Mon, 15 Jun 2009 13:43:32 -0000 Subject: [Haiku-bugs] [Haiku] #3136: 'long double' comparison against 0 does not work In-Reply-To: <042.b476766332fcbd8c83829395d435e27a@haiku-os.org> References: <042.b476766332fcbd8c83829395d435e27a@haiku-os.org> Message-ID: <051.1597cb5b1ae2e2bbbedb1c7b64ae4deb@haiku-os.org> #3136: 'long double' comparison against 0 does not work ------------------------+--------------------------------------------------- Reporter: bhaible | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by zooey): * status: new => closed * resolution: => invalid Comment: Well, it's been a while ... I have not been able to reproduce this, the given program just works with both r28400 and head (r31058), checking the last two versions of gcc2 (20081024 and 20080313), running on vmware and native. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:03:03 2009 From: trac at haiku-os.org (idefix) Date: Mon, 15 Jun 2009 14:03:03 -0000 Subject: [Haiku-bugs] [Haiku] #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" In-Reply-To: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> References: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> Message-ID: <049.295a4258bd40dc78854e7cb148e8d354@haiku-os.org> #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by idefix): The real problem here is that the window doesn't resize back to it's initial size when collapsing the 'Optional Packages'-field. See the attached screenshots: - Installer1.png: The Installer window after starting the program - Installer2.png: Clicked on the 'Show Optional Packages'-triangle - Installer3.png: Clicked on the 'Hide Optional Packages'-triangle -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:21:23 2009 From: trac at haiku-os.org (idefix) Date: Mon, 15 Jun 2009 14:21:23 -0000 Subject: [Haiku-bugs] [Haiku] #3709: Installer: Add clean install / archive and clean install option In-Reply-To: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> References: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> Message-ID: <049.6cdea971b50c9d29acceca2ce3a117c8@haiku-os.org> #3709: Installer: Add clean install / archive and clean install option ------------------------------------+--------------------------------------- Reporter: rossi | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by idefix): According to the notice, Installer will merge all folders (except system) and when a conflict occurs it will overwrite the files on the target volume with the files on the source volume.[[BR]] While this is fine for most folders, I would prefer it wouldn't do that for the home folder. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:40:12 2009 From: trac at haiku-os.org (stippi) Date: Mon, 15 Jun 2009 14:40:12 -0000 Subject: [Haiku-bugs] [Haiku] #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" In-Reply-To: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> References: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> Message-ID: <049.e6dd1180abefa7bd71445e9f7723632f@haiku-os.org> #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by stippi): I am aware of that, but why is it a problem? I think it's ok, after all, there is less visual noise if the window doesn't snap back. And the user may have resized it himself, in which case the window shouldn't snap back. But I would be ok with reopening the bug, too, if more people think it's not elegant enough. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:45:45 2009 From: trac at haiku-os.org (stippi) Date: Mon, 15 Jun 2009 14:45:45 -0000 Subject: [Haiku-bugs] [Haiku] #3709: Installer: Add clean install / archive and clean install option In-Reply-To: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> References: <040.458c0d7c0539de1558701257c2f78301@haiku-os.org> Message-ID: <049.761a6dbc7a861bc72bd454c18dfe710c@haiku-os.org> #3709: Installer: Add clean install / archive and clean install option ------------------------------------+--------------------------------------- Reporter: rossi | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): For the CD installation, this wouldn't be a problem, since the home folder on the CD doesn't contain much anyways. But when installing from another source, I agree it could be a problem. Maybe we should simply have this as an option. In any case, the Installer is really just copying things. It's easy enough to boot into Live-CD mode and copy any folders one needs, or leave out folders one doesn't need. And the Installer can still be used to make something bootable and nothing else. In the future, I also want to make it easy to reach Bootman from the Installer as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:54:19 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 15 Jun 2009 14:54:19 -0000 Subject: [Haiku-bugs] [Haiku] #4025: Change Shortcut-Switch to drop-down menu In-Reply-To: <044.b8e054b54e095792dead89014c3de438@haiku-os.org> References: <044.b8e054b54e095792dead89014c3de438@haiku-os.org> Message-ID: <053.f2c680c461ea0cb444ab3b1af5ad88c6@haiku-os.org> #4025: Change Shortcut-Switch to drop-down menu ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by humdinger): Well, for the stated reasons, a drop-down menu would be at least better than a changing button. Of course the problem you mention for special keymaps will remain. Maybe we can leave out the explicit option altogether. Have the COMMAND key with a red background and a bubble help saying "Shortcut key, e.g. CMD+C to copy". Then the user can put that key whereever she likes. BTW, I think exchanging keys should be left-click-drag&drop as it's less destructive and more often used than copying. The other specially coloured keys could get a bubble help as well. Maybe a little hint above the keyboard map is in order, or the newbie who doesn't read the user guide won't know what to do. Like, "Left-drag&drop to switch two keys. Right-drag&drop to copy a key.", and a legend: red: Shrortcut key, blue: Dead key. Or is that too much? Then a "RTFM" with a link to the user guide page would be more concise... :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 16:59:27 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 15 Jun 2009 14:59:27 -0000 Subject: [Haiku-bugs] [Haiku] #4024: Abbreviate special keys in Keymap panel In-Reply-To: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> References: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> Message-ID: <053.26ab3bcefc5cfa01b760563c39750877@haiku-os.org> #4024: Abbreviate special keys in Keymap panel --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by humdinger): Wide windows only where absolutely necessary. :) OK, I'll wait for maybe abbreviated keys for a new screenshot for the user guide (no pressure!) and make the changes I've already done to that topic and leave it with that for the time being. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 17:01:41 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 15 Jun 2009 15:01:41 -0000 Subject: [Haiku-bugs] [Haiku] #4024: Abbreviate special keys in Keymap panel In-Reply-To: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> References: <044.d70e45c0e481d6d6253ccc4024472544@haiku-os.org> Message-ID: <053.e904b2235cf8aa8fcb475d0e01e158dd@haiku-os.org> #4024: Abbreviate special keys in Keymap panel --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Description changed by humdinger: Old description: > This is r31031. > > You need a horizontally very large Keymap window to display all keys > untruncated. I'd propose to use abbreviations where possible: > > CAPS LOCK -> CAPS > NUM LOCK -> NUM > CONTROL -> CTRL > OPTION -> OPT > COMMAND -> COM > PAGE ↑ -> PG ↑ > PAGE ↓ -> PG ↓ > > It'd also be a good idea to somehow get rid of the list views to the > left. But where to put it...? Below the keymap? Dunno... New description: This is r31031. You need a horizontally very large Keymap window to display all keys untruncated. I'd propose to use abbreviations where possible: CAPS LOCK -> CAPS[[BR]] NUM LOCK -> NUM[[BR]] CONTROL -> CTRL[[BR]] OPTION -> OPT[[BR]] COMMAND -> COM[[BR]] PAGE ? -> PG ?[[BR]] PAGE ? -> PG ?[[BR]] It'd also be a good idea to somehow get rid of the list views to the left. But where to put it...? Below the keymap? Dunno... -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 17:04:46 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 15 Jun 2009 15:04:46 -0000 Subject: [Haiku-bugs] [Haiku] #4023: NumLock and CapsLock don't change keymap correctly In-Reply-To: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> References: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> Message-ID: <053.29956cd86bd79302831a20eb269c5099@haiku-os.org> #4023: NumLock and CapsLock don't change keymap correctly --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by humdinger): I see this behaviour in VirtualBox, but I just tried with a native Haiku and there NumLock and CapsLock work as expected. So, this bug is probably invalid. I do still experience this:[[BR]] "On my keyboard is a "Pause" key that acts under Haiku just like the NumLock key." I have a notebook. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 17:36:58 2009 From: trac at haiku-os.org (phoudoin) Date: Mon, 15 Jun 2009 15:36:58 -0000 Subject: [Haiku-bugs] [Haiku] #4019: mime_update.sh still have /boot/beos record In-Reply-To: <040.6c9471ea3851bb838733ae58ade3c8e4@haiku-os.org> References: <040.6c9471ea3851bb838733ae58ade3c8e4@haiku-os.org> Message-ID: <049.1781557df9bf02b655b8cc8ef47f763e@haiku-os.org> #4019: mime_update.sh still have /boot/beos record ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by phoudoin): That was on purpose. The command "/bin/finddir B_SYSTEM_DIRECTORY" failure indicates most probably that this constant name is not known. This constant was introduced along others at the same time we moved from /boot/beos/system/... to /boot/system/, to remove any BEOS reference in their name. Hence why I've considered *at time* that /boot/beos was the best reply on error. This transition period is over, anyway ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 19:27:14 2009 From: trac at haiku-os.org (idefix) Date: Mon, 15 Jun 2009 17:27:14 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors Message-ID: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Somewhere between r30946 and r31054, a change has caused my computer to not fully booting Haiku anymore. There are a lot of 'Out of memory'-errors in the r31054 seriallog, while there are none in the log from r30946. See attached seriallogs. Unfortunately I can't test any releases in between, as there weren't any images generated. The computer has a Celeron at 433MHz processor, 64MB memory and 440LX chipset. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 19:32:04 2009 From: trac at haiku-os.org (idefix) Date: Mon, 15 Jun 2009 17:32:04 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors In-Reply-To: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> References: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> Message-ID: <050.a03c0ac4ca7e75c54ed77dfecdb1b413@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by idefix): Please ignore 'seriallog booting r31054 v2.2.txt', it's the same as 'seriallog booting r31054 v2.txt'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 21:30:39 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 15 Jun 2009 19:30:39 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors In-Reply-To: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> References: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> Message-ID: <050.f2a41e5079eeb1c7afc18b8e58b67f25@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by mmadia): Replying to [comment:1 idefix]: > Please ignore 'seriallog booting r31054 v2.2.txt', it's the same as 'seriallog booting r31054 v2.txt'. deleted the attachment 'seriallog booting r31054 v2.2.txt' -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 21:45:37 2009 From: trac at haiku-os.org (diver) Date: Mon, 15 Jun 2009 19:45:37 -0000 Subject: [Haiku-bugs] [Haiku] #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" In-Reply-To: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> References: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> Message-ID: <049.ff0af00297fc0967861fe27a393d3e55@haiku-os.org> #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by diver): I think this behavior is really strange and I would expect it to snap back as it was before I clicked 'Show Optional Packages'. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 22:18:38 2009 From: trac at haiku-os.org (idefix) Date: Mon, 15 Jun 2009 20:18:38 -0000 Subject: [Haiku-bugs] [Haiku] #3671: mountvolume can't unmount a volume In-Reply-To: <041.92d74d583a810ec31be4dc156a254ba8@haiku-os.org> References: <041.92d74d583a810ec31be4dc156a254ba8@haiku-os.org> Message-ID: <050.06ff6feeda16da6eb1afd65400c4b25b@haiku-os.org> #3671: mountvolume can't unmount a volume ----------------------------------------------+----------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Comment(by idefix): Thanks for fixing. I can now unmount a volume with 'mountvolume -unmount test'. Both 'mountvolume -unmount /test' and 'mountvolume -unmount /test/' don't work though.[[BR]] Could mountvolume be extended to also support these two commands? This way it would be compatible with BeOS's version and also improve usability somewhat (tab-completion). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 22:21:54 2009 From: trac at haiku-os.org (diver) Date: Mon, 15 Jun 2009 20:21:54 -0000 Subject: [Haiku-bugs] [Haiku] #575: [SampleStudio] crash if you try to open a file In-Reply-To: <040.92e2d10ba6ec843c4eec0bd033dd3c2f@haiku-os.org> References: <040.92e2d10ba6ec843c4eec0bd033dd3c2f@haiku-os.org> Message-ID: <049.b5e63c14ffce657f024213f78d1be705@haiku-os.org> #575: [SampleStudio] crash if you try to open a file ----------------------------+----------------------------------------------- Reporter: diver | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Game Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by diver): * version: => R1 development * component: - General => Kits/Game Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 15 23:04:43 2009 From: trac at haiku-os.org (myob) Date: Mon, 15 Jun 2009 21:04:43 -0000 Subject: [Haiku-bugs] [Haiku] #3490: OSS media addon - no sound followed by only a fraction of samples playing In-Reply-To: <039.4eb24f63139810cd86458b3eb001ab06@haiku-os.org> References: <039.4eb24f63139810cd86458b3eb001ab06@haiku-os.org> Message-ID: <048.44be922c1b15809f165e85dde7a6594d@haiku-os.org> #3490: OSS media addon - no sound followed by only a fraction of samples playing ----------------------------+----------------------------------------------- Reporter: myob | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by myob): This is still apparent in r31035. When playing, these two lines are repeated to the syslog constantly: KERN: osscore: Audio output doesn't drain (107520/103424 0). KERN: len=0/1024, total=4096 The numbers never change. As an aside, I tried disabling syslog output to see if it would improve matters and I get no sound at all if its off... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 16 18:57:07 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 16 Jun 2009 16:57:07 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.5ffcd34da4fc6d23123a48706960ed4c@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): More info (to self): On NV34 it has become clear that after a failed modeswitch the pixelPLL isn't programmed (at least). Probably it's therefore not selected either. Which in turn means the card was setup for an old (pre) VGA style mode with fixed frequency setting. It's highly unlikely that any 'modern' VESA mode would be programmed without using the pixelPLL to determine the screen's refreshrate. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 16 19:44:25 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 16 Jun 2009 17:44:25 -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.1114dc241782b6c93bba9b67297228fe@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 rudolfc): Hi again, I just uploaded a testing version of the driver (a readme.FIRST is included). people having a black screen, or a turned off screen after boot, please test this driver and see if you can get a picture using it. Also please upload the log it creates (see readme) and place a comment here describing what happens. I'm curious to the results! Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 16 20:00:36 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 16 Jun 2009 18:00:36 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.4691d6b89292100212f6992f9ef8eeea@haiku-os.org> #3886: problems with GeForce 7300 GT --------------------------------------+------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by rudolfc): Hi once again pacman / Christian, I'm pasting a response from Axel here concerning the sources of your GFX benchmarking app: (axel wrote:) We have some at src/tests/system/benchmarks, but there are other locations, too. I guess we can just put it there for now, and clean up this mess one day (later) :-) (end axel). So if you have write access you can put the code up there. Otherwise you could mail it to me and I'll try to do that. Thanks a lot in advance!! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 16 23:19:40 2009 From: trac at haiku-os.org (korli) Date: Tue, 16 Jun 2009 21:19:40 -0000 Subject: [Haiku-bugs] [Haiku] #4023: NumLock and CapsLock don't change keymap correctly In-Reply-To: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> References: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> Message-ID: <053.81294fac4cc54fa75343ca7675c5329c@haiku-os.org> #4023: NumLock and CapsLock don't change keymap correctly ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: axeld Type: bug | Status: closed Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 16 23:21:13 2009 From: trac at haiku-os.org (korli) Date: Tue, 16 Jun 2009 21:21:13 -0000 Subject: [Haiku-bugs] [Haiku] #4023: NumLock and CapsLock don't change keymap correctly In-Reply-To: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> References: <044.1d05b7f6eadf5289cb20defe2f8e44e7@haiku-os.org> Message-ID: <053.cee0a20aa82a23e4f08ba2616b845678@haiku-os.org> #4023: NumLock and CapsLock don't change keymap correctly ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: axeld Type: bug | Status: reopened Priority: low | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by korli): * status: closed => reopened * resolution: invalid => Comment: sorry, didn't notice the line about Pause. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 18 15:59:08 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 18 Jun 2009 13:59:08 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors In-Reply-To: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> References: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> Message-ID: <050.1a4e1ad31153202214413a42fc989429@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by anevilyak): * priority: normal => critical * milestone: R1 => R1/alpha1 Comment: This appears to be because some change or other (not sure which yet) broke/disabled swap support. Both Ingo and I noticed neither of our systems has any swap, though we did nothing to explicitly disable it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 18 16:05:07 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 18 Jun 2009 14:05:07 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors In-Reply-To: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> References: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> Message-ID: <050.99f59a22a614f2aa2dcc01d8e9d82ddf@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ---------------------------+------------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): From a quick look, r30975 seems the only likely culprit in that range. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 18 16:34:36 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 18 Jun 2009 14:34:36 -0000 Subject: [Haiku-bugs] [Haiku] #4030: Regression: booting on 64MB causes 'Out of memory'-errors In-Reply-To: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> References: <041.223cfec2363d9f0589ffeddf81b75387@haiku-os.org> Message-ID: <050.4d83cd53bd7b67dde31ca8dc24b06900@haiku-os.org> #4030: Regression: booting on 64MB causes 'Out of memory'-errors ----------------------------+----------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Should be fixed in r31098. Thanks Axel! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 00:18:00 2009 From: trac at haiku-os.org (diver) Date: Thu, 18 Jun 2009 22:18:00 -0000 Subject: [Haiku-bugs] [Haiku] #3893: [Installer] "Please Choose Target" menu item is truncated In-Reply-To: <040.d33713ecdd3e8632fa208ee0d40849e6@haiku-os.org> References: <040.d33713ecdd3e8632fa208ee0d40849e6@haiku-os.org> Message-ID: <049.b5b2ffb1f248e1625437b8bba9f7b201@haiku-os.org> #3893: [Installer] "Please Choose Target" menu item is truncated ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by diver): Correct screenshot is attached now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 03:18:29 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 19 Jun 2009 01:18:29 -0000 Subject: [Haiku-bugs] [Haiku] #3582: [www.haiku-os.org/images/manual_makebootable] Public image requiring authorization to see it In-Reply-To: <041.f42de68f33dac187cc52ccacc8e3fbc0@haiku-os.org> References: <041.f42de68f33dac187cc52ccacc8e3fbc0@haiku-os.org> Message-ID: <050.e9ac40d80cca3259679fa402219a5966@haiku-os.org> #3582: [www.haiku-os.org/images/manual_makebootable] Public image requiring authorization to see it --------------------------+------------------------------------------------- Reporter: eazel7 | Owner: haiku-web Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Website/CMS | Version: Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: IIRC, this was fixed a while back. Please re-open if the issue still exists for either non-authenticated or authenticated users. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 13:10:00 2009 From: trac at haiku-os.org (axeld) Date: Fri, 19 Jun 2009 11:10:00 -0000 Subject: [Haiku-bugs] [Haiku] #4008: Detecting bitmaps with enough Translators will corrupt memory. In-Reply-To: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> References: <041.fe3fd8a2e8a4bda7e9709d68d9cff9e1@haiku-os.org> Message-ID: <050.672815600dbabd5eb13d5af11ba731ae@haiku-os.org> #4008: Detecting bitmaps with enough Translators will corrupt memory. ------------------------------------+--------------------------------------- Reporter: stippi | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: System/runtime_loader | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r31113 (the corruption), and r31115 (runtime loader now reserves memory upfront). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 13:15:13 2009 From: trac at haiku-os.org (axeld) Date: Fri, 19 Jun 2009 11:15:13 -0000 Subject: [Haiku-bugs] [Haiku] #3998: Failure to boot if vitrual memory set to more than available space In-Reply-To: <043.8158645f35e22bf69b3b46fa276ea7a9@haiku-os.org> References: <043.8158645f35e22bf69b3b46fa276ea7a9@haiku-os.org> Message-ID: <052.84de79193bc6df84d9979144ee3782d7@haiku-os.org> #3998: Failure to boot if vitrual memory set to more than available space ---------------------------+------------------------------------------------ Reporter: dlmcpaul | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * milestone: R1/alpha1 => R1 Comment: The syslog (unzipped would have been preferred for easier handling) from the booting system alone doesn't really help. In any case, since I cannot reproduce this, I don't think this deserves to be in the alpha milestone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 19:42:07 2009 From: trac at haiku-os.org (philcostin) Date: Fri, 19 Jun 2009 17:42:07 -0000 Subject: [Haiku-bugs] [Haiku] #2912: [Alpha 1]: Tracker for the proposals In-Reply-To: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> References: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> Message-ID: <049.d20ad493bf7a91882f649996f61650fb@haiku-os.org> #2912: [Alpha 1]: Tracker for the proposals -----------------------+---------------------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by philcostin): #1444 and #1689 are marked as R1 blockers, not R1 Alpha blockers. Is this ticket still valid? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 19 22:05:51 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 19 Jun 2009 20:05:51 -0000 Subject: [Haiku-bugs] [Haiku] #2912: [Alpha 1]: Tracker for the proposals In-Reply-To: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> References: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> Message-ID: <049.8cfe2dca5b170060b704e2a14c574c0b@haiku-os.org> #2912: [Alpha 1]: Tracker for the proposals -----------------------+---------------------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): Replying to [comment:3 philcostin]: > #1444 and #1689 are marked as R1 blockers, not R1 Alpha blockers. > > Is this ticket still valid? Still valid, waiting on #3150 and #3151, with #3308 and #3859 also on the watch list. Seeing as how #1444 has been removed from being an Alpha Blocker, does this also mean that Prop#12 should be removed from the Alpha requirements list? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 14:58:16 2009 From: trac at haiku-os.org (nopper) Date: Sat, 20 Jun 2009 12:58:16 -0000 Subject: [Haiku-bugs] [Haiku] #2841: ACPI parser error In-Reply-To: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> References: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> Message-ID: <050.247438795fba883f1fafc8d6ec2eceb8@haiku-os.org> #2841: ACPI parser error ---------------------+------------------------------------------------------ Reporter: nopper | Owner: ithamar Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------+------------------------------------------------------ Comment(by nopper): Tested on my PC seems working. Someone please test it :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 15:57:18 2009 From: trac at haiku-os.org (monni) Date: Sat, 20 Jun 2009 13:57:18 -0000 Subject: [Haiku-bugs] [Haiku] #2841: ACPI parser error In-Reply-To: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> References: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> Message-ID: <050.91c3c1ce777959f25e1e3d0d5cc25f04@haiku-os.org> #2841: ACPI parser error ---------------------+------------------------------------------------------ Reporter: nopper | Owner: ithamar Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------+------------------------------------------------------ Comment(by monni): There's a typo in the diff: rechareable -> rechargeable -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 15:59:52 2009 From: trac at haiku-os.org (nopper) Date: Sat, 20 Jun 2009 13:59:52 -0000 Subject: [Haiku-bugs] [Haiku] #2841: ACPI parser error In-Reply-To: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> References: <041.c9ee2087a8fac60f28dc323fc3d6a005@haiku-os.org> Message-ID: <050.0e96fc4db1bf50e9ead1c8a2d6577aa4@haiku-os.org> #2841: ACPI parser error ---------------------+------------------------------------------------------ Reporter: nopper | Owner: ithamar Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------+------------------------------------------------------ Comment(by nopper): Thanks for the notice monni. Fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 17:28:56 2009 From: trac at haiku-os.org (darkwyrm) Date: Sat, 20 Jun 2009 15:28:56 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.f36057ccb3f8e97e497916743bf8f485@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by darkwyrm): Here is the exact problem: When a project is saved, Paladin updates type attribute even when it is not needed. I *think* the problem lies somewhere in the icon-related code at the beginning of BPoseView::AttributeChanged(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 17:37:20 2009 From: trac at haiku-os.org (kaliber) Date: Sat, 20 Jun 2009 15:37:20 -0000 Subject: [Haiku-bugs] [Haiku] #4031: missing strtof() Message-ID: <042.accf004aeef5d22998f1376142073225@haiku-os.org> #4031: missing strtof() -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Missing header and implementation of strtof(). http://www.opengroup.org/onlinepubs/000095399/functions/strtod.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 18:16:28 2009 From: trac at haiku-os.org (fano) Date: Sat, 20 Jun 2009 16:16:28 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.1fc4e2cca100d9c60ba71a53f5cec260@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): Nothing changed for me, sorry... Always black screen and no logfile is created in my home folder... I've substituted the nvidia driver in /Haiku/system/add- ons/kernel/drivers/bin and the accelarant in /Haiku/system/add- ons/accelarants... is this right? I've something other to do? The very strange thing is that the screen is black but not out-of-range is a black screen but the display not go in "energy saving mode"... that is a signal is present... and OSD says 1280*1024 at 60 again all is right but the screen remains black! No mouse cursor too... nothing... and sadly no logs!!! My I've to try a new Haiku image? But I dont't think something can change... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 18:53:35 2009 From: trac at haiku-os.org (axeld) Date: Sat, 20 Jun 2009 16:53:35 -0000 Subject: [Haiku-bugs] [Haiku] #2912: [Alpha 1]: Tracker for the proposals In-Reply-To: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> References: <040.93a4408f46bdc35d3451914f87f63528@haiku-os.org> Message-ID: <049.6f28ea1d830d9cd9b6fae36b2b21bb32@haiku-os.org> #2912: [Alpha 1]: Tracker for the proposals -----------------------+---------------------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by axeld): I don't think so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 19:34:41 2009 From: trac at haiku-os.org (darkwyrm) Date: Sat, 20 Jun 2009 17:34:41 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.b770bbdb8c5263a08d97ba6d8bbd4936@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by darkwyrm): The code that causes the bug goes like this: BFile file("somefile",B_SOME_FLAGS); file.WriteAttrString("application/x-vnd.dw-Paladin.Project"); However, when using the following code in the same place, it does NOT occur: BFile file("somefile",B_SOME_FLAGS); BNodeInfo nodeInfo(&file); nodeInfo.SetType("application/x-vnd.dw-Paladin.Project"); When the bug occurs, the file type of the project in question goes from the project mime type to text/plain. I hope all of this helps track down the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 21:25:03 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 20 Jun 2009 19:25:03 -0000 Subject: [Haiku-bugs] [Haiku] #4032: keymap cli tool: add StyledEdit attributes Message-ID: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> #4032: keymap cli tool: add StyledEdit attributes ---------------------------------------------+------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ This is r31133. It'd be nice if keymap's dump function (-d) would add the StyledEdit styles attribute for fixed font formatting. Just that little bit of extra Haiku convenience... :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 22:05:27 2009 From: trac at haiku-os.org (atomozero) Date: Sat, 20 Jun 2009 20:05:27 -0000 Subject: [Haiku-bugs] [Haiku] #4033: New acpi embedded controller driver block boot Message-ID: <044.1201dbdb25145186a0ddc76052c96f9c@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: | -----------------------+---------------------------------------------------- whit changeset 31102 and 31102 i have problem make boot on my toshiba laptop (Satellite A100-750) whit acpi abilitate the boot stop at last icon :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 20 22:39:59 2009 From: trac at haiku-os.org (stippi) Date: Sat, 20 Jun 2009 20:39:59 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.e92b85205d9f2bfadca961ee09b5cbac@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by stippi): Hm, that doesn't look like it would work. Can you please post the actual code? What attribute name string do you use when using the file directly? Should be "BEOS:TYPE" and "application/x-vnd.dw-Paladin.Project" should actually be passed inside a BString! And the second question would be with what permissions you construct the BFile exactly. I suppose you just wrote the project file, so you probably have write permissions set. Maybe that's different from how BNodeInfo works, I don't know. It should still work, though, so the true WriteAttrString() call is the most interesting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 00:37:35 2009 From: trac at haiku-os.org (darkwyrm) Date: Sat, 20 Jun 2009 22:37:35 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.b1cc9504f30eb11b610351e99af25ac3@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by darkwyrm): Whoops! I guess that's what I get for trying to write code from memory. ;) Here is an exact copy of the code that duplicates the error. [[BR]] {{{ BFile file(path,B_READ_WRITE | B_CREATE_FILE | B_ERASE_FILE); if (file.InitCheck() != B_OK) { STRACE(2,("Couldn't create project file %s. Bailing out\n",path)); return; } STRACE(2,("Saved Project %s. Data as follows:\n%s\n",path,data.String())); file.Write(data.String(),data.Length()); fPath = path; fObjectPath = fPath.GetFolder(); BString objfolder("(Objects."); objfolder << GetName() << ")"; fObjectPath.Append(objfolder.String()); BString str(PROJECT_MIME_TYPE); file.WriteAttrString("BEOS:TYPE",&str); UpdateBuildInfo(); }}} [[BR]] PROJECT_MIME_TYPE is #defined elsewhere as "text/x-vnd.dw- Paladin.Project". The changes made to the code which do not show the bug replace the last three lines of code with this: {{{ BNodeInfo nodeInfo(&file); nodeInfo.SetType(PROJECT_MIME_TYPE); UpdateBuildInfo(); }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 00:47:21 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 20 Jun 2009 22:47:21 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.8d6e0da2c61a22c8ec194da744d77e2b@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by anevilyak): The problem could be that the type attribute is actually supposed to be B_MIME_TYPE, not B_STRING_TYPE. WriteAttrString assumes the latter, which could be what's triggering this issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 00:49:03 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 20 Jun 2009 22:49:03 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.9c1809de5eaee332c20cb7e924e19c99@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by anevilyak): To verify this, try replacing with file.WriteAttr("BEOS:TYPE", B_MIME_TYPE, 0, PROJECT_MIME_TYPE, strlen(PROJECT_MIME_TYPE)); -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 02:27:27 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 21 Jun 2009 00:27:27 -0000 Subject: [Haiku-bugs] [Haiku] #4034: BFS partition became read-only Message-ID: <041.fd6d44ddc05477bb95a6a87853e353df@haiku-os.org> #4034: BFS partition became read-only ------------------------------+--------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- While using a python build automation script to build Haiku, the partition spontaneously became read-only. The partition is 10GB with about 2GB free. On it is : haiku & buildtools source trees and the generated folder. System is r30928-gcc2 and has been up for 1.5days. Attached is syslog. Are there any tests or additional information that would be useful before re- initializing? {{{ /builder> checkfs -c /builder/ haiku-alpha.iso (inode = 2118556), has blocks already set checked 235784 nodes, 0 blocks not allocated, 3072 blocks already set, 3484 blocks could be freed files 186948 directories 48015 attributes 517 attr. dirs 282 indices 22 }}} some snippets from syslog: {{{ KERN: bfs: Remove:1696: No such file or directory KERN: bfs: Could not find value in index "last_modified"! KERN: bfs: Oh no, value 2621458 not found in fragments of node 184320... }}} {{{ KERN: bfs: KERN: double indirect->runs->run: block_run(66, 49596, 4): blocks 4374972 - 4374975 are already set! KERN: bfs: double indirect->runs->run: block_run(66, 49600, 4): blocks 4374976 - 4374979 are already set! }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 09:07:08 2009 From: trac at haiku-os.org (jprostko) Date: Sun, 21 Jun 2009 07:07:08 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid Message-ID: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- As noted by Humdinger on the Haiku Development list, there is an issue with some GCC2 apps such as Beam, BePDF, and VLC getting a "Missing symbol: __gxx_personality_v0" error upon loading in a GCC4/2 hybrid environment. I narrowed down the problem to r31110. Attached is a patch that addresses the issues on my end, although I don't think it's the way to handle the problem, since I kind of just went for the "try to get it working with the least amount of effort" approach. Naturally, reverting HaikuImage to 30109 would make things happy too, although counteract its whole intent, I suppose. I initally thought the problem was only an issue with the libnet.so symlink, but I noticed the Beam error was actually due to an issue with libnetapi.so, so I addressed that as well in the patch. I want to take a closer look at things later, but I think I'll head to sleep. In any case, I figured I'd submit a ticket with the patch just to give an idea where the issues lie. I kind of need to take a look at ImageRules and do some more builds to figure out more how all of these pieces fit together (like the use/non-use of "true") in rules such as the ones being used. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 11:38:31 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 21 Jun 2009 09:38:31 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.922a8b4b3d5ffae9d6116ef90a29506a@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => assigned Comment: Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 12:59:54 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 21 Jun 2009 10:59:54 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.33c67ada69ea0bcb9226e4c5c45d4368@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): Fixed in r31150. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 13:00:05 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 21 Jun 2009 11:00:05 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.1275efc469190c5186b7164744ea9a77@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid ---------------------------+------------------------------------------------ Reporter: jprostko | 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: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 14:43:55 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 21 Jun 2009 12:43:55 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.3f3ed80b6f34e31f5bfadd2bc7bcce10@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: planche2k@? (added) Comment: Ping: Could someone please review the attached patch? Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 15:23:36 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 21 Jun 2009 13:23:36 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.451796ab412418825a7bb99b215fb08f@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by humdinger): * status: closed => reopened * resolution: fixed => Comment: With r31152 I now have this error when launching e.g. BePDF: "Missing libraries: libstdc++.r4.so" I hope this justifies reopening the bug. Thanks to everybody looking into this! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 18:14:20 2009 From: trac at haiku-os.org (jprostko) Date: Sun, 21 Jun 2009 16:14:20 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.cfc3f68dec7a9d72890966c79b9b13dd@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by jprostko): Well, I can confirm that there isn't an libstdc++.r4.so present at all, which makes it kind of hard to find. ;) I'm using r31158. The plus side of this is that this made an unrelated bug evident to me, which I'll post a ticket about later when I get a chance. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 18:58:11 2009 From: trac at haiku-os.org (jprostko) Date: Sun, 21 Jun 2009 16:58:11 -0000 Subject: [Haiku-bugs] [Haiku] #4036: GCC2 apps added to GCC4/2 image when GCC4 version is available Message-ID: <043.c721c1b69e61ec5007ccbb837ba08d3d@haiku-os.org> #4036: GCC2 apps added to GCC4/2 image when GCC4 version is available --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- With a GCC4/2 hybrid, I noticed that builds including the optional packages of BezillaBrowser, KeymapSwitcher, and Vim all include the GCC 2 version of the respective apps, even when the GCC4 version is available. This is due to an unnecessary isHybridBuild check in OptionalPackages for these apps. Attached is a diff to make sure the GCC4 version of the apps is included in this case. This way if it's a pure GCC4 build, or a GCC4/2 hybrid, the GCC4 version of the app is added. If it's a GCC2 or GCC2/4 hybrid, the GCC2 version will be added. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 19:19:38 2009 From: trac at haiku-os.org (jprostko) Date: Sun, 21 Jun 2009 17:19:38 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.4fa1c343d59d8766f6e3f1861d60c4a4@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by jprostko): This bug can be closed again, as it was resolved in 31159. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 19:41:20 2009 From: trac at haiku-os.org (axeld) Date: Sun, 21 Jun 2009 17:41:20 -0000 Subject: [Haiku-bugs] [Haiku] #4035: Missing symbol in GCC4/2 Hybrid In-Reply-To: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> References: <043.1c719723481b8abe1122caa69b026fe1@haiku-os.org> Message-ID: <052.686dce9841182d1b22347480604bba37@haiku-os.org> #4035: Missing symbol in GCC4/2 Hybrid ---------------------------+------------------------------------------------ Reporter: jprostko | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Thanks for the note! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 21 20:36:35 2009 From: trac at haiku-os.org (HaikuBot) Date: Sun, 21 Jun 2009 18:36:35 -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.0bc4b514c4b7da394cee2fbce9e0e7ef@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 HaikuBot): I have same trouble on my Acer Travelmate 2493. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 22 11:17:05 2009 From: trac at haiku-os.org (miqlas) Date: Mon, 22 Jun 2009 09:17:05 -0000 Subject: [Haiku-bugs] [Haiku] #3554: Time out error if i copy Haiku from usb to HDD In-Reply-To: <041.32c018a722ae17ffd95271eea88b0239@haiku-os.org> References: <041.32c018a722ae17ffd95271eea88b0239@haiku-os.org> Message-ID: <050.55b31c3dc9c8ee19612797041c2c74ea@haiku-os.org> #3554: Time out error if i copy Haiku from usb to HDD ---------------------------+------------------------------------------------ Reporter: miqlas | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by miqlas): This problem fixed some revisions ago, and the transfer from USB to IDE a little bit faster now. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 22 23:37:40 2009 From: trac at haiku-os.org (axeld) Date: Mon, 22 Jun 2009 21:37:40 -0000 Subject: [Haiku-bugs] [Haiku] #4032: keymap cli tool: add StyledEdit attributes In-Reply-To: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> References: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> Message-ID: <053.5db57d46b1f5ff768578da51b122d072@haiku-os.org> #4032: keymap cli tool: add StyledEdit attributes ---------------------------------------------+------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by axeld): The keymap utility currently only dumps to the terminal, not a file, so it cannot write any attributes; this could be changed of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 22 23:50:30 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 22 Jun 2009 21:50:30 -0000 Subject: [Haiku-bugs] [Haiku] #4032: keymap cli tool: add StyledEdit attributes In-Reply-To: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> References: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> Message-ID: <053.4a8a009c9c1a4c742d45b2bb5901d047@haiku-os.org> #4032: keymap cli tool: add StyledEdit attributes ---------------------------------------------+------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by anevilyak): I thought it only dumps to the console if the -d option is given? At least its code appears to have the ability to write it to a BFile as well (see Keymap::Save()). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 08:56:14 2009 From: trac at haiku-os.org (modeenf) Date: Tue, 23 Jun 2009 06:56:14 -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.42500378085fda97d4ca995c51bf8e4c@haiku-os.org> #2547: A little patch to compile BeServed under Visual Studio 2008 --------------------------+------------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by modeenf): * cc: fredrik@? (added) * platform: All => x86 Comment: I'll Have a look on this. So Filesharing are a cpl.. :) didn't find a exe so now I know :), anyone tested this under Vista or Windows7? This can be put on me.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 12:28:54 2009 From: trac at haiku-os.org (axeld) Date: Tue, 23 Jun 2009 10:28:54 -0000 Subject: [Haiku-bugs] [Haiku] #4032: keymap cli tool: add StyledEdit attributes In-Reply-To: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> References: <044.4846b6123aa041aa5c6444f2839d2844@haiku-os.org> Message-ID: <053.8680f650db2fb161509704b5d50d43fe@haiku-os.org> #4032: keymap cli tool: add StyledEdit attributes ----------------------------------------------+----------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Keymap::Save() stores a binary keymap - it wouldn't make much sense to open that one with StyledEdit :-) Anyway, implemented in r31196. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 14:07:30 2009 From: trac at haiku-os.org (darkwyrm) Date: Tue, 23 Jun 2009 12:07:30 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.905abe4aeae64aee976b500dce01cab1@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by darkwyrm): Excellent idea, anevilyak, but to no avail. Using the WriteAttr() code you posted, it exhibits the same behavior as when I use WriteAttrString. All that I need to do is open a project and close it in both cases. Paladin saves the project and updates the MIME type. Using WriteAttr or WriteAttrString, the project icon disappears and, if double-clicked, gets opened in StyledEdit as a plaintext file. Using the BNodeInfo version, the project icon stays the way it should and double-clicking on the file opens it in Paladin like it should. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 18:31:10 2009 From: trac at haiku-os.org (dvh) Date: Tue, 23 Jun 2009 16:31:10 -0000 Subject: [Haiku-bugs] [Haiku] #4037: Tracker crash post-initialization Message-ID: <038.43ea1e4769efbd07f9578b1063c0f9fc@haiku-os.org> #4037: Tracker crash post-initialization ------------------------------+--------------------------------------------- Reporter: dvh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Sometimes immediately, sometimes with some coaxing, browsing directories with Tracker on a gcc4-r31095 build results in Tracker crash to gdb, under the following conditions: 1) Running Haiku from a nightly test image as primary master, under VirtualBox 2.2.4, either Ubuntu Jaunty or Windows XP Hosts. 2) Primary slave is mapped to a partition on disk 3) Partition is initialized to BFS block size 2048 using DiskSetup 4) Files from the disk image are copied to the host partition using cp -rf, rather than using Tracker Copying the contents of the system disk image to the host partition using Tracker preserves metadata and does not cause crashes during directory browsing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 19:19:23 2009 From: trac at haiku-os.org (dvh) Date: Tue, 23 Jun 2009 17:19:23 -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.6585f2a15a78b62a487e4e4327777db4@haiku-os.org> #4037: Tracker crash post-initialization ------------------------------+--------------------------------------------- Reporter: dvh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by dvh): There's chatter on-list about the question but I'm open to assistance with additional investigation into the state of the filesystem. This isn't fully isolated and it's difficult to reproduce. Also: is there an equivalent to dmidecode for use in bug reporting with haiku? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 20:53:48 2009 From: trac at haiku-os.org (miqlas) Date: Tue, 23 Jun 2009 18:53:48 -0000 Subject: [Haiku-bugs] [Haiku] #4038: Tracker random crash (GCC4 - r31165) Message-ID: <041.c149b55b4da6424f2ea2f86675f80047@haiku-os.org> #4038: Tracker random crash (GCC4 - r31165) ----------------------------------+----------------------------------------- Reporter: miqlas | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Sometimes if i try to drag the selected path from an Tracker window to the Terminal the Tracker crashing randomly. I have official GCC4 Haiku r31165 build. {{{ (gdb) bt #0 0x003bbe64 in BString::BString () from /boot/system/lib/libbe.so #1 0x005b0977 in BPrivate::BColumnTitle::Draw () from /boot/system/lib/libtracker.so #2 0x005b1898 in BPrivate::BTitleView::Draw () from /boot/system/lib/libtracker.so #3 0x005b27d8 in BPrivate::BTitleView::Draw () from /boot/system/lib/libtracker.so #4 0x003660d6 in BView::_Draw () from /boot/system/lib/libbe.so #5 0x0036f880 in BWindow::DispatchMessage () from /boot/system/lib/libbe.so #6 0x0036fc80 in BWindow::UpdateIfNeeded () from /boot/system/lib/libbe.so #7 0x0058a26b in BPrivate::BPoseView::WaitForMouseUpOrDrag () from /boot/system/lib/libtracker.so #8 0x0058a5c2 in BPrivate::BPoseView::MouseDown () from /boot/system/lib/libtracker.so #9 0x0036f23f in BWindow::DispatchMessage () from /boot/system/lib/libbe.so #10 0x0036bd55 in BWindow::task_looper () from /boot/system/lib/libbe.so #11 0x002bfd84 in BLooper::_task0_ () from /boot/system/lib/libbe.so #12 0x00639b75 in thread_entry () from /boot/system/lib/libroot.so #13 0x7003ffec in ?? () (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 21:55:42 2009 From: trac at haiku-os.org (El-Al) Date: Tue, 23 Jun 2009 19:55:42 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.94fc83a164421b81468f471e2d4da26b@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) -----------------------+---------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by El-Al): Replying to [comment:7 El-Al]: > Replying to [comment:6 El-Al]: > > A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post. > > > > > Even tried installing to an IDE drive as opposed to SATA. Same problem occurs. I guess the driver overhaul hasn't caused this problem at all. I'm stumped! Well, it seems as though this problem is related to a limitation in the motherboards BIOS. I have now changed the motherboard for another make and model. Haiku boots perfectly well now. I noticed (whilst looking through the BIOS) in the USB Configuration options a switch for BIOS EHCI hand-off. The explaination of the switch is as follows: This is a workaround for OSes without EHCI hand-off support. The EHCI ownership change should claim by EHCI driver. As can be seen by the original screen output, the systen froze at the point of change of ownership. This option was not available in the previous BIOS although the system was booting fine up to a point in time. What puzzles me is what actually happened in order to make the system stop booting. I can only think of two possibilities: 1. That I was responsible by flashing the BIOS (which I recall doing at some point). 2. That ongoing work to the USB subsystem has somehow exposed the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 23:42:33 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 23 Jun 2009 21:42:33 -0000 Subject: [Haiku-bugs] [Haiku] #4038: Tracker random crash (GCC4 - r31165) In-Reply-To: <041.c149b55b4da6424f2ea2f86675f80047@haiku-os.org> References: <041.c149b55b4da6424f2ea2f86675f80047@haiku-os.org> Message-ID: <050.ab0423c90eed4b60b91bb76a82c9d5ac@haiku-os.org> #4038: Tracker random crash (GCC4 - r31165) -----------------------------------+---------------------------------------- Reporter: miqlas | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: 3710 Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3710 Comment: Duplicate of #3710. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 23:44:09 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 23 Jun 2009 21:44:09 -0000 Subject: [Haiku-bugs] [Haiku] #3914: Tracker crash In-Reply-To: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> References: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> Message-ID: <052.09dfd62e2f6196bd179b1ca091ca1cba@haiku-os.org> #3914: Tracker crash -----------------------------------+---------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: 3710 Platform: x86 | Blocking: 4007 -----------------------------------+---------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3710 Comment: That's another duplicate of #3710 actually. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 23 23:53:42 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 23 Jun 2009 21:53:42 -0000 Subject: [Haiku-bugs] [Haiku] #2504: Haiku freezes at bootup (leaf icon) In-Reply-To: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> References: <040.38f1115d1bcc8f8b5f886e63a6c0f846@haiku-os.org> Message-ID: <049.a5d886a2c268ccbb3b08a80707ed65e6@haiku-os.org> #2504: Haiku freezes at bootup (leaf icon) -----------------------+---------------------------------------------------- Reporter: El-Al | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mmlr): > As can be seen by the original screen output, the systen froze at the point of change of ownership. No it didn't. At those points the handover has been done already and the controller was started. > This option was not available in the previous BIOS although the system was booting fine up to a point in time. What puzzles me is what actually happened in order to make the system stop booting. I don't quite understand. Does it not boot when setting this BIOS setting to either? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 03:53:46 2009 From: trac at haiku-os.org (Pete) Date: Wed, 24 Jun 2009 01:53:46 -0000 Subject: [Haiku-bugs] [Haiku] #4016: USB device locks up system (was: Wacom locks up system) In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.4e17afbd6deefdac3a75968636c1757d@haiku-os.org> #4016: USB device locks up system ---------------------+------------------------------------------------------ Reporter: Pete | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------+------------------------------------------------------ Comment(by Pete): This is apparently a conflict with OSS... After posting the original ticket, I found that all USB devices (including sticks) caused the lockup, which was complete -- no F12 or ctl-alt-del. I eventually got time to check older revisions is a spare partition on the machine -- and they all worked! I ended up plugging the apparently failing revision (30629) into the spare partition, and it worked also! Digging around, the only important difference was the freshly-compiled (on the machine) OSS system. Removing that has restored USB useability. (Interestingly an older oss system was accidentally left on the working partition. It gets loaded, but doesn't crash USB. [And doesn't work...]) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 10:12:13 2009 From: trac at haiku-os.org (stippi) Date: Wed, 24 Jun 2009 08:12:13 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Rewrite all old-style drivers to use "device manager" API. (was: USB device locks up system) In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.eea9d8743c6a44aa5cfe3c2c280a7642@haiku-os.org> #4016: Rewrite all old-style drivers to use "device manager" API. -------------------------+-------------------------------------------------- Reporter: Pete | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by stippi): * type: bug => enhancement * milestone: R1 => Unscheduled Comment: I don't know if we have a ticket for the kernel to prevent two drivers fighting over the same device. It's actually not possible with the BeOS driver interface. Most of the Haiku drivers still use that interface and not the new (in Haiku) "device manager" driver interface, which, AFAIU, would prevent two drivers from accessing the same hardware. So the fix of this problem is actually to re-write all old-style drivers to use the new device manager API. Of course we only have a problem when there actually are more then one drivers for the same device, as with your OSS installation and a Haiku native driver, probably "hda". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 10:12:28 2009 From: trac at haiku-os.org (stippi) Date: Wed, 24 Jun 2009 08:12:28 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Rewrite all old-style drivers to use "device manager" API. In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.a54c56aabc5b8787217aaec361242c4a@haiku-os.org> #4016: Rewrite all old-style drivers to use "device manager" API. -------------------------+-------------------------------------------------- Reporter: Pete | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by stippi): * owner: stippi => nobody -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 10:13:51 2009 From: trac at haiku-os.org (stippi) Date: Wed, 24 Jun 2009 08:13:51 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Rewrite all old-style drivers to use "device manager" API. In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.afe5c757cdfaf0afc9879c9db9d19397@haiku-os.org> #4016: Rewrite all old-style drivers to use "device manager" API. -------------------------+-------------------------------------------------- Reporter: Pete | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by stippi): Actually, OSS is as "native" as any other sound driver, I meant to say an "already included" driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 11:21:22 2009 From: trac at haiku-os.org (axeld) Date: Wed, 24 Jun 2009 09:21:22 -0000 Subject: [Haiku-bugs] [Haiku] #4016: Rewrite all old-style drivers to use "device manager" API. In-Reply-To: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> References: <039.9320697fc050cdbb6a45877988a49233@haiku-os.org> Message-ID: <048.5ddb7a91176c83cea7905d8a6815bd1b@haiku-os.org> #4016: Rewrite all old-style drivers to use "device manager" API. -------------------------+-------------------------------------------------- Reporter: Pete | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by axeld): Fran?ois wanted to work on something for this. Anyway, the old drivers should only be ported once the new device API is proven to be stable. Maybe USB would be a worthwhile port to see what still needs to be improved, but ACPI can probably already help there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 13:03:55 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 24 Jun 2009 11:03:55 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.bb0145c653633da57bf42fd7023abaa1@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by bonefish): I'd assume WriteAttr[String]() fails for some reason. The being identified as text/plain is probably because the project type doesn't have a sniffer rule (or does it?). So the obvious question is: What's the error code WriteAttr[String]() returns? Maybe that gives a lead on what goes wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 16:43:03 2009 From: trac at haiku-os.org (darkwyrm) Date: Wed, 24 Jun 2009 14:43:03 -0000 Subject: [Haiku-bugs] [Haiku] #3231: File type problems with Paladin in Haiku, not BeOS In-Reply-To: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> References: <047.7f10d7c830d5ae1c35ab5ff08228e2cf@haiku-os.org> Message-ID: <056.2af1b1347159415a78fceedb55bd26d0@haiku-os.org> #3231: File type problems with Paladin in Haiku, not BeOS ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by darkwyrm): WriteAttr isn't failing -- it returns 29, which == strlen(PROJECT_MIME_TYPE). I did a bunch of looking around in the Tracker and sniffer sources and, while I'm not very familiar at all with the sources, I didn't find anything that looked amiss at first glance. The project mime type and data are AFAIK properly installed. My development box runs R5, Zeta 1.2, and (right now) Haiku GCC4. The MIME stuff works exactly the same on both R5 and Zeta and everything works right, too. Just for completeness sake I've posted below the code that installs Paladin's project MIME type. {{{ void InitFileTypes(void) { BMimeType mime; BString string; BMessage msg,ext; BBitmap large_icon(BRect(0, 0, B_LARGE_ICON - 1, B_LARGE_ICON - 1), B_COLOR_8_BIT); memcpy(large_icon.Bits(),kProjectLargeIconBits,1024); BBitmap mini_icon(BRect(0, 0, B_MINI_ICON - 1, B_MINI_ICON - 1), B_COLOR_8_BIT); memcpy(mini_icon.Bits(),kProjectSmallIconBits,256); mime.SetType(PROJECT_MIME_TYPE); mime.SetShortDescription("Paladin Project"); mime.SetLongDescription("File to build a program with Paladin"); mime.SetIcon(&large_icon, B_LARGE_ICON); mime.SetIcon(&mini_icon, B_MINI_ICON); mime.SetPreferredApp(APP_SIGNATURE); mime.Install(); ext.AddString("extensions","pld"); mime.SetFileExtensions(&ext); } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 19:19:06 2009 From: trac at haiku-os.org (kaliber) Date: Wed, 24 Jun 2009 17:19:06 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h Message-ID: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Please remove following lines from math.h: {{{ #define PI M_PI #define PI2 M_PI_2 }}} It breaks build of some applications and it isn't POSIX http://opengroup.org/onlinepubs/007908775/xsh/math.h.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 19:23:55 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 24 Jun 2009 17:23:55 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.20578af088bfa107a8a3d4c507b28b93@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by umccullough): Ah, yes... this explains why I had problems compiling SETI at home. I worked around it differently in that case by changing their definition to PI_ I had meant to look into it myself, but got pre-occupied :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 22:12:34 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 24 Jun 2009 20:12:34 -0000 Subject: [Haiku-bugs] [Haiku] #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed In-Reply-To: <043.92194c43c26b1f704f6ee442e62f188a@haiku-os.org> References: <043.92194c43c26b1f704f6ee442e62f188a@haiku-os.org> Message-ID: <052.d52ff3d379b333ae2388d4362b2222f7@haiku-os.org> #3989: The fan on the graphics card nVidia GeForce 9600 GT all the time working at top speed -------------------------------------+-------------------------------------- Reporter: mr.Noisy | Owner: rudolfc Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): BTW, You might have a look at a cardBIOS update if you know how to update such a thing. It might be that a newer BIOS for your card silences the fan a bit.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 22:16:22 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 24 Jun 2009 20:16:22 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.331adea967759d7f83d2dea1dc72dcc6@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there, Since Haiku R31213 the nVidia driver uses DDC/EDID to detect ws screens that are connected using a VGA cable. Also the force_ws setting is reset to being false by default. If all is right the problems should be gone now and the settings file is nolonger needed. Can you confirm that please? If the problem is fixed I'll close this ticket. Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 22:35:45 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 24 Jun 2009 20:35:45 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.e9881b5953287a2db1ad33b724305518@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, Since Haiku R31213 the nVidia driver uses DDC/EDID to detect ws screens that are connected using a VGA cable. Also the force_ws setting is reset to being false by default. This should fix the dvi connected non-widescreen monitors shutting off/displaying blackness in non-native modes I think. Furthermore the driver now logs the pixelPLL programming settings done by the BIOS during startup, which could give me some important info on why some monitors shut off or detect a wrong refreshrate, so maybe it's interesting to upload another logfile from the current nVidia driver. If the current driver doesn't solve the problem, it might be interesting to test a special version of the driver to see if a shutting-off monitor would remain on and display the desktop if the pixelPLL's aren't programmed at all. See http://dev.haiku-os.org/ticket/1026#comment:27 You'll find a zip archive there with info and the special driver. If anyone tests some more, please let me know the results.. :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed Jun 24 22:42:53 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 24 Jun 2009 20:42:53 -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.e5c28b9fad2521a978bf2973f6ced1c4@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 rudolfc): Hmm, I just read that I advised to place the nvidia.settings file in the home folder. This is _wrong_! (oops, sorry..) It should be in: home/config/settings/kernel/drivers Fano, did you place the file there and enable full logging? The resulting logfile does get created in your home folder... It's named something like: nvidia.10de_0141_010000.0.log Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 00:26:57 2009 From: trac at haiku-os.org (aljen) Date: Wed, 24 Jun 2009 22:26:57 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.9baa3138cf7e17e12bd8a5d40b1c14c0@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by aljen): yeah, while porting llvm to haiku i needed to #undef PI too :/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 00:36:05 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 24 Jun 2009 22:36:05 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.97838b68b1926a294c211bc6e964aa7d@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | 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 Thu Jun 25 02:03:30 2009 From: trac at haiku-os.org (tigerdog) Date: Thu, 25 Jun 2009 00:03: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.7c2f6758cf5a55df982c3ffa38b784d6@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 tigerdog): sorry so slow to respond, been away for a while. I just tried the test driver. Still no video here, but the result is different. Before, my monitor reported no video at all. Now, it reports "out of range". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 04:11:40 2009 From: trac at haiku-os.org (jprostko) Date: Thu, 25 Jun 2009 02:11:40 -0000 Subject: [Haiku-bugs] [Haiku] #4036: [patch] GCC2 packages added to GCC4 hybrid instead of available GCC4 packages (was: GCC2 apps added to GCC4/2 image when GCC4 version is available) In-Reply-To: <043.c721c1b69e61ec5007ccbb837ba08d3d@haiku-os.org> References: <043.c721c1b69e61ec5007ccbb837ba08d3d@haiku-os.org> Message-ID: <052.347ccea67f32b9db5f88aea67378d465@haiku-os.org> #4036: [patch] GCC2 packages added to GCC4 hybrid instead of available GCC4 packages --------------------------+------------------------------------------------- Reporter: jprostko | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by jprostko): I forgot to mention that at the time this ticket was first submitted, it was revision 31158. This would be obvious from looking at the diff, but I wanted to explicitly state it here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 11:12:32 2009 From: trac at haiku-os.org (richienyhus) Date: Thu, 25 Jun 2009 09:12:32 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.8703de9a5e5231f6953070fd9abc2629@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by richienyhus): * cc: richienyhus@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 15:28:25 2009 From: trac at haiku-os.org (aljen) Date: Thu, 25 Jun 2009 13:28:25 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.8786dd192a9e1906cbb1ba1cf8c23d16@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by aljen): I encounter this today, when building & installing haiku on ~6gb partition Before booting into it, i did on Linux: {{{ aljen at Hitomi:~/Develop/Haiku$ sudo mount /dev/sda7 mnt -t befs aljen at Hitomi:~/Develop/Haiku$ df -h | grep sda7 /dev/sda7 6,6G 353M 6,2G 6% /home/aljen/Develop/Haiku/mnt }}} so there is only 353M used, then, i booted into Haiku and run df: {{{ Mount Type Total Free Flags Device --------------- -------- --------- --------- ------- -------------------------- /boot bfs 6.5G 2.2G QAM-P-W /dev/disk/ata/0/master/2_2 }}} Now after reboot into Linux, i test it again, but now with "Haiku results": {{{ aljen at Hitomi:~/Develop/Haiku$ sudo mount /dev/sda7 mnt -t befs aljen at Hitomi:~/Develop/Haiku$ df -h | grep sda7 /dev/sda7 6,6G 4,4G 2,2G 67% /home/aljen/Develop/Haiku/mnt }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 15:42:13 2009 From: trac at haiku-os.org (bga) Date: Thu, 25 Jun 2009 13:42:13 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.0c3e6b69fff813290d98d65c71147238@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by bga): In your specific case, it was probably just the swap file being created. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 15:51:04 2009 From: trac at haiku-os.org (aljen) Date: Thu, 25 Jun 2009 13:51:04 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.db1dce395ef9845e91daa30b09dbb0f1@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by aljen): Stupid me, sorry for time waste, i checked and indeed there is a 4gb swap file.. But my second machine at first run created 286mb swap file instead of 4gb (first have 4gb ram, second 3gb), i didn't check that at first place and that's why i thought it was that issue -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 19:39:32 2009 From: trac at haiku-os.org (idefix) Date: Thu, 25 Jun 2009 17:39:32 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.4b3446b273ea4c8f916d2e95d3332cc3@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by idefix): * status: closed => reopened * resolution: fixed => Comment: Unfortunately, I can still reproduce this with r31230 following the same steps. I also tried to not do a checkfs in the first step, but that didn't matter. The final crash is slightly different though (bfs_stat_index:2050 vs 2020): {{{ bfs: mounted "test0mkfs" (root node at 524288, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2050: No such file or directory bfs: AllocationBlock::Allocate(): some blocks are already allocated, start = 0, numBlocks = 4297 PANIC: blocks already set! Welcome to Kernel Debugging Land... Thread 170 "bfs block allocator" running on CPU 0 kdebug> bt stack trace for thread 170 "bfs block allocator" kernel stack: 0x81d92000 to 0x81d96000 frame caller :function + offset 0 81d95ba8 (+ 48) 8006545d :invoke_debugger_command + 0x0105 1 81d95bd8 (+ 64) 8006523d invoke_pipe_segment(debugger_command_pipe*: 0x81612030, int32: 0, 0x0 "") + 0x0079 2 81d95c18 (+ 64) 800655f0 :invoke_debugger_command_pipe + 0x009c 3 81d95c58 (+ 48) 80066fec ExpressionParser<0x81d95d08>::_ParseCommandPipe(0x81d95d04) + 0x0234 4 81d95c88 (+ 64) 80066426 ExpressionParser<0x81d95d08>::EvaluateCommand(0x80125c00 "bt", 0x81d95d04) + 0x02ba 5 81d95cc8 (+ 224) 80068400 :evaluate_debug_command + 0x0080 6 81d95da8 (+ 64) 800632b6 kernel_debugger_loop() + 0x01b6 7 81d95de8 (+ 32) 800641cd :kernel_debugger + 0x004d 8 81d95e08 (+ 192) 80064175 :panic + 0x0029 9 81d95ec8 (+ 96) 805c5832 AllocationGroup<0x82d4b000>::Allocate(Transaction&: 0x81d95fcc, uint16: 0x0 (0), int32: 4329) + 0x02b6 10 81d95f28 (+ 176) 805c6284 BlockAllocator<0x811c8094>::_Initialize(BlockAllocator*: NULL) + 0x032c 11 81d95fd8 (+ 32) 80057613 _create_kernel_thread_kentry() + 0x001b 12 81d95ff8 (+2116460552) 800575b0 thread_kthread_exit() + 0x0000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 19:58:24 2009 From: trac at haiku-os.org (humdinger) Date: Thu, 25 Jun 2009 17:58:24 -0000 Subject: [Haiku-bugs] [Haiku] #4040: Blue 16x16 preview rect background missing (easy) Message-ID: <044.15b2dd59d6cc01de216ca3cedd2b3028@haiku-os.org> #4040: Blue 16x16 preview rect background missing (easy) ---------------------------------------+------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: low | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ This is r31230 (gcc4 hybrid in VirtualBox). The background of the small blue 16x16 preview is missing. See attached screenshot. If there's an icon in the works, that does get rendered. It's just the blue background that's missing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 20:08:29 2009 From: trac at haiku-os.org (axeld) Date: Thu, 25 Jun 2009 18:08:29 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.767e74396f04434adf84fd36fac99759@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by axeld): I could not reproduce this problem. Can you please run either "bfsinfo -s" from the BFS-tools, or the output of "F12 - mount 3 - bfs _volume" - you need to replace the "3" with whatever device number that partition has (you can use the "mounts" command to see them all listed). The data I'm interested in is how the super block looks like. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 21:53:20 2009 From: trac at haiku-os.org (stippi) Date: Thu, 25 Jun 2009 19:53:20 -0000 Subject: [Haiku-bugs] [Haiku] #4040: Blue 16x16 preview rect background missing (easy) In-Reply-To: <044.15b2dd59d6cc01de216ca3cedd2b3028@haiku-os.org> References: <044.15b2dd59d6cc01de216ca3cedd2b3028@haiku-os.org> Message-ID: <053.4375b050dd50b37843ee6850c24867ef@haiku-os.org> #4040: Blue 16x16 preview rect background missing (easy) ----------------------------------------+----------------------------------- Reporter: humdinger | Owner: stippi Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Icon-O-Matic | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by stippi): * status: new => closed * resolution: => invalid Comment: This is on purpose. For performance reasons, there shouldn't be any number of previews. The blue background is not so useful for the 16x16 version, but 16x16 icons are used in menus, that's why there is a panel background colored preview instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 22:06:40 2009 From: trac at haiku-os.org (idefix) Date: Thu, 25 Jun 2009 20:06:40 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.8257c223722df9391a9e9a20a8cd83a8@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by idefix): After mkfs initialised the volume: {{{ PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs kdebug> continue bfs: mounted "test0mkfs" (root node at 524288, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2050: No such file or directory PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs 0x80f91f00 5 0x8100fee0 0x81002000 0x811cb0e0 bfs kdebug> mount 5 MOUNT: 0x80f91f00 id: 5 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x8100fee0 covers_vnode: 0x81002000 partition: 0x80fde198 lock: 0x80f91f10 flags: volume 0x8103e8c0: layer: 0 private_volume: 0x811cb0e0 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 5 block cache: 0x810a5258 journal: 0x80f8a690 allocator: 0x811cb2f4 root node: 0x81005000 indices node: 0x810453fc disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 4502 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 4 ag_shift = 16 (65536 bytes) num_ags = 58 flags = 0x434c454e (CLEN) log_blocks = (0, 233, 4096) log_start = 269 log_end = 269 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 4329, 1) }}} Then, after running checkfs on the volume: {{{ PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs 0x80f91f00 5 0x8100fee0 0x81002000 0x811cb0e0 bfs kdebug> mount 5 MOUNT: 0x80f91f00 id: 5 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x8100fee0 covers_vnode: 0x81002000 partition: 0x80fde198 lock: 0x80f91f10 flags: volume 0x8103e8c0: layer: 0 private_volume: 0x811cb0e0 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 5 block cache: 0x810a5258 journal: 0x80f8a690 allocator: 0x811cb2f4 root node: 0x81005000 indices node: 0x810453fc disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 4502 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 4 ag_shift = 16 (65536 bytes) num_ags = 58 flags = 0x434c454e (CLEN) log_blocks = (0, 233, 4096) log_start = 269 log_end = 269 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 4329, 1) }}} Booting into BeOS and using the BFS-tools: {{{ Welcome to the BeOS shell. $ mountvolume test0mkfs scanning volumes... test0mkfs mounted OK $ bfsinfo -s /test0mkfs/ Copyright (c) 2001-2008 pinc Software. disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE, little endian) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 4506 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 4 ag_shift = 16 num_ags = 58 flags = 0x434c454e (CLEN) log_blocks = (0, 233, 4096) log_start = 278 log_end = 278 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 4329, 1) $ chkbfs /test0mkfs/ bfs: /dev/disk/ide/ata/1/master/0/0_0 is read-only! Files processed: 11 BFS has 3 blocks allocated that should not be. Block allocation mismatches detected. Fixing. File system check completed. $ bfsinfo -s /test0mkfs/ Copyright (c) 2001-2008 pinc Software. disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE, little endian) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 4506 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 4 ag_shift = 16 num_ags = 58 flags = 0x434c454e (CLEN) log_blocks = (0, 233, 4096) log_start = 278 log_end = 278 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 4329, 1) }}} Booting back into Haiku and then mounting the partition (which results in a crash): {{{ PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs kdebug> continue bfs: mounted "test0mkfs" (root node at 524288, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2050: No such file or directory bfs: AllocationBlock::Allocate(): some blocks are already allocated, start = 0, numBlocks = 4297 PANIC: blocks already set! Welcome to Kernel Debugging Land... Thread 171 "bfs block allocator" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs 0x8100ae10 4 0x8100f908 0x81002b28 0x811c7e80 bfs kdebug> mount 4 MOUNT: 0x8100ae10 id: 4 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x8100f908 covers_vnode: 0x81002b28 partition: 0x80fde198 lock: 0x8100ae20 flags: volume 0x810a6ed8: layer: 0 private_volume: 0x811c7e80 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 4 block cache: 0x81078960 journal: 0x810789d8 allocator: 0x811c8094 root node: 0x80fe7e9c indices node: 0x81060550 disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 4506 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 4 ag_shift = 16 (65536 bytes) num_ags = 58 flags = 0x434c454e (CLEN) log_blocks = (0, 233, 4096) log_start = 278 log_end = 278 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 4329, 1) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 22:50:17 2009 From: trac at haiku-os.org (idefix) Date: Thu, 25 Jun 2009 20:50:17 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.b54072897c968d4650a5bc13d57278f6@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by idefix): Tried another experiment: Initialising the volume in BeOS: {{{ $ mkbfs 2048 /dev/disk/ide/ata/1/master/0/0_0 test0mkfs BFS w/2048 byte blocks successfully created on /dev/disk/ide/ata/1/master/0/0_0 as test0mkfs BFS Dump: fd 3 dev_block_size 512 dev_block_conversion 4 tmp block data @ 0x80041768 num bitmap blocks: 229 Disk Super Block: name: test0mkfs magic1: 0x42465331 fs byte order: little endian block size: 2048 num blocks: 3747161 num blocks used: 2603 inode size: 2048 magic2: 0xdd121031 num blocks per allocation group: 2 ag shift: 15 num ag's: 115 flags: 0x434c454e magic3: 0x15b6830e log start: 0 -- log end: 0 log area: ag : 0 start : 230 len : 2048 root dir inode: ag : 8 start : 0 len : 1 indices inode: ag : 0 start : 2278 len : 1 pad: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ------------------------------------------ nsid: -2147219936 nbitmap blocks 229 bv @ 0x800497c0 bbm_sem 6391 sem 6389 fd 3 dev block size 512 inodes: root 0x800fdc60 index 0x800ffdd8 name 0x801011f0 size 0x80102e18 create time 0x0 last m. time 0x80104230 index list @ 0x0 log sem 6392 cur_log_end 0 cur_lh 0x800fd388 active_lh 0 completed log entries @ 0x0 tmp blocks @ 0x80041768 tmp b. sem 6390 $ mountvolume test0mkfs scanning volumes... test0mkfs mounted OK $ bfsinfo -s /test0mkfs/ Copyright (c) 2001-2008 pinc Software. disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE, little endian) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 2800 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 30 log_end = 30 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) }}} Booting into Haiku and mounting the volume: {{{ bfs: mounted "test0mkfs" (root node at 262144, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2050: No such file or directory PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs 0x80f91b40 4 0x80f9b2a8 0x80feae14 0x811c7e80 bfs kdebug> mount 4 MOUNT: 0x80f91b40 id: 4 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x80f9b2a8 covers_vnode: 0x80feae14 partition: 0x80fde198 lock: 0x80f91b50 flags: volume 0x810a3ac8: layer: 0 private_volume: 0x811c7e80 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 4 block cache: 0x810b0078 journal: 0x81021960 allocator: 0x811c8094 root node: 0x80fe0bf4 indices node: 0x80ff2000 disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 2800 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 (32768 bytes) num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 32 log_end = 32 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) kdebug> continue }}} After running checkfs: {{{ PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mount 4 MOUNT: 0x80f91b40 id: 4 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x80f9b2a8 covers_vnode: 0x80feae14 partition: 0x80fde198 lock: 0x80f91b50 flags: volume 0x810a3ac8: layer: 0 private_volume: 0x811c7e80 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 4 block cache: 0x810b0078 journal: 0x81021960 allocator: 0x811c8094 root node: 0x80fe0bf4 indices node: 0x80ff2000 disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 2800 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 (32768 bytes) num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 32 log_end = 32 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) }}} And then booting back into BeOS: {{{ Welcome to the BeOS shell. $ mountvolume test0mkfs scanning volumes... test0mkfs mounted OK $ bfsinfo -s /test0mkfs/ Copyright (c) 2001-2008 pinc Software. disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE, little endian) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 3450 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 55 log_end = 55 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) $ chkbfs /test0mkfs/ bfs: /dev/disk/ide/ata/1/master/0/0_0 is read-only! Files processed: 19 No errors detected. File system check completed. $ bfsinfo -s /test0mkfs/ Copyright (c) 2001-2008 pinc Software. disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE, little endian) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 3450 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 55 log_end = 55 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) }}} And back into Haiku after running checkfs on the volume: {{{ bfs: mounted "test0mkfs" (root node at 262144, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2050: No such file or directory PANIC: keyboard requested halt. Welcome to Kernel Debugging Land... Thread 1 "idle thread 1" running on CPU 0 kdebug> mounts address id root covers cookie fs_name 0x80fa82d0 1 0x80f9b044 0x00000000 0x80f9a708 rootfs 0x80fa8348 2 0x80f9b0cc 0x80f9b088 0x80f9a758 devfs 0x80fc8f00 3 0x80f9b50c 0x80f9b484 0x811c6f00 bfs 0x81042f78 6 0x80feab6c 0x80fea000 0x811c7e80 bfs kdebug> mount 6 MOUNT: 0x81042f78 id: 6 device_name: /dev/disk/ata/1/master/0 root_vnode: 0x80feab6c covers_vnode: 0x80fea000 partition: 0x80fde198 lock: 0x81042f88 flags: volume 0x80ff6168: layer: 0 private_volume: 0x811c7e80 ops: 0x805e8c20 file_system: 0x805e8d60 file_system_name: bfs kdebug> bfs _volume id: 6 block cache: 0x810a89d8 journal: 0x810a8960 allocator: 0x811c8094 root node: 0x8102fbf4 indices node: 0x80f95e9c disk_super_block: name = test0mkfs magic1 = 0x42465331 (BFS1) valid fs_byte_order = 0x42494745 (BIGE) block_size = 2048 block_shift = 11 num_blocks = 3747161 used_blocks = 3198 inode_size = 2048 magic2 = 0xdd121031 (...1) valid blocks_per_ag = 2 ag_shift = 15 (32768 bytes) num_ags = 115 flags = 0x434c454e (CLEN) log_blocks = (0, 230, 2048) log_start = 64 log_end = 64 magic3 = 0x15b6830e (....) valid root_dir = (8, 0, 1) indices = (0, 2278, 1) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu Jun 25 22:57:26 2009 From: trac at haiku-os.org (axeld) Date: Thu, 25 Jun 2009 20:57:26 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.cb7d7c2946b7f44803f1c730cf7fad8f@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by axeld): Thanks! I was just going to ask you to initialize the volume under BeOS :-) I understand now what's going on: Haiku's BFS allocates the last allocation group completely, while it's only a partial one. BeOS' BFS only allocates what's needed. I'll probably fix that tomorrow; I keep the ticket at "critical" for the other related bug I already fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 00:20:06 2009 From: trac at haiku-os.org (darkwyrm) Date: Thu, 25 Jun 2009 22:20:06 -0000 Subject: [Haiku-bugs] [Haiku] #3250: Paladin RC2 don't work correctly with GCC4 hybrid build In-Reply-To: <041.b3b70f17e6bf2abde0c1213aab017123@haiku-os.org> References: <041.b3b70f17e6bf2abde0c1213aab017123@haiku-os.org> Message-ID: <050.90105e7806aaf66ef89a18b3cb45ed19@haiku-os.org> #3250: Paladin RC2 don't work correctly with GCC4 hybrid build ---------------------------+------------------------------------------------ Reporter: miqlas | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by darkwyrm): * status: new => closed * resolution: => fixed Comment: Tested Paladin 1.0 with r31227 hybrid build. Bug no longer is a problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 07:57:14 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 26 Jun 2009 05:57:14 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd Message-ID: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> #4041: no boot partition found while booting alpha-cd -----------------------+---------------------------------------------------- Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- GCC4 build with new ATA-Stack of r31233 on real hardware. If I boot from the CD, with the internally cdrom drive, I get the error that no boot partition can be found. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 11:36:35 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 09:36:35 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.34c29bda14d4aebac7633b5822876905@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Fixed in r31248. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 12:28:22 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 26 Jun 2009 10:28:22 -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.a35456e62616d55bd19dfc36682b36fc@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 rudolfc): Hi tigerdog, Could you modify nvidia.settings for the switchhead setting? Make that line read: switchead true And reboot. Try the testdriver first please, then also try the current driver from svn. The old driver and the testdriver select the wrong video output, the current svn driver should choose correctly since it now uses EDID (which works on your card and monitor). Please also upload a new clean log from a boot with the current svn driver.. Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 12:29:14 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 26 Jun 2009 10:29:14 -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.8277e3abd90f70df06e92d6cc078b94b@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 rudolfc): Oh, tigerdog, if you use the current svn driver you need to disable switchhead again! Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 13:17:46 2009 From: trac at haiku-os.org (phoudoin) Date: Fri, 26 Jun 2009 11:17:46 -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.35f34684b6e40a4bd2d92e05fbc1c768@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: | ------------------------------+--------------------------------------------- Comment(by phoudoin): Exact same problem seen a few hours ago, under a fresh r31238. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 13:21:20 2009 From: trac at haiku-os.org (michael.weirauch) Date: Fri, 26 Jun 2009 11:21:20 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number Message-ID: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> #4042: get_cached_block: invalid block number ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- r31248; gcc4; Mounting my storage partition from a fresh r31248 produces the attached KDL. Not reproduceable on a gcc2 r31060. Probably related to the r31248 change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 13:22:51 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 11:22:51 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.86bf23f2ccb3631773f9c53544218667@haiku-os.org> #4039: PI in math.h -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | 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 Fri Jun 26 13:43:25 2009 From: trac at haiku-os.org (michael.weirauch) Date: Fri, 26 Jun 2009 11:43:25 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number In-Reply-To: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> References: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> Message-ID: <060.e2bc62dea0ea8d68a71396542937e230@haiku-os.org> #4042: get_cached_block: invalid block number ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): From the r31248, I can however mount my r31060 installation partition without issue. checkfs on the storage partition shows no issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 13:53:14 2009 From: trac at haiku-os.org (idefix) Date: Fri, 26 Jun 2009 11:53:14 -0000 Subject: [Haiku-bugs] [Haiku] #2549: Can't change video mode when monitor can't display current video mode In-Reply-To: <041.26e7c8bcc69ce7ad54f7c6bf25988948@haiku-os.org> References: <041.26e7c8bcc69ce7ad54f7c6bf25988948@haiku-os.org> Message-ID: <050.3f4a86dfe74fc80a9d78da9036522aa2@haiku-os.org> #2549: Can't change video mode when monitor can't display current video mode --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by idefix): Replying to [ticket:2549 idefix]: > [...][[BR]] > Thirdly I remembered the [Ctrl]-[Alt]-[Shift]-[F12] keystroke which in BeOS causes the display to VGA mode @ 60 Hz. In Haiku however I go into the kernel debugger (as I discovered in the serial output, the monitor still displayed a warning).[[BR]] > [...][[BR]] > Secondly the [Ctrl]-[Alt]-[Shift]-[F12] keystroke should work the same as in BeOS. Changeset [31071] and [31160] implemented the [Ctrl]-[Alt]-[Esc] keystroke to switch the display to fallback video mode. This bug can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 13:59:00 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 11:59:00 -0000 Subject: [Haiku-bugs] [Haiku] #4039: PI in math.h In-Reply-To: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> References: <042.2ab298ddb411c52bc9fa0d06c552a9b6@haiku-os.org> Message-ID: <051.bc3b67ae8e1196ce580b8772710f3a5c@haiku-os.org> #4039: PI in math.h --------------------------------+------------------------------------------- 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 axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31250. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 14:05:26 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 26 Jun 2009 12:05:26 -0000 Subject: [Haiku-bugs] [Haiku] #2549: Can't change video mode when monitor can't display current video mode In-Reply-To: <041.26e7c8bcc69ce7ad54f7c6bf25988948@haiku-os.org> References: <041.26e7c8bcc69ce7ad54f7c6bf25988948@haiku-os.org> Message-ID: <050.828527285ea2becaa037192c99f8e235@haiku-os.org> #2549: Can't change video mode when monitor can't display current video mode ---------------------------------+------------------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Screen | 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 Fri Jun 26 14:48:52 2009 From: trac at haiku-os.org (togs) Date: Fri, 26 Jun 2009 12:48:52 -0000 Subject: [Haiku-bugs] [Haiku] #4043: [mouse preferences] Focus follow mouse dialog too short Message-ID: <039.1bb8b624bb623fb347ae6c1ab44ce846@haiku-os.org> #4043: [mouse preferences] Focus follow mouse dialog too short -------------------------------+-------------------------------------------- Reporter: togs | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Mouse | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- On my system, the focus follows mouse option dialog is too short for the longest option: Instant-Warping. This is at 1024x600 on r31243. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:05:44 2009 From: trac at haiku-os.org (togs) Date: Fri, 26 Jun 2009 13:05:44 -0000 Subject: [Haiku-bugs] [Haiku] #4044: Module settings text is trimmed Message-ID: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> #4044: Module settings text is trimmed -----------------------+---------------------------------------------------- Reporter: togs | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Long pieces of text (select the "Message" screensaver) are trimmed off in the Module settings groupbox area. r31243 at 1024x600. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:06:03 2009 From: trac at haiku-os.org (togs) Date: Fri, 26 Jun 2009 13:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #4044: Module settings text is trimmed In-Reply-To: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> References: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> Message-ID: <048.8d51f4ebfb248ba17c5329b4fa797690@haiku-os.org> #4044: Module settings text is trimmed -------------------------------------+-------------------------------------- Reporter: togs | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by togs): * component: - General => Preferences/ScreenSaver -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:11:07 2009 From: trac at haiku-os.org (michael.weirauch) Date: Fri, 26 Jun 2009 13:11:07 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number In-Reply-To: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> References: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> Message-ID: <060.d7aa8919de0f58b215a063bdf46d9b27@haiku-os.org> #4042: get_cached_block: invalid block number ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): Going back to r31427 for bfs does not KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:35:18 2009 From: trac at haiku-os.org (tigerdog) Date: Fri, 26 Jun 2009 13:35:18 -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.723127f7277f3aad700e4248ccf05c82@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 tigerdog): Interesting points: with the current SVN driver and with your test driver, nvidia.settings never gets created. Also, I can't get current SVN driver to work at all, even if I manually copy the settings file from an older version. I'll try again later today and upload the logs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:38:13 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 13:38:13 -0000 Subject: [Haiku-bugs] [Haiku] #4044: Module settings text is trimmed In-Reply-To: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> References: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> Message-ID: <048.6baf32d4ce7361910755ae62c86e7b2e@haiku-os.org> #4044: Module settings text is trimmed -------------------------------------+-------------------------------------- Reporter: togs | Owner: leavengood Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by axeld): * owner: axeld => leavengood Comment: Actually, each screen saver is responible for the size of its settings view itself. IIRC Ryan wrote "Message". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:40:30 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 13:40:30 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.cbf53356abccd5f29a6d5a79b3be50f9@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by axeld): * owner: axeld => marcusoverhagen * component: - General => Drivers/Disk Comment: I'm afraid we need a bit more information to make this a useful bug report, like: what kind of real hardware? A "listdev" output would be great. Also, does it boot with the old stack? Does it boot from HD? Is it a SATA or PATA CD-ROM? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:47:58 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 13:47:58 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number In-Reply-To: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> References: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> Message-ID: <060.86061e8f25cd15d9538acf02542c8df7@haiku-os.org> #4042: get_cached_block: invalid block number ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Does r31252 help? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 15:49:10 2009 From: trac at haiku-os.org (jahaiku) Date: Fri, 26 Jun 2009 13:49:10 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.9d075bc7d8605a035495dd119e635749@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by jahaiku): Replying to [comment:1 axeld]: > I'm afraid we need a bit more information to make this a useful bug report, like: what kind of real hardware? A "listdev" output would be great. Also, does it boot with the old stack? Does it boot from HD? Is it a SATA or PATA CD-ROM? The hardware is an old compaq notebook 17XL470 with PATA-cdrom. If I install Haiku on the HD it boots well from there. Is an lspci from Knoppix OK, too? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 16:53:24 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 14:53:24 -0000 Subject: [Haiku-bugs] [Haiku] #2573: Files taking *A LOT* more space on disk than the sum of their sizes. In-Reply-To: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> References: <038.bc4859dc9594321c87a7b4a91d4a1351@haiku-os.org> Message-ID: <047.0d56813a5a650e669b3c3ca344de0419@haiku-os.org> #2573: Files taking *A LOT* more space on disk than the sum of their sizes. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: The directory preallocations are now only 4K since r31253. Directory preallocations are only trimmed when their vnode is flushed, which doesn't happen that often when you have lots of memory. The Haiku source tree contained about 20000 directories - before, this could lead to a loss of 1.2 GB in preallocations. Now it's only 80 MB which I consider acceptable. A more refined solution would be to trim the preallocations after a certain time of inactivity, but I guess that's not worth the effort. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 17:01:37 2009 From: trac at haiku-os.org (leavengood) Date: Fri, 26 Jun 2009 15:01:37 -0000 Subject: [Haiku-bugs] [Haiku] #4044: Module settings text is trimmed In-Reply-To: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> References: <039.58f73a59e07852cdc9fbd99a82889153@haiku-os.org> Message-ID: <048.1513b72268358a000bc1071e56997a00@haiku-os.org> #4044: Module settings text is trimmed -------------------------------------+-------------------------------------- Reporter: togs | Owner: leavengood Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by leavengood): * status: new => assigned Comment: Axel is right, I'll take care of Message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 17:04:00 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 15:04:00 -0000 Subject: [Haiku-bugs] [Haiku] #3432: PANIC: tried to get writable block on a read-only cache ! In-Reply-To: <038.8a9c46acdbe184f16abd29ea03d3b3ab@haiku-os.org> References: <038.8a9c46acdbe184f16abd29ea03d3b3ab@haiku-os.org> Message-ID: <047.0dc2e89d21c7f086a5d5e55a0b8b295f@haiku-os.org> #3432: PANIC: tried to get writable block on a read-only cache ! -------------------------------+-------------------------------------------- Reporter: oco | 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: Should be fixed in r31255. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 17:05:31 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 15:05:31 -0000 Subject: [Haiku-bugs] [Haiku] #2076: Enhance (speed-up) the way trash empties trash. In-Reply-To: <041.6a03badf4567ea1d7818e5a86b3d77d1@haiku-os.org> References: <041.6a03badf4567ea1d7818e5a86b3d77d1@haiku-os.org> Message-ID: <050.70ba0906a6e08ea32a96560036335fdc@haiku-os.org> #2076: Enhance (speed-up) the way trash empties trash. -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: axeld Type: enhancement | 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 * component: File Systems/BFS => Applications/Tracker Comment: I wouldn't want to miss the preflight. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 19:06:32 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 26 Jun 2009 17:06:32 -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.f5227f0b38de86deca6be311362554a2@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 rudolfc): Hi, That file should manually be copied to home/config/settings/kernel/drivers when needed, it doesn't get created indeed. It's in SVN at the kerneldriver folder location. If you try the current driver, make sure you also copy the new kerneldriver: shared_info was modified. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 20:46:15 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 18:46:15 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.c2fc15edea4b59b1ce3c78dd1be04c44@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by axeld): Sure. Can you please also test booting with the old IDE stack? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 20:57:58 2009 From: trac at haiku-os.org (axeld) Date: Fri, 26 Jun 2009 18:57:58 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.f61773a2db700e360e6af531d1da61c3@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Rene or Ryan, aren't you both using git? Can either of you please have a look? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri Jun 26 22:59:41 2009 From: trac at haiku-os.org (michael.weirauch) Date: Fri, 26 Jun 2009 20:59:41 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number In-Reply-To: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> References: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> Message-ID: <060.4f0758d409f4fa20100b074caa49fb33@haiku-os.org> #4042: get_cached_block: invalid block number ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): Went directly to r31260 and mounting is fine. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 01:34:36 2009 From: trac at haiku-os.org (diver) Date: Fri, 26 Jun 2009 23:34:36 -0000 Subject: [Haiku-bugs] [Haiku] #3160: [bfs] empty folders takes too much disk space In-Reply-To: <040.6aa11895764d8db2fa5e5c953ca78736@haiku-os.org> References: <040.6aa11895764d8db2fa5e5c953ca78736@haiku-os.org> Message-ID: <049.0db047ef149a73bc0e97992ca41cc1cf@haiku-os.org> #3160: [bfs] empty folders takes too much disk space ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by diver): This is a dup of #2573. Please close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 10:53:19 2009 From: trac at haiku-os.org (axeld) Date: Sat, 27 Jun 2009 08:53:19 -0000 Subject: [Haiku-bugs] [Haiku] #3160: [bfs] empty folders takes too much disk space In-Reply-To: <040.6aa11895764d8db2fa5e5c953ca78736@haiku-os.org> References: <040.6aa11895764d8db2fa5e5c953ca78736@haiku-os.org> Message-ID: <049.8b588143584a913a0c5c29df63acfc2b@haiku-os.org> #3160: [bfs] empty folders takes too much disk space -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: duplicate | Blockedby: 2573 Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 2573 Comment: Thanks for the note. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 10:55:58 2009 From: trac at haiku-os.org (axeld) Date: Sat, 27 Jun 2009 08:55:58 -0000 Subject: [Haiku-bugs] [Haiku] #4042: get_cached_block: invalid block number In-Reply-To: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> References: <051.af03565e3f41494ee6d3703402bb4137@haiku-os.org> Message-ID: <060.f31de67e3e13a214c68ba8d9c461dd04@haiku-os.org> #4042: get_cached_block: invalid block number -------------------------------+-------------------------------------------- Reporter: michael.weirauch | Owner: axeld 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 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 16:30:51 2009 From: trac at haiku-os.org (adamk) Date: Sat, 27 Jun 2009 14:30:51 -0000 Subject: [Haiku-bugs] [Haiku] #3502: Haiku stops booting when checking partitioning_system In-Reply-To: <040.c22c30ef62c9fd7e86b0baa9dd5b810f@haiku-os.org> References: <040.c22c30ef62c9fd7e86b0baa9dd5b810f@haiku-os.org> Message-ID: <049.4a3bd9ba2203a3c6dfa9263345044a45@haiku-os.org> #3502: Haiku stops booting when checking partitioning_system ---------------------------+------------------------------------------------ Reporter: adamk | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by adamk): I no longer have this machine, actually, so you might as well close the bug. Adam -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 18:46:26 2009 From: trac at haiku-os.org (idefix) Date: Sat, 27 Jun 2009 16:46:26 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.39138cb48b37785dc0c5442516bac664@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS -------------------------------+-------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Comment(by idefix): Confirmed fixed. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 19:47:21 2009 From: trac at haiku-os.org (idefix) Date: Sat, 27 Jun 2009 17:47:21 -0000 Subject: [Haiku-bugs] [Haiku] #4045: mkfs ignores noindex option first time when no argument is supplied Message-ID: <041.6b2069907d184b5735c82139e02b5d1f@haiku-os.org> #4045: mkfs ignores noindex option first time when no argument is supplied ---------------------------------------------+------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ When you don't supply an argument to the noindex option, mkfs will ignore it the first time. The second time however, it won't ignore it. Steps to reproduce: - Initialise a volume with an index: {{{ ~> mkfs -t bfs -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume "test0mkfs" has been initialized successfully! ~> lsindex /test0mkfs/ BEOS:APP_SIG last_modified name size }}} - Initialise the same volume again, but with the noindex option: {{{ ~> mkfs -t bfs -o noindex -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume "test0mkfs" has been initialized successfully! ~> lsindex /test0mkfs/ BEOS:APP_SIG last_modified name size }}} - Initialise the same volume again, using the previous command: {{{ ~> mkfs -t bfs -o noindex -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])?yes Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume "test0mkfs" has been initialized successfully! ~> lsindex /test0mkfs/ lsindex: can't open index dir of device 25 }}} When you do however supply an argument to the noindex option, mkfs won't ignore it the first time: - Initialise a volume with an index: {{{ ~> mkfs -t bfs -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume "test0mkfs" has been initialized successfully! ~> lsindex /test0mkfs/ BEOS:APP_SIG last_modified name size }}} - Initialise the same volume again, but with argument '1' supplied to the noindex option: {{{ ~> mkfs -t bfs -o noindex=1 -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume "test0mkfs" has been initialized successfully! ~> lsindex /test0mkfs/ lsindex: can't open index dir of device 27 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat Jun 27 20:01:54 2009 From: trac at haiku-os.org (axeld) Date: Sat, 27 Jun 2009 18:01:54 -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.46eda45fc9f07e1affb050763eb882c2@haiku-os.org> #4045: mkfs ignores noindex option first time when no argument is supplied ------------------------------+--------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * component: Applications/Command Line Tools => File Systems/BFS Comment: This should be a parameter parsing problem (or uninitialized value) in BFS. Since "noindex" is a boolean setting, I would think it should always get a value. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 01:24:17 2009 From: trac at haiku-os.org (fano) Date: Sat, 27 Jun 2009 23:24:17 -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.21063b44efc304a2c6002eefe830bfee@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 installed the last svn (r31262) and after I put the nvidia.settings file in the right folder... and black screen as always and NO LOGS!!! So... a little discouraged I've tried the test driver but nothing... no LOGS for me! I've tried to set switchhead to true but nothing... black screen and no logs... At this point I don't know what to do... the screen is always black, no logs... in this situation I think you have no possibility to understand my problem... I have to hope that tigerdog's log is enough for you (and that if you solve its problem ... my system continues to no log anything!!! Thanks for trying, fano -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 04:30:59 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 28 Jun 2009 02:30:59 -0000 Subject: [Haiku-bugs] [Haiku] #1636: Tracker Assert On Start: Model.cpp:822, IsNodeOpen() In-Reply-To: <043.d23cc7065c73b3fd2e71415798775e6e@haiku-os.org> References: <043.d23cc7065c73b3fd2e71415798775e6e@haiku-os.org> Message-ID: <052.8bcd671ec22a6e08a09bbd4e3b9cff8f@haiku-os.org> #1636: Tracker Assert On Start: Model.cpp:822, IsNodeOpen() -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r31286. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 15:06:21 2009 From: trac at haiku-os.org (borg1980) Date: Sun, 28 Jun 2009 13:06:21 -0000 Subject: [Haiku-bugs] [Haiku] #3858: Continuous system speaker beep after reboot In-Reply-To: <043.ff7e0c2356629ecb702e8fce1e0bdcbd@haiku-os.org> References: <043.ff7e0c2356629ecb702e8fce1e0bdcbd@haiku-os.org> Message-ID: <052.71937fc6a7f4b0c05b1936b6481f6ae6@haiku-os.org> #3858: Continuous system speaker beep after reboot -----------------------+---------------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by borg1980): I upgraded Mainboard BIOS (ASUS P5B) and problem dissapeared. So it was probably not connected with Haiku itself and we can close this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 17:12:06 2009 From: trac at haiku-os.org (jackburton) Date: Sun, 28 Jun 2009 15:12:06 -0000 Subject: [Haiku-bugs] [Haiku] #3330: [Screenshot] Input field glitch when the text is moved In-Reply-To: <042.ca52e1b3d3532b782a778f5747950a8a@haiku-os.org> References: <042.ca52e1b3d3532b782a778f5747950a8a@haiku-os.org> Message-ID: <051.6cbac5d7c2c056f4dbce31621dd809e3@haiku-os.org> #3330: [Screenshot] Input field glitch when the text is moved --------------------------------------+------------------------------------- Reporter: Adek336 | Owner: julun Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Seems to be fixed now, probably by some commit by zooey. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 17:13:06 2009 From: trac at haiku-os.org (jackburton) Date: Sun, 28 Jun 2009 15:13:06 -0000 Subject: [Haiku-bugs] [Haiku] #2134: the text in a selectable text view with/or without scrollbar is moving up and down constantly while the left button is kept pressed In-Reply-To: <043.bbc7c7241bd3bca35d327bb4b2d7be41@haiku-os.org> References: <043.bbc7c7241bd3bca35d327bb4b2d7be41@haiku-os.org> Message-ID: <052.fdbf1eca1395a16f2441deacf1578b1c@haiku-os.org> #2134: the text in a selectable text view with/or without scrollbar is moving up and down constantly while the left button is kept pressed ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3235 ------------------------+--------------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: Fixed since some time already (probably by some commit by zooey or stippi) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 17:26:43 2009 From: trac at haiku-os.org (jackburton) Date: Sun, 28 Jun 2009 15:26:43 -0000 Subject: [Haiku-bugs] [Haiku] #3315: [Terminal] colored file background is shifted after resize In-Reply-To: <040.01a0a29ca013215caf23b767a7f58946@haiku-os.org> References: <040.01a0a29ca013215caf23b767a7f58946@haiku-os.org> Message-ID: <049.9e42dd3138e37d9e81658780a21fba11@haiku-os.org> #3315: [Terminal] colored file background is shifted after resize -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by jackburton): Is this still valid ? Can't reproduce here, at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 17:53:46 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 15:53:46 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.627fbf319daf2877894cb59c03655bfc@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: 1845 | -------------------------------------+-------------------------------------- Comment(by andreasf): Hi, I've confirmed it to boot at r31290 and r31292, without {{{nvidia.settings}}} file. So I suggest you close the ticket as fixed. Thanks for your help and overall driver efforts! Andreas -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 17:59:26 2009 From: trac at haiku-os.org (bga) Date: Sun, 28 Jun 2009 15:59:26 -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.6b98b4ea2be1af2248aa1fbcdd379c62@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): Although the BColorControl thing seems to have been fixed, the SoundPlay one still persists. I tried to track it down but could not really find my way through the app_server/interface kit code in the 2 hours I had to look into it. Stippi, any chance you could take a look at this one? I will have a haiku demo next week and SoundPlay is always used during the presentations. I would rather not have to explain that there is a bug that affects it. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:00:16 2009 From: trac at haiku-os.org (bga) Date: Sun, 28 Jun 2009 16:00:16 -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.afd157bca50d25f636f0d7006076634d@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 bga): Did anyone find the time to look into this (I didn't). It is still broken and is annoying as hell. :P -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:02:36 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:02:36 -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.b58ad01084164340d7251c2b191f534a@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 | ----------------------------------+----------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) Comment: Same cause probably, but it's definitely not (just) related to switching workspaces. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:19:56 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:19:56 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.c22358d36b92874533482d5a6e6d225d@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: andreas.faerber@? (removed) Comment: @Axel: Since the original r26977 patch was mine, you could trust me that the Git part is okay! ;) What I do not have a setup for, is a build ''without'' git. The ticket reporter or anyone else with a non-svn, non-git setup should have a look. Or commit it after reviewing that it doesn't affect regular svn users, and let people reopen later if necessary - the current svn state is a regression. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:26:59 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:26:59 -0000 Subject: [Haiku-bugs] [Haiku] #2696: unimplemented functions In-Reply-To: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> References: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> Message-ID: <051.d655fb7747959bc27149daa64eaa67ba@haiku-os.org> #2696: unimplemented functions -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: 2564 | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by andreasf): * cc: andreas.faerber@? (removed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:29:57 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:29:57 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.d6568fb2273517307366d22b1da3616e@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Changes (by andreasf): * cc: andreas.faerber@? (removed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:38:41 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:38:41 -0000 Subject: [Haiku-bugs] [Haiku] #2600: PowerStatus crash In-Reply-To: <039.a725bdcfdce56161113db2b329ef170e@haiku-os.org> References: <039.a725bdcfdce56161113db2b329ef170e@haiku-os.org> Message-ID: <048.c5bc85688ce542c16eee43aa413edace@haiku-os.org> #2600: PowerStatus crash ---------------------------+------------------------------------------------ Reporter: donn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: andreas.faerber@? (removed) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:44:11 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:44:11 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.5dfb42e44a0711f09b00bd4a4d3df76c@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:45:19 2009 From: trac at haiku-os.org (korli) Date: Sun, 28 Jun 2009 16:45:19 -0000 Subject: [Haiku-bugs] [Haiku] #3858: Continuous system speaker beep after reboot In-Reply-To: <043.ff7e0c2356629ecb702e8fce1e0bdcbd@haiku-os.org> References: <043.ff7e0c2356629ecb702e8fce1e0bdcbd@haiku-os.org> Message-ID: <052.d7096b575290cdafbde1b5a5bd03dec1@haiku-os.org> #3858: Continuous system speaker beep after reboot ------------------------+--------------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:48:23 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:48:23 -0000 Subject: [Haiku-bugs] [Haiku] #2600: PowerStatus crash In-Reply-To: <039.a725bdcfdce56161113db2b329ef170e@haiku-os.org> References: <039.a725bdcfdce56161113db2b329ef170e@haiku-os.org> Message-ID: <048.cc3f6649854811a3dcf2debd7b558ebb@haiku-os.org> #2600: PowerStatus crash ---------------------------+------------------------------------------------ Reporter: donn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by andreasf): * cc: planche2k@? (added) Comment: I still don't see a crash. Installing doesn't seem to work though: I neither get an icon nor an error message. System is gcc4, SiS, desktop. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 18:49:26 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 28 Jun 2009 16:49:26 -0000 Subject: [Haiku-bugs] [Haiku] #2696: unimplemented functions In-Reply-To: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> References: <042.80c5f449cc17c57d3f29b65adc3132f6@haiku-os.org> Message-ID: <051.6eab46c21494741ae007a995a166a7c7@haiku-os.org> #2696: unimplemented functions -------------------------------+-------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: 2564 | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 21:11:31 2009 From: trac at haiku-os.org (VinDuv) Date: Sun, 28 Jun 2009 19:11:31 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.aeb4534cc61ee3b513788f2ff78f92ed@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by VinDuv): Since force_ws has been disabled by default in r31213, making the display work without the settings file, I guess this bug can be closed ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 21:17:13 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 28 Jun 2009 19:17:13 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.7946d6422904d364a0bcb66dae827e8d@haiku-os.org> #2641: [nvidia] Video problems --------------------------------------+------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: assigned => closed * resolution: => fixed Comment: Thanks VinDuv, You're right :) Closing.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun Jun 28 21:19:44 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 28 Jun 2009 19:19:44 -0000 Subject: [Haiku-bugs] [Haiku] #2643: Black screen when DVI connected (non-native resolution) In-Reply-To: <043.0786930e484a2f240575b79901142eea@haiku-os.org> References: <043.0786930e484a2f240575b79901142eea@haiku-os.org> Message-ID: <052.66e1ca52428d3e8670d61f66dfe89fb7@haiku-os.org> #2643: Black screen when DVI connected (non-native resolution) --------------------------------------+------------------------------------- Reporter: andreasf | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: 1845 --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Ok, Thanks Andreas for testing! Closing. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 01:26:17 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 28 Jun 2009 23:26:17 -0000 Subject: [Haiku-bugs] [Haiku] #4046: [DiskProbe] Simplify Jumping to File and Block Offsets Message-ID: <043.eb15edf2edadf32cb62bc887ca1bd1c5@haiku-os.org> #4046: [DiskProbe] Simplify Jumping to File and Block Offsets ------------------------------------+--------------------------------------- Reporter: bonefish | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/DiskProbe | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- My most frequent use case for DiskProbe is that I want to have a look at data at a specific file offset. The current interface requires me to calculate block number and block offset manually, enter the block number in the block text field, and then find the offset in the block. The support for expressions in the block text field helps a bit, since it allows to at least jump to the right block without need for manual calculation (e.g. "fileOffset / 512"), but it's still annoying enough to have to calculate the block offset. Long story short, make the block offset and file offset fields editable too (ideally with expression support). And select the byte at the entered offset. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 02:06:33 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 29 Jun 2009 00:06:33 -0000 Subject: [Haiku-bugs] [Haiku] #1717: Node monitoring not working correctly in BFilePanel In-Reply-To: <044.40d0bda121d2a29ed3d4dc2e4b451e32@haiku-os.org> References: <044.40d0bda121d2a29ed3d4dc2e4b451e32@haiku-os.org> Message-ID: <053.70b3dc92df1e2c51fb8ae15a86770ba0@haiku-os.org> #1717: Node monitoring not working correctly in BFilePanel -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Fixed in r31307. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 03:03:09 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 29 Jun 2009 01:03:09 -0000 Subject: [Haiku-bugs] [Haiku] #4047: Team Monitor button text unclear Message-ID: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> #4047: Team Monitor button text unclear -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The "Restart t..." button just doesn't seem to look right. For new users how are they to know that "Restart t..." is there to "Restart the Desktop". Perhaps make the button slightly wider and change the text to "Restart Desktop"? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 06:06:10 2009 From: trac at haiku-os.org (someguy) Date: Mon, 29 Jun 2009 04:06:10 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) Message-ID: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) -----------------------+---------------------------------------------------- Reporter: someguy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- File attributes are not copied correctly when using cp from the terminal. The problem is caused by a bug introduced by ticket #4015 (r31000). A change was made to cp in order to copy empty attributes in files. The fix has a bug in it however. Line 166 in haiku/trunk/src/bin/coreutils/src/copy.c currently reads: if (bytesWritten != bytesRead || bytesRead == 0) It should read: if (bytesWritten == bytesRead || bytesRead == 0) The way it currently is, it continues through the loop one more time which writes 0 bytes to the attribute which erases the bits written the first time through. The bug can be reproduced simply by copying any file with attributes from the terminal using cp. You'll find the copied file has all the attributes of the original file, but they are empty. My privately built cp with the change fixes the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 07:42:26 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 29 Jun 2009 05:42:26 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.0b132693aadefe0f9a90df4d9afe7674@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by jahaiku): Here is the lspci output from knoppix: {{{ 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 00:09.0 Ethernet controller: Conexant HCF 56k Modem (rev 08) Subsystem: Compaq Computer Corporation 623-LAN Grizzly Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Capabilities: [5c] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel modules: atyfb }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 07:43:29 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 29 Jun 2009 05:43:29 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.4e39eb357e0e56c9af127e27b1998353@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by jahaiku): Here is listdev output from Haiku: {{{ device Multimedia controller (Multimedia audio controller) [4|1|0] vendor 125d: ESS Technology device 1988: ES1988 Allegro-1 device Communication controller [7|80|0] vendor 14f1: Conexant Systems, Inc. device 1815: HCF 56k Modem device Network controller (Ethernet controller) [2|0|0] vendor 14f1: Conexant Systems, Inc. device 1803: HCF 56k Modem device Bridge (CardBus bridge) [6|7|0] vendor 104c: Texas Instruments device ac50: PCI1410 PC card Cardbus Controller device Bridge [6|80|0] vendor 8086: Intel Corporation device 7113: 82371AB/EB/MB PIIX4 ACPI device Serial bus controller (USB Controller, UHCI) [c|3|0] vendor 8086: Intel Corporation device 7112: 82371AB/EB/MB PIIX4 USB device Mass storage controller (IDE interface) [1|1|80] vendor 8086: Intel Corporation device 7111: 82371AB/EB/MB PIIX4 IDE device Bridge (ISA bridge) [6|1|0] vendor 8086: Intel Corporation device 7110: 82371AB/EB/MB PIIX4 ISA device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 1002: ATI Technologies Inc device 4c4d: Rage Mobility P/M AGP 2x device Bridge (PCI bridge, Normal decode) [6|4|0] vendor 8086: Intel Corporation device 7191: 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge device Bridge (Host bridge) [6|0|0] vendor 8086: Intel Corporation device 7190: 440BX/ZX/DX - 82443BX/ZX/DX Host bridge }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 10:02:22 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 29 Jun 2009 08:02:22 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.569994c1d58bbea60639e3d3a19ce8db@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by jahaiku): Replying to [comment:3 axeld]: > Sure. Can you please also test booting with the old IDE stack? OK, I try the old stack tonight -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 10:11:21 2009 From: trac at haiku-os.org (stippi) Date: Mon, 29 Jun 2009 08:11:21 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.bb0397814ed14f7d5f164b43f5524273@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) -----------------------+---------------------------------------------------- Reporter: someguy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Your proposed fix would definitely be wrong. Consider the case that the attribute does not fit into the temporary buffer used in the loop. Those attributes would all only get their first chunk copied. In fact, the loop looks just fine as it is, I am trying to understand what the problem is... It looks a bit as if writing 0 bytes behind an existing attribute has some effect, while it shouldn't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 10:17:59 2009 From: trac at haiku-os.org (stippi) Date: Mon, 29 Jun 2009 08:17:59 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.5c1763a3534ffeef75b34069a8812865@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) -----------------------+---------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | 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 Mon Jun 29 10:27:33 2009 From: trac at haiku-os.org (diver) Date: Mon, 29 Jun 2009 08:27:33 -0000 Subject: [Haiku-bugs] [Haiku] #3315: [Terminal] colored file background is shifted after resize In-Reply-To: <040.01a0a29ca013215caf23b767a7f58946@haiku-os.org> References: <040.01a0a29ca013215caf23b767a7f58946@haiku-os.org> Message-ID: <049.67f109a0776e45fe3b3e05dd19a28a06@haiku-os.org> #3315: [Terminal] colored file background is shifted after resize -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by diver): Try to scroll to the previous output and you should find it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 10:28:29 2009 From: trac at haiku-os.org (stippi) Date: Mon, 29 Jun 2009 08:28:29 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.fe856942b9f24ea363da413075bd7d13@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) -----------------------+---------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): The problem is actually in the fs_write_attr() implementation. It will always create and truncate the existing attribute. The pos argument is irrelevant. The cp loop would iterate one more time unnecessarily and try to read/write 0 bytes, but that should not have been a problem. I will commit a better loop to cp after I fixed the fs_write_attr() implementation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 11:09:00 2009 From: trac at haiku-os.org (axeld) Date: Mon, 29 Jun 2009 09:09:00 -0000 Subject: [Haiku-bugs] [Haiku] #4047: Team Monitor button text unclear In-Reply-To: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> References: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> Message-ID: <051.9cf93c9eb58c1d38b78a48a1b84ede7d@haiku-os.org> #4047: Team Monitor button text unclear --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: axeld => bonefish * component: - General => Kits/Interface Kit Comment: That's a problem that only happens sometimes, and I think it's a problem with the layout engine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 11:43:45 2009 From: trac at haiku-os.org (stippi) Date: Mon, 29 Jun 2009 09:43:45 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.cc9ac946fb8906efbe251180b5253188@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) ------------------------+--------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: With r31310, the problem is fixed. Thanks a lot for the pointer in the right direction! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 14:00:22 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 29 Jun 2009 12:00:22 -0000 Subject: [Haiku-bugs] [Haiku] #4047: Team Monitor button text unclear In-Reply-To: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> References: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> Message-ID: <051.c244976edbb3e14c1a06c366e1232640@haiku-os.org> #4047: Team Monitor button text unclear --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | 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 Jun 29 14:25:22 2009 From: trac at haiku-os.org (dancxjo) Date: Mon, 29 Jun 2009 12:25:22 -0000 Subject: [Haiku-bugs] [Haiku] #4049: HDA driver doesn't produce audio Message-ID: <042.df0ee4320ba94f885cfea007cb95f578@haiku-os.org> #4049: HDA driver doesn't produce audio -------------------------------+-------------------------------------------- Reporter: dancxjo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Running SVN 31315 on real hardware. lspci in Linux says: 00:10.1 Audio device [0403]: nVidia Corporation MCP51 High Definition Audio [10de:026c] (rev a2) When I start up Haiku, the sound card "snaps" and then plays no sound whatsoever, though the driver appears to be loaded. The maximum volume in the Media Preflet is 0dB...is that normal? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 15:45:32 2009 From: trac at haiku-os.org (VinDuv) Date: Mon, 29 Jun 2009 13:45:32 -0000 Subject: [Haiku-bugs] [Haiku] #2489: No boot when HyperThreading is activated In-Reply-To: <041.b2aecae886747a7c51d2dc551386ed43@haiku-os.org> References: <041.b2aecae886747a7c51d2dc551386ed43@haiku-os.org> Message-ID: <050.d60f8f359425e2e545f71dc4f86eb78f@haiku-os.org> #2489: No boot when HyperThreading is activated --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by VinDuv): I made new tests with Haiku r31297. The boot process goes further (I can access the boot menu), but it stops before the first icon light up. Haiku still runs fine if HyperThreading is disabled.[[BR]] Should I open a new bug, or update this one ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 16:18:46 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 29 Jun 2009 14:18:46 -0000 Subject: [Haiku-bugs] [Haiku] #4047: Team Monitor button text unclear In-Reply-To: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> References: <042.24ee8c600331c732694d5a4f147ab8db@haiku-os.org> Message-ID: <051.b3649f5703de1e5d78bde61606cfa776@haiku-os.org> #4047: Team Monitor button text unclear ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r31316. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 16:31:42 2009 From: trac at haiku-os.org (someguy) Date: Mon, 29 Jun 2009 14:31:42 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.19a68ea939661fcea4138bcbb7e3c4a9@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) ------------------------+--------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by someguy): Thanks Stippi!! I came to my fix by reading the docs on fs_write_attr(). It says that it is an incomplete implementation and that pos is supposed to be ignored. It also says that you can basically write to an attribute only once as the next write will completely replace the attribute contents, even if the old data is larger than the new. In the case of the loop, it should actually never go through the loop more than once. If you change this behavior in fw_write_attr(), you could break a lot of existing apps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 16:34:57 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 29 Jun 2009 14:34:57 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.ae8a2228d5044f05895ad6f77a602d84@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) ------------------------+--------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by anevilyak): Replying to [comment:5 someguy]: > If you change this behavior in fw_write_attr(), you could break a lot of existing apps. That seems unlikely, the majority of apps do it via BNode/BFile's WriteAttr call, comparatively few use the low level C API directly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:13:46 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 29 Jun 2009 15:13:46 -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.d4e3a64f6dafd1b1aa8d7171beeb4aa9@haiku-os.org> #1072: Write an HDA audio driver and add-on -------------------------------+-------------------------------------------- Reporter: axeld | Owner: ithamar Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: x86 Blocking: 3193 | -------------------------------+-------------------------------------------- Comment(by scottmc): Replying to [comment:60 scottmc]: > Replying to [comment:25 scottmc]: > > Sound is now working on my nvidia based laptop now (Compaq cq50-215nr). Nice work! > > > > It used to work on my cq50-215nr, but hasn't for the last month or two. Media prefs show that it's detected, but I get no sound. I've attached a syslog and the output of listdev in case that can be of any help tracking down why it's no longer working on this model. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:21:25 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 29 Jun 2009 15:21:25 -0000 Subject: [Haiku-bugs] [Haiku] #3797: Smarter window sizing for Expander's "show contents" feature In-Reply-To: <048.1d87b3214fed252c58acff95773ebe39@haiku-os.org> References: <048.1d87b3214fed252c58acff95773ebe39@haiku-os.org> Message-ID: <057.2bbdd81930e7f8e1d8623e6364566f42@haiku-os.org> #3797: Smarter window sizing for Expander's "show contents" feature -----------------------------------+---------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Expander | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by scottmc): dupe of #1072? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:24:19 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 29 Jun 2009 15:24:19 -0000 Subject: [Haiku-bugs] [Haiku] #3797: Smarter window sizing for Expander's "show contents" feature In-Reply-To: <048.1d87b3214fed252c58acff95773ebe39@haiku-os.org> References: <048.1d87b3214fed252c58acff95773ebe39@haiku-os.org> Message-ID: <057.fe46b62fcf780743b67c84a588db29a7@haiku-os.org> #3797: Smarter window sizing for Expander's "show contents" feature -----------------------------------+---------------------------------------- Reporter: jonas.kirilla | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Expander | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by scottmc): Replying to [comment:2 scottmc]: > dupe of #1072? Opps wrong ticket, ignore that last comment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:26:18 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 29 Jun 2009 15:26:18 -0000 Subject: [Haiku-bugs] [Haiku] #4049: HDA driver doesn't produce audio In-Reply-To: <042.df0ee4320ba94f885cfea007cb95f578@haiku-os.org> References: <042.df0ee4320ba94f885cfea007cb95f578@haiku-os.org> Message-ID: <051.4904f992d5dc6c8f2ecccc2b8582da93@haiku-os.org> #4049: HDA driver doesn't produce audio -------------------------------+-------------------------------------------- Reporter: dancxjo | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by scottmc): This ticket and #3794 are dupes of #1072. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:48:57 2009 From: trac at haiku-os.org (stippi) Date: Mon, 29 Jun 2009 15:48:57 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.946d938ae62031889d18c3fd2e646eac@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) ------------------------+--------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by stippi): It wouldn't be good to change the behavior even if there was only a slim chance of breaking any app. However, I changed it such that writing chunks in a loop is now possible, but passing an offset of 0 will truncate any existing attribute of the same name. This means that only apps which passed an uninitialized pos argument (with a random value) could be broken now. I guess taking that risk is acceptable. :-) In any case it's important that writing attributes in chunks is possible, otherwise you limit the maximum argument length drastically, since it would otherwise need to fit into a single allocation. As in the example of the cp copy loop, it wouldn't support attributes larger than 64K. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 17:57:53 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 29 Jun 2009 15:57:53 -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.3315dbb2521c619cb91ab337e53e3411@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: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: 3156 | --------------------------+------------------------------------------------- Changes (by anevilyak): * owner: bonefish => zooey -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:01:13 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 29 Jun 2009 16:01:13 -0000 Subject: [Haiku-bugs] [Haiku] #3502: Haiku stops booting when checking partitioning_system In-Reply-To: <040.c22c30ef62c9fd7e86b0baa9dd5b810f@haiku-os.org> References: <040.c22c30ef62c9fd7e86b0baa9dd5b810f@haiku-os.org> Message-ID: <049.32dca5a0cb90dba9a27194c58619d2ba@haiku-os.org> #3502: Haiku stops booting when checking partitioning_system ----------------------------+----------------------------------------------- Reporter: adamk | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => invalid Old description: > I have a dual Xeon that I am trying to install Haiku on. It's an intel > ICH5 motherboard. I have a USB disk that I installed Haiku on from > another machine and am attempting to boot off the USB disk. It works on > one machine, but on this xeon, it stops booting with: > > Welcome to the Haiku boot loader! > > number of drives: 4 > > add_partitions_for(0x00105714, mountFS = no) > > add_partitions_for(fd = 0, mountFS = no) > > 0x00105a90 Partition::Partition > > 0x00105a90 Partition::Scan() > > check for partitioning_system: Amiga Partition Map > > check for partitioning_system: EFI GUID Partition Map > > check for partitioning_system: Intel Partition Map > > priority: 810 > > check for partitioning_system: Intel Extended Partition > > check for partitioning_system: Apple Partition Map > > The Xeon has three ATA hard drives, with FreeBSD and Vista on two, and > another one setup to use for Haiku, if I can get it to boot. > > I am attaching the full serial debug log > > Adam New description: I have a dual Xeon that I am trying to install Haiku on. It's an intel ICH5 motherboard. I have a USB disk that I installed Haiku on from another machine and am attempting to boot off the USB disk. It works on one machine, but on this xeon, it stops booting with: Welcome to the Haiku boot loader! number of drives: 4 add_partitions_for(0x00105714, mountFS = no) add_partitions_for(fd = 0, mountFS = no) 0x00105a90 Partition::Partition 0x00105a90 Partition::Scan() check for partitioning_system: Amiga Partition Map check for partitioning_system: EFI GUID Partition Map check for partitioning_system: Intel Partition Map priority: 810 check for partitioning_system: Intel Extended Partition check for partitioning_system: Apple Partition Map The Xeon has three ATA hard drives, with FreeBSD and Vista on two, and another one setup to use for Haiku, if I can get it to boot. I am attaching the full serial debug log Adam -- Comment: Thanks for the update. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:19:29 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 29 Jun 2009 16:19:29 -0000 Subject: [Haiku-bugs] [Haiku] #4048: Attributes not correctly copied (caused by fix to ticket #4015) In-Reply-To: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> References: <042.7697e500ef0066daf983d434adedbebc@haiku-os.org> Message-ID: <051.aa6c5f1f587897b45d41734023d9ef18@haiku-os.org> #4048: Attributes not correctly copied (caused by fix to ticket #4015) ------------------------+--------------------------------------------------- Reporter: someguy | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): Regarding the copy mechanism I still don't see why cp uses a different implementation than copyattr. IMO it would make sense to sync those two to make sure they both behave the same and are correct. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:31:36 2009 From: trac at haiku-os.org (idefix) Date: Mon, 29 Jun 2009 16:31:36 -0000 Subject: [Haiku-bugs] [Haiku] #3292: "Restart tracker" button shortened to "Restart t..." In-Reply-To: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> References: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> Message-ID: <051.93defa226848c68bafda7076b073dc5a@haiku-os.org> #3292: "Restart tracker" button shortened to "Restart t..." --------------------------------+------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by idefix): This bug is fixed with changeset:31316, see ticket:4047. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:32:44 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 29 Jun 2009 16:32:44 -0000 Subject: [Haiku-bugs] [Haiku] #3292: "Restart tracker" button shortened to "Restart t..." In-Reply-To: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> References: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> Message-ID: <051.bc6dd2a988e5a34d179f6fc4db8780da@haiku-os.org> #3292: "Restart tracker" button shortened to "Restart t..." ---------------------------------+------------------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Thanks for the update :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:37:18 2009 From: trac at haiku-os.org (axeld) Date: Mon, 29 Jun 2009 16:37:18 -0000 Subject: [Haiku-bugs] [Haiku] #3292: "Restart tracker" button shortened to "Restart t..." In-Reply-To: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> References: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> Message-ID: <051.3a7e9b26c7085f802d5ab6306d23897a@haiku-os.org> #3292: "Restart tracker" button shortened to "Restart t..." ---------------------------------+------------------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: closed => reopened * resolution: fixed => -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 18:37:34 2009 From: trac at haiku-os.org (axeld) Date: Mon, 29 Jun 2009 16:37:34 -0000 Subject: [Haiku-bugs] [Haiku] #3292: "Restart tracker" button shortened to "Restart t..." In-Reply-To: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> References: <042.dec2faa764a62477f7237a27be6ceac5@haiku-os.org> Message-ID: <051.6702aac1c08822586626e511a29dc8a2@haiku-os.org> #3292: "Restart tracker" button shortened to "Restart t..." ---------------------------------+------------------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Blockedby: 4047 Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => duplicate * blockedby: => 4047 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 22:46:09 2009 From: trac at haiku-os.org (Pete) Date: Mon, 29 Jun 2009 20:46:09 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.e427d476f4baac477c67fd72f6b4a34f@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by Pete): Tracked it down [after a long and convoluted journey...(:-/] The 'volumeWhich' switch (in desklink state) was somehow set to VOLUME_USE_PHYS_OUTPUT, which apparently is not compatible with the Crystal chip and/or OSS. (How this happened I'm not clear, as it seemed to be that way from the moment I installed the rev.) Finding the item in "Options" in the volume control menu and unsetting it fixed things, and sound works as it did before. I see a series of checks in MixerControl::MixerControl(...) that try to handle the various card possibilities, but maybe it doesn't cover my machine. If it fails, though, the error seems to be 'PRINT'ed (to syslog?); maybe it should put a message right in the volume control or something. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon Jun 29 22:53:21 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 29 Jun 2009 20:53:21 -0000 Subject: [Haiku-bugs] [Haiku] #3510: BWindow filters do not receive mouse clicks In-Reply-To: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> References: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> Message-ID: <051.2c2877c940f6ee836426ef2b5e140ed2@haiku-os.org> #3510: BWindow filters do not receive mouse clicks ----------------------------------+----------------------------------------- Reporter: matjako | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by jackburton): Does it change in any way if you use B_ANY_SOURCE instead of B_LOCAL_SOURCE ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 06:41:08 2009 From: trac at haiku-os.org (richienyhus) Date: Tue, 30 Jun 2009 04:41:08 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.871304b6550c8de70c22bdf1a6effadc@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): Gday, I do have another screen, but I have lent it to a family member for a good while. I will have to convince them that this will not affect their data, so it may take awhile to get back to you on that. I will try the special version of the driver in the next few days, as for the normal driver I will add the log file after this message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 07:52:03 2009 From: trac at haiku-os.org (jahaiku) Date: Tue, 30 Jun 2009 05:52:03 -0000 Subject: [Haiku-bugs] [Haiku] #4041: no boot partition found while booting alpha-cd In-Reply-To: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> References: <042.8725ef89dd65844a0bde4c981caa74ec@haiku-os.org> Message-ID: <051.ef4e24c1cab62b4104a37002452e4053@haiku-os.org> #4041: no boot partition found while booting alpha-cd --------------------------+------------------------------------------------- Reporter: jahaiku | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by jahaiku): Here are the results of the boot test from yesterday evening: Boot from HD with old IDE: OK[[BR]] Boot from HD with new ATA: OK[[BR]] Boot from CDROM with old IDE: OK[[BR]] Boot from CDROM with new ATA: Error as in the attached screenshot[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 11:00:41 2009 From: trac at haiku-os.org (aldeck) Date: Tue, 30 Jun 2009 09:00:41 -0000 Subject: [Haiku-bugs] [Haiku] #1636: Tracker Assert : Model.cpp:822, IsNodeOpen() (was: Tracker Assert On Start: Model.cpp:822, IsNodeOpen()) In-Reply-To: <043.d23cc7065c73b3fd2e71415798775e6e@haiku-os.org> References: <043.d23cc7065c73b3fd2e71415798775e6e@haiku-os.org> Message-ID: <052.3b20443e90e04e2d745826c9c5e08be3@haiku-os.org> #1636: Tracker Assert : Model.cpp:822, IsNodeOpen() -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by aldeck): * status: closed => reopened * resolution: fixed => Comment: Although it doesn't fail on start anymore (ie: opening desktop), the same problem is still present when opening some folders/file panels or when quiting Tracker with some folders open, making the debug build quite unpractical to use. Needs some more investigation.. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 11:11:34 2009 From: trac at haiku-os.org (aldeck) Date: Tue, 30 Jun 2009 09:11: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.f0ba79840a175615f24b4ef18e0243e7@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): Has anyone found a reproducible case? If not, can you give more details about what you where doing (and compiler/smp)? Also looked at descriptions of #4038 and #3914. I tried hard but i'm still unable to reproduce here with r31316 gcc2 4cpus. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 11:11:44 2009 From: trac at haiku-os.org (aldeck) Date: Tue, 30 Jun 2009 09:11:44 -0000 Subject: [Haiku-bugs] [Haiku] #4038: Tracker random crash (GCC4 - r31165) In-Reply-To: <041.c149b55b4da6424f2ea2f86675f80047@haiku-os.org> References: <041.c149b55b4da6424f2ea2f86675f80047@haiku-os.org> Message-ID: <050.7329d592e19942112acf6a1603d0154d@haiku-os.org> #4038: Tracker random crash (GCC4 - r31165) -----------------------------------+---------------------------------------- Reporter: miqlas | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: duplicate | Blockedby: 3710 Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Comment(by aldeck): miqlas: Could you give more details in #3710. Thanks :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 11:11:57 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 30 Jun 2009 09:11:57 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.8b39dd8f1c59bbadb1661cf12f209eb5@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there, You should set force_ws to false in nvidia.settings please, then retest the normal current driver. with the normal driver from which you take card logging 4, do you have a picture? If you retry with force_ws false, do all resolutions upto 1280x1024 work ok?? If not, which ones don't work? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 11:49:28 2009 From: trac at haiku-os.org (aldeck) Date: Tue, 30 Jun 2009 09:49:28 -0000 Subject: [Haiku-bugs] [Haiku] #1775: Tracker/BShelf crash on clicking replicant dragger menu (was: Tracker crash on clicking replicant menu) In-Reply-To: <044.ebb7c14ec00866cfed03126df25d3725@haiku-os.org> References: <044.ebb7c14ec00866cfed03126df25d3725@haiku-os.org> Message-ID: <053.6e1edb01b6c70fa7cc4b203c1c50ace3@haiku-os.org> #1775: Tracker/BShelf crash on clicking replicant dragger menu -----------------------------+---------------------------------------------- Reporter: elvencode | Owner: aldeck Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Old description: > Tested on build 23925 > > when clicking on the replicant grip 2/3 times moving a little the mouse > the menu (or probably the start of rendering a selection box in the > desktop) trigger a crash of the Tracker. It doesn't show up always but > quite frequently. New description: Tested on build 23925 when clicking on the replicant grip 2/3 times moving a little the mouse the menu (or probably the start of rendering a selection box in the desktop) trigger a crash of the Tracker. It doesn't show up always but quite frequently. edit: since r29949, it can only happen with a custom dragger popup menu. (cf. BeBook) -- Comment(by aldeck): made the summary/description a bit more exact -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 12:02:05 2009 From: trac at haiku-os.org (matjako) Date: Tue, 30 Jun 2009 10:02:05 -0000 Subject: [Haiku-bugs] [Haiku] #3510: BWindow filters do not receive mouse clicks In-Reply-To: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> References: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> Message-ID: <051.308a453b135224e4e1ec659f2b587ed4@haiku-os.org> #3510: BWindow filters do not receive mouse clicks ----------------------------------+----------------------------------------- Reporter: matjako | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by matjako): Replying to [comment:1 jackburton]: > Does it change in any way if you use B_ANY_SOURCE instead of B_LOCAL_SOURCE ? Indeed, with B_ANY_SOURCE the above test seem to work as expected! However, with B_LOCAL_SOURCE it is now totally erratic. Even MOUSE_MOVED messsages arrive only sporradically or not at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 12:15:13 2009 From: trac at haiku-os.org (axeld) Date: Tue, 30 Jun 2009 10:15:13 -0000 Subject: [Haiku-bugs] [Haiku] #4002: volume control replicant does not function after reboot In-Reply-To: <045.cfae979f67b38eb1f5b7d326d6eeeca5@haiku-os.org> References: <045.cfae979f67b38eb1f5b7d326d6eeeca5@haiku-os.org> Message-ID: <054.bd7ee84c74e75be602401ed17ba230b1@haiku-os.org> #4002: volume control replicant does not function after reboot -----------------------------+---------------------------------------------- Reporter: agildehaus | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r31322. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 12:32:00 2009 From: trac at haiku-os.org (jackburton) Date: Tue, 30 Jun 2009 10:32:00 -0000 Subject: [Haiku-bugs] [Haiku] #3510: BWindow filters do not receive mouse clicks In-Reply-To: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> References: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> Message-ID: <051.85bf5ea6bda1d68546e40447066c8dc7@haiku-os.org> #3510: BWindow filters do not receive mouse clicks ----------------------------------+----------------------------------------- Reporter: matjako | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by jackburton): I guess it's correct like it is. Those mouse messages are sent by the app_server, so they are remote messages. The fact that using B_LOCAL_SOURCE you get some messages is because, IIRC, BWindow sends some of these messages itself. The bebook is also very clear about that: to receive messages from app_server, you have to use B_REMOTE_SOURCE (or B_ANY_SOURCE), so I'd be inclined to close this bug as invalid. Did that code work on beos, by chance ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 12:42:46 2009 From: trac at haiku-os.org (matjako) Date: Tue, 30 Jun 2009 10:42:46 -0000 Subject: [Haiku-bugs] [Haiku] #3510: BWindow filters do not receive mouse clicks In-Reply-To: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> References: <042.8bfe2447bed248bd1c0855221facd1ad@haiku-os.org> Message-ID: <051.0a5ad4c09104c1e1e8795f2efbc496e6@haiku-os.org> #3510: BWindow filters do not receive mouse clicks ----------------------------------+----------------------------------------- Reporter: matjako | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Application Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by matjako): Replying to [comment:3 jackburton]: > I guess it's correct like it is. Those mouse messages are sent by the app_server, so they are remote messages. The fact that using B_LOCAL_SOURCE you get some messages is because, IIRC, BWindow sends some of these messages itself. > The bebook is also very clear about that: to receive messages from app_server, you have to use B_REMOTE_SOURCE (or B_ANY_SOURCE), so I'd be inclined to close this bug as invalid. > Did that code work on beos, by chance ? I agree, the trouble is on the BeOS both LOCAL and ANY sources give the same results - which is a potential compatibility issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 12:57:38 2009 From: trac at haiku-os.org (axeld) Date: Tue, 30 Jun 2009 10:57:38 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.797b4f8719dbe56de167d33d6094463f@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * owner: marcusoverhagen => mmu_man Comment: Let's have Fran?ois a look at OSS, and if that's solved okay there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 13:31:56 2009 From: trac at haiku-os.org (mmu_man) Date: Tue, 30 Jun 2009 11:31:56 -0000 Subject: [Haiku-bugs] [Haiku] #4001: No sound (OSS) and Volume Control replicant inactive In-Reply-To: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> References: <039.d0bb94c5d478861aae4517c876764c69@haiku-os.org> Message-ID: <048.f408e6c0ccc79b10f59cc3a14c0909ff@haiku-os.org> #4001: No sound (OSS) and Volume Control replicant inactive ---------------------------+------------------------------------------------ Reporter: Pete | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by mmu_man): * status: new => assigned Comment: I added this code to desklink to optionally control the card's master volume instead, but there is no single way to identify this control in the parameterweb, so I had to try several matches from known drivers. The mixer code in the OSS node doesn't do much processing and publishes stuff almost as given by the driver from the ioctl. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 15:01:24 2009 From: trac at haiku-os.org (mt) Date: Tue, 30 Jun 2009 13:01:24 -0000 Subject: [Haiku-bugs] [Haiku] #4050: ATA driver cannot recognize 2nd HDD Message-ID: <037.f7621f6c1caeb5ffe6e3fed8f527348a@haiku-os.org> #4050: ATA driver cannot recognize 2nd HDD --------------------------+------------------------------------------------- Reporter: mt | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- With IDE driver, system can recognize 2nd HDD's BFS partitions. But, with ATA driver cannot recognize 2nd HDD's BFS partitions. (See DriveSetup screenshots)[[BR]] Tested r31322, gcc4/gcc2 hybrid[[BR]] HDDs are connected via JMB363 SATA card, not on board SATA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 16:43:34 2009 From: trac at haiku-os.org (idefix) Date: Tue, 30 Jun 2009 14:43:34 -0000 Subject: [Haiku-bugs] [Haiku] #4051: [patch] Change tab order in 'Tracker Preferences'-window Message-ID: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> #4051: [patch] Change tab order in 'Tracker Preferences'-window ----------------------------------+----------------------------------------- Reporter: idefix | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- When the Defaults and Revert buttons are disabled, the tab order is in a clockwise direction:[[Image(disabledbuttons.png)]] As soon as one of the buttons are enabled, the taborder changes to a counterclockwise direction:[[Image(enabledbuttons-old.png)]] Attached [attachment:changetaborder.patch patch] changes the order to a clockwise direction when one of the buttons are enabled:[[Image (enabledbuttons-new.png)]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 17:21:24 2009 From: trac at haiku-os.org (axeld) Date: Tue, 30 Jun 2009 15:21:24 -0000 Subject: [Haiku-bugs] [Haiku] #2860: script doesn't recognize svn revision In-Reply-To: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> References: <042.87d4d91772af70d0f787abf4d95d175e@haiku-os.org> Message-ID: <051.b15766223542ef25d829ececc9150f2e@haiku-os.org> #2860: script doesn't recognize svn revision ---------------------------+------------------------------------------------ Reporter: Adek336 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: Applied in r31333, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 18:32:49 2009 From: trac at haiku-os.org (stippi) Date: Tue, 30 Jun 2009 16:32:49 -0000 Subject: [Haiku-bugs] [Haiku] #4051: [patch] Change tab order in 'Tracker Preferences'-window In-Reply-To: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> References: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> Message-ID: <050.0a005402464180619650e9cc71780acd@haiku-os.org> #4051: [patch] Change tab order in 'Tracker Preferences'-window ----------------------------------+----------------------------------------- Reporter: idefix | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: Excellent bug-report, idefix. Gotta remember the syntax you used. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 18:34:40 2009 From: trac at haiku-os.org (stippi) Date: Tue, 30 Jun 2009 16:34:40 -0000 Subject: [Haiku-bugs] [Haiku] #4051: [patch] Change tab order in 'Tracker Preferences'-window In-Reply-To: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> References: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> Message-ID: <050.e4aa4751458c4ad07d13cb923e03db88@haiku-os.org> #4051: [patch] Change tab order in 'Tracker Preferences'-window -----------------------------------+---------------------------------------- Reporter: idefix | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Applied in r31339. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 18:55:26 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 30 Jun 2009 16:55:26 -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.c51b35c70165655bda2c7eb3940d54ac@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 mmlr): I think it has to do with the column state. It usually happens when opening a folder on a read-only volume from an old BeOS installation (with the old column info attribute format) or when opening a freshly unzipped folder (with no column info attributes at all). I think it comes up when no column state is present yet. Opening works, but then when the columns should get invalidated it crashes (most probably because of accessing a deleted BString). It might be more easily visible with single window browse enabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 19:03:37 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 30 Jun 2009 17:03:37 -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.bd7b6431cb6f85616f20a832ccc13371@haiku-os.org> #4050: ATA driver cannot recognize 2nd HDD --------------------------+------------------------------------------------- Reporter: mt | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by marcusoverhagen): * cc: mmrl (added) Comment: The jmicron controller is running in IDE/ATA compatibility mode, so AHCI is not relevant here. Also partition type being BFS is not relevant. It looks like we properly detect the harddisk, but then fail whenever trying a read access. Relevant parts from logfile: {{{ 208 KERN: PCI: [dom 0, bus 3] bus 3, device 0, function 0: vendor 197b, device 2363, revision 02 209 KERN: PCI: class_base 01, class_function 01, class_api 85 210 KERN: PCI: vendor 197b: JMicron Technologies, Inc. 211 KERN: PCI: device 2363: JMicron 20360/20363 AHCI Controller 212 KERN: PCI: info: Mass storage controller (IDE interface) 213 KERN: PCI: line_size 04, latency 00, header_type 00, BIST 00 214 KERN: PCI: ROM base host edfe0000, pci edfe0000, size 00010000 215 KERN: PCI: cardbus_CIS 00000000, subsystem_id 2363, subsystem_vendor_id 197b 216 KERN: PCI: interrupt_line 0a, interrupt_pin 01, min_grant 00, max_latency 00 217 KERN: PCI: base reg 0: host 0000e800, pci 0000e800, size 00000010, flags 09 218 KERN: PCI: base reg 1: host 0000e400, pci 0000e400, size 00000010, flags 0d 219 KERN: PCI: base reg 2: host 0000e000, pci 0000e000, size 00000010, flags 09 220 KERN: PCI: base reg 3: host 0000d800, pci 0000d800, size 00000010, flags 0d 221 KERN: PCI: base reg 4: host 0000d400, pci 0000d400, size 00000010, flags 01 222 KERN: PCI: base reg 5: host edffe000, pci edffe000, size 00002000, flags 00 223 KERN: PCI: Capabilities: PM, PCIe 556 KERN: PCI-IDE: Controller in native mode: cmd 0xe800, ctrl 0xe402, irq 10 557 KERN: PCI-IDE: init channel... 558 KERN: PCI-IDE: channel index 0 559 KERN: PCI-IDE: bus master base 0xd400 560 KERN: PCI-IDE: init channel done 561 KERN: usb hub 2: port 0: new device connected 562 KERN: ata 4: signature of device 0: 0x0000 563 KERN: ata 4: signature of device 1: 0x0000 564 KERN: ata 4-0: using DMA mode 0x16 565 KERN: ata 4: identified ATA device 0 566 KERN: ata 4-1: using DMA mode 0x16 567 KERN: ata 4: identified ATA device 1 568 KERN: ata 4 error: command failed, error bit is set: 0x04 569 KERN: publish device: node 0x80fbdf50, path disk/ata/4/master/raw, module drivers/disk/scsi/scsi_disk/device_v1 570 KERN: ata 4 error: command failed, error bit is set: 0x04 571 KERN: publish device: node 0x80fc4190, path disk/ata/4/slave/raw, module drivers/disk/scsi/scsi_disk/device_v1 572 KERN: ata 4 error: invalid target device 573 KERN: Last message repeated 12 times. 686 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/4/slave/raw) 687 KERN: intel: ep_std_ops(0x1) 688 KERN: trying: partitioning_systems/intel/extended/v1 689 KERN: returned: -1 690 KERN: intel: ep_std_ops(0x2) 691 KERN: trying: partitioning_systems/intel/map/v1 692 KERN: intel: pm_identify_partition(0, 1: 0, 80026361856, 512) 693 KERN: usb hub 22: port 0: device removed 694 KERN: das_read(): request.Wait() returned: Device timeout 695 KERN: returned: -1 696 KERN: trying: file_systems/bfs/v1 697 KERN: das_read(): request.Wait() returned: Device timeout 698 KERN: returned: -1 699 KERN: trying: file_systems/devfs/v1 700 KERN: returned: -1 701 KERN: trying: file_systems/rootfs/v1 702 KERN: returned: -1 790 KERN: device 1: /dev/disk/ata/4/slave/raw 791 KERN: media status: No error 792 KERN: device flags: 2 793 KERN: offset: 0 794 KERN: size: 80026361856 (76319.85 MB) 795 KERN: content size: 0 796 KERN: block size: 512 797 KERN: child count: 0 798 KERN: index: -1 799 KERN: status: 2 800 KERN: flags: 1 801 KERN: volume: -1 802 KERN: disk system: 803 KERN: name: 804 KERN: content name: 805 KERN: type: 806 KERN: content type: 807 KERN: params: 808 KERN: content params: }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 19:04:03 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 30 Jun 2009 17:04: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.4bdb6d5f0c379eb74c24b482ff4efb9a@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: | --------------------------+------------------------------------------------- Changes (by marcusoverhagen): * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 19:05:53 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 30 Jun 2009 17:05:53 -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.819ebbe43a301e32ae867c14cb000de9@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 marcusoverhagen): Can you please tell me the brand and type number of the harddisks? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 19:17:32 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 30 Jun 2009 17:17:32 -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.71fb4a5d118504fbb95f6c99e7e24b6d@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: | --------------------------+------------------------------------------------- Changes (by mmlr): * cc: mmrl (removed) Comment: The relevant lines seem to be: {{{ 686 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/4/slave/raw) 687 KERN: intel: ep_std_ops(0x1) 688 KERN: trying: partitioning_systems/intel/extended/v1 689 KERN: returned: -1 690 KERN: intel: ep_std_ops(0x2) 691 KERN: trying: partitioning_systems/intel/map/v1 692 KERN: intel: pm_identify_partition(0, 1: 0, 80026361856, 512) 694 KERN: das_read(): request.Wait() returned: Device timeout 695 KERN: returned: -1 696 KERN: trying: file_systems/bfs/v1 697 KERN: das_read(): request.Wait() returned: Device timeout }}} Looks like a timeout or possibly a stall. Tuning some of the timeout values could proof this. It's mmlr btw. but I'm on the bugs-list anyway, so no CC is required. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue Jun 30 20:09:42 2009 From: trac at haiku-os.org (idefix) Date: Tue, 30 Jun 2009 18:09:42 -0000 Subject: [Haiku-bugs] [Haiku] #4051: [patch] Change tab order in 'Tracker Preferences'-window In-Reply-To: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> References: <041.ff92fca08d86b903bff2ba41b144c4bb@haiku-os.org> Message-ID: <050.e676f168aa11083ada2ef40fec8f84b7@haiku-os.org> #4051: [patch] Change tab order in 'Tracker Preferences'-window -----------------------------------+---------------------------------------- Reporter: idefix | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by idefix): Replying to [comment:1 stippi]: > Excellent bug-report, idefix. Gotta remember the syntax you used. Thanks, I felt like experimenting a bit with this ticket.[[BR]] Too bad the second line of text doesn't start on a new line; it did so in the preview... Ah well, something to remember next time. Replying to [comment:2 stippi]: > Applied in r31339. Thanks a lot! Thanks! :) -- Ticket URL: Haiku The Haiku operating system.