From trac at haiku-os.org Thu May 1 00:00:22 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 22:00:22 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.ef5707d4440615a21fd9bc3d7754b309@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): Screenshot ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 00:06:45 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 22:06:45 -0000 Subject: [Haiku-bugs] [Haiku] #1779: Media Player Crash Playing mov File In-Reply-To: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> References: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> Message-ID: <049.df1d273440f07ec87f03f05ec1e851c3@haiku-os.org> #1779: Media Player Crash Playing mov File ---------------------------------------+------------------------------------ Reporter: cebif | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by korli): * owner: marcusoverhagen => dlmcpaul Comment: Assigning David ... :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 00:09:53 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 22:09:53 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.7d28d8776c5244d17f692cb8cf34c25d@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by korli): * cc: korli (removed) Comment: we just need nielx feedback. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 00:31:43 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 22:31:43 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.a2fd1efa75494945cb505718c212bf4d@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Added 'screenmode.png' showing the error message mentioned. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 00:52:52 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 22:52:52 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.de363ac566745b52c9b8d52f57003978@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): What version? What's the video card setup? Is this on real hardware? Can you provide the output of your listdev? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 01:05:01 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 23:05:01 -0000 Subject: [Haiku-bugs] [Haiku] #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 In-Reply-To: <040.da57811c77e0a1a5bc9606fd7edabfb4@haiku-os.org> References: <040.da57811c77e0a1a5bc9606fd7edabfb4@haiku-os.org> Message-ID: <049.05b67b0e11b4bb5630a455c142823be4@haiku-os.org> #1988: PANIC: ASSERT FAILED (src/system/kernel/fs/vfs.cpp:747): oldRefCount > 0 ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by bonefish): Replying to [comment:2 scottmc]: > I just had this happen as well, on r25137. I was installing from one volume to another, both volumes are 4GB and had plenty of room on them. sc shows: > stack trace for thread 540 "copy_engine" > kernel stack: 0x92b7c000 to 0x92b80000 > user stack: 0x70000000 to 0x70040000 > frame caller :function + offset > 92b7f9bc (+ 52) 8008a8ff :invoke_debugger_command + 0x00cf A few more lines of the stack trace would be nice. The lines up to ":panic" are always the same. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 01:18:56 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 23:18:56 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.bbd5a0e404a589440920e66c0c6afbbf@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Replying to [comment:3 scottmc]: > What version? What's the video card setup? Is this on real hardware? Can you provide the output of your listdev? Haiku r25268 NeoMagic MagicMedia 256AV (NM2200) 2.5M Yes: a seperate partition on my Thinkpad 570 Don't know how... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 01:35:15 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 23:35:15 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.ba03333ef19cc75936f92071ca4ce5c7@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): Some more info: 1024x768 @ 16 bits/pixel is the maximum this video card can handle in BeOS and also in Haiku, until recently this Haiku bug came up, suggesting at first there's a higher setting possible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 01:46:10 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 30 Apr 2008 23:46:10 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.c32e6a9c99dd9ebc796dc7154a14ad56@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): I have an IBM 570E sitting right next to me that does that same thing. But other than showing an invalid video mode it's doing everything else that it should, like not allowing you to pick an unsupported video mode. It's much better than it was a few months ago. See the bad colors screenshot of ticket #1169 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 02:15:58 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 00:15:58 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails In-Reply-To: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> References: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> Message-ID: <052.7856d7f1bbd4988e18754cd1517c7859@haiku-os.org> #1981: mail_daemon can not send mails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by koki): FWIW, I just tested on r25268, and sending email is not working. I still get the "email at domain.com: Error while getting a message. Name not found [Sat Mar 29 19:09:28 2008]" message window, and the pending message in the "In" folder. Can anyone else confirm? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 02:40:42 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 00:40:42 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails In-Reply-To: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> References: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> Message-ID: <052.85a0ff4ba085c523432e25a009b41bec@haiku-os.org> #1981: mail_daemon can not send mails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): Replying to [comment:5 koki]: > FWIW, I just tested on r25268, and sending email is not working. I still get the "email at domain.com: Error while getting a message. Name not found [Sat Mar 29 19:09:28 2008]" message window, and the pending message in the "In" folder. Can anyone else confirm? r25275, working fine here! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 03:18:34 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 01:18:34 -0000 Subject: [Haiku-bugs] [Haiku] #1981: mail_daemon can not send mails In-Reply-To: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> References: <043.4176d1431dea833759361f5bf70d5819@haiku-os.org> Message-ID: <052.9039d166025fc8011bf0b0d771f13692@haiku-os.org> #1981: mail_daemon can not send mails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by bga): Also works perfectly here. Are you sure you are not either running an older version of MDR (maybe from a different partition) or are using settings created with an older version? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 03:39:14 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 01:39:14 -0000 Subject: [Haiku-bugs] [Haiku] #1779: Media Player Crash Playing mov File In-Reply-To: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> References: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> Message-ID: <049.35c3c824b5b51cc4eea8a7e96e66ff2a@haiku-os.org> #1779: Media Player Crash Playing mov File ---------------------------------------+------------------------------------ Reporter: cebif | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by cebif): Replying to [comment:2 dlmcpaul]: > Any chance you can put links to the files you are trying to play? > > I did the mov and mp4 reader code and the crash is occuring in the mov reader or it is doing something wrong. I tried to upload links as atachments from a shared folder I created on my computer but the links were uploading the whole files. That is tens of Mbs. How can I put these links? If I try and link from the original website that I downloaded from, they are gone. I suppose I could find newer mov files to link from. If I link files directly from my systen (Ubuntu 8.04), is it possible? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 03:51:51 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 01:51:51 -0000 Subject: [Haiku-bugs] [Haiku] #1779: Media Player Crash Playing mov File In-Reply-To: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> References: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> Message-ID: <049.b9f6090ef755a25b47cb11c394a7d5c4@haiku-os.org> #1779: Media Player Crash Playing mov File ---------------------------------------+------------------------------------ Reporter: cebif | Owner: dlmcpaul Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by dlmcpaul): * status: new => assigned Comment: Replying to [comment:4 cebif]: > Replying to [comment:2 dlmcpaul]: > > Any chance you can put links to the files you are trying to play? > > > > I did the mov and mp4 reader code and the crash is occuring in the mov reader or it is doing something wrong. > I tried to upload links as atachments from a shared folder I created on my computer but the links were uploading the whole files. > That is tens of Mbs. How can I put these links? > If I try and link from the original website that I downloaded from, they are gone. I suppose I could find newer mov files to link from. > If I link files directly from my systen (Ubuntu 8.04), is it possible? You are welcome to e-mail 1 file to me at dlmcpaul AT gmail.com if you have the upload capacity Cheers David -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 02:49:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 00:49:26 -0000 Subject: [Haiku-bugs] [Haiku] #2174: [mail_daemon] In Mail Status window one part of the text overlaps another In-Reply-To: <043.ca64843b15a26101f4a0d01eeff03dfd@haiku-os.org> References: <043.ca64843b15a26101f4a0d01eeff03dfd@haiku-os.org> Message-ID: <052.0c27d302cddaf4d6e5bbba807bb75ede@haiku-os.org> #2174: [mail_daemon] In Mail Status window one part of the text overlaps another ----------------------------------+----------------------------------------- Reporter: kaoutsis | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Resolution: fixed | Platform: All ----------------------------------+----------------------------------------- Comment (by kaoutsis): Replying to [comment:3 stippi]: > Fixed in r25244. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 07:15:32 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 05:15:32 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.bb1e924513d28e1cb04910035e6f6d78@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by tigerdog): * platform: All => x86 * component: - General => Drivers/Graphics Comment: Replying to [ticket:2071 tigerdog]: > Starting with r24669 nightly, Haiku does not correctly display accelerated video on my nVidia 7600GS card. Monitor sees no video signal. > > Nightly r24635 works OK. 24669 or later works OK in VESA mode. > > Copying nvidia accelerant and driver from older rev into non-working rev does NOT solve the problem. In reviewing commits, it seems the possible causes may be commits in rev 24638 or 24648. Is there some way to further narrow this problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 08:22:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 06:22:07 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.1afcf575a390a72c44033d3d10fd1f7e@haiku-os.org> #2188: Screen prefs. window shows wrong options ------------------------+--------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by meanwhile): It seems this bug came along with the fix for those bad coulours (which used to be on the 570 as well). BTW, you can still read (in the last comment from that ticket) that at the time I thought a better graphics setting had become available... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 11:01:01 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 09:01:01 -0000 Subject: [Haiku-bugs] [Haiku] #2083: EHCI bus hanging at boot. In-Reply-To: <038.f0c26633f412f90967d8536305dae776@haiku-os.org> References: <038.f0c26633f412f90967d8536305dae776@haiku-os.org> Message-ID: <047.f7242631d1d304f30ed4b7d25a6c98ff@haiku-os.org> #2083: EHCI bus hanging at boot. --------------------------+------------------------------------------------- Reporter: bga | Owner: mmlr Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by pieterpan): I knew that :-), but since I got no output I gave it a try anyway... I have enabled TRACE_USB in usb_p as you said, and now we get lots of output, hope it is useful for you. Sorry it took a while, i had taken the pics with my nice camera, but we're in the middle of a move, so that camera is now in our new house :) You'll have to make do with the crappy camera. The most interesting bit probably is (Only after I pressed F12, the "Last message repeated..." appeared) {{{ usb_uhci: installing interrupt handler usb_uhci: host controller halted Last message repeated 4459366 times }}} Let me know if I can try something else -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 11:10:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 09:10:03 -0000 Subject: [Haiku-bugs] [Haiku] #2181: BPopUpMenu doesn't accept keyboard navigation In-Reply-To: <041.4c73c76489f97ac8560540ab9c586a22@haiku-os.org> References: <041.4c73c76489f97ac8560540ab9c586a22@haiku-os.org> Message-ID: <050.82e4ba263a987515a9a6668ce4d4676f@haiku-os.org> #2181: BPopUpMenu doesn't accept keyboard navigation ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): It seems that after selection by the keyboard, _SelectItem(NULL) is called in BMenu::_Track()'s "Mouse pointer outside menu" block and reset the selection. I tried to modify, but failed. My bad code is here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 11:17:14 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 09:17:14 -0000 Subject: [Haiku-bugs] [Haiku] #2190: Updated posix license headers Message-ID: <041.60a14743bdbcab73878a305c1e419a75@haiku-os.org> #2190: Updated posix license headers -------------------------+-------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Attached is a patch that updates the posix headers' licence headers according to the coding guidelines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 11:19:20 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 09:19:20 -0000 Subject: [Haiku-bugs] [Haiku] #2191: Updated posix license headers Message-ID: <041.8b8ccb02b6acbd108b9c8f59fcce9f47@haiku-os.org> #2191: Updated posix license headers -------------------------+-------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Attached is a patch that updates the posix headers' licence headers according to the coding guidelines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 11:25:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 09:25:47 -0000 Subject: [Haiku-bugs] [Haiku] #2190: Updated posix license headers In-Reply-To: <041.60a14743bdbcab73878a305c1e419a75@haiku-os.org> References: <041.60a14743bdbcab73878a305c1e419a75@haiku-os.org> Message-ID: <050.42b905b486fc9edf7f318751c786ac9e@haiku-os.org> #2190: Updated posix license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by ekdahl): Oops, please close this. See #2191 instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 12:05:44 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 10:05:44 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.04adea2fdd43b9b4eb8413f0095e1b54@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by kaliber): I think I have similar situation with rev25276: {{{ wait interval 927868, scan pages 1096, free 3785, target 311 bfs: Insert:1306: Name in use Last message repeated 3 times. wait interval 925085, scan pages 1118, free 3773, target 323 bfs: Insert:1306: Name in use Last message repeated 2 times. PANIC: vnode 3:545947 already exists (node = 0x90f91300, vnode->node = 0x90df4180)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 192 "svn" kernel stack: 0x90a6c000 to 0x90a70000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 90a6f7fc (+ 52) 8008b2a3 :invoke_debugger_command + 0x00cf 90a6f830 (+ 64) 8008c04c :_ParseCommand__16ExpressionParserRi + 0x01f8 90a6f870 (+ 48) 8008ba3e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 90a6f8a0 (+ 228) 8008d160 :evaluate_debug_command + 0x0088 90a6f984 (+ 64) 80089dde :kernel_debugger_loop__Fv + 0x017a 90a6f9c4 (+ 48) 8008aa91 :kernel_debugger + 0x010d 90a6f9f4 (+ 192) 8008a979 :panic + 0x0029 90a6fab4 (+ 64) 80051015 :new_vnode + 0x0061 90a6faf4 (+ 80) 80588318 :New__14InodeAllocatorP9block_runUiR9block_runP12fs_vnode_opsPP5Inode + 0x0170 90a6fb44 (+ 176) 8058eab9 :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5InodeP12fs_vnode_opsUl + 0x0579 90a6fbf4 (+ 96) 80597829 :bfs_create__FP9fs_volumeP8fs_vnodePCciiPPvPx + 0x0125 90a6fc54 (+ 352) 800532ec :create_vnode__FP5vnodePCciib + 0x0188 90a6fdb4 (+ 320) 80053682 :file_create__FiPciib + 0x005a 90a6fef4 (+ 80) 80058994 :_user_open + 0x00bc 90a6ff44 (+ 100) 8009b2a2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x90a6ffa8 (end = 0x90a70000) eax 0x4f ebx 0x462c30 ecx 0x7ffe6374 edx 0xffff0104 esi 0x190ec0a0 edi 0x190ec1e0 ebp 0x7ffe63a0 esp 0x90a6ffdc eip 0xffff0104 eflags 0x202 vector: 0x63, error code: 0x0 90a6ffa8 (+ 0) ffff0104 7ffe63a0 (+ 64) 003293be :unknown + 0x113be 7ffe63e0 (+ 64) 002c7ff5 :unknown + 0xcff5 7ffe6420 (+ 80) 0023a918 :unknown + 0x5918 7ffe6470 (+ 64) 0024371a :unknown + 0xe71a 7ffe64b0 (+ 80) 00243c89 :unknown + 0xec89 7ffe6500 (+ 64) 00244013 :unknown + 0xf013 7ffe6540 (+ 64) 0023ba83 :unknown + 0x6a83 7ffe6580 (+ 64) 0023bc46 :unknown + 0x6c46 7ffe65c0 (+ 64) 0024d480 :unknown + 0x18480 7ffe6600 (+ 176) 0024dd6d :unknown + 0x18d6d 7ffe66b0 (+ 64) 002b4bc5 :unknown + 0x1bc5 7ffe66f0 (+ 96) 002a7b70 :unknown + 0x7b70 7ffe6750 (+ 64) 00352430 :unknown + 0xf430 7ffe6790 (+ 160) 002fb0d9 :unknown + 0x50d9 7ffe6830 (+ 64) 002fa83a :unknown + 0x483a 7ffe6870 (+ 48) 002fa02d :unknown + 0x402d 7ffe68a0 (+ 64) 002f9f8f :unknown + 0x3f8f 7ffe68e0 (+ 48) 0035284e :unknown + 0xf84e 7ffe6910 (+ 48) 003527ff :unknown + 0xf7ff 7ffe6940 (+ 48) 00351604 :unknown + 0xe604 7ffe6970 (+ 48) 0034915e :unknown + 0x615e 7ffe69a0 (+ 48) 00349c12 :unknown + 0x6c12 7ffe69d0 (+ 112) 002add17 :unknown + 0xdd17 7ffe6a40 (+ 112) 002adf57 :unknown + 0xdf57 7ffe6ab0 (+ 112) 002a8f85 :unknown + 0x8f85 7ffe6b20 (+ 176) 0023a1dc :unknown + 0x51dc 7ffe6bd0 (+ 160) 00230426 :unknown + 0x18426 7ffe6c70 (+ 64) 002304f3 :unknown + 0x184f3 7ffe6cb0 (+ 80) 0020c9b1 :unknown + 0xc9b1 7ffe6d00 (+ 640) 002091fc :unknown + 0x91fc 7ffe6f80 (+ 44) 00204c45 :unknown + 0x4c45 7ffe6fac (+ 48) 0010078e 2798:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 2797:svn_main_stack at 0x7efe7000 + 0xffffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 12:08:25 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 10:08:25 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.ed1d8ad62e1ad28a4917fb36bf1175e7@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by kaliber): Replying to [comment:7 kaliber]: > I think I have similar situation with rev25276: Sorry it was revision 25277 (using cutex in vm_cache) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 13:20:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 11:20:03 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.f32b7d365db10f39140005d6f72b6725@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Changes (by axeld): * component: - General => Drivers/Graphics/NeoMagic Comment: Did you cut/changed the 1stbootsituation.png in some way? Looks like it started up with 640x480 and 256 colors. What video mode is chosen by the boot loader? Can you provide a syslog? Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 13:44:53 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 11:44:53 -0000 Subject: [Haiku-bugs] [Haiku] #2189: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf0f, ip 0x80297ab0 In-Reply-To: <042.51fa43507850629cdba3cfc56283f855@haiku-os.org> References: <042.51fa43507850629cdba3cfc56283f855@haiku-os.org> Message-ID: <051.8d63dddc6d9826784ba448a9abd5ff10@haiku-os.org> #2189: PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf0f, ip 0x80297ab0 -------------------------------------+-------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * priority: normal => critical * resolution: => fixed * status: new => closed * component: - General => Network & Internet/TCP * milestone: R1 => R1/alpha1 Comment: Thanks, I could reproduce the problem easily with "wget ftp://..."; Ingo already notified me about a potential problem in my recent TCP changes, and it was exactly that. It's fixed in r25278. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 15:25:38 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 13:25:38 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.22e6b651bd9a2921d89df63dba2375a4@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU ---------------------------------+------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by andreasf): At r25278 (with Axel's network fixes) hangs in {{{addr_connect}}} test, without meaningful backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 16:00:12 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 14:00:12 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.c74ea96194e7493b130e55417a38df76@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Changes (by axeld): * priority: normal => critical * status: new => assigned * component: Network & Internet => Network & Internet/TCP * milestone: R1 => R1/alpha1 Comment: This might be the same problem that happens with the OpenSSH forwarding test - I will look into that in the next days. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 16:37:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 14:37:26 -0000 Subject: [Haiku-bugs] [Haiku] #2190: Updated posix license headers In-Reply-To: <041.60a14743bdbcab73878a305c1e419a75@haiku-os.org> References: <041.60a14743bdbcab73878a305c1e419a75@haiku-os.org> Message-ID: <050.112edacdb47d72081bfc40f13c5f425e@haiku-os.org> #2190: Updated posix license headers --------------------------+------------------------------------------------- Reporter: ekdahl | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: duplicate | Platform: All --------------------------+------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2190. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 22:19:14 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 20:19:14 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update to 1.2.25 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.a0f0c9aede763132a7d94b99679748a4@haiku-os.org> #2018: libpng needs update to 1.2.25 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): Seems they fixed another security issue in 1.2.26, 1.2.28 is out as I write this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 22:19:31 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 20:19:31 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.53ef289eacf70cfe09dcf0ac2e0a5f30@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): No, no changes (that'd be cheating!). What you see is what I got. I only brought it from 54 to 18 kb to be able to use as attachment, but that's another matter. I didn't touch the boot loader so I hope the answer 'the video mode was default' is workable. About the syslog: just like scottmc's 'output of the listdev': I would like to provide those data, if only I knew how to collect them... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 22:27:05 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 20:27:05 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.22cbd0418ffd5dca1d6e1f77f2b10d35@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): The original is here: http://www.xs4all.nl/~rrvvww/1stbootsituation.png -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 22:41:57 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 20:41:57 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.c5946852c56819dac089b99d69153b16@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by umccullough): listdev is a commandline tool in Haiku (and BeOS?) that prints out the hardware information for all PCI devices in your machine. If you have linux running on the same machine, you can usually use "lspci -nn" instead which gives a very similar output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 23:15:54 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 21:15:54 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.571f5c1b49e4caa446a64a4092e09ac0@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by axeld): Thanks for the linked shot; it's indeed in true color, not 8-bit as I first thought. Anyway, if you have a freshly installed Haiku, just boot, and then copy and attach the file /var/log/syslog to this report - that's all :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 23:25:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 21:25:07 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.162e84f0f4d8cc979d380bf4820575dc@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): Here we go: KERN: APM version 1.2 available, flags 3. KERN: smp_acpi_probe: entry base 0x9fc00, limit 0xa0000 KERN: smp_acpi_probe: entry base 0xf0000, limit 0x100000 KERN: smp_acpi_probe: found ACPI RSDP signature at 0x000f6d00 KERN: smp: using ACPI to detect MP configuration KERN: smp: found rsdp at 0x000f6d00 oem id: PTLTD KERN: smp: rsdp points to rsdt at 0x13ffac85 KERN: smp: searching 2 entries for APIC information KERN: smp: skipping uninteresting header 'FACP' KERN: smp: skipping uninteresting header 'BOOT' KERN: smp_mp_probe: entry base 0x9fc00, limit 0xa0000 KERN: smp_mp_probe: entry base 0xf0000, limit 0x100000 KERN: VESA version = 2.0 KERN: oem string: MagicMedia 256AV 48K KERN: EDID1: 4f KERN: EDID2: ebx 0 KERN: Welcome to the Haiku boot loader! KERN: number of drives: 1 KERN: add_partitions_for(0x00105190, mountFS = no) KERN: add_partitions_for(fd = 0, mountFS = no) KERN: 0x001052e4 Partition::Partition KERN: 0x001052e4 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(1, 1069796: 0, 10056130560, 512) KERN: Partition::SetTo(): active: 80 KERN: Partition::SetTo(): active: 0 Last message repeated 9 times KERN: priority: 810 KERN: check for partitioning_system: Intel Extended Partition KERN: check for partitioning_system: Apple Partition Map KERN: intel: pm_scan_partition(1, 1069796: 0, 10056130560, 512) KERN: 0x00105438 Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x00105438 KERN: 0x00105438 Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001054ec Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x001054ec KERN: 0x001054ec Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001055a0 Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x001055a0 KERN: 0x001055a0 Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001052e4 Partition::Scan: *** scan child 0x00105438 (start = 32256, size = 98671104, parent = 0x001052e4)! KERN: 0x00105438 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(2, 1070136: 32256, 98671104, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: priority: 100 KERN: check for partitioning_system: Intel Extended Partition KERN: intel: ep_identify_partition(2, 32256, 98671104, 512) KERN: check for partitioning_system: Apple Partition Map KERN: 0x001052e4 Partition::Scan: *** scan child 0x001054ec (start = 98703360, size = 254983680, parent = 0x001052e4)! KERN: 0x001054ec Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(2, 1070316: 98703360, 254983680, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: priority: 100 KERN: check for partitioning_system: Intel Extended Partition KERN: intel: ep_identify_partition(2, 98703360, 254983680, 512) KERN: check for partitioning_system: Apple Partition Map KERN: 0x001052e4 Partition::Scan: *** scan child 0x001055a0 (start = 353687040, size = 9697605120, parent = 0x001052e4)! KERN: 0x001055a0 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: priority: 949 KERN: initialize_commpage_syscall(): sysenter/sysexit supported KERN: allocate_commpage_entry(3, 5) -> 0xffff0100 KERN: allocate_commpage_entry(2, 12) -> 0xffff0108 KERN: apm_init() KERN: code32: 0xf000, 0x4108, length 0xffff KERN: code16: 0xf000, length 0xffff KERN: data: 0x40, length 0xffff KERN: heap_attach: attached to 0x90800000 - usable range 0x90803000 - 0x90a00000 KERN: ahci: ahci_get_supported_paths KERN: found root!! KERN: add module bus_managers/isa/root/device_v1 to list KERN: PCI: pci_module_init KERN: PCI: mechanism 1 controller found KERN: PCI: [dom 0, bus 0] bus 0, device 0, function 0: vendor 8086, device 7190, revision 03 KERN: PCI: class_base 06, class_function 00, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7190: 440BX/ZX/DX - 82443BX/ZX/DX Host bridge KERN: PCI: info: Bridge (Host bridge) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host f8000000, pci f8000000, size 04000000, flags 08 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AGP KERN: PCI: [dom 0, bus 0] bus 0, device 1, function 0: vendor 8086, device 7191, revision 03 KERN: PCI: class_base 06, class_function 04, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7191: 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge KERN: PCI: info: Bridge (PCI bridge, Normal decode) KERN: PCI: line_size 00, latency 40, header_type 01, BIST 00 KERN: PCI: subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: primary_bus 00, secondary_bus 01, subordinate_bus 01, secondary_latency 40 KERN: PCI: io_base_upper_16 0000, io_base f0 KERN: PCI: io_limit_upper_16 0000, io_limit 00 KERN: PCI: memory_base f420, memory_limit f470 KERN: PCI: prefetchable_memory_base_upper32 00000000, prefetchable_memory_base f500 KERN: PCI: prefetchable_memory_limit_upper32 00000000, prefetchable_memory_limit f5f0 KERN: PCI: bridge_control 8c, secondary_status a2a0 KERN: PCI: interrupt_line 00, interrupt_pin 00 KERN: PCI: ROM base host 00000000, pci 00000000, size ?? KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 1] bus 1, device 0, function 0: vendor 10c8, device 0005, revision 20 KERN: PCI: class_base 03, class_function 00, class_api 00 KERN: PCI: vendor 10c8: Neomagic Corporation KERN: PCI: device 0005: ThinkPad 570 KERN: PCI: info: Display controller (VGA compatible controller, VGA) KERN: PCI: line_size 00, latency 80, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 00dd, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant 10, max_latency ff KERN: PCI: base reg 0: host f5000000, pci f5000000, size 01000000, flags 08 KERN: PCI: base reg 1: host f4400000, pci f4400000, size 00400000, flags 00 KERN: PCI: base reg 2: host f4200000, pci f4200000, size 00100000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 0: vendor 104c, device ac1b, revision 03 KERN: PCI: class_base 06, class_function 07, class_api 00 KERN: PCI: vendor 104c: Texas Instruments KERN: PCI: device ac1b: PCI1450 KERN: PCI: info: Bridge (CardBus bridge) KERN: PCI: line_size 08, latency 40, header_type 82, BIST 00 KERN: PCI: subsystem_id 0130, subsystem_vendor_id 1014 KERN: PCI: primary_bus 00, secondary_bus 07, subordinate_bus 08, secondary_latency b0 KERN: PCI: bridge_controKERN: l c0, secondary_status 0200 KERN: PCI: memory_base_upper32 00000000, memory_base 00000000 KERN: PCI: memory_limit_upper32 00000000, memory_limit 00000000 KERN: PCI: io_base_upper32 00000000, io_base 00000000 KERN: PCI: io_limit_upper32 00000000, io_limit 00000000 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 1: vendor 104c, device ac1b, revision 03 KERN: PCI: class_base 06, class_function 07, class_api 00 KERN: PCI: vendor 104c: Texas Instruments KERN: PCI: device ac1b: PCI1450 KERN: PCI: info: Bridge (CardBus bridge) KERN: PCI: line_size 08, latency 40, header_type 82, BIST 00 KERN: PCI: subsystem_id 0130, subsystem_vendor_id 1014 KERN: PCI: primary_bus 00, secondary_bus 09, subordinate_bus 0a, secondary_latency b0 KERN: PCI: bridge_control c0, secondary_status 0200 KERN: PCI: memory_base_upper32 00000000, memory_base 00000000 KERN: PCI: memory_limit_upper32 00000000, memory_limit 00000000 KERN: PCI: io_base_upper32 00000000, io_base 00000000 KERN: PCI: io_limit_upper32 00000000, io_limit 00000000 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 5, function 0: vendor 1013, device 6003, revision 01 KERN: PCI: class_base 04, class_function 01, class_api 00 KERN: PCI: vendor 1013: Cirrus Logic KERN: PCI: device 6003: CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] KERN: PCI: info: Multimedia controller (Multimedia audio controller) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0132, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant 04, max_latency 18 KERN: PCI: base reg 0: host f4100000, pci f4100000, size 00001000, flags 00 KERN: PCI: base reg 1: host f4000000, pci f4000000, size 00100000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 0: vendor 8086, device 7110, revision 02 KERN: PCI: class_base 06, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7110: 82371AB/EB/MB PIIX4 ISA KERN: PCI: info: Bridge KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 1: vendor 8086, device 7111, revision 01 KERN: PCI: class_base 01, class_function 01, class_api 80 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7111: 82371AB/EB/MB PIIX4 IDE KERN: PCI: info: Mass storage controller (IDE interface) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00001800, pci 00001800, size 00000010, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 2: vendor 8086, device 7112, revision 01 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7112: 82371AB/EB/MB PIIX4 USB KERN: PCI: info: Serial bus controller (USB Controller, UHCI) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 0b, interrupt_pin 04, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00001820, pci 00001820, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 3: vendor 8086, device 7113, revision 02 KERN: PCI: class_base 06, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7113: 82371AB/EB/MB PIIX4 ACPI KERN: PCI: info: Bridge KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 7, function 0: vendor 11c1, device 0448, revision 01 KERN: PCI: class_base 07, class_function 80, class_api 00 KERN: PCI: vendor 11c1: Agere Systems KERN: PCI: device 0448: Lucent Win Modem KERN: PCI: info: Communication controller KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000040, subsystem_id 0131, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant fc, max_latency 0e KERN: PCI: base reg 0: host f4101000, pci f4101000, size 00000100, flags 00 KERN: PCI: base reg 1: host 00001810, pci 00001810, size 00000010, flags 09 KERN: PCI: base reg 2: host 00002000, pci 00002000, size 00000100, flags 01 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: found root!! KERN: add module bus_managers/pci/root/device_v1 to list KERN: has connection? no KERN: module: bus_managers/isa/root/device_v1, support: 1 KERN: module: bus_managers/pci/root/device_v1, support: 1 KERN: register rest: bus_managers/isa/root/device_v1 KERN: free bus_managers/isa/root/device_v1 KERN: register rest: bus_managers/pci/root/device_v1 KERN: free bus_managers/pci/root/device_v1 KERN: get_boot_partitions(): boot volume message: KERN: field: "booted from image", type: BOOL (0x424f4f4c): KERN: [ 0] false KERN: field: "partition offset", type: LLNG (0x4c4c4e47): KERN: [ 0] 7057322496 (0x1a4a63200) KERN: field: "boot method", type: LONG (0x4c4f4e47): KERN: [ 0] 0 (0x0) KERN: field: "boot drive number", type: LLNG (0x4c4c4e47): KERN: [ 0] 128 (0x80) KERN: field: "disk identifier", type: RAWT (0x52415754): KERN: [ 0] data: "0x805e89bc", 80 bytes KERN: get_boot_partitions(): boot method type: 0 KERN: partitioning system: partitioning_systems/intel/extended/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/intel/extended/v1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KKERN: DiskDeviceManager::_AddDiskSystem() done: No error KERN: partitioning system: partitioning_systems/intel/map/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/intel/map/v1) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 1 KERN: intel: pm_std_ops(0x1) KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 0 KERN: intel: pm_std_ops(0x2) KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/bfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/bfs/v1) KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/devfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/devfs/v1) KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/rootfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/rootfs/v1) KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: number of disk systems: 5 KERN: KDiskDeviceManager::_Scan(/dev/disk) KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0.3 KERN: PCI-IDE: Controller in legacy mode: cmd 0x1f0, ctrl 0x3f6, irq 14 KERN: PCI-IDE: init channel... KERN: PCI-IDE: bus 0, device 6, function 1: vendor 8086, device 7111 KERN: PCI-IDE: channel index 0 KERN: PCI-IDE: bus master base 0x1800 KERN: PCI-IDE: init channel done KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 0 KERN: IDE: create_device: bus 0x90ad2100, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0400 KERN: IDE: scan_device_int: device 0x90ad0400, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 1 KERN: IDE: create_device: bus 0x90ad2100, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 0 KERN: IDE: destroy_device: device 0x90ad0400 KERN: IDE: cleanup_device_links: device 0x90ad0400 KERN: IDE: create_device: bus 0x90ad2100, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0400 KERN: IDE: scan_device_int: device 0x90ad0400, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 1 KERN: IDE: create_device: bus 0x90ad2100, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_dsk/device_v1 to list KERN: ahci: ahci_get_supported_paths KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_cd/device_v1 to list KERN: has connection? yes KERN: module: drivers/disk/scsi/scsi_dsk/device_v1, support: 0.6 KERN: module: drivers/disk/scsi/scsi_cd/device_v1, support: 0 KERN: tried best module: drivers/disk/scsi/scsi_dsk/device_v1: No error KERN: free drivers/disk/scsi/scsi_cd/device_v1 KERN: PCI-IDE: Controller in legacy mode: cmd 0x170, ctrl 0x376, irq 15 KERN: PCI-IDE: init channel... KERN: PCI-IDE: bus 0, device 6, function 1: vendor 8086, device 7111 KERN: PCI-IDE: channel index 1 KERN: PCI-IDE: bus master base 0x1808 KERN: PCI-IDE: init channel done KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 0 KERN: IDE: create_device: bus 0x90ad2300, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: error bit set - no device or wrong type (status: 0x51) KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 1 KERN: IDE: create_device: bus 0x90ad2300, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0c00 KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: no fast response to inquiry KERN: IDE: scan_device_int: status 0x01 KERN: IDE: scan_device_int: bKERN: usy bit not set after 100ms - probably noone there KERN: IDE: scan_device_int: aborting because busy bit not set KERN: IDE: destroy_device: device 0x90ad0c00 KERN: IDE: cleanup_device_links: device 0x90ad0c00 KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 0 KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: IDE: create_device: bus 0x90ad2300, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: error bit set - no device or wrong type (status: 0x51) KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 1 KERN: IDE: create_device: bus 0x90ad2300, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0c00 KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: no fast response to inquiry KERN: IDE: scan_device_int: status 0x01 KERN: IDE: scan_device_int: busy bit not set after 100ms - probably noone there KERN: IDE: scan_device_int: aborting because busy bit not set KERN: IDE: destroy_device: device 0x90ad0c00 KERN: IDE: cleanup_device_links: device 0x90ad0c00 KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_dsk/device_v1 to list KERN: ahci: ahci_get_supported_paths KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_cd/device_v1 to list KERN: has connection? yes KERN: module: drivers/disk/scsi/scsi_dsk/device_v1, support: 0 KERN: module: drivers/disk/scsi/scsi_cd/device_v1, support: 0.6 KERN: tried best module: drivers/disk/scsi/scsi_cd/device_v1: No error KERN: free drivers/disk/scsi/scsi_dsk/device_v1 KERN: tried best module: busses/ide/generic_ide_pci/device_v1: No error KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: foundKERN: isa!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/ide_isa/device_v1 to list KERN: has connection? yes KERN: module: busses/ide/ide_isa/device_v1, support: 0.6 KERN: ISA-IDE: can't acquire resources 0x1f0 and 0x3f6 KERN: ISA-IDE: can't acquire resources 0x170 and 0x376 KERN: tried best module: busses/ide/ide_isa/device_v1: No error KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/ide_isa/device_v1 to list KERN: has connection? yes KERN: module: busses/ide/ide_isa/device_v1, support: 0.6 KERN: ISA-IDE: can't acquire resources 0x1f0 and 0x3f6 KERN: ISA-IDE: can't acquire resources 0x170 and 0x376 KERN: tried best module: busses/ide/ide_isa/device_v1: No error KERN: KDiskDeviceManager::_Scan(/dev/disk/ata) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/raw) KERN: found device: /dev/disk/ata/0/master/raw KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master/raw) KERN: found device: /dev/disk/atapi/1/master/raw KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/raw) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 1 KERN: intel: pm_std_ops(0x1) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 0: 0, 10056130560, 512) KERN: Partition::SetTo(): active: 80 KERN: Partition::SetTo(): active: 0 KERN: Last message repeated 9 times. KERN: returned: 810/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: trying: file_systems/bfs/v1 KERN: returned: -2147483648/1000 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: partitioning_systems/intel/map/v1 KERN: intel: pm_scan_partition(0, 0: 0, 10056130560, 512) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/0) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 32256, 98671104, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 2: 32256, 98671104, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 2 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 1 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 98703360, 254983680, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 3: 98703360, 254983680, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 2 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 353687040, 9697605120, 512) KERN: returned: 949/1000 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 4: 353687040, 9697605120, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: trying: file_systems/bfs/v1 KERN: returned: -2147483648/1000 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: partitioning_systems/intel/extended/v1 KERN: intel: ep_scan_partition(0, 353687040, 9697605120, 512) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_0) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 353719296, 2697859584, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 5: 353719296, 2697859584, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: KERN: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 4 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 3 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 3051611136, 1003451904, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 6: 3051611136, 1003451904, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 4 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 5 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 4 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_2) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 4055095296, 3002194944, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 7: 4055095296, 3002194944, 512) KERN: Partition::SetTo(): active: 58 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: 66 KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 6f KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 5 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 6 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 5 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_3) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 7057322496, 2993969664, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 8: 7057322496, 2993969664, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 6 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 7 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 6 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 1 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 1 KERN: device 0: /dev/disk/ata/0/master/raw KERN: media status: No error KERN: device flags: 2 KERN: offset: 0 KERN: size: 10056130560 (9590.273 MB) KERN: content size: 10056130560 KERN: block size: 512 KERN: child count: 3 KERN: index: -1 KERN: status: 0 KERN: flags: 5 KERN: volume: -1 KERN: disk system: partitioning_systems/intel/map/v1 KERN: name: KERN: content name: KERN: type: KERN: content type: Intel Partition Map KERN: params: KERN: content params: KERN: partition 2: /dev/disk/ata/0/master/0 KERN: offset: 32256 KERN: size: 98671104 (94.1 MB) KERN: content size: 98670592 KERN: block size: 1024 KERN: child count: 0 KERN: index: 0 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: -boot KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 1 KERN: content params: KERN: partition 3: /dev/disk/ata/0/master/1 KERN: offset: 98703360 KERN: size: 254983680 (243.171 MB) KERN: content size: 254983168 KERN: block size: 1024 KERN: child count: 0 KERN: index: 1 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: untitled KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 4: /dev/disk/ata/0/master/2 KERN: offset: 353687040 KERN: size: 9697605120 (9248.356 MB) KERN: content size: 9697605120 KERN: block size: 512 KERN: child count: 4 KERN: index: 2 KERN: status: 0 KERN: flags: 4 KERN: volume: -1 KERN: disk system: partitioning_systems/intel/extended/v1 KERN: name: KERN: content name: KERN: type: Intel Extended Partition KERN: content type: Intel Extended Partition KERN: params: type = 5 ; active = 0 KERN: content params: KERN: partition 5: /dev/disk/ata/0/master/2_0 KERN: offset: 353719296 KERN: size: 2697859584 (2572.879 MB) KERN: content size: 2697859072 KERN: block size: 1024 KERN: child count: 0 KERN: index: 0 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: BeOS5Max KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 6: /dev/disk/ata/0/master/2_1 KERN: offset: 3051611136 KERN: size: 1003451904 (956.966 MB) KERN: content size: 1003451392 KERN: block size: 1024 KERN: child count: 0 KERN: index: 1 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: -home KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 7: /dev/disk/ata/0/master/2_2 KERN: offset: 4055095296 KERN: size: 3002194944 (2863.116 MB) KERN: content size: 3002194944 KERN: block size: 1024 KERN: child count: 0 KERN: index: 2 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: BeOS Dano KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 8: /dev/disk/ata/0/master/2_3 KERN: offset: 7057322496 KERN: size: 2993969664 (2855.271 MB) KERN: content size: 2993969152 KERN: block size: 1024 KERN: child count: 0 KERN: index: 3 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: Haiku KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: device 1: /dev/disk/atapi/1/master/raw KERN: media status: No media present KERN: device flags: 5 KERN: bfs: mounted "Haiku" (root node at 65536, device = /dev/disk/ata/0/master/2_3) KERN: module: Search for file_cache/launch_speedup/v1 failed. KERN: partitioning system: partitioning_systems/session/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/session/v1) KERN: KDiskSystem::Load(): partitioning_systems/session/v1 -> 1 KERN: KDiskSystem::Unload(): partitioning_systems/session/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/fat/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/fat/v1) KERN: KDiskSystem::Load(): file_systems/fat/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/fat/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/iso9660/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/iso9660/v1) KERN: KDiskSystem::Load(): file_systems/iso9660/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/iso9660/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: KDiskDeviceManager::_Scan(/dev/disk) KERN: con_init: trying module console/frame_buffer/v1 KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/console KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/dprintf KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/keyboard KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/null KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/random KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/tty KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/zero KERN: KDiskDeviceManager::_Scan(/dev/disk/ata) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/1) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_1) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_2) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_3) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/raw) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master/raw) KERN: KDiskDeviceManager::_Scan(/dev/disk/scsi) KERN: loaded module /boot/beos/system/add- ons/kernel/drivers/dev/disk/scsi/scsi_cd KERN: loaded module /boot/beos/system/add- ons/kernel/drivers/dev/disk/scsi/scsi_dsk KERN: KDiskDeviceManager::_Scan(/dev/disk/usb) KERN: usb_uhci: successfully started the controller KERN: module: Search for busses/usb/ohci failed. KERN: usb_ehci: no devices found KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/disk/usb/usb_disk KERN: KDiskDeviceManager::_Scan(/dev/disk/virtual) KERN: nbd:>init_hardware() KERN: nbd:>init_driver() KERN: allocate_commpage_entry(4, 34) -> 0xffff0118 KERN: set_memory_write_back base 0 length 13ff0000 KERN: find_nearest 13ff0000 0 KERN: find_nearest 3ff0000 1 KERN: find_nearest 1ff0000 2 KERN: find_nearest ff0000 3 KERN: find_nearest 7f0000 4 KERN: find_nearest c010000 1 KERN: solutions: 0x10000000 0xfffffffffc000000 KERN: allocate MTRR slot 0, base = 0, length = 10000000, type=0x6 KERN: allocate MTRR slot 1, base = 10000000, length = 4000000, type=0x6 KERN: kernel debugger extension "debugger/hangman/v1": loaded KERN: kernel debugger extension "debugger/invalidate_on_exit/v1": loaded KERN: allocate MTRR slot 2, base = f5000000, length = 400000, type=0x1 KERN: REG: Failed to open shadow passwd DB file "/etc/shadow": No such file or directory KERN: bfs: bfs_open_dir:1461: Invalid Argument KERN: register_domain(1, internet) KERN: unregister_domain(0x90bb5800, 1, internet) KERN: register_domain(9, unix) KERN: unregister_domain(0x90bb5bc0, 9, unix) KERN: register_domain(1, internet) KERN: get_device_interface: ask "network/devices/ethernet/v1" for loop KERN: get_device_interface: ask "network/devices/loopback/v1" for loop KERN: 3com: init_hardware(0x80415958) KERN: 3com: no hardware found. KERN: etherpci: init_driver init_driver: etherpci not found KERN: ipro100: init_hardware(0x80412f04) KERN: ipro100: no hardware found. KERN: ipro1000: init_hardware(0x804317c4) KERN: ipro1000: no hardware found. KERN: marvell_yukon: init_hardware(0x80418c3c) KERN: marvell_yukon: no hardware found. KERN: nforce: init_hardware(0x80415cd8) KERN: nforce: no hardware found. KERN: rtl8139: init_hardware(0x80411ee0) KERN: rtl8139: no hardware found. KERN: syskonnect: init_hardware(0x80418258) KERN: syskonnect: no hardware found. KERN: via_rhine: init_hardware(0x80412238) KERN: via_rhine: no hardware found. KERN: intel_extreme: init_hardware() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/neomagic KERN: Radeon - init_hardware: Version: 5.1.6.0 KERN: Radeon - Radeon_CardDetect: no supported devices found KERN: savage: init_hardware - no supported devices KERN: vesa: init_hardware() KERN: vesa: init_driver() KERN: vesa: publish_devices() KERN: vesa: find_device() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/vesa KERN: allocate MTRR slot 3, base = f5000000, length = 1000000, type=0x1 KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2_hid: publish_devices KERN: ps2_hid: uninit_driver KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/ps2_hid KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/usb_hid KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/wacom KERN: emuxki: init_hardware() KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0x00000000 KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: bfs: bfs_open_dir:1461: Invalid Argument KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: cx23882: init_hardware() KERN: auich: init_hardware() KERN: auvia: init_hardware() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/audio/hmulti/emuxki KERN: firewire: fw_module_init KERN: firewire: found 0 cards KERN: firewire: fw_module_uninit KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/bus/usb_raw KERN: bfs: bfs_create_index:1941: File or Directory already exists KERN: Last message repeated 2 times. KERN: SCSI_DSK -- synchronize_cache: Last message repeated 11 times KERN: bfs: KERN: mounted "BeOS Dano" (root node at 65536, device = /dev/disk/ata/0/master/2_2) KERN: bfs: volume reports 2821259 used blocks, correct is 2821279 KERN: APM version 1.2 available, flags 3. KERN: smp_acpi_probe: entry base 0x9fc00, limit 0xa0000 KERN: smp_acpi_probe: entry base 0xf0000, limit 0x100000 KERN: smp_acpi_probe: found ACPI RSDP signature at 0x000f6d00 KERN: smp: using ACPI to detect MP configuration KERN: smp: found rsdp at 0x000f6d00 oem id: PTLTD KERN: smp: rsdp points to rsdt at 0x13ffac85 KERN: smp: searching 2 entries for APIC information KERN: smp: skipping uninteresting header 'FACP' KERN: smp: skipping uninteresting header 'BOOT' KERN: smp_mp_probe: entry base 0x9fc00, limit 0xa0000 KERN: smp_mp_probe: entry base 0xf0000, limit 0x100000 KERN: VESA version = 2.0 KERN: oem string: MagicMedia 256AV 48K KERN: EDID1: 4f KERN: EDID2: ebx 0 KERN: Welcome to the Haiku boot loader! KERN: number of drives: 1 KERN: add_partitions_for(0x00105190, mountFS = no) KERN: add_partitions_for(fd = 0, mountFS = no) KERN: 0x001052e4 Partition::Partition KERN: 0x001052e4 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(1, 1069796: 0, 10056130560, 512) KERN: Partition::SetTo(): active: 80 KERN: Partition::SetTo(): active: 0 Last message repeated 9 times KERN: priority: 810 KERN: check for partitioning_system: Intel Extended Partition KERN: check for partitioning_system: Apple Partition Map KERN: intel: pm_scan_partition(1, 1069796: 0, 10056130560, 512) KERN: 0x00105438 Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x00105438 KERN: 0x00105438 Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001054ec Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x001054ec KERN: 0x001054ec Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001055a0 Partition::Partition KERN: 0x001052e4 Partition::AddChild 0x001055a0 KERN: 0x001055a0 Partition::SetParent 0x001052e4 KERN: new child partition! KERN: 0x001052e4 Partition::Scan: *** scan child 0x00105438 (start = 32256, size = 98671104, parent = 0x001052e4)! KERN: 0x00105438 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(2, 1070136: 32256, 98671104, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: priority: 100 KERN: check for partitioning_system: Intel Extended Partition KERN: intel: ep_identify_partition(2, 32256, 98671104, 512) KERN: check for partitioning_system: Apple Partition Map KERN: 0x001052e4 Partition::Scan: *** scan child 0x001054ec (start = 98703360, size = 254983680, parent = 0x001052e4)! KERN: 0x001054ec Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: intel: pm_identify_partition(2, 1070316: 98703360, 254983680, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: priority: 100 KERN: check for partitioning_system: Intel Extended Partition KERN: intel: ep_identify_partition(2, 98703360, 254983680, 512) KERN: check for partitioning_system: Apple Partition Map KERN: 0x001052e4 Partition::Scan: *** scan child 0x001055a0 (start = 353687040, size = 9697605120, parent = 0x001052e4)! KERN: 0x001055a0 Partition::Scan() KERN: check for partitioning_system: Amiga Partition Map KERN: check for partitioning_system: EFI GUID Partition Map KERN: check for partitioning_system: Intel Partition Map KERN: priority: 949 KERN: initialize_commpage_syscall(): sysenter/sysexit supported KERN: allocate_commpage_entry(3, 5) -> 0xffff0100 KERN: allocate_commpage_entry(2, 12) -> 0xffff0108 KERN: apm_init() KERN: code32: 0xf000, 0x4108, length 0xffff KERN: code16: 0xf000, length 0xffff KERN: data: 0x40, length 0xffff KERN: heap_attach: attached to 0x90800000 - usable range 0x90803000 - 0x90a00000 KERN: ahci: ahci_get_supported_paths KERN: found root!! KERN: add module bus_managers/isa/root/device_v1 to list KERN: PCI: pci_module_init KERN: PCI: mechanism 1 controller found KERN: PCI: [dom 0, bus 0] bus 0, device 0, function 0: vendor 8086, device 7190, revision 03 KERN: PCI: class_base 06, class_function 00, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7190: 440BX/ZX/DX - 82443BX/ZX/DX Host bridge KERN: PCI: info: Bridge (Host bridge) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host f8000000, pci f8000000, size 04000000, flags 08 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AGP KERN: PCI: [dom 0, bus 0] bus 0, device 1, function 0: vendor 8086, device 7191, revision 03 KERN: PCI: class_base 06, class_function 04, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7191: 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge KERN: PCI: info: Bridge (PCI bridge, Normal decode) KERN: PCI: line_size 00, latency 40, header_type 01, BIST 00 KERN: PCI: subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: primary_bus 00, secondary_bus 01, subordinate_bus 01, secondary_latency 40 KERN: PCI: io_base_upper_16 0000, io_base f0 KERN: PCI: io_limit_upper_16 0000, io_limit 00 KERN: PCI: memory_base f420, memory_limit f470 KERN: PCI: prefetchable_memory_base_upper32 00000000, prefetchable_memory_base f500 KERN: PCI: prefetchable_memory_limit_upper32 00000000, prefetchable_memory_limit f5f0 KERN: PCI: bridge_control 8c, secondary_status a2a0 KERN: PCI: interrupt_line 00, interrupt_pin 00 KERN: PCI: ROM base host 00000000, pci 00000000, size ?? KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 1] bus 1, device 0, function 0: vendor 10c8, device 0005, revision 20 KERN: PCI: class_base 03, class_function 00, class_api 00 KERN: PCI: vendor 10c8: Neomagic Corporation KERN: PCI: device 0005: ThinkPad 570 KERN: PCI: info: Display controller (VGA compatible controller, VGA) KERN: PCI: line_size 00, latency 80, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 00dd, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant 10, max_latency ff KERN: PCI: base reg 0: host f5000000, pci f5000000, size 01000000, flags 08 KERN: PCI: base reg 1: host f4400000, pci f4400000, size 00400000, flags 00 KERN: PCI: base reg 2: host f4200000, pci f4200000, size 00100000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 0: vendor 104c, device ac1b, revision 03 KERN: PCI: class_base 06, class_function 07, class_api 00 KERN: PCI: vendor 104c: Texas Instruments KERN: PCI: device ac1b: PCI1450 KERN: PCI: info: Bridge (CardBus bridge) KERN: PCI: line_size 08, latency 40, header_type 82, BIST 00 KERN: PCI: subsystem_id 0130, subsystem_vendor_id 1014 KERN: PCI: primary_bus 00, secondary_bus 07, subordinate_bus 08, secondary_latency b0 KERN: PCI: bridge_controKERN: l c0, secondary_status 0200 KERN: PCI: memory_base_upper32 00000000, memory_base 00000000 KERN: PCI: memory_limit_upper32 00000000, memory_limit 00000000 KERN: PCI: io_base_upper32 00000000, io_base 00000000 KERN: PCI: io_limit_upper32 00000000, io_limit 00000000 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 1: vendor 104c, device ac1b, revision 03 KERN: PCI: class_base 06, class_function 07, class_api 00 KERN: PCI: vendor 104c: Texas Instruments KERN: PCI: device ac1b: PCI1450 KERN: PCI: info: Bridge (CardBus bridge) KERN: PCI: line_size 08, latency 40, header_type 82, BIST 00 KERN: PCI: subsystem_id 0130, subsystem_vendor_id 1014 KERN: PCI: primary_bus 00, secondary_bus 09, subordinate_bus 0a, secondary_latency b0 KERN: PCI: bridge_control c0, secondary_status 0200 KERN: PCI: memory_base_upper32 00000000, memory_base 00000000 KERN: PCI: memory_limit_upper32 00000000, memory_limit 00000000 KERN: PCI: io_base_upper32 00000000, io_base 00000000 KERN: PCI: io_limit_upper32 00000000, io_limit 00000000 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 5, function 0: vendor 1013, device 6003, revision 01 KERN: PCI: class_base 04, class_function 01, class_api 00 KERN: PCI: vendor 1013: Cirrus Logic KERN: PCI: device 6003: CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] KERN: PCI: info: Multimedia controller (Multimedia audio controller) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0132, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant 04, max_latency 18 KERN: PCI: base reg 0: host f4100000, pci f4100000, size 00001000, flags 00 KERN: PCI: base reg 1: host f4000000, pci f4000000, size 00100000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 0: vendor 8086, device 7110, revision 02 KERN: PCI: class_base 06, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7110: 82371AB/EB/MB PIIX4 ISA KERN: PCI: info: Bridge KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 1: vendor 8086, device 7111, revision 01 KERN: PCI: class_base 01, class_function 01, class_api 80 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7111: 82371AB/EB/MB PIIX4 IDE KERN: PCI: info: Mass storage controller (IDE interface) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00001800, pci 00001800, size 00000010, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 2: vendor 8086, device 7112, revision 01 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7112: 82371AB/EB/MB PIIX4 USB KERN: PCI: info: Serial bus controller (USB Controller, UHCI) KERN: PCI: line_size 00, latency 40, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 0b, interrupt_pin 04, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00001820, pci 00001820, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 6, function 3: vendor 8086, device 7113, revision 02 KERN: PCI: class_base 06, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 7113: 82371AB/EB/MB PIIX4 ACPI KERN: PCI: info: Bridge KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 0000, subsystem_vendor_id 0000 KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: PCI: [dom 0, bus 0] bus 0, device 7, function 0: vendor 11c1, device 0448, revision 01 KERN: PCI: class_base 07, class_function 80, class_api 00 KERN: PCI: vendor 11c1: Agere Systems KERN: PCI: device 0448: Lucent Win Modem KERN: PCI: info: Communication controller KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000040, subsystem_id 0131, subsystem_vendor_id 1014 KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant fc, max_latency 0e KERN: PCI: base reg 0: host f4101000, pci f4101000, size 00000100, flags 00 KERN: PCI: base reg 1: host 00001810, pci 00001810, size 00000010, flags 09 KERN: PCI: base reg 2: host 00002000, pci 00002000, size 00000100, flags 01 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM KERN: found root!! KERN: add module bus_managers/pci/root/device_v1 to list KERN: has connection? no KERN: module: bus_managers/isa/root/device_v1, support: 1 KERN: module: bus_managers/pci/root/device_v1, support: 1 KERN: register rest: bus_managers/isa/root/device_v1 KERN: free bus_managers/isa/root/device_v1 KERN: register rest: bus_managers/pci/root/device_v1 KERN: free bus_managers/pci/root/device_v1 KERN: get_boot_partitions(): boot volume message: KERN: field: "booted from image", type: BOOL (0x424f4f4c): KERN: [ 0] false KERN: field: "partition offset", type: LLNG (0x4c4c4e47): KERN: [ 0] 7057322496 (0x1a4a63200) KERN: field: "boot method", type: LONG (0x4c4f4e47): KERN: [ 0] 0 (0x0) KERN: field: "boot drive number", type: LLNG (0x4c4c4e47): KERN: [ 0] 128 (0x80) KERN: field: "disk identifier", type: RAWT (0x52415754): KERN: [ 0] data: "0x805e89bc", 80 bytes KERN: get_boot_partitions(): boot method type: 0 KERN: partitioning system: partitioning_systems/intel/extended/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/intel/extended/v1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KKERN: DiskDeviceManager::_AddDiskSystem() done: No error KERN: partitioning system: partitioning_systems/intel/map/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/intel/map/v1) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 1 KERN: intel: pm_std_ops(0x1) KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 0 KERN: intel: pm_std_ops(0x2) KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/bfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/bfs/v1) KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/devfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/devfs/v1) KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/rootfs/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/rootfs/v1) KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: number of disk systems: 5 KERN: KDiskDeviceManager::_Scan(/dev/disk) KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0.3 KERN: PCI-IDE: Controller in legacy mode: cmd 0x1f0, ctrl 0x3f6, irq 14 KERN: PCI-IDE: init channel... KERN: PCI-IDE: bus 0, device 6, function 1: vendor 8086, device 7111 KERN: PCI-IDE: channel index 0 KERN: PCI-IDE: bus master base 0x1800 KERN: PCI-IDE: init channel done KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 0 KERN: IDE: create_device: bus 0x90ad2100, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0400 KERN: IDE: scan_device_int: device 0x90ad0400, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 1 KERN: IDE: create_device: bus 0x90ad2100, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 0 KERN: IDE: destroy_device: device 0x90ad0400 KERN: IDE: cleanup_device_links: device 0x90ad0400 KERN: IDE: create_device: bus 0x90ad2100, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0400 KERN: IDE: scan_device_int: device 0x90ad0400, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2100, device-number 1 KERN: IDE: create_device: bus 0x90ad2100, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2100, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_dsk/device_v1 to list KERN: ahci: ahci_get_supported_paths KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_cd/device_v1 to list KERN: has connection? yes KERN: module: drivers/disk/scsi/scsi_dsk/device_v1, support: 0.6 KERN: module: drivers/disk/scsi/scsi_cd/device_v1, support: 0 KERN: tried best module: drivers/disk/scsi/scsi_dsk/device_v1: No error KERN: free drivers/disk/scsi/scsi_cd/device_v1 KERN: PCI-IDE: Controller in legacy mode: cmd 0x170, ctrl 0x376, irq 15 KERN: PCI-IDE: init channel... KERN: PCI-IDE: bus 0, device 6, function 1: vendor 8086, device 7111 KERN: PCI-IDE: channel index 1 KERN: PCI-IDE: bus master base 0x1808 KERN: PCI-IDE: init channel done KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 0 KERN: IDE: create_device: bus 0x90ad2300, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: error bit set - no device or wrong type (status: 0x51) KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 1 KERN: IDE: create_device: bus 0x90ad2300, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0c00 KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: no fast response to inquiry KERN: IDE: scan_device_int: status 0x01 KERN: IDE: scan_device_int: bKERN: usy bit not set after 100ms - probably noone there KERN: IDE: scan_device_int: aborting because busy bit not set KERN: IDE: destroy_device: device 0x90ad0c00 KERN: IDE: cleanup_device_links: device 0x90ad0c00 KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 0 KERN: IDE: destroy_device: device 0x90ad0800 KERN: IDE: cleanup_device_links: device 0x90ad0800 KERN: IDE: create_device: bus 0x90ad2300, device-number 0 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0800 KERN: IDE: scan_device_int: device 0x90ad0800, atapi 0 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: error bit set - no device or wrong type (status: 0x51) KERN: IDE: scan_device_int: device 0x90ad0800, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: got a fast response KERN: IDE: scan_device_int: device found KERN: IDE: scan_device_worker: bus 0x90ad2300, device-number 1 KERN: IDE: create_device: bus 0x90ad2300, device-number 1 KERN: IDE: setup_device_links: bus 0x90ad2300, device 0x90ad0c00 KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 0 KERN: IDE: scan_device_int: send_command failed KERN: IDE: scan_device_int: device 0x90ad0c00, atapi 1 KERN: IDE: scan_device_int: waiting 100ms... KERN: IDE: scan_device_int: no fast response to inquiry KERN: IDE: scan_device_int: status 0x01 KERN: IDE: scan_device_int: busy bit not set after 100ms - probably noone there KERN: IDE: scan_device_int: aborting because busy bit not set KERN: IDE: destroy_device: device 0x90ad0c00 KERN: IDE: cleanup_device_links: device 0x90ad0c00 KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_dsk/device_v1 to list KERN: ahci: ahci_get_supported_paths KERN: found scsi!! KERN: add module drivers/disk/scsi/scsi_cd/device_v1 to list KERN: has connection? yes KERN: module: drivers/disk/scsi/scsi_dsk/device_v1, support: 0 KERN: module: drivers/disk/scsi/scsi_cd/device_v1, support: 0.6 KERN: tried best module: drivers/disk/scsi/scsi_cd/device_v1: No error KERN: free drivers/disk/scsi/scsi_dsk/device_v1 KERN: tried best module: busses/ide/generic_ide_pci/device_v1: No error KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/scsi/ahci/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/legacy_sata/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/sata!! KERN: add module busses/ide/silicon_image_3112/device_v1 to list KERN: found pci!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/generic_ide_pci/device_v1 to list KERN: has connection? yes KERN: ahci: ahci_supports_device KERN: module: busses/scsi/ahci/device_v1, support: 0 KERN: module: busses/ide/legacy_sata/device_v1, support: 0 KERN: module: busses/ide/silicon_image_3112/device_v1, support: 0 KERN: module: busses/ide/generic_ide_pci/device_v1, support: 0 KERN: free busses/scsi/ahci/device_v1 KERN: free busses/ide/legacy_sata/device_v1 KERN: free busses/ide/silicon_image_3112/device_v1 KERN: free busses/ide/generic_ide_pci/device_v1 KERN: ahci: ahci_get_supported_paths KERN: foundKERN: isa!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/ide_isa/device_v1 to list KERN: has connection? yes KERN: module: busses/ide/ide_isa/device_v1, support: 0.6 KERN: ISA-IDE: can't acquire resources 0x1f0 and 0x3f6 KERN: ISA-IDE: can't acquire resources 0x170 and 0x376 KERN: tried best module: busses/ide/ide_isa/device_v1: No error KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: found drivers/dev/disk/ide!! KERN: add module busses/ide/ide_isa/device_v1 to list KERN: has connection? yes KERN: module: busses/ide/ide_isa/device_v1, support: 0.6 KERN: ISA-IDE: can't acquire resources 0x1f0 and 0x3f6 KERN: ISA-IDE: can't acquire resources 0x170 and 0x376 KERN: tried best module: busses/ide/ide_isa/device_v1: No error KERN: KDiskDeviceManager::_Scan(/dev/disk/ata) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/raw) KERN: found device: /dev/disk/ata/0/master/raw KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master) KERN: ahci: ahci_get_supported_paths KERN: found isa!! KERN: has connection? yes KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master/raw) KERN: found device: /dev/disk/atapi/1/master/raw KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/raw) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 1 KERN: intel: pm_std_ops(0x1) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 0: 0, 10056130560, 512) KERN: Partition::SetTo(): active: 80 KERN: Partition::SetTo(): active: 0 KERN: Last message repeated 9 times. KERN: returned: 810/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: trying: file_systems/bfs/v1 KERN: returned: -2147483648/1000 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: partitioning_systems/intel/map/v1 KERN: intel: pm_scan_partition(0, 0: 0, 10056130560, 512) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/0) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 32256, 98671104, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 2: 32256, 98671104, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 1 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 2 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 1 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 98703360, 254983680, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 0 KERN: intel: ep_std_ops(0x2) KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 3: 98703360, 254983680, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 2 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 1 KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 353687040, 9697605120, 512) KERN: returned: 949/1000 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 4: 353687040, 9697605120, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: trying: file_systems/bfs/v1 KERN: returned: -2147483648/1000 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: partitioning_systems/intel/extended/v1 KERN: intel: ep_scan_partition(0, 353687040, 9697605120, 512) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_0) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 353719296, 2697859584, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 5: 353719296, 2697859584, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 3 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: KERN: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 4 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 3 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_1) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 3051611136, 1003451904, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 6: 3051611136, 1003451904, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 4 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 5 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 4 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_2) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 4055095296, 3002194944, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 7: 4055095296, 3002194944, 512) KERN: Partition::SetTo(): active: 58 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: 66 KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 6f KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 5 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 6 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 5 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/ata/0/master/2_3) KERN: KDiskSystem::Load(): partitioning_systems/intel/extended/v1 -> 3 KERN: trying: partitioning_systems/intel/extended/v1 KERN: intel: ep_identify_partition(0, 7057322496, 2993969664, 512) KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 2 KERN: KDiskSystem::Load(): partitioning_systems/intel/map/v1 -> 3 KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(0, 8: 7057322496, 2993969664, 512) KERN: Partition::SetTo(): active: c3 KERN: intel: _ParsePrimary(): partition 0: bad location, ignoring KERN: Partition::SetTo(): active: ad KERN: intel: _ParsePrimary(): partition 1: bad location, ignoring KERN: Partition::SetTo(): active: 69 KERN: intel: _ParsePrimary(): partition 2: bad location, ignoring KERN: Partition::SetTo(): active: 79 KERN: intel: _ParsePrimary(): partition 3: bad location, ignoring KERN: returned: 100/1000 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 6 KERN: trying: file_systems/bfs/v1 KERN: returned: 800/1000 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 2 KERN: KDiskSystem::Load(): file_systems/devfs/v1 -> 1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/devfs/v1 -> 0 KERN: KDiskSystem::Load(): file_systems/rootfs/v1 -> 1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1000/1000 KERN: KDiskSystem::Unload(): file_systems/rootfs/v1 -> 0 KERN: scanning with: file_systems/bfs/v1 KERN: KDiskSystem::Load(): file_systems/bfs/v1 -> 7 KERN: KDiskSystem::Unload(): file_systems/bfs/v1 -> 6 KERN: KDiskSystem::Unload(): partitioning_systems/intel/extended/v1 -> 1 KERN: KDiskSystem::Unload(): partitioning_systems/intel/map/v1 -> 1 KERN: device 0: /dev/disk/ata/0/master/raw KERN: media status: No error KERN: device flags: 2 KERN: offset: 0 KERN: size: 10056130560 (9590.273 MB) KERN: content size: 10056130560 KERN: block size: 512 KERN: child count: 3 KERN: index: -1 KERN: status: 0 KERN: flags: 5 KERN: volume: -1 KERN: disk system: partitioning_systems/intel/map/v1 KERN: name: KERN: content name: KERN: type: KERN: content type: Intel Partition Map KERN: params: KERN: content params: KERN: partition 2: /dev/disk/ata/0/master/0 KERN: offset: 32256 KERN: size: 98671104 (94.1 MB) KERN: content size: 98670592 KERN: block size: 1024 KERN: child count: 0 KERN: index: 0 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: -boot KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 1 KERN: content params: KERN: partition 3: /dev/disk/ata/0/master/1 KERN: offset: 98703360 KERN: size: 254983680 (243.171 MB) KERN: content size: 254983168 KERN: block size: 1024 KERN: child count: 0 KERN: index: 1 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: untitled KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 4: /dev/disk/ata/0/master/2 KERN: offset: 353687040 KERN: size: 9697605120 (9248.356 MB) KERN: content size: 9697605120 KERN: block size: 512 KERN: child count: 4 KERN: index: 2 KERN: status: 0 KERN: flags: 4 KERN: volume: -1 KERN: disk system: partitioning_systems/intel/extended/v1 KERN: name: KERN: content name: KERN: type: Intel Extended Partition KERN: content type: Intel Extended Partition KERN: params: type = 5 ; active = 0 KERN: content params: KERN: partition 5: /dev/disk/ata/0/master/2_0 KERN: offset: 353719296 KERN: size: 2697859584 (2572.879 MB) KERN: content size: 2697859072 KERN: block size: 1024 KERN: child count: 0 KERN: index: 0 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: BeOS5Max KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 6: /dev/disk/ata/0/master/2_1 KERN: offset: 3051611136 KERN: size: 1003451904 (956.966 MB) KERN: content size: 1003451392 KERN: block size: 1024 KERN: child count: 0 KERN: index: 1 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: -home KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 7: /dev/disk/ata/0/master/2_2 KERN: offset: 4055095296 KERN: size: 3002194944 (2863.116 MB) KERN: content size: 3002194944 KERN: block size: 1024 KERN: child count: 0 KERN: index: 2 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: BeOS Dano KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: partition 8: /dev/disk/ata/0/master/2_3 KERN: offset: 7057322496 KERN: size: 2993969664 (2855.271 MB) KERN: content size: 2993969152 KERN: block size: 1024 KERN: child count: 0 KERN: index: 3 KERN: status: 0 KERN: flags: 2 KERN: volume: -1 KERN: disk system: file_systems/bfs/v1 KERN: name: KERN: content name: Haiku KERN: type: BFS Filesystem KERN: content type: Be File System KERN: params: type = 235 ; active = 0 KERN: content params: KERN: device 1: /dev/disk/atapi/1/master/raw KERN: media status: No media present KERN: device flags: 5 KERN: bfs: mounted "Haiku" (root node at 65536, device = /dev/disk/ata/0/master/2_3) KERN: module: Search for file_cache/launch_speedup/v1 failed. KERN: partitioning system: partitioning_systems/session/v1 KERN: KDiskDeviceManager::_AddDiskSystem(partitioning_systems/session/v1) KERN: KDiskSystem::Load(): partitioning_systems/session/v1 -> 1 KERN: KDiskSystem::Unload(): partitioning_systems/session/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/fat/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/fat/v1) KERN: KDiskSystem::Load(): file_systems/fat/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/fat/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: file system: file_systems/iso9660/v1 KERN: KDiskDeviceManager::_AddDiskSystem(file_systems/iso9660/v1) KERN: KDiskSystem::Load(): file_systems/iso9660/v1 -> 1 KERN: KDiskSystem::Unload(): file_systems/iso9660/v1 -> 0 KERN: KDiskDeviceManager::_AddDiskSystem() done: No error KERN: KDiskDeviceManager::_Scan(/dev/disk) KERN: con_init: trying module console/frame_buffer/v1 KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/console KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/dprintf KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/keyboard KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/null KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/random KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/tty KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/zero KERN: KDiskDeviceManager::_Scan(/dev/disk/ata) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/1) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_0) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_1) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_2) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/2_3) KERN: KDiskDeviceManager::_Scan(/dev/disk/ata/0/master/raw) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master) KERN: KDiskDeviceManager::_Scan(/dev/disk/atapi/1/master/raw) KERN: KDiskDeviceManager::_Scan(/dev/disk/scsi) KERN: loaded module /boot/beos/system/add- ons/kernel/drivers/dev/disk/scsi/scsi_cd KERN: loaded module /boot/beos/system/add- ons/kernel/drivers/dev/disk/scsi/scsi_dsk KERN: KDiskDeviceManager::_Scan(/dev/disk/usb) KERN: usb_uhci: successfully started the controller KERN: module: Search for busses/usb/ohci failed. KERN: usb_ehci: no devices found KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/disk/usb/usb_disk KERN: KDiskDeviceManager::_Scan(/dev/disk/virtual) KERN: nbd:>init_hardware() KERN: nbd:>init_driver() KERN: allocate_commpage_entry(4, 34) -> 0xffff0118 KERN: set_memory_write_back base 0 length 13ff0000 KERN: find_nearest 13ff0000 0 KERN: find_nearest 3ff0000 1 KERN: find_nearest 1ff0000 2 KERN: find_nearest ff0000 3 KERN: find_nearest 7f0000 4 KERN: find_nearest c010000 1 KERN: solutions: 0x10000000 0xfffffffffc000000 KERN: allocate MTRR slot 0, base = 0, length = 10000000, type=0x6 KERN: allocate MTRR slot 1, base = 10000000, length = 4000000, type=0x6 KERN: kernel debugger extension "debugger/hangman/v1": loaded KERN: kernel debugger extension "debugger/invalidate_on_exit/v1": loaded KERN: allocate MTRR slot 2, base = f5000000, length = 400000, type=0x1 KERN: REG: Failed to open shadow passwd DB file "/etc/shadow": No such file or directory KERN: bfs: bfs_open_dir:1461: Invalid Argument KERN: register_domain(1, internet) KERN: unregister_domain(0x90bb66c0, 1, internet) KERN: register_domain(9, unix) KERN: unregister_domain(0x90bb6a80, 9, unix) KERN: register_domain(1, internet) KERN: get_device_interface: ask "network/devices/ethernet/v1" for loop KERN: get_device_interface: ask "network/devices/loopback/v1" for loop KERN: 3com: init_hardware(0x80415958) KERN: 3com: no hardware found. KERN: etherpci: init_driver init_driver: etherpci not found KERN: ipro100: init_hardware(0x80412f04) KERN: ipro100: no hardware found. KERN: ipro1000: init_hardware(0x804317c4) KERN: ipro1000: no hardware found. KERN: marvell_yukon: init_hardware(0x80418c3c) KERN: marvell_yukon: no hardware found. KERN: nforce: init_hardware(0x80415cd8) KERN: nforce: no hardware found. KERN: rtl8139: init_hardware(0x80411ee0) KERN: rtl8139: no hardware found. KERN: syskonnect: init_hardware(0x80418258) KERN: syskonnect: no hardware found. KERN: via_rhine: init_hardware(0x80412238) KERN: via_rhine: no hardware found. KERN: intel_extreme: init_hardware() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/neomagic KERN: Radeon - init_hardware: Version: 5.1.6.0 KERN: Radeon - Radeon_CardDetect: no supported devices found KERN: savage: init_hardware - no supported devices KERN: vesa: init_hardware() KERN: vesa: init_driver() KERN: vesa: publish_devices() KERN: vesa: find_device() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/graphics/vesa KERN: allocate MTRR slot 3, base = f5000000, length = 1000000, type=0x1 KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2_hid: publish_devices KERN: ps2_hid: uninit_driver KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/ps2_hid KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/usb_hid KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/input/wacom KERN: emuxki: init_hardware() KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0x00000000 KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: bfs: bfs_open_dir:1461: Invalid Argument KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: cx23882: init_hardware() KERN: auich: init_hardware() KERN: auvia: init_hardware() KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/audio/hmulti/emuxki KERN: bfs: bfs_create_index:1941: File or Directory already exists KERN: firewire: fw_module_init KERN: firewire: found 0 cards KERN: firewire: fw_module_uninit KERN: loaded driver /boot/beos/system/add- ons/kernel/drivers/dev/bus/usb_raw KERN: bfs: bfs_create_index:1941: File or Directory already exists Last message repeated 1 time KERN: SCSI_DSK -- synchronize_cache: -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 23:31:19 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 21:31:19 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.595defa07508c0a284a7cc19ccce2b2c@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): Oops you asked for an attachment...see syslog.txt -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 23:34:12 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 21:34:12 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.769771de43c790d22a59bf97043cd695@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by scottmc): Note that mine wasn't from a fresh install. I can get one from a fresh install but that won't happen today. Note that in DOS it's only using the middle 2/3's of the screen, so the weird video on this thing isn't just in BeOS/Haiku. A listdev output can be gotten by typing listdev > filename.txt in terminal. I attached one from the 570E to #1169. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 1 23:54:13 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 21:54:13 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.ecf0aaed9e9829b078f7ab97fa82c937@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): Wait, mine isn't from a very first boot of a fresh install either...will post that within 30 minutes from now :D -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 00:09:18 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 01 May 2008 22:09:18 -0000 Subject: [Haiku-bugs] [Haiku] #2188: Screen prefs. window shows wrong options In-Reply-To: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> References: <044.8c380161423acf8529c4ddebac9ba8be@haiku-os.org> Message-ID: <053.b35f27da1759b46c31aeb1c7c2b69e59@haiku-os.org> #2188: Screen prefs. window shows wrong options ----------------------------------------+----------------------------------- Reporter: meanwhile | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/NeoMagic | Version: R1 development Resolution: | Platform: All ----------------------------------------+----------------------------------- Comment (by meanwhile): Guaranteed fresh...only a few minutes old and coming from the very first boot of a brand new install, here's freshsyslog.txt !! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 03:24:15 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 01:24:15 -0000 Subject: [Haiku-bugs] [Haiku] #2005: SB600 on HP6715b laptop finds no bootable devices. In-Reply-To: <039.78854b8e207617752d27e2f867835753@haiku-os.org> References: <039.78854b8e207617752d27e2f867835753@haiku-os.org> Message-ID: <048.1d178324dd6feeae661267921fadbc38@haiku-os.org> #2005: SB600 on HP6715b laptop finds no bootable devices. ---------------------------+------------------------------------------------ Reporter: euan | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by euan): I found what the issue is from a post over at openbsd. My laptop has overlapping memory regions: SB600 AHCI Bar[5] @ D0609000-D0609100 (size 100h) SB600 Audio Bar[0] @ D0608000-D060C000 (size 4000h) I confirmed this is the issue by adding a function in pci_fixup.c currently it just disables the audio device, and sets the bar to 0. I plan to change this to search for these two devices, check that the addresses match, and if they do (make the assumption that this pc is a an HP6715b) and move one of the BARs to an unallocated region. I implemented a version using GetNthPciInfo() but it doesn't seem to work at all. Perhaps this api isn't quite ready yet at this stage in boot. so i'll try again tomorrow using some static variables in pci_fixup. slightly more hackish but should do the trick. http://lists.freebsd.org/pipermail/freebsd- hardware/2007-December/004812.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 16:40:16 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 14:40:16 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.395c6a15eff94b20c61940b206d933d4@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): I added kernel tracing to AHCI port and it seems your intuition was partially right. it is not a invalid address (like 0xdeadbeef) that seems to be causing this error but any address above the 2048 Mb mark will do that. For instance, tracing showed that this error occured when the following entry was added to the prd table: address: 0x80006000 size: 2048 In other words, any idea about why AHCI would fail if accessing addresses above 0x80000000? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 16:48:24 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 14:48:24 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.665f86c78301ac780f15df5289427d78@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): Just as a side note, it is now clear why I only recently started getting this error. I used to have only 2 Gb of memory on my machine so AHCI could never access any address above this. Now I have 4 Gb as mentioned above. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 17:06:03 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 15:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.085b3648fcdaf098a66efeefb08e3334@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): Can you please attach a syslog with the PCI data dump? Perhaps the ahci device is sitting behind a misconfigured PCI-PCI bridge and receives a PCI master abort. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 17:24:12 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 15:24:12 -0000 Subject: [Haiku-bugs] [Haiku] #2014: Add 7zip In-Reply-To: <042.e8b8afcdf06cbee864587dc6a74ae461@haiku-os.org> References: <042.e8b8afcdf06cbee864587dc6a74ae461@haiku-os.org> Message-ID: <051.62662d1e92f2e552bd5e8b211421b92a@haiku-os.org> #2014: Add 7zip --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by scottmc): 7za fails when run on vmware in dual CPU mode. The 7zip maintainer is going to look into it when he has time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 17:38:24 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 15:38:24 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.d087baba13a0270a4e371f942032dd3f@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by anevilyak): * cc: anevilyak (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 18:43:14 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 16:43:14 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.c910dd68289debfc86555380f504afa2@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): Attached the syslog output from my machine. Let me know if you need anything else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 18:58:28 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 16:58:28 -0000 Subject: [Haiku-bugs] [Haiku] #2192: Installer "Onto" button clips badly Message-ID: <042.ab16775ef698cf59977bd77b2f62f0cd@haiku-os.org> #2192: Installer "Onto" button clips badly -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- When selecting an onto volume with text that won't fit into the button it should clip the text and clip of the button before the frame of the dialog box. Perhaps a similar fix like the one used to fix the file copy name text clipping issue. It's only off by a few pixels now, so not a big issue, but still one that should be cleaned up. Attached is a composted screenshot showing the long volume name list which is fine and then the clipped button, and also the file copy box that is fixed using... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 19:43:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 17:43:23 -0000 Subject: [Haiku-bugs] [Haiku] #2193: Gzip needs 1.2.4b patch applied Message-ID: <042.a109a20fe19d60af2bab2ede47b1bcfd@haiku-os.org> #2193: Gzip needs 1.2.4b patch applied ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Platform: All | ---------------------------------------------+------------------------------ From http://www.gzip.org/ Important security patch gzip 1.2.4 may crash when an input file name is too long (over 1020 characters). The buffer overflow may be exploited if gzip is run by a server such as an ftp server. Some ftp servers allow compression and decompression on the fly and are thus vulnerable. See technical details here. This patch to gzip 1.2.4 fixes the problem. The beta version 1.3.3 already includes a sufficient patch; use this version if you have to handle files larger than 2 GB. A new official version of gzip will be released soon. note that the last update to that page was July 27th, 2003, so probably not going to see a released 1.3.3 soon. I suggest we patch to 1.2.4b, here's the url to the patch file: http://www.gzip.org/gzip-1.2.4b.patch -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 20:08:57 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 18:08:57 -0000 Subject: [Haiku-bugs] [Haiku] #2194: KDL while using WGET with rt18139 Message-ID: <042.c5ca4744261df836361890420bc438c7@haiku-os.org> #2194: KDL while using WGET with rt18139 --------------------------------+------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: All | --------------------------------+------------------------------------------- typing by hand so only putting in the first part here. If you need more let me know. PANIC: vm_page fault: unhandle page fault in kernel space at 0x4f951caf, ip 0x80098c98 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> sc stack trace for thread 64 "/dev/net/rtl18139/0 reader" kernel stack: 0x8052c000 to 0x80530000 frame caller :function + offset 8052fa20 (+ 52) 8008b63f :invoke_debugger_command + 0x00cf 8052fa54 (+ 64) 8008c3e8 :_ParseCommand__16ExpressionParserRi + 0x01f9 To reproduce, boot a fresh dev image of r25283 on real hardware with a Realtek RTL-8139/8139C/8139C+ network controller. Attempt to use WGET to grab a file, KDL unsues about 70% of the way through. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 20:45:26 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 18:45:26 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.6935c2fdb3f119d704be5d02fdf2cc0e@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by axeld): How does it look now, after r25294? At least the OpenSSH forwarding test now works here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 21:35:45 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 19:35:45 -0000 Subject: [Haiku-bugs] [Haiku] #2195: [Pe] puts libnetwork into R5 compatibility mode Message-ID: <043.bf5976a17f3244e1eb894afd6af53e86@haiku-os.org> #2195: [Pe] puts libnetwork into R5 compatibility mode --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Currently, the {{{Pe}}} Optional Package on Pe startup leads to the debug message {{{ libnetwork.so running in R5 compatibility mode. }}} It should be recompiled/updated to avoid this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 22:03:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 20:03:50 -0000 Subject: [Haiku-bugs] [Haiku] #2196: testgl fails Message-ID: <042.11118a6d0c0b8ec1681ba5ba415ca14b@haiku-os.org> #2196: testgl fails -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- Everything for the SDL library appears to build correctly, but three of the tests fail, testgamma, testdyngl, and testgl. Attached is a screencap of the testgl debug dump. It looks like mesa got linked in, so I'm puzzled why it's failing the test. Perhaps it requires hardwareGL? Maybe someone can make heads or tails of the screencap and recommend further debugging tests? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 22:10:35 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 20:10:35 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.0f076ef1e3326ac25553f6085e2b52a9@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by andreasf): At r25294 in {{{peek_close}}}: {{{ kdebug> sc 51767 stack trace for thread 51767 "socket" kernel stack: 0x95449000 to 0x9544d000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 9544cbf4 (+ 32) 8002f112 :context_switch__FP6threadT0 + 0x0026 9544cc14 (+ 64) 8002f39c :scheduler_reschedule + 0x0268 9544cc54 (+ 32) 8003c48c :thread_block_with_timeout_locked + 0x00d0 9544cc74 (+ 80) 800306a0 :switch_sem_etc + 0x0384 9544ccc4 (+ 64) 800302ee :acquire_sem_etc + 0x0026 9544cd04 (+ 64) 802f7392 :Wait__8WaitListRQ28BPrivatet10AutoLocker2Z5mutexZQ28BPrivate12MutexLockingx + 0x006a 9544cd44 (+ 48) 802f8e2a :_WaitForEstablished__11TCPEndpointRQ28BPrivatet10AutoLocker2Z5mutexZQ28BPrivate12Mutexe 9544cd74 (+ 96) 802f7a35 :Connect__11TCPEndpointPC8sockaddr + 0x0071 9544cdd4 (+ 48) 802f697b :tcp_connect__FP12net_protocolPC8sockaddr + 0x0023 9544ce04 (+ 48) 802d7d41 :socket_connect__FP10net_socketPC8sockaddrUi + 0x0055 9544ce34 (+ 48) 802ddc0e :stack_interface_connect__FP10net_socketPC8sockaddrUi + 0x002e 9544ce64 (+ 48) 8004b3d5 :common_connect__FiPC8sockaddrUib + 0x0049 9544ce94 (+ 176) 8004c7c8 :_user_connect + 0x0080 9544cf44 (+ 100) 8009b682 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x9544cfa8 (end = 0x9544d000) eax 0x82 ebx 0x3c89f8 ecx 0x5 edx 0x1800fbe0 esi 0x7ffe6e30 edi 0x20 ebp 0x7ffe6dfc esp 0x9544cfdc eip 0xffff0102 eflags 0x200217 vector: 0x63, error code: 0x0 9544cfa8 (+ 0) ffff0102 7ffe6dfc (+ 112) 00218582 :ne_addr_destroy + 0x00c6 (nearest) 7ffe6e6c (+ 64) 0021864f :ne_sock_connect + 0x0073 7ffe6eac (+ 48) 00202712 :_term_after + 0x0122 (nearest) 7ffe6edc (+ 48) 00202840 :_term_after + 0x0250 (nearest) 7ffe6f0c (+ 48) 00203014 :_term_after + 0x0a24 (nearest) 7ffe6f3c (+ 64) 00204fac :main + 0x03c8 7ffe6f7c (+ 48) 0020250f :_start + 0x005b 7ffe6fac (+ 48) 0010078e 1044226:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 1044225:socket_main_stack at 0x7efe7000 + 0xffffec }}} Then after {{{continue}}} something new: {{{FAIL (count not connect to server: Operation would block}}} I'll recheck whether #2195 had any influence on this, and whether my F12 had any influence on it or whether I was just too impatient by now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 2 22:29:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 20:29:04 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.80046493b21c0fa855e94971dcf631d7@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: x86 -------------------------------------+-------------------------------------- Comment (by andreasf): Same revision, after restart, without Pe started, immediately passes {{{peek_close}}} but runs into a ca. two minute timeout in {{{read_and_peek}}} test, again leading to: {{{ FAIL (could not connect to server: Operation would block) }}} Next try, one test earlier, {{{small_reads}}}, and in the same run in {{{line_overlow}}} and {{{line_mingle}}} (which both passed the run before). Still looks a little random, but CPU is no longer 100% (~0%) and it times out at all. I noticed for some test earlier that client and server were being set up on the same (single) thread, could that be a problem? Seems like a non- standard scenario. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 00:27:36 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 22:27:36 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.2f6a298638dbcbfd1fd2a46d2d86868d@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): I have no idea right now what could be wrong. Is this really happening with all addresses > 2GB? Perhaps printing the bios e820 memory map to syslog will give some insight. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 00:38:45 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 22:38:45 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.4b45bd530380d79c7dbd1be3eea99e3d@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): does removing the firewire driver fix the problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 00:49:56 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 22:49:56 -0000 Subject: [Haiku-bugs] [Haiku] #1222: check if AboutHaiku lists an acknowledgment for all packages In-Reply-To: <045.849bde80d50effc77930688f383230ab@haiku-os.org> References: <045.849bde80d50effc77930688f383230ab@haiku-os.org> Message-ID: <054.a0a7bbc82762ff1d23934f9980f8c464@haiku-os.org> #1222: check if AboutHaiku lists an acknowledgment for all packages -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: nielx Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: fixed | Platform: All -------------------------+-------------------------------------------------- Changes (by nielx): * status: new => closed * resolution: => fixed Comment: Fixed in r25297. Thanks Scott for all the work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 01:00:18 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 23:00:18 -0000 Subject: [Haiku-bugs] [Haiku] #2196: testgl fails In-Reply-To: <042.11118a6d0c0b8ec1681ba5ba415ca14b@haiku-os.org> References: <042.11118a6d0c0b8ec1681ba5ba415ca14b@haiku-os.org> Message-ID: <051.82b3336c8dc5b783775cc25abb450799@haiku-os.org> #2196: testgl fails --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Changes (by andreasf): * cc: andreasf (added) * platform: All => x86 Comment: The actual error message is in the fifth line of your screenshot: {{{ Thread 23214 called debugger(): looper must be locked before proceeding }}} Since it runs to that point, it likely has nothing to do with linking. What does `bt` say? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 01:52:14 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 02 May 2008 23:52:14 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox Message-ID: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> #2197: KDL when starting Firefox --------------------------+------------------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Platform: All | --------------------------+------------------------------------------------- When starting Firefox from firefox.bin or link to it, it almost always results in KDL. If starting it in Terminal from the firefox script it starts OK. I have the "UserSetupEnvironment" file in: /home/config/boot. I had to create the /boot folder I am using Firefox 2.0.0.12 and Haiku r25268 on its own partition. I will attach screen images of KDL with backtrace and my "UserSetupEnvironment" file. I don't think there is anything wrong with this file. It is the same one, a copy of the file I use in BeOSR5.05 Bone and no problems with it there. I have Firefox in the same folder in /apps as in BeOSR5.05 Bone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 02:50:11 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 00:50:11 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.3e4ab6e49d7e781bda8203106681b599@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): I have no idea if any address after 2 Gb results in the problem, but empirical evidence seems to point to this (all the time it crashed, the last address added to the prd table was > 2 Gb). Also removing the firewire bus manager didn't help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 06:13:40 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 04:13:40 -0000 Subject: [Haiku-bugs] [Haiku] #2198: BTabView::SetSelectionMessage() Message-ID: <041.8b7339452e246c2f10f9287bba27a681@haiku-os.org> #2198: BTabView::SetSelectionMessage() --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: All | --------------------------------+------------------------------------------- I want BTabView::SetSelectionMessage() like BListView::SetSelectionMessage(). It is convenient for handling change of tab. For example, displaying help message for current tab, partiall layouting for similar view like search/replace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 09:39:11 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 07:39:11 -0000 Subject: [Haiku-bugs] [Haiku] #2198: BTabView::SetSelectionMessage() In-Reply-To: <041.8b7339452e246c2f10f9287bba27a681@haiku-os.org> References: <041.8b7339452e246c2f10f9287bba27a681@haiku-os.org> Message-ID: <050.ae2f6a6bcdc9e9d55b7fa7983b5eb94f@haiku-os.org> #2198: BTabView::SetSelectionMessage() ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by shinta): I thought about implementation. If BTabView with SetSelectionMessage() is implemented normally (like BListView), BTabView inherits both BView and BInvoker. But, this way breaks binary compatibility because of FBC (Fragile Base Class) problem. I think implementing BTabView by "has a" BInvoker won't be influenced by FBC problem. But, it is a bit trickky. I think it is better to let this enhancement wait for after Haiku R1 (breaking binary compatibility). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 13:20:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 11:20:12 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.24fb6a25c33df2699a735bc6f33280d4@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: hugosantos Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * owner: axeld => hugosantos * priority: normal => blocker * component: Applications => Network & Internet/TCP * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 14:41:20 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 12:41:20 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.fbe55ed96e21afbe68ea3d57b73723df@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * owner: hugosantos => axeld Comment: TCP still had Hugo as owner, but I'm afraid that's another component for me now :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 15:02:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 13:02:43 -0000 Subject: [Haiku-bugs] [Haiku] #2199: [PATCH] Typo in r25297 Message-ID: <043.eadb6c16c1cc61cadb9e3613f183f473@haiku-os.org> #2199: [PATCH] Typo in r25297 -------------------------+-------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- It's {{{sharutils}}}, not {{{shareutils}}}. Patch attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 15:17:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 13:17:31 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.683ddb216f2f53266877d262babc7ccf@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by bga): * priority: normal => blocker Comment: Ok, I did several tests now and after around 8 attempts it seems obvious to me that it is not exactly failing with addresses above 2 Gb. It is failing with exactly the same address all the time (0x80006000). I just attached a new KDL capture with the output of the traced command (showing the past 30 entries on it). Note that the oast entry is the address mentioned and this happened every single time. Considering we know that this address causes problems, would adding debug checking for this specific address somewhere help? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 15:18:39 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 13:18:39 -0000 Subject: [Haiku-bugs] [Haiku] #2194: KDL while using WGET with rt18139 In-Reply-To: <042.c5ca4744261df836361890420bc438c7@haiku-os.org> References: <042.c5ca4744261df836361890420bc438c7@haiku-os.org> Message-ID: <051.0a86335ec007733b83364321d02162ac@haiku-os.org> #2194: KDL while using WGET with rt18139 ---------------------------------+------------------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by bonefish): Up to (and including) the ":panic" line the beginnings of all stack traces are the same. So if you have to type anything manually the "PANIC: ..." line, the name of the thread, and a few lines of the stack trace after the ":panic" will be of most interest. You can also omit all numbers in the stack trace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 15:50:04 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 13:50:04 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon Message-ID: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon ------------------------------+--------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- BNodeInfo::GetIcon() can get vector icon by passing B_RGBA32 BBitmap, but, BMimeType::GetIcon() can't get. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 16:35:28 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 14:35:28 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon In-Reply-To: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> References: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> Message-ID: <050.113986f7a6cc794589158a43630c9013@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon -------------------------------+-------------------------------------------- Reporter: shinta | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: I'm afraid you will need to get more specific. If BMimeType::GetIcon() was generally broken, most icons in Tracker would not be visible. Particularily, BMimeType::GetIcon() is based on BNode like BNodeInfo. Please describe your particular situation in more detail. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 17:15:49 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 15:15:49 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon In-Reply-To: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> References: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> Message-ID: <050.3be001850af2378ccb372e94201b4e99@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon -------------------------------+-------------------------------------------- Reporter: shinta | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by shinta): Sorry! It was my misunderstanding! BMimeType::GetIcon() works well. By the way, why doesn't database_access.cpp's get_icon() use BIconUtils::GetIcon() such as the attached file? Sorry, I couldn't test the code because "jam -q" in src/kits/storage didn't work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 21:56:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 19:56:05 -0000 Subject: [Haiku-bugs] [Haiku] #2201: [PATCH] Disc Time Label (fDiscTime) not long enough Message-ID: <047.a4b7c7049929c5f4c8c957c896631e0b@haiku-os.org> #2201: [PATCH] Disc Time Label (fDiscTime) not long enough -----------------------------------+---------------------------------------- Reporter: sbrokenshire | Owner: darkwyrm Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CDPlayer | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- Using VMWare, Haiku SVN r25302 This is reproduced by starting CDPlayer, inserting an Audio CD (over 10 minutes long) and playing it. Disc Time Label (fDiscTime) shows the current and total disc time but total disc time is partially shown because fDiscTime is not long enough. Expected both current and total disc time to be shown in full. Patch attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 22:49:46 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 20:49:46 -0000 Subject: [Haiku-bugs] [Haiku] #2202: attempt to release lock 0x800d053c with interrupts enable Message-ID: <047.fabdd29ab8893ef66154f5b56ed845a0@haiku-os.org> #2202: attempt to release lock 0x800d053c with interrupts enable --------------------------+------------------------------------------------- Reporter: skarmiglione | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | --------------------------+------------------------------------------------- on senryu distro for virtualbox(in xp x64 version) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 3 23:23:16 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 21:23:16 -0000 Subject: [Haiku-bugs] [Haiku] #2203: Public header files need to be ANSI-compliant Message-ID: <043.ce1a7796582fd349a3b430f3c54160d4@haiku-os.org> #2203: Public header files need to be ANSI-compliant -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- In the posix headers there are lots of single-line comments, breaking compilation with {{{-ansi -pedantic}}}, as used by some software, such as freetype2. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 00:25:55 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 22:25:55 -0000 Subject: [Haiku-bugs] [Haiku] #2005: SB600 on HP6715b laptop finds no bootable devices. In-Reply-To: <039.78854b8e207617752d27e2f867835753@haiku-os.org> References: <039.78854b8e207617752d27e2f867835753@haiku-os.org> Message-ID: <048.0fa789a68a23843426ddc038a193480b@haiku-os.org> #2005: SB600 on HP6715b laptop finds no bootable devices. ---------------------------+------------------------------------------------ Reporter: euan | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by euan): patch attached to disable the audio device for now. will need to look into remapping in a future version. AHCI now works! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 00:50:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 22:50:21 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update to 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.392f2f838509759a710ecb2d8e540671@haiku-os.org> #2018: libpng needs update to 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by scottmc): * status: closed => reopened * resolution: fixed => * summary: libpng needs update to 1.2.25 to fix security issue => libpng needs update to 1.2.28 to fix security issue Comment: 1.2.28 compiles and passes all tests, just need to update in tree: http://tools.assembla.com/BePorts/wiki/media-libs/libpng Reopened the ticket due to it be labeled a security fix on libpng's site. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 01:22:09 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 03 May 2008 23:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.92cfe0c5d2e24b6bc4fb7d14eaf3181b@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by kaoutsis): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 03:26:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 01:26:56 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.96a9cfbf6f4fc0174e20872d30e25352@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): Please use r25306 and define TRACE_MEMORY_MAP and ENABLE_SERIAL to generate a new syslog / serial log with it. I don't think haiku is using the information correctly. FYI, this is from my board (4GB) extended memory info (from 0xe820): base 0x00000000, len 0x0009fc00, type 1 (memory) base 0x0009fc00, len 0x00000400, type 2 (reserved) base 0x000e3000, len 0x0001d000, type 2 (reserved) base 0x00100000, len 0xcfeb0000, type 1 (memory) base 0xcffb0000, len 0x0000e000, type 3 (ACPI reclaim) base 0xcffbe000, len 0x00032000, type 4 (ACPI NVS) base 0xcfff0000, len 0x00010000, type 2 (reserved) base 0xfee00000, len 0x00001000, type 2 (reserved) base 0xffb00000, len 0x00500000, type 2 (reserved) base 0x100000000, len 0x30000000, type 1 (memory) phys memory ranges: base 0x00000000, length 0xcffb0000 allocated phys memory ranges: base 0x0009f000, length 0x00321000 allocated virt memory ranges: base 0x80000000, length 0x006c5000 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 03:28:34 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 01:28:34 -0000 Subject: [Haiku-bugs] [Haiku] #2204: Missing or invalid form token. Do you have cookies enabled? Message-ID: <050.f5fbdc87e29214a5e345070fafd68271@haiku-os.org> #2204: Missing or invalid form token. Do you have cookies enabled? -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website/Trac | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Can somebody please fix this error? It appears sometimes when trying to add comments. {{{ Bad Request Missing or invalid form token. Do you have cookies enabled? }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 02:47:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 00:47:53 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon In-Reply-To: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> References: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> Message-ID: <050.2fa67d377b92eb6fd89dcf53138a6e59@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon -------------------------------+-------------------------------------------- Reporter: shinta | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by stippi): A mime database entry may specify several icons. Especially application entries may specify the icon of the application, plus one or more icons for associated files. Your code would only retrieve the application icon, since it ignores the "const char* fileType" parameter. As far as I am aware, every code that deals with icons, uses BIconUtils sooner or later. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 11:28:40 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 09:28:40 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon In-Reply-To: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> References: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> Message-ID: <050.803ea3a75b4ca140c7daf95329144b9e@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon -------------------------------+-------------------------------------------- Reporter: shinta | Owner: stippi Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by shinta): Thank you for explaining! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 12:08:54 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 10:08:54 -0000 Subject: [Haiku-bugs] [Haiku] #2205: [S3 diver] gives black screen after reboot Message-ID: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> #2205: [S3 diver] gives black screen after reboot ------------------------------+--------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- On behalf of totish (http://qube.ru/users/totish) I have Compaq Presario 714EA laptop with S3 Twister-K (card ID: 8d02, vendor ID:S3 Inc.(0x5333) ) Gerald Zajac sent me S3 driver compiled for R5, which i use in BeOS and Dano. I have 5 partitions with following OSes installed: Windows 98 Mandriva Dano BeOS Max Haiku The problem is: after reboot my laptop's screen goes black until i press space (which will activate first menu item in bootman) or hard reset. After that Windows 98 will start to load with half-shifted windows logo. This problem happens with Dano, BeOS Max and Haiku, but not with Windows 98 and Mandriva. If i remove S3 driver reboot works ok in all BeOS variants (i see text printed by BIOS). And windows logo is normal again. Please tell what additional info i should provide to help with this bug? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 12:09:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 10:09:30 -0000 Subject: [Haiku-bugs] [Haiku] #2205: [S3 diver] gives black screen after reboot In-Reply-To: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> References: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> Message-ID: <049.c9b5e46586235d170aca2741693ffa54@haiku-os.org> #2205: [S3 diver] gives black screen after reboot -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by diver): * cc: gerald, zajac (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 12:10:10 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 10:10:10 -0000 Subject: [Haiku-bugs] [Haiku] #2205: [S3 diver] screen goes black after reboot In-Reply-To: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> References: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> Message-ID: <049.ab19fd51ca00124b27706aab3a1fadc9@haiku-os.org> #2205: [S3 diver] screen goes black after reboot -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by diver): * summary: [S3 diver] gives black screen after reboot => [S3 diver] screen goes black after reboot -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 14:40:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 12:40:53 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.fe949d6a714e4f14785cf798cbb718cc@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): Here is mine: KERN: extended memory info (from 0xe820): KERN: base 0x00000000, len 0x0009ec00, type 1 (memory) KERN: base 0x0009ec00, len 0x00001400, type 2 (reserved) KERN: base 0x000e4000, len 0x0001c000, type 2 (reserved) KERN: base 0x00100000, len 0xbfe80000, type 1 (memory) KERN: base 0xbff80000, len 0x0000e000, type 3 (ACPI reclaim) KERN: base 0xbff8e000, len 0x00052000, type 4 (ACPI NVS) KERN: base 0xbffe0000, len 0x00020000, type 2 (reserved) KERN: base 0xe0000000, len 0x10000000, type 2 (reserved) KERN: base 0xfee00000, len 0x00001000, type 2 (reserved) KERN: base 0xffe00000, len 0x00200000, type 2 (reserved) KERN: base 0x100000000, len 0x40000000, type 1 (memory) Funny enough, I didn't find the other information anywhere in the output (note I do not have a serial port, so I am checking syslog). I wonder if I missed a define somewhere... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 14:48:57 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 12:48:57 -0000 Subject: [Haiku-bugs] [Haiku] #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. Message-ID: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. ---------------------------------+------------------------------------------ Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Platform: x86 | ---------------------------------+------------------------------------------ ShowImage (JPEGTranslator) crashes while reading Bride14MP.jpg. Bride14MP.jpg is Kodak Digital Camera sample file from http://wwwjp.kodak.com/JP/ja/professional/products/cameras/dcsproslr/sampleImageBride.shtml (This is Japanese site.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 15:13:17 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 13:13:17 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.966d5ba68a24f0ed5b6927594aba3227@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by andreasf): Update: bsd headers were included in r25137. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 15:21:43 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 13:21:43 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.4a2202c06430b511d1903850f069fdf5@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by andreasf): In addition to the missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. pkg-config files are also missing for libpng, whose headers are present under 3rdparty. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 15:54:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 13:54:02 -0000 Subject: [Haiku-bugs] [Haiku] #2207: Full volume causes hang after reboot Message-ID: <040.6e3532f230f937bec0f784ffde3ef214@haiku-os.org> #2207: Full volume causes hang after reboot -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- SW: 32-bit Ubuntu 8.04, Vmware Player 2.0.3, vmware-image built with gcc 2.95, rev 25306 HW: Lenovo T60 laptop Adding the optional package Links to UserBuildConfig without increasing the default disk size (currently 100 MB), causes a hang after rebooting. The first boot up is ok, the second one hangs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 16:27:06 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 14:27:06 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.ef933074c58138e5eef0848cfb03f54b@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Comments about the src_preferences_screensaver_ScreenSaverApp.cpp.diff: Actually there are modifications in two files: a) src/preferences/screensaver/ScreenSaverApp.cpp b) src/preferences/screensaver/ScreenSaverWindow.cpp Besides the find_directory fix, i take the freedom to add an enhancement: Now the ScreenSaver pref. can receive more than one ref at a time; so you can add one or more screensavers with the 'add' button or you can simply drag and drop the screensavers into the ScreenSaver window :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 18:13:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 16:13:52 -0000 Subject: [Haiku-bugs] [Haiku] #2208: "Disable user add-ons" doesn't work about input server add-ons Message-ID: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> #2208: "Disable user add-ons" doesn't work about input server add-ons ----------------------------------+----------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- I placed canna IM to ~/config/add-ons/input_server/methods. On booting Haiku, I selected safe mode option "Disable user add-ons", but, canna IM was usable. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 18:15:20 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 16:15:20 -0000 Subject: [Haiku-bugs] [Haiku] #1222: check if AboutHaiku lists an acknowledgment for all packages In-Reply-To: <045.849bde80d50effc77930688f383230ab@haiku-os.org> References: <045.849bde80d50effc77930688f383230ab@haiku-os.org> Message-ID: <054.ed9faf267046a8d02de42719016e8d90@haiku-os.org> #1222: check if AboutHaiku lists an acknowledgment for all packages -------------------------+-------------------------------------------------- Reporter: wkornewald | Owner: nielx Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: fixed | Platform: All -------------------------+-------------------------------------------------- Comment (by bonefish): Replying to [comment:20 bonefish]: > Replying to [comment:18 axeld]: > > BTW libMicro is an optional package as well, and doesn't have to be listed this way; the optional packages should now come with proper licensing information. > > Only the ones that download a zip file, which would contain a description file. That obviously doesn't work for optional packages built from sources in our repository. So I guess I have to add a rule that adds a copyright description after all. Did that in r25313. The new rules AddOptionalPackDescriptionToHaikuImage and AddLicenseToHaikuImage can be used in optional package descriptions to add the copyright entries and licenses. I did that for the libMicro optional package (r25314). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 18:33:22 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 16:33:22 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty Message-ID: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> #2209: Input method draws converting strings dirty --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- Input methods (IM) like Canna IM draws converting strings (bgcolor = pink, blue) dirty. See the attached picture. I guess that BView's low color (view color?) is set to white, although should be set to pink, blue. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 4 20:45:38 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 18:45:38 -0000 Subject: [Haiku-bugs] [Haiku] #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too Message-ID: <041.e42e0e567f26e193d44a2ed83bad8cd2@haiku-os.org> #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too -------------------------------------+-------------------------------------- Reporter: stpere | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- This enhancement is a followup of ticket 2170 : Following suggestion from Stephan, I've enhanced the revert feature of the Time preflets. 1. Clicking the revert button now also revert the timezone. 2. I have moved the revert button to the BaseView (below the tabs) 3. Since that on the default vmware-image (at least on my setup), there are no timezone link and this seems to confuse the preflet (it shows no text in the rolldown menu and the city list is empty), now, it assumes the Greenwich meridian time and shows it in the "Others" area. Note: I've encountered a crash once when reverting, but have not been capable to reproduce it. I've tried all the combinations I could think of (default to random timezone, then revert; random timezone to random timezone, then revert; etc...) and it seems to work ok. Note 2: I'm a bit confused by the desired behaviour or the localtime/gmt radio button in datetime panel. Could someone confirms it's ok? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 5 00:07:31 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 22:07:31 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.4161c7688712accf7f6e9a7966e2807e@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Changes (by koki): * cc: koki (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 5 00:13:15 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 04 May 2008 22:13:15 -0000 Subject: [Haiku-bugs] [Haiku] #2200: BMimeType::GetIcon() can't get vector icon In-Reply-To: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> References: <041.e5b443cb6e51b505141c83a0b95cea6d@haiku-os.org> Message-ID: <050.551a079dafd6589be432c4b6fa8a41d7@haiku-os.org> #2200: BMimeType::GetIcon() can't get vector icon -------------------------------+-------------------------------------------- Reporter: shinta | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: invalid | Platform: x86 -------------------------------+-------------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => invalid Comment: No problem at all! I am closing this as invalid then. I hope this conclusion is correct. Please just reopen if I misunderstood and there is a problem still left. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 5 09:12:14 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 05 May 2008 07:12:14 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.792a9c8825ca261f2b73daa3c260581c@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): I think string should be drawn separately (blue/red region) like attached patch. But, the patch has a bug on line breaking. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 5 18:27:47 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 05 May 2008 16:27:47 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.d1e6d230d34b9999afc39f772d19d830@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): I rewrited patch. TextView.diff should fix this problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 5 20:29:28 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 05 May 2008 18:29:28 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.e33e5e0cb820de16a3fc4615218995fd@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * owner: axeld => jackburton Comment: Thanks! I'll assign this to Stefano for review, as he is our BTextView master :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 6 00:56:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 05 May 2008 22:56:42 -0000 Subject: [Haiku-bugs] [Haiku] #2208: "Disable user add-ons" doesn't work about input server add-ons In-Reply-To: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> References: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> Message-ID: <050.124ee3b5cc1fd4d29f57197ede28f26b@haiku-os.org> #2208: "Disable user add-ons" doesn't work about input server add-ons -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by korli): It seems we would need B_SAFEMODE_DISABLE_USER_ADD_ONS in drivers/driver_settings.h Thoughts ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 6 14:32:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 06 May 2008 12:32:23 -0000 Subject: [Haiku-bugs] [Haiku] #2061: Installer button always shows "Begin" In-Reply-To: <042.aba83a0e9b67deba2eedc12ad92797fe@haiku-os.org> References: <042.aba83a0e9b67deba2eedc12ad92797fe@haiku-os.org> Message-ID: <051.da6f564019c3972d03604822d74a9924@haiku-os.org> #2061: Installer button always shows "Begin" -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * owner: axeld => korli * component: Applications => Applications/Installer Comment: I have a patch here by Christian Fasshauer that he should attach to this bug soon for review. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 6 23:33:04 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 06 May 2008 21:33:04 -0000 Subject: [Haiku-bugs] [Haiku] #2208: "Disable user add-ons" doesn't work about input server add-ons In-Reply-To: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> References: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> Message-ID: <050.300db3bf1c94abb50fbd97e054bc76bd@haiku-os.org> #2208: "Disable user add-ons" doesn't work about input server add-ons -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by korli): Could you check with r25330 please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 14:41:44 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 12:41:44 -0000 Subject: [Haiku-bugs] [Haiku] #2208: "Disable user add-ons" doesn't work about input server add-ons In-Reply-To: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> References: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> Message-ID: <050.94458d632186a46e8df51b72be26b10c@haiku-os.org> #2208: "Disable user add-ons" doesn't work about input server add-ons -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): Thank you for modifying! It works well. I worried about the code "Unload()". Are add-ons loaded once? But, it seems not to be loaded. We can avoid harmful add-ons. Thank you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 15:13:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 13:13:59 -0000 Subject: [Haiku-bugs] [Haiku] #2208: "Disable user add-ons" doesn't work about input server add-ons In-Reply-To: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> References: <041.e33765e07cbadba3a5bbda307caf29a4@haiku-os.org> Message-ID: <050.7a33ebecdad03df1745a54e90c431224@haiku-os.org> #2208: "Disable user add-ons" doesn't work about input server add-ons -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Replying to [comment:3 shinta]: > I worried about the code "Unload()". Are add-ons loaded once? But, it seems not to be loaded. We can avoid harmful add-ons. Actually the Deskbar loads replicants which were loaded on the last shutdown. So the input method replicant could load even if the input_server didn't try to load it. For this reason, we unload the replicant anytime it shouldn't be loaded. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 15:31:17 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 13:31:17 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.58710bf805b3e9c0ebd792dbaa4f65e5@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): I have reviewed the patch and it looks fine to me. However, as I understand, all this is supposed to do is fix the bad text anti-aliasing. The patch adds considerable overhead just to be able to use B_OP_COPY text rendering (the only text rendering where the low color of the view is used regardless of the true background of the text). While B_OP_COPY rendering is indeed much faster, the added client-server communication in this patch should completely ruin any speed gains. Therefor, I would vote to keep the original code and simply add a view->SetDrawingMode(B_OP_OVER) before rendering the inputted text in order to make the text blend with the true background. This also makes the code easier to read, understand and extend. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 15:33:11 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 13:33:11 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.143f6e5b3bbcfbd0898c45887ec5bb1d@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): Oh, forgot to mention... there are a couple of issues with the patch as is: The drawing view is not used consistently, so with double buffered drawing, it would not work. And the added private function has a typo in it's name. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 15:48:42 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 13:48:42 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.f333759816a18404a744f44db6c9f46f@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by stippi): SHINTA, could you have a look at my "Alternative Fix" patch? Does that solve the observed problem as well? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 16:42:37 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 14:42:37 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.243d61bcaa6bfbfa6d9e2054680d3ca6@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): stippi, your patch works well. It's simple! Thank you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 17:40:37 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 15:40:37 -0000 Subject: [Haiku-bugs] [Haiku] #2209: Input method draws converting strings dirty In-Reply-To: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> References: <041.c98acbd2eed0a8ed92d61f83a70bbf1c@haiku-os.org> Message-ID: <050.035a7b71343e4817caf38a5b21095df5@haiku-os.org> #2209: Input method draws converting strings dirty ---------------------------------+------------------------------------------ Reporter: shinta | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback (was unable to test). Thus fixed in r25349. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 18:20:46 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 16:20:46 -0000 Subject: [Haiku-bugs] [Haiku] #2211: KDL: vm_page_fault: unhandled page fault in kernel space at 0xccccccd0, ip 0x80044480 Message-ID: <043.c03736721dd10f0d6eca1804015f49f9@haiku-os.org> #2211: KDL: vm_page_fault: unhandled page fault in kernel space at 0xccccccd0, ip 0x80044480 -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- where stack trace for thread 9776 "ScreenSaver" kernel stack: 0x93004000 to 0x93008000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 93007ae8 (+ 52) 8008baa7 :invoke_debugger_command + 0x00cf 93007b1c (+ 64) 8008c850 :_ParseCommand__16ExpressionParserRi + 0x01f8 93007b5c (+ 48) 8008c242 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 93007b8c (+ 228) 8008d964 :evaluate_debug_command + 0x0088 93007c70 (+ 64) 8008a5e2 :kernel_debugger_loop__Fv + 0x017a 93007cb0 (+ 48) 8008b295 :kernel_debugger + 0x010d 93007ce0 (+ 192) 8008b17d :panic + 0x0029 93007da0 (+ 64) 800626df :vm_page_fault + 0x00ab 93007de0 (+ 64) 80098259 :page_fault_exception + 0x00b1 93007e20 (+ 12) 8009b93d :int_bottom + 0x001d (nearest) iframe at 0x93007e2c (end = 0x93007e84) eax 0x910ce0f0 ebx 0xcccccccc ecx 0x7 edx 0x246 esi 0x7 edi 0x910ce0f0 ebp 0x93007e94 esp 0x93007e60 eip 0x80044480 eflags 0x10286 vector: 0xe, error code: 0x0 93007e2c (+ 104) 80044480 :deselect_select_infos__FP15file_descriptorP11select_info + 0x0014 93007e94 (+ 64) 800441f0 :remove_fd__FP10io_contexti + 0x00ac 93007ed4 (+ 48) 80043f9f :close_fd_index + 0x0017 93007f04 (+ 32) 80044a5d :common_close__Fib + 0x0031 93007f24 (+ 32) 80045334 :_user_close + 0x0018 93007f44 (+ 100) 8009bab2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x93007fa8 (end = 0x93008000) eax 0x79 ebx 0x72c0e0 ecx 0x7ffd289c edx 0x910ce0f4 esi 0x2a8 edi 0x7 ebp 0x7ffd255c esp 0x93007fdc eip 0xffff0102 eflags 0x203 vector: 0x63, error code: 0x0 93007fa8 (+ 0) ffff0102 7ffd255c (+ 64) 00577326 :ReadAttr__C5BNodePCcUlxPvUl + 0x005a 7ffd259c (+1024) 0020a95a <_APP_>:_term_after + 0x014e (nearest) 7ffd299c (+ 48) 0020a9ee <_APP_>:_term_after + 0x01e2 (nearest) 7ffd29cc (+82416) 0020b57b <_APP_>:RefsReceived__14ScreenSaverAppP8BMessage + 0x0a7f 7ffe6bbc (+ 496) 004aabae :DispatchMessage__12BApplicationP8BMessageP8BHandler + 0x02b2 7ffe6dac (+ 64) 004b51b9 :task_looper__7BLooper + 0x0211 7ffe6dec (+ 64) 004a9535 :Run__12BApplication + 0x0075 7ffe6e2c (+ 336) 0020bd87 <_APP_>:main + 0x002f 7ffe6f7c (+ 48) 0020a72b <_APP_>:_start + 0x005b 7ffe6fac (+ 48) 0010078e 21901:runtime_loader_seg0ro at 0x00100000 + 0x78e 7ffe6fdc (+ 0) 7ffe6fec 21900:ScreenSaver_main_stack at 0x7efe7000 + 0xffffec kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 18:54:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 16:54:05 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.5a7b5d6147ddce976ffe808ee5124400@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by tqh): * cc: tqh (added) Comment: That UserSetupEnvironment seems to be broken. Has it gone broken when uploading or is that so? Look at end of second line. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 22:03:06 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 20:03:06 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot Message-ID: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- SW: 32-bit Ubuntu 8.04, Vmware Player 2.0.3, vmware-image built with gcc 2.95 HW: Lenovo T60 laptop Since r25309, with a freshly built .vmdk, the Haiku desktop icons (Haiku, Trash, Home) don't appear until after first reboot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 22:07:55 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 20:07:55 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.f9fd6c8331a1b32d27e1430ae1ed11f5@haiku-os.org> #2212: r25309 removed desktop icons from first boot ------------------------+--------------------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Changes (by anevilyak): * cc: anevilyak (added) * owner: axeld => bonefish Comment: This was one of Ingo's changes I believe, reassigning. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 22:09:11 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 20:09:11 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.8bd9ea6b932101ad10195b8cc085044b@haiku-os.org> #2212: r25309 removed desktop icons from first boot ------------------------+--------------------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by diver): I have the same problem with reaal hw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 7 22:55:17 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 20:55:17 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.c1326d3f25ba0e4dbf397380a5abcb94@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by bonefish): * component: - General => Applications/Tracker Comment: I've seen that problem earlier, so I don't think my changes are to blame. They might cause the bug to occur more frequently though. Maybe the incoming MIME update messages cause some message queue to run full and result in a deadlock. Might be related to #1715. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 00:20:33 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 22:20:33 -0000 Subject: [Haiku-bugs] [Haiku] #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! In-Reply-To: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> References: <040.572daffe104be83e982ae20fb33b51e3@haiku-os.org> Message-ID: <049.1531a3212e95c7ebc330010699e6f406@haiku-os.org> #1914: PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)! ----------------------------+----------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: reopened Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Similar with a fresh built r25359 Installer was used to install Haiku on a smaller fresh empty disk (smaller than the boot disk), it produced errors but FinishScript was tried to be launched though. Bash complains it was not executable Then tried 'vi' on the FinishScript. {{{ SCSI_DSK -- synchronize_cache: wait interval 1000000, scan pages 512, free 4096, target 0 Last message repeated 3 times. SCSI_DSK -- synchronize_cache: bfs: invalid node [0x93945400] read from offset 89088 (block 3382), inode at 2114 bfs: BPlusTree::_SeekDown() could not open node 89088 bfs: Insert:1275: General system error bfs: Update:288: General system error bfs: Create:2468: General system error bfs: invalid node [0x93945400] read from offset 89088 (block 3382), inode at 2114 bfs: BPlusTree::_SeekDown() could not open node 89088 bfs: Insert:1275: General system error bfs: Update:288: General system error bfs: Create:2468: General system error PANIC: vnode 3:393737 already exists (node = 0x90c6b780, vnode->node = 0x90cdad80)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 245 "vim main()" kernel stack: 0x92988000 to 0x9298c000 user stack: 0x70000000 to 0x70040000 frame caller :function + offset 9298b7fc (+ 52) 800485db :invoke_debugger_command + 0x00cf 9298b830 (+ 64) 80049384 :_ParseCommand__16ExpressionParserRi + 0x01f8 9298b870 (+ 48) 80048d76 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 9298b8a0 (+ 228) 8004a498 :evaluate_debug_command + 0x0088 9298b984 (+ 64) 80047116 :kernel_debugger_loop__Fv + 0x017a 9298b9c4 (+ 48) 80047dc9 :kernel_debugger + 0x010d 9298b9f4 (+ 192) 80047cb1 :panic + 0x0029 9298bab4 (+ 64) 8007611a :new_vnode + 0x006a 9298baf4 (+ 80) 805c1338 :New__14InodeAllocatorP9block_runUiR9block_runP12fs_vnode_opsPP5Inode + 0x0170 9298bb44 (+ 176) 805c7ad9 :Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5InodeP12fs_vnode_opsUl + 0x0579 9298bbf4 (+ 96) 805d0849 :bfs_create__FP9fs_volumeP8fs_vnodePCciiPPvPx + 0x0125 9298bc54 (+ 352) 80078418 :create_vnode__FP5vnodePCciib + 0x0188 9298bdb4 (+ 320) 800787b6 :file_create__FiPciib + 0x005a 9298bef4 (+ 80) 8007db54 :_user_open + 0x00bc 9298bf44 (+ 100) 8009f1c2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x9298bfa8 (end = 0x9298c000) eax 0x55 ebx 0x62c584 ecx 0x7003f700 edx 0xffff0104 esi 0x18051537 edi 0x18047510 ebp 0x7003f72c esp 0x9298bfdc eip 0xffff0104 eflags 0x202 vector: 0x63, error code: 0x0 9298bfa8 (+ 0) ffff0104 7003f72c (+1232) 00296153 <_APP_>:get_file_in_dir + 0x031b (nearest) 7003fbfc (+ 48) 00292589 <_APP_>:ml_open_file + 0x006d 7003fc2c (+ 48) 00292660 <_APP_>:check_need_swap + 0x0044 7003fc5c (+ 448) 002700ad <_APP_>:readfile + 0x0881 7003fe1c (+ 112) 0022656f <_APP_>:open_buffer + 0x0127 7003fe8c (+ 240) 00286b3f <_APP_>:main + 0x1acf 7003ff7c (+ 48) 00315fc5 <_APP_>:call_main__FPv + 0x0025 7003ffac (+ 48) 005a6f40 :_get_next_team_info + 0x005c (nearest) 7003ffdc (+ 0) 7003ffec 2135:vim main()_245_stack at 0x70000000 + 0x3ffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 00:54:30 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 07 May 2008 22:54:30 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.29e250259ea85d539e6599c468ee41a5@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Comments about the src_preferences_screensaver_ScreenSaverApp.cpp.diff: ?he ScreenSaver pref. is now capable to distinguish the real screensavers and installs only them to the user addon directory, when the user drop files in the ScreenSaver pref. window; tested successfully with the collection of screensavers attached to #511 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 05:12:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 03:12:33 -0000 Subject: [Haiku-bugs] [Haiku] #1462: via.accelerant and via.driver are missing from the build. In-Reply-To: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> References: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> Message-ID: <051.18cb495e88a3476927c8390396839c77@haiku-os.org> #1462: via.accelerant and via.driver are missing from the build. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by bbjimmy): * status: closed => reopened * resolution: fixed => Comment: The driver was removed again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 05:16:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 03:16:33 -0000 Subject: [Haiku-bugs] [Haiku] #2088: kernel page writer thread In-Reply-To: <042.63a36be1f3c7d11fa5a408b57a7c51a7@haiku-os.org> References: <042.63a36be1f3c7d11fa5a408b57a7c51a7@haiku-os.org> Message-ID: <051.687ec8d99cb7c3f7b581bf9cf455e354@haiku-os.org> #2088: kernel page writer thread ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by bbjimmy): Please close this ticket -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 05:32:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 03:32:03 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. Message-ID: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> #2213: KDL page fault re-starting tne media server. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ r25336 From the Media Preferences app, select Restart Media Services and the system stops with a KDL page fault. I am using Auvia 8235 but the system always defaults to VIA VT82135 after updating to a newer HAIKU version. This device will not produce any sound. Setting the system to use the Auvia 8235 for input and output then restarting the media services will always KDL. after rebooting, the proper audio device is selected and the sound system then works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 09:44:51 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 07:44:51 -0000 Subject: [Haiku-bugs] [Haiku] #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen In-Reply-To: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> References: <040.17c8090d9b429398540eaed4e454250d@haiku-os.org> Message-ID: <049.a08371a394b23363f03583b2b5cdc3fd@haiku-os.org> #1959: nVidia Corporation NV11 [GeForce2 Go]: drawing problems after new splash screen --------------------------------------+------------------------------------- Reporter: nielx | Owner: korli Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by nielx): * status: new => closed * resolution: => fixed Comment: Fixed. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 10:32:32 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 08:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #2088: kernel page writer thread In-Reply-To: <042.63a36be1f3c7d11fa5a408b57a7c51a7@haiku-os.org> References: <042.63a36be1f3c7d11fa5a408b57a7c51a7@haiku-os.org> Message-ID: <051.3451193284f79d69fcff3cfe406db423@haiku-os.org> #2088: kernel page writer thread ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:04:30 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.5a00afb70336c1c7dea42bcd30fc9c33@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Could you provide a stacktrace ? (type 'sc') Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:15:27 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:15:27 -0000 Subject: [Haiku-bugs] [Haiku] #1462: via.accelerant and via.driver are missing from the build. In-Reply-To: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> References: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> Message-ID: <051.beedfa6a4609d4f222ba485b05e26a5f@haiku-os.org> #1462: via.accelerant and via.driver are missing from the build. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by korli): It was removed in r24620 because it seems not mature enough: see #1973 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:22:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:22:08 -0000 Subject: [Haiku-bugs] [Haiku] #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset In-Reply-To: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> References: <044.c690a35a0e5b6d7b59e9d6ffb3cf95aa@haiku-os.org> Message-ID: <053.c78eaf85905ae7cf4e24093eee64f8bb@haiku-os.org> #1973: Video drivers and VESA driver don't work with VIA K8N800 video chipset -----------------------------------+---------------------------------------- Reporter: zaranthos | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/VIA | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * owner: axeld => rudolfc Comment: Reassigning to Rudolf in case he has an idea. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:25:44 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:25:44 -0000 Subject: [Haiku-bugs] [Haiku] #1462: via.accelerant and via.driver are missing from the build. In-Reply-To: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> References: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> Message-ID: <051.2ca236b4060eb6908f65650812bc9118@haiku-os.org> #1462: via.accelerant and via.driver are missing from the build. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by korli): Maybe we should remove the PCI id impacted by #1973 and add again the driver. Which PCI id do you have the driver working with ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:29:39 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:29:39 -0000 Subject: [Haiku-bugs] [Haiku] #2176: Opening new tab in Terminal should switch to the new tab. In-Reply-To: <038.5ce84d356f6e488645fdbcc5b8d8cb4f@haiku-os.org> References: <038.5ce84d356f6e488645fdbcc5b8d8cb4f@haiku-os.org> Message-ID: <047.f7dc81bee91b547ce9ca11e834769ea6@haiku-os.org> #2176: Opening new tab in Terminal should switch to the new tab. ------------------------------------+--------------------------------------- Reporter: bga | Owner: jackburton Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Platform: All ------------------------------------+--------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: It's done in r25365 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:41:57 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:41:57 -0000 Subject: [Haiku-bugs] [Haiku] #2214: [Terminal]: replicant capable Message-ID: <042.041e6b13e5ee468043c8331d1c533559@haiku-os.org> #2214: [Terminal]: replicant capable -----------------------------------+---------------------------------------- Reporter: emitrax | Owner: jackburton Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Applications/Terminal | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- Terminal is not replicant capable, or if it is, it miss the replicant button. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 12:44:15 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 10:44:15 -0000 Subject: [Haiku-bugs] [Haiku] #1462: via.accelerant and via.driver are missing from the build. In-Reply-To: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> References: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> Message-ID: <051.01437063b3fe65beab64906c400396de@haiku-os.org> #1462: via.accelerant and via.driver are missing from the build. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Changes (by axeld): * status: reopened => closed * resolution: => invalid Comment: The driver as a whole is really not yet mature enough to be used. It must not be added to the image by default yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 13:45:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 11:45:59 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.a54ca5f724f8766bc025794dcca45725@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by korli): HWindow.cpp, TrackerInitialState.cpp and FontManager.cpp patched -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 14:09:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 12:09:59 -0000 Subject: [Haiku-bugs] [Haiku] #2214: [Terminal]: replicant capable In-Reply-To: <042.041e6b13e5ee468043c8331d1c533559@haiku-os.org> References: <042.041e6b13e5ee468043c8331d1c533559@haiku-os.org> Message-ID: <051.1fef2d67f5e062e336a672d975f32778@haiku-os.org> #2214: [Terminal]: replicant capable ------------------------------------+--------------------------------------- Reporter: emitrax | Owner: jackburton Type: enhancement | Status: closed Priority: low | Milestone: Unscheduled Component: Applications/Terminal | Version: R1 development Resolution: fixed | Platform: All ------------------------------------+--------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: It's done in r25370. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 18:15:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 16:15:03 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal colors as replicant goto black on white even if selected otherwise Message-ID: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> #2215: Terminal colors as replicant goto black on white even if selected otherwise -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- To duplicate, change the color settings of the terminal, and then drag it out as a replicant, you then see your colors go back to black on white. I think this was in r25374 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 18:17:38 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 16:17:38 -0000 Subject: [Haiku-bugs] [Haiku] #2216: KDL when attempting to open Audio CD in tracker Message-ID: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> #2216: KDL when attempting to open Audio CD in tracker -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Audio CD automounts and is shown on the desktop, but when I try to open it I get dropped into KDL. This was with a development build for vmware, r25374 i think. Screenshot attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 20:21:02 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 18:21:02 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.b8682cd436ba3c19d8359dcd0bc56987@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): Hi Marcus. Did the information I posted help at all? Also, any idea why the rest of the information was not printed? Any chance that, for some reason, that function is not being called at all in my configuration? ddew, do you have a serial port on your machine so you can try to get more information? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 8 20:48:40 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 08 May 2008 18:48:40 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.2a0713f74b180cb5ef382ed4fcd4689d@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by ddew): I do have a serial port on it but I still haven't had time to get hold of a serial cable, I'll hopefully be able to pick one up this weekend and do some testing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 9 09:29:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 09 May 2008 07:29:04 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.fa7ea1b616342988fb9acf3dd1c6d9da@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by jackburton): Replying to [comment:20 bga]: > Hi Marcus. Did the information I posted help at all? Also, any idea why the rest of the information was not printed? Any chance that, for some reason, that function is not being called at all in my configuration? > Some of the early boot logging doesn't end up in the syslog, it seems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 9 15:58:18 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 09 May 2008 13:58:18 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.89980cad6dee10276c786a0f8f7650a0@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by stippi): > > > Should be fixed with r24607. If it doesn't happen for you anymore, > > > please close this ticket. > > I hit the problem again with r24614. I suppose I have to reinitialize > > partitions that I used with an earlier BFS version, right? > You better should Can this be closed then? :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 9 16:00:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 09 May 2008 14:00:39 -0000 Subject: [Haiku-bugs] [Haiku] #2148: BFS volume not fully written to In-Reply-To: <043.3083193f1d74cb863e554761dcc63606@haiku-os.org> References: <043.3083193f1d74cb863e554761dcc63606@haiku-os.org> Message-ID: <052.c63ce50e10e6d083d753b66106901cee@haiku-os.org> #2148: BFS volume not fully written to -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by stippi): Andreas, what about it... is the problem fixed now? :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 9 17:28:29 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 09 May 2008 15:28:29 -0000 Subject: [Haiku-bugs] [Haiku] #1956: Garbage In Files In-Reply-To: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> References: <043.b26038f2dc2fcacc60d26d407839e6d0@haiku-os.org> Message-ID: <052.431d6b2135c748703b4499b67782cda7@haiku-os.org> #1956: Garbage In Files ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Talked to Ingo on the phone, this one has just been forgotten... fixed in r24607. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 9 21:47:30 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 09 May 2008 19:47:30 -0000 Subject: [Haiku-bugs] [Haiku] #2148: BFS volume not fully written to In-Reply-To: <043.3083193f1d74cb863e554761dcc63606@haiku-os.org> References: <043.3083193f1d74cb863e554761dcc63606@haiku-os.org> Message-ID: <052.0710236fd2585c96b0aae469c6c8e1c7@haiku-os.org> #2148: BFS volume not fully written to -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Platform: x86 -------------------------------+-------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: According to Andreas, the problem is fixed since r25249. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 04:43:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 02:43:12 -0000 Subject: [Haiku-bugs] [Haiku] #947: Konatu Tohaba isn't recognized as monospaced font In-Reply-To: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> References: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> Message-ID: <054.99ad2b87927d039ed8b30da29336b1e9@haiku-os.org> #947: Konatu Tohaba isn't recognized as monospaced font -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by shinta): Japanese monospaced font generally has two kind of width. Characters like alphabet or number (inluded in western font) have narrow width (512 in your example). They are called "Hankaku". On the other hand, mainly Japanese caracters like kana or kanji have wide width (1024 in your example). They are called "Zenkaku". Zenkaku's width is exactly twice of Hankaku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 04:45:07 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 02:45:07 -0000 Subject: [Haiku-bugs] [Haiku] #947: Konatu Tohaba isn't recognized as monospaced font In-Reply-To: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> References: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> Message-ID: <054.5a0e23f29c215124645b7de6490b3c9d@haiku-os.org> #947: Konatu Tohaba isn't recognized as monospaced font -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Changes (by shinta): * cc: shinta (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 05:16:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 03:16:50 -0000 Subject: [Haiku-bugs] [Haiku] #1471: Deskbar's Auto Raise could be activated more specifically In-Reply-To: <044.efcd1d1de086b9b991d4dd4325c114af@haiku-os.org> References: <044.efcd1d1de086b9b991d4dd4325c114af@haiku-os.org> Message-ID: <053.005391668c5b2b40b5af20f5d4dd3532@haiku-os.org> #1471: Deskbar's Auto Raise could be activated more specifically --------------------------+------------------------------------------------- Reporter: meanwhile | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by shinta): * cc: shinta (added) Comment: I have a request, too. Currently, Deskbar get focus on raising, but, I don't like. I need to click previous window when cursors accidentaly hit Deskbar. I like behavior of Windows' taskbar's auto raise. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 05:26:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 03:26:57 -0000 Subject: [Haiku-bugs] [Haiku] #1735: Integrate changes from the japanese community In-Reply-To: <045.462b8ab56e5974d20bc4e4e0c873736b@haiku-os.org> References: <045.462b8ab56e5974d20bc4e4e0c873736b@haiku-os.org> Message-ID: <054.78ed76f6b2556bbfa946631f4d5092d7@haiku-os.org> #1735: Integrate changes from the japanese community --------------------------+------------------------------------------------- Reporter: jackburton | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by shinta): * cc: shinta (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 05:45:52 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 03:45:52 -0000 Subject: [Haiku-bugs] [Haiku] #947: Konatu Tohaba isn't recognized as monospaced font In-Reply-To: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> References: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> Message-ID: <054.fb47a617ce94ae2c8746a18e28ab29e1@haiku-os.org> #947: Konatu Tohaba isn't recognized as monospaced font -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Changes (by koki): * cc: koki (added) Comment: According to the definition of "monospaced font" in the FontForge FAQ... http://fontforge.sourceforge.net/faq.html#monospace ...for a font to be considered monospaced, all glyphs must have the same width. By this definition, Japanese fonts (which include single-width and double-width glyphs) are not monospaced. FWIW, we actually had a related discussion on this thread of the Pe mailing list here: http://www.freelists.org/archives/pedevel/04-2008/msg00059.html It would be really nice if Haiku could, at the OS level, recognize this Japanese fonts as monospaced, so that they can be selected/used in applications. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 07:03:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 05:03:29 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.700d333c754ba8d8d7a121267db6e1c3@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by bbjimmy): As close as I can get to a stack trace. It's not a very good image I'm afraid. http://coquilletkd.com/fatelk/haiku/DSCN0784.JPG -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 07:51:00 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 05:51:00 -0000 Subject: [Haiku-bugs] [Haiku] #2217: Terminal replicant graphic scrolls off the screen Message-ID: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> #2217: Terminal replicant graphic scrolls off the screen -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- The little graphic that allows you to drag the replicant around, scrolls up with the screen with test, eventually disappearing. When the terminal is dragged out to the desktop and this happens you now have no visible way to close it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 07:55:28 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 05:55:28 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) Message-ID: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) ----------------------------------+----------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- Currently, key binding for turning on/off input methods (switching Roman <--> (Japanese) input methods) is "Alt+Space" or "Alt+Zenkaku/Hankaku". (FYI: Zenkaku/Hankaku is a key which Japanese keyboard has.) Alt+Space is good. Alt+Zenkaku/Hankaku is required to change in Japanese community. Please no-midifiers Zenkaku/Hankaku, not Alt+Zenkaku/Hankaku. Currently, Zenkaku/Hankaku itself has no function, so, it is reasonable to make no- modifiers Zenkaku/Hankaku turn on/off. Actually, old versions of Windows used Alt+Zenkaku/Hankaku to turn on/off input methods, but, current version of Windows uses no-modifiers Zenkaku/Hankaku. cf: JPBE.net IM relative forum thread http://www.jpbe.net/forum/viewtopic.php?p=7763#7763 Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (enhancement No.2) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 08:36:59 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 06:36:59 -0000 Subject: [Haiku-bugs] [Haiku] #2219: Bottomline window doesn't confirm strings on switching focus view Message-ID: <041.050c9ca87003e558344dc598aeb9334f@haiku-os.org> #2219: Bottomline window doesn't confirm strings on switching focus view ----------------------------------+----------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- When we input Japanese strings with inline input by IM (input method), unconfirmed strings (blue backed strings) is confirmed on switching focus view. But, when we input through bottomline window, unconfirmed strings isn't confirmed on switching focus view. ZETA has same bug. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (bug No.15) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 08:44:51 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 06:44:51 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.16a076ef78e042cdab99f79c119ffd21@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by koki): * cc: koki (added) Comment: SHINTA-san, Can you provide a patch to attain the desired change? If you can, please provide one as an attachment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 08:53:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 06:53:57 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.11d1913a041ff713b91eb55fd00526ee@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): I'll try. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 09:56:14 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 07:56:14 -0000 Subject: [Haiku-bugs] [Haiku] #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) Message-ID: <041.8ebc7d3b95778d708ba44ac6d6596515@haiku-os.org> #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- When bottomline window is closed, B_INPUT_METHOD_STOPPED is sent to input method whether unconfirmed strings exist or not. I think that B_INPUT_METHOD_STOPPED should be sent only if unconfirmed strings exist. This bug influence to Anthy for Haiku. When I convert in bottomline window and don't confirm kana-kanji strings, next one character is disposed because B_INPUT_METHOD_STOPPED make Anthy flush next one character. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (bug No.16) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 10:39:39 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 08:39:39 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.68a29f2861687a5313c542f648e7c8fd@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * owner: marcusoverhagen => mmu_man Comment: Indeed, the photo is pretty bad - try without the flash next time, and try to put your elbows on the table as a tripod replacement :-) Anyway, it looks like it's somewhere in OSS. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 12:39:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 10:39:57 -0000 Subject: [Haiku-bugs] [Haiku] #2217: Terminal replicant graphic scrolls off the screen In-Reply-To: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> References: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> Message-ID: <051.d940b0eb328602b2a9e9f584f5c9c48c@haiku-os.org> #2217: Terminal replicant graphic scrolls off the screen ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by stippi): I would vote to remove the replicant feature for the time being, unless this can be solved. I think even the replicant needs a scroll bar, so I would put it onto a different level of the view hierarchy. As it is now, I think it is just irritating. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 12:44:48 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 10:44:48 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one Message-ID: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- In R5, kLeftTitledWindowLook's leftside title bar is from top to bottom. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (bug No.17) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 12:48:00 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 10:48:00 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap Message-ID: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap ----------------------------------+----------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Platform: x86 | ----------------------------------+----------------------------------------- Zenkaku/Hankaku key code isn't defined in Japanese keymap. Current key code seem to be space. Haiku: r25124+ [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (bug No.18) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 12:53:39 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 10:53:39 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.fac381ae2ce246a673ceb90951899a3f@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by mmu_man): * status: new => assigned Comment: Yes I know about it. I first need to port my changes to the mercurial tree before I can investigate. Btw, it might be due to the fact that 2 media nodes exist (one in /boot/beos/add-ons from jam and one in ~/config/add-ons from the optional package). It shouldn't KDL anyway but maybe if you remove one it will work around it meanwhile ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 12:54:22 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 10:54:22 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.8c0727418da4b8fb8c8a844cfc34a566@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by mmu_man): It might also be due to conflicts with the native driver... but that can't be fixed before Haiku has proper device resource reservation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:29:30 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:29:30 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.2ba6c90fdb6479bd9e373a68de4a95dc@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): Attached patch changes two key codes: Zenkaku/Hankaky key and Katakana/Hiragana key. Japanese specific key codes are below: {{{ Key name Scan Windows' Windows' code(?) constants virtual key code -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Zenkaku/Hankaku 0x11 VK_OEM_AUTO 0xf3 Katakana/Hiragana 0x6e VK_OEM_COPY 0xf2 Henkan 0x6d VK_CONVERT 0x1c Muhenkan 0x6c VK_NONCONVERT 0x1d }}} (cf. http://lldev.jp/hsp/script/h_virtual_key.html) I didn't change the key codes of Henkan and Muhenkan because their key codes are already used by arrow keys. I tested this patch at my Japanese keyboard "Owltech OWL-KB108PA". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:29:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:29:58 -0000 Subject: [Haiku-bugs] [Haiku] #2201: [PATCH] Disc Time Label (fDiscTime) not long enough In-Reply-To: <047.a4b7c7049929c5f4c8c957c896631e0b@haiku-os.org> References: <047.a4b7c7049929c5f4c8c957c896631e0b@haiku-os.org> Message-ID: <056.73b1679930f0d04a43431d7d98e25bc5@haiku-os.org> #2201: [PATCH] Disc Time Label (fDiscTime) not long enough ------------------------------------+--------------------------------------- Reporter: sbrokenshire | Owner: darkwyrm Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/CDPlayer | Version: R1 development Resolution: fixed | Platform: All ------------------------------------+--------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r25412. I did not use your patch, because it was just another way of hardcoding the size, and it also didn't fix the potential track time truncation either. The problem was that the size calculation was based on the wrong string with regards to proportional fonts. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:34:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:34:21 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one In-Reply-To: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> References: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> Message-ID: <050.73d7bf739d40664cb5fca878d8c9d593@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): And why do we have to do the same thing? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:42:40 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:42:40 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one In-Reply-To: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> References: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> Message-ID: <050.9fb3730a8aea7b2b33927f6de9694cd4@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): Sorry, I sent twice same attach image. This is R5 style. Is there any reason to change? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:42:39 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:42:39 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.6a48192d3a4175bf1d4f6e73a74d4ea7@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by stippi): Ok, I applied the keycodes diff in r25413. I suppose that's not all to make it work though, is it? Thanks so far! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:43:54 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:43:54 -0000 Subject: [Haiku-bugs] [Haiku] #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too In-Reply-To: <041.e42e0e567f26e193d44a2ed83bad8cd2@haiku-os.org> References: <041.e42e0e567f26e193d44a2ed83bad8cd2@haiku-os.org> Message-ID: <050.b7a18b1ece1e0e984ea2e40d583c802c@haiku-os.org> #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too --------------------------------------+------------------------------------- Reporter: stpere | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned Comment: Working on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:53:13 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:53:13 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.44d60ce53719c9e520e2ff822eb46863@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): I think about other two key codes later because I don't face problems yet. Thank you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:56:18 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:56:18 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.3ee1299f88f5da0d36eb6cdbbb41e6d7@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by korli): I'm wondering in which code 0xf3 and 0xf2 are supposed to be used ? We might want to reserve these codes in InterfaceDefs.h -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 13:59:30 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 11:59:30 -0000 Subject: [Haiku-bugs] [Haiku] #2217: Terminal replicant graphic scrolls off the screen In-Reply-To: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> References: <042.fac7f913b38d5ca44c1298e3f4e81700@haiku-os.org> Message-ID: <051.3dc3e70647abc12717302b561e6b6631@haiku-os.org> #2217: Terminal replicant graphic scrolls off the screen ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Same here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:09:03 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:09:03 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.242fd6699fa6a9c8879e2be27a1dcc8c@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): This patch and patch for #2222 (r25413) realize this enhancement. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:14:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:14:43 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.f845c1ed6231da4d7f511b9c0ab72fad@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by cebif): Replying to [comment:3 tqh]: > That UserSetupEnvironment seems to be broken. Has it gone broken when uploading or is that so? Look at end of second line. Yes it is broken I think from looking at it now. It is the same uploaded as on my system both Haiku and BeOSR5.05 Bone. I don't know why it was sensitive to the error (not all times) in Haiku and not in BeOSR5.05 Bone.It looks like a ":" and "A" was missing in that order. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:20:11 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:20:11 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.42d756bb8a29433e7c6ea13de37a894c@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): I used 0xf2/0xf3 which is same as Windows' value. I think that Microsoft selected these value because these value seem to be rarely conflict other key codes. It maybe better to add B_ZENKAKU_HANKAKU and B_KATAKANA_HIRAGANA to InterfaceDefs.h. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:25:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:25:15 -0000 Subject: [Haiku-bugs] [Haiku] #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too In-Reply-To: <041.e42e0e567f26e193d44a2ed83bad8cd2@haiku-os.org> References: <041.e42e0e567f26e193d44a2ed83bad8cd2@haiku-os.org> Message-ID: <050.53cae8768cb1e1ec21e30e0c0bc58af0@haiku-os.org> #2210: [PATCH] Followup of ticket 2170 : Revert button now works for timezones too --------------------------------------+------------------------------------- Reporter: stpere | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: fixed | Platform: All --------------------------------------+------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Applied in r25415. Nice work, thanks a lot and sorry for the delay! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:40:20 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:40:20 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.083c616462ad02deca1d4d7b688729ba@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by korli): I applied in r25416. Could you confirm please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:44:13 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:44:13 -0000 Subject: [Haiku-bugs] [Haiku] #2222: Zenkaku/Hankaku key code in Japanese keymap In-Reply-To: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> References: <041.985d1a703f6c1053fc06a3a08201864d@haiku-os.org> Message-ID: <050.e5d6cb9b97738702fef78cb1a062fbe8@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:52:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:52:05 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.769f02328d5a81cd93f1eb27f8c50e7a@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:4 korli]: > HWindow.cpp, TrackerInitialState.cpp and FontManager.cpp patched May be TrackerInitialState.cpp is forgotten? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 14:57:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 12:57:21 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.dc7390a26f0044b9749ea01b4ad01829@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by tqh): So when you corrected that it works correctly? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 15:24:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 13:24:15 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.7b84d0308141e8d7e39c07fa2ca5f5fd@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): Thank you. But, a bit difference. not {{{ if ((fKeyInfo.modifiers & B_COMMAND_KEY) != 0 && (byte == ' ' || static_cast(byte) == B_ZENKAKU_HANKAKU)) { }}} but {{{ if ((fKeyInfo.modifiers & B_COMMAND_KEY) != 0 && byte == ' ' || static_cast(byte) == B_ZENKAKU_HANKAKU) { }}} because B_ZENKAKU_HANKAKU doesn't need B_COMMAND_KEY. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 15:54:19 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 13:54:19 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.bfb61ca4ccdc499b454ec98f9ab470e6@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r25421. It's better to explicitly use parenthesis for such comparisons :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 16:33:27 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 14:33:27 -0000 Subject: [Haiku-bugs] [Haiku] #2218: Key binding for turning on/off inputh methods (IM) In-Reply-To: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> References: <041.8f83acfac2bd33e2278d6c693f513f7e@haiku-os.org> Message-ID: <050.e1cf2bd7738947600e80e33299bc50a8@haiku-os.org> #2218: Key binding for turning on/off inputh methods (IM) -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Comment (by shinta): Thank you :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 16:37:47 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 14:37:47 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.c3e60c0b36d42f53837c0a37e4c29056@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by ddew): Tried booting 25422 here and I still get bitten by the allocate_compage issue. As I can't readily remove ram to test the ahci bug I'll have to take a raincheck on capturing the log until I can boot Haiku without taking any out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 17:14:17 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 15:14:17 -0000 Subject: [Haiku-bugs] [Haiku] #2213: KDL page fault re-starting tne media server. In-Reply-To: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> References: <042.ffb4bde7e8e81472058e4ebe6cc215d0@haiku-os.org> Message-ID: <051.2ef4d91484430a742ad6dde617e27204@haiku-os.org> #2213: KDL page fault re-starting tne media server. ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by bbjimmy): Replying to [comment:5 mmu_man]: > maybe if you remove one it will work around it meanwhile ? No... still end up in kdl. here is a better image of the stack trace ( different camera .) http://coquilletkd.com/fatelk/haiku/P5090040.JPG -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 18:58:46 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 16:58:46 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one In-Reply-To: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> References: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> Message-ID: <050.7db408f7c56319c7d58d277316e3e71c@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: We're using tabs, and I don't think there is any reason to abandon them when using the left titled look. Give the window a name to make it look better :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 20:33:53 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 18:33:53 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.7551b1e1a1302ca18f3099f632f68220@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by anevilyak): Hi, a minor observation to add to this bug: I looked into this with gdb, and Tracker's desktop window thread was waiting on a port read, which I assume is normal since it should normally wait for app_server messages. After telling it to continue however, it woke up again and the Desktop repainted and worked normally. Any ideas? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 21:07:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 19:07:31 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one In-Reply-To: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> References: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> Message-ID: <050.76d56a18a752fac9db5a62af8053332c@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------------+------------------------------------------ Changes (by koki): * cc: koki (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 21:30:07 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 19:30:07 -0000 Subject: [Haiku-bugs] [Haiku] #2203: [PATCH] Public header files need to be ANSI-compliant In-Reply-To: <043.ce1a7796582fd349a3b430f3c54160d4@haiku-os.org> References: <043.ce1a7796582fd349a3b430f3c54160d4@haiku-os.org> Message-ID: <052.11998bc098e0f7073bc3b14dc82242f6@haiku-os.org> #2203: [PATCH] Public header files need to be ANSI-compliant ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by andreasf): * summary: Public header files need to be ANSI-compliant => [PATCH] Public header files need to be ANSI-compliant Comment: The attached patch depends on #2108 and fixes all posix/ headers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 21:39:38 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 19:39:38 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.a10a0f934358a9bf0ef4e1e5ff0ef22b@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by luroh): Fwiw, the bug does not appear when running haiku.image in (unaccellerated) qemu. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 23:31:24 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 21:31:24 -0000 Subject: [Haiku-bugs] [Haiku] #2203: [PATCH] Public header files need to be ANSI-compliant In-Reply-To: <043.ce1a7796582fd349a3b430f3c54160d4@haiku-os.org> References: <043.ce1a7796582fd349a3b430f3c54160d4@haiku-os.org> Message-ID: <052.2a6be9207d7322fc08683a6588cae09c@haiku-os.org> #2203: [PATCH] Public header files need to be ANSI-compliant ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r25433. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 23:39:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 21:39:05 -0000 Subject: [Haiku-bugs] [Haiku] #2108: [PATCH] Problematic definition of assert macro In-Reply-To: <043.dc5d0e283f22f29022d9f939dfa5cc5d@haiku-os.org> References: <043.dc5d0e283f22f29022d9f939dfa5cc5d@haiku-os.org> Message-ID: <052.3eef9f0942f76b0641e31c4cbe0bf923@haiku-os.org> #2108: [PATCH] Problematic definition of assert macro ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by andreasf): This patch has been committed as part of r25433, so this ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 23:42:51 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 21:42:51 -0000 Subject: [Haiku-bugs] [Haiku] #2199: [PATCH] Typo in r25297 In-Reply-To: <043.eadb6c16c1cc61cadb9e3613f183f473@haiku-os.org> References: <043.eadb6c16c1cc61cadb9e3613f183f473@haiku-os.org> Message-ID: <052.e3dbda391ff172339a3bfae3cfe5f220@haiku-os.org> #2199: [PATCH] Typo in r25297 --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by andreasf): Ping! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 23:51:10 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 21:51:10 -0000 Subject: [Haiku-bugs] [Haiku] #2108: [PATCH] Problematic definition of assert macro In-Reply-To: <043.dc5d0e283f22f29022d9f939dfa5cc5d@haiku-os.org> References: <043.dc5d0e283f22f29022d9f939dfa5cc5d@haiku-os.org> Message-ID: <052.f35a2a531531757c9abaceb7f42575bd@haiku-os.org> #2108: [PATCH] Problematic definition of assert macro ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 10 23:53:19 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 10 May 2008 21:53:19 -0000 Subject: [Haiku-bugs] [Haiku] #2199: [PATCH] Typo in r25297 In-Reply-To: <043.eadb6c16c1cc61cadb9e3613f183f473@haiku-os.org> References: <043.eadb6c16c1cc61cadb9e3613f183f473@haiku-os.org> Message-ID: <052.0a8140aef6efd29b7ef201332692d134@haiku-os.org> #2199: [PATCH] Typo in r25297 --------------------------+------------------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Pong! :-) Fixed in r25436. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 02:18:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 00:18:39 -0000 Subject: [Haiku-bugs] [Haiku] #1109: Kernel module to enable Linux drivers in Haiku In-Reply-To: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> References: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> Message-ID: <057.66ce1819b2bde4ec13b2d32110b5097b@haiku-os.org> #1109: Kernel module to enable Linux drivers in Haiku ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by kaoutsis): Some comments and questions about libuks_and_jfs.diff.zip the questions: a) Is it possible this kind of implementation? (making a wrapper kernel library in order to keep the driver sources untouched) And if so what rules should someone follow? b) Does it really worth the effort? the comments: a) There are a huge number of defines, macros, and inline assembly that make the whole effort a bit difficult :-D b) there are several changes from one version of the linux kernel to another, making the effort, a moving target. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 03:24:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 01:24:53 -0000 Subject: [Haiku-bugs] [Haiku] #1462: via.accelerant and via.driver are missing from the build. In-Reply-To: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> References: <042.590553fa24e408db0b54046a5449c4cd@haiku-os.org> Message-ID: <051.dff328dd133921a8e96600b51935071f@haiku-os.org> #1462: via.accelerant and via.driver are missing from the build. ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Comment (by bbjimmy): Replying to [comment:7 axeld]: > The driver as a whole is really not yet mature enough to be used. > It must not be added to the image by default yet. This is my hardware: North Bridge: VIA - - CPU to PCI Bridge Vendor: 0x1106 - Device: 0x3205 South Bridge: VIA - VT8235 - PCI to ISA Bridge Vendor: 0x1106 - Device: 0x3177 Video Card: VIA - KM400 - VIA Technologies, Inc. VT8378 [S3 UniChrome] Graphics Adapter Vendor: 0x1106 - Device: 0x7205 Sound Card: VIA - VT8233/33A/8235/8237 - AC97 Enhanced Audio Controller Vendor: 0x1106 - Device: 0x3059 Ethernet Card: Accton - SMC EN5030B - 12078a1 107d Vendor: 0x1113 - Device: 0x1211 The driver works ok for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 04:11:19 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 02:11:19 -0000 Subject: [Haiku-bugs] [Haiku] #1779: Media Player Crash Playing mov File In-Reply-To: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> References: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> Message-ID: <049.603dc45967836a6e574c177c066aa5ff@haiku-os.org> #1779: Media Player Crash Playing mov File ---------------------------------------+------------------------------------ Reporter: cebif | Owner: dlmcpaul Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by dlmcpaul): Applied a fix in r25444 metadata size was not being set, causing random data to be passed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 04:12:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 02:12:56 -0000 Subject: [Haiku-bugs] [Haiku] #1779: Media Player Crash Playing mov File In-Reply-To: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> References: <040.db03ce828cf1bb851ae92acbcb7de61a@haiku-os.org> Message-ID: <049.6d02fa67e8bf13d73d0e2a9f297ce2e5@haiku-os.org> #1779: Media Player Crash Playing mov File ---------------------------------------+------------------------------------ Reporter: cebif | Owner: dlmcpaul Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by dlmcpaul): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 03:01:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 01:01:56 -0000 Subject: [Haiku-bugs] [Haiku] #1715: Tracker Deadlock on AppLooper Port In-Reply-To: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> References: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> Message-ID: <052.0afb581cfc7d20c2368c59d3aef16f37@haiku-os.org> #1715: Tracker Deadlock on AppLooper Port -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by anevilyak): Is it possible it's not using the intra-app shortcut because it initializes the BMessenger that it passes to StartWatching by signature rather than by a looper/handler pointer? Bear in mind this code is shared for BFilePanel as well, so it may not necessarily be invoked from Tracker itself, but it seems BMessenger doesn't detect the fact that it's the same app when the signature constructor is used. Perhaps I'm wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 07:46:04 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 05:46:04 -0000 Subject: [Haiku-bugs] [Haiku] #2221: kLeftTitledWindowLook's look is different from R5's one In-Reply-To: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> References: <041.331b29f548ed5f62dea1222de969db88@haiku-os.org> Message-ID: <050.b115f6d9c633464ff0fcaae4c54b5150@haiku-os.org> #2221: kLeftTitledWindowLook's look is different from R5's one ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): Tab (mean title bar?) is short so that it can slide, isn't it? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 11:23:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 09:23:00 -0000 Subject: [Haiku-bugs] [Haiku] #1715: Tracker Deadlock on AppLooper Port In-Reply-To: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> References: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> Message-ID: <052.3643ba0cead2e22e8692530c5e50c610@haiku-os.org> #1715: Tracker Deadlock on AppLooper Port -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by axeld): That can't be the problem; the BMessenger always only resolves to a combination of team and port - it's not responsible for the intra-app short cut, that all happens in BMessage. Also, the problem doesn't seem to happen on BeOS R5 which does not have such a shortcut, it always uses the port. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 11:30:34 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 09:30:34 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) Message-ID: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> #2223: KDL in tty driver (rev. 25445) -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- {{{ vm_soft_fault: va 0xdeadbef3 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xdeadbef3, ip 0x80045773, write 0, user 0, thread 0x24f5 PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbef3, ip 0x80045773 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> kdebug> bt stack trace for thread 9461 "w>Terminal 1" kernel stack: 0x977b4000 to 0x977b8000 user stack: 0x70082000 to 0x700c2000 frame caller :function + offset 977b7730 (+ 48) 80048dab :invoke_debugger_command + 0x00cf 977b7760 (+ 64) 80049b54 :_ParseCommand__16ExpressionParserRi + 0x01f8 977b77a0 (+ 48) 80049546 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 977b77d0 (+ 224) 8004ac68 :evaluate_debug_command + 0x0088 977b78b0 (+ 64) 800478e6 :kernel_debugger_loop__Fv + 0x017a 977b78f0 (+ 48) 80048599 :kernel_debugger + 0x010d 977b7920 (+ 192) 80048481 :panic + 0x0029 977b79e0 (+ 64) 800935a7 :vm_page_fault + 0x00ab 977b7a20 (+ 64) 8009d675 :page_fault_exception + 0x00b1 977b7a60 (+ 12) 800a0d4d :int_bottom + 0x001d (nearest) iframe at 0x977b7a6c (end = 0x977b7ac4) eax 0xdeadbeef ebx 0x90c8d880 ecx 0x0 edx 0x90c8d880 esi 0x1 edi 0x801cc0a8 ebp 0x977b7ad4 esp 0x977b7aa0 eip 0x80045773 eflags 0x10282 vector: 0xe, error code: 0x0 977b7a6c (+ 104) 80045773 :notify_select_events + 0x001b 977b7ad4 (+ 32) 8004581b :notify_select_event + 0x0027 977b7af4 (+ 64) 80045c40 :notify_select_event_pool + 0x005c 977b7b34 (+ 48) 801c5f45 :tty_notify_select_event__FP3ttyUc + 0x0031 977b7b64 (+ 48) 801c5fd1 :tty_notify_if_available__FP3ttyT0b + 0x0085 977b7b94 (+ 48) 801c4ef3 :_._12WriterLocker + 0x0067 977b7bc4 (+ 208) 801c7a1d :tty_write_to_tty_master_unsafe__FP10tty_cookiePCcPUl + 0x0469 977b7c94 (+ 320) 801c7b5d :tty_write_to_tty_master__FP10tty_cookiePCvPUl + 0x0089 977b7dd4 (+ 48) 801c9093 :master_write__FPvxPCvPUl + 0x0027 977b7e04 (+ 128) 80067b20 :devfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x0178 977b7e84 (+ 64) 8007955a :file_write__FP15file_descriptorxPCvPUl + 0x0036 977b7ec4 (+ 80) 80069fe9 :common_user_io__FixPvUlb + 0x017d 977b7f14 (+ 48) 8006a4dc :_user_write + 0x0028 977b7f44 (+ 100) 800a0ec2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x977b7fa8 (end = 0x977b8000) eax 0x78 ebx 0x81aaec ecx 0x700c1c90 edx 0xffff0104 esi 0x22740b edi 0x22740d ebp 0x700c1ccc esp 0x977b7fdc eip 0xffff0104 eflags 0x203 vector: 0x63, error code: 0x0 977b7fa8 (+ 0) ffff0104 700c1ccc (+ 48) 00216e7a <_APP_>:Write__5ShellPCvUl + 0x002e 700c1cfc (+ 80) 0021fa1a <_APP_>:KeyDown__8TermViewPCcl + 0x03b2 700c1d4c (+ 464) 00385ceb :DispatchMessage__7BWindowP8BMessageP8BHandler + 0x0aef 700c1f1c (+ 96) 00389fc4 :task_looper__7BWindow + 0x0270 700c1f7c (+ 48) 002e2ed3 :_task0___7BLooperPv + 0x003f 700c1fac (+ 48) 00795030 :_get_next_team_info + 0x005c (nearest) 700c1fdc (+ 0) 700c1fec 196701:w>Terminal 1_9461_stack at 0x70082000 + 0x3ffec kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 11:32:47 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 09:32:47 -0000 Subject: [Haiku-bugs] [Haiku] #1109: Kernel module to enable Linux drivers in Haiku In-Reply-To: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> References: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> Message-ID: <057.1c72dfbf68adbd4e78d19a755cbfb0aa@haiku-os.org> #1109: Kernel module to enable Linux drivers in Haiku ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): Of course it's possible, it's just not at all feasible. First of all, a better source of drivers would be FreeBSD - the license is just more appealing. Also, in my experience, the code is often cleaner and better written (although often packed with less features). The best reason, however, is what say in your comments: Linux doesn't have a stable kernel API at all. Such an effort would just be a waste of time IMO. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 11:54:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 09:54:02 -0000 Subject: [Haiku-bugs] [Haiku] #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. In-Reply-To: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> References: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> Message-ID: <046.a53674a80d47c5a938a3325da2e7189e@haiku-os.org> #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. ----------------------------------+----------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Translators | Version: R1 development Resolution: | Platform: x86 ----------------------------------+----------------------------------------- Comment (by stippi): Axel, it's entering an infinite loop in convert_exif_to_message() and parse_tiff_directory(). {{{ fcffa7a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffa7e0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffa820 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffa860 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffa8a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffa8e0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffa920 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffa960 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffa9a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffa9e0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaa20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffaa60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaaa0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffaae0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffab20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffab60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaba0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffabe0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffac20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffac60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaca0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcfface0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffad20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffad60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffada0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffade0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffae20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffae60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaea0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffaee0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffaf20 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffaf60 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffafa0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffafe0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb020 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb060 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb0a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb0e0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb120 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb160 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb1a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb1e0 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb220 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb260 e4dd931a parse_tiff_directory(TReadHelper &, long long, BMessage &, convert_tag const *, unsigned long) + 000000fa fcffb2a0 e4dd943c parse_tiff_directory(TReadHelper &, BMessage &, convert_tag const *, unsigned long) + 000000ac fcffb2e0 e4dd95d2 convert_exif_to_message(BPositionIO &, BMessage &, convert_tag const *, unsigned long) + 0000017e fcffb370 e4dd9659 convert_exif_to_message(BPositionIO &, BMessage &) + 00000029 fcffb3a0 e4ddd32c Decompress(BPositionIO *, BPositionIO *, BMessage *, __jmp_buf_tag const (*)[1]) + 00000154 fcffb730 e4ddc979 Translate + 000000b9 fcffb780 ec5e1f12 BTranslatorRoster::Translate(BPositionIO *, translator_info const *, BMessage *, BPositionIO *, unsigned long, unsigned long, char const *) + 00000142 fcffb9b4 80011e11 ShowImageView::SetImage(entry_ref const *) + 000001d5 fcffbd80 8001a08d ShowImageWindow::ShowImageWindow(entry_ref const *, BMessenger const &) + 00000559 fcffbe64 80010278 ShowImageApp::Open(entry_ref const *) + 00000038 fcffbe8c 800101e1 ShowImageApp::RefsReceived(BMessage *) + 000000ad fcffbec4 ec16916c BApplication::DispatchMessage(BMessage *, BHandler *) + 00000494 fcffc0e4 ec171a19 BLooper::task_looper(void) + 00000275 fcffc140 ec16740c BApplication::Run(void) + 00000068 fcffc154 8000fa90 main + 0000003c fcffc34c 8000f924 _start + 00000060 ShowImage: }}} Have not looked at the code yet, but it is 100% reproducable, also in ZETA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 12:33:02 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 10:33:02 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.2d44ba86e6e1f5fb487962f9037b336c@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * owner: axeld => bonefish * component: - General => Drivers/TTY -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 13:44:23 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 11:44:23 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.c4036c9ef923bd10fa31d2ebd6d113bc@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by kaliber): Is it a duplicate of bug #2189? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 13:53:08 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 11:53:08 -0000 Subject: [Haiku-bugs] [Haiku] #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. In-Reply-To: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> References: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> Message-ID: <046.83c7efbd732fe0cbe9a4eef9e978dbd2@haiku-os.org> #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. ----------------------------------+----------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Add-Ons/Translators | Version: R1 development Resolution: | Platform: x86 ----------------------------------+----------------------------------------- Changes (by axeld): * status: new => assigned * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 13:59:18 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 11:59:18 -0000 Subject: [Haiku-bugs] [Haiku] #2029: KDL (page fault) in network stack linked list code when quitting Firefox (closing socket) In-Reply-To: <041.bd98a059cd6efae80901753a7f223bf9@haiku-os.org> References: <041.bd98a059cd6efae80901753a7f223bf9@haiku-os.org> Message-ID: <050.42e2e81dddc878951f9c9bcf943f598e@haiku-os.org> #2029: KDL (page fault) in network stack linked list code when quitting Firefox (closing socket) -------------------------------------+-------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by kaliber): Maybe it's related to the bug #2189? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 14:32:04 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 12:32:04 -0000 Subject: [Haiku-bugs] [Haiku] #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. In-Reply-To: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> References: <037.73bff6d34aa7b20f261eee716f600649@haiku-os.org> Message-ID: <046.004fbee6b18966c8bbcb6467a79d7c38@haiku-os.org> #2206: ShowImage (JPEGTranslator) crashes while reading jpeg file. ----------------------------------+----------------------------------------- Reporter: mt | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Add-Ons/Translators | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------------+----------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: The EXIF data is corrupted in those files - fixed in r25447. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 14:58:25 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 12:58:25 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.d9078ddf985f9eabe90e4bf60c419569@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by bonefish): Please give the revision number and the circumstances under which that happened. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 15:02:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 13:02:44 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.7786f4ece7425ab5d959c9b390f92e18@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by cebif): Replying to [comment:5 tqh]: > So when you corrected that it works correctly? Yes, I have retested with corrections to UserSetupEnvironment and it has not crashed at startup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 16:33:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 14:33:52 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.6656f506a127c7d64fcc080d0adec76f@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by tqh): This bug can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 16:34:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 14:34:26 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.66d748e0d46e61205e8da1f1e7b5934b@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaliber): Replying to [comment:2 bonefish]: > Please give the revision number and the circumstances under which that happened. Please read the title again - revision 25445 :) I was starting another terminal window (Ctrl-N) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 16:45:53 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 14:45:53 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.9708d180cd62a1bbceed1fd91523c315@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by stippi): Actually, this hints to a problem in the runtime loader, if all it takes is a corrupt PATH variable to trigger a kernel panic under certain conditions. So I would leave this bug open. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 17:47:17 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 15:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.a4b5f805a563a92ba2f86a4e193a0d6f@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by tqh): Yes, although I saw it is a different bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 18:31:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 16:31:26 -0000 Subject: [Haiku-bugs] [Haiku] #1965: No Shell Prompt In Terminal In-Reply-To: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> References: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> Message-ID: <052.203af6926124efd831a2b38527d49349@haiku-os.org> #1965: No Shell Prompt In Terminal ------------------------+--------------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r25452. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 18:47:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 16:47:42 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.57cdcccc13993b5c04c00475440cdecc@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by bonefish): Replying to [comment:3 kaliber]: > Replying to [comment:2 bonefish]: > > Please give the revision number and the circumstances under which that happened. > Please read the title again - revision 25445 :) Oh, sorry, totally overlooked that. BTW, it's nicer to have the revision number in the description and prefixed with "r" (r25445), so that Trac automatically hyperlinks it to the revision. > I was starting another terminal window (Ctrl-N) Tried to reproduce it, but without success so far. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 19:07:33 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 17:07:33 -0000 Subject: [Haiku-bugs] [Haiku] #2223: KDL in tty driver (rev. 25445) In-Reply-To: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> References: <042.efc184f14cee43f39eab5f17406dea3a@haiku-os.org> Message-ID: <051.e3ad153a74e006496d2e7f9ecf6d36c6@haiku-os.org> #2223: KDL in tty driver (rev. 25445) --------------------------+------------------------------------------------- Reporter: kaliber | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/TTY | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaliber): > > I was starting another terminal window (Ctrl-N) > > Tried to reproduce it, but without success so far. I also cannot reproduce it, sorry. I try to better describe situation. I had 2 open terminals: 1. Compiling something (using autotools) and redirecting an output to the file.txt 2. tail -f file.txt -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 21:28:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 19:28:30 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.07ac0472f8c65aa53c3920ba8201a65d@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): comments on src_bin_desklink_desklink.cpp.diff: * the usual find_directory() fix * i took the freedom, to add a 'About desklink...' menu item to the pop up menu. But i used the asynchronous Go() version (with the NULL argument); The synchronous version ate all the cpu, but i don't know if that is a bug, since the alert was inside the MessageReceived() loop. The asynchronous Go() version seems to work fine, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 21:40:10 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 19:40:10 -0000 Subject: [Haiku-bugs] [Haiku] #1109: Kernel module to enable Linux drivers in Haiku In-Reply-To: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> References: <048.4cd3b881c742804b5662d46eb79be2be@haiku-os.org> Message-ID: <057.ec4a1561cdea086ecd9c8e7f8df99ce2@haiku-os.org> #1109: Kernel module to enable Linux drivers in Haiku ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by kaoutsis): Replying to [comment:4 axeld]: > ...Such an effort would just be a waste of time IMO. Ok, thanks for looking into this; i agree. I am relieved now :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 22:47:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 20:47:56 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.03017349af24fed59e35f0645fa67daf@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by cebif): Replying to [comment:7 cebif]: > Replying to [comment:5 tqh]: > > So when you corrected that it works correctly? > Yes, I have retested with corrections to UserSetupEnvironment and it has not crashed at startup. I spoke too soon. It is still crashing. It just needed some more tests to find out; after I started Firefox from first booting Haiku this morning. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 23:00:40 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 21:00:40 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.92dd3804f75850dec5fed8703e6bcf53@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by cebif): It is still crashing (not everytime) even with the UserSetupEnvironment from Bebits directly copied here without any alteration, to show the literal path. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 11 23:16:01 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 21:16:01 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.39b1a920288598b426efcb548d315100@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by tqh): Same type of backtrace? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 00:57:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 22:57:09 -0000 Subject: [Haiku-bugs] [Haiku] #2064: libMicro port In-Reply-To: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> References: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> Message-ID: <052.23c3f7bce161d0559d76d806aa5e84e9@haiku-os.org> #2064: libMicro port --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_tests_system_benchmarks_libMicro_Jamfile.diff: * Allow the mutex and the pthread_create libMicro benchmarks run for real. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 01:23:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 23:23:11 -0000 Subject: [Haiku-bugs] [Haiku] #2100: the libmicro test program mallocT2_100k blocks In-Reply-To: <043.e2c854c4a83cc8f6156def960327cf35@haiku-os.org> References: <043.e2c854c4a83cc8f6156def960327cf35@haiku-os.org> Message-ID: <052.49a1fc8d6ce0f37355321061c99da589@haiku-os.org> #2100: the libmicro test program mallocT2_100k blocks ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): r25459: same behavior as previous -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 01:35:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 23:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #2224: [Terminal] doesn't respect tabs when pasting a text in the prompt. Message-ID: <043.756721bdcd2108c1c2add7e0619455dc@haiku-os.org> #2224: [Terminal] doesn't respect tabs when pasting a text in the prompt. -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- * Copy a text that include inside it one or more tabs. * Paste that text to the terminal's prompt. Tab(s) are missing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 01:37:16 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 11 May 2008 23:37:16 -0000 Subject: [Haiku-bugs] [Haiku] #2224: [Terminal] doesn't respect tabs when pasting a text in the prompt. In-Reply-To: <043.756721bdcd2108c1c2add7e0619455dc@haiku-os.org> References: <043.756721bdcd2108c1c2add7e0619455dc@haiku-os.org> Message-ID: <052.a794d4cd15bcb58ec8a47ca7315e70c9@haiku-os.org> #2224: [Terminal] doesn't respect tabs when pasting a text in the prompt. ------------------------------------+--------------------------------------- Reporter: kaoutsis | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by kaoutsis): * owner: axeld => jackburton * component: - General => Applications/Terminal Comment: revision is r25459 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 02:06:20 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 00:06:20 -0000 Subject: [Haiku-bugs] [Haiku] #2124: the libmicro test program connection fails In-Reply-To: <043.6322618a81e7a71982ef298cd2b8164b@haiku-os.org> References: <043.6322618a81e7a71982ef298cd2b8164b@haiku-os.org> Message-ID: <052.67259a1a0c7331e429c38a95f0273284@haiku-os.org> #2124: the libmicro test program connection fails ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): r25459: the attached connection-output is no longer valid. New behavior: the program runs and after ~10 seconds prints the message: benchmark:accept: Operation timed out and needs ctl+c to stop. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 02:17:33 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 00:17:33 -0000 Subject: [Haiku-bugs] [Haiku] #2128: loop consumer kernel thread has very high cpu usage In-Reply-To: <043.3e575fbe404959ac85d468d3a870a548@haiku-os.org> References: <043.3e575fbe404959ac85d468d3a870a548@haiku-os.org> Message-ID: <052.3eb2d5b002fa11ce1311d86072d7aec0@haiku-os.org> #2128: loop consumer kernel thread has very high cpu usage ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): r25459: it's fixed! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 03:08:33 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 01:08:33 -0000 Subject: [Haiku-bugs] [Haiku] #2226: unmounting a volume, haiku freezes Message-ID: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> #2226: unmounting a volume, haiku freezes -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r25459 Either from tracker, either from terminal. Tested with two different volumes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 02:51:01 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 00:51:01 -0000 Subject: [Haiku-bugs] [Haiku] #2225: [vlc] can not longer play a single video stream Message-ID: <043.dd3d57c576702d601b589fd3e4cee609@haiku-os.org> #2225: [vlc] can not longer play a single video stream -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r25459, * tested with vlc that comes with the optional package. * when starting play video streams from internet goes immediately to the debugger: see attached gdb.txt * i remember that 6 months ago, most of these streams (internet tv stations) played smoothly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 09:09:30 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 07:09:30 -0000 Subject: [Haiku-bugs] [Haiku] #1965: No Shell Prompt In Terminal In-Reply-To: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> References: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> Message-ID: <052.9b9592901963b7383b1fc8be87369ba4@haiku-os.org> #1965: No Shell Prompt In Terminal ------------------------+--------------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): Replying to [comment:1 bonefish]: > Fixed in r25452. The fix is nice et all, but maybe we could at the same time delay the SIGWINCH in Terminal, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 09:32:34 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 07:32:34 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.6ff70670ce7b468a8e9afc63676b8c3f@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by jackburton): Replying to [comment:5 luroh]: > Fwiw, the bug does not appear when running haiku.image in (unaccellerated) qemu. It does here (unaccelerated qemu under ubunty Hardy) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 10:41:53 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 08:41:53 -0000 Subject: [Haiku-bugs] [Haiku] #2128: loop consumer kernel thread has very high cpu usage In-Reply-To: <043.3e575fbe404959ac85d468d3a870a548@haiku-os.org> References: <043.3e575fbe404959ac85d468d3a870a548@haiku-os.org> Message-ID: <052.314f5a6f1862a507015a0c99a7751165@haiku-os.org> #2128: loop consumer kernel thread has very high cpu usage -------------------------------------+-------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by axeld): * priority: normal => critical * resolution: => fixed * status: new => closed * component: - General => Network & Internet/TCP * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 12:00:56 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 10:00:56 -0000 Subject: [Haiku-bugs] [Haiku] #2064: libMicro port In-Reply-To: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> References: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> Message-ID: <052.2f6211841e6dfb73d766457e714c66c7@haiku-os.org> #2064: libMicro port --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by korli): Replying to [comment:12 kaoutsis]: > src_tests_system_benchmarks_libMicro_Jamfile.diff: > * Allow the mutex and the pthread_create libMicro benchmarks > run for real. Applied in r25460. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 12:33:33 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 10:33:33 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.12457029d7f3d2a388db5849349ea085@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by korli): Applied desklink.cpp.diff in r25462. I factorized the alert code and change a few things. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 13:38:04 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 11:38:04 -0000 Subject: [Haiku-bugs] [Haiku] #2226: unmounting a volume, haiku freezes In-Reply-To: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> References: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> Message-ID: <052.a09769e6e81a2db928b484549d14f506@haiku-os.org> #2226: unmounting a volume, haiku freezes ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by korli): Works here with r25463. Could you check please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 13:38:35 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 11:38:35 -0000 Subject: [Haiku-bugs] [Haiku] #2061: Installer button always shows "Begin" In-Reply-To: <042.aba83a0e9b67deba2eedc12ad92797fe@haiku-os.org> References: <042.aba83a0e9b67deba2eedc12ad92797fe@haiku-os.org> Message-ID: <051.4bead26169e716b87b6a03a2e4afad40@haiku-os.org> #2061: Installer button always shows "Begin" -------------------------------------+-------------------------------------- Reporter: scottmc | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Platform: All -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r25466. I replaced the call to QuitRequested() with a PostMessage(B_QUIT_REQUESTED). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 13:56:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 11:56:49 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.d505cc7126bc166eab2d402fef09c6d7@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by stippi): Still with us in r25463. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:02:00 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:02:00 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. Message-ID: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. --------------------------+------------------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | --------------------------+------------------------------------------------- My computer has a JMicron controller that has SATA/PATA ports. I have one SATA HD connected to one of the SATA ports and a 500 GH HD and a DVD-RW drive connected to the PATA port. The SATA HD is detected and works well but the devices connected to the PATA controller are not. For example, when trying to boot Haiku from the PATA HD, it starts booting and then fails because it can not find the boot device. When booting it from the SATA HD, I noticed this in the syslog: KERN: ahci: ahci_scan_bus, cookie 0x9100ce40 KERN: ahci: no device present on port 0 Last message repeated 1 time KERN: ahci: no device present on port 1 Last message repeated 1 time These messages probably refer to the PATA controller (only 2 ports) but although it does not find devices, there *ARE* devices attached (and they work under Windows and under Linux). Full syslog attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:11:20 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:11:20 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. In-Reply-To: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> References: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> Message-ID: <047.b462e30caa06130bb058588e58f47b53@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. ---------------------------+------------------------------------------------ Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): Some things I noticed that may or may not be usefull: 1 - My BIOS has an option to configure PATA devices as AHCI or IDE. Either option results in exactly the same problem. 2 - Linux always configures the devices as AHCI, it seems (they show up as sdX devices). 3 - Dunno if it matter but both devices jumpers are set to cable select, which means there is no explicitly configured master/slave. 4 - Even if I disconnect the IDE HD, the DVD drive is still not detected. Didn't try disconnecting only the DVD drive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:12:36 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:12:36 -0000 Subject: [Haiku-bugs] [Haiku] #2226: unmounting a volume, haiku freezes In-Reply-To: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> References: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> Message-ID: <052.4dd84274cbdb8a02092cdf97b6d3a128@haiku-os.org> #2226: unmounting a volume, haiku freezes ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): Replying to [comment:1 korli]: > Works here with r25463. Could you check please ? Yes, it's fixed, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:14:40 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:14:40 -0000 Subject: [Haiku-bugs] [Haiku] #947: Konatu Tohaba isn't recognized as monospaced font In-Reply-To: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> References: <045.abb08586fb8bdea6a983fb0fd698e249@haiku-os.org> Message-ID: <054.72666d16ea7162e2115559d0b4123a77@haiku-os.org> #947: Konatu Tohaba isn't recognized as monospaced font -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All -------------------------+-------------------------------------------------- Comment (by jackburton): Replying to [comment:6 koki]: > According to the definition of "monospaced font" in the FontForge FAQ... > > http://fontforge.sourceforge.net/faq.html#monospace > > ...for a font to be considered monospaced, all glyphs must have the same width. By this definition, Japanese fonts (which include single-width and double-width glyphs) are not monospaced. Now I understand some of the code I found (and removed) in Terminal (which was originally written by japanese developers). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:22:22 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:22:22 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal colors as replicant goto black on white even if selected otherwise In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.735d08185afd5bb2e48da879556d400b@haiku-os.org> #2215: Terminal colors as replicant goto black on white even if selected otherwise ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by jackburton): All settings are ignored when terminal is a replicant. This happens because settings are saved/loaded at the window level, not at the TermView level. This was done because I thought one could want to use different settings when embedding the TermView either directly or via replicant. But maybe this wasn't a good idea... maybe I should move settings again into TermView. Thoughts ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:43:05 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:43:05 -0000 Subject: [Haiku-bugs] [Haiku] #2228: vm_page_fault after Media Restart Message-ID: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> #2228: vm_page_fault after Media Restart -----------------------+---------------------------------------------------- Reporter: franxico | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- I'm using VMWare, Haiku R25312, I could reproduce this crash: 1- Set sound event for name said in Vision 2- After your name is said, sound goes crappy 3- Try to restart the Media 4- KDL I can't provide any bt, because it hangs in KDL. All I have is: PANIC: vm_page_fault: unhandled page fault in kernel space at 0x6972646c, ip 0x92bb8882 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 14:51:36 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 12:51:36 -0000 Subject: [Haiku-bugs] [Haiku] #2090: [PATCH] Suppress runtime_loader error message "cannot open file" In-Reply-To: <043.c54280676a44bf468639dc3f01254ef0@haiku-os.org> References: <043.c54280676a44bf468639dc3f01254ef0@haiku-os.org> Message-ID: <052.72b58054bb59b5429f8fa504e002443f@haiku-os.org> #2090: [PATCH] Suppress runtime_loader error message "cannot open file" ------------------------------------+--------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Platform: x86 ------------------------------------+--------------------------------------- Comment (by andreasf): My patch has been obsoleted with r25437. Please close the ticket as fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 15:01:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 13:01:42 -0000 Subject: [Haiku-bugs] [Haiku] #2226: unmounting a volume, haiku freezes In-Reply-To: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> References: <043.aef143ea5957b0d74ad16318f952c3c1@haiku-os.org> Message-ID: <052.05850ce3e02a28e052aa86b3a33bf343@haiku-os.org> #2226: unmounting a volume, haiku freezes ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: fixed for real in r25467. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 15:02:51 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 13:02:51 -0000 Subject: [Haiku-bugs] [Haiku] #2090: [PATCH] Suppress runtime_loader error message "cannot open file" In-Reply-To: <043.c54280676a44bf468639dc3f01254ef0@haiku-os.org> References: <043.c54280676a44bf468639dc3f01254ef0@haiku-os.org> Message-ID: <052.491bc3891b7de682a15b492ffa16defa@haiku-os.org> #2090: [PATCH] Suppress runtime_loader error message "cannot open file" ------------------------------------+--------------------------------------- Reporter: andreasf | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: fixed | Platform: x86 ------------------------------------+--------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 15:04:08 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 13:04:08 -0000 Subject: [Haiku-bugs] [Haiku] #1965: No Shell Prompt In Terminal In-Reply-To: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> References: <043.54ec17eb4d0003de0d41f8c19b3b10d9@haiku-os.org> Message-ID: <052.bc8c0fda532434293157dacc07cb2496@haiku-os.org> #1965: No Shell Prompt In Terminal ------------------------+--------------------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): Replying to [comment:2 jackburton]: > Replying to [comment:1 bonefish]: > > Fixed in r25452. > > The fix is nice et all, but maybe we could at the same time delay the SIGWINCH in Terminal, though. You mean wait with setting the tty window size? I don't know, why we should do that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 15:04:17 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 13:04:17 -0000 Subject: [Haiku-bugs] [Haiku] #2228: vm_page_fault after Media Restart In-Reply-To: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> References: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> Message-ID: <052.95890a8663e83778198d2f579a39df6f@haiku-os.org> #2228: vm_page_fault after Media Restart -----------------------------------+---------------------------------------- Reporter: franxico | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * owner: axeld => marcusoverhagen * component: - General => Servers/media_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 17:05:30 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 15:05:30 -0000 Subject: [Haiku-bugs] [Haiku] #1715: Tracker Deadlock on AppLooper Port In-Reply-To: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> References: <043.72040e8497207d23ce07363ece6d7100@haiku-os.org> Message-ID: <052.7e40511a09cd3aa550601fd56aa70a8d@haiku-os.org> #1715: Tracker Deadlock on AppLooper Port -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by anevilyak): Replying to [comment:7 axeld]: > That can't be the problem; the BMessenger always only resolves to a combination of team and port - it's not responsible for the intra-app short cut, that all happens in BMessage. > > Also, the problem doesn't seem to happen on BeOS R5 which does not have such a shortcut, it always uses the port. In that case it seems we have two bugs here. That having been said, I'm noticing some relatively odd behavior on this one with the debugger. The bug consistently happens here in the latest revs on real hardware, and when I break into it with the debugger, it's waiting to read from the port, which shouldn't be the case if the port is full of waiting data. However, when I then tell it 'continue', it catches a SIGTRAP again for some reason. continue a second time, and suddenly the thread wakes up and all is normal (i.e. Desktop repaints again, etc.). Is it possible it's hitting some edge case/race with respect to waking up the thread when new data is ready for read on the port? With respect to the other issue (intra-app shortcut), the only way I could see this failing is if BPrivate::current_team() is not resolving to the correct team ID at that point, which wouldn't really make sense though since I thought get_thread_info() should return correct data more or less as soon as the thread is created. Will see if I can add some traces and debug this more since I have it 100% reproducible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 17:17:27 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 15:17:27 -0000 Subject: [Haiku-bugs] [Haiku] #2228: vm_page_fault after Media Restart In-Reply-To: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> References: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> Message-ID: <052.d4dd31c8a7542468cc017256f6efc3ca@haiku-os.org> #2228: vm_page_fault after Media Restart -----------------------------------+---------------------------------------- Reporter: franxico | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: duplicate | Platform: x86 -----------------------------------+---------------------------------------- Changes (by korli): * status: new => closed * resolution: => duplicate Comment: dup of #2213 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 19:20:33 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 17:20:33 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.2f012527e58af3ea01736c34d483117b@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by luroh): Replying to [comment:6 jackburton]: > Replying to [comment:5 luroh]: > > Fwiw, the bug does not appear when running haiku.image in (unaccellerated) qemu. > It does here (unaccelerated qemu under ubunty Hardy) It does here too now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 19:45:53 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 17:45:53 -0000 Subject: [Haiku-bugs] [Haiku] #2228: vm_page_fault after Media Restart In-Reply-To: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> References: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> Message-ID: <052.a98998e0a5801b5b38e317985bf172c9@haiku-os.org> #2228: vm_page_fault after Media Restart -----------------------------------+---------------------------------------- Reporter: franxico | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: duplicate | Platform: x86 -----------------------------------+---------------------------------------- Comment (by umccullough): "hangs in KDL" - is that because you're using the vmware images provided by Haikuware and they have the vmware video driver enabled? If so, then you should probably remind Karl that the driver doesn't work in KDL and should definitely be removed from his images for testing purposes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 19:51:31 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 17:51:31 -0000 Subject: [Haiku-bugs] [Haiku] #2228: vm_page_fault after Media Restart In-Reply-To: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> References: <043.918399df6316c99e3d1d097b4deb4666@haiku-os.org> Message-ID: <052.b829c5f285752bb90e08c9caae9b38d9@haiku-os.org> #2228: vm_page_fault after Media Restart -----------------------------------+---------------------------------------- Reporter: franxico | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/media_server | Version: R1 development Resolution: duplicate | Platform: x86 -----------------------------------+---------------------------------------- Comment (by franxico): It worked after some tries. It is very very slow, but worked anyway, so I could get the sc. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 20:38:34 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 18:38:34 -0000 Subject: [Haiku-bugs] [Haiku] #1043: add encoding support to our Media Kit In-Reply-To: <045.20519a0fa708b5dcd6c6fbef988e9c71@haiku-os.org> References: <045.20519a0fa708b5dcd6c6fbef988e9c71@haiku-os.org> Message-ID: <054.3538a0a6612fe3985ad90926438947bd@haiku-os.org> #1043: add encoding support to our Media Kit -----------------------------+---------------------------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by mauricek): * cc: mauricek (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 20:44:45 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 18:44:45 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.f599e9615c3e1edcc9b52fa3bf4b66ed@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try again with r25476+ and provide the usual serial output ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 22:31:48 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 20:31:48 -0000 Subject: [Haiku-bugs] [Haiku] #711: [app_server] extremely high cpu usage on replicant movement In-Reply-To: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> References: <040.63633f11a31b470fd6b71f750a6bb4c7@haiku-os.org> Message-ID: <049.0aeb0010314b81b9b67df2b4259f320d@haiku-os.org> #711: [app_server] extremely high cpu usage on replicant movement ---------------------------------+------------------------------------------ Reporter: diver | Owner: stippi Type: bug | Status: assigned Priority: low | Milestone: R1 Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => assigned Comment: The problem is that app_server does not implement "rect tracking". It always uses transparent bitmaps to attach anything to the mouse cursor, so this is where the high CPU usage is coming from. This bug will be resolved when rect tracking is implemented. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 22:36:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 20:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #2216: KDL when attempting to open Audio CD in tracker In-Reply-To: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> References: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> Message-ID: <051.4f9c40b1e41e6bf3d9e07900adee6b98@haiku-os.org> #2216: KDL when attempting to open Audio CD in tracker ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by axeld): * component: - General => File Systems/ISO 9660 Comment: What audio CD have you been trying to use, or is the result the same with different ones? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 22:52:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 20:52:58 -0000 Subject: [Haiku-bugs] [Haiku] #2216: KDL when attempting to open Audio CD in tracker In-Reply-To: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> References: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> Message-ID: <051.c258479fda646271056b50bdf0645fe4@haiku-os.org> #2216: KDL when attempting to open Audio CD in tracker ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by scottmc): This might be being caused by a CD-ROM drive that is about to die, as it's been acting the the last couple of weeks. I'll try the CD in a different computer on vmware and see if it follows the CD disc or the drive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 23:24:53 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 21:24:53 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.a916f604a9ba6c017394afba80abac4d@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Comment (by scottmc): Any progress on this one? If I were to try using the alternate IDE driver where would that be located? I have a build system setup and can make the changes, just let me know what to try out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 12 23:50:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 12 May 2008 21:50:19 -0000 Subject: [Haiku-bugs] [Haiku] #1444: SATA testing on real hardware - fails to boot In-Reply-To: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> References: <042.6d42e64b1d90ed4f4f92d24220c524df@haiku-os.org> Message-ID: <051.43866418d2dd0c38ec2aadb2f74e3dcc@haiku-os.org> #1444: SATA testing on real hardware - fails to boot ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: x86 ---------------------------+------------------------------------------------ Changes (by umccullough): * cc: axeld (removed) Comment: (removing axel from cc since he gets duplicates that way) I've successfully used the ata bus manager in place of ide to fix my SATA boot issues: In order to switch to the replacement "ata" bus manager rather than the "ide" - you go into src/add-ons/kernel/bus_managers/Jamfile and change where it specifies "ide" to "ata" in the SubInclude's. Since the jam target is the same name, nothing else needs to change and you can just rebuild the haiku image to have the "ata" replace the old one. It is slower (only supports PIO mode currently), and doesn't seem to support ATAPI devices yet (so, no CDROMs) - but it does seem to fix several problems where SATA doesn't work. Note: sometimes you do have to wait a while for it to work still - it might appear to be hung, but mine usually works within 30-60 seconds. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 09:16:31 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 07:16:31 -0000 Subject: [Haiku-bugs] [Haiku] #1846: Media does not retain preferred settings In-Reply-To: <040.fd3b9bce9062b192a89fdea564992559@haiku-os.org> References: <040.fd3b9bce9062b192a89fdea564992559@haiku-os.org> Message-ID: <049.ac619601623b961dd55c621c1af69dc9@haiku-os.org> #1846: Media does not retain preferred settings --------------------------------+------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by mauricek): * cc: mauricek (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 09:17:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 07:17:53 -0000 Subject: [Haiku-bugs] [Haiku] #1846: Media does not retain preferred settings In-Reply-To: <040.fd3b9bce9062b192a89fdea564992559@haiku-os.org> References: <040.fd3b9bce9062b192a89fdea564992559@haiku-os.org> Message-ID: <049.cf46e3f0fe5f6d99864b9c706476a793@haiku-os.org> #1846: Media does not retain preferred settings --------------------------------+------------------------------------------- Reporter: cebif | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by mauricek): Is this one still valid? I cannot reproduce it anymore and remember that I did some work related to this quite some time ago. Could you please verify that this bug has been resolved by now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 10:06:28 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 08:06:28 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.3c62169795a72b9a0155c18e228fd723@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): Serial output is in attachment 'serial25477'; the behaviour's unchanged. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 10:52:40 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 08:52:40 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.ae3b24d7b49417f310832f3d9a1e74fa@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by korli): * status: new => assigned Comment: I need to patch the ac97 code. I hope to do so soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 12:56:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 10:56:53 -0000 Subject: [Haiku-bugs] [Haiku] #2070: Terminal displays artifacts in bottom In-Reply-To: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> References: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> Message-ID: <052.a4cafb6e3995cc8262e92aece06ccc06@haiku-os.org> #2070: Terminal displays artifacts in bottom ------------------------------------+--------------------------------------- Reporter: andreasf | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: x86 ------------------------------------+--------------------------------------- Comment (by jackburton): Do I have to do something particular to reproduce it ? I can't see any artifact. Are you running in double buffered mode ? (IOW: vesa or 16 bit depth by chance ?) I am. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 13:09:35 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 11:09:35 -0000 Subject: [Haiku-bugs] [Haiku] #2070: Terminal displays artifacts in bottom In-Reply-To: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> References: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> Message-ID: <052.d385c6f6854634b29851950d62b6921e@haiku-os.org> #2070: Terminal displays artifacts in bottom ------------------------------------+--------------------------------------- Reporter: andreasf | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: x86 ------------------------------------+--------------------------------------- Comment (by stippi): For example, execute "listarea", then use the scrollbar to scroll all the way to the bottom of the Terminal view. There is a "clean area" below the last output. But then, at the very bottom, there are some random fragments from the output further up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 14:24:42 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 12:24:42 -0000 Subject: [Haiku-bugs] [Haiku] #2070: Terminal displays artifacts in bottom In-Reply-To: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> References: <043.3b0a6ce95705c54e89d5ef7e3dcc35db@haiku-os.org> Message-ID: <052.73b83e0b5256bd1f1ead660f4f891503@haiku-os.org> #2070: Terminal displays artifacts in bottom ------------------------------------+--------------------------------------- Reporter: andreasf | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: x86 ------------------------------------+--------------------------------------- Comment (by jackburton): Thanks, I can reproduce it this way. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 16:06:49 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 14:06:49 -0000 Subject: [Haiku-bugs] [Haiku] #2216: KDL when attempting to open Audio CD in tracker In-Reply-To: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> References: <042.d957104a8af92ce330d732582c779a7b@haiku-os.org> Message-ID: <051.fb7f0f3043836128a6328dd1d7434ba2@haiku-os.org> #2216: KDL when attempting to open Audio CD in tracker ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by scottmc): I just tried it on a second computer and it also dropped into KDL when trying to open the CD. I tried it with a couple different CDs, same thing on both of them. Foo Fighters - In Your Honor, this is one that had sunncomm's protection on it but that shouldn't matter here. The other was Blink-182 self titled CD, I see that this one is labeled as an "enhanced CD". I can try some others to see if it's all CDs or if it's just ones that have hidden extra content. Anyone else setup their vmware images to access a CD? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 17:37:06 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 15:37:06 -0000 Subject: [Haiku-bugs] [Haiku] #61: Build POSIX test suite for haiku In-Reply-To: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> References: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> Message-ID: <058.9b01e3591ea481d2a508ea68059613cf@haiku-os.org> #61: Build POSIX test suite for haiku -----------------------------+---------------------------------------------- Reporter: andrewbachmann | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kaoutsis): Comments on posix-testsuite.diff: * made the output easier to observe; * added the sigsuspend_6-1 test to the package; * made the fork_3-1 test return when it fails; * added output to the pthread_once tests; * other minor cosmetic changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 18:32:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 16:32:10 -0000 Subject: [Haiku-bugs] [Haiku] #1639: Sometimes the posix test fork_3-1 fails. In-Reply-To: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> References: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> Message-ID: <052.3840d3ee599915f585568db5cb1c8798@haiku-os.org> #1639: Sometimes the posix test fork_3-1 fails. --------------------------------+------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by kaoutsis): * summary: the posix test fork_3-1 always fails. => Sometimes the posix test fork_3-1 fails. Comment: r25481, back to 'Sometimes' :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 18:44:11 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 16:44:11 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.c863b6a5fbeb013f87b97b6981cc39f8@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_system_kernel_main.cpp.diff: updated to r25481 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 13 19:40:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 13 May 2008 17:40:48 -0000 Subject: [Haiku-bugs] [Haiku] #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders In-Reply-To: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> References: <042.5b336a58ca3a611a4e39f9649efe9b34@haiku-os.org> Message-ID: <051.380df4a9df0589f6cf7b7b7a7ece7b2e@haiku-os.org> #1420: Copying a folder with the same name as an existing folder should offer the option to merge both folders -----------------------------------+---------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by scottmc): Just noticed this on BeTips server: http://betips.net/1997/09/09/dont-overwrite-existing-folders/ So it was "supposed" to be changed in R5, but I guess it didn't make it. I really think this should be addressed in R1. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 05:24:29 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 03:24:29 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. Message-ID: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> #2229: Background image does not center. -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- r28481 The Backgrounds Preferences application will no longer center an image. The image is shifted to the left when "Center" is selected and applied. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 07:19:50 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 05:19:50 -0000 Subject: [Haiku-bugs] [Haiku] #2230: pthread.h WARNING comma at the end of enum list Message-ID: <042.bda0f537e47396ae083914500229eed8@haiku-os.org> #2230: pthread.h WARNING comma at the end of enum list --------------------------+------------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- in lines 37 and 42. Not sure if this is in all builds or just the development build, i'm guessing it's just the development build. WARNING showed up while trying to build openal and removing the comma from the end of those two lines got rid of the WARNING message. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 10:03:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 08:03:05 -0000 Subject: [Haiku-bugs] [Haiku] #2231: [Pe] Find / Replace text entry box is only 3-4 pixels high Message-ID: <042.dab23c69c4be62e9bb3bdb2f8d08e3dd@haiku-os.org> #2231: [Pe] Find / Replace text entry box is only 3-4 pixels high ----------------------------+----------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Attached screenshot shows this better than I can explain it. Also there is a stray line in the middle of the dialog box as well. Sorry if this is a dupe as I wasn't able to search on "Pe" as it was too short. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 13:02:32 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 11:02:32 -0000 Subject: [Haiku-bugs] [Haiku] #511: [ScreenSaver] Many stability and other problems In-Reply-To: <040.13f4c046e032d852544afd83ddcbcbf8@haiku-os.org> References: <040.13f4c046e032d852544afd83ddcbcbf8@haiku-os.org> Message-ID: <049.e76957f1b7ac9a5b42e8771192d9eaac@haiku-os.org> #511: [ScreenSaver] Many stability and other problems --------------------------+------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences | Version: Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): The file 'Fetcher' included in ScreenSaver_2.zip doen't appear to be a valid screensaver, or it's corrupted; i tested also on r5, it doesn't do anything in preview mode (selecting Fetcher the test button is disabled), and if i insist selected it as screensaver, ScreenSaver pref. just ignore it. On Haiku crashes the ScreenSaver pref. if selected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 14:55:03 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 12:55:03 -0000 Subject: [Haiku-bugs] [Haiku] #2230: pthread.h WARNING comma at the end of enum list In-Reply-To: <042.bda0f537e47396ae083914500229eed8@haiku-os.org> References: <042.bda0f537e47396ae083914500229eed8@haiku-os.org> Message-ID: <051.b008e057d085b937b9267c2aa51295cc@haiku-os.org> #2230: pthread.h WARNING comma at the end of enum list ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r25487. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 16:08:02 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 14:08:02 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.c37ad7b8cfdc506cf1c73561606a03db@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: kaoutsis Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_preferences_screensaver_ScreenSaverApp.cpp.diff: * fixed a typo, that i introduced to the 'check for a screensaver' routine: the buffer that is used to contain the informations in order to examine if the file is a screensaver was not use memset correctly (only the first 4096 bytes were filled with 'a', not the entire buffer); that caused a bug: in some rare cases, the buffer when is reused, may contains the string 'StartSaver', that was left there from the examination of a previous real screensaver file, since these addresses would be part of the program's free address space, resulting in a wrong decision about the file in question. The fix makes now the routine more efficient: it doesn't use memset to fill the whole buffer with 'a' every time that the buffer is initialized, but only at the point where it finds a screensaver file, it fills the specific positions of the string with 'a', thus memset is using only 10 bytes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 20:28:02 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 18:28:02 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.6ca85d7162a79ecbfddb0b24dd623b1f@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by mjw): I have been working on freeciv and have noticed the same problem. What happens in freeciv's case is that some elements of argv are set to NULL before the BApplication object is instantiated. argc is unchanged. Eventually, BApplication::_ArgvReceived() is called with the correct value of argc, but all the NULL elements of argv are missing (so argc > num elements in argv). So, to cut a long story short, the free(argv[i]) call in _ArgvReceived() ends up freeing random pointers, causing the crash. I have attached a patch that fixes this bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 20:29:05 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 18:29:05 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.588bcb5dc707619ba9bc457aafd1a106@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Changes (by mjw): * cc: mjw (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 21:48:45 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 19:48:45 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.e5d356c90b81a6ba917fb595258efebc@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by stippi): The patch does not fix the error completely. The entire array needs to be initialized to NULLs, since an error could occur in the middle of loop. Then your patch would only initialize that entry, but break out of the loop early. Then the remaining items would still be uninitialized. But thanks for catching this one! (And sorry I forgot to credit you in the commit message, didn't intend to!) Does r25494 also fix the Firefox problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 22:06:17 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 20:06:17 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops Message-ID: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> #2232: Installer stops -----------------------+---------------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- r28481 running the installer in QEMU ( installing from the haiku image file to another image file )the installer copies all the files then stops running while displaying : "Finishing Installation." . one has to run makebootable to make the installation work after killing the installer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 22:08:50 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 20:08:50 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.9e8b6a3d1d68b285e6621b92386f50d9@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by mjw): Oh yeah - missed that one. D'oh. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 23:18:03 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 21:18:03 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.9b517ca862f0bddbcc7babd397571aad@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Changes (by korli): * owner: axeld => korli * component: - General => Applications/Installer -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 14 23:40:53 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 14 May 2008 21:40:53 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. In-Reply-To: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> References: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> Message-ID: <051.f25e7fd8657131cb7a1785e02c0fddff@haiku-os.org> #2229: Background image does not center. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by korli): Screenshot ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 04:37:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 02:37:07 -0000 Subject: [Haiku-bugs] [Haiku] #2197: KDL when starting Firefox In-Reply-To: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> References: <040.bc1f1d61cc07c8133b1ca8b713b00c21@haiku-os.org> Message-ID: <049.b65146551d7ea4cebbd894b50461f273@haiku-os.org> #2197: KDL when starting Firefox -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by cebif): I have tested again in r24577, I mean many repeat tests and it is not crashing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 06:14:52 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 04:14:52 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.113987e1b5fe412369630fd62f80f541@haiku-os.org> #1853: RTL8168 recognized but not working ---------------------------------+------------------------------------------ Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by anxiety): I just tested the old revision, despite seeing nothing wrong with the changes. I'm getting the same issue so it must be problem somewhere else. Do 0x8167 or 0x8169 work? Is anyone else having similar problems with other network cards? Nothing else in the drive has been touched so your guess is as good as mine as to where the problem lies. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 07:26:23 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 05:26:23 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.e22e2e5af262e77d3020f3a31030b6d3@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by umccullough): I just tested firefox 2.0.0.15pre BONE (experimental build from bebits) on r25493 and the problem didn't even exist there, so it may have already been fixed sometime in the last 6 months. Wish I'd noticed earlier - I'll try to track down the approximate timeframe that it got fixed if I can. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 09:18:50 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 07:18:50 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.36b00f9ee260b20a89482d0cd6480d68@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by stippi): * owner: kaoutsis => stippi * status: assigned => new Comment: I am looking into the remaining patches. They all look pretty good, I am just thinking that the Append() calls need error checking and for some of these, I consider using hardcoded paths as fallbacks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 09:19:01 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 07:19:01 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.52f007b68adc32476b5410c58d800d9d@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by stippi): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 11:03:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 09:03:41 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.e478bbe5bec05840cfb3d2035716cb5d@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by axeld): I don't know if this is really necessary - if Append() already fails, there doesn't seem to be much memory left to do anything useful, anyway :-) Well, the stuff in the kernel might do so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 11:16:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 09:16:08 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal colors as replicant goto black on white even if selected otherwise In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.74967f1330f8cc722dcbe7d9be71d802@haiku-os.org> #2215: Terminal colors as replicant goto black on white even if selected otherwise ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by axeld): * owner: axeld => jackburton * component: - General => Applications/Terminal Comment: For the ActivityMonitor, I used the following method: usually, it reads its settings in the window class, puts it into a message, and passes this one to the ActivityView. When archiving the ActivityView, it would remember these settings, and store it in its own message. That way, it takes over the current settings at the time the replicant was initialized, but still allows its own settings afterwards. In any case, as stippi mentioned, the replicant must include the scrollview to be of use, so there needs to be some sort of shell anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 12:47:19 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 10:47:19 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal colors as replicant goto black on white even if selected otherwise In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.95391872826d3da9f108a85fa0727378@haiku-os.org> #2215: Terminal colors as replicant goto black on white even if selected otherwise ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by jackburton): Replying to [comment:2 axeld]: > For the ActivityMonitor, I used the following method: usually, it reads its settings in the window class, puts it into a message, and passes this one to the ActivityView. > When archiving the ActivityView, it would remember these settings, and store it in its own message. That way, it takes over the current settings at the time the replicant was initialized, but still allows its own settings afterwards. Ok, thanks, I'll have a look at what you did in ActivityView. > In any case, as stippi mentioned, the replicant must include the scrollview to be of use, so there needs to be some sort of shell anyway. To fix this problem, the TermView itself could include the scrollbar... I haven't put much thinking on this yet, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 13:56:03 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 11:56:03 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.962bb63c8875b0f0b2196d68c7a9f9b7@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by stippi): devfs.cpp.diff applied in r25503. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 13:56:54 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 11:56:54 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.ad450d32f3df95e188cea534174c8fc1@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by stippi): team.cpp.diff applied in r25506. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 14:10:56 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 12:10:56 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.6cdc46f78ab782819d8334b6d3d97ce4@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by stippi): system_kernel_main.cpp.diff applied in r25509. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 15:04:34 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 13:04:34 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.0bf03322df27b0b9e0046ca2e3d380a9@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by bonefish): I'm actually not quite sure, whether I find it a good idea to use find_directory() in system components like the kernel or the runtime loader. They just complicate things without real benefit. I mean, the whole point of using find_directory() in applications is to still work as expected when the system's directory layout changes. But these components *are* the system. I think I'd rather use a common single header file that defines the paths. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 15:23:56 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 13:23:56 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.e71b47522119837816b23f6ca3f7d066@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by axeld): That common single header sounds like a good idea. It should then be used by the kernel and find_directory() itself (if viable). find_directory() would only make sense in the kernel as well, if we make these paths configurable - which I don't think is really necessary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 15:56:32 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 13:56:32 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal colors as replicant goto black on white even if selected otherwise In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.1bbc24ad15783f633d22ee4a7b4ffbd8@haiku-os.org> #2215: Terminal colors as replicant goto black on white even if selected otherwise ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Comment (by scottmc): Bonus points if you can also allow transparentcy. ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 18:20:46 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 16:20:46 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.c62d59ba44ab0ec87fe01be2fe8a862b@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:16 korli]: > About src_preferences_screensaver_ScreenSaverApp.cpp.diff, I'm not sure the way the 'check for a screensaver' is done is good. Why not let the screensaver loading do its job ? I'm not sure, either :-) There are two issues here: 1) The basic idea was that the screensaver list should contains only screensaver files. Imagine the scenario: a user drops a readme file, and that readme appears in the screensaver list. If we can prevent that, i think that to check for a valid screensaver, is a good idea. Of course, if we want the screensaver list to contain only screensaver files, there is more work to be done. For example, the user may drop the file(s) directly to the addons directory, then the screensaver list should updated with only the valid screensaver files, and if the user insist to drop the file in the ScreenSaver window, he will get the alert info: file x, is not a screensaver file. 2) Now the 'routine' check: Obviously, the routine is some kind of practical algorithm :-) All the screensaver-binary-files that i could tested contained the 'StartSaver' string somewhere inside a 80k limit (actually the real limit is somewhere between 40k, i increased to 80k just in case). Of course, a valid screensaver should use the StartSaver() function (i hope this hypothesis is correct). Giving the fact, that the user hopefully, will drop screensaver files, the routine checks first the first 4096 bytes, then 4096 * 2, then 4096 * 3, and so on; it usually finds the screensaver after 4 or 5 tries. Now if the user drops a irrelevant file then indeed the check hits the limits (n = 20 times and each time checks 4096 * 1, 4096 * 2, ...,4096 * n bytes). If you think that 1. is a good idea, then we can think over 2. It's up to you :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 19:25:21 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 17:25:21 -0000 Subject: [Haiku-bugs] [Haiku] #2233: Wrong moduleImage->info[0]->name and moduleImage->path for scsi_dsk and scsi_cd in module.cpp Message-ID: <043.9125a6bc0a4238543a8afeb15d57d7ec@haiku-os.org> #2233: Wrong moduleImage->info[0]->name and moduleImage->path for scsi_dsk and scsi_cd in module.cpp -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- moduleImage->info[0]->name is drivers/disk/scsi/scsi_dsk/device_v1 moduleImage->path /boot/beos/system/add- ons/kernel/drivers/disk/scsi/scsi_dsk image->name is scsi_dsk moduleImage->info[0]->name is drivers/disk/scsi/scsi_cd/device_v1 moduleImage->path /boot/beos/system/add- ons/kernel/drivers/disk/scsi/scsi_cd image->name is scsi_cd Path /boot/beos/system/add-ons/kernel/drivers/disk doesn't exist -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 14:14:25 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 12:14:25 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.ab6d19b3b6998d203c716e5a3b38b276@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by korli): About src_preferences_screensaver_ScreenSaverApp.cpp.diff, I'm not sure the way the 'check for a screensaver' is done is good. Why not let the screensaver loading do its job ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 15 23:17:40 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 21:17:40 -0000 Subject: [Haiku-bugs] [Haiku] #2233: Wrong moduleImage->info[0]->name and moduleImage->path for scsi_dsk and scsi_cd in module.cpp In-Reply-To: <043.9125a6bc0a4238543a8afeb15d57d7ec@haiku-os.org> References: <043.9125a6bc0a4238543a8afeb15d57d7ec@haiku-os.org> Message-ID: <052.de87322d41b631aab00f5b32e717a6a8@haiku-os.org> #2233: Wrong moduleImage->info[0]->name and moduleImage->path for scsi_dsk and scsi_cd in module.cpp ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: It will when I'm done with new device architecture :-) I'm closing this now already, since it goes away anyway, and I probably would forget about this later ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 00:03:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 22:03:47 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.cbb9097b1d6873ee222d79d4f2891741@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by korli): Replying to [comment:19 kaoutsis]: > If you think that 1. is a good idea, then we can think over 2. I'm OK for 1. I think 2. is not the way to go. I would prefer the actual code to load the addon: image = load_add_on(path); if (image != B_OK) ... if (get_image_symbol((image, "instantiate_screen_saver", B_SYMBOL_TYPE_TEXT, (void **)&instantiate) != B_OK) ... unload_add_on(image); Isn't it better? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 00:11:51 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 22:11:51 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.1a6145d775bdf364448980b93cd83eda@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by korli): then it's fixed ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 00:18:58 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 22:18:58 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. In-Reply-To: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> References: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> Message-ID: <051.1de65f22b207297d3e515f9f57ad8aa9@haiku-os.org> #2229: Background image does not center. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by korli): Can't reproduce. What's your screen resolution ? Can you provide the image ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 00:20:27 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 22:20:27 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.8ddf83666b768d178b84409c1c11db35@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try again with r25516+ please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 00:34:34 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 22:34:34 -0000 Subject: [Haiku-bugs] [Haiku] #1895: Add Canna input method to UserBuildConfig.sample In-Reply-To: <037.3fc2ab2c30c25a03d0f4d3ec2a66cf3f@haiku-os.org> References: <037.3fc2ab2c30c25a03d0f4d3ec2a66cf3f@haiku-os.org> Message-ID: <046.e9802c0eb5786870cea02cf090ebeeb8@haiku-os.org> #1895: Add Canna input method to UserBuildConfig.sample --------------------------+------------------------------------------------- Reporter: mt | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All --------------------------+------------------------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid Comment: canna is already built in HaikuImage: see "optional" root directory of the image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 01:37:51 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 15 May 2008 23:37:51 -0000 Subject: [Haiku-bugs] [Haiku] #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) In-Reply-To: <041.8ebc7d3b95778d708ba44ac6d6596515@haiku-os.org> References: <041.8ebc7d3b95778d708ba44ac6d6596515@haiku-os.org> Message-ID: <050.022e951032ccc3f9572fbd16c2e26e15@haiku-os.org> #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed Comment: Applied in r25518. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 10:08:08 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 08:08:08 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.2f4730001b463716092ce1368377cfbf@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:20 korli]: > Replying to [comment:19 kaoutsis]: > > If you think that 1. is a good idea, then we can think over 2. > > I'm OK for 1. I think 2. is not the way to go. I would prefer the actual code to load the addon: > > image = load_add_on(path); > if (image != B_OK) > ... > if (get_image_symbol((image, "instantiate_screen_saver", B_SYMBOL_TYPE_TEXT, (void **)&instantiate) != B_OK) > ... > unload_add_on(image); > > Isn't it better? I believe yes. I will try an implementation based upon this idea; i will take my time, and i will come back later with an updated patch, OK? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 13:30:29 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 11:30:29 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) Message-ID: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) ----------------------------+----------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- I consider this to be a bug of some kind; I can't see what the blue leaf stands for, (I thought it was supposed to be a feather), when I look at the BeOS r5 desktop I see immediately that it is BeOS because it is written (on the logo) in the DeskBar. This might seem silly, but this is purely marketing, I know the Haiku-logo is in the Desktop background picture, but a lot of users change their Desktop background picture and probably show their Desktop screen to other users but most importantly will upload screenshots. 2nd: it must be obvious the Leaf-menu-logo is clickable and will open the application menu. For example; the Windows XP's Start-menu has written "Start" on it's button, it lights up when mouse-over, and it is more or less button-ish. 3nd: it is called leaf-menu, but as I said, I couldn't tell it was a leaf but thought it was a feather, thus it did not occur immediately to me that it was referencing the Deskbar Menu or better former "Be menu", which btw is also not very clear. Thank you for your attention. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 16:28:19 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 14:28:19 -0000 Subject: [Haiku-bugs] [Haiku] #2235: cdrecord no longer recognizes virtual device Message-ID: <041.5d126e1a09501c6e1481e89f6ef9967e@haiku-os.org> #2235: cdrecord no longer recognizes virtual device -----------------------+---------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I reported a month ago: [http://www.haikuware.com/20080405201/latest/cd-burning-under-haiku] that you could actually use cdrecord along with a front-end to burn CDs in Haiku under Vmware. My device was detected, and I actually erased a CD this way. I believe it happened several weeks ago, where the device is no longer detected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 17:23:01 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 15:23:01 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... Message-ID: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ---------------------------+------------------------------------------------ Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Platform: x86 | ---------------------------+------------------------------------------------ Tested with r25522. I tested the updated AUICH driver(r25497) and it crashes media_addon_server landing to KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 17:31:40 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 15:31:40 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.33f7f35a38b362f3606dd1b6ddd97d3d@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Trac doesn't allow images higher than 500k. Here is the link to the screen shot. http://img513.imageshack.us/my.php?image=auichkdltg9.jpg Alternate: http://img513.imageshack.us/img513/5718/auichkdltg9.jpg -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 17:51:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 15:51:23 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.5722f016aa7bd70b39cf826157ae3433@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by mmlr): Well this has been discussed previously I think. IMO it's not really necessary. The references you put here are not really good ones BTW. Windows does not have the OS name in the start menu button and in Vista it doesn't even say "Start" anymore. Also when using a windows < XP or with the classic theme the button does not light up or anything. Under linux you usually have the gnome foot, the KDE k thing or something to that extend. I _might_ agree that it should be made more recognizable as a clickable button, although it is really only the very first time you use the OS where you might not know it is a button. So some kind of quick introduction at first boot explaining it would perfectly suffice IMO. So the only reason I would see to change the logo is from the marketing perspective. I don't know if this is a strong enough argument for it though. Another thing that might point into the direction of changing the logo is that the current one doesn't really look right when the Deskbar is used in the horizontal layout. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 18:01:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 16:01:55 -0000 Subject: [Haiku-bugs] [Haiku] #2232: Installer stops In-Reply-To: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> References: <042.d680184d20a7da48e6571c1a765d8a47@haiku-os.org> Message-ID: <051.fa5891ed0f7832dc22adcf315796c157@haiku-os.org> #2232: Installer stops -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: | Platform: All -------------------------------------+-------------------------------------- Comment (by bbjimmy): For an experiment, I added a line at the beginning of the InstallerFinishScropt file: #!/bin/sh ## The installer finish script. alert "InstallerFinishScript is running" OK the alert poped up, but the installer did not finish and the target partition was not bootable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 18:30:20 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 16:30:20 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.c38f6bdf80b6de7323444ddc5dc565d0@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Seems not related to AUICH driver ... Similar problems : #2228, #2213 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 19:08:42 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 17:08:42 -0000 Subject: [Haiku-bugs] [Haiku] #2237: Multiple declarations in posix/netdb.h Message-ID: <042.4283f0b14c1841b777d2c47251d1786f@haiku-os.org> #2237: Multiple declarations in posix/netdb.h -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- For example line: struct hostent *getipnodebyname __P((const char *, int, int, int *)); is declared two times. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 20:21:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 18:21:04 -0000 Subject: [Haiku-bugs] [Haiku] #2237: Multiple declarations in posix/netdb.h In-Reply-To: <042.4283f0b14c1841b777d2c47251d1786f@haiku-os.org> References: <042.4283f0b14c1841b777d2c47251d1786f@haiku-os.org> Message-ID: <051.b609585d44aabb2edeefbbd72759146b@haiku-os.org> #2237: Multiple declarations in posix/netdb.h ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): I see *getipnodebyaddr duped as well, are there any others? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 20:37:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 18:37:55 -0000 Subject: [Haiku-bugs] [Haiku] #2237: Multiple declarations in posix/netdb.h In-Reply-To: <042.4283f0b14c1841b777d2c47251d1786f@haiku-os.org> References: <042.4283f0b14c1841b777d2c47251d1786f@haiku-os.org> Message-ID: <051.47943407131b94781b1c97c4d3d2831d@haiku-os.org> #2237: Multiple declarations in posix/netdb.h ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaliber): And there is also: {{{ void freehostent __P((struct hostent *)); }}} I don't know why it's duped. Maybe it should be freehostent_r insted of freehostent? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 16 23:05:41 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 21:05:41 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.c18814b345343bebb549b8b316631a5d@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Hi guys, I came around to test the driver more -- and guess what: it's in perfect working order. The fault has been introduced by axel(?) while completely rewriting the AGP busmanager. Simply disable AGP mode via nvidia.settings and reboot. I'll try to have a look at the busmanager this weekend to see if I can nail the problem there. Unless Axel can find it quickly of course ;-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 00:25:51 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 22:25:51 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.71677308145fc134a224ae990ad4227f@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): bga the memory doesn't show anything unusual, although I don't know why not all output is printed. if possible, please use r25523 and run the new "pcistatus" command from KDL after the panic happened. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 01:27:07 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 23:27:07 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.5f57f6f4a1647793848293e1187ea46b@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by marcusoverhagen): * cc: marcusoverhagen (added) Comment: I also get this with r25523 while checking out haiku source. Used memory in ActivityMonitor was 694 MB when it crashed (on a 4GB machine). {{{ vm_soft_fault: kernel thread accessing invalid user memory! vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x30010800, ip 0x30010800, write 0, user 0, thread 0xb CPU 1 halted! CPU 3 halted! CPU 0 halted! PANIC: vm_page_fault: unhandled page fault in kernel space at 0x30010800, ip 0x30010800 Welcome to Kernel Debugging Land... Running on CPU 2 kdebug> sc stack trace for thread 11 "block notifier/writer" kernel stack: 0x80151000 to 0x80155000 frame caller :function + offset 80154a60 (+ 48) 800496e7 :invoke_debugger_command + 0x00cf 80154a90 (+ 64) 8004a490 :_ParseCommand__16ExpressionParserRi + 0x01f8 80154ad0 (+ 48) 80049e82 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 80154b00 (+ 224) 8004b5a4 :evaluate_debug_command + 0x0088 80154be0 (+ 64) 80048222 :kernel_debugger_loop__Fv + 0x017a 80154c20 (+ 48) 80048ed5 :kernel_debugger + 0x010d 80154c50 (+ 192) 80048dbd :panic + 0x0029 80154d10 (+ 64) 8009410f :vm_page_fault + 0x00ab 80154d50 (+ 64) 8009e289 :page_fault_exception + 0x00b1 80154d90 (+ 12) 800a197d :int_bottom + 0x001d (nearest) iframe at 0x80154d9c (end = 0x80154df4) eax 0x30010800 ebx 0xa485ebe4 ecx 0x0 edx 0x200246 esi 0xa485ec04 edi 0x80154e40 ebp 0x80154e48 esp 0x80154dd0 eip 0x30010800 eflags 0x210287 vector: 0xe, error code: 0x0 [*** READ/WRITE FAULT ***] kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 01:36:42 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 16 May 2008 23:36:42 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.3eb4bd7f8b1316f3554d9be2b8fe96c8@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by marcusoverhagen): This might be related, too. {{{ PANIC: free(): free failed for address 0x8014bd98 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> sc stack trace for thread 11 "block notifier/writer" kernel stack: 0x80151000 to 0x80155000 frame caller :function + offset 80154b08 (+ 48) 800496e7 :invoke_debugger_command + 0x00cf 80154b38 (+ 64) 8004a490 :_ParseCommand__16ExpressionParserRi + 0x01f8 80154b78 (+ 48) 80049e82 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 80154ba8 (+ 224) 8004b5a4 :evaluate_debug_command + 0x0088 80154c88 (+ 64) 80048222 :kernel_debugger_loop__Fv + 0x017a 80154cc8 (+ 48) 80048ed5 :kernel_debugger + 0x010d 80154cf8 (+ 192) 80048dbd :panic + 0x0029 80154db8 (+ 48) 8002e814 :free + 0x0074 80154de8 (+ 96) 800238ee :flush_pending_notifications__FP11block_cache + 0x01a6 80154e48 (+ 64) 80023999 :flush_pending_notifications__Fv + 0x006d 80154e88 (+ 336) 800259c1 :block_notifier_and_writer__FPv + 0x0055 80154fd8 (+ 32) 80040d6f :_create_kernel_thread_kentry__Fv + 0x001b 80154ff8 (+2146086920) 80040d04 :thread_kthread_exit__Fv + 0x0000 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 02:08:00 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 00:08:00 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.40a65a6edb8194e8511edb55ef5a080a@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): According to the syslog from 05/02/08, the pci latency settings on your system appear so be in a normal range. Nothing unusually large, and that shouldn't cause any PCI errors anyway, just might have an performance impact for the other devices with low latency settings. I wasn't able to reproduce this so far, as bug #2059 always happens earlier here. Please try the pcistatus command next. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 02:20:18 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 00:20:18 -0000 Subject: [Haiku-bugs] [Haiku] #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) In-Reply-To: <041.8ebc7d3b95778d708ba44ac6d6596515@haiku-os.org> References: <041.8ebc7d3b95778d708ba44ac6d6596515@haiku-os.org> Message-ID: <050.63eec48ef0eddc31ecd548cdbbc5995d@haiku-os.org> #2220: Undesired B_INPUT_METHOD_STOPPED is sent to input method (IM) ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Comment (by shinta): Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 03:36:55 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 01:36:55 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.dcafa59fec63688db78fd40b0061f564@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): I tried pcistatus. Everything was right according to it except for this: domain 0, bus 0, dev 31, func 2, PCI device status 0x22b8 Received Master-Abort Let me know if you need the full output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 03:53:04 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 01:53:04 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.a8dbed03c62c45ebd4bfba1345f8e578@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): And, btw, I have been reproducing this bug in a different way now. What I do is zip up the entire source tree (probably any large enough zip file will do) and move it to the image. Then I unpack it there. I have to do it twice but 100% of the time, it will panic during the second time the file is being unzipped. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 11:32:16 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 09:32:16 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.6f8b9019a92689764653827027b8909d@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): This at least confirms that the ahci controler experiences a PCI master abort. {{{ KERN: PCI: [dom 0, bus 0] bus 0, device 31, function 2: vendor 8086, device 2922, revision 02 632 KERN: PCI: class_base 01, class_function 06, class_api 01 633 KERN: PCI: vendor 8086: Intel Corporation 634 KERN: PCI: device 2922: 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller 635 KERN: PCI: info: Mass storage controller (SATA controller, AHCI 1.0) 636 KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 637 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 638 KERN: PCI: cardbus_CIS 00000000, subsystem_id 8277, subsystem_vendor_id 1043 639 KERN: PCI: interrupt_line 03, interrupt_pin 02, min_grant 00, max_latency 00 640 KERN: PCI: base reg 0: host 00007c00, pci 00007c00, size 00000010, flags 09 641 KERN: PCI: base reg 1: host 00007880, pci 00007880, size 00000010, flags 0d 642 KERN: PCI: base reg 2: host 00007800, pci 00007800, size 00000010, flags 09 643 KERN: PCI: base reg 3: host 00007480, pci 00007480, size 00000010, flags 0d 644 KERN: PCI: base reg 4: host 00007400, pci 00007400, size 00000020, flags 01 645 KERN: PCI: base reg 5: host fe5fe800, pci fe5fe800, size 00000800, flags 00 646 KERN: PCI: Capabilities: MSI, PM, SATA, vendspec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 11:36:10 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 09:36:10 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.9da3bf7667fb95e853104d3ab977f28e@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 12:05:15 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 10:05:15 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.93fa6b68c0a2a54afef6461119454b85@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Update: To be really sure about that AGP problem I decided to test my old driver V0.80 combined with AGP busmanager V0.02 (both on bebits). The same behaviour applies. In other words: The rewritten AGP busmanager is probably not the problem after all! (sorry :) So: in conclusion for now (I'll test other cards later on): the bootscreen introduced the problem? Please tell me: is the gfx driver used in any way to create this bootscreen? It's known (by me) for nvidia that it's unwise to use the driver before AGP mode is enabled. If the driver is used for the bootscreen while AGP is still down (I don't know how this could be though since the driver's accelerant calls the manager itself, unless loading and starting the kernel driver already causes the malfunction) that might cause the problem. The problem is in fact a communications problem with the AGP bus. Comms is partially lost. I've had this problem before (but then even worse) when I did a few things out of correct order in the AGP busmanager (diff between V0.01 and 0.02). MTRR is not the problem BTW. OK, back to work ;-) Bye! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 12:25:57 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 10:25:57 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.e802a441b11e5fb1a2406221086e0b57@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r25525. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 13:03:41 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 11:03:41 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.89756918566b62ee5346a3d4589a7580@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Update2: Now tested TNT1 AGP (NV04), FX5200 AGP (NV34) and MX4000 AGP (NV18). All same behaviour. Mainboard is Asus P3 mainboard with P3-600/133Mhz FSB. AGP1.0 capable. I compared driver logs: here is what I found: === R5: (after creating internal modelist, before calling first setmode) ACCELERANT_MODE_COUNT: the modelist contains 147 modes GET_MODE_LIST: exporting the modelist created before. SETMODE: (ENTER) initial modeflags: $8000011f --- (after comleting setting mode): 8 overlay hooks are called (except SUPPORTED_FEATURES) Haiku: ACCELERANT_MODE_COUNT: not called GET_MODE_LIST:not called 9 overlay hooks are called (is illegal at this point!!) SETMODE: (ENTER) initial modeflags: $00000000 (eof) === I expect there's nothing to worry about here concerning this bug, but I see another bug (in my strong opinion): Overlay hooks should not be asked for if no mode was previously set!! Overlay hooks may or may not be available to the client (appserver here) depending on the mode previously set. The accelerant is per definition in an undefined state on haiku when the overlay hooks are called for the first time! OK, that's it for now. I'll try to trace the AGP busmanager and kerneldriver later on. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 13:07:16 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 11:07:16 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.278981feac9a7c61a93c2033540a4096@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * owner: emitrax => mmlr * priority: normal => blocker * status: new => assigned Comment: Working on it. This is a blocker for R1/alpha. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 13:56:43 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 11:56:43 -0000 Subject: [Haiku-bugs] [Haiku] #2172: neon's single_read test hangs at 100% CPU In-Reply-To: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> References: <043.c761896317f88f11b7764cbb7a0354c7@haiku-os.org> Message-ID: <052.9689b14cd3a3456e0816acef6db86513@haiku-os.org> #2172: neon's single_read test hangs at 100% CPU -------------------------------------+-------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: Network & Internet/TCP | Version: R1 development Resolution: fixed | Platform: x86 -------------------------------------+-------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r25526. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 14:07:42 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 12:07:42 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.c729d87248035074874cdc4949fa3191@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by stippi): Thank you Rudolf for all your research on this! It is very useful and appreciated. I might be able to fix some of the problems you pointed out. I can confirm that the driver is not used for anything bootscreen related. It will be used only by app_server at the point where it finds out about capabilities, which should be shortly before the mode is switched and blue desktop background is rendered. The boot screen is drawn via VESA and BIOS stuff. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 17:15:32 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 15:15:32 -0000 Subject: [Haiku-bugs] [Haiku] #2059: KDL during svn checkout in block notifier/writer In-Reply-To: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> References: <044.6ebbdfd8333437235326f20214f0188c@haiku-os.org> Message-ID: <053.8b928c82a3c9218ef1fd75144d2bd3e7@haiku-os.org> #2059: KDL during svn checkout in block notifier/writer ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: All ----------------------------+----------------------------------------------- Comment (by stippi): Works beautifully now! Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 18:07:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 16:07:12 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.d9c9169153ca8984e3bdb2643ca0233a@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): I will. (but there are haven't been any new builds after r25477 from May 12th) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 18:10:46 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 16:10:46 -0000 Subject: [Haiku-bugs] [Haiku] #2238: KDL on mounting BFS drive Message-ID: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> #2238: KDL on mounting BFS drive ------------------------------+--------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Platform: x86 | ------------------------------+--------------------------------------------- I've got Haiku running on real hardware here, when I go to mount my Zeta drive, Haiku KDLs. Unfortunately, it gives me no option to use the keyboard and mouse after that so I can't get a backtrace KDL text is: "PANIC: could not read block 28682635: bytesRead: -1, error: Device seek error" The Haiku and Zeta partitions are on the same SATA HDD. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 18:25:30 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 16:25:30 -0000 Subject: [Haiku-bugs] [Haiku] #2238: KDL on mounting BFS drive In-Reply-To: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> References: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> Message-ID: <048.312f603be9d81b7fc9f37d03c9c3e863@haiku-os.org> #2238: KDL on mounting BFS drive -------------------------------+-------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by stippi): Unless you are using a USB keyboard, you should be able to enter "sc" into the kernel debugger to get a stack trace. If nothing else, take photos of the KDL output and attach them to this bug. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 18:35:06 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 16:35:06 -0000 Subject: [Haiku-bugs] [Haiku] #2238: KDL on mounting BFS drive In-Reply-To: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> References: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> Message-ID: <048.08b7f1577f203a493ca1847b346ac146@haiku-os.org> #2238: KDL on mounting BFS drive -------------------------------+-------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by myob): I'm using a USB keyboard... that is the complete output unfortunately! I'll try to find a PS/2 board later on. Should add - its r25477, the partition used to mount - last tried about November 2007 - and comes up clean in a chkbfs from Zeta. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 19:03:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 17:03:12 -0000 Subject: [Haiku-bugs] [Haiku] #2238: KDL on mounting BFS drive In-Reply-To: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> References: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> Message-ID: <048.5f504d1294c7dbef79861b4deb3a68d9@haiku-os.org> #2238: KDL on mounting BFS drive -------------------------------+-------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by emitrax): Is it possible to add sc as an automatic command when entering KDL? It seems like a good solution in this situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 20:26:34 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 18:26:34 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.339a119d9921d0a404689d2db4b04149@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): Hi stippi, Want me to take over this one? I have some experience with the BCLV code so I'd be willing. Also, which scroll area are you referring to? Horizontal or Vertical? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 23:31:34 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 21:31:34 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.5f66b1079c58867acd8b02117f1da43f@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * owner: stippi => anevilyak Comment: Oh yes, please do! Vertical scrolling seems to work fine. But horizontal scrolling does not affect the header view. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 23:39:09 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 21:39:09 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.559f11ec5cd771fb92fcca38c54c460e@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: new => assigned Comment: Will look, do you have any good app for a testcase illustrating this or will I need to write one? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 17 23:45:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 21:45:21 -0000 Subject: [Haiku-bugs] [Haiku] #2238: KDL on mounting BFS drive In-Reply-To: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> References: <039.860753a87de83006fddd8c15ccce949d@haiku-os.org> Message-ID: <048.067d51bd86e2ccccfa24eb4d02bdd870@haiku-os.org> #2238: KDL on mounting BFS drive -------------------------------+-------------------------------------------- Reporter: myob | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by axeld): There is a better one: it's possible to handover the USB keyboard to the BIOS again during the KDL session. That way, USB keyboards can be used there, too. IIRC Michael wanted to implement this some time ago... But there is another solution: just remove the USB drivers from Haiku, and enable USB legacy emulation in your system's BIOS. Then you should be able to use it as well. To remove the Haiku USB drivers, you should remove the USB bus manager at least (eventually also UHCI/EHCI). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 00:24:52 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 17 May 2008 22:24:52 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.4efb306b49c4b50dcb050cd02fc2235e@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): DriveSetup can be used to reproduce it. It also builds in the test environment, in case you want to use that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 02:24:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 00:24:56 -0000 Subject: [Haiku-bugs] [Haiku] #2143: KDL in net timer. In-Reply-To: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> References: <038.81320c9ffad65dc8d88e69f601272f32@haiku-os.org> Message-ID: <047.9b3e5e890e53c2666233f1e9f3f338ae@haiku-os.org> #2143: KDL in net timer. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by bonefish): Probably related (r25537): {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbeef, ip 0xdeadbeef Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> sc stack trace for thread 66 "net timer" kernel stack: 0x807ca000 to 0x807ce000 frame caller :function + offset 807cdc20 (+ 48) 8004e69b :invoke_debugger_command + 0x00cf 807cdc50 (+ 64) 8004f444 :_ParseCommand__16ExpressionParserRi + 0x01f8 807cdc90 (+ 48) 8004ee36 :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 807cdcc0 (+ 224) 80050558 :evaluate_debug_command + 0x0088 807cdda0 (+ 64) 8004d1d6 :kernel_debugger_loop__Fv + 0x017a 807cdde0 (+ 48) 8004de89 :kernel_debugger + 0x010d 807cde10 (+ 192) 8004dd71 :panic + 0x0029 807cded0 (+ 64) 8009acef :vm_page_fault + 0x00ab 807cdf10 (+ 64) 800a4de1 :page_fault_exception + 0x00b1 807cdf50 (+ 12) 800a857d :int_bottom + 0x001d (nearest) iframe at 0x807cdf5c (end = 0x807cdfb4) eax 0xdeadbeef ebx 0x807c9498 ecx 0x9115f000 edx 0x200246 esi 0x91be9e6c edi 0x0 ebp 0x807cdfd8 esp 0x807cdf90 eip 0xdeadbeef eflags 0x210287 vector: 0xe, error code: 0x0 807cdf5c (+ 124) deadbeef 807cdfd8 (+ 32) 800446ef :_create_kernel_thread_kentry__Fv + 0x001b 807cdff8 (+2139299848) 80044684 :thread_kthread_exit__Fv + 0x0000 }}} If TCP does indeed use the timers as explained on the commit mailing list recently, it might be a good idea to remove the race condition, as it perfectly explains these kinds of problems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 02:30:58 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 00:30:58 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.e38bee046e0988bf6f1facfec0619b0f@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by umccullough): It worked prior to r25494 (in fact, I tested back to 24500 and it even worked there I believe) With r25536 now though, it spits some output to the terminal window that I hadn't seen before: /boot/apps/firefox> firefox --safe-mode Error parsing B_ARGV_RECEIVED message. Message: BMessage('_ARG') { argc = int32(0x2 or 2) argv = string("./firefox", 10 bytes) cwd = string("/boot/apps/firefox", 19 bytes) } /boot/apps/firefox> This was tested with Firefox 2.0.0.15pre BONE from the Experimental Build page on bebits. I think this issue can safely be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 02:32:06 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 00:32:06 -0000 Subject: [Haiku-bugs] [Haiku] #1620: Firefox crashes with "-safe-mode" switch In-Reply-To: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> References: <046.23460023e9ad4847fc94b85d005ea8b7@haiku-os.org> Message-ID: <055.aff4d4f4892dc352cdf938daa93cb00c@haiku-os.org> #1620: Firefox crashes with "-safe-mode" switch --------------------------------+------------------------------------------- Reporter: umccullough | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by umccullough): Just in case it wasn't clear - even with the output mentioned in my previous comment, it does start without crashing at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 05:00:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 03:00:11 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.17b1a95345bc9492be90e699ea2b31a7@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by tigerdog): Thought maybe this was caused by a monitor known to report erroneous EDID info, but new monitor does the same thing. :( -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 05:00:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 03:00:36 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.b989314e9111397efb81031e44650897@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by tigerdog): Still standing by to test but it's now more difficult since Haiku doesn't boot properly on my hardware (unless I use video safe mode - see bug 2071) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 07:41:37 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 05:41:37 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.e7150f9ec76a927e39ca9dad82e3b0e9@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by humdinger): This should be the same bug: ticket #1252 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 13:36:24 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 11:36:24 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.44cd24004f0ddb2ad2ea00a597bf7616@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_preferences_screensaver_ScreenSaverApp.cpp.2.diff: There are a number of changes in order to make the ScreenSaver pref. contains only screensavers in the list, notably: 1) The use of load_add_on() and get_image_symbol() functions. Note however that there is a difference in relation with the previous implementation: Besides the really irrelevant files, the routine now 'cuts off' also screensaver files that can't loaded correctly, there are two cases: a) screesaver-files with missing library, e.g libGLU.so b) screensaver-files with unresolved symbols, e.g elf_resolve_symbol: could not resolve symbol 'ReadFrames__11BMediaTrackPcPxP12media_header' 2) The use of watch_node() in order to monitor the user's Screen Savers addons directory. Since we are moving to a multiuser environment, i think there isn't need to monitor other dirs, the user would access these dirs read-only. * Although the list is updated with only the valid screensaver files on the fly, namely when the ScreenSaver pref. is running and the user drops the file(s) directly to the addons directory, the ScrenSaver pref. crashes is some cases if the user selects some item from the list; i still don't know why and where. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 14:11:27 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 12:11:27 -0000 Subject: [Haiku-bugs] [Haiku] #1855: Glibc wide char functions are disabled In-Reply-To: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> References: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> Message-ID: <054.08aadbbb4d8c7b78caf66599ae9107cc@haiku-os.org> #1855: Glibc wide char functions are disabled --------------------------------+------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by andreasf): Jack, Replying to [comment:1 jackburton]: > More info on this: > iofwide.c needs gconv_trans.c, but as soon as I include it in the build, it complains about undefined __libc_dlopen, __libc_dlclose, etc. > We are actually using the bsd version of these functions, which have different names. What's the status of these issues? If it's just a naming issue but the signature is identical we could just {{{ #define __libc_dlopen bsd_name_of_dlopen #define __libc_dlclose bsd_name_of_dlclose }}} Portable.NET detects the presence of mbrtowc & co. but then fails at runtime. Manually commenting out its {{{HAVE_MBRTOWC}}} et al. makes it run okay. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 15:24:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 13:24:44 -0000 Subject: [Haiku-bugs] [Haiku] #1855: Glibc wide char functions are disabled In-Reply-To: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> References: <045.34bab0da7c7771105187bde6b57a07a9@haiku-os.org> Message-ID: <054.3473a86706e0fa0d1e56a4758b3a839a@haiku-os.org> #1855: Glibc wide char functions are disabled --------------------------------+------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by jackburton): Replying to [comment:9 andreasf]: > Jack, > > Replying to [comment:1 jackburton]: > > More info on this: > > iofwide.c needs gconv_trans.c, but as soon as I include it in the build, it complains about undefined __libc_dlopen, __libc_dlclose, etc. > I did this already. But the problem is a bit more involved, unfortunately :) Last time I tried to track down the issue (uncommenting / reverting all the disabled stuff), I still end up with a non-working support for wide char stuff. And currently I don't have the time (and will) to look into this. So if anyone else wants to have a look, I'd be glad to step down :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 18:10:11 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 16:10:11 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.066d6f17ebf04d9c00c6696e8b260656@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by nutela): Say, shouldn't haiku be _better_ then MS Windows? I agree with your points mmlr but comparing it with Windows... is not such a good idea since Windows is IMO a very bad OS, especially from a usability perspective. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 18:45:19 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 16:45:19 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.0a060f34cdb16d4e6e02829cb2f76498@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): Actually, no. BeShare uses the column list view from Santa's Gift Bag, which has nothing in common code-wise with BColumnListView. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 19:19:54 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 17:19:54 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.a2d262474ddcf5ac4cca68518e5ac35b@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by mmlr): That's not what I said. I compared it to windows since you brought it up as a reference. I just pointed out that comparing to other OSes it doesn't seem to be particularly common to put the name there. I would like to hear from Jorge on that matter from the marketing perspective and maybe from Stephan if he could fit it in nicely. If it's not doable to put the name there so that it looks more attractive than a logo or a part of the logo, then I simply wouldn't do it. If it can be easily integrated so that it looks good then why not give it a try of course. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 19:26:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 17:26:21 -0000 Subject: [Haiku-bugs] [Haiku] #2239: kernel doen't free memory that was requested from userspace programs Message-ID: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> #2239: kernel doen't free memory that was requested from userspace programs -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- * boost_1_35_0.tar.bz2 * ~/Desktop/boost_1_35_0> pwd /boot/home/Desktop/boost_1_35_0 ~/Desktop/boost_1_35_0> ./configure --includedir=/boot/develop/headers/ --libdir=/boot/home/config/lib/ * ~/Desktop/boost_1_35_0> make install * after making a lot of targets, mostly copying the boost headers to the destination directory, the memory of kernel team increases constantly and then happens the 'vfork: Out of memory'. From that moment, it's impossible to build the rest 163 targets, if you try again the 'make install'; see vfork.png and ProcessController-status.png, the memory is never freed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 21:23:43 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 19:23:43 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.d1b77c53e05309f622bf99285228182a@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): Hi stippi, One thing that strikes me as immediately odd is that the ScrollTo hooks don't seem to be getting called....at least the printfs in said hooks aren't showing up at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 21:30:40 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 19:30:40 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.f5bcb59ea0b6551245b3821fb3d3f58c@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Could you give the top of the screen (before Welcome to the kernel land) ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 21:50:19 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 19:50:19 -0000 Subject: [Haiku-bugs] [Haiku] #2239: kernel doen't free memory that was requested from userspace programs In-Reply-To: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> References: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> Message-ID: <052.6a3f64cd7c8f4a3cf15d29ad82a481e6@haiku-os.org> #2239: kernel doen't free memory that was requested from userspace programs ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): revision is r25539 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 22:07:05 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 20:07:05 -0000 Subject: [Haiku-bugs] [Haiku] #2239: kernel doesn't free memory that was requested from userspace programs In-Reply-To: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> References: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> Message-ID: <052.2f47aab4a31d3e6ade4bc70f72750464@haiku-os.org> #2239: kernel doesn't free memory that was requested from userspace programs ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by kaoutsis): * summary: kernel doen't free memory that was requested from userspace programs => kernel doesn't free memory that was requested from userspace programs -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 22:40:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 20:40:46 -0000 Subject: [Haiku-bugs] [Haiku] #2239: kernel doesn't free memory that was requested from userspace programs In-Reply-To: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> References: <043.cfcc5642cbf0318dc9e7779a453a4cd4@haiku-os.org> Message-ID: <052.e65f8549da897a8d358b40f15b06e822@haiku-os.org> #2239: kernel doesn't free memory that was requested from userspace programs ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by ddew): If it helps I experience the same issue when building haiku in haiku. Restarting the build fails with the same error but a reboot sorts it out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 22:53:22 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 20:53:22 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.c12076737ad01a03b85bdd2ce1c87946@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by axeld): As I recall, the logo area is too small to have a Haiku writing in there that could look good. Besides that, I like the leaf, and I think it's nice trying to connect this to Haiku when it comes to operating systems. You rarely see screenshots completely out of context, and don't know what system you see running. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 22:58:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 20:58:00 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.18dd8cd9cdfd74452ab56c6de1ed504f@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by stippi): When I designed the new Deskbar menu button, I started out with the Haiku name and arrived at the current logo after a lot of tries. The problem with the Deskbar along the top or bottom needs to be fixed of course. I guess if I was using it that way, it would have annoyed my enough to motivate a fix by now. (I guess my fix would simply be to make the button wider.) If no one beats me to it, I will probably fix it eventually. Personally, I don't feel that the word "Haiku" on screenshots is a strong enough reason if it doesn't actually look better. I think a graphical logo can be a strong or even a stronger association, it doesn't have to be a word. Microsoft is doing this in Vista and Apple does it since ages in Mac OS. Linux desktops are doing it as well. IMHO, the leaf or feather (I don't take sides on that one :-) is just more tasteful. That being said, if someone comes with a better looking logo that integrates the word "Haiku", then we can change it of course. It has to be convincing and pretty obviously better though, IMHO. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 23:06:18 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 21:06:18 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.bbc2edf071a1de809e5a074957e0ce4a@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): Doh... just change BScrollBar::ValueChanged() to call ScrollTo() instead of ScrollBy(). That should do it. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 23:07:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 21:07:00 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.e39b9c0a5253e656c017506235df8671@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): Thanks for tracking this one down, Rene! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 18 23:09:50 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 21:09:50 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.6acf69d2f4ac9fa052a38ed19081e919@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by stippi): I feel very stupid now, because I was looking at BScrollBar::ValueChanged() _very_ often. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 00:16:33 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 22:16:33 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.de8968de9f34be8daf9e9a4319465704@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Uppps! sorry .. It should be: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0x41445303, ip 0x800abcb7 }}} If you need a new complete screenshot I can give it toworrow. As additional information: - It does not crash under GCC4 version of Haiku. But still cannot test the driver because of another crash which is not related to the media_server or to the driver. (Out of Topic: Should I file tickets for crashes that occours in GCC4 version, but does not occour in GCC2 version?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 00:19:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 22:19:09 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.6b2a0444f0273e2a8f3901d0b091c6c2@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): I was finally able to reproduce this, too. PANIC: ahci fatal error, is 0x20000000 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> pcistatus domain 0, bus 0, dev 0, func 0, PCI device status 0x1090 Received Target-Abort domain 0, bus 0, dev 1, func 0, PCI device status 0x0010 domain 0, bus 0, dev 1, func 0, PCI bridge secondary status 0x0000 domain 0, bus 0, dev 1, func 0, PCI bridge control 0x001b domain 0, bus 1, dev 0, func 0, PCI device status 0x0018 domain 0, bus 1, dev 0, func 1, PCI device status 0x0010 domain 0, bus 0, dev 26, func 0, PCI device status 0x0290 domain 0, bus 0, dev 26, func 1, PCI device status 0x0290 domain 0, bus 0, dev 26, func 7, PCI device status 0x0290 domain 0, bus 0, dev 27, func 0, PCI device status 0x0010 domain 0, bus 0, dev 28, func 0, PCI device status 0x0010 domain 0, bus 0, dev 28, func 0, PCI bridge secondary status 0x0000 domain 0, bus 0, dev 28, func 0, PCI bridge control 0x0003 domain 0, bus 0, dev 28, func 4, PCI device status 0x0010 domain 0, bus 0, dev 28, func 4, PCI bridge secondary status 0x0000 domain 0, bus 0, dev 28, func 4, PCI bridge control 0x0003 domain 0, bus 0, dev 28, func 5, PCI device status 0x0010 domain 0, bus 0, dev 28, func 5, PCI bridge secondary status 0x0000 domain 0, bus 0, dev 28, func 5, PCI bridge control 0x0003 domain 0, bus 0, dev 29, func 0, PCI device status 0x0290 domain 0, bus 0, dev 29, func 1, PCI device status 0x0290 domain 0, bus 0, dev 29, func 2, PCI device status 0x0298 domain 0, bus 0, dev 29, func 3, PCI device status 0x0290 domain 0, bus 0, dev 29, func 7, PCI device status 0x0290 domain 0, bus 0, dev 30, func 0, PCI device status 0x0810 Signalled Target-Abort domain 0, bus 0, dev 30, func 0, PCI bridge secondary status 0x2280 Received Master-Abort domain 0, bus 0, dev 30, func 0, PCI bridge control 0x0823 domain 0, bus 5, dev 0, func 0, PCI device status 0x0290 domain 0, bus 5, dev 1, func 0, PCI device status 0x0230 domain 0, bus 0, dev 31, func 0, PCI device status 0x0210 domain 0, bus 0, dev 31, func 2, PCI device status 0x22b8 Received Master-Abort domain 0, bus 0, dev 31, func 3, PCI device status 0x0280 kdebug> traced * 420238. [ 7] 566882313: ahci port - prd table - controller: 0x90d65240, index: 2, address: 0x7fff5000, size: 4096 420239. [ 7] 566883592: ahci port - prd table - controller: 0x90d65240, index: 2, address: 0x80004000, size: 4096 printed 30 entries within range 420210 to 420239 (30 of 420239 total, 420239 ever) PCI: [dom 0, bus 0] bus 0, device 31, function 2: vendor 8086, device 2922, revision 02 PCI: class_base 01, class_function 06, class_api 01 PCI: vendor 8086: Intel Corporation PCI: device 2922: 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller PCI: info: Mass storage controller (SATA controller, AHCI 1.0) PCI: line_size 00, latency 00, header_type 00, BIST 00 PCI: ROM base host 00000000, pci 00000000, size 00000000 PCI: cardbus_CIS 00000000, subsystem_id 7345, subsystem_vendor_id 1462 PCI: interrupt_line 0b, interrupt_pin 02, min_grant 00, max_latency 00 PCI: base reg 0: host 0000c000, pci 0000c000, size 00000010, flags 09 PCI: base reg 1: host 0000bc00, pci 0000bc00, size 00000010, flags 0d PCI: base reg 2: host 0000b880, pci 0000b880, size 00000010, flags 09 PCI: base reg 3: host 0000b800, pci 0000b800, size 00000010, flags 0d PCI: base reg 4: host 0000b480, pci 0000b480, size 00000020, flags 01 PCI: base reg 5: host dffff000, pci dffff000, size 00000800, flags -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 00:48:47 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 22:48:47 -0000 Subject: [Haiku-bugs] [Haiku] #2240: CPU 3 halted! Message-ID: <050.f54dae99b367b6b8eb6cb739b6bcd6f8@haiku-os.org> #2240: CPU 3 halted! -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- I've seen haiku deadlock after printing "CPU 3 halted!" to serial output. Normally, this would be followed by CPU 2, 1 and drop into KDL, but it doesn't. Seen with r25523 and again today with r25553. Happens randomly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 01:01:20 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 23:01:20 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.29d7edeb051b01d3a8688c8aa9a60dd2@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): I found the problem: PRD table: kdebug> dw 0x8016d580 [0x8016d580] .p.............. 80007000 ffffffff 00000000 00000fff kdebug> dw 0x8016d590 [0x8016d590] .??............. 09c7e000 00000000 00000000 000007ff -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 01:20:17 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 23:20:17 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.9e3ea744d6b0b3f2048b7842a455aa18@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: assigned Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by marcusoverhagen): some test code: #include typedef unsigned long addr_t; typedef unsigned long long uint64; int main() { char *p = (char *)0x80004000; printf("p = %p\n", p); printf("(unsigned long) = %lx\n", (unsigned long)p); printf("(uint64) = %llx\n", (uint64)p); printf("(uint64) (addr_t) = %llx\n", (uint64)(addr_t)p); printf("(uint64) (addr_t) >> 32 = %llx\n", ((uint64)(addr_t)p) >> 32); printf("(addr_t) >> 32 = %lx\n", ((addr_t)p) >> 32); } marcus at dagobert:~/develop/haiku/src$ gcc pointer.c pointer.c: In function ?main?: pointer.c:11: warning: cast from pointer to integer of different size pointer.c:14: warning: right shift count >= width of type marcus at dagobert:~/develop/haiku/src$ ./a.out p = 0x80004000 (unsigned long) = 80004000 (uint64) = ffffffff80004000 (uint64) (addr_t) = 80004000 (uint64) (addr_t) >> 32 = 0 (addr_t) >> 32 = 80004000 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 01:49:47 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 23:49:47 -0000 Subject: [Haiku-bugs] [Haiku] #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 In-Reply-To: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> References: <039.bfc901636bbf6a21745b2eaebf18b155@haiku-os.org> Message-ID: <048.76ac0e768d8063daa8736852533d069e@haiku-os.org> #2021: AHCI fatal error when checking out the SVN tree on Haiku r24735 ---------------------------+------------------------------------------------ Reporter: ddew | Owner: marcusoverhagen Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * status: assigned => closed * resolution: => fixed Comment: The bug is fixed in r25557. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 01:52:28 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 18 May 2008 23:52:28 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.f4f9d8a22d22585bbcf7d34c1cdce7bf@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): If that's the case, shouldn't we modify BView::ScrollBy so it just wraps a call to the virtual version? AFAIK the virtual hook should be called in all cases, otherwise the app can't always get correct behavior, since ScrollBy is not overrideable. Replacing ScrollBy with ScrollTo in ValueChanged does indeed make BCLV behave correctly here btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 02:08:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 00:08:42 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.f6eacc64dd2d3ed375b36aae17b24708@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): Also, this would seem to imply that it is indeed also the cause of ticket #1252, though I'll need to test if that one behaves correctly with that change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 02:17:18 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 00:17:18 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.0646745ed7eca9a12c0d9f118069a852@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): Should be fixed in r25559, please verify. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 02:17:40 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 00:17:40 -0000 Subject: [Haiku-bugs] [Haiku] #1838: Horizontal scrolling is broken in BColumnListView. In-Reply-To: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> References: <041.180041d994286fcdb14887f232be26cc@haiku-os.org> Message-ID: <050.8ad553897f40bfbd68d76bda14f25eb6@haiku-os.org> #1838: Horizontal scrolling is broken in BColumnListView. ---------------------------------+------------------------------------------ Reporter: stippi | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Fixed in r25559. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 02:21:50 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 00:21:50 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.dcca0adec816fdd691019cc896e02c06@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by anevilyak): * owner: stippi => anevilyak -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 02:21:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 00:21:58 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.fe819a264ff642894e409e432d8adfe6@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 12:27:43 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 10:27:43 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.cb0cb03d7f05fe97f62749d28e943ecd@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_servers_registrar_TRoster.cpp.diff: * removed unused variable static const char *const kVitalSystemAppPathPrefix * use of find_directory() & BPath & co. * use of D(PRINT()) macro to return errors -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 12:55:30 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 10:55:30 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.e25b8afaf39090ddcd32bc4693836d1f@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_servers_debug_DebugServer.cpp.diff: * updated to r25560 * also take into account the returned status values of BPath::Append() -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 14:56:26 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 12:56:26 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.fa320b895c9df88f2d96e0023375cf80@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): My laptop (Dell Inspiron 1100 with i845 and ich4 chipset) just started to crash with the auich driver similarly as well. It just started to happen after the recent auich changes I think. It never did work properly with the auich driver before either - making horrible noise when trying to play sound, and then a bunch of crackling sounds when I rebooted out of Haiku. I've been too lazy to report it, but now that it crashes, it's clearly something that I should report. I can also provide some serial logs for my laptop, but not until the end of this week (since I'm out of town currently using the laptop for business). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 15:26:55 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 13:26:55 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.a70ff4da8682e6096a5654c8e0e38bf4@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by nutela): Thanks for the feedback. I think we can agree that having the name in the logo and having a clear- to-see menu entry are 2 different things. I agree that the name in the logo is purely a marketing thing except when used as a reference in a manual like "like click the logo with the word Haiku next to it". Here are my thoughts about the clear-to-see menu entries. My problem with lots of menu's like these is that you can't tell which is the 'main' one, take KDE's bar or Gnome's bar, at work we have a few systems, Red Hat and Suse mainly, I frequently search for an application, settings and status -menu only to find it after I have clicked other symbols (I frequently launch a terminal or some other thing by clicking on the wrong widget) and then I think by myself [sarcasm on] "Duh, so this tiny 16x16 little red thing (red hat) is the entry, well terrific!" [sarcasm off] At least Suse used a tiny triangle (arrow) to discern between an regular shortcut icon and a menu. Suse version 10.x has got a nice "start menu" IMHO although the tabs are rather difficult to distinguish from the active one (it is still far better then XP's). It think it helps that the logo has a different size and aspect ratio the all other icons and widgets. MS's OTOH Start-logo maybe sounds dumb, it is pretty obvious. You can't get much more clear then that IMHO. The same applies for my cellphone's (Sony Ericson K750i) menu entry "Menu" So to conclude, this menu entry should "stand out", glow or something similar when mouse is over it (if only if it would be the single thing which would do that in the entire OS) too show it is clickable, something more than the gazillion of functionality which is waiting to be discovered by the user. Of course it would be nice if the menu entry would be pretty as well, a blue leaf is a little bit illogical, I thought Haiku's theme was 3 leafs, red, green and yellow? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 15:31:04 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 13:31:04 -0000 Subject: [Haiku-bugs] [Haiku] #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) In-Reply-To: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> References: <041.efe9bdb3698ab501b79efe3a396997ff@haiku-os.org> Message-ID: <050.72f5283d916f234f16d7aaf8d88fbb1c@haiku-os.org> #2234: put Haiku's name into Haiku's DeskBar (Like BeOS R5) -----------------------------+---------------------------------------------- Reporter: nutela | Owner: stippi Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by nutela): I can't seem to edit? I mean to say in the stand-out-part that the DeskBar menu button should be different from all other "gazillion of functionality" like widgets and other graphical gling and bling we can witness on the web and other 'modern' operating systems. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 15:35:07 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 13:35:07 -0000 Subject: [Haiku-bugs] [Haiku] #2185: Scan the source tree and use find_directory() where appropriate (no hard-coded paths anymore) In-Reply-To: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> References: <043.d4c2c44caf774ea60d9aff32d010fd33@haiku-os.org> Message-ID: <052.d8cc2ce2b29fd768e3ad5c63a9d38fb8@haiku-os.org> #2185: Scan the source tree and use find_directory() where appropriate (no hard- coded paths anymore) --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_apps_processcontroller_PCWorld.cpp.diff: * find_directory() and friends. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 18:11:32 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 16:11:32 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.6d48629bfce7bf896181c8d079fad95b@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by humdinger): Thanks yak. If nobody beats me to it, I will verify as soon as there's a vmware image available that contains r25559. Sadly something's broken in http://haiku-files.org/ . No new images since May 12. The Build Factory is at r25551 or something... The build logs there are also quite out of date: r23722 from January 24. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 18:36:15 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 16:36:15 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.236c447e9e231e506248f8e8408a8255@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by anevilyak): That'd be cool, I don't really have a good BeShare setup to test with, but I'm 99% certain it's the same issue since it would've affected more or less anything that needed custom behavior on scroll. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 19:22:13 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 17:22:13 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.d8ac0f243a94f7cba47631b5d34f884e@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Could you try again with r25562 please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 19:43:18 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 17:43:18 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.135b2aac2e46fb4146c9f47d2d688d3c@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): It seems it is fixed, thanks. Now I tested the updated driver, but I couldn't get any sound. I looked at "Media Preferences" and saw in "AC97 mixer" that all controls were muted. (not the Audio Mixer but AC97 Mixer) So I unmuted them but there wasn't any change. Closed the Preferences windows and opened it again. And again the AC97 Mixer controls were all muted, even tough I changed them for sure. Seems it doesn't change the setting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 20:58:57 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 18:58:57 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.543eb75f9720ff6f8798cee12d388620@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): It's funny, when I enable debugging from debug.h it just works. When i disable again it brakes again. I noticed that it finds Vendor ID in DEBUG mode, but not in NON-DEBUG mode. I attached the log files. I hope it helps ... Tested with r25563. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 21:18:12 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 19:18:12 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) Key requires a double keypress to be displayed Message-ID: <042.cf3ad6eb421bab67c53692eb72a67162@haiku-os.org> #2241: ~ (tilda) 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 Platform: All | -----------------------+---------------------------------------------------- At first I just thought I have a bad key on my keyboard, but now I've noticed it happens only when I'm in Haiku and happens on any keyboard I've used in Haiku so it seems it's a haiku bug. Not sure if this is related to an already reported bug or not though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 21:37:03 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 19:37:03 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.909a1bd3ec83fa66df230ccfeb36dd94@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Added a patch which could fix the above problem. (The fix works for me). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:06:00 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:06:00 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.50b82a7d5117d3a3ddaccc5e1391f739@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Looked in the patch. Weird, did the driver work before the ac97 regression ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:46:08 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:46:08 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.517f870b7a8ed1bad47209d3749a282d@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): I didn't have any problem before the AUICH update. And also i tried several times after my fix, actually it does not fix completely. But it fixes the problem with the codec Vendor id retrival. Even tough it finds the codec id correctly sometimes i can't hear any sound.(I could hear in debug mode). Will try to increase the snooze time and see what happens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:46:07 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:46:07 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation Message-ID: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Required by wine specs: http://www.opengroup.org/onlinepubs/000095399/functions/pthread_attr_setscope.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:46:23 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:46:23 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation In-Reply-To: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> References: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> Message-ID: <052.7018807e640cb8312c7134cfa8bac626@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by kaoutsis): * type: bug => enhancement -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:52:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:52:42 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.4602ad89b8231d69f71a68eaa80b9dc0@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Commited fix for currently last known bug in r25565 and also added OHCI to the image. Please feel invited to extensively test it out. It should work for all devices that do not need isochronous transfers which means mice, keyboards, hubs, memory sticks, usb network adapters, usb serial adapters... should work now (but only if a driver is present of course). Note however that some of these devices might use EHCI and not OHCI (which should have made them work even before OHCI was implemented). You can verify what devices are present by looking through "/dev/bus/usb" (with "find /dev/bus/usb" for example) and read out device infos with the usb_dev_info command. Check the output of "usb_dev_info /dev/bus/usb/x/hub" of the "x" where your device is listed under to see if it is attached to a OHCI or EHCI roothub. If you want to really stress test you could also remove the "/boot/beos/system/add- ons/kernel/busses/usb/ehci" so all devices are forced to use OHCI. Please report back here if you encounter errors. Syslogs and output of usb_dev_info will be helpful in those cases. I can guide you for further debugging if necessary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 22:57:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 20:57:58 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation In-Reply-To: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> References: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> Message-ID: <052.3201e4c540e8d8b7fbf14d776af3ec4b@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): {{{ make[1]: Leaving directory `/boot/home/Desktop/wine-1.0-rc1/include' make[1]: Entering directory `/boot/home/Desktop/wine-1.0-rc1/loader' gcc -c -I. -I. -I../include -I../include -Wall -pipe -fno-strict- aliasing -Wwrite-strings -Wpointer-arith -g -O2 -o pthread.o pthread.c /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c: In function `create_thread': /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c:117: warning: implicit declaration of function `pthread_attr_setscope' /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c: In function `exit_thread': /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c:192: warning: `noreturn' function does return /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c: In function `abort_thread': /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c:202: warning: `noreturn' function does return gcc -c -I. -I. -I../include -I../include -Wall -pipe -fno-strict- aliasing -Wwrite-strings -Wpointer-arith -g -O2 -o main.o main.c gcc -o wine-pthread -Wl,--export-dynamic pthread.o main.o -L../libs/wine -lwine ../libs/port/libwine_port.a -Wl,--rpath,\$ORIGIN/../libs/wine pthread.o: In function `create_thread': /boot/home/Desktop/wine-1.0-rc1/loader/pthread.c:117: undefined reference to `pthread_attr_setscope' collect2: ld returned 1 exit status make[1]: *** [wine-pthread] Error 1 make[1]: Leaving directory `/boot/home/Desktop/wine-1.0-rc1/loader' }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 23:01:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 21:01:19 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation In-Reply-To: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> References: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> Message-ID: <052.56e50f7d92c87aa8688ee08e62120519@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Irrelevant, but makes good to the 'haiku' psychology, at least mine :-) {{{ ~/Desktop/wine-1.0-rc1/tools/wrc> ./wrc --version Wine Resource Compiler version 1.0-rc1 Copyright 1998-2000 Bertho A. Stultiens 1994 Martin von Loewis ~/Desktop/wine-1.0-rc1/tools/wrc> ls -lh /boot/home/config/lib/libwine.so* lrwxrwxrwx 1 baron root 12 May 19 23:28 /boot/home/config/lib/libwine.so -> libwine.so.1 lrwxrwxrwx 1 baron root 14 May 19 23:28 /boot/home/config/lib/libwine.so.1 -> libwine.so.1.0 -rwxr-xr-x 1 baron root 6.2M May 19 23:04 /boot/home/config/lib/libwine.so.1.0 ~/Desktop/wine-1.0-rc1/tools/wrc> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 23:11:00 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 21:11:00 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.f7fc79fc6e6c2c96b80168dab1d1ec4b@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): Isn't that just the default for the US-International keymap? IOW it's just a deadkey and should be like that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 23:14:54 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 21:14:54 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.88cde3cfcfaa8245f669a530c99eb3bd@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by bonefish): Replying to [comment:1 axeld]: > Isn't that just the default for the US-International keymap? IOW it's just a deadkey and should be like that? Maybe, but then we should change the default keymap to American, which seems to work as expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 19 23:50:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 21:50:19 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.58e67dff3440b4a7ac9bb4b07c85e171@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): I updated a bit the ac97 reset in r25566. Hope it can help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 00:04:28 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 22:04:28 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.42a46bf4a64ced879ba9f4dfed40b3ca@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): The last patch fixed it completely, for me. I think the problem is after the cold reset initiated, it doesn't wait enough to finish the cold reset. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 00:12:09 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 22:12:09 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.12fe8521cfabfcebe1212e333b236da7@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Upps didn't see your patch. will now test it ... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 00:19:42 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 22:19:42 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.ea1829ca8629f2158a9167028de25cfc@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Works great! Thanks. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 01:04:36 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 23:04:36 -0000 Subject: [Haiku-bugs] [Haiku] #61: Build POSIX test suite for haiku In-Reply-To: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> References: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> Message-ID: <058.4ab58c5b7462bbba9308e2c89d49d61b@haiku-os.org> #61: Build POSIX test suite for haiku -----------------------------+---------------------------------------------- Reporter: andrewbachmann | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by bonefish): Thanks, applied in r25567. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 01:22:17 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 23:22:17 -0000 Subject: [Haiku-bugs] [Haiku] #1639: Sometimes the posix test fork_3-1 fails. In-Reply-To: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> References: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> Message-ID: <052.81b2deb8e7160cd1c535a50b3ca6bc7f@haiku-os.org> #1639: Sometimes the posix test fork_3-1 fails. --------------------------------+------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r25568. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 01:37:27 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 19 May 2008 23:37:27 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.3c77d598e45bcd1bcf5cc0e538b8066a@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by tigerdog): Excellent! I'll pick up the next nightly, install and test. Thanks for your efforts! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 04:38:30 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 02:38:30 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.c6a6e7eb74ea219bedc0a54d046b777a@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Replying to [comment:17 mmlr]: > Please report back here if you encounter errors. Syslogs and output of usb_dev_info will be helpful in those cases. I can guide you for further debugging if necessary. Thanks for working on this! We really appreciate your efforts. Anyway, I tested r25566, but it never gets past the leaf-disk icon on the boot screen. r25564, on the other hand, boots successfully. I'll attach the serial log for both revisions. I can probably get the syslog too if that will help as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 06:00:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 04:00:57 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.2596f75bd526000df4f94414f293db00@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by umccullough): Yes, it's always been this way in the default image AFAICR. Interestingly, if you execute "cd ~" and the ~ doesn't appear in the shell (because you didn't press it twice) it still changes to your home directory anyway :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 08:12:25 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 06:12:25 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.d4b97e276efd7162763b74ea0f4d99ae@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by koki): * cc: koki (added) Comment: > Isn't that just the default for the US-International keymap? > IOW it's just a deadkey and should be like that? Yes, this is in fact the expected behavior for the US-International keymap. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 08:18:12 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 06:18:12 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) Message-ID: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> #2243: KDL upon boot (before Tracker loads) ------------------------------+--------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- Haiku r25566 on an HP Pavilion zv5400us laptop. Haiku KDLs upon boot, after the Deskbar & Terminal are loaded, and before Tracker is run. 100% reproducible. Haiku will finish to load Tracker and run OK after entering "Continue" command in KDL. pcistatus/backtraces/listdev outputs and syslog attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 08:29:42 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 06:29:42 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.3bb8c2f119911472e0cef694aa0e7364@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by koki): * cc: marcusoverhagen (added) Comment: Forgot to mention: Haiku does not KDL if fw_raw driver is removed. FWIW. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:05:14 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:05:14 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.4a73461190442b831a26489769a8f1f7@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Thanks for testing and your patience :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:11:19 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:11:19 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.e05d5026bbda410b3e49c1b0beb53a6f@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by mmlr): As the firewire driver seems to cause instability for GCC4 builds too, I'd vote for removing it from the image until the issues have been sorted out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:22:33 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:22:33 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.177f3ebac02b943a9befe1b6c7276062@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): FWIW, built-in mousepad works fine now with r25477. Which means this bug seems to be fixed, so I guess it is OK to close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:24:21 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:24:21 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.95ff07af0bb450c4a07cd3da633f1767@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): Sorry, that was actually with r25566 (not r25477 as noted in previous comment). :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:26:26 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:26:26 -0000 Subject: [Haiku-bugs] [Haiku] #1749: Sound & video become choppy in MediaPlayer when mouse is moved In-Reply-To: <039.6d1bebf0df24e59e37b3660a6ceb77be@haiku-os.org> References: <039.6d1bebf0df24e59e37b3660a6ceb77be@haiku-os.org> Message-ID: <048.85090e745f2774e229d8717a23b88a76@haiku-os.org> #1749: Sound & video become choppy in MediaPlayer when mouse is moved ---------------------------------------+------------------------------------ Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by koki): FWIW, both sound and video play well now in r25566. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:33:25 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:33:25 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.20bbf01c8f852fae9967ddf73e5042fb@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => high Comment: +1! I have a machine that also only boots okay when I remove the firewire driver. I've removed it in r25572 for now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 09:26:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 07:26:36 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.7a651e1bb7c2483091931caa8a8997f4@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): This was probably caused by enabling interrupts before the handler was installed (this looked suspicious to me from the start, but didn't trigger problems with my only test card). I've fixed that in r25571 so this should not happen anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 10:16:32 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 08:16:32 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.2e3e35e8f0050adb2e4bec75a407a402@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by mmlr): I suppose then you have an OHCI controller and this was a legacy emulation issue? Could you check what USB devices you have ("find /dev/bus/usb") and then check if the touchpad is actually attached to the system using USB (using usb_dev_info on the device and the hub to see if it's actually OHCI)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 10:22:09 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 08:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #1749: Sound & video become choppy in MediaPlayer when mouse is moved In-Reply-To: <039.6d1bebf0df24e59e37b3660a6ceb77be@haiku-os.org> References: <039.6d1bebf0df24e59e37b3660a6ceb77be@haiku-os.org> Message-ID: <048.ea16da6d29c61206dd20b02b3c32e81b@haiku-os.org> #1749: Sound & video become choppy in MediaPlayer when mouse is moved ---------------------------------------+------------------------------------ Reporter: koki | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: I guess this was caused by a legacy emulated OHCI device and would be closely related to bug #1580. Closing this one now in that case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 11:17:08 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 09:17:08 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.58ed19a5ce08f4ce04041d447c0fe0db@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by stippi): But there is definitely something fishy with the ~ key. It works differently in Haiku than what I am used to. For example, if you press it and then move the cursor, it should dump the character. I think in Haiku you have to press it twice for that to happen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 12:41:34 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 10:41:34 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.d269f98ddce5e16e618fe428a2f4a424@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by marcusoverhagen): The firewire controller seems to generate a parity error, when DMA is enabled in fwohci_rx_enable(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 12:48:52 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 10:48:52 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.e704b118bc78b862cfaece3d6c0b6d1c@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): Mixed results now (with r25565): the attached serial data show the second boot which was successfull, then the third boot, which wasn't and the fourth, which wasn't either (but got further and showed a Terminal window). I didn't catch data from the first boot as I had the cable connected to the wrong serial port at that time... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 15:29:00 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 13:29:00 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.79f555cb3737d5eec8517e4be7627d70@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => assigned Comment: That adding OHCI did change the behaviour when legacy emulation is turned on does not sound so unlikely to me. Installing the OHCI driver (even if it did not actually work) should have caused the BIOS to get kicked off the OHCI controller, disabling legacy emulation. So that either turning legacy emulation off by hand or an installed OHCI driver gives the same behaviour was to be expected. Anyway, now that the OHCI driver is implemented and present by default, could you please verify if this ticket is still required? If everything works now I'd like to close it. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 15:38:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 13:38:53 -0000 Subject: [Haiku-bugs] [Haiku] #2227: Devices connected to a JMicron PATA controller are not detected. In-Reply-To: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> References: <038.f976ec578c7846f0f8da56b64f24f48c@haiku-os.org> Message-ID: <047.46ba1c1b9c0b4d7d896c3384db448f3d@haiku-os.org> #2227: Devices connected to a JMicron PATA controller are not detected. ---------------------------+------------------------------------------------ Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bga): With Marcus help, it became obviously that the problem was a result of bug #5 and happened like this: 1 - The BIOS had PNP OS enabled so it would not try to configure the devices leaving it to the OS to do that. 2 - The JMicron controller reported itself as 2 different devices but one of them had no interrupt line assigned to it. 3 - So the IDE stack would load, find the PATA controller but fail to work with it as it had no IRQ assigned. I changed my BIOS settings so the PNP OS option is now disabled (which means that the BIOS itself would configure the devices) and this resulted in better results (I am at work now, will post the syslog when I am back at home later today): 1 - The controller gets an IRQ. 2 - It seems to be correctly initialized and the attached drives (a DVR-RW drive and an HD) are detected and identified as an atapi and an ata device. 3 - But then send_command() fails on both devices and they are ignored. A side effect of whatever happens is that the HD light in the tower case keeps lit up all the time but the devices are not published to /dev/disk. Ideas? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 15:58:04 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 13:58:04 -0000 Subject: [Haiku-bugs] [Haiku] #1726: PS/2 mouse doesn't work In-Reply-To: <041.f98b41c9fc53dec56e115bb3b8eb100f@haiku-os.org> References: <041.f98b41c9fc53dec56e115bb3b8eb100f@haiku-os.org> Message-ID: <050.7763ebeae6b479fed80ab45b2fb93e14@haiku-os.org> #1726: PS/2 mouse doesn't work --------------------------------+------------------------------------------- Reporter: ekdahl | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by mmlr): * cc: mmlr (removed) Comment: Going through bugs related to OHCI... Since OHCI is now implemented and included by default, this could be further investigated if it is still an issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:12:42 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:12:42 -0000 Subject: [Haiku-bugs] [Haiku] #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found In-Reply-To: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> References: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> Message-ID: <051.a92ecbfef0660566cb82b3344920961f@haiku-os.org> #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by mmlr): As OHCI is implemented now, an updated status would be nice. The controller should now have a driver and so USB input devices should work when booted. I would be interested in hearing if it still hangs at boot sometimes. If it was related to the missing OHCI this should now hopefully be fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:25:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:25:23 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.490b99c1bce576fe2bc33460ae7494b2@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): First, there's no problem with my 1394 card on my box. This problem may be due to the PCI sub system changeset 25550 two days ago. Now PCI bus enable Parity Error and SERR by default. Some broken PCI-1394 card does not clear all the memory on-chip during boot(hardware reset?), then PCI bus parity errors =>NMI interrupt. The broken_hardware_patch may fix the bug, if so please close this ticket. Would someone help test it? ps:can we just enable bus master bit by default? Regards, JiSheng -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:34:33 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:34:33 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.d76ec0c799c9cd7edd66c8f242b7a407@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): once a bug, please report it, so I can dig into it and fix. PS: thanks mmu_man for reminding me which maybe caused the bug -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:37:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:37:53 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.dd9e328fe493e74867fa010f18b97e5b@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by marcusoverhagen): Some more info. With r25550 I enabled the PCI-PCI bridge reporting of parity errors on it's secondary side. That means, when a PCI device attached to the bridge generates a parity error, the bridge will report it as SERR, usually generating an NMI. PCI bridge configuration happens here: 97 KERN: PCI: dom 0, bus 0, dev 10, func 0, changed PCI bridge control from 0x0200 to 0x0823 98 KERN: PCI: dom 0, bus 0, dev 11, func 0, changed PCI bridge control from 0x000f to 0x082f The bridge is: 243 KERN: PCI: [dom 0, bus 0] bus 0, device 10, function 0: vendor 10de, device 00dd, revision a2 and the secondary bus is number 2 250 KERN: PCI: primary_bus 00, secondary_bus 02, subordinate_bus 02, secondary_latency 80 Where the firewire controller is located: 262 KERN: PCI: [dom 0, bus 2] bus 2, device 0, function 0: vendor 104c, device 8026, revision 00 264 KERN: PCI: vendor 104c: Texas Instruments 265 KERN: PCI: device 8026: TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) While it might be possible to not enable parity error reporting at all, or to disable it for a blacklist of broken devices, I'm not sure if it isn't the firewire driver that is guilty here. Masquerading of errors usually only leads to undetected data corruption. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:42:32 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:42:32 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.2a2af5afec94f3c1a189c0588d925b81@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by marcusoverhagen): I found a similar problem here: http://lists.freebsd.org/pipermail/freebsd- current/2004-November/042438.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:43:28 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:43:28 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.240c940ee0c3f78699e934ce9d6038db@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by marcusoverhagen): http://marc.info/?t=109967176800001&r=1&w=2 http://marc.theaimsgroup.com/?l=dragonfly-kernel&m=109967161431080&w=2 http://marc.theaimsgroup.com/?l=freebsd-current&m=109967788619188&w=2 http://lists.freebsd.org/pipermail/freebsd- current/2004-November/042476.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:50:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:50:01 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.64a18d4daaf2580ea61b7e6383f27f47@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by anevilyak): * cc: anevilyak (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 16:51:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 14:51:56 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.4b167c817417cd1fe313e34cb034e926@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): yep. There's a same bug in FreeBSD's stack. Perhaps FreeBSD now disable parity error(?I'm not sure), so the line is removed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 17:10:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 15:10:22 -0000 Subject: [Haiku-bugs] [Haiku] #2243: KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.3a8ec3185c738a009358c4b2416699dd@haiku-os.org> #2243: KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): Just for the record, while I didn't have a KDL, when the FW driver is installed, the system hangs completely. I haven't yet tested again with the parity check enabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 17:04:47 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 15:04:47 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.6b04ba1b951b9280e818463edb1929b0@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Just tested r25573, and it still hangs at the same spot. I'll attach the serial log. If there's anything else I can provide or do, just ask. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 17:17:27 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 15:17:27 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.61ac47151ea390ee88a42ef40a024f03@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by jackburton): If I connect the external USB mouse on my laptop (OHCI), the system hangs. There is no output in the syslog when this happens. I can provide the complete syslog (with the mouse disconnected) if needed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 17:44:16 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 15:44:16 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.9ab6d66f9b1af0af14fd22f12e95c42a@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Replying to [comment:21 j_freeman]: > Just tested r25573, and it still hangs at the same spot. I'll attach the serial log. If there's anything else I can provide or do, just ask. In fact it isn't the same spot. In the first syslog you attached the OHCI didn't seem to be installed at all. Now in the new one it seems to be present. It's interesting though that it hangs with and also without at around the same stage. Replying to [comment:22 jackburton]: > If I connect the external USB mouse on my laptop (OHCI), the system hangs. Is that if you boot with the mouse connected it hangs, or as soon as you hot-plug the mouse in it hangs? What you both could do is enable complete logging of all things USB by adding "#define TRACE_USB" at the top of "/haiku/trunk/src/add- ons/kernel/bus_managers/usb/usb_p.h". This should give much more details into the processes and might reveal where it actually hangs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 17:57:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 15:57:48 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.e1eb5f351f491e0de3a6ca17c6791657@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Replying to [comment:23 mmlr]: > Replying to [comment:21 j_freeman]: > > Just tested r25573, and it still hangs at the same spot. I'll attach the serial log. If there's anything else I can provide or do, just ask. > > In fact it isn't the same spot. In the first syslog you attached the OHCI didn't seem to be installed at all. Now in the new one it seems to be present. Hmm, are you referring to the file I attached called "syslog" because if so you can ignore that one. It was late last night, and that was actually from a different machine which in fact does not have OHCI. The last two serial logs seem to end exactly at the same place, the only difference (toward the end) is the lack of "More than 99% interrupts of vector 10 are unhandled" line.[[BR]] > What you both could do is enable complete logging of all things USB by adding "#define TRACE_USB" at the top of "/haiku/trunk/src/add- ons/kernel/bus_managers/usb/usb_p.h". This should give much more details into the processes and might reveal where it actually hangs. Will do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 18:12:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 16:12:36 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.3d8874fa00b2e4586fab8ebe2ccffd0e@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by humdinger): You're right. It was the same bug. It scrolls alright now. Thanks very much! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 18:16:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 16:16:01 -0000 Subject: [Haiku-bugs] [Haiku] #1252: BeShare: Userlist column-headings aren't scrolled In-Reply-To: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> References: <044.d470efb30af8fbc8bb6b61e75e633b4a@haiku-os.org> Message-ID: <053.ce90c89ab0d0801b3f9d4cfac3bbab48@haiku-os.org> #1252: BeShare: Userlist column-headings aren't scrolled ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by anevilyak): * status: assigned => closed * resolution: => fixed Comment: Thanks for testing :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 18:52:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 16:52:48 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.b69b737bd743b2b81f00da0652d7de08@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Changes (by marcusoverhagen): * summary: KDL upon boot (before Tracker loads) => Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) Comment: Regarding this issue in general, why is the firewire device transmitting that data using DMA to the system RAM? As I understand it, it is still with bad parity, because it's RAM has never been written to before (assuming the above idea is correct). That seems to happen when receiving is enabled in fwohci_rx_enable(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:16:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:16:01 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.2f14da9fdbc35813d9e9c769de5ea57a@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you try again with r25574 please ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:23:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:23:24 -0000 Subject: [Haiku-bugs] [Haiku] #2244: No desktop icons on first boot Message-ID: <043.08dae69213062c9e40fa2ef78da0626f@haiku-os.org> #2244: No desktop icons on first boot -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- Since a couple of revisions before r25573, on first boot of Haiku, Tracker does not display the desktop icons. To have them displayed, I can either kill Tracker and restart the desktop, or reboot Haiku. This is fully reproducible on first boot, never on subsequent boots. System is SMP. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:31:59 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:31:59 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.014e480a37e1e86ceaba6d3f66f01dd1@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by andreasf): I have successfully booted Haiku, used a hot-plugged IntelliMouse Explorer 4.0 and mounted a FAT partition from a hot-plugged no-name flash stick. Everything working fine, except the mouse too fast for my taste. ;-) If you'd like me to test anything in particular or want serial logs for comparison, let me know. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:37:48 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:37:48 -0000 Subject: [Haiku-bugs] [Haiku] #2244: No desktop icons on first boot In-Reply-To: <043.08dae69213062c9e40fa2ef78da0626f@haiku-os.org> References: <043.08dae69213062c9e40fa2ef78da0626f@haiku-os.org> Message-ID: <052.158556bdb2efcd5118d94abb472763ad@haiku-os.org> #2244: No desktop icons on first boot ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: x86 ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: Duplicate of bug #2212. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:40:08 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:40:08 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.b293257db8ac0fe0ccecef2765e8e677@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Comment (by korli): Could you check it's still working with r25574 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:47:47 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:47:47 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.6e1c769c6cc16e8f39118a914c0050ff@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by andreasf): With mouse attached, same boot issue here. Serial log attached. When it appears to hang, the last things were the entries about usb_disk followed by uhci: no devices found; then after some time, the IDE errors start pouring in. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:53:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:53:10 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.408cb1e9236e550c16b53f8ed69dab4c@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by koki): I believe the mousepad is PS/2; but here is the output of "find /dev/bus/usb" anyway: /dev/bus/usb /dev/bus/usb/0 /dev/bus/usb/0/hub /dev/bus/usb/1 /dev/bus/usb/1/hub /dev/bus/usb/2 /dev/bus/usb/2/hub /dev/bus/usb/raw HTH. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 19:59:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 17:59:01 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.5d56d0cb2d854ad6ce885c47d36299f7@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Changes (by andreasf): * cc: andreasf (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 20:14:21 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 18:14:21 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.5a1826970c85e970b6809956f3b2b2af@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): j_freeman: I suppose you do have something attached to the ports when booting too? If so could you try if booting without a device works for you? Also when it hangs at boot could you try getting into KDL by pressing f12 and then run the "ints" command and see if there is some insanely high number on any of the interrupts line (in the handled count column most probably). Andreas: That's interesting. Could you also check the "ints" command in KDL and look for high numbers? I suppose that it is still an interrupt flood that is triggered. Probably due to the roothub change notification when a device is already plugged in. Thanks for testing! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 20:52:31 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 18:52:31 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.84ad6eafdb3fed04fb0ce21029c837dd@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Hi again (Stephan :) I've placed the harddisk containing Haiku-OS in my other system (the 'old' P4-2800 533Mhz FSB Asus board). This system has a GeForce2ti (NV15) in it. It behaves the same: that is, the acceleration engine doesn't yield any results, nor does it crash. I've checked the syslog and saw Haiku OS is doing a number of things different (rather: extra) compared to R5/dano: - The EDID info block is fetched from the connected screen to determine the max (or native) resolution of this screen; - Haiku-OS switches to that mode using a VESA BIOS call (I guess). This is done before the switch takes place to protected mode (VESA 2.0 and 3.0 both work correctly on my systems here). I've looked at the AGP busmanager messages: they are only there if the nvidia driver is in place: Hence the busmanager is only called by the gfx (kernel) driver as it should be (just like in R5/dano). All in all everything looks nice and dandy :-) I'm getting the real BeOS feeling here guys! Haiku works neat.. (just a few KDL's still). And it's a bit slow in drawing yet? OK, Because the VESA EDID and Setmode calls are not done on R5/dano I decided to test with 'multiple' (ok: 2) gfx cards in the P4 system. Primary BIOS card was a PCI G200 (Matrox) and the AGP NV15 was 'not used'. Using the nvidia driver I am telling R5 and Haiku to use this one for the desktop instead of the Matrox card. Looking at the syslog after a system boot/shutdown cycle I see Haiku fetching EDID and BIOS info from the MAtrox card. The spashscreen displays there and the resolution is switched OK. After the app_server starts up the nvidia card is initialized (coldstarted, using ananog VGA connection to screen). The Desktop comes up and the system is running OK. The acceleration engine is still down however. Conclusion, the BIOS calls are not the problem. So, I think I tested everything I could now (well, more or less), and the system behaves OK, just like the driver on R5/dano. On Haiku however the acceleration engine doesn't do it's thing. I think I'm looking at a compiler problem or something (I've seen it before with the 2D driver causing the 3D accelerant to nolonger function: it was a shared_info struct variable size compiler interpretation difference using different versions of the compiler.). Looks like I'll need to do a bughunt through shared_info once again. Or some other variable. Anyone any ideas or pointers for me maybe??? I'll continue searching when I have time again, hopefully within a week or two max. Bye for now! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 21:14:34 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 19:14:34 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.ad1ddfc583ba9d7f9eb6bf5483be434b@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): Tested and works fine! ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 21:15:29 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 19:15:29 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.914152f72e021fbe1769b2510f8fd5e5@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by andreasf): Replying to [comment:27 mmlr]: > Could you also check the "ints" command in KDL and look for high numbers? I suppose that it is still an interrupt flood that is triggered. This is after waiting a couple of seconds: {{{ KDiskDeviceManager::_Scan(/dev/disk/usb) usb_uhci: no devices found CPU 1 halted! PANIC: Keyboard Requested Halt Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> ints int 0, enabled 1, handled 0, unhandled 0 0x8009fc74 int 1, enabled 1, handled 0, unhandled 0, ACTIVE 0x8009d6b0 int 6, enabled 1, handled 0, unhandled 0 0x80277b30 int 10, enabled 1, handled 0, unhandled 0 0x80277b30 int 11, enabled 3, handled 1566713, unhandled 0 0x80277b30 0x805c3aa0 0x805c3aa0 int 14, enabled 1, handled 217, unhandled 0 0x805c3aa0 int 15, enabled 1, handled 32, unhandled 0 0x805c3aa0 int 219, enabled 1, handled 12017, unhandled 0 0x8009ecb8 int 221, enabled 1, handled 603, unhandled 0 0x8009eccc int 222, enabled 1, handled 0, unhandled 0 0x8009ecf4 int 223, enabled 1, handled 0, unhandled 0 0x8009ece0 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 21:18:44 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 19:18:44 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.85c75b07fb08b8767a2bc2785f24a03e@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Replying to [comment:27 mmlr]: > j_freeman: I suppose you do have something attached to the ports when booting too? If so could you try if booting without a device works for you? Also when it hangs at boot could you try getting into KDL by pressing f12 and then run the "ints" command and see if there is some insanely high number on any of the interrupts line (in the handled count column most probably). Yes, I had a webcam and a Microsoft mouse connected. It boots fine with them disconnected, but about every second this is output over the serial debug: {{{ usb_ohci_roothub: request: 0 usb_ohci: port 0 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 1 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 2 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 3 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 4 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 5 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 6 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 7 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 8 status 0x0100 change 0x0000 usb_ohci_roothub: request: 0 usb_ohci: port 9 status 0x0100 change 0x0000 }}} It just keeps printing that out over and over, even after Tracker and the Deskbar have been loaded. Then I tried booting with the mouse connected, and I went into KDL and gave an "ints" command as you instructed: {{{ usb_ohci: version 1.0, legacy support USB Stack: allocating 256 bytes for USB OHCI Host Controller Communication Area USB Stack: area = 0x000000dc, size = 4096, log = 0x802ae000, phy = 0x03e4a000 usb_ohci: cold started usb_ohci: port count is 10 usb_ohci: installing interrupt handler usb_ohci: OHCI Host Controller Driver constructed usb_ohci: root hub status change Last message repeated 2416715 times. CPU 0 halted! PANIC: Keyboard Requested Halt Welcome to Kernel Debugging Land... Running on CPU 1 kdebug> ints int 0, enabled 1, handled 0, unhandled 0 0x8009fc74 int 1, enabled 1, handled 0, unhandled 0, ACTIVE 0x8009d6b0 int 5, enabled 2, handled 8, unhandled 0 0x805c4aa00x805c4aa0 int 10, enabled 3, handled 2416716, unhandled 0 0x802a239c0x805c4aa00x805c4aa0 int 11, enabled 2, handled 12, unhandled 4 0x805c4aa00x805c4aa0 int 14, enabled 1, handled 398, unhandled 0 0x805c4aa0 int 15, enabled 1, handled 0, unhandled 0 0x805c4aa0 int 219, enabled 1, handled 11417, unhandled 0 0x8009ecb8 int 221, enabled 1, handled 736, unhandled 0 0x8009eccc int 222, enabled 1, handled 0, unhandled 0 0x8009ecf4 int 223, enabled 1, handled 0, unhandled 0 0x8009ece0 kdebug> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 21:35:30 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 19:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #2245: OpenGrok search is very much out of date Message-ID: <050.52e169c3eecc428c1bb91eccc4bcb163@haiku-os.org> #2245: OpenGrok search is very much out of date -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: R1 Component: Website | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- The OpenGrok search at http://haiku.it.su.se:8180/source/ is very much out of date. It doesn't even include changes that were done more than 4 month ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 21:44:53 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 19:44:53 -0000 Subject: [Haiku-bugs] [Haiku] #1580: Mouse freezes (permanently or intermittently) after brief movement In-Reply-To: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> References: <039.c5f04878714f48c6a8bd56b57271fca7@haiku-os.org> Message-ID: <048.2c468dda42cf91fadbd5c8a4ad68ebe5@haiku-os.org> #1580: Mouse freezes (permanently or intermittently) after brief movement --------------------------------+------------------------------------------- Reporter: koki | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Resolution: fixed | Platform: x86 --------------------------------+------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Yeah, in that case it seems there are no USB devices attached at all. It still might very well have been a legacy support issue. The strangest things seem to be happening when legacy support is involved... The only thing you could try to further verify that would be to remove the OHCI driver ("/boot/beos/system/add-ons/kernel/busses/usb/ohci") again and see if the behaviour returns. In any case I will resolve this ticket as fixed per your report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 22:09:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 20:09:43 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.035b6b4956e5104c7b6e92e2583ca98c@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): That's perfect, it's exactly what I expected. When booting with devices plugged in it will cause the roothub change interrupt to be triggered pretty much right away. This is not a problem, and it does in fact get handled (otherwise the unhandled count would be a huge number instead). The problem is that these interrupts do not seem to get acknowledged for some reason, so that as soon as the interrupt is handled, another one is generated right away and so on, which brings the system to a halt. {{{ usb_ohci_roothub: request: 0 usb_ohci: port 0 status 0x0100 change 0x0000 }}} That's normal behaviour. The hubs are polled for status changes every second to detect changes on connection status and handle them correctly. Once you plug something in the, change and status field will first get different, then the change will be cleared and the device becomes usable. This could be further optimized by instead of polling using the notification mechanisms to only do on demand bus exploration. USB hubs support that with a dedicated interrupt endpoint, OHCI and EHCI provide an interrupt (the very same one that probably causes the hangs in this case). These could be leveraged to remove the need for polling. Sadly UHCI does not provide such a mechanism so the polling cannot be completely removed (although it could be moved into the UHCI driver). However as it is not really an expensive thing (as the roothubs are short-circuited and do pretty direct register reads to get the status) this enhancement is not urgent at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 22:38:08 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 20:38:08 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.c439d5b3dd9e17ce11006b23648e10f5@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Bootup hangs should be fixed in r25578. Please verify. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 22:41:42 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 20:41:42 -0000 Subject: [Haiku-bugs] [Haiku] #524: [Scooby] BView doesn't follow BWindow on resize In-Reply-To: <040.c2d612b80a1a65c56839719fa724e36e@haiku-os.org> References: <040.c2d612b80a1a65c56839719fa724e36e@haiku-os.org> Message-ID: <049.420d1e9394c90fb65c8ac1d0e7254ead@haiku-os.org> #524: [Scooby] BView doesn't follow BWindow on resize ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by julun): * status: new => closed * platform: => All * resolution: => fixed Comment: This works now, tested against r25580. Dunno when it was fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 23:15:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 21:15:10 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.729c5edb46726825b1aaa23136fc9d90@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Replying to [comment:31 mmlr]: > Bootup hangs should be fixed in r25578. Please verify. The mouse isn't as smooth as PS/2 (kind of jittery), but no more boot hanging! Thanks for your work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 23:17:51 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 21:17:51 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.fc0d7f655514818b6e3a09ad15d0883e@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Replying to [comment:32 j_freeman]: > The mouse isn't as smooth as PS/2 (kind of jittery), but no more boot hanging! Thanks for your work! If you still have the debug output turned on this would be expected. Otherwise it's a bug ;-). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 20 23:57:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 21:57:43 -0000 Subject: [Haiku-bugs] [Haiku] #1639: Sometimes the posix test fork_3-1 fails. In-Reply-To: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> References: <043.dea63991d83d7b00bb54874add499658@haiku-os.org> Message-ID: <052.641aa3265b553e11dad11c94e265b5d2@haiku-os.org> #1639: Sometimes the posix test fork_3-1 fails. --------------------------------+------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Comment (by kaoutsis): Replying to [comment:3 bonefish]: > Fixed in r25568. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 00:50:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 20 May 2008 22:50:57 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.5a8e383053a7cbe8d28d7eca5e120389@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by j_freeman): Replying to [comment:33 mmlr]: > Replying to [comment:32 j_freeman]: > > The mouse isn't as smooth as PS/2 (kind of jittery), but no more boot hanging! Thanks for your work! > > If you still have the debug output turned on this would be expected. Otherwise it's a bug ;-). Ah, indeed that was why. :p -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 06:51:09 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 04:51:09 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.77d14842895b4bee19fb8ff22a0b2541@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): It now shows the Deskbar each time, but the boot process ends there; the OS freezes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 12:20:48 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 10:20:48 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.b9d150b211e4cc18d2978ceac2cd12d7@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): because once bus reset, the all sid packets(include itself) will be received. DMA is used to transmit these packets. IMO, it is still the parity problem. Because the firewire stack is ok before on koki's box. I need to find a pc with the same problem and test it, for there's no problem on my box. Any suggestions? axeld, what's the serial debug information when the system hangs? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 13:28:01 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 11:28:01 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.615d88f902bada4bc95bf051781b49f6@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by axeld): IIRC it didn't dump anything helpful, and I couldn't even enter KDL. If you have any idea on how I can dig into this more, let me know. Is it possible to gracefully handle a parity problem by turning the check off and dump a warning to syslog? If that is not possible, I think the only solution would be to turn parity checking off by default, and make it available via a config setting only (that defaults to off). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 13:39:14 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 11:39:14 -0000 Subject: [Haiku-bugs] [Haiku] #757: [app_server] deadlock on workspace switching In-Reply-To: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> References: <040.c62241fd41a75711deeeff54858e49b1@haiku-os.org> Message-ID: <049.183f414e48fc31a01d83a940521f1c38@haiku-os.org> #757: [app_server] deadlock on workspace switching ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: blocker | Milestone: R1/alpha1 Component: Servers/app_server | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): I managed to deadlock it in the same way in r25588. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 17:45:56 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 15:45:56 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.f71cc079047670a0f9493f87d0d17b13@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by koki): > Because the firewire stack is ok before on koki's box. FWIW, I actually don't know if the FW stack was OK before, as I never used it for anything. What I can say is that, if there was a problem with FW before r25566, it did not manifest itself the way it does now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 18:17:24 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 16:17:24 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.2ba2b321e3b1b047602628e880d4f165@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): it means that the firewire stack is initialized OK. > FWIW, I actually don't know if the FW stack was OK before, as I never >used it for anything. What I can say is that, if there was a problem with >FW before r25566, it did not manifest itself the way it does now. >Is it possible to gracefully handle a parity problem by turning the >check off and dump a warning to syslog? If that is not possible, I think >the only solution would be to turn parity checking off by default, and >make it available via a config setting only (that defaults to off). the broken_hardware_patch should turn off pci-1394 card parity check. But result is the there is a parity error with pci-bridge. would someone help test this new patch -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 18:22:49 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 16:22:49 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.d84b954ab65d22629e988e02b507b800@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): > would someone help test this new patch I mean only the patch2. a few lines fixed and enable postedWriteEnable bit of HCControl register. thank DeakYak explain the "posted" mean;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 20:43:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 18:43:59 -0000 Subject: [Haiku-bugs] [Haiku] #2246: [patch] tcpdump/libpcap pcap_platform_finddevs broken Message-ID: <038.b771d7bdc418eed8cc9ed0d496c89c89@haiku-os.org> #2246: [patch] tcpdump/libpcap pcap_platform_finddevs broken --------------------------------------+------------------------------------- Reporter: mjw | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- pcap_platform_finddevs implementation modifies internal libpcap structures when adding devices to the device list. However, libpcap expects the device list to be ordered in a subtle way: the first device in the list should not be a loopback device. When tcpdump was run on my machine without any arguments, the loopback device ended up as the first device in the list, which caused tcpdump to exit immediately complaining that there were no suitable devices found. This patch adds devices to the device list using pcap_add_if() to ensure the device list is suitably ordered. tcpdump can now be executed without any arguments to make it listen on a default device. I have also added suitable defines to that "tcpdump -D" will now show the list of available devices. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 21:34:48 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 19:34:48 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.0ffa47605141d377c075a04068999940@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Changes (by j_freeman): * cc: j_freeman (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 22:53:56 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 20:53:56 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.27cce29cc4298a3c6ba729155aa67b18@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Once again, could you check with r25592 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 21 23:00:46 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 21:00:46 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.3c3af7c5fb958de5e20bd406dfa5c3ba@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Comment (by herdemir): You seem to forgot the comma after "Philips", i think after r25589. {{{ "ESS Technology", "Harman International", "Nvidea", - "Philips", + "Philips" "Texas Instruments", "VLSI Technology", "TriTech", }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 01:17:43 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 23:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog Message-ID: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ If I enable my motherboard's Firewire controller, I get thousands of entries with the message in the summary. Note that this happens regardless of whether the firewire bus manager is actually loaded or not. Disabling the controller in the BIOS makes the problem go away. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 01:18:32 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 21 May 2008 23:18:32 -0000 Subject: [Haiku-bugs] [Haiku] #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog In-Reply-To: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> References: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> Message-ID: <053.e87a06e0bb8fc8d0a2fb3b59b4816b06@haiku-os.org> #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): Note also that the message volume is enough to put the CPU usage at 100% and generally slow the system to a crawl. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 05:08:52 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 03:08:52 -0000 Subject: [Haiku-bugs] [Haiku] #2241: ~ (tilda) 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.1479de6ed052e728d21947eaa32edc60@haiku-os.org> #2241: ~ (tilda) 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 Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by koki): The behavior described in this bug is the expected behavior of a deadkey; for example, pressing "~" followed by "n" will display "?". There is some strange behavior when you want to cancel input before you press the second keystroke, but it looks to me like that would probably require a different bug report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 05:12:16 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 03:12:16 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. In-Reply-To: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> References: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> Message-ID: <051.414067b06e900e6128485db1bd760d5e@haiku-os.org> #2229: Background image does not center. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by bbjimmy): Replying to [comment:2 korli]: > Can't reproduce. What's your screen resolution ? Can you provide the image ? done. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 06:12:26 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 04:12:26 -0000 Subject: [Haiku-bugs] [Haiku] #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog In-Reply-To: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> References: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> Message-ID: <053.3f8f760e2a2d2b04148b5fb7ab5b34aa@haiku-os.org> #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by anevilyak): For what's it worth by the way, Linux identifies the same FW controller as being on IRQ 19, while I see Haiku identifies it as IRQ 3... does Haiku not currently make use of IO APICs? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 06:47:42 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 04:47:42 -0000 Subject: [Haiku-bugs] [Haiku] #2236: Updated AUICH driver crashes media_addon_server ... In-Reply-To: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> References: <043.fed99334bbf4cce1caf29dff4d532654@haiku-os.org> Message-ID: <052.e4e31a9ee100db990c9ed05a9dd57dd7@haiku-os.org> #2236: Updated AUICH driver crashes media_addon_server ... ----------------------------+----------------------------------------------- Reporter: herdemir | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Comment (by umccullough): Also working properly on my Dell Inspiron now (never did before!) Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 07:45:50 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 05:45:50 -0000 Subject: [Haiku-bugs] [Haiku] #927: [nvidia] stability problems with GeForce 7300 In-Reply-To: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> References: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> Message-ID: <049.ae2629d75d67253e8cc16dde4e0e61b1@haiku-os.org> #927: [nvidia] stability problems with GeForce 7300 --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by j_freeman): * cc: j_freeman (added) Comment: It seems GeForce 7800 GT (device 0092) has started having this issue as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 08:06:06 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 06:06:06 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.28850d020441f3dcdde597a85d2bf9ce@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): (Please ignore the first attachment, r25593serial.txt. Use r25593serial2.txt instead) The last message from the log seemed to repeat forever, so I shut down the PC after a while. Perhaps because of the size of the log caused by this behaviour, copy and paste didn't save the very first part of the log, or I somehow messed up. Let me know when and if you need this part too. Sorry! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 08:25:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 06:25:41 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.aff552a64aa7438bfa04eab0105e250c@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by koki): I tried a build with the patched fw_raw (thanks Deadyak!), and it still KDLs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 09:51:29 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 07:51:29 -0000 Subject: [Haiku-bugs] [Haiku] #2246: [patch] tcpdump/libpcap pcap_platform_finddevs broken In-Reply-To: <038.b771d7bdc418eed8cc9ed0d496c89c89@haiku-os.org> References: <038.b771d7bdc418eed8cc9ed0d496c89c89@haiku-os.org> Message-ID: <047.182ca94df746334696405e10b10939ed@haiku-os.org> #2246: [patch] tcpdump/libpcap pcap_platform_finddevs broken ---------------------------------------+------------------------------------ Reporter: mjw | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: How could I miss pcap_add_if()? I was already wondering what I was doing back there :-) It definitely worked when I tested it, though; apparently the order of the interfaces might have differed in my configuration. I made some minor changes to your patch, and applied it in r25601. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 09:53:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 07:53:08 -0000 Subject: [Haiku-bugs] [Haiku] #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog In-Reply-To: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> References: <044.3c188a34b916f240b8fd1c5726875817@haiku-os.org> Message-ID: <053.f57914699a8c1080d9d27865f8ceb2c8@haiku-os.org> #2247: lots of "KERN: More than 99% interrupts of vector 3 are unhandled" messages in syslog ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): We currently only use PIC programming. I actually wanted to work on that after I'm done with the new device manager, though, as I hope it will fix some weird problems I encounter on recent hardware with the HDA driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 12:13:42 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 10:13:42 -0000 Subject: [Haiku-bugs] [Haiku] #2116: Add definition INET_ADDRSTRLEN in netinet/in.h In-Reply-To: <040.fc502c8131b2e6ed2a3f1fcca3b30f20@haiku-os.org> References: <040.fc502c8131b2e6ed2a3f1fcca3b30f20@haiku-os.org> Message-ID: <049.a06ccca6334baa4e6c848165fe8b56ed@haiku-os.org> #2116: Add definition INET_ADDRSTRLEN in netinet/in.h --------------------------------+------------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by andreasf): Update: {{{INET_ADDRSTRLEN}}} has been added in r25598. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:09:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:09:08 -0000 Subject: [Haiku-bugs] [Haiku] #2116: Add definition INET_ADDRSTRLEN in netinet/in.h In-Reply-To: <040.fc502c8131b2e6ed2a3f1fcca3b30f20@haiku-os.org> References: <040.fc502c8131b2e6ed2a3f1fcca3b30f20@haiku-os.org> Message-ID: <049.6dc56f0017b5ab110ba7a1169abd3099@haiku-os.org> #2116: Add definition INET_ADDRSTRLEN in netinet/in.h --------------------------------+------------------------------------------- Reporter: nielx | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: The IPv6 stuff should all go into netinet/in6.h. I'm closing this bug, as we don't support IPv6 yet, and INET_ADDRSTRLEN has been added in the mean time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:14:48 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:14:48 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.dd3cdf207e5747d2feb2b7c9608fd6cd@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Any other feedback? If there are no remaining issues I'd like to close this enhancement as fixed. The functionality blocking R1/alpha has been implemented and the isochronous support is tracked in the isochronous enhancement #1045. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:50:44 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:50:44 -0000 Subject: [Haiku-bugs] [Haiku] #2248: [PATCH] Fix struct issue in private net_buffer.h Message-ID: <043.5d012dadc7a319b5541d67821735b383@haiku-os.org> #2248: [PATCH] Fix struct issue in private net_buffer.h --------------------------------+------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- Bluetooth build ({{{h2generic}}} driver) on Haiku is currently broken due to lack of {{{struct}}} for {{{ancillary_data_container}}} in {{{headers/private/net/net_buffer.h}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:52:52 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:52:52 -0000 Subject: [Haiku-bugs] [Haiku] #2248: [PATCH] Fix struct issue in private net_buffer.h In-Reply-To: <043.5d012dadc7a319b5541d67821735b383@haiku-os.org> References: <043.5d012dadc7a319b5541d67821735b383@haiku-os.org> Message-ID: <052.b838b90d077fa916ed43c4104c9d1a2e@haiku-os.org> #2248: [PATCH] Fix struct issue in private net_buffer.h ---------------------------------+------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by andreasf): The above patch fixes this by adding {{{struct}}}. An alternative might be a typedef for {{{ancillary_data_container}}}. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:56:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:56:33 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.771cc6456593da9695474109b1a36a06@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): Replying to [comment:19 koki]: > I tried a build with the patched fw_raw (thanks Deadyak!), and it still KDLs. hmmm. Then moudule patched is firewire,not fw_raw. replaced wrong file? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 13:59:43 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 11:59:43 -0000 Subject: [Haiku-bugs] [Haiku] #2248: [PATCH] Fix struct issue in private net_buffer.h In-Reply-To: <043.5d012dadc7a319b5541d67821735b383@haiku-os.org> References: <043.5d012dadc7a319b5541d67821735b383@haiku-os.org> Message-ID: <052.6bd43cb017f3a846c4f5b64037ca9e54@haiku-os.org> #2248: [PATCH] Fix struct issue in private net_buffer.h ---------------------------------+------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Applied in r25606. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 14:35:08 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 12:35:08 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.cd93c94bde1f01dd75e3dab9b815c8be@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by anevilyak): The correct file was patched, I sent him a new image with your patch applied, he didn't just replace one file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 14:32:55 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 12:32:55 -0000 Subject: [Haiku-bugs] [Haiku] #1908: page_fault in network stack (using Firefox) In-Reply-To: <041.6791160cc3e1d20aeb33f16337318daa@haiku-os.org> References: <041.6791160cc3e1d20aeb33f16337318daa@haiku-os.org> Message-ID: <050.1970986153d44c47de32d005cdf69a55@haiku-os.org> #1908: page_fault in network stack (using Firefox) ---------------------------------------+------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by franxico): Replying to [ticket:1908 stippi]: > I just booted Haiku and launched Firefox without much delay. Next thing I know, I was in KDL: Just dit that a couple of times with VMWare, r25562, FF 2.0.0.12, with no problems at all. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 15:31:29 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 13:31:29 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. Message-ID: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. -------------------------+-------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- see attached error.txt -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 15:35:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 13:35:41 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. In-Reply-To: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> References: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> Message-ID: <052.05783ad78fcb4096e00a81d9098d34f4@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): some references: http://haiku.it.su.se:8180/source/xref/headers/private/kernel/elf32.h http://haiku.it.su.se:8180/source/xref/src/tools/elfsymbolpatcher/Elf.h http://haiku.it.su.se:8180/source/xref/headers/build/private/storage/Elf.h http://www.linux-foundation.org/spec/book/ELF-generic/ELF-generic.txt http://www.linux- foundation.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB_lines.txt http://refspecs.linux-foundation.org/LSB_1.1.0/gLSB/specialsections.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 15:42:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 13:42:47 -0000 Subject: [Haiku-bugs] [Haiku] #2250: Quitting Applications: 0xffff0104 in ?? () Message-ID: <041.3df926f572b39f8f86ee849e07e1d213@haiku-os.org> #2250: Quitting Applications: 0xffff0104 in ?? () --------------------------------+------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- I've noticed quite a few legacy BeOS applications run fine on Haiku, but when you quit them, they crash. I've tested a number of applications, and came up with five that crashed when exiting, and was looking to see if there was anything similar between them via the debugger. Three of the applications have 0xffff0104 in ?? () as #0. They are CrackAttack, GobeProductive, and InDepth. I've included the other two as well. Perhaps I should file individual tickets? Attached is a zipfile with the backtraces of the five apps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 15:44:13 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 13:44:13 -0000 Subject: [Haiku-bugs] [Haiku] #2251: Weird entry in /dev Message-ID: <043.5834fd25dd5cc3730f178fed4f1b81d3@haiku-os.org> #2251: Weird entry in /dev -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- In {{{/dev}}}, I see this entry at the end of `ls -l`: {{{ crw-r--r-- 1 baron root 0 May 22 13:32 \314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\314\276\255\336\357\276\255\336 }}} This is unexpected. :) System is SMP, has OHCI USB, and the Bluetooth stack was added to the image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 15:43:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 13:43:33 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.8978ed7804d74d1b941cacd23dece97f@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by tigerdog): I've been unable to test until today, when the last change made it into a nightly build. I'll test this morning (California time) and post any issues I find. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 16:03:28 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 14:03:28 -0000 Subject: [Haiku-bugs] [Haiku] #2251: Weird entry in /dev In-Reply-To: <043.5834fd25dd5cc3730f178fed4f1b81d3@haiku-os.org> References: <043.5834fd25dd5cc3730f178fed4f1b81d3@haiku-os.org> Message-ID: <052.dc8d391e6991bb57581d2d1cc9bf1dd5@haiku-os.org> #2251: Weird entry in /dev ------------------------+--------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: duplicate | Platform: x86 ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Duplicate of #1840. Can you pin it down to a change since when this happens (like adding BT)? In any case, let's continue in ticked #1840. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 16:03:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 14:03:47 -0000 Subject: [Haiku-bugs] [Haiku] #1934: tcpdump is broken. In-Reply-To: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> References: <038.551535fe70f75fd4c1d0b0eb8fc9c911@haiku-os.org> Message-ID: <047.a70f4bbdd3136bef99dc7bde7d644aac@haiku-os.org> #1934: tcpdump is broken. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Platform: x86 ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Looks like someone could still had problems... fixed by James Woodcock in r25601. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 16:04:22 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 14:04:22 -0000 Subject: [Haiku-bugs] [Haiku] #1840: Strange output from ls /dev In-Reply-To: <041.12bd45285101f826b397cf0ecf58e405@haiku-os.org> References: <041.12bd45285101f826b397cf0ecf58e405@haiku-os.org> Message-ID: <050.1c26ecf01918aca99cd49ddc1bf125ae@haiku-os.org> #1840: Strange output from ls /dev ---------------------+------------------------------------------------------ Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All ---------------------+------------------------------------------------------ Changes (by axeld): * cc: andreasf (added) Comment: Not anymore, #2251 is a duplicate of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 16:08:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 14:08:33 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. In-Reply-To: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> References: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> Message-ID: <052.0520fd1b6edbc4197da3680a4b4a8bf5@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by axeld): Are you using private Haiku headers to compile Wine? Why would you want to do that? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 16:28:04 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 14:28:04 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. In-Reply-To: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> References: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> Message-ID: <052.50d15c93cca25aa802bc3fa591d06550@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:2 axeld]: > Are you using private Haiku headers to compile Wine? Why would you want to do that? Platforms that can build wine have a public header 'elf.h'; e.g the debian linux has a /usr/include/elf.h btw: i have found a solution, but i want to check it again, before post it here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 18:10:52 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 16:10:52 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. In-Reply-To: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> References: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> Message-ID: <052.7cd9cb81c4d6c3d39efcd903d6ca15f2@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Well, we don't. It's not a part of POSIX either - if Wine needs this header, then it should be provided by the Haiku port, but you shouldn't expect to be able to use a private Haiku header for this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 18:33:13 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 16:33:13 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.983742976fda9f0dda3dfb49328c4512@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by tigerdog): Tested on system with nVidia chipset. Logitech G7 (wireless) mouse works well; not even jittery as described by j_freeman. Mouse also works when hot-plugged. USB Flash drive works. HOWEVER, I also have a separate Logitech S510 wireless USB Keyboard/mouse combo. Mouse does not work at all; keyboard is jerky, dropping characters and/or repeating them. The receiver is plugged into a KVM switch, but because they work fine under Windows XP, Windows 2000 and Ubuntu 8.04, the combination is at least known to work under other circumstances. I've tried with and without PS2 KB attached, with and without PS2 emulation in BIOS. No change in any case. I don't have serial debug capability at the moment; is there another way to provide useful information? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 18:45:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 16:45:33 -0000 Subject: [Haiku-bugs] [Haiku] #2252: KDL during untaring Message-ID: <042.c93bd56de32ec27dc08511cbdf693481@haiku-os.org> #2252: KDL during untaring -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- I'm using rev25610. I cannot reproduce it. {{{ wait interval 483251, scan pages 4690, free 1868, target 2228 check through wait interval 479541, scan pages 4720, free 1852, target 2244 wait interval 481628, scan pages 4703, free 1861, target 2235 wait interval 523376, scan pages 4366, free 2041, target 2055 wait interval 389782, scan pages 5446, free 1465, target 2631 wait interval 347802, scan pages 5785, free 1284, target 2812 wait interval 372619, scan pages 5584, free 1391, target 2705 vm_soft_fault: va 0x0 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x805b9393, write 0, user 0, thread 0x800a PANIC: vm_page_fault: unhandled page fault in kernel space at 0x0, ip 0x805b9393 Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> kdebug> kdebug> bt stack trace for thread 32778 "tar" kernel stack: 0x9397e000 to 0x93982000 user stack: 0x7efe7000 to 0x7ffe7000 frame caller :function + offset 93981390 (+ 48) 800498a3 :invoke_debugger_command + 0x00cf 939813c0 (+ 64) 8004a64c :_ParseCommand__16ExpressionParserRi + 0x01f8 93981400 (+ 48) 8004a03e :EvaluateCommand__16ExpressionParserPCcRi + 0x01de 93981430 (+ 224) 8004b760 :evaluate_debug_command + 0x0088 93981510 (+ 64) 800483de :kernel_debugger_loop__Fv + 0x017a 93981550 (+ 48) 80049091 :kernel_debugger + 0x010d 93981580 (+ 192) 80048f79 :panic + 0x0029 93981640 (+ 64) 800942c5 :vm_page_fault + 0x00b1 93981680 (+ 64) 8009e41d :page_fault_exception + 0x00b1 939816c0 (+ 12) 800a1b0a :int_bottom + 0x002a (nearest) iframe at 0x939816cc (end = 0x93981724) eax 0x0 ebx 0x805bee24 ecx 0x90ba2000 edx 0x246 esi 0x1 edi 0x90ba4000 ebp 0x93981734 esp 0x93981700 eip 0x805b9393 eflags 0x10282 vector: 0xe, error code: 0x0 939816cc (+ 104) 805b9393 :sim_scsi_io + 0x0123 93981734 (+ 64) 806a5b01 :scsi_async_io + 0x0245 93981774 (+ 96) 806b7e4f :periph_read_write + 0x01fb 939817d4 (+ 80) 806b7bfb :periph_read + 0x003f 93981824 (+ 64) 806b3d3e :das_read + 0x0042 93981864 (+ 160) 805a5bb4 :block_io_readv_int + 0x042c 93981904 (+ 80) 805a6390 :block_io_read + 0x0040 93981954 (+ 64) 8006d166 :Process__11IOSchedulerR9IORequest + 0x0052 93981994 (+ 112) 800684b5 :devfs_read__FP9fs_volumeP8fs_vnodePvxT2PUl + 0x0141 93981a04 (+ 64) 8007a156 :file_read__FP15file_descriptorxPvPUl + 0x0036 93981a44 (+ 96) 8006b4fd :_kern_read + 0x0145 93981aa4 (+ 64) 800a9f52 :read_pos + 0x0036 93981ae4 (+ 80) 80024957 :get_cached_block__FP11block_cachexPbb + 0x010b 93981b34 (+ 80) 8002760a :block_cache_get_etc + 0x004e 93981b84 (+ 64) 8057c84e :SetTo__15AllocationBlockR15AllocationGroupUs + 0x00ae 93981bc4 (+ 128) 8057d8dd :AllocateBlocks__14BlockAllocatorR11TransactionlUsUsUsR9block_run + 0x018d 93981c44 (+ 80) 8057dcf7 :Allocate__14BlockAllocatorR11TransactionP5InodexR9block_runUs + 0x018b 93981c94 (+ 288) 8058c154 :_GrowStream__5InodeR11Transactionx + 0x02f8 93981db4 (+ 48) 8058d709 :SetFileSize__5InodeR11Transactionx + 0x0069 93981de4 (+ 64) 8058bb16 :WriteAt__5InodeR11TransactionxPCUcPUl + 0x023a 93981e24 (+ 96) 80598fd0 :bfs_write__FP9fs_volumeP8fs_vnodePvxPCvPUl + 0x00d0 93981e84 (+ 64) 8007a196 :file_write__FP15file_descriptorxPCvPUl + 0x0036 93981ec4 (+ 80) 8006ac25 :common_user_io__FixPvUlb + 0x017d 93981f14 (+ 48) 8006b118 :_user_write + 0x0028 93981f44 (+ 100) 800a1ce2 :pre_syscall_debug_done + 0x0002 (nearest) iframe at 0x93981fa8 (end = 0x93982000) eax 0x7b ebx 0x2ef760 ecx 0x7ffe6da0 edx 0xffff0104 esi 0x61 edi 0x61 ebp 0x7ffe6ddc esp 0x93981fdc eip 0xffff0104 eflags 0x207 vector: 0x63, error code: 0x0 93981fa8 (+ 0) ffff0104 7ffe6ddc (+ 48) 0023436d <_APP_ at 0x00200000>:unknown + 0x3436d 7ffe6e0c (+ 48) 0022c58e <_APP_ at 0x00200000>:unknown + 0x2c58e 7ffe6e3c (+ 80) 00211e59 <_APP_ at 0x00200000>:unknown + 0x11e59 7ffe6e8c (+ 48) 00212c16 <_APP_ at 0x00200000>:unknown + 0x12c16 7ffe6ebc (+ 144) 0021851d <_APP_ at 0x00200000>:unknown + 0x1851d 7ffe6f4c (+ 48) 002238c8 <_APP_ at 0x00200000>:unknown + 0x238c8 7ffe6f7c (+ 48) 00208df7 <_APP_ at 0x00200000>:unknown + 0x8df7 7ffe6fac (+ 48) 0010084a 704808:runtime_loader_seg0ro at 0x00100000 + 0x84a 7ffe6fdc (+ 0) 7ffe6fec 704807:tar_main_stack at 0x7efe7000 + 0xffffec }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 20:25:50 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 18:25:50 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.ce186433e9b65faf17e8175c40a83d26@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Replying to [comment:37 tigerdog]: > HOWEVER, I also have a separate Logitech S510 wireless USB Keyboard/mouse combo. Mouse does not work at all; keyboard is jerky, dropping characters and/or repeating them. The receiver is plugged into a KVM switch, but because they work fine under Windows XP, Windows 2000 and Ubuntu 8.04, the combination is at least known to work under other circumstances. I've tried with and without PS2 KB attached, with and without PS2 emulation in BIOS. No change in any case. Both of these are issues with usb_hid. Composite hid devices are not currently supported by our usb_hid meaning that for devices that combine two devices in one USB plug one of them won't work. That's simply because usb_hid looks for the first usable interface and uses that. The keyboard issues you mention are reproducible with one system I have. I will look into those but suspect they are also caused by usb_hid (might be OHCI though). In any case I'm going to work on the usb_hid driver as one of the next things. Will open a corresponding ticket for it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 20:39:10 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 18:39:10 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards Message-ID: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards ----------------------------------+----------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Platform: All | ----------------------------------+----------------------------------------- Composite devices that combine multiple HID devices in one USB device like most wireless mouse/keyboard dongles are not currently supported by our usb_hid. Also usb_hid does only implement the boot protocol for keyboards which is only a basic operational model for keyboards which limits the functionality (i.e. "multimedia" keys not working). I am opening this ticket since issues with composite HID devices were reported to me multiple times already and to indicate that I'm going to work on the usb_hid driver in that regard. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 20:39:28 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 18:39:28 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards In-Reply-To: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> References: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> Message-ID: <048.be8b5b58bacefe016649836d081f69c3@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by mmlr): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 20:47:53 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 18:47:53 -0000 Subject: [Haiku-bugs] [Haiku] #2254: [patch] please enable user-mode filters in libpcap Message-ID: <038.e8dd08096ea6316c817f40fa7c07730c@haiku-os.org> #2254: [patch] please enable user-mode filters in libpcap -----------------------+---------------------------------------------------- Reporter: mjw | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- The attached patch enables user-mode packet filters in the pcap library. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 22:12:45 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 20:12:45 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.d50ebc2ffae9bb6cd028cb5a5866e40c@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Could you check with r25616 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 22:43:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 20:43:59 -0000 Subject: [Haiku-bugs] [Haiku] #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. In-Reply-To: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> References: <043.3b1db87674d6441dad2336de8e3449dc@haiku-os.org> Message-ID: <052.b15781dccd5dc72326382e130d45d013@haiku-os.org> #2249: Building wine-1.0-rc1/dlls/dbghelp/elf_module.c fails. --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:4 axeld]: > Well, we don't. It's not a part of POSIX either - if Wine needs this header, then it should be provided by the Haiku port, but you shouldn't expect to be able to use a private Haiku header for this. OK -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 22:58:10 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 20:58:10 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards In-Reply-To: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> References: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> Message-ID: <048.8dd98216f8a385638fd6eb44bcf1ec76@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by axeld): That's great news! I do have a Microsoft natural keyboard in case you want to have it for testing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 22 23:02:49 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 22 May 2008 21:02:49 -0000 Subject: [Haiku-bugs] [Haiku] #2250: Quitting Applications: 0xffff0104 in ?? () In-Reply-To: <041.3df926f572b39f8f86ee849e07e1d213@haiku-os.org> References: <041.3df926f572b39f8f86ee849e07e1d213@haiku-os.org> Message-ID: <050.cdb027334719594a5257b2080497d7ad@haiku-os.org> #2250: Quitting Applications: 0xffff0104 in ?? () ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: invalid | Platform: All ---------------------------------+------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: The back traces look very different. Please open separate tickets. The GobeProductive trace might just indicate a problem in the application itself (e.g. double free() or clobbered memory). The 0xffff0104 address is fine -- it is used for syscalls. Two hints: - gdb prints a line why a thread entered the debugger (among otherwise useless output). Please also provide it -- in doubt copy all output. - Please don't attach zipped text files unless there's a good reason (e.g. large test set or something). It just adds overhead for the people who look at the bug report, as they have to download and unzip the stuff first. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 02:31:09 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 00:31:09 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.ed56a69517950f2d5f7258c9a713d359@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by oco): Here is the end of the console output when i boot r25614 with USB trace on my laptop (ACER Aspire 1513 LMI). The boot process stop when booting without a card in the flash reader (internally connected through USB) : USB Stack: register driver "usb_disk" USB Stack: installing notify hooks for driver "usb_disk" USB Device 2: reporting device USB Device 3: reporting device usb_module: get_configuration(24) usb_module: send_request(24, 0xa1, 0xfe, 0x0000, 0x0000, 1, 0x80281d03, 0x80281d04) usb_disk: device reports a lun count of 1 usb_module: queue_bulk(28, 0x80281c68, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281cd4, 36, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281c58, 13, 0x805236c4, 0x90cb3f80) usb_disk: vendor_identification "Generic " usb_disk: product_identification "Flash R/W " usb_disk: product_revision_level "2002" usb_module: queue_bulk(28, 0x80281ca8, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281c98, 13, 0x805236c4, 0x90cb3f80) usb_disk: operation 0x00 failed at the SCSI level usb_module: queue_bulk(28, 0x80281bc8, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281c34, 18, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281bb8, 13, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(28, 0x802813f8, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x802813e8, 13, 0x805236c4, 0x90cb3f80) usb_disk: operation 0x00 failed at the SCSI level usb_module: queue_bulk(28, 0x80281318, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281384, 18, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x80281308, 13, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(28, 0x80281408, 31, 0x805236c4, 0x90cb3f80) usb_module: queue_bulk(27, 0x8028146c, 13, 0x805236c4, 0x90cb3f80) usb_ohci: td error: 0x00000004 usb_module: clear_feature(27, 0) usb_module: queue_bulk(27, 0x802813f8, 13, 0x805236c4, 0x90cb3f80) If i put a SD card in the reader, Haiku boot fine. And i can even write to the card. I have no serial port on this laptop but i have attached the syslog for the two boot sequences : the first is incomplete because of the freeze. The second (with the card) is ok. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 04:47:18 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 02:47:18 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.a227753dc9870f4f1d659283f45f20cb@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): Hi korli, well it works now: the OS boots nicely (and fully). BTW, I never had any sound from Haiku yet, but this may be too early, judging by the fact that all sliders in Media prefs. are muted by default and immediately return to that situation after 'unmuting' each and then closing the prefs. window. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 04:49:03 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 02:49:03 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.272656489a9952d8f59eb8636519a251@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): Thanks for your patience and hard work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 13:02:18 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 11:02:18 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.6cae3bf290bfd8ca55248c68c8aa0ed8@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by jackburton): Replying to [comment:22 jackburton]: > If I connect the external USB mouse on my laptop (OHCI), the system hangs. > There is no output in the syslog when this happens. > > I can provide the complete syslog (with the mouse disconnected) if needed. With r25627 the external USB mouse works perfectly! Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 13:09:08 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 11:09:08 -0000 Subject: [Haiku-bugs] [Haiku] #2009: [Firefox] stopped working since a few revisions In-Reply-To: <040.ce24014ee9cba94d110a3e31d7fbba16@haiku-os.org> References: <040.ce24014ee9cba94d110a3e31d7fbba16@haiku-os.org> Message-ID: <049.4d2a46a6f0174a4b0f87ac2d8acd3d33@haiku-os.org> #2009: [Firefox] stopped working since a few revisions ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by diver): Sure, i tested it several times with 500mb image inside vmware, so this is not a problem. Some info about network settings in my place: It is a home local network with 1000 users in. We have dhcpd server so everyone will get a ip like 172.28.xx.xx. To have an access to the internet one should use VPN (pptp) client to connect to our freebsd mpd server. However, changing network settings in vmware do change a behavior. By default .vmx file is set to bridged mode. In this mode my local network is working fine. ifconfig inside Haiku shows an ip 172.28.xx.xx and i could ping every server i have _inside_ my LAN, but i can't access internet. If I change vmware to use NAT, Haiku will not have an ip and firefox loads fine. If I turn off "Connect at power on" in vmware network setting, then ifconfig will not show my nic and firefox loads fine too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 13:25:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 11:25:23 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation In-Reply-To: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> References: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> Message-ID: <052.05962529214ac8f105a370453761c27b@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: fixed | Platform: All --------------------------+------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r25628. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 14:20:27 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 12:20:27 -0000 Subject: [Haiku-bugs] [Haiku] #2242: pthread_attr_getscope, pthread_attr_setscope implementation In-Reply-To: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> References: <043.f61309d497ccfb682a2d86c55bd49746@haiku-os.org> Message-ID: <052.28847fb7b1fa0b161995e1ddb249c70f@haiku-os.org> #2242: pthread_attr_getscope, pthread_attr_setscope implementation --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: closed Priority: low | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: fixed | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): Replying to [comment:4 axeld]: > Fixed in r25628. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 15:11:54 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 13:11:54 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.ecf115fa97ed708ce51d664636b2de9f@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): I examined about 10 box, found a linux pc with a similar problem. But the Linux kernel's NMI default behavior is emit a message and continue, so there is no problem usually. I sent a patch to lkml:http://lkml.org/lkml/2008/5/21/163. But After a lot of test today, I found that the problem is the same even the patch applied. And about FreeBSD, the NMI ISR is just panic, but their PCI only enable master bit by default(no sure). So there is also no problem usually. IMHO, Could we just only enable pci master or emit a message when NMI interrupt happened? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 16:50:35 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 14:50:35 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. Message-ID: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. ----------------------------+----------------------------------------------- Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Platform: All | ----------------------------+----------------------------------------------- Virtual Box: http://www.virtualbox.org/ Emulates an ICH AC97 Audio Controller. I've installed and tested OSS with Haiku under Virtual Box. The media server seems to detect the controller is present, although there's no sound output (tested with core audio on a MacBook). See the attached pics 1&2. Changing any options and restarting the server will crash it (100% reproducible). See attached backtrace #3. You can test OSS and Haiku under VirtualBox here: [http://www.haikuware.com/view-details/development/app-installation /senryu-virtual-box-edition] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 16:57:44 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 14:57:44 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.a21f4bd9fc33a0f84e82bcc55007914c@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => mmu_man Comment: REassigning, as the crash seems to be OSS related. But has the box really 3 audio devices? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 17:07:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 15:07:39 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.1625d9e6ce488b4be4177584f0f51cd9@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by mmlr): I would say that having two drivers for the same device (auich and the OSS ich driver in this case) is generally not a good idea. I don't know if both are opened at the same time though. There have recently been auich fixes by Jerome that might not be included in your image. If you provided the revision number this could be verified. The last fix in this regard was in r25616. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 17:37:30 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 15:37:30 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.128a2626c3a2a36abc51602b1d6786f6@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kvdman): Hi, The revision tested was 25562. I only have one audio device enabled in Virtual Box's preferences. I'll remove the auich driver, and see what happens. Also, I'll try to see how revisions after 25616 affect this problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 18:08:10 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 16:08:10 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.d1bb8ada55bcbe84943449ca61225d92@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kvdman): With r25562, if you remove the auich driver, the sound actually works! It is crackly though. You will get the same crash if you try to restart the media server though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 18:13:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 16:13:50 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.c192e13efbb674ae50cc975728c5b9a0@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by stippi): I think there was a bug report for that crash though. Please note that the OpenSound package is broken in that Haiku itself already comes with the OpenSound media node (installed in the system path) and then the package installs another version of that node in the home folder. So one of them should be deleted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 18:54:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 16:54:55 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.30e2277cb2bdf003fd6a840b955a15ff@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kvdman): Here's what I can tell you. I think only the Vmware image contains the OSS package. I downloaded a raw image from haiku-files.org, converted it to a virtual box image. The only controller that shows up is the Auich. The sound works, but is horrible. I then used a Vmware image. After deleting the Auich driver, and the second OSS folder as Stippi described, the sound works as well (I believe the quality is better than the Auich driver, but still not great). Now when the media server is restarted, it won't crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 18:57:52 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 16:57:52 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.5d81696d2057ad25cea99ca509873c56@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kvdman): Sorry, forgot to mention that this was tested under r25619. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 11:42:27 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 09:42:27 -0000 Subject: [Haiku-bugs] [Haiku] #2255: checking for gethostbyname In-Reply-To: <042.95cb0886e8ab5ecd5bb7ebb704744e38@haiku-os.org> References: <042.95cb0886e8ab5ecd5bb7ebb704744e38@haiku-os.org> Message-ID: <051.29d62355a1e09e71eb2db360590dfaae@haiku-os.org> #2255: checking for gethostbyname ------------------------+--------------------------------------------------- Reporter: begasus | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: x86 ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: libnetwork.so is what Haiku uses. Compatibility for BeOS in only for already compiled applications, not for apps that you compile with the Haiku headers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 20:53:51 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 18:53:51 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.bdbea90d375d7e8f45c130864a4b5cfe@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by andreasf): VirtualBox 1.6 is the first official version to provide Mac support, and I found it to be rather unstable on my MacBook Core Duo. If it works in VMware Fusion or Q, it could well be a VirtualBox issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 20:58:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 18:58:39 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.646430b527223c197e77e1882b9fa172@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Changes (by mmu_man): * status: new => assigned Comment: As stippi said, the media node is both in the image and the package, that's because it used to be in the port, and I built it along with OSS to make an R5 zip, that's not used as package... OTH, the node comming with the image is built with the native gcc, which means installing OSS will work on gcc4 images too. Having the addon twice shouldn't cause problems anyway, open() is denied to the 2nd one. At least it's not as much of a problem than having 2 drivers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 21:19:07 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 19:19:07 -0000 Subject: [Haiku-bugs] [Haiku] #2257: Warning: PAGE_SIZE redefined Message-ID: <043.636e08b1a5679155deb1172c9707bbe6@haiku-os.org> #2257: Warning: PAGE_SIZE redefined -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- Probably related to r25626, Haiku build results in multiple warnings that {{{PAGE_SIZE}}} is being redefined. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 21:41:41 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 19:41:41 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.ccc9c0a263a7afed61e24163560472ef@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by korli): Replying to [comment:15 meanwhile]: > Hi korli, well it works now: the OS boots nicely (and fully). > > BTW, I never had any sound from Haiku yet, but this may be too early, judging by the fact that all sliders in Media prefs. are muted by default and immediately return to that situation after 'unmuting' each and then closing the prefs. window. Didn't understand : there is no sound ? Could you post a serial output ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 22:41:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 20:41:04 -0000 Subject: [Haiku-bugs] [Haiku] #1919: Cursor hangs on startup In-Reply-To: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> References: <044.216253a81a35f1fd229dcbb677851cfa@haiku-os.org> Message-ID: <053.1877969647ff998fe10b6b0c20c8db73@haiku-os.org> #1919: Cursor hangs on startup ----------------------------+----------------------------------------------- Reporter: meanwhile | Owner: korli Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by meanwhile): Earlier Haiku revisions on this PC never had working sound, so in fact this may be a seperate issue/bug. In r245619 I do notice a very short crack through my headphones at the moment after the Terminal shows up and before the Deskbar shows up, so there was an audio signal for a short moment. In 'Media' preferences window, when selecting 'Auich ICH' on the tab called 'AC97 Mixer', all the sliders have 'Mute' selected with a blue cross. When removing the blue crosses and then closing the Media preferences window and re-opening it, the blue crosses are there again; that's what I meant by "all sliders are muted". Anyhow, I hope the r245619boot.txt attachment will be informative. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 23:01:12 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 21:01:12 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.b43a8bb82a291146fac1c6f0a18261e8@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kvdman): I'm a bit confused now, I just downloaded the images from the factory, and OSS doesn't seem to be installed anymore (25619). By the way, if OSS is to be in the image anyways, shouldn't the optional package be removed? I'm not really clear what solved the problem, whether it was Jerome's changes to the media kit (and me testing it on an updated revision as suggested by mmlr), or deleting the OSS install in /home, but it doesn't crash anymore and there's sound, so the ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 23:13:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 21:13:50 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.4e33b4abffaab13c8b641e19015c2c8f@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by umccullough): The OSS Media node in the Haiku repo is *not* OSS itself - it's just a layer that allows OSS to behave like a driver for the media kit, IIRC. AFAIK, it should not be part of the image by default, (neither should OSS in fact). Haiku has an auich/ac97 driver already, and should not require OSS for that functionality. I have successfully used it on several ICH audio devices with good luck, and with the latest changes it even works flawlessly on my laptop where it had problems previously. Having OSS installed on the same image as the native drivers is just asking for trouble. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 23:16:39 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 21:16:39 -0000 Subject: [Haiku-bugs] [Haiku] #2258: resize-button in tab changes color sometimes Message-ID: <041.e29b24945e9d88d430de32b58a642c1e@haiku-os.org> #2258: resize-button in tab changes color sometimes ----------------------------+----------------------------------------------- Reporter: jdawin | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- Under certain conditions, the resize- and close-buttons in the tab change their color on clicking. To reproduze this behaviour do this: 1. open a folder, say "Haiku" from the Desktop 2. open another folder inside the first one, say "beos" 3. open yet another inside this second folder, say "etc" 4. now activate the "Haiku"-window, and maximize it, if it isn't already 5. make it smaller by dragging the bottom-right edge 6. scroll one the scrollbars 7. move the window around 8. click on the resize-button. Now, or after a few more clicks on the resize-button the button should change its color to dark blue or grey, which is unexpected. To see the close-button change its color, click on it without releasing the mouse-button The effect is quite unpredictable. I could not figure out a rule for which color comes up or which window needs how many clicks on resize to show the effect. But the above method worked quite reliably for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 00:16:11 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 22:16:11 -0000 Subject: [Haiku-bugs] [Haiku] #2258: resize-button in tab changes color sometimes In-Reply-To: <041.e29b24945e9d88d430de32b58a642c1e@haiku-os.org> References: <041.e29b24945e9d88d430de32b58a642c1e@haiku-os.org> Message-ID: <050.51c1c63843c7301e646a8c5212c4540d@haiku-os.org> #2258: resize-button in tab changes color sometimes -----------------------------+---------------------------------------------- Reporter: jdawin | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by j_freeman): * cc: j_freeman (added) Comment: I've seen this from time to time as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 00:33:53 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 22:33:53 -0000 Subject: [Haiku-bugs] [Haiku] #2255: checking for gethostbyname In-Reply-To: <042.95cb0886e8ab5ecd5bb7ebb704744e38@haiku-os.org> References: <042.95cb0886e8ab5ecd5bb7ebb704744e38@haiku-os.org> Message-ID: <051.647e68c8cf729b6c45386c91d51208bb@haiku-os.org> #2255: checking for gethostbyname ------------------------+--------------------------------------------------- Reporter: begasus | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: x86 ------------------------+--------------------------------------------------- Comment (by scottmc): here's one example of how to fix ports to deal with this: http://tools.assembla.com/BePorts/browser/BePorts/trunk/net-misc/curl /curl-CVS.diff?rev=68 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 03:35:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 01:35:21 -0000 Subject: [Haiku-bugs] [Haiku] #1727: Haiku panics with vm_page fault/double fault after 20-30s usage In-Reply-To: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> References: <038.c78dd316936a9ee073ffdb24b1a5c2b3@haiku-os.org> Message-ID: <047.0d957c7edfbce0ef9575001e5cf5eca6@haiku-os.org> #1727: Haiku panics with vm_page fault/double fault after 20-30s usage ----------------------------+----------------------------------------------- Reporter: tqh | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by absabs): I come across the same problem on a 1394 card with via chip while trying to solve the parity error bug (ticket 2243). I can dig into this problem and try to fix it > As you can see from the pic, today it went back to crashing after a few minutes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 03:38:55 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 01:38:55 -0000 Subject: [Haiku-bugs] [Haiku] #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) In-Reply-To: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> References: <039.2c1e408a5b7c1ab2a819c404ebb17a67@haiku-os.org> Message-ID: <048.7dbc7bcac7ad938a71088724c7fafa20@haiku-os.org> #2243: Firewire driver provokes PCI parity error and KDL upon boot (before Tracker loads) -------------------------------+-------------------------------------------- Reporter: koki | Owner: absabs Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/FireWire | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by absabs): hmmm, there is no such problem with the 1394card on my box. So I think it is the Linux pc's pci slot problem. I can't install other os on that box because the box is very important. I need to find another box -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 10:32:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 08:32:23 -0000 Subject: [Haiku-bugs] [Haiku] #2255: checking for gethostbyname Message-ID: <042.95cb0886e8ab5ecd5bb7ebb704744e38@haiku-os.org> #2255: checking for gethostbyname -----------------------+---------------------------------------------------- Reporter: begasus | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- While trying to compile curl I came across the problem that it can't find -lnet (even try'd with -lbind) to check against it. This used to work before, Jack told me over at IRC that libbind and libnet links are removed from the developer folder. I then changed the configure script to use -lnetwork in order to make it find gethostbyname. Is this planned to stay like this or is it just a temporarily change? Breaks some possix things the way it is now (one needs to manually edit ./configure to check against -lnetwork). PS. This is with revision 25571. (if it is already fixed in a later revision just ignore this ;) ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 10:23:19 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 08:23:19 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards In-Reply-To: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> References: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> Message-ID: <048.8f29e0cf0238ea96e4488def3bcadea1@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by mmlr): Replying to [comment:2 axeld]: > That's great news! I do have a Microsoft natural keyboard in case you want to have it for testing. I do too ;-). Those keyboards have the dual configuration of a simple boot-protocol interface that does not support the multimedia keys and a full HID interface. So getting that going will enable those keys. But after they are enable we have to devise a plan as to what to do with them. SpicyKeys comes to mind, maybe we should integrate this kind of functionality. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 10:19:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 08:19:04 -0000 Subject: [Haiku-bugs] [Haiku] #1050: implement a WiFi stack In-Reply-To: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> References: <045.5222f32311d9d2dcab22154271938480@haiku-os.org> Message-ID: <054.026080932e22e3948050db2d215bbfdb@haiku-os.org> #1050: implement a WiFi stack ------------------------------------------+--------------------------------- Reporter: wkornewald | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Network & Internet/Wireless | Version: R1 development Resolution: | Platform: All ------------------------------------------+--------------------------------- Comment (by tqh): For what's it worth. I'm working on getting net80211 to compile from FreeBSD trunk. To me it looks like it will compile with just supplying the right compabilityheaders and libcrypto. After that I believe network gurus will need to help/review the work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 10:14:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 08:14:50 -0000 Subject: [Haiku-bugs] [Haiku] #2049: Mozilla applications fail to discover application signature In-Reply-To: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> References: <041.24d66c723300fec3ed563eec06b361c0@haiku-os.org> Message-ID: <050.3d8970c89fe00288f620abcadee8bc89@haiku-os.org> #2049: Mozilla applications fail to discover application signature ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by tqh): * cc: tqh (added) Comment: And yes it's ugly :) We should probably add #ifdefs for different apps in mozilla code instead. And an #error if it's one that we don't know about. mmadia, I believe this is something that would fit you btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 23 10:05:38 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 23 May 2008 08:05:38 -0000 Subject: [Haiku-bugs] [Haiku] #2009: [Firefox] stopped working since a few revisions In-Reply-To: <040.ce24014ee9cba94d110a3e31d7fbba16@haiku-os.org> References: <040.ce24014ee9cba94d110a3e31d7fbba16@haiku-os.org> Message-ID: <049.be6cf40ad39daed0863e27cc31bc3c2b@haiku-os.org> #2009: [Firefox] stopped working since a few revisions ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by tqh): diver, if that is you full UserBuildConfig your image is not big enough. The default is only 100MB and the build script doesn't care about partition size so do increase the size in UserBuildConfig, I can't show you the exact variable, but it should be in the sample or readme version of UserBuildConfig. You will get all kinds weirdness with apps if you try to write more than the image size. I believe there is a bug about that the build-script should fail or warn, but currently it doesn't. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 13:30:21 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 11:30:21 -0000 Subject: [Haiku-bugs] [Haiku] #1840: Strange output from ls /dev In-Reply-To: <041.12bd45285101f826b397cf0ecf58e405@haiku-os.org> References: <041.12bd45285101f826b397cf0ecf58e405@haiku-os.org> Message-ID: <050.79b4d7d801bfef884cf3151045845140@haiku-os.org> #1840: Strange output from ls /dev ---------------------+------------------------------------------------------ Reporter: ekdahl | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: x86 ---------------------+------------------------------------------------------ Changes (by andreasf): * platform: All => x86 Comment: Axel asked in #2251: > Can you pin it down to a change since when this happens (like adding BT)? No, I don't look into /dev so often... It hasn't occurred again since I reported it, despite continued presence of Bluetooth stack and dongle. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 13:43:48 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 11:43:48 -0000 Subject: [Haiku-bugs] [Haiku] #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. In-Reply-To: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> References: <041.13083c72e1617fed3d25980e5cfb91b0@haiku-os.org> Message-ID: <050.1a635d7fa010606ecacf86da46eafcfe@haiku-os.org> #2256: Virtual Box No Sound Despite Detection, Crashes When Restaring Media Server. -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by mmu_man): Once again the problem is not about OSS, it's about the pci bus manager or config manager or whichever not providing a mean to reserve a device for exclusive use. Some cards are and will always be only supported through OSS, because it just works and noone is interested in spending time on writing a driver for it. Also, I made it possible to disable selecte drivers from OSS by editting the osscore settings file, it should be easy to remove support for ich or whatever. I just didn't because I need to udate the port anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 22:44:41 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 20:44:41 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.265c56a32b1532fc57cb853fe9d693ff@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Changes (by tigerdog): * cc: tigerdog (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 24 22:46:09 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 24 May 2008 20:46:09 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.c9ba90a0341034de8ab28c9e6952fd52@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by tigerdog): this may be the cause of the problem reported in http://dev.haiku- os.org/ticket/2071 Rudolph, I'll be happy to test any potential changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 07:11:38 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 05:11:38 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes Message-ID: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> #2259: cp command copies BFS attributes ---------------------------------------------+------------------------------ Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Platform: x86 | ---------------------------------------------+------------------------------ When we copy some files by Tracker, the BFS attributes of its files are also copied. But, by cp command (/boot/beos/bin/cp), attributes are not copied. I want cp command copy BFS attributes. Haiku: r25524 [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (enhancement No.3) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 11:53:56 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 09:53:56 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.3ce506874fa63def06a1b5b17c3d7e0b@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Platform: x86 ----------------------------------------------+----------------------------- Comment (by mmlr): I'd tend to classify this as invalid. The cp command has never copied BFS attributes and IMO should not either (it's a handy way of getting rid of attributes). So this is expected behaviour. There is "copyattr -d" that copies file data and attributes and should be used to achieve attribute and data copies from the command line. But I won't decide on that, waiting for other opinions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 12:09:03 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 10:09:03 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.7cad0e49bc8ff35881f5fb9133ba49a6@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Platform: x86 ----------------------------------------------+----------------------------- Comment (by marcusoverhagen): Support for attributes was added to mv and cp in r8401. I tested this in r25634 and it still works. This bug report is invalid. I believe this behaviour is a good idea and should be kept. There is even a command line switch to disable that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 12:32:28 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 10:32:28 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.5810c2ae7d4bd884815e2b462eebaa4e@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------------------------+----------------------------- Changes (by mmlr): * status: new => closed * resolution: => invalid Comment: Right, tested this too and it works like this. Also "--ignore-attributes" does what it is supposed to do. Closing as invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 13:17:54 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 11:17:54 -0000 Subject: [Haiku-bugs] [Haiku] #2260: r25620 causes leaf menu to disappear after changing screen resolution Message-ID: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> #2260: r25620 causes leaf menu to disappear after changing screen resolution -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -----------------------+---------------------------------------------------- SW: 32-bit Ubuntu 8.04, Vmware Player 2.0.3, vmware-image built with gcc 2.95-3 HW: Lenovo T60 laptop 1) Boot a r25620 vmware build. 2) Leaf -> Preferences -> Screen 3) Set resolution to 800x600 and press Apply. 4) Close Screen window. 5) Leaf -> Restart Result: missing main menu, see picture. This problem does not happen with rev 25619 and is still present in rev 25653. Tested with clobber vmware builds. Let me know if you want them available for download. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 13:54:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 11:54:30 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.031bb5dfa8421092be805815afb7758c@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------------------------+----------------------------- Comment (by shinta): Mmm... I tried again, but, in my r25628, cp doesn't work. Above is Terminal's log. TestSrc.txt is saved by StyledEdit and has some attrs. But, after cp, TestDest.txt doesn't have attrs. cp seem to copy icon related attributes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 14:36:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 12:36:46 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.821dea154124e56c874332b3dfa1b799@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------------------------+----------------------------- Comment (by mmlr): That'd be a bug then. Are you sure you're not using a different version of cp? Can you post what "which cp" outputs and can you check if the "--ignore-attributes" argument is listed in "cp --help"? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:03:44 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:03:44 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.f6823e9d99dc6542f27169ba53b51e72@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: invalid | Platform: x86 ----------------------------------------------+----------------------------- Comment (by shinta): "which cp" returns "/bin/cp" and "--ignore-attributes" argument is listed before "-i, --interactive". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:07:59 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:07:59 -0000 Subject: [Haiku-bugs] [Haiku] #2260: r25620 causes leaf menu to disappear after changing screen resolution In-Reply-To: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> References: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> Message-ID: <049.4dd043459bc3766acf7537ee0cc1b35e@haiku-os.org> #2260: r25620 causes leaf menu to disappear after changing screen resolution ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by stippi): Hm. Looking at the r25620 change set, which seems completely unrelated, I am tempted to think you would see the same behavior with r25619 if you tried more times. Maybe it would sometimes work correctly with r25620 too. How many times have you tried this with either revision? It looks a bit like this could be an error that happens randomly and is unrelated to r25620. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:23:25 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:23:25 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.07bc3b5740e664c32d95b6baa0dc0047@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Platform: x86 ----------------------------------------------+----------------------------- Changes (by mmlr): * status: closed => reopened * type: enhancement => bug * resolution: invalid => Comment: Then this is a bug. What filesystem does this happen on? Also it doesn't seem that you're copying between volumes or such. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:40:00 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:40:00 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.c45126835896fc6c85dd7df521413bf1@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by euan): * cc: euan (added) Comment: I've attached a screen dump of a KDL when booting on my HP 6715b laptop. Seems to be in the USB bus mananger. OHCI chipset, sdcard reader. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:42:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:42:36 -0000 Subject: [Haiku-bugs] [Haiku] #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h Message-ID: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h -----------------------+---------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- specs http://www.opengroup.org/onlinepubs/000095399/basedefs/sys/stat.h.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 16:16:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 14:16:46 -0000 Subject: [Haiku-bugs] [Haiku] #2262: "restrict" keyword issue in posix/search.h Message-ID: <042.1d247d0fc4942936a077b2378be431ed@haiku-os.org> #2262: "restrict" keyword issue in posix/search.h -----------------------+---------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Consider a axample: {{{ #include #include int main() { return 0; } }}} and try to compile: {{{ In file included from /boot/home/1.c:2: /boot/develop/headers/posix/search.h:35: conflicting types for `restrict' /boot/develop/headers/posix/search.h:35: previous declaration of `restrict' }}} Changing restrict to __restrict fixes the problem, but I'm not sure that is a good solution. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 16:20:39 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 14:20:39 -0000 Subject: [Haiku-bugs] [Haiku] #2260: r25620 causes leaf menu to disappear after changing screen resolution In-Reply-To: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> References: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> Message-ID: <049.f13b974280a66a572e99e89dba3690c7@haiku-os.org> #2260: r25620 causes leaf menu to disappear after changing screen resolution ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by luroh): Replying to [comment:1 stippi]: > I am tempted to think you would see the same behavior with r25619 if you tried more times. Maybe it would sometimes work correctly with r25620 too. You might very well be right in that r25620 is merely exposing a bug instead of causing it. Having tested both builds >10 times, I can say that the bug isn't *always* repeatable with r25620 (though very reliable), but I cannot see the bug at all with r25619. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 16:23:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 14:23:42 -0000 Subject: [Haiku-bugs] [Haiku] #2259: cp command copies BFS attributes In-Reply-To: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> References: <041.a9b2252274b151b8a2dc24783f805239@haiku-os.org> Message-ID: <050.6cba6370795eb38ad657660e3f1e7b0b@haiku-os.org> #2259: cp command copies BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Platform: x86 ----------------------------------------------+----------------------------- Comment (by shinta): Filesystem is BFS, and, src and dest volume are same. In Senryu distribution (VirtualBox), cp works well. It may be my problem about Haiku build. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 17:12:14 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 15:12:14 -0000 Subject: [Haiku-bugs] [Haiku] #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h In-Reply-To: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> References: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> Message-ID: <052.0faf6b54b510044b5db50905aa034440@haiku-os.org> #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by andreasf): This has been a common issue for ports, see some examples and workarounds at HaikuPorts (formerly BePorts). BeOS did not have it either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 17:19:09 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 15:19:09 -0000 Subject: [Haiku-bugs] [Haiku] #2260: r25620 causes leaf menu to disappear after changing screen resolution In-Reply-To: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> References: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> Message-ID: <049.539627b3f68e5a504635fc2c61c6cf2b@haiku-os.org> #2260: r25620 causes leaf menu to disappear after changing screen resolution ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by luroh): Let me add a few other bits of information that might be helpful in nailing this and perhaps other related problems. 1. This bug is a bit of a pain, since I haven't found a way to restore the vmdk to prevent it from hanging at boot, short of replacing it with a fresh copy (which is easy for me, but might require others to re-download the build). 2. I have put a copy (18MB, 7zip) of the hanging r25620 vmdk here: http://www.megaupload.com/?d=ZNBOORAK Perhaps someone could confirm that it hangs on their machine as well. A fresh, never booted vmdk is available here: http://www.megaupload.com/?d=GVK5ZWXJ 3. Once and only once, when booting a fresh r25620 build, I got a print_server error that I've never seen before or since. Pictures attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 17:21:26 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 15:21:26 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.79c07fbc090284c267d5a56ba542eeb7@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): The crash should be fixed in r25654. That the device does not fully initialize is because of a timeout. This is most probably caused by having full debug output enabled and the associated delays. Could you please try without TRACE_USB and see if the device still fails to init correctly? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 15:50:46 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 13:50:46 -0000 Subject: [Haiku-bugs] [Haiku] #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h In-Reply-To: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> References: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> Message-ID: <052.b8be804020cb3c4ab1f061e8bda60f7f@haiku-os.org> #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by kaoutsis): Required by wine: {{{ /Haiku1/packages/wine-1.0-rc1/dlls/ntdll> make gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wwrite-strings -Wpointer-arith -g -O2 -o directory.o directory.c /Haiku1/packages/wine-1.0-rc1/dlls/ntdll/directory.c: In function `append_entry': /Haiku1/packages/wine-1.0-rc1/dlls/ntdll/directory.c:947: structure has no member named `st_blocks' make: *** [directory.o] Error 1 }}} directory.c at line 947 +-1: {{{ info->EndOfFile.QuadPart = st.st_size; info->AllocationSize.QuadPart = (ULONGLONG)st.st_blocks * 512; info->FileAttributes |= FILE_ATTRIBUTE_ARCHIVE; }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 22:06:30 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 20:06:30 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.62d8ab5c9a76acae6a837dda52e7066c@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by euan): I've still to try the patch will do real soon (tm). I think this is the cause, as in several boots since reporting I've found that if i whirl the mousepad round and round whilst booting the issue doesn't occur. Remember when I said Haiku doesn't work unless a mouse / keyboard event occurs??? I also got the AHCI errors again, so I think it is due to this interrupt / hardware issue somewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 22:34:18 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 20:34:18 -0000 Subject: [Haiku-bugs] [Haiku] #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h In-Reply-To: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> References: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> Message-ID: <052.6d36dcdca4e74e2240b1f6296ed97df1@haiku-os.org> #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h ------------------------+--------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by nielx): Git also assumes this st_blocks to exist. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 23:22:36 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 21:22:36 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.31a7c522ddb0598d390deea1cde4d03e@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by umccullough): Just tested this myself (as I found my Corum III discs!) Still missing the symbol ReadFrames__11BMediaTrackPcPxP12media_header -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 23:23:07 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 21:23:07 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.20d8623930e8d43aa28befa4bc1531be@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by umccullough): BTW, there's a patch attached to this ticket... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 25 23:47:15 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 21:47:15 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.a1f77e75e105d71a61a30303674cef61@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by mmu_man): Since noone vetoed it, I applied it as r25656. Please test. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:09:42 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:09:42 -0000 Subject: [Haiku-bugs] [Haiku] #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h In-Reply-To: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> References: <043.f51f2d66d12472bbb82569cdfe88fb0a@haiku-os.org> Message-ID: <052.1be6511489797585d71cad4726803a4c@haiku-os.org> #2261: Member named `st_blocks' is missing from struct stat in sys/stat.h --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Changes (by bonefish): * type: bug => enhancement * component: - General => System Comment: stat::st_blocks is actually part of the XSI extension. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:11:59 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:11:59 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.e1de949b9b2ff42f8f23c13cd25a5433@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by zenja): The issue can now be closed. I've tested it with build R25653, and it works like a charm. BTW - I've also tested my USB 1.1 backlit keyboard and mouse. It works for the first minute or so, then fails to respond. Reconnecting the keyboard / mouse fixes the issue. Since there has been weekly activity on the USB stack, I'll wait for another week or so before logging a concrete issue. I might now finally be able to port some of my OpenGL projects to Haiku. Cheers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:27:13 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:27:13 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.526feffb2b1bbe78d91a0754f11c3b54@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by euan): tried the updated patch, seems more stable. I get mostly the ahci issue now. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:36:03 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:36:03 -0000 Subject: [Haiku-bugs] [Haiku] #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly In-Reply-To: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> References: <041.c3b223b19d4d0d2f2f352fd545740f96@haiku-os.org> Message-ID: <050.d3e7f1cb3a199015d93184916268a71f@haiku-os.org> #1949: Haiku: wireless Logitech mx3200 keyboard and mouse + USB receiver not working correctly --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => assigned Comment: Could you please try this with a current revision that includes the rewritten usb_hid (r25657 and up). Composite devices like this should work now. Also the keyboard side might have improved a bit as I think I've fixed a few issues with the code on the go. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:40:52 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:40:52 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.6061de9aef67df675c6a670c8614bba6@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Replying to [comment:37 tigerdog]: > HOWEVER, I also have a separate Logitech S510 wireless USB Keyboard/mouse combo. Mouse does not work at all; keyboard is jerky, dropping characters and/or repeating them. The receiver is plugged into a KVM switch, but because they work fine under Windows XP, Windows 2000 and Ubuntu 8.04, the combination is at least known to work under other circumstances. I've implemented composite device support while rewriting usb_hid. Could you check if this works correctly now? HID issues are going to be handled as part of enhancement #2253, but if this helps verify that OHCI works fine on your hardware now I'd welcome that info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:42:21 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:42:21 -0000 Subject: [Haiku-bugs] [Haiku] #2253: usb_hid should support composite devices and non-boot protocol keyboards In-Reply-To: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> References: <039.ca98566102eaf2f700bef3c38b520c6f@haiku-os.org> Message-ID: <048.b6b42633d2ad6de60a26d8b0a1f416a9@haiku-os.org> #2253: usb_hid should support composite devices and non-boot protocol keyboards -----------------------------------+---------------------------------------- Reporter: mmlr | Owner: mmlr Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Keyboard/USB | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by mmlr): Composite devices should be supported as of r25657. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 00:44:32 2008 From: trac at haiku-os.org (Haiku) Date: Sun, 25 May 2008 22:44:32 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.ed5aac6df056c4a86df5bc889c35eebf@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by mmlr): Replying to [comment:44 euan]: > tried the updated patch, seems more stable. I get mostly the ahci issue now. :) Does that mean that it is just more stable and there are still OHCI issues or does OHCI now work as expected? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 03:07:50 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 01:07:50 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.b36bc5bb9bea0e84afae9bdd8499b76b@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by umccullough): Definitely fixes the missing symbol issue - but there are apparently other problems preventing Corum III from working (I will log them as separate issues) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 03:23:58 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 01:23:58 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.cde17248c5bd93f0a90433a06acc9d67@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by tigerdog): Replying to [comment:45 mmlr]: I've implemented composite device support while rewriting usb_hid. Could you check if this works correctly now? HID issues are going to be handled as part of enhancement #2253, but if this helps verify that OHCI works fine on your hardware now I'd welcome that info. I can't build Haiku ATM, so I'll have to try after the next nightly build is posted. Thanks for the extra effort on composite devices! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 11:58:16 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 09:58:16 -0000 Subject: [Haiku-bugs] [Haiku] #1044: USB OHCI support In-Reply-To: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> References: <045.95d7cf1f9f7c375158db263698ccd0fb@haiku-os.org> Message-ID: <054.dd6457b9a9ec200f3aa37884d3d0cb83@haiku-os.org> #1044: USB OHCI support --------------------------+------------------------------------------------- Reporter: wkornewald | Owner: mmlr Type: enhancement | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by euan): Replying to [comment:47 tigerdog]: > Replying to [comment:45 mmlr]: > I've implemented composite device support while rewriting usb_hid. Could you check if this works correctly now? HID issues are going to be handled as part of enhancement #2253, but if this helps verify that OHCI works fine on your hardware now I'd welcome that info. > > I can't build Haiku ATM, so I'll have to try after the next nightly build is posted. Thanks for the extra effort on composite devices! As long as I keep moving the mouse round and round USB and everything else ticks along just fine. I can mount the usb memory cards now, and copy files. So I'd say it's working. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 12:27:00 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 10:27:00 -0000 Subject: [Haiku-bugs] [Haiku] #2215: Terminal as replicant doesn't respect settings In-Reply-To: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> References: <042.965068ab525910e39f8af1db17b31374@haiku-os.org> Message-ID: <051.08b0e8f4e83fc14838135a8d3518c1c7@haiku-os.org> #2215: Terminal as replicant doesn't respect settings ------------------------------------+--------------------------------------- Reporter: scottmc | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by jackburton): * summary: Terminal colors as replicant goto black on white even if selected otherwise => Terminal as replicant doesn't respect settings -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 13:41:46 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 11:41:46 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.492cb91fa22ffd139c24b3c8dc445a93@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by rudolfc): Hi, I was pointed at this error and it might be the same one as ticket #1950. Assuming this is the case I am now testing r24635 on a GF2Ti (NV15). It does _not_ work. I'll test r23198 and up since that's still online (haikufiles) to see if there's a revision working still for bug 1950. stay tuned. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 13:58:56 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 11:58:56 -0000 Subject: [Haiku-bugs] [Haiku] #1891: No keyboard or mouse input on real hardware In-Reply-To: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> References: <043.3e5b5319685d174aa810166ac0cef370@haiku-os.org> Message-ID: <052.eadcc5cd3e1e06b6a08cc59dd71b22f9@haiku-os.org> #1891: No keyboard or mouse input on real hardware --------------------------+------------------------------------------------- Reporter: salierix | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Platform: All --------------------------+------------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:10 zenja]: > BTW - I've also tested my USB 1.1 backlit keyboard and mouse. It works for the first minute or so, then fails to respond. Reconnecting the keyboard / mouse fixes the issue. Since there has been weekly activity on the USB stack, I'll wait for another week or so before logging a concrete issue. That might have been fixed (or made worse) through my rewrite of usb_hid. You could try with r25658 and up as that should include error handling. Will close this bug now, if there should be further issues with usb_hid please report them in enhancement #2253. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 14:49:31 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 12:49:31 -0000 Subject: [Haiku-bugs] [Haiku] #2263: USB Key doesn't work Message-ID: <045.3e7db024b77ce246c3830001c0b845a4@haiku-os.org> #2263: USB Key doesn't work -------------------------+-------------------------------------------------- Reporter: jackburton | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: All | -------------------------+-------------------------------------------------- I have a somewhat old 256MB USB key which doesn't work in Haiku (while it does in windows and linux). Note that another USB key (1GB) works flawlessly on Haiku. Attached is the syslog when I attach the key. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 19:49:32 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 17:49:32 -0000 Subject: [Haiku-bugs] [Haiku] #2260: r25620 causes leaf menu to disappear after changing screen resolution In-Reply-To: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> References: <040.b2bbcd8b2702f518dd05dc902272deb6@haiku-os.org> Message-ID: <049.6160689cd6a67c4f0147d245d9f86713@haiku-os.org> #2260: r25620 causes leaf menu to disappear after changing screen resolution ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by axeld): A stack crawl of the print_server problem would have been helpful in case you encounter it again (type "bt" in the GDB debugger terminal). But since this probably doesn't have anything to do with the bug you're describing here, it would be better to open a new ticket for this (in case it happens again, and you can retrieve that data). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 21:13:28 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 19:13:28 -0000 Subject: [Haiku-bugs] [Haiku] #2264: Media Checker Crash Message-ID: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> #2264: Media Checker Crash -----------------------------+---------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- This is the 1st time in a long time I've been unable to boot Haiku through Vmware. Maybe due to Axel's recent changes in the device manager? Freshly built rev25664 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 21:22:20 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 19:22:20 -0000 Subject: [Haiku-bugs] [Haiku] #2264: Media Checker Crash In-Reply-To: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> References: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> Message-ID: <050.fc66ad959e4c1be46d0de56a17b12c60@haiku-os.org> #2264: Media Checker Crash ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by mmlr): Happened to me as well the first time I booted after the device manager integration. The second time I couldn't reproduce it though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 21:40:08 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 19:40:08 -0000 Subject: [Haiku-bugs] [Haiku] #2264: Media Checker Crash In-Reply-To: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> References: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> Message-ID: <050.eb862540a10e761ff9780a11afd105d4@haiku-os.org> #2264: Media Checker Crash ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): Hm, I keep getting the crash after several reboots. See if anyone else can verify this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 22:18:19 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 20:18:19 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.50efc8e2a1619bc70040f1e6ebe5f3e1@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by rudolfc): Hi there, I've traced the versions where it went wrong: r24493 is working OK; r24511 is faulty. It's MTRR-WC failed mapping because of overlapping regions after all: commenting out the change in the kernel done in r24494 fixes the problem. I'm now running r24865 in 32bit accelerated mode on my NV15. I don't know what is the first mapped region that is later on overlapped by my driver's request, but that deserves to be investigated. If that's legal then overlapping regions may not be blocked I'd say! Can someone (kernel) have a look at this???? Bye! Rudolf. PS: I'm posting this finding in ticket #1950 as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 22:19:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 20:19:49 -0000 Subject: [Haiku-bugs] [Haiku] #1950: Garbled screen contents with true colour mode on nvidia gf2mx In-Reply-To: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> References: <042.f15ad8e18c31676a011caebc5344d3a8@haiku-os.org> Message-ID: <051.ca47f2bde28c9f11cdc662cde7e4096a@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 ------------------------+--------------------------------------------------- Comment (by rudolfc): Hi there, I've traced the versions where it went wrong: r24493 is working OK; r24511 is faulty. It's MTRR-WC failed mapping because of overlapping regions after all: commenting out the change in the kernel done in r24494 fixes the problem. I'm now running r24865 in 32bit accelerated mode on my NV15. I don't know what is the first mapped region that is later on overlapped by my driver's request, but that deserves to be investigated. If that's legal then overlapping regions may not be blocked I'd say! Can someone (kernel) have a look at this???? Bye! Rudolf. PS: I'm posting this finding in ticket #2071 as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 26 23:56:49 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 21:56:49 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem Message-ID: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> #2265: KDL harddisk problem --------------------------+------------------------------------------------- Reporter: mrsunshine | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: x86 | --------------------------+------------------------------------------------- When booting straight out i get the kdl stated in the screenshots attached, im unable to get serial logs due to stupid laptop has no old school ports =) HDSize: 80GB lspci -nn: 00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950] (rev 10) 00:01.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a3f] 00:04.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a36] 00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37] 00:06.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a38] 00:07.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a39] 00:12.0 IDE interface [0101]: ATI Technologies Inc 4379 Serial ATA Controller [1002:4379] (rev 80) 00:13.0 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB Host Controller [1002:4374] (rev 80) 00:13.1 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB Host Controller [1002:4375] (rev 80) 00:13.2 USB Controller [0c03]: ATI Technologies Inc IXP SB400 USB2 Host Controller [1002:4373] (rev 80) 00:14.0 SMBus [0c05]: ATI Technologies Inc IXP SB400 SMBus Controller [1002:4372] (rev 83) 00:14.1 IDE interface [0101]: ATI Technologies Inc Standard Dual Channel PCI IDE Controller [1002:4376] (rev 80) 00:14.2 Audio device [0403]: ATI Technologies Inc SB450 HDA Audio [1002:437b] (rev 01) 00:14.3 ISA bridge [0601]: ATI Technologies Inc IXP SB400 PCI-ISA Bridge [1002:4377] (rev 80) 00:14.4 PCI bridge [0604]: ATI Technologies Inc IXP SB400 PCI-PCI Bridge [1002:4371] (rev 80) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS485 [Radeon Xpress 1100 IGP] [1002:5975] 02:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter [168c:001c] (rev 01) 08:01.0 CardBus bridge [0607]: ENE Technology Inc CB-712/4 Cardbus Controller [1524:1412] (rev 10) 08:01.1 FLASH memory [0501]: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller [1524:0530] (rev 01) 08:01.2 SD Host controller [0805]: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller [1524:0550] (rev 01) 08:01.3 FLASH memory [0501]: ENE Technology Inc FLASH memory: ENE Technology Inc: [1524:0520] (rev 01) 08:01.4 FLASH memory [0501]: ENE Technology Inc SD/MMC Card Reader Controller [1524:0551] (rev 01) 08:02.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 00:04:39 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 22:04:39 -0000 Subject: [Haiku-bugs] [Haiku] #2266: Notifications not send when attachment added to ticket Message-ID: <050.17dfb7c464ad7da6a748337b1ae2ee5b@haiku-os.org> #2266: Notifications not send when attachment added to ticket -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: haiku-web Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: Website/Trac | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Email notifications are not send when an attachment is added to a ticket. When monitoring tickets by email, this is unhandy. Please change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 01:29:05 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 23:29:05 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem In-Reply-To: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> References: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> Message-ID: <054.079ad06901677f0a85de9eb8005f0bb6@haiku-os.org> #2265: KDL harddisk problem ----------------------------+----------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by bonefish): * owner: marcusoverhagen => axeld * priority: normal => blocker * component: Drivers/Disk => System/Kernel * milestone: R1 => R1/alpha1 Comment: The problem can be reproduced under VMware, if the virtual machine has a second hard disk. It crashes in devfs_ioctl() (B_GET_MEDIA_STATUS). The log lists an earlier devfs_get_vnode(), but no devfs_open_vnode() for the concerned node. Interestingly the given cookie had been returned by an devfs_open() for another node earlier. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 01:33:05 2008 From: trac at haiku-os.org (Haiku) Date: Mon, 26 May 2008 23:33:05 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem In-Reply-To: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> References: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> Message-ID: <054.1ddc6bf8895325ecef022f4901c5e622@haiku-os.org> #2265: KDL harddisk problem ----------------------------+----------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by euan): Same issue here. 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380] 00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c] r25668 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 02:31:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 00:31:05 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.c4d67f1b57360bcbe7185145f4ab9dd4@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by tigerdog): Rudolph, thanks for finding this! Haiku without your driver is like Irish Coffee without the whiskey - still useable but not nearly as much fun. Kernel team, back to you! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 04:35:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 02:35:36 -0000 Subject: [Haiku-bugs] [Haiku] #2267: Sound plays with noise (using OSS) Message-ID: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> #2267: Sound plays with noise (using OSS) ----------------------------+----------------------------------------------- Reporter: apple7 | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Platform: x86 | ----------------------------+----------------------------------------------- firt: I'm new user of haiku, i have problem for reproducer sound. my card sound, is hd audio (alc883) after install OSS driver, the hard is detect, but sound is out with distortion.The test of OSS in terminal is good, but restart media_server the system failbure. info ~> /boot/home/config/bin/ossinfo Version info: OSS 4.1test0 (b 071114/200711250325 (0x00040003) GPL Platform: Haiku/BePC 1 r25633 May 24 2008 11:23:58 (unknown) Number of audio devices: 7 Number of audio engines: 7 Number of MIDI devices: 0 Number of mixer devices: 1 Device objects 0: oss0 OSS core services 1: hdaudio0 nVidia HD Audio HD Audio controller nVidia HD Audio Vendor ID 0x10de03f0 Subvendor ID 0x1019a88d Codec 0: ALC883 (0x10ec0883/0x1019c601) MIDI devices (/dev/midi*) Mixer devices (/dev/mixer*) 0: nVidia HD Audio ALC883 (Mixer 0 of device object 1) Audio devices /dev/oss/hdaudio0/pcm0 nVidia HD Audio front (device index 0) /dev/oss/hdaudio0/pcm1 nVidia HD Audio rear (device index 1) /dev/oss/hdaudio0/pcm2 nVidia HD Audio center/LFE (device index 2) /dev/oss/hdaudio0/pcm3 nVidia HD Audio side (device index 3) /dev/oss/hdaudio0/pcm4 nVidia HD Audio fp-front (device index 4) /dev/oss/hdaudio0/pcmin0 nVidia HD Audio rec1 (device index 5) /dev/oss/hdaudio0/pcmin1 nVidia HD Audio rec2 (device index 6) ~> attach screen of media_preference (thanks for time and sorry foy my english) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 04:56:51 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 02:56:51 -0000 Subject: [Haiku-bugs] [Haiku] #2262: "restrict" keyword issue in posix/search.h In-Reply-To: <042.1d247d0fc4942936a077b2378be431ed@haiku-os.org> References: <042.1d247d0fc4942936a077b2378be431ed@haiku-os.org> Message-ID: <051.578278b197a261113bc2dbfaac31158e@haiku-os.org> #2262: "restrict" keyword issue in posix/search.h ------------------------+--------------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by scottmc): * cc: scottmc (added) Comment: This affects tiff, maybe others. http://tools.assembla.com/BePorts/wiki/media-libs/tiff Adding myself to the cc so I'll know when I can try tiff again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 07:52:09 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 05:52:09 -0000 Subject: [Haiku-bugs] [Haiku] #2267: Sound plays with noise (using OSS) In-Reply-To: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> References: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> Message-ID: <050.4cad3c59e255fae980433690a66543ce@haiku-os.org> #2267: Sound plays with noise (using OSS) -----------------------------+---------------------------------------------- Reporter: apple7 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => mmu_man -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 13:23:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 11:23:22 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem In-Reply-To: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> References: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> Message-ID: <054.df5befac68eadf8910ac818a876fa408@haiku-os.org> #2265: KDL harddisk problem ----------------------------+----------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 13:34:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 11:34:01 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem In-Reply-To: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> References: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> Message-ID: <054.c7d32e9795d32beae82caa64d0d4804c@haiku-os.org> #2265: KDL harddisk problem ----------------------------+----------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: x86 ----------------------------+----------------------------------------------- Comment (by axeld): Replying to [comment:1 bonefish]: > Interestingly the given cookie had been returned by an devfs_open() for another node earlier. Yes, because someone didn't update the debug output when he changed the FS API recently ; you don't see the values you'd expect there yet :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 14:04:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 12:04:22 -0000 Subject: [Haiku-bugs] [Haiku] #2265: KDL harddisk problem In-Reply-To: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> References: <045.6428bb0e03c52f8433d644cb009e38d8@haiku-os.org> Message-ID: <054.40ef636523243d5736830fb9ace33de1@haiku-os.org> #2265: KDL harddisk problem ----------------------------+----------------------------------------------- Reporter: mrsunshine | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Platform: x86 ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r25670. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 14:10:30 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 12:10:30 -0000 Subject: [Haiku-bugs] [Haiku] #2267: Sound plays with noise (using OSS) In-Reply-To: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> References: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> Message-ID: <050.69c6359779fd1f84d562b82b25f45d21@haiku-os.org> #2267: Sound plays with noise (using OSS) -----------------------------+---------------------------------------------- Reporter: apple7 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by bipolar): I have the same issues in my system, two sound cards: SiS 7018 and Aureal Vortex 2 (8820). Sound comming out from the media_server is heavily distorted, "stretched in time" so it seems and with frequent pauses/hiccups. But... After quitting the media_server, running oss_test from the terminal goes all well. Sound is great for both devices. I'm willing to test this further, just shout. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 14:41:00 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 12:41:00 -0000 Subject: [Haiku-bugs] [Haiku] #2264: Media Checker Crash In-Reply-To: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> References: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> Message-ID: <050.00e49e399b36ce735b64aab2fd79139e@haiku-os.org> #2264: Media Checker Crash ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by kvdman): This was apparently fixed as #2265 in r25670. At least the screenshot looks the exact same as the one I provided. [http://cia.vc/stats/project/OpenBeOS/.message/8089ae] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:08:51 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:08:51 -0000 Subject: [Haiku-bugs] [Haiku] #514: [NetPositive] slow scroll with middle button In-Reply-To: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> References: <040.5789c52c63dcd0ef5cf721e7d5938c4d@haiku-os.org> Message-ID: <049.6e9efc757b969915a3b2f8b9c23a0418@haiku-os.org> #514: [NetPositive] slow scroll with middle button ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * platform: => All * component: - General => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:13:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:13:23 -0000 Subject: [Haiku-bugs] [Haiku] #926: [app_server] could dead lock when scrolling in NetPositive In-Reply-To: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> References: <040.c255cf763563c3d545ea7e5c87f12e05@haiku-os.org> Message-ID: <049.cee4072f250215b0e9f0e68efdf21c5a@haiku-os.org> #926: [app_server] could dead lock when scrolling in NetPositive ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): I think this bug could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:21:00 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:21:00 -0000 Subject: [Haiku-bugs] [Haiku] #1315: [app_server] shifted images in ScreenSaver In-Reply-To: <040.b884e1091b64b11e72f50fba8a03b409@haiku-os.org> References: <040.b884e1091b64b11e72f50fba8a03b409@haiku-os.org> Message-ID: <049.5df1e3a3f2b4eb54f91ecc415a0db60d@haiku-os.org> #1315: [app_server] shifted images in ScreenSaver ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by diver): * summary: [ScreenSaver] shifted images => [app_server] shifted images in ScreenSaver -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:22:49 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:22:49 -0000 Subject: [Haiku-bugs] [Haiku] #1403: vlance driver calls acquire_sem_etc() from its interrupt routine In-Reply-To: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> References: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> Message-ID: <049.1e095852b0735d15b66fe9722fedaa10@haiku-os.org> #1403: vlance driver calls acquire_sem_etc() from its interrupt routine ------------------------------+--------------------------------------------- Reporter: diver | Owner: Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by diver): Axel? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:17:02 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:17:02 -0000 Subject: [Haiku-bugs] [Haiku] #927: [nvidia] stability problems with GeForce 7300 In-Reply-To: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> References: <040.4551861d616e1c747f375cd9bac88b12@haiku-os.org> Message-ID: <049.e91327f504bb6f4c9646c660daaf1c90@haiku-os.org> #927: [nvidia] stability problems with GeForce 7300 --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Changes (by diver): * cc: rudolfc (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:25:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:25:56 -0000 Subject: [Haiku-bugs] [Haiku] #1409: [app_server] crash in BPrivate::processHeap In-Reply-To: <040.781773159d87eb9d098654b6982c40c4@haiku-os.org> References: <040.781773159d87eb9d098654b6982c40c4@haiku-os.org> Message-ID: <049.ead383552dd5579adee2aa75226c9f34@haiku-os.org> #1409: [app_server] crash in BPrivate::processHeap ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Never happend to me again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:27:15 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:27:15 -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.71f17ae5c7a6794b73d166308fabc4c7@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 Resolution: | Platform: All -----------------------------------+---------------------------------------- Changes (by diver): * cc: siarzhuk, fyysik (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:30:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:30:56 -0000 Subject: [Haiku-bugs] [Haiku] #1947: [PackageInstaller] fails to install ButterFly pkg In-Reply-To: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> References: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> Message-ID: <049.854f30293f561a2ec936001f34c3f0b8@haiku-os.org> #1947: [PackageInstaller] fails to install ButterFly pkg --------------------------------------------+------------------------------- Reporter: diver | Owner: sil2100 Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Resolution: | Platform: All --------------------------------------------+------------------------------- Comment (by diver): This bug could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:32:43 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:32:43 -0000 Subject: [Haiku-bugs] [Haiku] #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size. In-Reply-To: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> References: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> Message-ID: <049.03e4afed6ff43b7bfe01f2430a8da03d@haiku-os.org> #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size. ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by diver): * owner: axeld => bonefish * component: - General => Build System -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:33:50 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:33:50 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.50f6fe430821cb49e342127e1b44b6a1@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): I think this should be fixed before R1 alpha. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:36:04 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:36:04 -0000 Subject: [Haiku-bugs] [Haiku] #1403: vlance driver calls acquire_sem_etc() from its interrupt routine In-Reply-To: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> References: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> Message-ID: <049.6c3ba0140209218e4a4b553f46a46e50@haiku-os.org> #1403: vlance driver calls acquire_sem_etc() from its interrupt routine ------------------------------+--------------------------------------------- Reporter: diver | Owner: Type: bug | Status: new Priority: low | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => low Comment: The driver still has this bug. I'm not sure if this driver supports some actual hardware besides VMware; if not, we should just remove it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:36:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:36:22 -0000 Subject: [Haiku-bugs] [Haiku] #2205: [S3 diver] screen goes black after reboot In-Reply-To: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> References: <040.75fa08d63aaa8210a84551e299218f7a@haiku-os.org> Message-ID: <049.c99d895fae955812c0cb814045b7258e@haiku-os.org> #2205: [S3 diver] screen goes black after reboot -------------------------------+-------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: All -------------------------------+-------------------------------------------- Comment (by diver): We need subcomponent for s3 driver with Gerald as owner. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:38:32 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:38:32 -0000 Subject: [Haiku-bugs] [Haiku] #1571: [audio_mixer] remove useless info tab (easy) In-Reply-To: <040.9615be92d428f54b02c4fb04af049cdf@haiku-os.org> References: <040.9615be92d428f54b02c4fb04af049cdf@haiku-os.org> Message-ID: <049.350371f7c2ef70b9d521f1614cec32ef@haiku-os.org> #1571: [audio_mixer] remove useless info tab (easy) --------------------------------+------------------------------------------- Reporter: diver | Owner: leavengood Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by diver): Any decision? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:39:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:39:10 -0000 Subject: [Haiku-bugs] [Haiku] #134: [SoundRecorder] doesn't start In-Reply-To: <040.48eed639ab99e1fa58e48ec9edca3c67@haiku-os.org> References: <040.48eed639ab99e1fa58e48ec9edca3c67@haiku-os.org> Message-ID: <049.a5e21a3b101e2baadfcd5d23b5eb23ea@haiku-os.org> #134: [SoundRecorder] doesn't start -----------------------------------------+---------------------------------- Reporter: diver | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/SoundRecorder | Version: Resolution: | Platform: All -----------------------------------------+---------------------------------- Changes (by diver): * summary: SoundRecorder doesn't start => [SoundRecorder] doesn't start -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 15:44:38 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 13:44:38 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.9dedd3618a2556086a84a20e84e63ae4@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by diver): Still here in r25655. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 16:03:01 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 14:03:01 -0000 Subject: [Haiku-bugs] [Haiku] #1409: [app_server] crash in BPrivate::processHeap In-Reply-To: <040.781773159d87eb9d098654b6982c40c4@haiku-os.org> References: <040.781773159d87eb9d098654b6982c40c4@haiku-os.org> Message-ID: <049.099aaccd712ef64be7953eb774552f17@haiku-os.org> #1409: [app_server] crash in BPrivate::processHeap ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, closing. Definitely looks like something that would have been fixed meanwhile. Please reopen if it ever happens again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 16:04:17 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 14:04:17 -0000 Subject: [Haiku-bugs] [Haiku] #1947: [PackageInstaller] fails to install ButterFly pkg In-Reply-To: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> References: <040.90189cb09709edd4c8bc4ae79f81a4ad@haiku-os.org> Message-ID: <049.76eac24df805a25a1ba22074100878ca@haiku-os.org> #1947: [PackageInstaller] fails to install ButterFly pkg --------------------------------------------+------------------------------- Reporter: diver | Owner: sil2100 Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/PackageInstaller | Version: R1 development Resolution: fixed | Platform: All --------------------------------------------+------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Ok, thanks for updating. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 16:12:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 14:12:57 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.031ea50d60877a80de0133e668f2a302@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by stippi): I did fix the flickering for VESA and I have a plan for how it could be fixed it for accelerated drivers: By using a back buffer that is used only for the region touched by such transparent overlays, separating drawing commands that arrive intersecting with this region into a part that is drawn in software (to the back buffer) and another part which is rendered to the front buffer (accelerated for certain commands). The part that touched the back buffer is then composited with the overlay and copied to the front buffer. This would eliminate flickering in a way similar to the current VESA mode while still using acceleration. If someone wrote a driver for AMD X1400 hardware, that would certainly boost my motivation to work on this... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 16:19:33 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 14:19:33 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.9dd0f1a90ed64a9c1324bcc42b81246d@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): Strange, but several months ago moving an icon didn't cause flickering. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 17:06:13 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 15:06:13 -0000 Subject: [Haiku-bugs] [Haiku] #2264: Media Checker Crash In-Reply-To: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> References: <041.e2a5984b09146a586731d21bc98d6bae@haiku-os.org> Message-ID: <050.218e4a1ff02156cd875c763f7e1da27b@haiku-os.org> #2264: Media Checker Crash ------------------------------+--------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Device Kit | Version: R1 development Resolution: duplicate | Platform: All ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate Comment: Yes, indeed, it was the same thing. Apparently #2265 is a duplicate of this one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 17:20:49 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 15:20:49 -0000 Subject: [Haiku-bugs] [Haiku] #2254: [patch] please enable user-mode filters in libpcap In-Reply-To: <038.e8dd08096ea6316c817f40fa7c07730c@haiku-os.org> References: <038.e8dd08096ea6316c817f40fa7c07730c@haiku-os.org> Message-ID: <047.5a34c6f528f9a137ddc8737597d824d0@haiku-os.org> #2254: [patch] please enable user-mode filters in libpcap ------------------------+--------------------------------------------------- Reporter: mjw | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r25673. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 17:44:30 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 15:44:30 -0000 Subject: [Haiku-bugs] [Haiku] #361: [Tracker] wrong scrollbar alignment In-Reply-To: <040.b3ae7dfbdfd0076e984b777efb05de3b@haiku-os.org> References: <040.b3ae7dfbdfd0076e984b777efb05de3b@haiku-os.org> Message-ID: <049.0b6b2170ec6aea4a304c1d2a0c8451f3@haiku-os.org> #361: [Tracker] wrong scrollbar alignment -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by jackburton): Could this have been fixed in r25559 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 17:51:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 15:51:10 -0000 Subject: [Haiku-bugs] [Haiku] #734: missing mkbfs utility In-Reply-To: <057.fda55eeca2c4d55f3c591df39fd8c419@haiku-os.org> References: <057.fda55eeca2c4d55f3c591df39fd8c419@haiku-os.org> Message-ID: <066.917f50eb8fb5df15dfd84035175bdb6a@haiku-os.org> #734: missing mkbfs utility ----------------------------------------------+----------------------------- Reporter: adeynichenko at gmail.com | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: | Platform: All ----------------------------------------------+----------------------------- Comment (by jackburton): Shouldn't this be closed ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 17:51:36 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 15:51:36 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.23fed3fb77209c5890376d79538184b3@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by jackburton): So, let's close this one :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 18:38:24 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 16:38:24 -0000 Subject: [Haiku-bugs] [Haiku] #1403: vlance driver calls acquire_sem_etc() from its interrupt routine In-Reply-To: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> References: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> Message-ID: <049.5f3bd63b240e5b6c2141355dde8dfbd3@haiku-os.org> #1403: vlance driver calls acquire_sem_etc() from its interrupt routine ------------------------------+--------------------------------------------- Reporter: diver | Owner: Type: bug | Status: new Priority: low | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by umccullough): I believe the VMWare vlance interface emulates the AMD PCNet32 device which does supposedly exist in real hardware (although I've personally not ever seen it myself). Whether this vlance driver was also written to support the original AMD PCNet32 devices, on the other hand, I have no clue. FWIW, I do remember Travis telling me that NewOS previously had a rudimentary pcnet32 driver as well... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 18:43:22 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 16:43:22 -0000 Subject: [Haiku-bugs] [Haiku] #897: Missing symbol for Corum III: ReadFrames In-Reply-To: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> References: <043.6f9f94e045fee493105bc012ead17e93@haiku-os.org> Message-ID: <052.0daf302f73ff7ba7c7e2a296d5e5eac6@haiku-os.org> #897: Missing symbol for Corum III: ReadFrames -----------------------------+---------------------------------------------- Reporter: darkwyrm | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: fixed | Platform: All -----------------------------+---------------------------------------------- Changes (by mmu_man): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 19:00:31 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 17:00:31 -0000 Subject: [Haiku-bugs] [Haiku] #734: missing mkbfs utility In-Reply-To: <057.fda55eeca2c4d55f3c591df39fd8c419@haiku-os.org> References: <057.fda55eeca2c4d55f3c591df39fd8c419@haiku-os.org> Message-ID: <066.bc3e5d6396675507fe4e4fe31d9b327e@haiku-os.org> #734: missing mkbfs utility ----------------------------------------------+----------------------------- Reporter: adeynichenko at gmail.com | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Platform: All ----------------------------------------------+----------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Indeed, mkfs is part of the image since r25491. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 20:05:28 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 18:05:28 -0000 Subject: [Haiku-bugs] [Haiku] #2268: vm_page_fault in kernel space with RTL8139 network card Message-ID: <040.1d034efa4c1f43516de33b44197aa7f1@haiku-os.org> #2268: vm_page_fault in kernel space with RTL8139 network card --------------------------------+------------------------------------------- Reporter: monni | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- Crashes while browsing with firefox, downloading several or long files using wget. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 20:08:59 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 18:08:59 -0000 Subject: [Haiku-bugs] [Haiku] #2269: KDL at startup r 25668 Message-ID: <043.78fd87d10e25128890e40d2f94dbf301@haiku-os.org> #2269: KDL at startup r 25668 -----------------------+---------------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- something changed between 25654 and 25668 resulting in KDL at startup: KDiskSystem::Load():file_system/bfs/v1->1 trying:file_systems/devfs/v1 returned -1 Panic vm_page_fault:unhandled pagefault in kernel space at 0x30 ip 0x800566ce Maybe something to do with recent changes to ATA bus manager and known temporary regressions? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 20:46:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 18:46:05 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk Message-ID: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk --------------------------+------------------------------------------------- Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- When installing Haiku with Firefox optional package on very small real partition, Haiku deletes /dev/sda1 node and fails to install without repartitioning drive and rebooting Linux. When looking at the partition boundaries using cfdisk, it seems end of the partition gets overwritten in partition table. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 21:00:57 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 19:00:57 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.0d60e1c63003a93d1302bf7204f36c7a@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by stippi): Ahm... just to make sure we are talking about the same thing: I am talking about the flickering of the transparent icon that gets attached to the mouse. The flickering is caused by the cursor+icon being removed from the screen and reappearing at the new position when you move the mouse. You mean the same thing, right? What graphics hardware do you use? Does Haiku have a driver for it? Did that situation change a couple months ago? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 21:19:10 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 19:19:10 -0000 Subject: [Haiku-bugs] [Haiku] #2268: vm_page_fault in kernel space with RTL8139 network card In-Reply-To: <040.1d034efa4c1f43516de33b44197aa7f1@haiku-os.org> References: <040.1d034efa4c1f43516de33b44197aa7f1@haiku-os.org> Message-ID: <049.8fd546b9475bb900dc76bc26f3875608@haiku-os.org> #2268: vm_page_fault in kernel space with RTL8139 network card ---------------------------------+------------------------------------------ Reporter: monni | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by axeld): This is probably a duplicate of bug #1641. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 21:21:47 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 19:21:47 -0000 Subject: [Haiku-bugs] [Haiku] #2269: KDL at startup r 25668 In-Reply-To: <043.78fd87d10e25128890e40d2f94dbf301@haiku-os.org> References: <043.78fd87d10e25128890e40d2f94dbf301@haiku-os.org> Message-ID: <052.7af7c88b295f52ff5ea55a3a4ab62d6a@haiku-os.org> #2269: KDL at startup r 25668 ------------------------+--------------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: This revision is already outdated, and this bug has already been fixed since r25670. Please always retest with a current revision before reporting a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 22:10:37 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 20:10:37 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.27196f99b4b8d98bd51c0a3d8f2a93a3@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by paulogeyer): * component: - General => Network & Internet Comment: Hi, i've installed haiku on my disk today, and i couldn't use the BCM44xx driver. I seems to be loaded, but i can't get dhcp information from my network, i've tried to set up manually, but it didn't work too. paulo at samsa:~$ lspci |grep Eth 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 22:26:45 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 20:26:45 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.030db9731f2335ae6291099f8f4cc776@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by umccullough): Did you use the ported bfe driver attached to this ticket? or the GPL bcm44xx driver that is already in the Haiku repo? They are different drivers, I don't think the one attached to this ticket is in the repo yet (although, perhaps it should be?). Also, when running lspci, it's always a good idea to throw -nn parameter on there to also pull the vendor/deviceid in the text. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 22:46:23 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 20:46:23 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk In-Reply-To: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> References: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> Message-ID: <049.afdb9d47195a55e4e2cd24c6f614e954@haiku-os.org> #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Please provide the following information: - All relevant build variables you set (in doubt your complete UserBuildConfig). - The command line you use to invoke jam. - The build output. - The exact size of the concerned partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 22:53:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 20:53:05 -0000 Subject: [Haiku-bugs] [Haiku] #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size. In-Reply-To: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> References: <040.9a8eb2429d3cd6ebe92663ee8a3d9a75@haiku-os.org> Message-ID: <049.1dfbbdb90a82e31f11372b43770a346a@haiku-os.org> #2012: [HaikuImage] Remove Bitstream fonts to reduce haiku image size. ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by bonefish): * owner: bonefish => axeld * component: Build System => Servers/app_server Comment: No clue what those fonts are good for. Bouncing to the app server component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:04:05 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:04:05 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.a45903a389db2d7505850cd871a9fb74@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by paulogeyer): paulo at samsa:~$ lspci |grep Eth 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) paulo at samsa:~$ lspci -nm|grep 06:01.0 06:01.0 "0200" "14e4" "170c" -r02 "1025" "0090" i've tried the broadcom driver from the haiku repo, i'll try this bfe now Replying to [comment:4 umccullough]: > Did you use the ported bfe driver attached to this ticket? or the GPL bcm44xx driver that is already in the Haiku repo? > > They are different drivers, I don't think the one attached to this ticket is in the repo yet (although, perhaps it should be?). > > Also, when running lspci, it's always a good idea to throw -nn parameter on there to also pull the vendor/deviceid in the text. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:05:32 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:05:32 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.220038f617bcf4d1e536fe4ad4dc0c3d@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by andybe): Replying to [comment:4 umccullough]: > Did you use the ported bfe driver attached to this ticket? or the GPL bcm44xx driver that is already in the Haiku repo? > > They are different drivers, I don't think the one attached to this ticket is in the repo yet (although, perhaps it should be?). > > Also, when running lspci, it's always a good idea to throw -nn parameter on there to also pull the vendor/deviceid in the text. This is a skeleton of bcm440 driver port from freebsd, it is not finished yet. I tested some source on my laptop, but fail on transfer. I got no time yet to look at it. This driver doesn't stop (hang up on irq) like the gpl one here in the source tree. AndyBe -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:19:07 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:19:07 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.cece8406bea82bd4fdf74aa7125c2166@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by scottmc): * summary: libpng needs update to 1.2.28 to fix security issue => libpng needs update >= 1.2.28 to fix security issue Comment: v1.2.29 is now out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:22:06 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:22:06 -0000 Subject: [Haiku-bugs] [Haiku] #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found In-Reply-To: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> References: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> Message-ID: <051.f19523865ba4e073d1ee82bce4f57c11@haiku-os.org> #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): Ok, it seems to be better with r25673 running on it now. I've tried 5 or 6 reboots and restarts but always boots all the way up now. Can close this one now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:25:39 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:25:39 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.b588e614a569902af830bfd73035a0e5@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Comment (by paulogeyer): also, how do i use this? i've found there's a jamfile, but i don't know how to compile Replying to [comment:6 andybe]: > Replying to [comment:4 umccullough]: > > Did you use the ported bfe driver attached to this ticket? or the GPL bcm44xx driver that is already in the Haiku repo? > > > > They are different drivers, I don't think the one attached to this ticket is in the repo yet (although, perhaps it should be?). > > > > Also, when running lspci, it's always a good idea to throw -nn parameter on there to also pull the vendor/deviceid in the text. > > This is a skeleton of bcm440 driver port from freebsd, it is not finished yet. I tested some source on my laptop, but fail on transfer. I got no time yet to look at it. This driver doesn't stop (hang up on irq) like the gpl one here in the source tree. > > AndyBe -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:39:39 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:39:39 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.cac91fe61b0912722a1ba4d0082ff737@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ---------------------------------+------------------------------------------ Reporter: andybe | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by umccullough): * type: bug => enhancement Comment: Replying to [comment:5 paulogeyer]: > i've tried the broadcom driver from the haiku repo If you're having problems with the one in the Haiku repo, you should probably open a separate bug for that since this ticket doesn't really appear to be a bug so much as a submission of a partially ported driver :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:46:31 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:46:31 -0000 Subject: [Haiku-bugs] [Haiku] #2271: checking whether -lc should be explicitly linked in results in a yes Message-ID: <042.48bb248d28b9410ded168c125d270e4c@haiku-os.org> #2271: checking whether -lc should be explicitly linked in results in a yes -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- While trying to build libSDL under Haiku as i586-haiku, the configure check for -lc results in a "yes", causing make to fail for not finding -lc. This may or may not be a problem with Haiku. but changing to --build=i586-beos also it to build. From the config.log output: {{{ configure:8437: checking whether -lc should be explicitly linked in configure:8442: gcc -c -I/boot/home/config/include -I./include -D_GNU_SOURCE=1 -I./include -D_GNU_SOURCE=1 conftest.c >&5 configure:8445: $? = 0 configure:8460: gcc -nostart conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| grep -lc \>/dev/null 2\>\&1 configure:8463: $? = 1 configure:8475: result: yes }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:46:27 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:46:27 -0000 Subject: [Haiku-bugs] [Haiku] #2047: bfe (broadcom bcm44x) driver In-Reply-To: <041.061548526823b6f5f906d872804dc132@haiku-os.org> References: <041.061548526823b6f5f906d872804dc132@haiku-os.org> Message-ID: <050.3ff08e49da667b63ca1807ef4c0c2591@haiku-os.org> #2047: bfe (broadcom bcm44x) driver ------------------------------+--------------------------------------------- Reporter: andybe | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Changes (by umccullough): * component: Network & Internet => Drivers/Network Comment: Hopefully enhancement is the right type... but forgot to update the others -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 27 23:55:56 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 21:55:56 -0000 Subject: [Haiku-bugs] [Haiku] #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found In-Reply-To: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> References: <042.16415aefa711796e26fd6a358645e12f@haiku-os.org> Message-ID: <051.7ad6ab09c9bfdd2b009a39cdd491b154@haiku-os.org> #2063: AMD Geode nano-size motherboard sometimes hangs at usb_uhci: no devices found ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: All ------------------------+--------------------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Cool, thanks for checking. Please reopen if it isn't fixed after all! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 00:09:27 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 22:09:27 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk In-Reply-To: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> References: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> Message-ID: <049.addc66744642a83271dbe2477b713ea9@haiku-os.org> #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by monni): Replying to [comment:1 bonefish]: > Please provide the following information: > - All relevant build variables you set (in doubt your complete UserBuildConfig). > - The command line you use to invoke jam. > - The build output. > - The exact size of the concerned partition. Build variables: HAIKU_IMAGE_DIR = /dev ; HAIKU_IMAGE_NAME = sda1 ; HAIKU_IMAGE_SIZE = 100 ; AddOptionalHaikuImagePackages Vision Firefox ; command line to invoke jam: jam haiku-image Exact size of the partition is 2441.4 MB, but if I put it in HAIKU_IMAGE_SIZE, it errors out even earlier. Can't get build output right now as I have to boot through Ubuntu Live CD because bootman doesn't support booting from SCSI drives and I can't change boot order from BIOS. Obviously it should ignore the HAIKU_IMAGE_SIZE, but for some reasons it forgets that it is writing to real drive instead of image file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 01:10:12 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 23:10:12 -0000 Subject: [Haiku-bugs] [Haiku] #2271: checking whether -lc should be explicitly linked in results in a yes In-Reply-To: <042.48bb248d28b9410ded168c125d270e4c@haiku-os.org> References: <042.48bb248d28b9410ded168c125d270e4c@haiku-os.org> Message-ID: <051.02f38636fc12b65ed6537c66d0d7084b@haiku-os.org> #2271: checking whether -lc should be explicitly linked in results in a yes ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Changes (by andreasf): * cc: andreasf (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 01:38:39 2008 From: trac at haiku-os.org (Haiku) Date: Tue, 27 May 2008 23:38:39 -0000 Subject: [Haiku-bugs] [Haiku] #2271: checking whether -lc should be explicitly linked in results in a yes In-Reply-To: <042.48bb248d28b9410ded168c125d270e4c@haiku-os.org> References: <042.48bb248d28b9410ded168c125d270e4c@haiku-os.org> Message-ID: <051.599b996a8c88f9d4fdc15107a56b683c@haiku-os.org> #2271: checking whether -lc should be explicitly linked in results in a yes ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Platform: All ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: As already written on the HaikuPorts mailing list, I don't see how that would be a Haiku problem. Even if it were a related bug in the auto tools port (which I don't think it is), let's track it at HaikuPorts. My best guess is that you haven't run libtoolize correctly, BTW. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 03:19:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 01:19:59 -0000 Subject: [Haiku-bugs] [Haiku] #1403: vlance driver calls acquire_sem_etc() from its interrupt routine In-Reply-To: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> References: <040.47891ae93a2af2afa21eb597269a0102@haiku-os.org> Message-ID: <049.23c203b44749e301f0d511ca5e8a2076@haiku-os.org> #1403: vlance driver calls acquire_sem_etc() from its interrupt routine ------------------------------+--------------------------------------------- Reporter: diver | Owner: Type: bug | Status: new Priority: low | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Platform: All ------------------------------+--------------------------------------------- Comment (by umccullough): Even more interesting, it looks like Haiku's repo already has the beginnings of a FreeBSD port of "if_le" which includes pcnet/lance: http://dev.haiku-os.org/browser/haiku/trunk/src/add- ons/kernel/drivers/network/pcnet/dev/le Maybe if that was finished, vlance could be replaced in the image. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 09:53:44 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 07:53:44 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk In-Reply-To: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> References: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> Message-ID: <049.690beef61b9a522238c471de408888c9@haiku-os.org> #2270: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by axeld): It would be interesting if we could stop jam from deleting failed targets - that would definitely be nice for the image target. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 12:33:59 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 10:33:59 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Build system deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk In-Reply-To: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> References: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> Message-ID: <049.4aeb13ac1268f09ea1f4523110f44e41@haiku-os.org> #2270: Build system deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by stippi): * summary: Installer deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk => Build system deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk Comment: Ah, now I get it. I was thinking the actual Installer application does something like that! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 18:24:57 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 16:24:57 -0000 Subject: [Haiku-bugs] [Haiku] #2272: forkpty() symbol is missing in default build Message-ID: <040.af67970e9efeae780ff45b3ba49169dd@haiku-os.org> #2272: forkpty() symbol is missing in default build --------------------------+------------------------------------------------- Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- When compiling muscle test suite, it compiles fine when I add bsd/libutil.h, but linker complains about missing symbol forkpty. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 18:51:19 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 16:51:19 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.9c4405772573520d31aa5e4821f5f43a@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): Ah, I see. There is no flickering in vmware. And I only recently started testing on real hw. So that situation din't changed. False alarm, sorry. Should this be moved to app_server component? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 19:03:30 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 17:03:30 -0000 Subject: [Haiku-bugs] [Haiku] #2273: [runtime_loader] double clicking it leads to proplems Message-ID: <040.0751f733a1ff9f8944c298bce34adefe@haiku-os.org> #2273: [runtime_loader] double clicking it leads to proplems -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Platform: All | -----------------------------------+---------------------------------------- If you double click runtime_loader you will not be able to launch any other app. Also there will be empty items in Team Monitor. Tested in vmware with r25683. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 19:17:42 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 17:17:42 -0000 Subject: [Haiku-bugs] [Haiku] #2273: [runtime_loader] double clicking it leads to problems In-Reply-To: <040.0751f733a1ff9f8944c298bce34adefe@haiku-os.org> References: <040.0751f733a1ff9f8944c298bce34adefe@haiku-os.org> Message-ID: <049.655ef744748d1f6d764789816a0e48ba@haiku-os.org> #2273: [runtime_loader] double clicking it leads to problems ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: | Platform: All ------------------------------------+--------------------------------------- Changes (by diver): * summary: [runtime_loader] double clicking it leads to proplems => [runtime_loader] double clicking it leads to problems -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 19:19:38 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 17:19:38 -0000 Subject: [Haiku-bugs] [Haiku] #361: [Tracker] wrong scrollbar alignment In-Reply-To: <040.b3ae7dfbdfd0076e984b777efb05de3b@haiku-os.org> References: <040.b3ae7dfbdfd0076e984b777efb05de3b@haiku-os.org> Message-ID: <049.516414fd3c7ce472d0bb1e89a5b00c34@haiku-os.org> #361: [Tracker] wrong scrollbar alignment -----------------------------------+---------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: Resolution: | Platform: All -----------------------------------+---------------------------------------- Comment (by diver): Not realy, just tested and alignment is still wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 20:30:40 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 18:30:40 -0000 Subject: [Haiku-bugs] [Haiku] #2013: [Tracker] Dragging a file around make icon redraw constantly. In-Reply-To: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> References: <040.098030b327ea9466cb2abeb42feaf1e6@haiku-os.org> Message-ID: <049.e8cbb802897192a1dfa19ea1965bd0f3@haiku-os.org> #2013: [Tracker] Dragging a file around make icon redraw constantly. ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Resolution: | Platform: All ---------------------------------+------------------------------------------ Changes (by stippi): * component: Applications/Tracker => Servers/app_server Comment: Oh, yeah, thanks for noticing. Tracker has nothing to do with it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 20:44:44 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 18:44:44 -0000 Subject: [Haiku-bugs] [Haiku] #2274: The use of ETHER_DEBUG macro in etherpci.c produce warnings Message-ID: <043.ff813f900ed1bd4b37c096f64efb4f8a@haiku-os.org> #2274: The use of ETHER_DEBUG macro in etherpci.c produce warnings -----------------------------+---------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Platform: All | -----------------------------+---------------------------------------------- Cc generated/objects/haiku/x86/release/add- ons/kernel/drivers/network/etherpci/etherpci.o src/add-ons/kernel/drivers/network/etherpci/etherpci.c: In function `open_hook': src/add-ons/kernel/drivers/network/etherpci/etherpci.c:1497: warning: unsigned int format, pointer arg (arg 3) src/add-ons/kernel/drivers/network/etherpci/etherpci.c: In function `close_hook': src/add-ons/kernel/drivers/network/etherpci/etherpci.c:1546: warning: unsigned int format, pointer arg (arg 2) src/add-ons/kernel/drivers/network/etherpci/etherpci.c: In function `free_hook': src/add-ons/kernel/drivers/network/etherpci/etherpci.c:1616: warning: char format, etherpci_private_t arg (arg 2) src/add-ons/kernel/drivers/network/etherpci/etherpci.c:1616: warning: too few arguments for format src/add-ons/kernel/drivers/network/etherpci/etherpci.c: In function `control_hook': src/add-ons/kernel/drivers/network/etherpci/etherpci.c:1709: warning: too few arguments for format -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 21:34:43 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 19:34:43 -0000 Subject: [Haiku-bugs] [Haiku] #2275: Radeon driver GCC4 issues. Message-ID: <039.a2808672f1309807033e7095f55f6353@haiku-os.org> #2275: Radeon driver GCC4 issues. -------------------------------------+-------------------------------------- Reporter: euan | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Platform: x86 | -------------------------------------+-------------------------------------- Radeon driver fails to run when built with GCC4. Bad stuff happens, and darkness is final outcome. Log to follow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 22:46:14 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 20:46:14 -0000 Subject: [Haiku-bugs] [Haiku] #2272: forkpty() symbol is missing in default build In-Reply-To: <040.af67970e9efeae780ff45b3ba49169dd@haiku-os.org> References: <040.af67970e9efeae780ff45b3ba49169dd@haiku-os.org> Message-ID: <049.b053ddf4bbdd1a37d059f7e6c11cafcb@haiku-os.org> #2272: forkpty() symbol is missing in default build ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Platform: All ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Removed forkpty() prototype in r25684. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 28 23:29:26 2008 From: trac at haiku-os.org (Haiku) Date: Wed, 28 May 2008 21:29:26 -0000 Subject: [Haiku-bugs] [Haiku] #1203: Haiku USB in BeOS R5 In-Reply-To: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> References: <041.a998994b38b90fc6acdc0bd1164ac15d@haiku-os.org> Message-ID: <050.68240e45104d541d4113886aedc298a7@haiku-os.org> #1203: Haiku USB in BeOS R5 --------------------------+------------------------------------------------- Reporter: nutela | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by nutela): Hi I tested the new revision 25683 IIRC of the USB stack on R5, because building a new haiku image takes much more time, I don't know if this is still compatible with R5. It crashes into KDL on boot, only when no USB devices are attached will it boot fully. There is also a 2nd earlier bug still present, when I connect my wacom graphire the mouse and the wacom both seem to control the cursor which should be fine but after a while the mouse stops controlling the cursor and will only regain control after the wacom has been pulled out. I have a KDL pic of the version proir to this one but honestly I don't know exactly which one this is so I'll leave it at that for the moment, the bug manifest itself in this version on R5 as well so... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 05:30:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 03:30:41 -0000 Subject: [Haiku-bugs] [Haiku] #2275: Radeon driver GCC4 issues. In-Reply-To: <039.a2808672f1309807033e7095f55f6353@haiku-os.org> References: <039.a2808672f1309807033e7095f55f6353@haiku-os.org> Message-ID: <048.80e94daa2e0257491226c9167d7b936b@haiku-os.org> #2275: Radeon driver GCC4 issues. --------------------------------------+------------------------------------- Reporter: euan | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Resolution: | Platform: x86 --------------------------------------+------------------------------------- Comment (by anevilyak): FYI, the system itself appears to be running OK...keyboard is responding to numlock, I can ping, etc., it's just the display that's in an invalid mode. Let me know what else I can do to help debug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 07:06:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 05:06:41 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.5ccb850213d771a0ab513b8bcdd41b44@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by tigerdog): On a hunch, I tried starting with "don't call the bios" and accelerated graphics works here! Thought this might be useful info. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 09:32:56 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 07:32:56 -0000 Subject: [Haiku-bugs] [Haiku] #805: Fast read/write locker In-Reply-To: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> References: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> Message-ID: <049.5ebd28743ad4417ebad8dda62f0f2e5b@haiku-os.org> #805: Fast read/write locker ---------------------------------------+------------------------------------ Reporter: axeld | Owner: Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by axeld): * priority: normal => low * component: System/Kernel => Network & Internet/Stack -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 11:18:21 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 09:18:21 -0000 Subject: [Haiku-bugs] [Haiku] #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript Message-ID: <041.f9f58f7e0cf34ebcd31e27d5ccf95a8b@haiku-os.org> #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript --------------------------+------------------------------------------------- Reporter: stippi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Platform: All | --------------------------+------------------------------------------------- For example, if I put "Stephan A?mus" there, the boot icons light up until the rocket and then all activity stops. Either this is a build system problem or a problem in the multi-user code paths. Assigning to Ingo in any case... :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 11:29:59 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 09:29:59 -0000 Subject: [Haiku-bugs] [Haiku] #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript In-Reply-To: <041.f9f58f7e0cf34ebcd31e27d5ccf95a8b@haiku-os.org> References: <041.f9f58f7e0cf34ebcd31e27d5ccf95a8b@haiku-os.org> Message-ID: <050.4e27e20c88af5a4c6ad62894e7f6da28@haiku-os.org> #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript ---------------------------+------------------------------------------------ Reporter: stippi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by jackburton): What about a problem in bash instead ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 14:24:40 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 12:24:40 -0000 Subject: [Haiku-bugs] [Haiku] #805: Fast read/write locker In-Reply-To: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> References: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> Message-ID: <049.f1f07a198a7a4350b7ff59800524c332@haiku-os.org> #805: Fast read/write locker ---------------------------------------+------------------------------------ Reporter: axeld | Owner: Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by bonefish): What properties should the upgrade to write lock function have? I suppose you've something different in mind than read unlock + write lock. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 14:41:28 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 12:41:28 -0000 Subject: [Haiku-bugs] [Haiku] #2277: Broadcom 4401 NIC Message-ID: <045.56a3dfd36795ea405ce4c0275e7a7341@haiku-os.org> #2277: Broadcom 4401 NIC --------------------------------+------------------------------------------- Reporter: paulogeyer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- Hi, this week i've successfully installed haiku in my computer, which is an "Acer Aspire 5630", really nice, it runs fast and pretty stable! but i've got a problem with my Broadcom 4401 NIC (i've tried the GPL bcm44xx driver), it seems to be loaded, but i can't configure it via DHCP or manually, i'll put some information about my NIC here: ''paulo at samsa:~$ lspci |grep Eth 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) paulo at samsa:~$ lspci -nm|grep 06:01.0 06:01.0 "0200" "14e4" "170c" -r02 "1025" "0090"'' i know some C programming, but nothing about driver and OS programming, so i couldn't figure out what's going wrong here -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 14:54:14 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 12:54:14 -0000 Subject: [Haiku-bugs] [Haiku] #805: Fast read/write locker In-Reply-To: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> References: <040.73aab237a07b7cc51269d65927b5ad78@haiku-os.org> Message-ID: <049.4a3702ff2799ea3e027af7e962e3b582@haiku-os.org> #805: Fast read/write locker ---------------------------------------+------------------------------------ Reporter: axeld | Owner: Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Network & Internet/Stack | Version: Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by axeld): I have no idea anymore :-) I guess we should put this ticket aside until we have real concurrency speed problems to solve. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 14:58:36 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 12:58:36 -0000 Subject: [Haiku-bugs] [Haiku] #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript In-Reply-To: <041.f9f58f7e0cf34ebcd31e27d5ccf95a8b@haiku-os.org> References: <041.f9f58f7e0cf34ebcd31e27d5ccf95a8b@haiku-os.org> Message-ID: <050.ff87b2869198bd82883afec16d95e769@haiku-os.org> #2276: If HAIKU_ROOT_USER_REAL_NAME contains UTF8 chars, Haiku fails at Bootscript ---------------------------+------------------------------------------------ Reporter: stippi | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Comment (by bonefish): Works fine here (OpenSuse 10.3). On which platform did you build? How does the generated/objects/common/passwd look like? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 15:30:28 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 13:30:28 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.08631c81263784f95112d810a368989f@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by rudolfc): Hi, I tried that here as well some week ago or so: nogo. I think some BIOSes map the gfx card with MTRR-WC (if requested in BIOS- SETUP). maybe preventing this 'fixes'the problem as well.. (I'll try that too if I get around to it) Still, the acc. should work as well if mapping succeeds without WC. It does so on BeOS R5 and Dano. It does not (apparantly) on Haiku. (Did not check yet if non-WC mapping itself fails though). Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 15:35:19 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 13:35:19 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.8070a5c852d71da07e8c48ce5781e54c@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Platform: x86 -----------------------------------+---------------------------------------- Comment (by emitrax): I don't know if this is useful information or not, but the icons are actually there, although they don't get displayed. In fact, if you try to drag them around you'll see them, or if you right click on them the related menu will come up. BTW: Still happens with latest r25698, vmplayer on linux. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 16:00:09 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 14:00:09 -0000 Subject: [Haiku-bugs] [Haiku] #2278: Mime type database for APE (Monkey's Audio) Message-ID: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> #2278: Mime type database for APE (Monkey's Audio) -------------------------+-------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x86 | -------------------------+-------------------------------------------------- I want a file type for Monkey's Audio audio file. Currently, I'm developing Monkey's Audio Suite for Haiku. Haiku: r25653 [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (enhancement No.4) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 16:05:49 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 14:05:49 -0000 Subject: [Haiku-bugs] [Haiku] #2278: Mime type database for APE (Monkey's Audio) In-Reply-To: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> References: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> Message-ID: <050.359772db59e1ce8a21beec031d1ee29b@haiku-os.org> #2278: Mime type database for APE (Monkey's Audio) --------------------------+------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by shinta): Above attached files is to be added src/data/beos_mime/audio. I didn't test it because I don't know how to add it to Jamfile. How can I add? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 16:40:34 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 14:40:34 -0000 Subject: [Haiku-bugs] [Haiku] #2278: Mime type database for APE (Monkey's Audio) In-Reply-To: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> References: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> Message-ID: <050.d61cd896432890f9789e9da0570b5eeb@haiku-os.org> #2278: Mime type database for APE (Monkey's Audio) --------------------------+------------------------------------------------- Reporter: shinta | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 16:51:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 14:51:41 -0000 Subject: [Haiku-bugs] [Haiku] #2279: [Network] kdl during firefox start Message-ID: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> #2279: [Network] kdl during firefox start --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Platform: All | --------------------------------------+------------------------------------- I've got a kdl when I enabled network (checked "Connected" radiobutton) in vmware settings during firefox start. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 16:53:33 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 14:53:33 -0000 Subject: [Haiku-bugs] [Haiku] #2279: [Network] kdl during firefox start In-Reply-To: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> References: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> Message-ID: <049.c4597baf0e520c48c38707d1c8a9b14c@haiku-os.org> #2279: [Network] kdl during firefox start ---------------------------------------+------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by diver): Forgot to add .png to filename. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 19:28:07 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 17:28:07 -0000 Subject: [Haiku-bugs] [Haiku] #2278: Mime type database for APE (Monkey's Audio) In-Reply-To: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> References: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> Message-ID: <050.55dae9ca4dc741805d6ef7bdedd1dd97@haiku-os.org> #2278: Mime type database for APE (Monkey's Audio) --------------------------+------------------------------------------------- Reporter: shinta | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: x86 --------------------------+------------------------------------------------- Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Added in r25706. It is enough to place the file there, no Jamfile needs to be changed, it will be picked up automatically. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 19:36:47 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 17:36:47 -0000 Subject: [Haiku-bugs] [Haiku] #2279: [Network] kdl during firefox start In-Reply-To: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> References: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> Message-ID: <049.5fd33751bb799bc8d7631cec55840e63@haiku-os.org> #2279: [Network] kdl during firefox start ---------------------------------------+------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Changes (by tqh): * cc: tqh (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 19:39:19 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 17:39:19 -0000 Subject: [Haiku-bugs] [Haiku] #2279: [Network] kdl during firefox start In-Reply-To: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> References: <040.031725d78effca7de80dc1b25c7cf48e@haiku-os.org> Message-ID: <049.b208b9af5726618bc3b84e2ea116d09b@haiku-os.org> #2279: [Network] kdl during firefox start ---------------------------------------+------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: | Platform: All ---------------------------------------+------------------------------------ Comment (by tqh): From the backtrace it looks to probably be a problem in the intel network driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 20:25:43 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 18:25:43 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.5ba3f8c206e6788047b447e9c351f078@haiku-os.org> #2212: r25309 removed desktop icons from first boot --------------------------------+------------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Changes (by axeld): * component: Applications/Tracker => Servers/registrar Comment: I've investigated this a bit, and the Desktop window's message port is filled up with B_META_MIME_CHANGED messages - caused by the script that updates all MIME information upon first start. Not sure why it didn't manage to keep up. I think the solution to this problem in general should be to change the registrar to reporting in less detail when adding whole MIME types. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 22:20:40 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 20:20:40 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.f063fc7eceb3504c90b2311ad3ad2f50@haiku-os.org> #2212: r25309 removed desktop icons from first boot --------------------------------+------------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by bonefish): Replying to [comment:10 axeld]: > I've investigated this a bit, and the Desktop window's message port is filled up with B_META_MIME_CHANGED messages - caused by the script that updates all MIME information upon first start. > > Not sure why it didn't manage to keep up. I think the solution to this problem in general should be to change the registrar to reporting in less detail when adding whole MIME types. Optimizing the MIME update message mechanism is certainly a good idea. I disagree, however, that this is the solution to this bug. That a port runs full should be rather harmless. That it isn't emptied is a real problem, though, and should be fixed. Until that happened, I wouldn't do anything that makes the bug less reproducible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 22:51:41 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 20:51:41 -0000 Subject: [Haiku-bugs] [Haiku] #2280: Can't take screenshot in 16 bit colour space Message-ID: <041.6e339803e4111faea0884aa8d950bf65@haiku-os.org> #2280: Can't take screenshot in 16 bit colour space --------------------------------+------------------------------------------- Reporter: idefix | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Platform: All | --------------------------------+------------------------------------------- I wanted to make a screenshot for another bug, but was unable to do so: SaveToPNG: /boot/home/screen3.png (1024x768) Unsupported color space I found this comment in [http://dev.haiku- os.org/browser/haiku/trunk/src/servers/app/PNGDump.cpp#L73 PNGDump.cpp]: // TODO: support other color spaces if needed The S3 driver only supports 8 bit and 16 bit colour spaces, so I need this support. Could somebody implement it? Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 23:08:24 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 21:08:24 -0000 Subject: [Haiku-bugs] [Haiku] #1299: messed up screen with intel_extreme driver In-Reply-To: <042.059c56243d87428b499389bd6a735725@haiku-os.org> References: <042.059c56243d87428b499389bd6a735725@haiku-os.org> Message-ID: <051.0f55290cd7992f3a1f590e69da25d60e@haiku-os.org> #1299: messed up screen with intel_extreme driver ---------------------------------------------+------------------------------ Reporter: modeenf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: | Platform: x86 ---------------------------------------------+------------------------------ Comment (by atomozero): I still have the same problem :( r25709 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 23:52:04 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 21:52:04 -0000 Subject: [Haiku-bugs] [Haiku] #2281: pdfwriter uses parent class name as regular function name Message-ID: <040.e26b366e301a6c7473e28071dee20e79@haiku-os.org> #2281: pdfwriter uses parent class name as regular function name ------------------------------+--------------------------------------------- Reporter: monni | Owner: laplace Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Printers | Version: R1 development Platform: All | ------------------------------+--------------------------------------------- /src/add-ons/print/drivers/pdf/source/XReferences.h Has member function bool Link(XRefDef* def, MatchResult* result); in class LocalLink which shadows destructor of parent class "Link" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 29 23:52:21 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 21:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.6a2f8b1f58bea40726a56ca2b0b6f8e0@haiku-os.org> #2212: r25309 removed desktop icons from first boot --------------------------------+------------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: x86 --------------------------------+------------------------------------------- Comment (by axeld): I just tried it on my quad core, and came to the same conclusion :-) It still happens there, even though there should be plenty of CPU power free to empty that message port. I'll check tomorrow what this window is up to. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 00:19:18 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 22:19:18 -0000 Subject: [Haiku-bugs] [Haiku] #2282: Tracker forgets settings Message-ID: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> #2282: Tracker forgets settings -----------------------+---------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: All | -----------------------+---------------------------------------------------- Using build 25714, tracker doesn't remember its settings. i.e 'show folder location in title bar', 'single window navigation' etc. If you select them, tracker behaves, upon restarting, the settings are forgotten. Additionally, I've noticed all paths are forgotten. i.e to the development directory. Adding them in .profile remedies the situation, but I've never had to do this before. Finally, deskbar doesn't launch properly. See the attached screenshot. Everything mentioned 100% reproducible. Tested in Vmware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 01:46:40 2008 From: trac at haiku-os.org (Haiku) Date: Thu, 29 May 2008 23:46:40 -0000 Subject: [Haiku-bugs] [Haiku] #2018: libpng needs update >= 1.2.28 to fix security issue In-Reply-To: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> References: <042.f66e61cb6a9a76ba49a91935d929e81e@haiku-os.org> Message-ID: <051.3b189ae470d8d4931b7d7ea2ae4af4fa@haiku-os.org> #2018: libpng needs update >= 1.2.28 to fix security issue ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by scottmc): I downloaded the 1.2.29 source code files and dropped the matching ones over the 1.2.26 in my haiku source png folders, total of 19 'c' files and 2 'h' files, skipping the pngtest.c file. Then ran svn diff. output diff file attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 04:34:15 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 02:34:15 -0000 Subject: [Haiku-bugs] [Haiku] #2267: Sound plays with noise (using OSS) In-Reply-To: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> References: <041.d5b5a7c80f65311174adae8b12bad08a@haiku-os.org> Message-ID: <050.ab67a63083280c41a38c0630ed2777d4@haiku-os.org> #2267: Sound plays with noise (using OSS) -----------------------------+---------------------------------------------- Reporter: apple7 | Owner: mmu_man Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: | Platform: x86 -----------------------------+---------------------------------------------- Comment (by apple7): Replying to [comment:2 bipolar]: > I have the same issues in my system, two sound cards: > SiS 7018 and Aureal Vortex 2 (8820). > > Sound comming out from the media_server is heavily distorted, "stretched in time" so it seems and with frequent pauses/hiccups. > > But... After quitting the media_server, running oss_test from the terminal goes all well. Sound is great for both devices. > > I'm willing to test this further, just shout. Yes, thanks, now sound is god! But we can fix problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 09:01:04 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 07:01:04 -0000 Subject: [Haiku-bugs] [Haiku] #2283: less needs updating Message-ID: <042.142de9f511d0449e1ada1b5cbfec5baa@haiku-os.org> #2283: less needs updating ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Platform: All | ---------------------------------------------+------------------------------ Current version of less is 418, Haiku currently a 'lesser' version...382. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 10:42:29 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 08:42:29 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) Message-ID: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> #2284: Page Fault on boot (25717) ---------------------------+------------------------------------------------ Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Platform: x64 | ---------------------------+------------------------------------------------ I get a page fault at 0x0 when booting Haiku (compiled with GCC2 or GCC4), before the "rocketship" icon lights up. The stack crawl does not provide any useful information; it starts in int_bottom, and goes directly to the page fault interrupt handler. Hardware: AMD64 X2, SATA Drive in SATA mode, Synaptics touchpad, Firewire (though the module is not in the image), nVIDIA 6150 integrated graphics and nforce 430 chipset. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 10:42:30 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 08:42:30 -0000 Subject: [Haiku-bugs] [Haiku] #2285: Bootloader fails when chainloaded from grub 1/2 in a specific way. Message-ID: <048.e5f6ab65586a95dcc932c4e8b61a7277@haiku-os.org> #2285: Bootloader fails when chainloaded from grub 1/2 in a specific way. --------------------------------+------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Platform: x64 | --------------------------------+------------------------------------------- When I load my haiku partition (/dev/sda2) from GRUB Legacy as such: {{{ chainloader (hd0,1)+1 }}} I get a read error (bootloader debug turned on) From GRUB 2: {{{ set root=(hd0,2) chainloader +1 }}} I also get a read error BUT, with GRUB 1 and {{{ root (hd0,1) chainloader +1 }}} The bootloader works just fine. This is probably a bug in GRUB, but I think it might be related to int 13 and how the bootloader uses it; when GRUB reads the disk BEFORE chainloading, there is no issue, but when only the first sector is loaded, the boot fails. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:12:26 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:12:26 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.420758f6f4b899dce062ac2a5c03b8a8@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed * component: Servers/registrar => Applications/Tracker Comment: Fixed in r25719. I'll open a new ticket about the registrar improvements. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:14:09 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:14:09 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation Message-ID: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> #2286: Too many MIME updates on MIME type creation -------------------------------+-------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- The registrar sends out tons of B_META_MIME_CHANGED notices when new MIME types are installed - this should be calmed down to an acceptable number, possibly just one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:15:01 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:15:01 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.6f049c9c0c9582ce49f5bb570edc95f0@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Comment (by axeld): Ticket #2286 tracks the registrar's part in this problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:28:40 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:28:40 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) In-Reply-To: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> References: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> Message-ID: <057.5689f1c1d6074c6ac66a76b75bada84b@haiku-os.org> #2284: Page Fault on boot (25717) ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => blocker * milestone: R1 => R1/alpha1 Comment: Can you turn on on-screen-debug output in the boot loader's safe mode menu, and see where it stops? Also, you may want to try with a revision somewhere before r25660 and see if that helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:30:10 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:30:10 -0000 Subject: [Haiku-bugs] [Haiku] #2282: Tracker forgets settings In-Reply-To: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> References: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> Message-ID: <050.719bc219b742140fb7041a49f1f4e90e@haiku-os.org> #2282: Tracker forgets settings ----------------------------+----------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by axeld): * priority: normal => critical * component: - General => System/Kernel * milestone: R1 => R1/alpha1 Comment: I can reproduce this bug. This must be a recently introduced problem; the TrackerSettings file is just filled with zeros instead of the data it should contain. I guess Deskbar has the same issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 11:32:52 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 09:32:52 -0000 Subject: [Haiku-bugs] [Haiku] #2270: Build system deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk In-Reply-To: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> References: <040.dd3df7874e2de09994048a060dbd39d5@haiku-os.org> Message-ID: <049.a6e84a53f737656ef25b16d133acdce8@haiku-os.org> #2270: Build system deletes /dev/sda1 node in Ubuntu when installing Haiku on real disk ---------------------------+------------------------------------------------ Reporter: monni | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Platform: All ---------------------------+------------------------------------------------ Changes (by marcusoverhagen): * cc: marcusoverhagen (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 12:37:23 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 10:37:23 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation In-Reply-To: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> References: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> Message-ID: <049.3d89595c87f7e0bed12c6effb42b70f8@haiku-os.org> #2286: Too many MIME updates on MIME type creation --------------------------------+------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by diver): Could this be related to bug #257? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 12:41:14 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 10:41:14 -0000 Subject: [Haiku-bugs] [Haiku] #257: [Expander] first launch In-Reply-To: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> References: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> Message-ID: <049.cfba25dc0045a122f0807863afe52f7b@haiku-os.org> #257: [Expander] first launch ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by axeld): This might have been fixed with r25719, please check. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 12:42:17 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 10:42:17 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation In-Reply-To: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> References: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> Message-ID: <049.85fb0501a2f31aa8527ad9793bd69e53@haiku-os.org> #2286: Too many MIME updates on MIME type creation --------------------------------+------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Comment (by axeld): Yes, probably - but since the delay is now much shorter, the problem should be gone if that was it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 13:11:08 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 11:11:08 -0000 Subject: [Haiku-bugs] [Haiku] #257: [Expander] first launch In-Reply-To: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> References: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> Message-ID: <049.1996cbfbc2a824ff3ef481d83b24273b@haiku-os.org> #257: [Expander] first launch ------------------------+--------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: Resolution: | Platform: All ------------------------+--------------------------------------------------- Comment (by diver): I think this could even be fixed in r25309, where Ingo added mimeset -apps -f /boot/beos/apps mimeset -apps -f /boot/beos/preferences So now both Expander and MediaPlayer should write their supported MIME types at first boot, regardless of whether you'll launch them of not, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 13:29:06 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 11:29:06 -0000 Subject: [Haiku-bugs] [Haiku] #2278: Mime type database for APE (Monkey's Audio) In-Reply-To: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> References: <041.58a55ee759ba9ef65730ddbeedab9b77@haiku-os.org> Message-ID: <050.a3821875470ed7a49fc0556e2765e5d7@haiku-os.org> #2278: Mime type database for APE (Monkey's Audio) --------------------------+------------------------------------------------- Reporter: shinta | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Platform: x86 --------------------------+------------------------------------------------- Comment (by shinta): Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 13:49:00 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 11:49:00 -0000 Subject: [Haiku-bugs] [Haiku] #257: [Expander] first launch In-Reply-To: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> References: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> Message-ID: <049.e088061e0ec2b9554d73a2c3efb58207@haiku-os.org> #257: [Expander] first launch --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Servers/registrar | Version: Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by diver): * component: - General => Servers/registrar Comment: Yes, it's seems "fixed". But I think r25309 could've been hide this bug and could potentially lead to boot time increase due to a slow MIME type write as stated above. What do you guys think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:06:53 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:06:53 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.d799ee0b82c554e594fff09978887113@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Comment (by stippi): What I am wondering though... shouldn't the Tracker window recover after a while? Was nothing drawn because of the app_server bug (when the return code of SendMessage() was still not checked)? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:09:24 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:09:24 -0000 Subject: [Haiku-bugs] [Haiku] #2287: Screesaver crash on exit from modules tab Message-ID: <040.81f57169e9f8f72db15b281319d74dee@haiku-os.org> #2287: Screesaver crash on exit from modules tab -------------------------------------+-------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Platform: All | -------------------------------------+-------------------------------------- Screensaver app crashes when qiutting from the modules tab. When either IFS or Spider is selected. 1) Open Screensaver preflet 2) Click modules tab 3) Select either Spider or IFS 4) Quit the preflet while still in modules tab The result is Screensaver crashes. Reproduceable every time. The crash wont happen if after step 3, the Fade tab is clicked then the preflet is quit from there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:11:54 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:11:54 -0000 Subject: [Haiku-bugs] [Haiku] #257: [Expander] first launch In-Reply-To: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> References: <040.e4bcbd65624657fca6e82036d290d4ad@haiku-os.org> Message-ID: <049.1539244ec749b73c33afcff4fc99f571@haiku-os.org> #257: [Expander] first launch --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: That only happens once at the very first boot. I think the general idea behind that is ok. The other option would be to make the build system do this, but think the current solution is more fool proof. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:14:57 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:14:57 -0000 Subject: [Haiku-bugs] [Haiku] #2287: Screesaver crash on exit from modules tab In-Reply-To: <040.81f57169e9f8f72db15b281319d74dee@haiku-os.org> References: <040.81f57169e9f8f72db15b281319d74dee@haiku-os.org> Message-ID: <049.ae77e80286fe067e74a5e3ea59a7f8bc@haiku-os.org> #2287: Screesaver crash on exit from modules tab --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by cebif): I was testing in r25575. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:18:55 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:18:55 -0000 Subject: [Haiku-bugs] [Haiku] #2212: r25309 removed desktop icons from first boot In-Reply-To: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> References: <040.7ad3b0063ffa244ba16a7a8465b70d6d@haiku-os.org> Message-ID: <049.f1478ab54e26505f9994f1e6b6d77125@haiku-os.org> #2212: r25309 removed desktop icons from first boot -----------------------------------+---------------------------------------- Reporter: luroh | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: fixed | Platform: x86 -----------------------------------+---------------------------------------- Comment (by axeld): After the app_server fix, the Tracker window would recover after a while, but I'm not sure how exactly - I mean I don't know who triggered the next update message that finally arrived. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:20:19 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:20:19 -0000 Subject: [Haiku-bugs] [Haiku] #1299: messed up screen with intel_extreme driver In-Reply-To: <042.059c56243d87428b499389bd6a735725@haiku-os.org> References: <042.059c56243d87428b499389bd6a735725@haiku-os.org> Message-ID: <051.95c7b686f1367a4958a47b9e09e5fbdc@haiku-os.org> #1299: messed up screen with intel_extreme driver ---------------------------------------------+------------------------------ Reporter: modeenf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Resolution: | Platform: x86 ---------------------------------------------+------------------------------ Comment (by axeld): Thanks to luroh, I now have an i945 based laptop so that I am able to look into this over the next weeks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:47:21 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:47:21 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) In-Reply-To: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> References: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> Message-ID: <057.8f6f5d9986e35312c4e9d8413d09e117@haiku-os.org> #2284: Page Fault on boot (25717) ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Comment (by bga): It may or may not be the same bug, but I an getting a crash during boot in the ahci driver (actually, the ahci driver calls up on the pci bus and pci crashes). I am not at home now so can't provide a backtrace, but this seems to be obviously related to the new driver model. I will capture the kdl screen later today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 14:49:36 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 12:49:36 -0000 Subject: [Haiku-bugs] [Haiku] #2282: Tracker forgets settings In-Reply-To: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> References: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> Message-ID: <050.a3609abf60eca8ed16e5ecf7dc57aa20@haiku-os.org> #2282: Tracker forgets settings ----------------------------+----------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by kvdman): It happened after rev25562, I don't know where exactly. I tested a new revision six days after and incurred the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 17:53:19 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 15:53:19 -0000 Subject: [Haiku-bugs] [Haiku] #2288: KDL when I unplug USB Wacom pentablet Message-ID: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> #2288: KDL when I unplug USB Wacom pentablet -------------------------+-------------------------------------------------- Reporter: idefix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Platform: x86 | -------------------------+-------------------------------------------------- With r25684 the computer goes into KDL when I unplug my Wacom Graphire 2 USB pentablet. Previous revisions didn't show this behaviour (previous one I tested was 1 - 2 weeks old I think). How to reproduce: - Start Haiku with tablet connected. - Pull USB plug out of USB port. - Haiku enters KDL. I tested this two times, see attached syslog-outputs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 18:00:31 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 16:00:31 -0000 Subject: [Haiku-bugs] [Haiku] #2288: KDL when I unplug USB Wacom pentablet In-Reply-To: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> References: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> Message-ID: <050.d745437be009fd256b2c24a7f5330907@haiku-os.org> #2288: KDL when I unplug USB Wacom pentablet --------------------------+------------------------------------------------- Reporter: idefix | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Comment (by idefix): Looks like second text file didn't upload correctly: the beginning is truncated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 18:08:31 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 16:08:31 -0000 Subject: [Haiku-bugs] [Haiku] #2288: KDL on rescanning of legacy drivers In-Reply-To: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> References: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> Message-ID: <050.d6e2c474823244aa8a71323ccdb917ef@haiku-os.org> #2288: KDL on rescanning of legacy drivers --------------------------+------------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Platform: x86 --------------------------+------------------------------------------------- Changes (by mmlr): * owner: mmlr => axeld * summary: KDL when I unplug USB Wacom pentablet => KDL on rescanning of legacy drivers Comment: Assigning to Axel as this is caused by the new device manager. Unplugging any USB device will show this behaviour. Relabeling bug accordingly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 18:49:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 16:49:50 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) In-Reply-To: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> References: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> Message-ID: <057.1bf5331fb2cbf9483a6bc3e111d3c24d@haiku-os.org> #2284: Page Fault on boot (25717) ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Comment (by dustin howett): {{{ Legacy SATA: controller found! vendor 0x10de, device 0x0266 Legacy SATA: controller_probe PCI-IDE: Controller in native mode: cmd 0x30c0, ctrl 0x30b6, irq 5 PCI-IDE: init channel... PCI-IDE: channel index 0 PCI-IDE: bus master base 0x3090 PCI-IDE: init channel done vm_soft_fault: kernel thread accessing invalud user memory! vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x0, write 0, user 0, thread 0xb }}} I find it odd that legacy_sata is being used... ahci used to work properly for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 18:54:43 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 16:54:43 -0000 Subject: [Haiku-bugs] [Haiku] #2144: Test case: jam -q -a Terminal In-Reply-To: <043.e29b66e2e2d24798c025010e54a806fc@haiku-os.org> References: <043.e29b66e2e2d24798c025010e54a806fc@haiku-os.org> Message-ID: <052.77984ccc409f712c646690d5f073881b@haiku-os.org> #2144: Test case: jam -q -a Terminal --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): File jam-q-a-Terminal-times.2.txt updated with r25715 and r25719. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 20:02:47 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 18:02:47 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) In-Reply-To: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> References: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> Message-ID: <057.d9b18cae8a4649da883906bf20de4042@haiku-os.org> #2284: Page Fault on boot (25717) ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Comment (by dustin howett): 22659 works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 20:04:31 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 18:04:31 -0000 Subject: [Haiku-bugs] [Haiku] #2284: Page Fault on boot (25717) In-Reply-To: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> References: <048.bfb72f9386e7aa9daa3a55dc9e971a91@haiku-os.org> Message-ID: <057.084e0e918ccd132a9137b61ca23bd3cf@haiku-os.org> #2284: Page Fault on boot (25717) ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: - General | Version: R1 development Resolution: | Platform: x64 ----------------------------+----------------------------------------------- Comment (by dustin howett): That is.. r25659 works. Oops. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 20:43:58 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 18:43:58 -0000 Subject: [Haiku-bugs] [Haiku] #2064: libMicro port In-Reply-To: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> References: <043.346c94e350c82ddd688950dff1c59695@haiku-os.org> Message-ID: <052.6c1378fd972d4a3bc6ccb4569698724c@haiku-os.org> #2064: libMicro port --------------------------+------------------------------------------------- Reporter: kaoutsis | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Platform: All --------------------------+------------------------------------------------- Comment (by kaoutsis): src_tests_system_benchmarks_libMicro.diff: * Allow the msync libMicro benchmark to compile for real * Added a plain test for msync to the bench script, since the original bench script didn't have one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 22:23:50 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 20:23:50 -0000 Subject: [Haiku-bugs] [Haiku] #1853: RTL8168 recognized but not working In-Reply-To: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> References: <043.6eabb69a28bfed60f7d87956365282b5@haiku-os.org> Message-ID: <052.376fcb250d1b1aa21f9c39bd76d5a3ef@haiku-os.org> #1853: RTL8168 recognized but not working ---------------------------------+------------------------------------------ Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: | Platform: x86 ---------------------------------+------------------------------------------ Comment (by phoudoin): Same here on my temporary motherboard replacement, which comes with builtin rtl8168/8111 gigabit ethernet controller. It's recognized as an ethernet card by the driver, but the link checker always report "no link". Hope my old no so "Rock Solid (tm)" Asus P5W DH motherboard will be fixed soon. Meanwhile, let's look in the mess if I can found a supported PCI NIC :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 22:30:49 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 20:30:49 -0000 Subject: [Haiku-bugs] [Haiku] #2288: KDL on rescanning of legacy drivers In-Reply-To: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> References: <041.2e83c6c1aaa2292e404b22b9a3cf4781@haiku-os.org> Message-ID: <050.0127213e0e85b4a024a16ccb0978fe24@haiku-os.org> #2288: KDL on rescanning of legacy drivers --------------------------+------------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Platform: x86 --------------------------+------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Should be fixed in r25729 although this seems to need some more work anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 30 22:33:31 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 20:33:31 -0000 Subject: [Haiku-bugs] [Haiku] #2287: Screesaver crash on exit from modules tab In-Reply-To: <040.81f57169e9f8f72db15b281319d74dee@haiku-os.org> References: <040.81f57169e9f8f72db15b281319d74dee@haiku-os.org> Message-ID: <049.86523d045add46c2fb089e8834513d0c@haiku-os.org> #2287: Screesaver crash on exit from modules tab --------------------------------------+------------------------------------- Reporter: cebif | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/ScreenSaver | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by meanwhile): Maybe related to (or even the same as) #2057 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 00:17:13 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 22:17:13 -0000 Subject: [Haiku-bugs] [Haiku] #2282: Tracker forgets settings In-Reply-To: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> References: <041.c47708a2bf1826a5bc5d127e995629c2@haiku-os.org> Message-ID: <050.90dd279fe208bf75d67d0f075e1be9c1@haiku-os.org> #2282: Tracker forgets settings ----------------------------+----------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Changes (by luroh): * cc: luroh (added) Comment: I think I have traced the deskbar problem to r25620 but it could do with some more testing, see ticket #2260 (contains links to vmware image files). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 00:46:57 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 22:46:57 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation In-Reply-To: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> References: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> Message-ID: <049.68c22b507b6c68164fbb6ce2489de2ed@haiku-os.org> #2286: Too many MIME updates on MIME type creation --------------------------------+------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 01:01:17 2008 From: trac at haiku-os.org (Haiku) Date: Fri, 30 May 2008 23:01:17 -0000 Subject: [Haiku-bugs] [Haiku] #61: Build POSIX test suite for haiku In-Reply-To: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> References: <049.5a167f1f0d0a17c90f7ad1531b88bc4d@haiku-os.org> Message-ID: <058.ae31317696fecbcc0533b4f99c310d82@haiku-os.org> #61: Build POSIX test suite for haiku -----------------------------+---------------------------------------------- Reporter: andrewbachmann | Owner: Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: Resolution: | Platform: All -----------------------------+---------------------------------------------- Comment (by kaoutsis): posix-testsuite_killpg_sigpause.diff: * added the killpg() and sigpause() tests to the package -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 02:21:32 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 00:21:32 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation In-Reply-To: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> References: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> Message-ID: <049.d2b94c0da091fab57234f0feea9ae448@haiku-os.org> #2286: Too many MIME updates on MIME type creation --------------------------------+------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Actually there weren't that many notifications sent. Usually just one "created" notification and a few "updates" (one for each set property). As of r25730 we only send the "created" notification in such cases. For the first boot that reduces the number of sent messages from some 320 to 109. There still are a handful of unavoidable duplicates (for the servers that are started before the mimeset script runs), but other than that there really are that many MIME types involved. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 06:46:59 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 04:46:59 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. In-Reply-To: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> References: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> Message-ID: <051.27f19fa760604b2bee88809b548de889@haiku-os.org> #2229: Background image does not center. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: | Platform: All --------------------------------------+------------------------------------- Comment (by bbjimmy): PLEASE CLOSE THIS TICKET The issue seems to have been a corrupted setting for Icon size. I changed the icon size and all the above issues were resolved. Changing back to the default size did not bring the problems back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 07:26:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 05:26:31 -0000 Subject: [Haiku-bugs] [Haiku] #2289: scsi_dsk, scsi_cd broken, symbol api_version missing Message-ID: <040.1f975e51ef8b778c0cd49c98f28d587b@haiku-os.org> #2289: scsi_dsk, scsi_cd broken, symbol api_version missing --------------------------+------------------------------------------------- Reporter: monni | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Platform: All | --------------------------+------------------------------------------------- Some people actually use SCSI devices... erf... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 08:23:08 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 06:23:08 -0000 Subject: [Haiku-bugs] [Haiku] #2290: bluetooth crashes when removing device Message-ID: <040.007f6bc38c42a1ccbbd6956a21e2033d@haiku-os.org> #2290: bluetooth crashes when removing device -------------------------------+-------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- vm_page_fault iframe at 0x80532e70 (end = 0x80532ec8) 80532e70 (+ 104) 0x93a85ec3 nb_destroy + 0x0017 80532ed8 (+ 48) 0x93a84804 device_removed + 0x00e4 eax 0x0 ebx 0x93a88504 ecx 0x0 edx 0x909ece40 esi 0x0 edi 0x909ecee0 ebp 0x80532ed0 esp 0x80532ea4 eip 0x93a85ec3 eflags 0x10292 Sorry about lack of formatting, had to hand-write -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 08:49:13 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 06:49:13 -0000 Subject: [Haiku-bugs] [Haiku] #2291: vm_soft_fault when discovering bluetooth devices Message-ID: <040.c50b25037ba7cd5854594f884896fac6@haiku-os.org> #2291: vm_soft_fault when discovering bluetooth devices -------------------------------+-------------------------------------------- Reporter: monni | Owner: oruizdorantes Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Bluetooth | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- How to reproduce: Run bt_discovery before starting bluetooth_server Experienced behavior: No KDL Expected behavior: whine like a baby KERN: BT device_control: ioctl() opcode 12999 size 7. KERN: BT command_complete: 11 09:10:00: KERN: BT assembly_rx: count 12 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT device_control: ioctl() opcode 12999 size 7. KERN: BT command_complete: 11 14:0c:00: KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: Last message repeated 14 times. KERN: BT assembly_rx: count 14 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT device_control: ioctl() opcode 12999 size 12. KERN: BT command_complete: 16 01:04:05: KERN: BT assembly_rx: count 6 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 3 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: vm_soft_fault: va 0x0 not covered by area in address space KERN: vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x0, ip 0x800a28a8, write 1, user 0, thread 0x13d KERN: BT device_control: ioctl() opcode 12999 size 17. KERN: BT command_complete: 21 19:04:0a: KERN: BT assembly_rx: count 6 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland KERN: BT assembly_rx: count 16 0x00000000 0x8058f3e0 KERN: Last message repeated 15 times. KERN: BT assembly_rx: count 1 0x00000000 0x8058f3e0 KERN: BT assembly_rx: Frame goes up! KERN: BT post_packet_up: HCI not present, Posting to userland -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 11:04:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 09:04:29 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.934edcd83fdfd9595ca76ea56b30dcfa@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by rudolfc): Hi again, I've looked at the repository, and the MTRR overlap check was disabled with: http://dev.haiku-os.org/changeset/24946 On april 12th. My version was from april 8th so I suffered from this problem. Tigerdog, would you say that a current version of Haiku works without problems, even if you don't select 'don't call the BIOS' ? Thanks! BTW: I've been playing around a bit more with the kernel, and I get the feeling that the function get_mtrr doesn't work reliable.. (?). Over here MTRR fails sometimes (if overlap check enabled), even though the gfx card isn't the primary card in the system and therefore should not be mapped before. It looks like fail or not: the driver doesn't work. Until I just disable that overlap check function that is. I don't (fully) grasp the situation here (yet). What I do know (I think) is that the driver is OK since on R5 it's always working, even if I modify the kerneldriver to don't use MTRR. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 12:22:36 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 10:22:36 -0000 Subject: [Haiku-bugs] [Haiku] #2292: Revision 25730 break compilation under BeOS R5/BONE Message-ID: <038.60151ca456e59ccb65ce492b234ea84c@haiku-os.org> #2292: Revision 25730 break compilation under BeOS R5/BONE -------------------------------+-------------------------------------------- Reporter: oco | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- Here is the jam output : $ jam ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...found 6600 target(s)... ...updating 7 target(s)... C++ ../../../generated/objects/haiku/x86/release/servers/registrar/MIMEManager.o MIMEManager.cpp: In method `void MIMEManager::MessageReceived(BMessage *)': MIMEManager.cpp:232: no matching function for call to `BPrivate::Storage::Mime::CreateAppMetaMimeThread::CreateAppMetaMimeThread (const char *, int, BMessenger, entry_ref *, bool &, int32 &, BMessage *)' mime/CreateAppMetaMimeThread.h:23: candidates are: BPrivate::Storage::Mime::CreateAppMetaMimeThread::CreateAppMetaMimeThread(const char *, long int, BPrivate::Storage::Mime::Database *, BMessenger, const entry_ref *, bool, long int, BMessage *) mime/CreateAppMetaMimeThread.h:25: BPrivate::Storage::Mime::CreateAppMetaMimeThread::CreateAppMetaMimeThread(const BPrivate::Storage::Mime::CreateAppMetaMimeThread &) MIMEManager.cpp:239: no matching function for call to `BPrivate::Storage::Mime::UpdateMimeInfoThread::UpdateMimeInfoThread (const char *, int, BMessenger, entry_ref *, bool &, int32 &, BMessage *)' mime/UpdateMimeInfoThread.h:23: candidates are: BPrivate::Storage::Mime::UpdateMimeInfoThread::UpdateMimeInfoThread(const char *, long int, BPrivate::Storage::Mime::Database *, BMessenger, const entry_ref *, bool, long int, BMessage *) mime/UpdateMimeInfoThread.h:25: BPrivate::Storage::Mime::UpdateMimeInfoThread::UpdateMimeInfoThread(const BPrivate::Storage::Mime::UpdateMimeInfoThread &) /boot/apps/haiku/cross-tools/bin/i586-pc-haiku-gcc -c "MIMEManager.cpp" -O2 -Wall -Wno-trigraphs -Wno-ctor-dtor-privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare -nostdinc -Wno-multichar -D_ZETA_USING_DEPRECATED_API_=1 -D_ZETA_TS_FIND_DIR_=1 -D__HAIKU__ -DHAIKU_DISTRO_COMPATIBILITY_DEFAULT -D__INTEL__ -DARCH_x86 -D_BEOS_R5_COMPATIBLE_ -DHAIKU_TARGET_PLATFORM_HAIKU -I../../../build/user_config_headers -I../../../build/config_headers -I. -I../../../generated/objects/common/servers/registrar -I../../../generated/objects/bone/x86/common/servers/registrar -I../../../generated/objects/haiku/x86/common/servers/registrar -Imime -I- -I../../../headers/private/app -I../../../headers/private/kernel -I../../../headers/private/libroot -I../../../headers/private/shared -I../../../headers/private/storage -I../../../headers/private/tracker -I../../../headers/private/. -I../../../headers/private/system -I../../../headers/private/system/arch/x86 -I../../../headers/build/gcc-2.95.3 -I../../../headers -I../../../headers/posix -I../../../headers/gnu -I../../../headers/glibc -I../../../headers/os -I../../../headers/os/add-ons -I../../../headers/os /add-ons/file_system -I../../../headers/os/add-ons/graphics -I../../../headers/os/add-ons/input_server -I../../../headers/os/add- ons/registrar -I../../../headers/os/add-ons/screen_saver -I../../../headers/os/add-ons/tracker -I../../../headers/os/app -I../../../headers/os/device -I../../../headers/os/drivers -I../../../headers/os/game -I../../../headers/os/interface -I../../../headers/os/kernel -I../../../headers/os/media -I../../../headers/os/mail -I../../../headers/os/midi -I../../../headers/os/midi2 -I../../../headers/os/net -I../../../headers/os/opengl -I../../../headers/os/storage -I../../../headers/os/support -I../../../headers/os/translation -I../../../headers/private/. -I../../../headers/cpp -o "../../../generated/objects/haiku/x86/release/servers/registrar/MIMEManager.o" ; ...failed C++ ../../../generated/objects/haiku/x86/release/servers/registrar/MIMEManager.o ... ...removing ../../../generated/objects/haiku/x86/release/servers/registrar/MIMEManager.o C++ ../../../generated/objects/haiku/x86/release/servers/registrar/Registrar.o C++ ../../../generated/objects/haiku/x86/release/servers/registrar/CreateAppMetaMimeThread.o C++ ../../../generated/objects/haiku/x86/release/servers/registrar/Database.o C++ ../../../generated/objects/haiku/x86/release/servers/registrar/MimeUpdateThread.o C++ ../../../generated/objects/haiku/x86/release/servers/registrar/UpdateMimeInfoThread.o ...skipped registrar for lack of MIMEManager.o... ...failed updating 1 target(s)... ...skipped 1 target(s)... ...updated 5 target(s)... Workaround : svn update -r25729 in src/servers/registrar -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 13:54:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 11:54:31 -0000 Subject: [Haiku-bugs] [Haiku] #2286: Too many MIME updates on MIME type creation In-Reply-To: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> References: <040.1ce5e332cd5fbd156f5209f32e8dfcbe@haiku-os.org> Message-ID: <049.be1c420276b19d492290f084a9b851ae@haiku-os.org> #2286: Too many MIME updates on MIME type creation --------------------------------+------------------------------------------- Reporter: axeld | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Comment (by axeld): I think reducing the number of messages by two thirds is rather nice. But I think we may want to rethink the whole port limitations at one point anyway. For one, they really should use pageable memory to reduce the memory pressure they may currently impose when ports aren't emptied. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 14:00:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 12:00:58 -0000 Subject: [Haiku-bugs] [Haiku] #2293: KDL during boot when scanning for devices. Message-ID: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> #2293: KDL during boot when scanning for devices. ---------------------------+------------------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Platform: All | ---------------------------+------------------------------------------------ Since the chnage in the driver architeture, my machine does not boot Haiku anymore. It crashes when the ahci bus calls ip on the pci bus. KDL capture attched. Let me know if you need more information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 16:21:34 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 14:21:34 -0000 Subject: [Haiku-bugs] [Haiku] #2294: functions declared in headers/posix/iconv.h are not published by libroot.so Message-ID: <038.a61e4e8bf85dc8ff1f5ea300cefec5d5@haiku-os.org> #2294: functions declared in headers/posix/iconv.h are not published by libroot.so -------------------------------+-------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Platform: All | -------------------------------+-------------------------------------------- I discover this problem using widestring in FreePascal. This feature rely on those functions. There is a problem while loading programs that use those functions. I will attach the quick patch i have done to test publishing those functions. Programs are launched correctly, but the implementation remains broken (according to freepascal test suite). So, don't apply it ! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 17:20:05 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 15:20:05 -0000 Subject: [Haiku-bugs] [Haiku] #2292: Revision 25730 break compilation under BeOS R5/BONE In-Reply-To: <038.60151ca456e59ccb65ce492b234ea84c@haiku-os.org> References: <038.60151ca456e59ccb65ce492b234ea84c@haiku-os.org> Message-ID: <047.ee1654f5006bffbd9fe328141bb20b6a@haiku-os.org> #2292: Revision 25730 break compilation under BeOS R5/BONE --------------------------------+------------------------------------------- Reporter: oco | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Platform: All --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r25736. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 18:34:58 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 16:34:58 -0000 Subject: [Haiku-bugs] [Haiku] #2289: scsi_dsk, scsi_cd broken, symbol api_version missing In-Reply-To: <040.1f975e51ef8b778c0cd49c98f28d587b@haiku-os.org> References: <040.1f975e51ef8b778c0cd49c98f28d587b@haiku-os.org> Message-ID: <049.dad533e320c1b009203ee09f1d3264dc@haiku-os.org> #2289: scsi_dsk, scsi_cd broken, symbol api_version missing ---------------------------+------------------------------------------------ Reporter: monni | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: The device manager and architecture has recently received a major overhaul, and thus the system is not completely working yet. The missing components will be fixed over the next few days. In any case, the new device manager does not use the api_version symbol anymore. Also, scsi_dsk cannot be broken or you couldn't even run Haiku. I've ported scsi_cd today. Just be patient. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 21:02:51 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 19:02:51 -0000 Subject: [Haiku-bugs] [Haiku] #2295: wget and kernel panic Message-ID: <040.3a368ec401595df98af19ca25b66172c@haiku-os.org> #2295: wget and kernel panic --------------------------------+------------------------------------------- Reporter: hugen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Platform: x86 | --------------------------------+------------------------------------------- I used command to download Firefox via Terminal: wget http://sheltonfamily.org/firefoxbuilds/firefox-2.0.0.14.en- US.beosBONE-i586.zip and I have Kernel Panic. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 22:17:50 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 20:17:50 -0000 Subject: [Haiku-bugs] [Haiku] #2295: wget and kernel panic In-Reply-To: <040.3a368ec401595df98af19ca25b66172c@haiku-os.org> References: <040.3a368ec401595df98af19ca25b66172c@haiku-os.org> Message-ID: <049.2ecd5f78d83cbe1d885498d36e1e5f8e@haiku-os.org> #2295: wget and kernel panic ---------------------------------+------------------------------------------ Reporter: hugen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: duplicate | Platform: x86 ---------------------------------+------------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => duplicate Comment: Duplicate of 1641 (and probably 2268). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 22:22:31 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 20:22:31 -0000 Subject: [Haiku-bugs] [Haiku] #2071: No accelerated video starting r24669 nightly In-Reply-To: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> References: <043.0bad686bfb0a381474b780317ac47d69@haiku-os.org> Message-ID: <052.c92d0847e968e4d0c80aab1f13dc4d56@haiku-os.org> #2071: No accelerated video starting r24669 nightly -------------------------------+-------------------------------------------- Reporter: tigerdog | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: | Platform: x86 -------------------------------+-------------------------------------------- Comment (by tigerdog ): as of Friday's nightly, seems to be working. Thanks, Rudolph! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 23:10:38 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 21:10:38 -0000 Subject: [Haiku-bugs] [Haiku] #2229: Background image does not center. In-Reply-To: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> References: <042.985928b5b8cbe7908660123a1f02051e@haiku-os.org> Message-ID: <051.4ffbad6f6d799a3d8ed5c349510b73d6@haiku-os.org> #2229: Background image does not center. --------------------------------------+------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Resolution: invalid | Platform: All --------------------------------------+------------------------------------- Changes (by korli): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 23:47:33 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 21:47:33 -0000 Subject: [Haiku-bugs] [Haiku] #2293: KDL during boot when scanning for devices. In-Reply-To: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> References: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> Message-ID: <047.510bcba1ed0e97f887e1df9d7a87a760@haiku-os.org> #2293: KDL during boot when scanning for devices. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): What revision are you testing with? Also, if at all possible, please enable tracing in device_manager.cpp, and devfs.cpp, and attach a full log until that error comes. The output of the dm_tree KDL command might also be helpful. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 23:53:12 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 21:53:12 -0000 Subject: [Haiku-bugs] [Haiku] #2293: KDL during boot when scanning for devices. In-Reply-To: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> References: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> Message-ID: <047.806260cc5be0f9608ca10366e0d867a9@haiku-os.org> #2293: KDL during boot when scanning for devices. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by axeld): You could also add some debug output to ahci_supports_device(), and pci_device_get_pci_info() to see where and why it fails exactly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 23:56:08 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 21:56:08 -0000 Subject: [Haiku-bugs] [Haiku] #2293: KDL during boot when scanning for devices. In-Reply-To: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> References: <038.a25f50d4ee276053a69672710a6d4660@haiku-os.org> Message-ID: <047.96e408bf393dd77b24a3b06c6ba23d59@haiku-os.org> #2293: KDL during boot when scanning for devices. ----------------------------+----------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Platform: All ----------------------------+----------------------------------------------- Comment (by bga): Since the change in the driver architeture, my machine does not boot Haiku anymore. It crashes when the ahci bus calls ip on the pci bus. KDL capture attched. Let me know if you need more information. As soon as I am back at my computer at home I will try tracing it and will post the results. Didn?t try anything like that yet because I am not near my Haiku computer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 31 23:56:29 2008 From: trac at haiku-os.org (Haiku) Date: Sat, 31 May 2008 21:56:29 -0000 Subject: [Haiku-bugs] [Haiku] #2289: scsi_dsk, scsi_cd broken, symbol api_version missing In-Reply-To: <040.1f975e51ef8b778c0cd49c98f28d587b@haiku-os.org> References: <040.1f975e51ef8b778c0cd49c98f28d587b@haiku-os.org> Message-ID: <049.080853f45782a1f0561c1a2562a17b3f@haiku-os.org> #2289: scsi_dsk, scsi_cd broken, symbol api_version missing ---------------------------+------------------------------------------------ Reporter: monni | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: invalid | Platform: All ---------------------------+------------------------------------------------ Comment (by axeld): BTW if you have a specific error that you don't think is right, please report it; it's not very helpful to have a generic report like this one. -- Ticket URL: Haiku The Haiku operating system.