From trac at haiku-os.org Fri May 1 00:14:35 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Apr 2009 22:14:35 -0000 Subject: [Haiku-bugs] [Haiku] #3846: Intel_extreme driver problem on i855g In-Reply-To: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> References: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> Message-ID: <050.1d0f7aaabe2ce38214b34b5ae5016a16@haiku-os.org> #3846: Intel_extreme driver problem on i855g --------------------------------------------+------------------------------- Reporter: walera | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------------------+------------------------------- Comment(by axeld): That probably means the video address is not properly set; the noise at the top is the memory at the start of the shared memory that is not used for the image itself. Unfortunately, I don't have access to a i855g, and the i865g I have seems to work fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:15:00 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Apr 2009 22:15:00 -0000 Subject: [Haiku-bugs] [Haiku] #3846: Intel_extreme driver problem on i855g In-Reply-To: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> References: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> Message-ID: <050.9daa4bcdeb35c086ef44735bf4bb1d72@haiku-os.org> #3846: Intel_extreme driver problem on i855g --------------------------------------------+------------------------------- Reporter: walera | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------------------+------------------------------- Comment(by axeld): Does changing the resolution work at all? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:32:41 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Apr 2009 22:32:41 -0000 Subject: [Haiku-bugs] [Haiku] #3845: S3 Virge graphics card recognised, but driver is not used In-Reply-To: <044.cd316fffda8a8e4d7c475fafeb96693b@haiku-os.org> References: <044.cd316fffda8a8e4d7c475fafeb96693b@haiku-os.org> Message-ID: <053.8cb7e0c32fdddf63df422566e00fddf4@haiku-os.org> #3845: S3 Virge graphics card recognised, but driver is not used ---------------------------------+------------------------------------------ Reporter: BenoitRen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/S3 | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------------+------------------------------------------ Comment(by axeld): It might also be slow because Stephan disabled the use of the acceleration engine, as with faster memory busses, this actually slows down the graphics instead. So if your card is actually in use, we might want to rethink that change again; in the "old age", acceleration was indeed needed for a good performance. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:41:47 2009 From: trac at haiku-os.org (axeld) Date: Thu, 30 Apr 2009 22:41:47 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.130494801d4717339a3b096eec9bc74f@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): If pinging did not work either, this cannot really be TCPs fault, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:45:11 2009 From: trac at haiku-os.org (diver) Date: Thu, 30 Apr 2009 22:45:11 -0000 Subject: [Haiku-bugs] [Haiku] #3040: [DeskCalc] font size is not consistent In-Reply-To: <040.56fc60ce0c7187980742a776cc8f953f@haiku-os.org> References: <040.56fc60ce0c7187980742a776cc8f953f@haiku-os.org> Message-ID: <049.5b2dba73d699e7fa238ad152223e4afe@haiku-os.org> #3040: [DeskCalc] font size is not consistent ------------------------------------+--------------------------------------- Reporter: diver | Owner: zooey Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/DeskCalc | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: Still here in r30519, reopeining. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:55:00 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Apr 2009 22:55:00 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.3599e01a2c36517c8ce18ad25a9a014c@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Quite puzzling...what happens here is Deskbar tries to do a ConvertToScreen invocation on a parent menu (it selects the parent if it's not in Expando mode). However, when invoked via the keyboard, the parent menu winds up not being locked, while when invoking via the mouse it does...have not yet figured out why. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 00:57:17 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 30 Apr 2009 22:57:17 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.97335226c2e6b70520f0c6cc7f97e5be@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: anevilyak Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): On a related note though, the mouse positioning is irrelevant here. Picking anything from the team submenu via the keyboard suffices to reproduce this bug, regardless of mouse location. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 01:14:22 2009 From: trac at haiku-os.org (bga) Date: Thu, 30 Apr 2009 23:14:22 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.edefd3c2327f4e13ff8630fb80e3929e@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by bga): Well, that's why I said TCP/IP. ;) Anyway, I never tried to ping after I saw the problem but one of the side-effects can be easily visible if you visit http://www.bug-br.org.br. Every single time the page has problems. The most visible one is that images are only half downloaded or not downloaded at all (and yes, works fine in Windows, Linux and MacOS). Check the left nav bar and you will see what I mean. Sometimes it seems not even the full HTML is downloaded! You are probably thinking: Ah, but that could be a Firefox bug! Except that: {{{ [/boot/home]> wget -vvv http://www.bug-br.org.br/img/menu/menu_beos.gif --2009-04-30 20:09:49-- http://www.bug-br.org.br/img/menu/menu_beos.gif Resolving www.bug-br.org.br... 69.73.189.194 Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2063 (2.0K) [image/gif] Saving to: `menu_beos.gif' 70% [==========================> ] 1,448 --.-K/s in 0s 2009-04-30 20:09:49 (11.8 MB/s) - Connection closed at byte 1448. Retrying. --2009-04-30 20:09:49-- (try: 2) http://www.bug- br.org.br/img/menu/menu_beos.gif Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2063 (2.0K), 615 remaining [image/gif] Saving to: `menu_beos.gif' 70% [+++++++++++++++++++++++++++ ] 1,448 --.-K/s in 0s 2009-04-30 20:09:50 (0.00 B/s) - Connection closed at byte 1448. Retrying. --2009-04-30 20:09:50-- (try: 3) http://www.bug- br.org.br/img/menu/menu_beos.gif Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2063 (2.0K), 615 remaining [image/gif] Saving to: `menu_beos.gif' 70% [+++++++++++++++++++++++++++ ] 1,448 --.-K/s in 0s 2009-04-30 20:09:50 (0.00 B/s) - Connection closed at byte 1448. Retrying. --2009-04-30 20:09:50-- (try: 4) http://www.bug- br.org.br/img/menu/menu_beos.gif Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Length: 2063 (2.0K), 615 remaining [image/gif] Saving to: `menu_beos.gif' 70% [+++++++++++++++++++++++++++ ] 1,448 --.-K/s in 0s }}} This is just a snippet, it just continues trying to download and fails at exactly the same point all the time. And yes, at the exact same time I downloaded the same file in 3 different computers here at home and all worked without any problems whatsoever. Hope this helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 01:54:35 2009 From: trac at haiku-os.org (stpere) Date: Thu, 30 Apr 2009 23:54:35 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.a3bcb5c43d06e831bfb5b12a76905219@haiku-os.org> #3752: CharacterMap Window is way too big. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by stpere): Does r30529 help? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 02:08:01 2009 From: trac at haiku-os.org (bga) Date: Fri, 01 May 2009 00:08:01 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.65b3726e9fa0e631e570fa71d29adb3c@haiku-os.org> #3752: CharacterMap Window is way too big. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by bga): Nope. I would guess that in some point in the code it is resizing itself to that huge size. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 03:19:56 2009 From: trac at haiku-os.org (HaiColon) Date: Fri, 01 May 2009 01:19:56 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.75368977a87b1a9a791ee5f811e84670@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by HaiColon): I just remembered that ping doesn't work from within a virtual machine (due to the bridged or NAT networking I guess, can't remember, it is explained in the VirtualBox manual). I can't remember now if I have tried pinging when I was using Haiku in VMWare or when I was using Haiku installed to harddisk, so maybe pinging just didn't work because of VMWare. The harddisk in the computer I had Haiku installed on is dead so I can't test it there but I'll make room on a partition on my other computer and try it out there. Additionally, I found out that Twitter.com also has problems in Haiku. Sometimes Haiku doesn't even connect (or rather, tries to connect for a long time, don't know if it ever timeouts), sometimes it downloads only part of the html source (or xml when using curl and the Twitter API), sometimes it downloads everything as it should. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 03:46:36 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 01 May 2009 01:46:36 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.9889122f00f71a19506d8c4ca6751a88@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by mmlr): Replying to [comment:4 bga]: > http://www.bug-br.org.br. Every single time the page has problems. The most visible one is that images are only half downloaded or not downloaded at all I'm not able to reproduce it with that side. It works just fine for me. > [/boot/home]> wget -vvv http://www.bug-br.org.br/img/menu/menu_beos.gif This one works fine as well, even if trying over and over. Since the download is indicated to stop at 1448. This somehow looks close to the common MTU values, so maybe this is a MTU problem? Depending on the route to a target you'd be able to reproduce or not. Maybe you could try playing around with your MTU setting and see if this changes anything. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 05:20:18 2009 From: trac at haiku-os.org (HaiColon) Date: Fri, 01 May 2009 03:20:18 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.e3c0c6e6f9f0c9fc157ad8a653ef1b42@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by HaiColon): I tried it again in VMware because I get a KDL with the newest revision of Haiku that I installed to disk. Ping does in fact work in VMWare. Maybe it's just VirtualBox where it doesn't work. So, just disregard my last comment :) I can't help with trying out different MTU settings because I don't know how to do that. I only found tutorials on how to do that with ping in Windows, but not on Linux. So hopefully bga or someone else who also encountered this problem will try this out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 05:48:00 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 01 May 2009 03:48:00 -0000 Subject: [Haiku-bugs] [Haiku] #3839: Thunderbird crashes if attaching files to email In-Reply-To: <040.f354711a08343ad3c0c9b83ab3f6cfd1@haiku-os.org> References: <040.f354711a08343ad3c0c9b83ab3f6cfd1@haiku-os.org> Message-ID: <049.cb772ccbd172e4603c5c709efe2fe0ae@haiku-os.org> #3839: Thunderbird crashes if attaching files to email --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): T-bird 2.0.0.17 and I'm now building from Dano using the standard cross- compiler. This fault didn't coincide with the change from 5.0.3 to 5.1d0. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 06:11:57 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 01 May 2009 04:11:57 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.98214f9be86d84b39fadc284c41b572a@haiku-os.org> #3840: CD-ROM build broken --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Checked at r30496 and I can build a bootable CD again. Apparent differences in the build were partially caused by the same fault that I reported in #3766 with the addition that some stuff was still included under the /boot/beos tree. That stuff is no longer visible in the r30496 build. Please close, resolved. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 07:12:45 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 01 May 2009 05:12:45 -0000 Subject: [Haiku-bugs] [Haiku] #3766: BFS formatted USB memory stick shows weird directory structure In-Reply-To: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> References: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> Message-ID: <049.fa1a6fb9256af315c0cd97ce31abb9cb@haiku-os.org> #3766: BFS formatted USB memory stick shows weird directory structure --------------------------------------+------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by haiqu): Further information: Initializing a HDD will exhibit this directory anomaly also. It goes away the first time the Home directory is viewed by selecting it from the tree browser, which is why nobody noctied this before. I'd say it's just some property of /boot/home/Desktop that isn't being set during the build process. If you check a CD build you can see it, and also the /var directory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 10:09:12 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 01 May 2009 08:09:12 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail Message-ID: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> #3847: Boot Fail -----------------------+---------------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- I use Haiku on my laptop (Acer Travelmate 2493). Unfortunately, since r30515 Haiku going in KDL. (See attachment) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 10:44:34 2009 From: trac at haiku-os.org (stippi) Date: Fri, 01 May 2009 08:44:34 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.353230b46a3c0982ecb466326829ec29@haiku-os.org> #3840: CD-ROM build broken ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => invalid Comment: The "update-all" target really has some side effects. It may look like there are problems, but they don't exist on a clean build. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 10:47:01 2009 From: trac at haiku-os.org (stippi) Date: Fri, 01 May 2009 08:47:01 -0000 Subject: [Haiku-bugs] [Haiku] #3766: BFS formatted USB memory stick shows weird directory structure In-Reply-To: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> References: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> Message-ID: <049.ef0ed2cdaab669f3f7efbbe723de1974@haiku-os.org> #3766: BFS formatted USB memory stick shows weird directory structure --------------------------------------+------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by stippi): I am pretty sure that I came across code in Tracker which takes care of such things. For DriveSetup (or the backend which implements initializing), the fix is probably rather easy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 10:49:02 2009 From: trac at haiku-os.org (stippi) Date: Fri, 01 May 2009 08:49:02 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.e66f483061302db153e566ca185dcc3f@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by stippi): * priority: normal => blocker * component: - General => System/Kernel * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 10:50:33 2009 From: trac at haiku-os.org (stippi) Date: Fri, 01 May 2009 08:50:33 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.5b6024a39ae77c216d0b9e7fa4e18fce@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by stippi): If I am not mistaken, the other pre-fetching bug was re-opened mistakenly and then closed again, but no new bug was created? If it was, then this is a duplicate, but otherwise, the bug can be tracked in this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 11:53:47 2009 From: trac at haiku-os.org (walera) Date: Fri, 01 May 2009 09:53:47 -0000 Subject: [Haiku-bugs] [Haiku] #3846: Intel_extreme driver problem on i855g In-Reply-To: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> References: <041.8e2da958b60be9625819b9679aa20321@haiku-os.org> Message-ID: <050.b2789ecb905ef8c9a7eadbb522646186@haiku-os.org> #3846: Intel_extreme driver problem on i855g --------------------------------------------+------------------------------- Reporter: walera | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------------------+------------------------------- Comment(by walera): On first photo (Intel_extreme.jpg) resolution 1024x768 (native resolution for my notebooks) with 32 bit colors. Only this resolution acceptable for work. I add photos with resolution: 1024x768 8 bit (system hang up after apply this mode) - 1024x768_8.jpg 1024x768 16 bit - 1024x768_16.jpg 800x600 32 bit - 800x600_32.jpg 640x480 32 bit (system hang up after apply this mode) - 640x480_32.jpg -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 12:16:33 2009 From: trac at haiku-os.org (axeld) Date: Fri, 01 May 2009 10:16:33 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.faad76f42d99868c6b76c918db83c67d@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by axeld): Can you please tell how much memory your laptop has? This is a very weird bug, and I can't see how this should happen - it means the cache was deleted during the I/O, which should be impossible considering that the calling code as well as the precaching code owns a reference to it. Are you building the images yourselves? Is this a clean build? When exactly does the problem appear? What's the output of the "syslog" and "threads" commands in KDL? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 12:19:27 2009 From: trac at haiku-os.org (axeld) Date: Fri, 01 May 2009 10:19:27 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.73773365de1587daba56a5cf0b41c922@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): An MTU related problem sounds indeed probable. What kind of KDL are you running into now? Is that like #3847? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 12:21:15 2009 From: trac at haiku-os.org (axeld) Date: Fri, 01 May 2009 10:21:15 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.5abd9a7d167f5266155043026c555faf@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): You can change the MTU setting either with the "route" command, or for the whole interface via "ifconfig". Something like "ifconfig /dev/net/ipro1000/0 mtu 1448" should do the trick. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 12:34:43 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 01 May 2009 10:34:43 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.190973a003eac2e2aeda72a81816a5d2@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there, From the looks of it, you depend on a VESA modeswitch before the driver kicks in. This modeswitch needs to set the your native resolution as you pointed out. Haiku's Screen preflet has a nasty side effect (as I just encountered) compared to the BeOS version: it overwrites your VESA settings file after exiting this app. If you would want to test with a lower resolution on the panel after bootup: you probably need to set (for instance) 1024x768 with Screen: exit it, then modify the vesa file to read 1400x1050 Again, then do the reboot. Would that work? (or, probably in other words: if you switch down from 1400x1050 on your correctly working internal panel using 'Screen': does dat immediately kill your display, or does it only kill your display after the next boot-up? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 12:48:52 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 01 May 2009 10:48:52 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.c6169ed9152efe2a1e6a12ab8a5bc970@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): I just tested such a thing here: and it turns out that that vesa settings file might not even be written back to disk promptly. I needed a reboot to find that the file was overwritten by Screen, even though I checked it to be correct *after* exiting that app! So, double-check every step on the way please... Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 13:41:43 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 01 May 2009 11:41:43 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.97b62ad37e65eceaf9669bc2d6b12af7@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by HaikuBot): Laptop has 1Gb DDR2 533, Intel Celeron M 1730 Mhz, Intel GMA 950, 120 Gb HDD. Yep, i`m build by myself. Yes, clean build, I also try raw image r30526 from haiku-files.org. Haiku going in KDL after last boot icon (rocket). Output of syslog and threads in attachments. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 14:10:02 2009 From: trac at haiku-os.org (walera) Date: Fri, 01 May 2009 12:10:02 -0000 Subject: [Haiku-bugs] [Haiku] #3583: listusb not find some USB-devices connected to USB hub In-Reply-To: <041.1fa5d7be7a1d1ea98ad236557a9e05bb@haiku-os.org> References: <041.1fa5d7be7a1d1ea98ad236557a9e05bb@haiku-os.org> Message-ID: <050.c7cf03d804d52de4ff0c1b57b41c755f@haiku-os.org> #3583: listusb not find some USB-devices connected to USB hub -------------------------+-------------------------------------------------- Reporter: walera | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by walera): Replying to [comment:6 mmlr]: > Can you provide a syslog with the lowspeed hub attached please? I update syslog in attachments. This syslog from R30531. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 15:16:05 2009 From: trac at haiku-os.org (bga) Date: Fri, 01 May 2009 13:16:05 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.3170fb3901b453231f61ab3071b181c5@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by bga): It is definitly MTU related, but changing the MTU does not help: {{{ [/boot/home]> ifconfig /dev/net/marvell_yukon/1 mtu 1448 [/boot/home]> ifconfig /dev/net/marvell_yukon/1 Hardware Type: Ethernet, Address: 00:1e:8c:3a:65:24 Media Type: 100 MBit, 100BASE-TX inet addr: 192.168.0.2, Bcast: 192.168.0.255, Mask: 255.255.255.0 MTU: 1448, Metric: 0, up broadcast link Receive: 9356 packets, 0 errors, 7580362 bytes, 0 mcasts, 0 dropped Transmit: 8814 packets, 0 errors, 746182 bytes, 0 mcasts, 0 dropped Collisions: 0 loop Hardware Type: Local Loopback, Address: none inet addr: 127.0.0.1, Mask: 255.0.0.0 MTU: 16384, Metric: 0, up loopback link Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0 }}} The first time I tried to download a problematic image with this, it worked. But then I tried again: {{{ [/boot/home]> wget -vvv http://www.bug-br.org.br/img/menu/menu_beos.gif --2009-05-01 10:06:24-- http://www.bug-br.org.br/img/menu/menu_beos.gif Resolving www.bug-br.org.br... 69.73.189.194 Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2063 (2.0K) [image/gif] Saving to: `menu_beos.gif.2' 67% [=========================> ] 1,396 --.-K/s in 0s 2009-05-01 10:06:25 (25.1 MB/s) - Connection closed at byte 1396. Retrying. }}} Then I changed the MTU again, just in case: {{{ [/boot/home]> ifconfig /dev/net/marvell_yukon/1 mtu 1300 [/boot/home]> ifconfig /dev/net/marvell_yukon/1 Hardware Type: Ethernet, Address: 00:1e:8c:3a:65:24 Media Type: 100 MBit, 100BASE-TX inet addr: 192.168.0.2, Bcast: 192.168.0.255, Mask: 255.255.255.0 MTU: 1300, Metric: 0, up broadcast link Receive: 9569 packets, 0 errors, 7685679 bytes, 0 mcasts, 0 dropped Transmit: 9018 packets, 0 errors, 769910 bytes, 0 mcasts, 0 dropped Collisions: 0 loop Hardware Type: Local Loopback, Address: none inet addr: 127.0.0.1, Mask: 255.0.0.0 MTU: 16384, Metric: 0, up loopback link Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0 }}} And tried again: {{{ [/boot/home]> wget -vvv http://www.bug-br.org.br/img/menu/menu_beos.gif --2009-05-01 10:07:35-- http://www.bug-br.org.br/img/menu/menu_beos.gif Resolving www.bug-br.org.br... 69.73.189.194 Connecting to www.bug-br.org.br|69.73.189.194|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2063 (2.0K) [image/gif] Saving to: `menu_beos.gif.3' 60% [======================> ] 1,248 --.-K/s in 0s 2009-05-01 10:07:35 (10.2 MB/s) - Connection closed at byte 1248. Retrying. }}} As you can see, the failure point is always some bytes before the MTU size. Other than that, I am connected to a cable connection so there is no framing involved (protocol is straight ATM/Ethernet), so the MTU size of 1500 should be fine. Anyway, decreasing the MTU file seems to have improved things a bit as wget tries to download the files 3 or four times and then succeeds. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 16:01:45 2009 From: trac at haiku-os.org (zooey) Date: Fri, 01 May 2009 14:01:45 -0000 Subject: [Haiku-bugs] [Haiku] #3040: [DeskCalc] font size is not consistent In-Reply-To: <040.56fc60ce0c7187980742a776cc8f953f@haiku-os.org> References: <040.56fc60ce0c7187980742a776cc8f953f@haiku-os.org> Message-ID: <049.7be583e4d06f7cae81dbc29c6c15e721@haiku-os.org> #3040: [DeskCalc] font size is not consistent ------------------------------------+--------------------------------------- Reporter: diver | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/DeskCalc | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by zooey): * status: reopened => closed * resolution: => fixed Comment: Thanks diver, for the heads up - should be fixed for real in r30532. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 16:08:20 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 01 May 2009 14:08:20 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.06c5c8af10685e1ae074ccf790327e7d@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by mmlr): It's not just "some bytes" before the MTU size, it seems to always be exactly 52 bytes. So there's probably some buffer size that is miscalculated in some circumstances. It might be interesting to have a dump of the traffic such a wget download triggers and analyze if there is something fishy about the content. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 16:15:33 2009 From: trac at haiku-os.org (marcinw) Date: Fri, 01 May 2009 14:15:33 -0000 Subject: [Haiku-bugs] [Haiku] #3848: Boot failure on Virtual PC 5.1/2004 Message-ID: <042.37a41de3665341efc2c725616f129012@haiku-os.org> #3848: Boot failure on Virtual PC 5.1/2004 ---------------------------+------------------------------------------------ Reporter: marcinw | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Haiku r30526 (pre-built GCC2 image from haiku-files) fails to boot on Virtual PC 5.1 and 2004. Serial output attached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 16:52:39 2009 From: trac at haiku-os.org (bbjimmy) Date: Fri, 01 May 2009 14:52:39 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound Message-ID: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ r30529 This sound system worked perfectly until recent changes were made. I use the startup sound file from BeOS r5. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 16:56:35 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 01 May 2009 14:56:35 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.8d2b8fec74a43b3f68d90413b54108c8@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by anevilyak): * owner: marcusoverhagen => korli * component: Audio & Video => Drivers/Audio Comment: Any specifics as to roughly what revision the behavior changed at? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 17:22:22 2009 From: trac at haiku-os.org (bbjimmy) Date: Fri, 01 May 2009 15:22:22 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.b9a2c38a37dd665dcac70fec53b0c4cb@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by bbjimmy): Works fine in r30496 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 17:42:14 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 01 May 2009 15:42:14 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? Message-ID: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- It is possible that systems are outthere that have an older gfx card, but a fairly recent monitor. In such a case the native resolution of this monitor can be higher than the highest available VESA mode in the card's BIOS. On top of that, it's very possible that the native resolution can be set by the haiku gfx driver. Since such a resolution will automatically also be preset in the 'vesa' config file, on next boot that non-existing mode will be set. The result is no signal (or hanging cards) during the boot and the boot- icons won't be visible. The kernel should check a vesa settings file against reported available VESA modes from the card at boot-time, and fall back to a lower mode if the requested mode is not there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 17:46:29 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 01 May 2009 15:46:29 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.328ba197f5cdc115ce836e5bb44aa4fa@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): I saw this problem on TNT1, TNT2, TNT2-M64, NV11 and NV15 from nvidia. You'll see the monitor shutoff during boot, and come back on after the gfx driver takes over. Assigning to Axel because I think you know how the VESA stuff works, correct? Bye, and thanks in advance for looking into this.. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 17:53:53 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 01 May 2009 15:53:53 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.795f95042541f58fc36e40193e840197@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by rudolfc): * cc: Rudolf.Cornelissen@? (added) Comment: BTW: the kernel reports refreshrates instead of colordepths belonging to the modes. colordepths are the important ones here, not the refresh!?! I know that for the older cards 32bit colordepths are mostly not supported in the VESA bios.. Since the desktop is used in 32bit because otherwise no acc yet, a decent fallback would be 16bit mode VESA during boot. I think you now have all the info I have here. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 17:58:45 2009 From: trac at haiku-os.org (tqh) Date: Fri, 01 May 2009 15:58:45 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.e4f1d5cadfa16f894f2d9e5563996ae2@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by tqh): * cc: fredrik.holmqvist@? (added) Comment: You can test if this patch makes any difference. It's a bit of duplication of what the platform code does on init, but it might be useful. It might need to filter the initial list compared to the monitor mode though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 18:15:48 2009 From: trac at haiku-os.org (kvdman) Date: Fri, 01 May 2009 16:15:48 -0000 Subject: [Haiku-bugs] [Haiku] #3838: Add Vmware Addons? In-Reply-To: <041.de7cdcfbeb199810e19ad5b2e9a0fff4@haiku-os.org> References: <041.de7cdcfbeb199810e19ad5b2e9a0fff4@haiku-os.org> Message-ID: <050.232822453b37c85f0f7544dda2f554f4@haiku-os.org> #3838: Add Vmware Addons? -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Add-Ons/Input Methods | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by kvdman): Vincent, Do you plan on updating and integrating the Vmware Video Driver into your package? There's currently some issues with it: [http://haiku.it.su.se:8180/source/xref/src/add- ons/kernel/drivers/graphics/vmware/] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 19:45:58 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 01 May 2009 17:45:58 -0000 Subject: [Haiku-bugs] [Haiku] #3841: USB Keyboard Loses Shift State When Changing Shift Keys In-Reply-To: <043.30cd2dfa1cfede1d2f01fdfd08a80fa1@haiku-os.org> References: <043.30cd2dfa1cfede1d2f01fdfd08a80fa1@haiku-os.org> Message-ID: <052.b2498306e48fe9769944b469c796c1f5@haiku-os.org> #3841: USB Keyboard Loses Shift State When Changing Shift Keys ----------------------------------+----------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by mmlr): * component: Drivers/Keyboard/USB => Servers/input_server Comment: Actually this is not a problem of usb_hid. The keyboard input_server add- on handles the modifier changes incorrectly. The reported modifier state looks about as follows: {{{ left shift down: 0x0000 -> 0x0101 = B_SHIFT_KEY | B_LEFT_SHIFT_KEY right shift down: 0x0101 -> 0x0301 = B_SHIFT_KEY | B_LEFT_SHIFT_KEY | B_RIGHT_SHIFT_KEY left shift up: 0x0301 -> 0x0200 = B_RIGHT_SHIFT_KEY }}} So when the left shift key is released it will not only remove the B_LEFT_SHIFT_KEY flag, but also incorrectly remove the B_SHIFT_KEY flag. You can see this pretty well in the Keymap preferences where the correct shift key is always displayed as pressed, but the keymap changes from shifted to unshifted when releasing the first modifier key. The reason why you don't see it for PS/2 is a behavioural difference. The PS/2 keyboard driver includes modifiers in repeat key handling, meaning that a pressed shift key will constantly fire B_UNMAPPED_KEY_DOWN and B_MODIFIERS_CHANGED messages. For usb_hid this isn't the case, as it only repeats actual keys and no modifiers. What you get is that the B_SHIFT_KEY flag is removed (incorrectly) as above, but on the next repeat it'll get set again. You can see that in the Keymap prefs as well, as when you release one of the shift keys, the keymap will switch to the unshifted one for a short time and then be shifted again. I'm looking into fixing the lost B_SHIFT_KEY flag now, but I'm not sure about the behaviour difference. I personally find it more sensible to exclude the modifiers from repeat handling as in the usb_hid case as they don't actually need to be repeated. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 20:44:24 2009 From: trac at haiku-os.org (mmlr) Date: Fri, 01 May 2009 18:44:24 -0000 Subject: [Haiku-bugs] [Haiku] #3841: USB Keyboard Loses Shift State When Changing Shift Keys In-Reply-To: <043.30cd2dfa1cfede1d2f01fdfd08a80fa1@haiku-os.org> References: <043.30cd2dfa1cfede1d2f01fdfd08a80fa1@haiku-os.org> Message-ID: <052.2452e20c74cda67e6592f8fe6360f441@haiku-os.org> #3841: USB Keyboard Loses Shift State When Changing Shift Keys -----------------------------------+---------------------------------------- Reporter: bonefish | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30538. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 23:27:02 2009 From: trac at haiku-os.org (mmu_man) Date: Fri, 01 May 2009 21:27:02 -0000 Subject: [Haiku-bugs] [Haiku] #3832: KDL on NFS Mount In-Reply-To: <041.9f4d6ec0ca5e6518be6e2a5063b20c94@haiku-os.org> References: <041.9f4d6ec0ca5e6518be6e2a5063b20c94@haiku-os.org> Message-ID: <050.852547854485023c7c6f1cde5c29ca7f@haiku-os.org> #3832: KDL on NFS Mount -------------------------------+-------------------------------------------- Reporter: egrath | Owner: mmu_man Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/NFS | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by mmu_man): * status: new => closed * resolution: => duplicate Comment: Duplicate of #3500. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 1 23:56:18 2009 From: trac at haiku-os.org (HaiColon) Date: Fri, 01 May 2009 21:56:18 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.f1994d4d90cbf2764e3d1b78f55e2331@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by HaiColon): Replying to [comment:8 axeld]: > An MTU related problem sounds indeed probable. > > What kind of KDL are you running into now? Is that like #3847? Yeah that's the error I get. Thanks for the link, now I don't have to borrow a digital camera :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 00:08:57 2009 From: trac at haiku-os.org (luroh) Date: Fri, 01 May 2009 22:08:57 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.695fec2042617f0d1c6e50ca234c4bb8@haiku-os.org> #3752: CharacterMap Window is way too big. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by luroh): This problem was introduced in r29910, fwiw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 01:08:24 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Fri, 01 May 2009 23:08:24 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.6995d63fdc87a26ad18f35e09ca62c07@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by marcusoverhagen): I also see this error in r30543 (with ata_stack, but I don't think that matters) After using haiku for about 5 to 15 minutes, suddenly usb mouse and keyboard no longer work. in the syslog there is a message "usb uhci: host controller halted" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 01:23:38 2009 From: trac at haiku-os.org (luroh) Date: Fri, 01 May 2009 23:23:38 -0000 Subject: [Haiku-bugs] [Haiku] #3851: increased memory consumption since r30515 Message-ID: <040.75de7e678ec71445a6cc1db2d2e07fac@haiku-os.org> #3851: increased memory consumption since r30515 -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- With r30515, memory consumption has jumped from 72 to 76 MB (+5.5%) in vmware, according to About. Thought I'd just mention this in case it's not wanted/intended behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 01:35:43 2009 From: trac at haiku-os.org (kvdman) Date: Fri, 01 May 2009 23:35:43 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.4e4252258ba85b9630af22bf598fdd41@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by kvdman): * component: Drivers/Disk => Drivers/USB Comment: I changed this to USB, because I believe there's a USB error now affecting all Macs from booting Haiku (tested Haiku with r30522) and the new ATA stack). I hope that Michael Lotz will get a copy, if not could someone CC it to him? I've tested this on a Mac Pro (Desktop) and MacBook, they both book Haiku to the same error, please see the attached screenshot (Z.jpg). By the way, I can't use the keyboard at all on both machines, one's a touchpad, the other a USB keyboard (Apple). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 01:50:43 2009 From: trac at haiku-os.org (HaiColon) Date: Fri, 01 May 2009 23:50:43 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.42f454a085a380a3d55b3cf6e5e2bba1@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by HaiColon): I get the same error on my computer, at least I'm 99% sure. I can't take a picture of it since I don't have a digital camera. From the things I do remember from the stacktrace output it seems to be exactly the same error, goes into KDL after the last boot icon like HaikuBot said. I did a jam clean before building, gcc2 build, 1.5 GB RAM, Gigabyte k8nmf-9 Mainboard, Athlon XP 3200+ CPU. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 01:51:38 2009 From: trac at haiku-os.org (umccullough) Date: Fri, 01 May 2009 23:51:38 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.6ef29d3c37af9c36be280dc172b400a2@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): If there is a new bug, there should be a new ticket. You should use the Blocking/Blocked By to indicate that you cannot re-test the other ticket until the new ticket is fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:05:13 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:05:13 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.a3bbf08dcb201de23a2bc63b0b9bbb96@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by kvdman): Thanks for that info Urias. I just assume the above, but am unsure that's why I'd be uncomfortable with your suggestion. It just seems logical because the keyboards don't work on both machines and there's an EHCI error on both machines which is exactly the same. It is true that I can't debug further because I don't have a working keyboard though, and Intel Mac's don't have PS/2 keyboard controllers - but I'm not a dev. Perhaps someone else can chime in? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:13:36 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 00:13:36 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.144ef41b123c0665a472de8b609803b4@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by marcusoverhagen): * component: Drivers/USB => Drivers/Disk Comment: This Z.jpg is clearly something ehci related. please file a bug report against ehci. Make sure to include a backtrace (type bt and press Enter) in the image next time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:36:29 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:36:29 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.5d0ee8ee97f005bc6fc628d0f4a14fae@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by kvdman): The link to that news item from ReactOS (can run on Macs since 2006 apparently) is here: [http://www.reactos.org/en/news_page_28.html] I think the guy that solved the bug for ReactOS is the founder of the Xbox Linux project: [http://www.michael-steil.de/] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:42:56 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 02 May 2009 00:42:56 -0000 Subject: [Haiku-bugs] [Haiku] #3854: reindexed attributes do not persist across reboots. Message-ID: <041.48927e960c738044b72be859274d7054@haiku-os.org> #3854: reindexed attributes do not persist across reboots. ------------------------------+--------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I took reindex from 30511 (or slightly newer) and dropped it into 30356. `reindex -rv USER:BKP /boot`. The files with that attribute will display as expected in a Tracker Query. On the next reboot only 1 file will display in the Tracker Query. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:53:24 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 00:53:24 -0000 Subject: [Haiku-bugs] [Haiku] #3855: MediaPlayer doesn't play from file beginning Message-ID: <050.3f13a9e1344e1289ab3b664745f769ef@haiku-os.org> #3855: MediaPlayer doesn't play from file beginning --------------------------------------+------------------------------------- Reporter: marcusoverhagen | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- When MediaPlayer is playing an avi file, and I drop a second avi file on the player window, the second file doesn't start playback from the beginning, but instead from somewhere in the middle. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:54:41 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 00:54:41 -0000 Subject: [Haiku-bugs] [Haiku] #3855: MediaPlayer doesn't play from file beginning In-Reply-To: <050.3f13a9e1344e1289ab3b664745f769ef@haiku-os.org> References: <050.3f13a9e1344e1289ab3b664745f769ef@haiku-os.org> Message-ID: <059.3f3c4b834cb2fbb6f69c6d02013a4911@haiku-os.org> #3855: MediaPlayer doesn't play from file beginning --------------------------------------+------------------------------------- Reporter: marcusoverhagen | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => stippi Comment: Perhaps you can fix this faster than I could. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:55:47 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 00:55:47 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.08b0df4fb53607029ff6ffa411b0a505@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): No, there is no bug. I'm absolutely sure that this is not related to USB and just a coincidence that the EHCI finisher is active. Please verify that by removing all USB drivers and the USB bus_manager. This is the classical ide stack crash. Please make sure that you really are using the ata bus_manager and ensure that you haven't installed both of them, because in that case the ide one will be used. Also there is no problem with USB and Macs. USB itself works just fine. The problem is that the interrupt routing doesn't work. The non IO-APIC interrupt model we are using doesn't route through the PCI interrupts. Therefore the USB controllers won't be able to interrupt and all transfers will simply time out. I know that because I have reportedly working Haiku on a Mac Book with USB in polling mode. Please verify the above points so this one can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 03:14:35 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 01:14:35 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.62d20256ae95dc372dab6d898c829b0a@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by marcusoverhagen): There is a KDL module, not included by default in the image, which is called "auto_stack_trace". Please include it in the image to get more debug information. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 03:19:56 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 01:19:56 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.0cbe0ffd899505673e47f8955d4d79fc@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): It's unlikely that the kernel debugger modules are already loaded at this point. What you should be able to do though is to enable on screen debug output and hit "P" to disable paging so that it won't stop when the USB controllers take over. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 03:22:42 2009 From: trac at haiku-os.org (mmu_man) Date: Sat, 02 May 2009 01:22:42 -0000 Subject: [Haiku-bugs] [Haiku] #3500: mount_nfs crashes Haiku In-Reply-To: <040.5ddc569ad312f67ec698af69a1c087e6@haiku-os.org> References: <040.5ddc569ad312f67ec698af69a1c087e6@haiku-os.org> Message-ID: <049.46b977686ec24fece811629c234ddca5@haiku-os.org> #3500: mount_nfs crashes Haiku ------------------------------+--------------------------------------------- Reporter: adamk | Owner: mmu_man Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems/NFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by mmu_man): * status: new => assigned Comment: Fixed in r30546. 2 new calls were introduced in the VFS and the nfs addon wasn't updated accordingly. It still has issues listing subfolders, but at least doesn't crash anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 03:33:58 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 01:33:58 -0000 Subject: [Haiku-bugs] [Haiku] #3731: Font preflet using Layout engine In-Reply-To: <041.e0f4d579835c56a37bd2a983def5082d@haiku-os.org> References: <041.e0f4d579835c56a37bd2a983def5082d@haiku-os.org> Message-ID: <050.752b5ac17f8023ddab4bfc5cb526391e@haiku-os.org> #3731: Font preflet using Layout engine --------------------------+------------------------------------------------- Reporter: stpere | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 03:42:06 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 01:42:06 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.4dd709b574ac6be9eb6564257f25a9b6@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by marcusoverhagen): USB is stable (> 1 hour now) when not using my KVM switch to switch to different machines. Perhaps using the KVM switch CS1764 somehow triggers a bug. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:16:45 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 02:16:45 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.a00dc9a5ace0e05b255ec8ff0947df14@haiku-os.org> #3367: [Screenshot] don't need white border -------------------------------------+-------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stpere): I made a change to Screenshot application some time ago (r30457). There is still the fancy border around the box, but not the white margin. Is it ok for you? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:22:40 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Sat, 02 May 2009 02:22:40 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice Message-ID: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- When switching with a USB KVM switch between machines, haiku will sometimes crash when a file descriptor belonging to the usb mouse is close()ed. See attachment. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:32:04 2009 From: trac at haiku-os.org (schmedly) Date: Sat, 02 May 2009 02:32:04 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.ad22ca42d2ea50c07aa404ef1c92e94f@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by schmedly): I have the same KVM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:39:07 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 02:39:07 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.fe91f86364bb88599f3fe71ae1651d64@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by kvdman): How can I hit 'p' when the keyboard doesn't work? I'll verify that I'm using the ATA bus manager by deleting the IDE drivers tomorrow, but I enabled it in the UserBuildConfig, as described by mmu_man. In any case, the Haiku image as is (haiku-files.org), does not work on Apple products. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:51:55 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 02:51:55 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.e3a8eaca194bbb3439dc1a2905f6c56d@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by kvdman): Hi Michael, Perhaps these tickets are both irrelevant (#1599, and #3853), and can be closed. Then a new one opened regarding: 'The problem is that the interrupt routing doesn't work. The non IO-APIC interrupt model we are using doesn't route through the PCI interrupts. Therefore the USB controllers won't be able to interrupt and all transfers will simply time out. I know that because I have reportedly working Haiku on a Mac Book with USB in polling mode.' -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 04:55:24 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 02 May 2009 02:55:24 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.3245422adf671036af82614947ab797d@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by anevilyak): There isn't really a need for a new ticket for that, it's already a quite well known issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:28:56 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:28:56 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku Message-ID: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Please see the ticket #1599 for relevant info. I believe there's an EHCI error in Haiku, which makes it impossible to boot Haiku on Apple hardware (see the screenshot Z.jpg). I cannot get a backtrace because the keyboard doesn't work on both Apple machines I've tested (MacPro, and MacBook). It is the exact same EHCI error btw. From the ReactOS project: 'ReactOS development builds (trunk) have run fine now for two days on Intel Mac (with Bootcamp installed) computers. Intel Mac's consist of standard hardware but there are some differences which had made it impossible to run ReactOS before. Intel Mac's don't have PS/2 keyboard controllers. GRUB as well as Darwin's BIOS loader had similar problems sometime ago, good that it has been fixed in ReactOS too. Intel Mac's BIOS has a "serial port" bug, it reports that COM1 exist, but no one is there physically. Two other BIOS bug are related to reading CD/DVD drives. ReactOS does support HID-compliant devices, especially USB keyboard and mouse which is relevant for Intel Mac. We want to thank Michael Steil for making this possible. Stay tuned for ReactOS 0.3.1 which will incorporate these improvements and will be released in late december 2006.' -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:17:06 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:17:06 -0000 Subject: [Haiku-bugs] [Haiku] #3852: MeTOS crashing, again. Message-ID: <041.197f1ca39e04144af92c5b9dfe398a45@haiku-os.org> #3852: MeTOS crashing, again. --------------------------------+------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Binary compatibility problem. There was an older bug that was resolved (#1553) regarding MeTOS: [http://www.haikuware.com/directory/view-details/development/gui- creation/metos] but this one seems to involve CTabView, BTabView? Tested on r30522. {{{ GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 225 called debugger(): looper must be locked before proceeding Reading symbols from /boot/system/runtime_loader...done. Loaded symbols for /boot/system/runtime_loader Reading symbols from /boot/system/lib/libbe.so...done. Loaded symbols for /boot/system/lib/libbe.so Reading symbols from /boot/system/lib/libroot.so...done. Loaded symbols for /boot/system/lib/libroot.so Reading symbols from /boot/system/lib/libtracker.so...done. Loaded symbols for /boot/system/lib/libtracker.so Reading symbols from /boot/system/lib/libtranslation.so...done. Loaded symbols for /boot/system/lib/libtranslation.so Reading symbols from /boot/apps/Develop/MeTOS/lib/libMeTOS.so...done. Loaded symbols for /boot/apps/Develop/MeTOS/lib/libMeTOS.so Reading symbols from /boot/apps/Develop/MeTOS/lib/libCS.so...done. Loaded symbols for /boot/apps/Develop/MeTOS/lib/libCS.so Reading symbols from /boot/system/lib/libnetwork.so...done. Loaded symbols for /boot/system/lib/libnetwork.so Reading symbols from /boot/system/lib/libstdc++.r4.so...done. Loaded symbols for /boot/system/lib/libstdc++.r4.so Reading symbols from /boot/system/lib/libtextencoding.so...done. Loaded symbols for /boot/system/lib/libtextencoding.so Reading symbols from /boot/home/config/lib/libiconv.so...done. Loaded symbols for /boot/home/config/lib/libiconv.so Reading symbols from /boot/apps/Develop/MeTOS/AddOns/Translators/MeTOSProjectFile...done. Loaded symbols for /boot/apps/Develop/MeTOS/AddOns/Translators/MeTOSProjectFile Loaded symbols for /boot/apps/Develop/MeTOS/AddOns/Translators/MeTOSProjectFile Reading symbols from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/BePascalCodeGenerator...done. Loaded symbols for /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/BePascalCodeGenerator Reading symbols from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator...done. Loaded symbols for /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/apps/Develop/MeTOS/MeTOS (225) thread MeTOS (225)] 0xffff0104 in ?? () (gdb) bt #0 0xffff0104 in ?? () #1 0x004f78b6 in debugger () from /boot/system/lib/libroot.so #2 0x00323d03 in BLooper::AssertLocked () from /boot/system/lib/libbe.so #3 0x003226bc in BLooper::Unlock () from /boot/system/lib/libbe.so #4 0x0031d506 in BHandler::UnlockLooper () from /boot/system/lib/libbe.so #5 0x009840b1 in CTabView::Select () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #6 0x003ba8d4 in BTabView::AddTab () from /boot/system/lib/libbe.so #7 0x0097c3e5 in CPPCodeWin::CPPCodeWin () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #8 0x0097bfae in CPPCodeGenerator::CPPCodeGenerator () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #9 0x0097c12c in instantiate_VCodeGenerator () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #10 0x00227461 in MetosApp::LoadGenerators () #11 0x00224b24 in MetosApp::MetosApp () #12 0x002244e7 in main () (gdb) cont Continuing. Thread 225 caused an exception: Segment violation Program received signal SIGSEGV, Segmentation fault. 0x003226bc in BLooper::Unlock () from /boot/system/lib/libbe.so (gdb) bt #0 0x003226bc in BLooper::Unlock () from /boot/system/lib/libbe.so #1 0x0031d506 in BHandler::UnlockLooper () from /boot/system/lib/libbe.so #2 0x009840b1 in CTabView::Select () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #3 0x003ba8d4 in BTabView::AddTab () from /boot/system/lib/libbe.so #4 0x0097c3e5 in CPPCodeWin::CPPCodeWin () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #5 0x0097bfae in CPPCodeGenerator::CPPCodeGenerator () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #6 0x0097c12c in instantiate_VCodeGenerator () from /boot/apps/Develop/MeTOS/AddOns/CodeGenerators/CPPCodeGenerator #7 0x00227461 in MetosApp::LoadGenerators () #8 0x00224b24 in MetosApp::MetosApp () #9 0x002244e7 in main () (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:16:34 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 08:16:34 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.1961735ca91551d04f5278c2faafb5c5@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): Yes, same KVM here. ATEN CS-1764. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:23:56 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 08:23:56 -0000 Subject: [Haiku-bugs] [Haiku] #3855: MediaPlayer doesn't play from file beginning In-Reply-To: <050.3f13a9e1344e1289ab3b664745f769ef@haiku-os.org> References: <050.3f13a9e1344e1289ab3b664745f769ef@haiku-os.org> Message-ID: <059.34d3fd33d13c87817bb10417501151c0@haiku-os.org> #3855: MediaPlayer doesn't play from file beginning --------------------------------------+------------------------------------- Reporter: marcusoverhagen | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/MediaPlayer | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by stippi): I can try... the problem is that sometimes the asynchronous playback manager gets in the way. The Controller tries to reset everything, but sometimes the values are reset in the PlaybackManager to old values from the previous stream. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:29:03 2009 From: trac at haiku-os.org (diver) Date: Sat, 02 May 2009 08:29:03 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.19c5cc528e9301a775673a57c52be9d6@haiku-os.org> #3367: [Screenshot] don't need white border -------------------------------------+-------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by diver): I don't know, but from screenshot I think it would look better without fancy border. What do you think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:29:13 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 08:29:13 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.cea0ea01cb41adfbbd485ae7e5e235ad@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by stippi): Karl, from reading through your Live-CD comments on haikuware, it looks like you have tested your Macs with this Live-CD you made. But the problem is that when you enable the ATA stack the way Francois has prepared, it will still not be installed correctly for the boot CD (the floppy image part). I hope to make a patch today which fixes this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:32:35 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 08:32:35 -0000 Subject: [Haiku-bugs] [Haiku] #3852: MeTOS crashing, again. In-Reply-To: <041.197f1ca39e04144af92c5b9dfe398a45@haiku-os.org> References: <041.197f1ca39e04144af92c5b9dfe398a45@haiku-os.org> Message-ID: <050.965995642c0a452f5fb3d3e671ba8e6b@haiku-os.org> #3852: MeTOS crashing, again. --------------------------------+------------------------------------------- Reporter: kvdman | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stippi): * owner: axeld => bonefish Comment: This looks like a problem which Ingo has introduced recently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 10:48:10 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 02 May 2009 08:48:10 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.dc8eed541e28fc2af2c166e01dc94607@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by VinDuv): Replying to [comment:7 rudolfc]: > Would that work? (or, probably in other words: if you switch down from 1400x1050 on your correctly working internal panel using 'Screen': does dat immediately kill your display, or does it only kill your display after the next boot-up? Yes, changing the resolution immediately results in a garbled screen. When the Screens preferences restore the original resolution, the image goes back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:29:53 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:29:53 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.0f6c83cc8ea60a679e9a8c0b03d36787@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by kvdman): I've opened a new ticket in this regard - #3853 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 12:17:35 2009 From: trac at haiku-os.org (Disreali) Date: Sat, 02 May 2009 10:17:35 -0000 Subject: [Haiku-bugs] [Haiku] #2118: Bash Upgrade In-Reply-To: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> References: <042.371c0a519829327d69dea0de369cb4ab@haiku-os.org> Message-ID: <051.677e702f167d6b6248d9965624de5847@haiku-os.org> #2118: Bash Upgrade ---------------------------------------------+------------------------------ Reporter: emitrax | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: Unscheduled Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by Disreali): As bash-4.0 has been released, I would make that version the target. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 12:24:33 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 02 May 2009 10:24:33 -0000 Subject: [Haiku-bugs] [Haiku] #3852: MeTOS crashing, again. In-Reply-To: <041.197f1ca39e04144af92c5b9dfe398a45@haiku-os.org> References: <041.197f1ca39e04144af92c5b9dfe398a45@haiku-os.org> Message-ID: <050.14292f92d5ec1c2188a734a493886ef7@haiku-os.org> #3852: MeTOS crashing, again. ---------------------------------+------------------------------------------ Reporter: kvdman | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r30558. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 12:29:09 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 10:29:09 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.a777a5a63911195aa62f6df15d21ffc0@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by stippi): In r30557, I've now applied the enabling of the ATA stack via {{{HAIKU_ATA_STACK = 1 ;}}} in the UserBuildConfig also to generating the boot CD. You can create a boot CD with the command {{{jam -q haiku-cd}}}. *Only* this command will create a proper boot CD with write and attribute file system overlays, so that a ISO file-system, single-track Live-CD is created where programs think they can write to the CD. I don't know how you created the Senryu boot CD, but please check with a plain Haiku boot CD, in order to rule out any errors specific to your Senryu distro. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 12:30:57 2009 From: trac at haiku-os.org (rudolfc) Date: Sat, 02 May 2009 10:30:57 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.f36a587f7ba0f816571073be64d3f4b6@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Could you modify nvidia.settings to disable the force_ws option? The aspect ratio mentioned in your logfile is wrong (1.6 instead of 1.33). Maybe panel scaling messes up... Sorry I did not see that before. force_ws is enabled by default these days since a lot of monitors are ws, but maybe that's a problem on some (your) system??? Please test and upload a new logfile with that setting changed.. Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 02:24:21 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 00:24:21 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.ef8fccba50ddadce596b41e2865959cf@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by kvdman): Thanks for that Marcus, I can't type bt, because the keyboards don't work on either machines, either the touchpad or USB keyboard, see the ReactOS comment, I think it may be relavant: ''ReactOS development builds (trunk) have run fine now for two days on Intel Mac (with Bootcamp installed) computers. Intel Mac's consist of standard hardware but there are some differences which had made it impossible to run ReactOS before. Intel Mac's don't have PS/2 keyboard controllers. GRUB as well as Darwin's BIOS loader had similar problems sometime ago, good that it has been fixed in ReactOS too. Intel Mac's BIOS has a "serial port" bug, it reports that COM1 exist, but no one is there physically. Two other BIOS bug are related to reading CD/DVD drives. ReactOS does support HID-compliant devices, especially USB keyboard and mouse which is relevant for Intel Mac. We want to thank Michael Steil for making this possible. Stay tuned for ReactOS 0.3.1 which will incorporate these improvements and will be released in late december 2006.' But, I'll file a new bug in this EHCI bug then, although I can't do much more. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 15:05:53 2009 From: trac at haiku-os.org (korli) Date: Sat, 02 May 2009 13:05:53 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.1bd4e6e82514edba601af5e7ab0ccd0a@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by korli): Maybe related to wav reader changes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 15:18:45 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 13:18:45 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.4ffa2f12769907ac54d0b49d7bea95b0@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Iteresting. Sadly "Host Controller Halted" is not a very informative error code on it's own. The specs list it to be set when in single stepping mode after fetching a descriptor (which we're not using), when the run/stop bit goes to 0 (which we never do) or when an internal error occurs (only candidate). They also list a few explicit conditions that cause it to get set namely PCI master/target aborts (unlikely, I've never seen that anywhere at least), suspend mode (which we aren't using), again run/stop which we are only setting to run on initialization, or the two actual error cases invalid max length or invalid PID. In case it is a host error the "Host System Error" bit would be set as well, and in case it's a protocol error the "Process Error" bit should be set (likely the device not properly shutting down the connection). Any of you that can reproduce this please change the TRACE_MODULE() to TRACE_MODULE_ERROR() in lines 1716 and 1721 in src/add-ons/kernel/busses/usb/uhci.cpp to verfiy that. In case it's a protocol error it's possible that we can just reenable the schedule, but we'll likely need some cleanup to happen and I'd like to cross reference other implementations before doing any change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 15:39:25 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 13:39:25 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.a2e5529575d2065b042f820d9e380348@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): I enabled it generally r30565 now, so you can just update as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 15:45:35 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 13:45:35 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.b158cc58f462b3b2ae905804766b345b@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): Replying to [comment:5 kvdman]: > How can I hit 'p' when the keyboard doesn't work? If you are able to navigate the boot menu to enable on-screen debug output (I heard it is troublesome due to it loosing keystrokes, but it should work with some persistence) you should also be able to press "p" through legacy keyboard emulation. You just have to press "p" before the USB controllers are initialized as that will kick out any remaining emulation. You can hit it after the first page of output. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 16:12:34 2009 From: trac at haiku-os.org (bga) Date: Sat, 02 May 2009 14:12:34 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.445fde4b735e3df237cbf33600c0e843@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bga): It also stops here for me (sometimes it runs for hours, sometimes for minutes) and I am not using any KVM switches. *BUT* i am using the keyboard connected to the computer and the mouse connected to the keyboard (the keyboard acts as a hub). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 16:31:12 2009 From: trac at haiku-os.org (oco) Date: Sat, 02 May 2009 14:31:12 -0000 Subject: [Haiku-bugs] [Haiku] #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be Message-ID: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ New bug entry to report the one found by HaikuBot (in #3835). I reproduce it on my new laptop with r30563. This laptop is a dual-core with 4 Gb of memory. Here is a link to a screen shot with the call stack : http://dev.haiku- os.org/attachment/ticket/3835/KDL.jpg -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 16:42:44 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 02 May 2009 14:42:44 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.1647927c1354a6283a259354f0dcdd74@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Replying to [comment:12 bga]: > It also stops here for me (sometimes it runs for hours, sometimes for minutes) and I am not using any KVM switches. Then it's likely an unrelated issue. That it's behind a hub shouldn't matter. There is at least one known issue related to hubs, but it will either work or not, not stop after some time. There's already another bug report open for that issue I think. If you can make out an actual error in syslog when this happens that'd be helpful. Best to just leave a "tail -F /var/log/syslog" running in a visible Terminal somewhere so you can catch it even without input devices. Also if this is a host controller going down, you should be able to connect to other ports controlled by other controllers to get the devices back. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:03:06 2009 From: trac at haiku-os.org (HaikuBot) Date: Sat, 02 May 2009 15:03:06 -0000 Subject: [Haiku-bugs] [Haiku] #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be In-Reply-To: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> References: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> Message-ID: <047.f9127ecae720e74df2695f767f78d239@haiku-os.org> #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by HaikuBot): I already opened ticket #3847. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:12:58 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 15:12:58 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.a2b67f6d63d62de075c2638aa6a55493@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku -------------------------+-------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by kvdman): I've used a new ISO CD as per Stephan's patch r30557. Michael was right. It now boots, but stops with a new error. It's also the same error in Qemu, as the two Macs. Attached > A.jpg. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:17:41 2009 From: trac at haiku-os.org (oco) Date: Sat, 02 May 2009 15:17:41 -0000 Subject: [Haiku-bugs] [Haiku] #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be In-Reply-To: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> References: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> Message-ID: <047.19692813e34271c51bb68e0ab78cc9cc@haiku-os.org> #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be ---------------------------+------------------------------------------------ Reporter: oco | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by oco): Oh sorry ! Didn't find it after only a very quick search. I should be more careful next time. I will update the new one as there is already a discussion. This one could be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:27:30 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 02 May 2009 15:27:30 -0000 Subject: [Haiku-bugs] [Haiku] #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be In-Reply-To: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> References: <038.3321877ca5d32277ef299d90db825b13@haiku-os.org> Message-ID: <047.c10a19d0108c1ce40fc3017dc02b7f08@haiku-os.org> #3857: [precache] PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbe47 from eip 0x800402be ----------------------------+----------------------------------------------- Reporter: oco | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3847 Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate * blockedby: => 3847 Comment: Duplicate of #3847. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:27:54 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 02 May 2009 15:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #3853: EHCI bug prevent Apple products from booting Haiku In-Reply-To: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> References: <041.1aa85d7a2fc2808e24e307b5fe4ab14f@haiku-os.org> Message-ID: <050.3ebf8db4d0092ea39a189732ce738232@haiku-os.org> #3853: EHCI bug prevent Apple products from booting Haiku --------------------------+------------------------------------------------- Reporter: kvdman | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: invalid | Blockedby: 3847 Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => invalid * blockedby: => 3847 Comment: That would be ticket #3847. Closing this one as it no longer serves any purpose of its own. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 17:35:32 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 15:35:32 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.635a39d21646b2ea9b3748848d79a9ac@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: 3847 | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by kvdman): * blockedby: => 3847 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 18:55:27 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 16:55:27 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.849e8ce9295fb2dcee6a89dc40988b13@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): I can reproduce this bug without ever using the KVM to switch computers. I am not sure that what BGA is seeing is something else necessarily. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 19:35:01 2009 From: trac at haiku-os.org (oco) Date: Sat, 02 May 2009 17:35:01 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.a2830df8c41bb966c8a335739a6670ec@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by oco): * blocking: 1599, 3853, 3857 => Comment: I reproduce it on my new laptop with r30563. This laptop is a dual-core with 4 Gb of memory. I am not able to reproduce it on my older one with 512 Mb.[[BR]] I is my own build, compiled under Haiku. I boot from a USB hard drive. I will add some more informations later (syslog and threads). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 19:55:48 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 02 May 2009 17:55:48 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.a88c25223e9baecd16df098547cebf73@haiku-os.org> #3752: CharacterMap Window is way too big. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by jonas.kirilla): Looking at CharacterMap (having zoomed it to fit the screen) the bottom and right borders look oddly borderless, as if the view could draw on those borders. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:03:55 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 02 May 2009 18:03:55 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.4bf01d3e7dbbb507964b5c207d01c9ca@haiku-os.org> #3752: CharacterMap Window is way too big. ---------------------------------------+------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------+------------------------------------ Comment(by jonas.kirilla): See screenshots. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:07:35 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 18:07:35 -0000 Subject: [Haiku-bugs] [Haiku] #2984: StyledEdit font selection In-Reply-To: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> References: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> Message-ID: <050.ef0629f72cadf942c2f9022b16bccf36@haiku-os.org> #2984: StyledEdit font selection -------------------------------------+-------------------------------------- Reporter: miqlas | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by stpere): * owner: korli => stpere * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:12:48 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 18:12:48 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.fd335b1e016e398f99950336f27d7d47@haiku-os.org> #3367: [Screenshot] don't need white border -------------------------------------+-------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stpere): I joined a screenshot showing how it would look without the fancy border. You be the judge :) If you think it would look better and nobody opposes, I will commit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:29:28 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 18:29:28 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.0ee258650bdee775932bdf3d84f3ceb8@haiku-os.org> #3367: [Screenshot] don't need white border -------------------------------------+-------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): I would like the scrollview/text control border (same thing). If nothing else, you can make a view that uses be_control_look to draw the border, or add it to the image displaying view. The BBox border (fancy border) has changed to be 3 pixels wide, and there is a raised inner edge now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:40:10 2009 From: trac at haiku-os.org (kvdman) Date: Sat, 02 May 2009 18:40:10 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.d9e7142ef4e4ca440aed1fb3e63e7eba@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by kvdman): Why was 1599 blocking removed? 1599 hasn't been closed and this bug is blocking Haiku from booting on Macs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 20:59:22 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 02 May 2009 18:59:22 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.d0c354439fcac95c9b7478c930aefafe@haiku-os.org> #3847: Boot Fail ------------------------------+--------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 1599, 3853, 3857 | ------------------------------+--------------------------------------------- Changes (by anevilyak): * blocking: => 1599, 3853, 3857 Comment: Probably an accidental edit on oco's part. Reinstated previous blocker list. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 21:07:42 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 02 May 2009 19:07:42 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.c1f05ea45d66741949186ea75841bc41@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by VinDuv): Replying to [comment:10 rudolfc]: > Could you modify nvidia.settings to disable the force_ws option? The aspect ratio mentioned in your logfile is wrong (1.6 instead of 1.33). Maybe panel scaling messes up... That was it ! It works now :-) Thanks ! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 21:36:52 2009 From: trac at haiku-os.org (axeld) Date: Sat, 02 May 2009 19:36:52 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.53a0129cea430baa85ba0198980a4c2f@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857 | ---------------------------+------------------------------------------------ Changes (by axeld): * blocking: 1599, 3853, 3857 => 3857 Comment: Those bugs have *nothing* to do with this bug, so removing from the blocking ones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 21:50:18 2009 From: trac at haiku-os.org (luroh) Date: Sat, 02 May 2009 19:50:18 -0000 Subject: [Haiku-bugs] [Haiku] #1667: Haiku runs dogslow on real hardware (kernel team hang) In-Reply-To: <041.1fb9edae2424a800ee459de53364b90e@haiku-os.org> References: <041.1fb9edae2424a800ee459de53364b90e@haiku-os.org> Message-ID: <050.53068bac46c66bef8562637c6de8b704@haiku-os.org> #1667: Haiku runs dogslow on real hardware (kernel team hang) ---------------------------+------------------------------------------------ Reporter: konrad | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by luroh): konrad: does this still happen? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 22:32:10 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 20:32:10 -0000 Subject: [Haiku-bugs] [Haiku] #2984: StyledEdit font selection In-Reply-To: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> References: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> Message-ID: <050.c9e002b7e755d3b707610270105f645b@haiku-os.org> #2984: StyledEdit font selection -------------------------------------+-------------------------------------- Reporter: miqlas | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stpere): I committed a fix for this in r30590. I think I got all corner cases covered, but I will leave this ticket open a few days just in case I missed one. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 22:33:35 2009 From: trac at haiku-os.org (zooey) Date: Sat, 02 May 2009 20:33:35 -0000 Subject: [Haiku-bugs] [Haiku] #3829: [patch] Locale Kit integration In-Reply-To: <045.44df21a597c18dbc1e9d8a0f87334a78@haiku-os.org> References: <045.44df21a597c18dbc1e9d8a0f87334a78@haiku-os.org> Message-ID: <054.b704f4b96fb8a8c41bf12465c2dd0a7f@haiku-os.org> #3829: [patch] Locale Kit integration --------------------------+------------------------------------------------- Reporter: pulkomandy | Owner: zooey Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Applied - the locale kit can now be built and some parts are even working. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 22:39:53 2009 From: trac at haiku-os.org (stippi) Date: Sat, 02 May 2009 20:39:53 -0000 Subject: [Haiku-bugs] [Haiku] #2984: StyledEdit font selection In-Reply-To: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> References: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> Message-ID: <050.c40955cb9f81fa16093a001a74fea000@haiku-os.org> #2984: StyledEdit font selection -------------------------------------+-------------------------------------- Reporter: miqlas | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): In praxis, it turned out to be usually more convenient to rather close a ticket in error, then to leave stale tickets around that sometimes get forgotten. :-) If you are not sure, you can leave a comment like "Please reopen if...". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 2 22:43:47 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 20:43:47 -0000 Subject: [Haiku-bugs] [Haiku] #2984: StyledEdit font selection In-Reply-To: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> References: <041.64e6671517863b2ce1ba34b65ff2e273@haiku-os.org> Message-ID: <050.10a371b44c2d37434fcec850c0b50998@haiku-os.org> #2984: StyledEdit font selection --------------------------------------+------------------------------------- Reporter: miqlas | Owner: stpere Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: Please reopen if... ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 00:53:21 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 02 May 2009 22:53:21 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.e071cd5836bec5b14a972bf73bec49d0@haiku-os.org> #3840: CD-ROM build broken ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Stippi, The `update-all` build target hasn't been available since before I started working on the modern Haiku, over a month ago. I use: jam -q haiku-image A complete clean build each time is out of the question, it would take too long. As it is, today's `svn update` invoked a 3960 file rebuild which will take an hour or so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 00:56:54 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 02 May 2009 22:56:54 -0000 Subject: [Haiku-bugs] [Haiku] #3766: BFS formatted USB memory stick shows weird directory structure In-Reply-To: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> References: <040.27f288c1d8bcf4d294243f26db61ae03@haiku-os.org> Message-ID: <049.cf6d2378af5fbc46c888611e333a986d@haiku-os.org> #3766: BFS formatted USB memory stick shows weird directory structure --------------------------------------+------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by haiqu): Yes, I expected it would be fairly simple. Of course you could not fix it in a CD build, unless the invisible directory characteristics could somehow be written into the image and transferred. But during a disk/stick format, sure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 01:00:20 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 23:00:20 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.eee1ec88ca69e720bea1747b20c3c4b9@haiku-os.org> #3367: [Screenshot] don't need white border --------------------------------------+------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by stpere): * status: new => closed * resolution: => fixed Comment: I committed a fix for this in r30593. If it's still not perfect, feel free to reopen this ticket. The new border is definitely more subtle. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 01:27:15 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 02 May 2009 23:27:15 -0000 Subject: [Haiku-bugs] [Haiku] #3692: Disable message at Restart/Shutdown??? In-Reply-To: <040.2bc2b38fe485ff25e867065bd6aeea4e@haiku-os.org> References: <040.2bc2b38fe485ff25e867065bd6aeea4e@haiku-os.org> Message-ID: <049.4e2d524211625d7c1f21fdd4744e3715@haiku-os.org> #3692: Disable message at Restart/Shutdown??? -----------------------------+---------------------------------------------- Reporter: haiqu | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Comment(by haiqu): I'm happy with the solution implemented in #3733. Nice work! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 01:47:05 2009 From: trac at haiku-os.org (stpere) Date: Sat, 02 May 2009 23:47:05 -0000 Subject: [Haiku-bugs] [Haiku] #3717: Remove "Fonts" tab from Fonts preferences applet In-Reply-To: <039.8db3020ae74dbbf5bc2db0d74319dd78@haiku-os.org> References: <039.8db3020ae74dbbf5bc2db0d74319dd78@haiku-os.org> Message-ID: <048.7f79bd13699548ae3fa085597de10ec5@haiku-os.org> #3717: Remove "Fonts" tab from Fonts preferences applet -----------------------------+---------------------------------------------- Reporter: koki | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3716 -----------------------------+---------------------------------------------- Changes (by stpere): * status: new => closed * resolution: => fixed Comment: I implemented this suggestion in r30594. It will be easy to revert to the tabView when more tabs are needed in the future. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 02:37:12 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 03 May 2009 00:37:12 -0000 Subject: [Haiku-bugs] [Haiku] #3733: re-implement Deskbar's restart+shutdown functionality In-Reply-To: <041.c84dde6563a93760db74575728c4c5a2@haiku-os.org> References: <041.c84dde6563a93760db74575728c4c5a2@haiku-os.org> Message-ID: <050.d91ac9e0eba95fbf9a7c1d568c9c25d6@haiku-os.org> #3733: re-implement Deskbar's restart+shutdown functionality -----------------------------------+---------------------------------------- Reporter: mmadia | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Deskbar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: implemented in Changeset [30512] by kirilla -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 03:01:33 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 01:01:33 -0000 Subject: [Haiku-bugs] [Haiku] #3384: App/Demo Pulse : incorect mode restoration from Deskbar In-Reply-To: <041.47b897692cf227e672887ddab74bf324@haiku-os.org> References: <041.47b897692cf227e672887ddab74bf324@haiku-os.org> Message-ID: <050.de2063f487753dfe970e8afaa447df7b@haiku-os.org> #3384: App/Demo Pulse : incorect mode restoration from Deskbar ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: stpere Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30595. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 03:08:14 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 01:08:14 -0000 Subject: [Haiku-bugs] [Haiku] #3611: scrollbar : incorrect scrolling In-Reply-To: <041.559a2e0d9d4df1b111410a7c68b8ddd7@haiku-os.org> References: <041.559a2e0d9d4df1b111410a7c68b8ddd7@haiku-os.org> Message-ID: <050.72c8ae683293fef9012fc5b78d59e124@haiku-os.org> #3611: scrollbar : incorrect scrolling --------------------------------+------------------------------------------- Reporter: mmadia | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stpere): * owner: axeld => stpere * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 03:24:26 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 01:24:26 -0000 Subject: [Haiku-bugs] [Haiku] #3611: scrollbar : incorrect scrolling In-Reply-To: <041.559a2e0d9d4df1b111410a7c68b8ddd7@haiku-os.org> References: <041.559a2e0d9d4df1b111410a7c68b8ddd7@haiku-os.org> Message-ID: <050.22fbe527d94f2311a85719b9da79e66a@haiku-os.org> #3611: scrollbar : incorrect scrolling ---------------------------------+------------------------------------------ Reporter: mmadia | Owner: stpere Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: fixed in r30596! Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 05:25:11 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 03:25:11 -0000 Subject: [Haiku-bugs] [Haiku] #3300: Terminal in full screen doesn't have scrollbar for one tab In-Reply-To: <042.6b93559de8d3d54462270057e7eb5a5f@haiku-os.org> References: <042.6b93559de8d3d54462270057e7eb5a5f@haiku-os.org> Message-ID: <051.333484323552e8906f9a72e7f02d2f76@haiku-os.org> #3300: Terminal in full screen doesn't have scrollbar for one tab ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by stpere): * status: new => closed * resolution: => fixed Comment: I committed a fix for this in r30597. Thanks ! If you feel there should be a scrollbar when there is only one tab open, we can discuss it. It is certainly possible to do. For the moment, it's fixed when there are several tabs open. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 02:23:47 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 00:23:47 -0000 Subject: [Haiku-bugs] [Haiku] #3384: App/Demo Pulse : incorect mode restoration from Deskbar In-Reply-To: <041.47b897692cf227e672887ddab74bf324@haiku-os.org> References: <041.47b897692cf227e672887ddab74bf324@haiku-os.org> Message-ID: <050.489072c20baed8b9be853b776ec09887@haiku-os.org> #3384: App/Demo Pulse : incorect mode restoration from Deskbar -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by stpere): * owner: axeld => stpere * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 07:52:09 2009 From: trac at haiku-os.org (umccullough) Date: Sun, 03 May 2009 05:52:09 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.bd5fdb112888f84537c005ef1fe9e814@haiku-os.org> #3840: CD-ROM build broken ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): update-all is not a target, it's a build action. It's meant to be used with a build profile (very easy to setup in your UserBuildConfig). In order to use it, you would invoke with: jam -q @profilename update-all where @profilename represents a build profile you have declared to either build an image (either raw or vmware), build to a partition device, or install to BFS directory (the last option is only available from beos- compatible hosts) As stippi indicates, the update-all build action does have issues anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 09:39:46 2009 From: trac at haiku-os.org (diver) Date: Sun, 03 May 2009 07:39:46 -0000 Subject: [Haiku-bugs] [Haiku] #3367: [Screenshot] don't need white border In-Reply-To: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> References: <040.c35e9caf54822a3830994bedf79216ca@haiku-os.org> Message-ID: <049.ded21b0af7be7bdc6c48d17a050f1358@haiku-os.org> #3367: [Screenshot] don't need white border --------------------------------------+------------------------------------- Reporter: diver | Owner: julun Type: enhancement | Status: closed Priority: low | Milestone: R1 Component: Applications/Screenshot | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by diver): Thanks, the new border is fine :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 09:58:27 2009 From: trac at haiku-os.org (borg1980) Date: Sun, 03 May 2009 07:58:27 -0000 Subject: [Haiku-bugs] [Haiku] #3858: Continuous system speaker beep after reboot Message-ID: <043.ff7e0c2356629ecb702e8fce1e0bdcbd@haiku-os.org> #3858: Continuous system speaker beep after reboot -----------------------+---------------------------------------------------- Reporter: borg1980 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- After every Haiku restart (reboot) my system speaker beeps continuously until i press reset button. Soundcard - AD1988A. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 10:01:09 2009 From: trac at haiku-os.org (stippi) Date: Sun, 03 May 2009 08:01:09 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.255aa05a30715b7428e8e58023bd2d2b@haiku-os.org> #3840: CD-ROM build broken ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): It looks to me like your original problem was that you installed a clean build (what you get from jam -q haiku-image) over an existing installation -- resulting in a mess after the directory restructuring we did, which you slowly resolved. I assumed you had reached this point by using "update- all". Looking from the point of the result, it's pretty much the same thing. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 10:18:57 2009 From: trac at haiku-os.org (shinta) Date: Sun, 03 May 2009 08:18:57 -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.743f8b44b838d6bd25f24f239754f8f5@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by shinta): * status: closed => reopened * resolution: fixed => Comment: Sorry, I mistook the key name. Not B_ZENKAKU_HANKAKU, but B_HANKAKU_ZENKAKU. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 10:20:23 2009 From: trac at haiku-os.org (shinta) Date: Sun, 03 May 2009 08:20:23 -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.1df13b5d210748c192a6e1358187f3dd@haiku-os.org> #2222: Zenkaku/Hankaku key code in Japanese keymap -----------------------------------+---------------------------------------- Reporter: shinta | Owner: korli Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Servers/input_server | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Comment(by shinta): Above zenhan.diff fixes the name. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 10:21:03 2009 From: trac at haiku-os.org (stippi) Date: Sun, 03 May 2009 08:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder Message-ID: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I have a mail folder where I sort notifications from our Trac into. Sometimes, after retrieving mails, the number of mails in this folder is back down to 13 messages, even though additional messages have accumulated there in the past days/weeks. It's like the second or third time that this has happened. I retrieved mails with Beam. Beam showed 20 new messages this morning after I last checked mails yesterday. When I clicked on the mail folder, there were no new messages and quite a few older ones where deleted. Only those 13 mails left. This is what the syslog has to say about this: {{{ KERN: bfs: mounted "Traffic" (root node at 524288, device = /dev/disk/scsi/0/5/0/3_2) KERN: /dev/net/rtl8139/0: media change, media 0x900026 quality 1000 speed 10000 KERN: hda_stream_start() offset 80 KERN: hda_stream_start() offset 0 KERN: bfs: bfs_create_index:1986: File or Directory already exists KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790012 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790012 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790012 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790012 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 790293 is already deleted! KERN: bfs: GetNextMatching:1060: Bad data KERN: bfs: could not get inode 790293 in index "be:deskbar_item_status"! KERN: bfs: bfs_create_index:1986: File or Directory already exists Last message repeated 1 time KERN: ps2: probe_mouse Extended PS/2 mouse found KERN: ps2: devfs_publish_device input/mouse/ps2/intelli_0, status = 0x00000000 KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found Last message repeated 1 time KERN: bfs: bfs_open_dir:1528: Invalid Argument KERN: bfs: inode at 281479271677984 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 281479271677984 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 281479271677984 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 281479271677984 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: KERN: could not get inode 0 in index "MAIL:status"! KERN: bfs: KERN: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: KERN: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 1136640 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: invalid duplicate node: first left link points to 545460846595! Last message repeated 12 times KERN: bfs: removeDuplicate: Invalid array size in duplicate 924672 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: invalid duplicate node: first left link points to 545460846595! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 3688327 is already deleted! KERN: bfs: InitCheck:310: Bad data KERN: bfs: inode at 3688327 is already deleted! KERN: bfs: bfs_open_dir:1528: Invalid Argument KERN: bfs: inode at 281479271677984 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 281479271677984 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 281479271677984 requested! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 281479271677984 in index "MAIL:status"! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: bfs: inode at 0 requested! KERN: bfs: GetNextMatching:1060: General system error KERN: bfs: could not get inode 0 in index "MAIL:status"! KERN: register_domain(9, unix) KERN: bfs: removeDuplicate: Invalid array size in duplicate 43008 == 282720517226520! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: removeDuplicate: Invalid array size in duplicate 391168 == -1! KERN: bfs: Insert:1300: Bad data KERN: bfs: Update:290: Bad data KERN: bfs: invalid duplicate node: first left link points to 545460846595! KERN: bfs: Insert:1300: I/O error KERN: bfs: Update:290: I/O error }}} I don't know what is special about this folder. Hm, IIRC, one time I merged mails in this folder from my other machine. I zipped up all the mails in that machines "trac" folder and copied the zip over to my main work machine, unzipped it there and removed any duplicate mails. This was after April 10. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 10:32:42 2009 From: trac at haiku-os.org (stippi) Date: Sun, 03 May 2009 08:32:42 -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.41319c4d9c640b12a3bf43a8b6fc5e56@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 | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Fixed in r30599. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 11:00:32 2009 From: trac at haiku-os.org (shinta) Date: Sun, 03 May 2009 09:00:32 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX Message-ID: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> #3860: Mime type database for MDX -------------------------+-------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- I want a file type for MDX. Currently, I'm developing MDX codec. Haiku: r30186[[BR]] [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (enhancement No.6) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 11:09:44 2009 From: trac at haiku-os.org (shinta) Date: Sun, 03 May 2009 09:09:44 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX In-Reply-To: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> References: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> Message-ID: <050.af865b47b47f653ccdb7f32943241023@haiku-os.org> #3860: Mime type database for MDX -------------------------+-------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by shinta): Above x-mdx is the file for src/data/beos_mime/audio to add MDX mime type. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 12:04:22 2009 From: trac at haiku-os.org (stippi) Date: Sun, 03 May 2009 10:04:22 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.68216fa9ac22d36c54a2f781f29d5008@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): This is what I got now with r30575: {{{ KERN: usb uhci: process error KERN: usb uhci: host controller halted KERN: usb error control pipe 44: timeout waiting for queued request to complete KERN: usb error hub 43: error updating port status KERN: usb error control pipe 44: timeout waiting for queued request to complete KERN: usb error hub 43: error updating port status KERN: usb error control pipe 44: timeout waiting for queued request to complete KERN: usb error hub 43: error updating port status KERN: usb error control pipe 44: timeout waiting for queued request to complete KERN: usb error hub 43: error updating port status }}} The last two lines keep repeating every second or so. So it's a "process error", whatever that means. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 13:10:24 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 03 May 2009 11:10:24 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.6068c5acdcae89da3dfa9bdc0349742e@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Hi, I've got extra information: it turns out that the 32bit mode is available, but only for DVI connected screens. On a VGA connected screen the screen turns off. I am hoping that the VESA definition has info on colordepths supported for the modes, and maybe also have info on the connection type, so that Haiku's kernel can take that into account. Another option would be checking the modesetting status reported by the VESA BIOS, and on failure fallback to a lower mode. If such a status bit is defined that is.. Axel? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 13:51:32 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 03 May 2009 11:51:32 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX In-Reply-To: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> References: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> Message-ID: <050.96052969ce54ca948c4fd34641eafb02@haiku-os.org> #3860: Mime type database for MDX --------------------------+------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by jonas.kirilla): * status: new => closed * resolution: => fixed Comment: Committed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 14:00:35 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 03 May 2009 12:00:35 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.aeadb8da220f8c0b45ea5f863a74acd9@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by bonefish): * priority: normal => high * milestone: R1 => R1/alpha1 Comment: Just ran into it with r30345. Bumping priority and milestone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 14:45:00 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 03 May 2009 12:45:00 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.44299abdc776818e2b3353ab6a8e142e@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Additional info: same error is there on NV28, GF4Ti, ID0x0281. Port2 has a less good DAC than port 1, so ort2 can do VESA1280x1024x32 only on DVI connections.. 16bit mode works though. (no icons screen in 32bit.) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 14:48:42 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 03 May 2009 12:48:42 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.22b4568e9c4169a2c77e19fefb620c92@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Eliminated a possible cause in r30605. When a mapped file was shrunk, pages could be freed without removing their mappings. That would fit the reported case where the mapping was in a "libtracker.so_seg0ro" area, *if* libtracker.so was re-compiled and a program using it was still running. The other reported cases (TextSearch, nc) don't seem to fit, though. So I'm leaving the ticket open. I've introduced a new panic()ing check in r30606 which will hopefully trigger earlier. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 20:50:34 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 03 May 2009 18:50:34 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.d1a54d0acb093de67fa789c457ca760c@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Replying to [comment:15 stippi]: {{{ KERN: usb uhci: process error KERN: usb uhci: host controller halted }}} Thank's, so it's the device that somehow messes up either the transfer length or the PID values. I'll cross reference other implementations and see how to best resolve such an error. In the best case we may be able to simply acknowledge the error and restart the schedule. Replying to [comment:15 stippi]: {{{ KERN: usb error control pipe 44: timeout waiting for queued request to complete KERN: usb error hub 43: error updating port status }}} > > The last two lines keep repeating every second or so. So it's a "process error", whatever that means. It means that an unexpected value for the PID (identifying the contents of the arriving or outgoing packet) or an invalid transfer length was received. It's most probably a device bug. That the lines repeat is expected. In the error case the schedule is stopped and interrupts are disabled for the controller, so no transfers will work anymore and instead simply time out. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 21:12:31 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 03 May 2009 19:12:31 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.c56bc1a45b09afbf9b501ff27752fe64@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): More additional info: The same behaviour applies to NV11 and NV15 (GF2MX and GF2Ti): they say they support VESA 1280x1024x16 and x8:, only the 8bit mode actually works. 16bit shutsoff the screen. The strange thing is that on these cards only a VGA connected screen can be used, no DVI. Is the displayed failsave modelist in the bootmanager actually correct or is it 'off by one'? (just ventilating my thoughts here..) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 21:56:08 2009 From: trac at haiku-os.org (stpere) Date: Sun, 03 May 2009 19:56:08 -0000 Subject: [Haiku-bugs] [Haiku] #2613: Calling Minimize() in Window constructor does not work. In-Reply-To: <038.a1a7dd0860f90f5052cf4bd111637b17@haiku-os.org> References: <038.a1a7dd0860f90f5052cf4bd111637b17@haiku-os.org> Message-ID: <047.914ed53c429b462d661f303a6ae8c2cf@haiku-os.org> #2613: Calling Minimize() in Window constructor does not work. ----------------------------+----------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by stpere): I tried to reproduce this bug but my impression is that it got fixed in r28938. Bruno, can you confirm if it's still bogus with your test case? I did put a Minimize call in StyledEdit Window constructor and it started minimized, as expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 21:57:54 2009 From: trac at haiku-os.org (bbjimmy) Date: Sun, 03 May 2009 19:57:54 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.10b1159ebc20941d8e0aeb7675744344@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by bbjimmy): r30607 VLC plays the sound files perfectly, but Media player, Sounds preferences, and playsound all distort the output. This is not a driver issue, but the media codec must be hosed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:05:45 2009 From: trac at haiku-os.org (axeld) Date: Sun, 03 May 2009 20:05:45 -0000 Subject: [Haiku-bugs] [Haiku] #3851: increased memory consumption since r30515 In-Reply-To: <040.75de7e678ec71445a6cc1db2d2e07fac@haiku-os.org> References: <040.75de7e678ec71445a6cc1db2d2e07fac@haiku-os.org> Message-ID: <049.0c9497bd46c7ee2bf46784e97162026d@haiku-os.org> #3851: increased memory consumption since r30515 ------------------------+--------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: This is just fine; the system preloads all executables now before usage, so it's expected that it requires more memory for this. Thanks for the note, though! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:07:55 2009 From: trac at haiku-os.org (axeld) Date: Sun, 03 May 2009 20:07:55 -0000 Subject: [Haiku-bugs] [Haiku] #2451: uname -a display BeOS instead of Haiku In-Reply-To: <042.1a123ffba494d4502d3668c9d558e578@haiku-os.org> References: <042.1a123ffba494d4502d3668c9d558e578@haiku-os.org> Message-ID: <051.d796faefc1618c1612458cd4070994d6@haiku-os.org> #2451: uname -a display BeOS instead of Haiku ------------------------+--------------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Completely agreed - but this also means we can close this ticket, I guess. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:10:13 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 03 May 2009 20:10:13 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX In-Reply-To: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> References: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> Message-ID: <050.5662444d88f5cba43ada7e8db8effd70@haiku-os.org> #3860: Mime type database for MDX --------------------------+------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by jonas.kirilla): Shinta, I forgot to mention you in the commit message. My apologies. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:11:15 2009 From: trac at haiku-os.org (axeld) Date: Sun, 03 May 2009 20:11:15 -0000 Subject: [Haiku-bugs] [Haiku] #3854: reindexed attributes do not persist across reboots. In-Reply-To: <041.48927e960c738044b72be859274d7054@haiku-os.org> References: <041.48927e960c738044b72be859274d7054@haiku-os.org> Message-ID: <050.1a41014a7412e301341323cfa37a1a95@haiku-os.org> #3854: reindexed attributes do not persist across reboots. ------------------------------+--------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => high * status: new => assigned * milestone: R1 => R1/alpha1 Comment: The actual problem is that the entry is removed from the index - if you reopen the query another time in the same session, the other entries will already be gone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:30:08 2009 From: trac at haiku-os.org (axeld) Date: Sun, 03 May 2009 20:30:08 -0000 Subject: [Haiku-bugs] [Haiku] #3854: reindexed attributes do not persist across reboots. In-Reply-To: <041.48927e960c738044b72be859274d7054@haiku-os.org> References: <041.48927e960c738044b72be859274d7054@haiku-os.org> Message-ID: <050.e5dd6fc3a625dc0117c9fd3d07a85d50@haiku-os.org> #3854: reindexed attributes do not persist across reboots. -------------------------------+-------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30616. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 3 22:52:11 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 03 May 2009 20:52:11 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.cadd7bf59ce2d0d66b757c6ca9d12903@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Replying to [comment:16 mmlr]: > It means that an unexpected value for the PID (identifying the contents of the arriving or outgoing packet) or an invalid transfer length was received. It's most probably a device bug. Actually it isn't. It must be something coming from the software side. The UHCI specs declare the process error as a "catastrophic failure", but I wouldn't quite go that far ;-). It still can only be either a wrong PID or max length, that gets set by us. I've reviewed the PIDs and there's not really anything that could go wrong. They are set in any case. Even if the wrong ones would be set that wouldn't trigger a process error but one of the other normal error cases. This leaves the max length which I reviewed as well and couldn't make out anything suspicious. But if at all it's the more likely candidate as it is the more complex of both and has a chance of being miscalculated or invalid. Of course it could also be a general memory corruption, but I'd say that's rather unlikely as it should affect more use cases. I can reproduce this error in one setup here, though only relatively randomly and will try tracking it down now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 00:14:12 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 03 May 2009 22:14:12 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac Message-ID: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- A disc I burned on my Mac appears to have major interpretation problems with our iso9660 driver. The actual contents of the disc look as follows: {{{ 05/03/2009 11:20 AM 17,313,824 Helmer_altMoviePoster.jpg 04/13/2009 03:01 PM 209,176,224 Helmer_altMoviePoster.psd 05/03/2009 11:08 AM 4,106,772 Helmer_MoviePoster.jpg 04/13/2009 03:02 PM 134,074,020 Helmer_MoviePoster.psd 4 File(s) 364,670,840 bytes 0 Dir(s) 0 bytes free }}} However, our iso9660 add-on claims this instead: {{{ total 591 dr-xr-xr-x 0 rene root 2048 May 3 16:47 . drwxrwxrwx 1 rene root 0 May 3 17:03 .. -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd }}} None of the files are usable. Syslog of that CD insertion: {{{ KERN: Media changed from /dev/disk/atapi/4/master/raw KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1 KERN: intel: ep_std_ops(0x2) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(8, 1: 0, 366448640, 2048) KERN: returned: -1 KERN: trying: file_systems/bfs/v1 KERN: returned: -1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: raw_command: KERN: returned: 0.699 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 39:45.55) KERN: returned: -2147483648 KERN: trying: file_systems/ext2/v1 KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(8, 0x93823ec0) KERN: found primary descriptor KERN: iso9660_primary_descriptor: KERN: volume descriptor type: 1 (primary) KERN: standard identifier: CD001 (valid) KERN: version: 1 KERN: identifier: 'PORTFOLIODISC1' KERN: size: 178780 KERN: set size: 1 KERN: sequence number: 1 KERN: logical block size: 2048 KERN: path table size: 10 KERN: set identifier: KERN: root directory record: KERN: length: 34 KERN: location: 41 KERN: data length: 2048 KERN: volume space: 1 KERN: iso9660_info::set_string(0x93823ec0 (''), 'PORTFOLIODISC1', 32) KERN: returned: 0.6 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/userlandfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 KERN: scanning with: partitioning_systems/session/v1 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1 KERN: intel: ep_std_ops(0x2) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(8, 6: 0, 366448640, 2048) KERN: returned: -1 KERN: trying: file_systems/bfs/v1 KERN: returned: -1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: returned: -1 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 39:45.55) KERN: returned: -2147483648 KERN: trying: file_systems/ext2/v1 KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(8, 0x811f9150) KERN: found primary descriptor KERN: iso9660_primary_descriptor: KERN: volume descriptor type: 1 (primary) KERN: standard identifier: CD001 (valid) KERN: version: 1 KERN: identifier: 'PORTFOLIODISC1' KERN: size: 178780 KERN: set size: 1 KERN: sequence number: 1 KERN: logical block size: 2048 KERN: path table size: 10 KERN: set identifier: KERN: root directory record: KERN: length: 34 KERN: location: 41 KERN: data length: 2048 KERN: volume space: 1 KERN: iso9660_info::set_string(0x811f9150 (''), 'PORTFOLIODISC1', 32) KERN: returned: 0.6 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/userlandfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 KERN: scanning with: file_systems/iso9660/v1 KERN: Media changed from /dev/disk/atapi/4/master/raw KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1 KERN: intel: ep_std_ops(0x2) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(8, 1: 0, 366448640, 2048) KERN: returned: -1 KERN: trying: file_systems/bfs/v1 KERN: returned: -1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: raw_command: KERN: returned: 0.699 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 39:45.55) KERN: returned: -2147483648 KERN: trying: file_systems/ext2/v1 KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(8, 0x811f91b0) KERN: found primary descriptor KERN: iso9660_primary_descriptor: KERN: volume descriptor type: 1 (primary) KERN: standard identifier: CD001 (valid) KERN: version: 1 KERN: identifier: 'PORTFOLIODISC1' KERN: size: 178780 KERN: set size: 1 KERN: sequence number: 1 KERN: logical block size: 2048 KERN: path table size: 10 KERN: set identifier: KERN: root directory record: KERN: length: 34 KERN: location: 41 KERN: data length: 2048 KERN: volume space: 1 KERN: iso9660_info::set_string(0x811f91b0 (''), 'PORTFOLIODISC1', 32) KERN: returned: 0.6 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/userlandfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 KERN: scanning with: partitioning_systems/session/v1 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) KERN: intel: ep_std_ops(0x1) KERN: trying: partitioning_systems/intel/extended/v1 KERN: returned: -1 KERN: intel: ep_std_ops(0x2) KERN: trying: partitioning_systems/intel/map/v1 KERN: intel: pm_identify_partition(8, 7: 0, 366448640, 2048) KERN: returned: -1 KERN: trying: file_systems/bfs/v1 KERN: returned: -1 KERN: trying: file_systems/devfs/v1 KERN: returned: -1 KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: returned: -1 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: raw_command: KERN: 01. 00:02.00 (length 39:45.55) KERN: returned: -2147483648 KERN: trying: file_systems/ext2/v1 KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(8, 0x811f9120) KERN: found primary descriptor KERN: iso9660_primary_descriptor: KERN: volume descriptor type: 1 (primary) KERN: standard identifier: CD001 (valid) KERN: version: 1 KERN: identifier: 'PORTFOLIODISC1' KERN: size: 178780 KERN: set size: 1 KERN: sequence number: 1 KERN: logical block size: 2048 KERN: path table size: 10 KERN: set identifier: KERN: root directory record: KERN: length: 34 KERN: location: 41 KERN: data length: 2048 KERN: volume space: 1 KERN: iso9660_info::set_string(0x811f9120 (''), 'PORTFOLIODISC1', 32) KERN: returned: 0.6 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/userlandfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 KERN: scanning with: file_systems/iso9660/v1 }}} Let me know if you need any other information, I can make these discs pretty much at will. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 00:27:59 2009 From: trac at haiku-os.org (zooey) Date: Sun, 03 May 2009 22:27:59 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input Message-ID: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- If you have StyledEdit and/or Mail open with a changed document and then select shutdown from the deskbar menu, the respective alerts asking whether or not to save the document appear, but only for a couple of seconds, then the system proceeds to shut down. Expected behaviour would be to wait until the user answers the dialog (possibly showing an additional hint that the application may be waiting for that answer). I've seen this in VMware with both gcc2 and gcc4 builds. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 00:34:09 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 03 May 2009 22:34:09 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.0804982d1a537517221af6d5d17ff8a4@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Description changed by anevilyak: Old description: > A disc I burned on my Mac appears to have major interpretation problems > with our iso9660 driver. The actual contents of the disc look as follows: > > {{{ > 05/03/2009 11:20 AM 17,313,824 Helmer_altMoviePoster.jpg > 04/13/2009 03:01 PM 209,176,224 Helmer_altMoviePoster.psd > 05/03/2009 11:08 AM 4,106,772 Helmer_MoviePoster.jpg > 04/13/2009 03:02 PM 134,074,020 Helmer_MoviePoster.psd > 4 File(s) 364,670,840 bytes > 0 Dir(s) 0 bytes free > }}} > > However, our iso9660 add-on claims this instead: > {{{ > total 591 > dr-xr-xr-x 0 rene root 2048 May 3 16:47 . > drwxrwxrwx 1 rene root 0 May 3 17:03 .. > -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg > -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg > -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd > -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd > -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg > -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg > -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd > -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd > }}} > > None of the files are usable. Syslog of that CD insertion: > {{{ > KERN: Media changed from /dev/disk/atapi/4/master/raw > KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) > KERN: intel: ep_std_ops(0x1) > KERN: trying: partitioning_systems/intel/extended/v1 > KERN: returned: -1 > KERN: intel: ep_std_ops(0x2) > KERN: trying: partitioning_systems/intel/map/v1 > KERN: intel: pm_identify_partition(8, 1: 0, 366448640, 2048) > KERN: returned: -1 > KERN: trying: file_systems/bfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/devfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/rootfs/v1 > KERN: returned: -1 > KERN: trying: partitioning_systems/session/v1 > KERN: raw_command: > KERN: returned: 0.699 > KERN: trying: file_systems/attribute_overlay/v1 > KERN: returned: -1 > KERN: trying: file_systems/cdda/v1 > KERN: raw_command: > KERN: 01. 00:02.00 (length 39:45.55) > KERN: returned: -2147483648 > KERN: trying: file_systems/ext2/v1 > KERN: returned: -2147483648 > KERN: trying: file_systems/fat/v1 > KERN: returned: -1 > KERN: trying: file_systems/iso9660/v1 > KERN: identify(8, 0x93823ec0) > KERN: found primary descriptor > KERN: iso9660_primary_descriptor: > KERN: volume descriptor type: 1 (primary) > KERN: standard identifier: CD001 (valid) > KERN: version: 1 > KERN: identifier: 'PORTFOLIODISC1' > KERN: size: 178780 > KERN: set size: 1 > KERN: sequence number: 1 > KERN: logical block size: 2048 > KERN: path table size: 10 > KERN: set identifier: > KERN: root directory record: > KERN: length: 34 > KERN: location: 41 > KERN: data length: 2048 > KERN: volume space: 1 > KERN: iso9660_info::set_string(0x93823ec0 (''), 'PORTFOLIODISC1', > 32) > KERN: returned: 0.6 > KERN: trying: file_systems/nfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/userlandfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/write_overlay/v1 > KERN: returned: -1 > KERN: scanning with: partitioning_systems/session/v1 > KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) > KERN: intel: ep_std_ops(0x1) > KERN: trying: partitioning_systems/intel/extended/v1 > KERN: returned: -1 > KERN: intel: ep_std_ops(0x2) > KERN: trying: partitioning_systems/intel/map/v1 > KERN: intel: pm_identify_partition(8, 6: 0, 366448640, 2048) > KERN: returned: -1 > KERN: trying: file_systems/bfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/devfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/rootfs/v1 > KERN: returned: -1 > KERN: trying: partitioning_systems/session/v1 > KERN: returned: -1 > KERN: trying: file_systems/attribute_overlay/v1 > KERN: returned: -1 > KERN: trying: file_systems/cdda/v1 > KERN: raw_command: > KERN: 01. 00:02.00 (length 39:45.55) > KERN: returned: -2147483648 > KERN: trying: file_systems/ext2/v1 > KERN: returned: -2147483648 > KERN: trying: file_systems/fat/v1 > KERN: returned: -1 > KERN: trying: file_systems/iso9660/v1 > KERN: identify(8, 0x811f9150) > KERN: found primary descriptor > KERN: iso9660_primary_descriptor: > KERN: volume descriptor type: 1 (primary) > KERN: standard identifier: CD001 (valid) > KERN: version: 1 > KERN: identifier: 'PORTFOLIODISC1' > KERN: size: 178780 > KERN: set size: 1 > KERN: sequence number: 1 > KERN: logical block size: 2048 > KERN: path table size: 10 > KERN: set identifier: > KERN: root directory record: > KERN: length: 34 > KERN: location: 41 > KERN: data length: 2048 > KERN: volume space: 1 > KERN: iso9660_info::set_string(0x811f9150 (''), 'PORTFOLIODISC1', > 32) > KERN: returned: 0.6 > KERN: trying: file_systems/nfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/userlandfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/write_overlay/v1 > KERN: returned: -1 > KERN: scanning with: file_systems/iso9660/v1 > KERN: Media changed from /dev/disk/atapi/4/master/raw > KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) > KERN: intel: ep_std_ops(0x1) > KERN: trying: partitioning_systems/intel/extended/v1 > KERN: returned: -1 > KERN: intel: ep_std_ops(0x2) > KERN: trying: partitioning_systems/intel/map/v1 > KERN: intel: pm_identify_partition(8, 1: 0, 366448640, 2048) > KERN: returned: -1 > KERN: trying: file_systems/bfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/devfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/rootfs/v1 > KERN: returned: -1 > KERN: trying: partitioning_systems/session/v1 > KERN: raw_command: > KERN: returned: 0.699 > KERN: trying: file_systems/attribute_overlay/v1 > KERN: returned: -1 > KERN: trying: file_systems/cdda/v1 > KERN: raw_command: > KERN: 01. 00:02.00 (length 39:45.55) > KERN: returned: -2147483648 > KERN: trying: file_systems/ext2/v1 > KERN: returned: -2147483648 > KERN: trying: file_systems/fat/v1 > KERN: returned: -1 > KERN: trying: file_systems/iso9660/v1 > KERN: identify(8, 0x811f91b0) > KERN: found primary descriptor > KERN: iso9660_primary_descriptor: > KERN: volume descriptor type: 1 (primary) > KERN: standard identifier: CD001 (valid) > KERN: version: 1 > KERN: identifier: 'PORTFOLIODISC1' > KERN: size: 178780 > KERN: set size: 1 > KERN: sequence number: 1 > KERN: logical block size: 2048 > KERN: path table size: 10 > KERN: set identifier: > KERN: root directory record: > KERN: length: 34 > KERN: location: 41 > KERN: data length: 2048 > KERN: volume space: 1 > KERN: iso9660_info::set_string(0x811f91b0 (''), 'PORTFOLIODISC1', > 32) > KERN: returned: 0.6 > KERN: trying: file_systems/nfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/userlandfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/write_overlay/v1 > KERN: returned: -1 > KERN: scanning with: partitioning_systems/session/v1 > KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) > KERN: intel: ep_std_ops(0x1) > KERN: trying: partitioning_systems/intel/extended/v1 > KERN: returned: -1 > KERN: intel: ep_std_ops(0x2) > KERN: trying: partitioning_systems/intel/map/v1 > KERN: intel: pm_identify_partition(8, 7: 0, 366448640, 2048) > KERN: returned: -1 > KERN: trying: file_systems/bfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/devfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/rootfs/v1 > KERN: returned: -1 > KERN: trying: partitioning_systems/session/v1 > KERN: returned: -1 > KERN: trying: file_systems/attribute_overlay/v1 > KERN: returned: -1 > KERN: trying: file_systems/cdda/v1 > KERN: raw_command: > KERN: 01. 00:02.00 (length 39:45.55) > KERN: returned: -2147483648 > KERN: trying: file_systems/ext2/v1 > KERN: returned: -2147483648 > KERN: trying: file_systems/fat/v1 > KERN: returned: -1 > KERN: trying: file_systems/iso9660/v1 > KERN: identify(8, 0x811f9120) > KERN: found primary descriptor > KERN: iso9660_primary_descriptor: > KERN: volume descriptor type: 1 (primary) > KERN: standard identifier: CD001 (valid) > KERN: version: 1 > KERN: identifier: 'PORTFOLIODISC1' > KERN: size: 178780 > KERN: set size: 1 > KERN: sequence number: 1 > KERN: logical block size: 2048 > KERN: path table size: 10 > KERN: set identifier: > KERN: root directory record: > KERN: length: 34 > KERN: location: 41 > KERN: data length: 2048 > KERN: volume space: 1 > KERN: iso9660_info::set_string(0x811f9120 (''), 'PORTFOLIODISC1', > 32) > KERN: returned: 0.6 > KERN: trying: file_systems/nfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/userlandfs/v1 > KERN: returned: -1 > KERN: trying: file_systems/write_overlay/v1 > KERN: returned: -1 > KERN: scanning with: file_systems/iso9660/v1 > }}} > > Let me know if you need any other information, I can make these discs > pretty much at will. New description: A disc I burned on my Mac appears to have major interpretation problems with our iso9660 driver. The actual contents of the disc look as follows: {{{ 05/03/2009 11:20 AM 17,313,824 Helmer_altMoviePoster.jpg 04/13/2009 03:01 PM 209,176,224 Helmer_altMoviePoster.psd 05/03/2009 11:08 AM 4,106,772 Helmer_MoviePoster.jpg 04/13/2009 03:02 PM 134,074,020 Helmer_MoviePoster.psd 4 File(s) 364,670,840 bytes 0 Dir(s) 0 bytes free }}} However, our iso9660 add-on claims this instead: {{{ total 591 dr-xr-xr-x 0 rene root 2048 May 3 16:47 . drwxrwxrwx 1 rene root 0 May 3 17:03 .. -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg -r--r--r-- 0 rene root 91095 May 3 11:08 Helmer_MoviePoster.jpg -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd -r--r--r-- 0 rene root 54130 Apr 13 15:02 Helmer_MoviePoster.psd -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg -r--r--r-- 0 rene root 98113 May 3 11:20 Helmer_altMoviePoster.jpg -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd -r--r--r-- 0 rene root 57832 Apr 13 15:01 Helmer_altMoviePoster.psd }}} None of the files are usable. Syslog of that CD insertion: {{{ Media changed from /dev/disk/atapi/4/master/raw KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) intel: ep_std_ops(0x1) trying: partitioning_systems/intel/extended/v1 returned: -1 intel: ep_std_ops(0x2) trying: partitioning_systems/intel/map/v1 intel: pm_identify_partition(8, 1: 0, 366448640, 2048) returned: -1 trying: file_systems/bfs/v1 returned: -1 trying: file_systems/devfs/v1 returned: -1 trying: file_systems/rootfs/v1 returned: -1 trying: partitioning_systems/session/v1 raw_command: returned: 0.699 trying: file_systems/attribute_overlay/v1 returned: -1 trying: file_systems/cdda/v1 raw_command: 01. 00:02.00 (length 39:45.55) returned: -2147483648 trying: file_systems/ext2/v1 returned: -2147483648 trying: file_systems/fat/v1 returned: -1 trying: file_systems/iso9660/v1 identify(8, 0x811f9130) found primary descriptor iso9660_primary_descriptor: volume descriptor type: 1 (primary) standard identifier: CD001 (valid) version: 1 identifier: 'PORTFOLIODISC1' size: 178780 set size: 1 sequence number: 1 logical block size: 2048 path table size: 10 set identifier: root directory record: length: 34 location: 41 data length: 2048 volume space: 1 iso9660_info::set_string(0x811f9130 (''), 'PORTFOLIODISC1', 32) returned: 0.6 trying: file_systems/nfs/v1 returned: -1 trying: file_systems/userlandfs/v1 returned: -1 trying: file_systems/write_overlay/v1 returned: -1 scanning with: partitioning_systems/session/v1 KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) intel: ep_std_ops(0x1) trying: partitioning_systems/intel/extended/v1 returned: -1 intel: ep_std_ops(0x2) trying: partitioning_systems/intel/map/v1 intel: pm_identify_partition(8, 10: 0, 366448640, 2048) returned: -1 trying: file_systems/bfs/v1 returned: -1 trying: file_systems/devfs/v1 returned: -1 trying: file_systems/rootfs/v1 returned: -1 trying: partitioning_systems/session/v1 returned: -1 trying: file_systems/attribute_overlay/v1 returned: -1 trying: file_systems/cdda/v1 raw_command: 01. 00:02.00 (length 39:45.55) returned: -2147483648 trying: file_systems/ext2/v1 returned: -2147483648 trying: file_systems/fat/v1 returned: -1 trying: file_systems/iso9660/v1 identify(8, 0x811f9120) found primary descriptor iso9660_primary_descriptor: volume descriptor type: 1 (primary) standard identifier: CD001 (valid) version: 1 identifier: 'PORTFOLIODISC1' size: 178780 set size: 1 sequence number: 1 logical block size: 2048 path table size: 10 set identifier: root directory record: length: 34 location: 41 data length: 2048 volume space: 1 iso9660_info::set_string(0x811f9120 (''), 'PORTFOLIODISC1', 32) returned: 0.6 trying: file_systems/nfs/v1 returned: -1 trying: file_systems/userlandfs/v1 returned: -1 trying: file_systems/write_overlay/v1 returned: -1 scanning with: file_systems/iso9660/v1 ISOMount - ENTER B_GET_PARTITION_INFO: ioctl returned error ISOMount: open device/file "/dev/disk/atapi/4/master/0" ISOMount: Is an ISO9660 volume, initting rec InitVolDesc - ENTER InitVolDesc - system id string is APPLE COMPUTER, INC., TYPE: 0002 InitVolDesc - volume id string is PORTFOLIODISC1 InitNode - ENTER, bufstart is 0x82e6b7a7, record length is 34 bytes InitNode - data start LBN is 41 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x82e6b7c8 InitVolDesc - volume set id string is InitVolDesc - volume pub id string is InitVolDesc - volume dataPreparer string is InitVolDesc - volume app id string is InitVolDesc - copyright is ISO9660: volume->blockSize = 2048 ISOMount: block size multiplier is 1 ISO9660: cache init: dev 9, max blocks 178780 ISO9660 Extensions: Microsoft Joliet Level 1 InitNode - ENTER, bufstart is 0x82e6b7a7, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x82e6b7c8 ISOMount - EXIT, returning 0x819c0800 Media changed from /dev/disk/atapi/4/master/raw KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/raw) intel: ep_std_ops(0x1) trying: partitioning_systems/intel/extended/v1 returned: -1 intel: ep_std_ops(0x2) trying: partitioning_systems/intel/map/v1 intel: pm_identify_partition(8, 1: 0, 366448640, 2048) returned: -1 trying: file_systems/bfs/v1 returned: -1 trying: file_systems/devfs/v1 returned: -1 trying: file_systems/rootfs/v1 returned: -1 trying: partitioning_systems/session/v1 raw_command: returned: 0.699 trying: file_systems/attribute_overlay/v1 returned: -1 trying: file_systems/cdda/v1 raw_command: 01. 00:02.00 (length 39:45.55) returned: -2147483648 trying: file_systems/ext2/v1 returned: -2147483648 trying: file_systems/fat/v1 returned: -1 trying: file_systems/iso9660/v1 identify(8, 0x8118cec0) found primary descriptor iso9660_primary_descriptor: volume descriptor type: 1 (primary) standard identifier: CD001 (valid) version: 1 identifier: 'PORTFOLIODISC1' size: 178780 set size: 1 sequence number: 1 logical block size: 2048 path table size: 10 set identifier: root directory record: length: 34 location: 41 data length: 2048 volume space: 1 iso9660_info::set_string(0x8118cec0 (''), 'PORTFOLIODISC1', 32) returned: 0.6 trying: file_systems/nfs/v1 returned: -1 trying: file_systems/userlandfs/v1 returned: -1 trying: file_systems/write_overlay/v1 returned: -1 scanning with: partitioning_systems/session/v1 KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/4/master/0) intel: ep_std_ops(0x1) trying: partitioning_systems/intel/extended/v1 returned: -1 intel: ep_std_ops(0x2) trying: partitioning_systems/intel/map/v1 intel: pm_identify_partition(8, 11: 0, 366448640, 2048) returned: -1 trying: file_systems/bfs/v1 returned: -1 trying: file_systems/devfs/v1 returned: -1 trying: file_systems/rootfs/v1 returned: -1 trying: partitioning_systems/session/v1 returned: -1 trying: file_systems/attribute_overlay/v1 returned: -1 trying: file_systems/cdda/v1 raw_command: 01. 00:02.00 (length 39:45.55) returned: -2147483648 trying: file_systems/ext2/v1 returned: -2147483648 trying: file_systems/fat/v1 returned: -1 trying: file_systems/iso9660/v1 identify(8, 0x8118ceb0) found primary descriptor iso9660_primary_descriptor: volume descriptor type: 1 (primary) standard identifier: CD001 (valid) version: 1 identifier: 'PORTFOLIODISC1' size: 178780 set size: 1 sequence number: 1 logical block size: 2048 path table size: 10 set identifier: root directory record: length: 34 location: 41 data length: 2048 volume space: 1 iso9660_info::set_string(0x8118ceb0 (''), 'PORTFOLIODISC1', 32) returned: 0.6 trying: file_systems/nfs/v1 returned: -1 trying: file_systems/userlandfs/v1 returned: -1 trying: file_systems/write_overlay/v1 returned: -1 scanning with: file_systems/iso9660/v1 ISOMount - ENTER B_GET_PARTITION_INFO: ioctl returned error ISOMount: open device/file "/dev/disk/atapi/4/master/0" ISOMount: Is an ISO9660 volume, initting rec InitVolDesc - ENTER InitVolDesc - system id string is APPLE COMPUTER, INC., TYPE: 0002 InitVolDesc - volume id string is PORTFOLIODISC1 InitNode - ENTER, bufstart is 0x82e6b7a7, record length is 34 bytes InitNode - data start LBN is 41 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x82e6b7c8 InitVolDesc - volume set id string is InitVolDesc - volume pub id string is InitVolDesc - volume dataPreparer string is InitVolDesc - volume app id string is InitVolDesc - copyright is ISO9660: volume->blockSize = 2048 ISOMount: block size multiplier is 1 ISO9660: cache init: dev 9, max blocks 178780 ISO9660 Extensions: Microsoft Joliet Level 1 InitNode - ENTER, bufstart is 0x82e6b7a7, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x82e6b7c8 ISOMount - EXIT, returning 0x819c0800 }}} Let me know if you need any other information, I can make these discs pretty much at will. -- updated log with TRACE_ISO9660 enabled. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 00:36:36 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 03 May 2009 22:36:36 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.80fa5924629496dbfc4489ba2e273eba@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Also, trace log from when running the ls -la that resulted in the above output: {{{ InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffc5d, record length is 176 bytes InitNode - data start LBN is 446 InitNode - data length is 17313824 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffcb0 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffd0d, record length is 176 bytes InitNode - data start LBN is 111086 InitNode - data length is 57832 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffd60 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffdbd, record length is 176 bytes InitNode - data start LBN is 8949 InitNode - data length is 209176224 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffe10 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. ISOReadDirEnt - success, name is ., block 44, pos 0, inode id 47244640256 ISOReadDirEnt - EXIT, result is No error, vnid is 47244640256 ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 ISOReadDirEnt - success, name is .., block 44, pos 226, inode id 47244640482 ISOReadDirEnt - EXIT, result is No error, vnid is 47244640482 ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_MoviePoster.jpg, block 44, pos 260, inode id 47244640516 ISOReadDirEnt - EXIT, result is No error, vnid is 47244640516 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_MoviePoster.jpg, block 44, pos 430, inode id 47244640686 ISOReadDirEnt - EXIT, result is No error, vnid is 47244640686 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_MoviePoster.psd, block 44, pos 600, inode id 47244640856 ISOReadDirEnt - EXIT, result is No error, vnid is 47244640856 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_MoviePoster.psd, block 44, pos 770, inode id 47244641026 ISOReadDirEnt - EXIT, result is No error, vnid is 47244641026 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_altMoviePoster.jpg, block 44, pos 940, inode id 47244641196 ISOReadDirEnt - EXIT, result is No error, vnid is 47244641196 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffc5d, record length is 176 bytes InitNode - data start LBN is 446 InitNode - data length is 17313824 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffcb0 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_altMoviePoster.jpg, block 44, pos 1116, inode id 47244641372 ISOReadDirEnt - EXIT, result is No error, vnid is 47244641372 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffd0d, record length is 176 bytes InitNode - data start LBN is 111086 InitNode - data length is 57832 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffd60 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_altMoviePoster.psd, block 44, pos 1292, inode id 47244641548 ISOReadDirEnt - EXIT, result is No error, vnid is 47244641548 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffc5d, record length is 176 bytes InitNode - data start LBN is 446 InitNode - data length is 17313824 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffcb0 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffd0d, record length is 176 bytes InitNode - data start LBN is 111086 InitNode - data length is 57832 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffd60 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER InitNode - ENTER, bufstart is 0x9eeffdbd, record length is 176 bytes InitNode - data start LBN is 8949 InitNode - data length is 209176224 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffe10 RR: 41, 41, end of extensions. ISOReadDirEnt - success, name is Helmer_altMoviePoster.psd, block 44, pos 1468, inode id 47244641724 ISOReadDirEnt - EXIT, result is No error, vnid is 47244641724 InitNode - ENTER, bufstart is 0x9eeff801, record length is 226 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: . RR: Start of extensions at 0x9eeff822 RR: 53, 50, end of extensions. InitNode - ENTER, bufstart is 0x9eeff8e3, record length is 34 bytes InitNode - data start LBN is 44 InitNode - data length is 2048 InitNode - flags are 2 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 1 DirRec ID String is: .. RR: Start of extensions at 0x9eeff904 InitNode - ENTER, bufstart is 0x9eeff905, record length is 170 bytes InitNode - data start LBN is 113121 InitNode - data length is 91095 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff952 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeff9af, record length is 170 bytes InitNode - data start LBN is 111115 InitNode - data length is 4106772 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.jpg RR: Start of extensions at 0x9eeff9fc RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffa59, record length is 170 bytes InitNode - data start LBN is 178632 InitNode - data length is 54130 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffaa6 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffb03, record length is 170 bytes InitNode - data start LBN is 113166 InitNode - data length is 134074020 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 44 DirRec ID String is: Helmer_MoviePoster.psd RR: Start of extensions at 0x9eeffb50 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffbad, record length is 176 bytes InitNode - data start LBN is 8901 InitNode - data length is 98113 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffc00 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffc5d, record length is 176 bytes InitNode - data start LBN is 446 InitNode - data length is 17313824 InitNode - flags are 0 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.jpg RR: Start of extensions at 0x9eeffcb0 RR: 41, 41, end of extensions. InitNode - ENTER, bufstart is 0x9eeffd0d, record length is 176 bytes InitNode - data start LBN is 111086 InitNode - data length is 57832 InitNode - flags are 4 InitNode - fileUnitSize is 0 InitNode - interleave gap size = 0 InitNode - volume seq num is 16777217 InitNode - file id length is 50 DirRec ID String is: Helmer_altMoviePoster.psd RR: Start of extensions at 0x9eeffd60 RR: 41, 41, end of extensions. ISOReadDirEnt - ENTER ISOReadDirEnt - EXIT, result is No such file or directory, vnid is 47244641724 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 01:02:17 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 03 May 2009 23:02:17 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.0839cdce6858ae3458c63ae1c5b2baca@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by jonas.kirilla): I?ve seen this too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 01:02:36 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 03 May 2009 23:02:36 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.1392338334a2156da3a4b90e942625c7@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Another note of interest: FreeBSD lists the entries twice also, but with a slight name difference: {{{ -r-xr-xr-x 1 root wheel 91095 May 3 11:08 =Helmer_MoviePoster.jpg -r-xr-xr-x 1 root wheel 54130 Apr 13 15:02 =Helmer_MoviePoster.psd -r-xr-xr-x 1 root wheel 98113 May 3 11:20 =Helmer_altMoviePoster.jpg -r-xr-xr-x 1 root wheel 57832 Apr 13 15:01 =Helmer_altMoviePoster.psd -r-xr-xr-x 1 root wheel 4106772 May 3 11:08 Helmer_MoviePoster.jpg -r-xr-xr-x 1 root wheel 134074020 Apr 13 15:02 Helmer_MoviePoster.psd -r-xr-xr-x 1 root wheel 17313824 May 3 11:20 Helmer_altMoviePoster.jpg -r-xr-xr-x 1 root wheel 209176224 Apr 13 15:01 Helmer_altMoviePoster.psd }}} Note also that the sizes on the =-prefixed names match the ones reported on Haiku. The second set are correct though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 01:11:37 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 03 May 2009 23:11:37 -0000 Subject: [Haiku-bugs] [Haiku] #3863: Canceling shutdown blames application Message-ID: <048.35b694c21fefeda8bc767842f01818d0@haiku-os.org> #3863: Canceling shutdown blames application -------------------------------+-------------------------------------------- Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- If a user cancels shutdown early when waiting for an application to quit (say Bezilla) before the kill button appears, the resulting info alert credits the application with canceling the shutdown, whereas it was actually me, the user, who canceled the shutdown. It might seem like a good idea to discern between the two: - application cancels shutdown - user cancels shutdown When the user cancels shutdown there is no need to inform the user. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 02:43:13 2009 From: trac at haiku-os.org (pedroeloy) Date: Mon, 04 May 2009 00:43:13 -0000 Subject: [Haiku-bugs] [Haiku] #3477: Add new deviceid for GeForce Go 7300 In-Reply-To: <044.2d133d60ef9eff438765db5464c809ce@haiku-os.org> References: <044.2d133d60ef9eff438765db5464c809ce@haiku-os.org> Message-ID: <053.4194a554d4d30d7755537b2e79cdc3c9@haiku-os.org> #3477: Add new deviceid for GeForce Go 7300 -------------------------------------+-------------------------------------- Reporter: pedroeloy | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by pedroeloy): Great stuff! Since r30598 that the nvidia driver works with my native 1280x800 resolution. This ticket can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 03:20:33 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 04 May 2009 01:20:33 -0000 Subject: [Haiku-bugs] [Haiku] #3477: Add new deviceid for GeForce Go 7300 In-Reply-To: <044.2d133d60ef9eff438765db5464c809ce@haiku-os.org> References: <044.2d133d60ef9eff438765db5464c809ce@haiku-os.org> Message-ID: <053.a60771c43ef9ff2fa4d2edbe2996cd40@haiku-os.org> #3477: Add new deviceid for GeForce Go 7300 --------------------------------------+------------------------------------- Reporter: pedroeloy | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: Thanks for the update! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 03:31:36 2009 From: trac at haiku-os.org (bbjimmy) Date: Mon, 04 May 2009 01:31:36 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.c499f05e6f72846572a457d1a7f89c3d@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by bbjimmy): I changed to the startup and beep sounds from Windows XP and they work pertectly. The codec is not working properly for all .wav files. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 03:57:15 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 04 May 2009 01:57:15 -0000 Subject: [Haiku-bugs] [Haiku] #3864: inconsistent behavior : modifying directories in Terminal and Tracker Message-ID: <041.0fbc0d188f71832d31078533689d23b5@haiku-os.org> #3864: inconsistent behavior : modifying directories in Terminal and Tracker ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- I'm not sure if this is valid or not or Tracker is the correct component. Either way this is a bit odd. {{{ mkdir /development mkdir /development/haiku-source open /development use Tracer to create New Folder use Tracker to rename folder --> fail. }}} expected behavior: be able to rename that folder in Tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 05:48:08 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 03:48:08 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX In-Reply-To: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> References: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> Message-ID: <050.484133202d238c32086ee3d71e1002f0@haiku-os.org> #3860: Mime type database for MDX --------------------------+------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by shinta): * cc: shinta.0806@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 05:49:45 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 03:49:45 -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.bd674b23d264db1b0a5f8f7ed1938276@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 | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by shinta): * cc: shinta.0806@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 05:51:45 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 03:51:45 -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.f6980a6bd20cdd6f299b0cbb5f36925e@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 | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Comment(by shinta): Thanks for committing! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 06:26:00 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 04:26:00 -0000 Subject: [Haiku-bugs] [Haiku] #3860: Mime type database for MDX In-Reply-To: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> References: <041.66856f529af83a8162cd9c9fc83d9acc@haiku-os.org> Message-ID: <050.d0cfdb08d4f4144ba965b542b5b93bb7@haiku-os.org> #3860: Mime type database for MDX --------------------------+------------------------------------------------- Reporter: shinta | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by shinta): Thank you for committing at r30603! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 08:05:16 2009 From: trac at haiku-os.org (stippi) Date: Mon, 04 May 2009 06:05:16 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.51efc2ffea92454fe746254c519f6ba9@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): Awesome, thanks! It's like the last remaining "general" bug I keep hitting... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 08:12:37 2009 From: trac at haiku-os.org (stippi) Date: Mon, 04 May 2009 06:12:37 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.7fb27a13d153dd24d5cb9d672ae7de43@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by stippi): Sounds like the change to Deskbar, which toggles a boolean in the message to Registrar should be reverted, and instead the Registrar should be changed to not display the alert. Alertnatively, the Registrar shutdown API should be changed, so that "wait for user input" and "display confirmation alert" are two separate things. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 11:04:35 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 09:04:35 -0000 Subject: [Haiku-bugs] [Haiku] #3809: [Patch] Nicer output of additional modes from EDI In-Reply-To: <038.6ae3245aea86797e1baee3558e6f0677@haiku-os.org> References: <038.6ae3245aea86797e1baee3558e6f0677@haiku-os.org> Message-ID: <047.7519803207a166a64b0045cc5bd25b09@haiku-os.org> #3809: [Patch] Nicer output of additional modes from EDI -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Applied in r30622. If fixed the only style violation: there is always a space between the comment start and the comment; and since it refers to the line above, it should also be indented one tab. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 11:20:51 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 09:20:51 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab Message-ID: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- When BView "ParentView" has the child BTabView "ChildView" and "ChildView"'s selection of tab is changed, "ParentView"'s DrawAfterChildren() isn't called. Haiku: r30186[[BR]] [http://www2u.biglobe.ne.jp/~shinta/be/ SHINTA] (Bug No.22) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 11:21:04 2009 From: trac at haiku-os.org (shinta) Date: Mon, 04 May 2009 09:21:04 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab In-Reply-To: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> References: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> Message-ID: <050.9d41218b02977a905a3665f90f680eed@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by shinta): * cc: shinta.0806@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 11:24:18 2009 From: trac at haiku-os.org (stippi) Date: Mon, 04 May 2009 09:24:18 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab In-Reply-To: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> References: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> Message-ID: <050.9254785e91efbb63b6257bb9c846cc96@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): You are probably mixing up different things. DrawAfterChildren() is only called if your (parent) view has the flag "B_DRAW_ON_CHILDREN" set. BTabViews do not have this flag set, unless you manually added this flag yourself. If you have not done so, this bug is invalid. Have you added the flag? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 11:40:19 2009 From: trac at haiku-os.org (stippi) Date: Mon, 04 May 2009 09:40:19 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab In-Reply-To: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> References: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> Message-ID: <050.7ce4ae6ea12de6e9758a3f3633c5c4dc@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): I looked at the BeBook documentation for DrawAfterChildren() again. It is unfortunately not clear, but I am pretty sure I checked the BeOS behavior. The documentation hints that you want to use this for the rare case where you want to paint *on* children, but it doesn't mention the fact that this is only possible if you also have the B_DRAW_ON_CHILDREN flag set. Anyways, although the documentation may be misleading, Haiku should be 100% compatible with BeOS in this regard, I wrote a specific test application for this to cover various situations. DrawOnChildren() is never called if the flag is not set. It doesn't make any sense either, since if you don't paint *on* children, the drawing order is irrelevant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 13:51:16 2009 From: trac at haiku-os.org (pulkomandy) Date: Mon, 04 May 2009 11:51:16 -0000 Subject: [Haiku-bugs] [Haiku] #3866: Update the Locale preflet to use the layout manager Message-ID: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> #3866: Update the Locale preflet to use the layout manager -------------------------+-------------------------------------------------- Reporter: pulkomandy | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- This is a patch to the locale kit preflet to use the layout manager. The preflet still doesn't do anything useful, but this way we can get started to add the real things in there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 14:02:16 2009 From: trac at haiku-os.org (bga) Date: Mon, 04 May 2009 12:02:16 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.2069358e9411fe6c045674d000c5c487@haiku-os.org> #3849: Auvia 8235 distorted output sound ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by bga): * owner: korli => dlmcpaul Comment: This is a codec issue so assigning it to dlmcpaul. Are your sound files with problems small enough? If so, attach them to this bug or make them available somewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 14:02:33 2009 From: trac at haiku-os.org (bga) Date: Mon, 04 May 2009 12:02:33 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Auvia 8235 distorted output sound In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.e5ef77d5559b0169fd4e94967511e4b3@haiku-os.org> #3849: Auvia 8235 distorted output sound ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by bga): * component: Drivers/Audio => Audio & Video/Codecs -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 14:05:24 2009 From: trac at haiku-os.org (bga) Date: Mon, 04 May 2009 12:05:24 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. (was: Auvia 8235 distorted output sound) In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.f8312cb5458eff15a0c0ee268fd63e11@haiku-os.org> #3849: Audio files with distorted sound. ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 14:54:01 2009 From: trac at haiku-os.org (brunobratwurst) Date: Mon, 04 May 2009 12:54:01 -0000 Subject: [Haiku-bugs] [Haiku] #3867: intel hd audio driver (hda) using 100% of CPU 0 power. Message-ID: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> #3867: intel hd audio driver (hda) using 100% of CPU 0 power. ----------------------------+----------------------------------------------- Reporter: brunobratwurst | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------+----------------------------------------------- Haiku 30.April 2009 after moving the hda driver to the desktop and rebooting, I am able to use USB-Mouse and USB-Pendrive. Also the power/speed of the two processors are normal. The sound is working though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 14:58:13 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 12:58:13 -0000 Subject: [Haiku-bugs] [Haiku] #3867: intel hd audio driver (hda) using 100% of CPU 0 power. In-Reply-To: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> References: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> Message-ID: <058.5d21e48fbe95ef3c9d988118ea310d0e@haiku-os.org> #3867: intel hd audio driver (hda) using 100% of CPU 0 power. -------------------------------+-------------------------------------------- Reporter: brunobratwurst | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------+-------------------------------------------- Changes (by anevilyak): * owner: marcusoverhagen => axeld * component: Audio & Video => Drivers/Audio/HDA -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 15:42:30 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 13:42:30 -0000 Subject: [Haiku-bugs] [Haiku] #3867: intel hd audio driver (hda) using 100% of CPU 0 power. In-Reply-To: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> References: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> Message-ID: <058.9305e0d4fa327254c068e418573e94ee@haiku-os.org> #3867: intel hd audio driver (hda) using 100% of CPU 0 power. --------------------------------+------------------------------------------- Reporter: brunobratwurst | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: You must not install OpenSound and the hda driver at the same time, if hda is actually used. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 15:45:04 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 13:45:04 -0000 Subject: [Haiku-bugs] [Haiku] #3866: Update the Locale preflet to use the layout manager In-Reply-To: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> References: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> Message-ID: <054.f64d634da3e85c706f6652172b815a3e@haiku-os.org> #3866: Update the Locale preflet to use the layout manager -------------------------+-------------------------------------------------- Reporter: pulkomandy | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by axeld): Can you please use the GSoC mailing list for GSoC related patches instead? This will prevent the bug tracker from being flooded. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 15:47:24 2009 From: trac at haiku-os.org (zooey) Date: Mon, 04 May 2009 13:47:24 -0000 Subject: [Haiku-bugs] [Haiku] #3866: Update the Locale preflet to use the layout manager In-Reply-To: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> References: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> Message-ID: <054.60aac3b9304408620c9e21b84e9b693f@haiku-os.org> #3866: Update the Locale preflet to use the layout manager -------------------------+-------------------------------------------------- Reporter: pulkomandy | Owner: zooey Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by zooey): * owner: axeld => zooey * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:09:39 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 04 May 2009 14:09:39 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot Message-ID: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- My laptop hangs on shutdown/reboot, if acpi is not enabled. The last thing I see on screen is "Waiting for other processes to quit", then it hangs there. No "reboot now". With ACPI Enabled, instead, it displays the "reboot now" button (it should shutdown or reboot automatically, but this should be a different bug, I guess). This started happening only since some time (a month or so). The laptop is a Fujitsu Siemens amilo LI2735, centrino based. r30622. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:15:48 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 04 May 2009 14:15:48 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.1c9ef0120a0859eebdcbabd7b25ff8a4@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by michael.weirauch): Can confirm this. Happened yesterday with ACPI enabled. Can't recall if it always happens as my system usually freezes during operation and I regularly don't restart ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:24:57 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 14:24:57 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.fdfe92f9dc756c4aa8305552d2669b1d@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by axeld): The problematic change should be the one from Olivier which kills all apps before rebooting. Obviously, there is one (or more) components in your system that doesn't like to be freed. Can you remove drivers to find the candidate? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:26:27 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 04 May 2009 14:26:27 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.1b673b1bbbd739aff00b2377c77aef93@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by jackburton): Replying to [comment:2 axeld]: > The problematic change should be the one from Olivier which kills all apps before rebooting. Obviously, there is one (or more) components in your system that doesn't like to be freed. Yeah, that's what I was thinking, too. It's weird it doesn't happen with ACPI enabled, though. > Can you remove drivers to find the candidate? Yes, of course. Will do that this evening. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:33:50 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 04 May 2009 14:33:50 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.88d8239dd90db8c8d713691af2109d12@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by michael.weirauch): Oops, misread this... ("'''not''' enabled) Will retest. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:34:25 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 04 May 2009 14:34:25 -0000 Subject: [Haiku-bugs] [Haiku] #2803: System freezed with network cable attached, with rtl81xx driver In-Reply-To: <045.294eedd8af1d53aef24f97b4b156681f@haiku-os.org> References: <045.294eedd8af1d53aef24f97b4b156681f@haiku-os.org> Message-ID: <054.bb160cd9ded8831714b30fe39d646888@haiku-os.org> #2803: System freezed with network cable attached, with rtl81xx driver ------------------------------+--------------------------------------------- Reporter: jackburton | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by jackburton): * status: new => closed * resolution: => fixed Comment: I was able to test this and doesn't seem to happen anymore. I think the winning change was introduced by Michael Lotz in r29242. Closing. Should we close #2084 as well, since from the comment there it appears to have been fixed ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 16:41:27 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 14:41:27 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.02dec1c1586fb62a87932fce556fe182@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Changes (by anevilyak): * owner: anevilyak => jackburton * status: assigned => new Comment: Don't suppose you have any idea on this one Stefano? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 19:14:57 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 04 May 2009 17:14:57 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.ebd66f4a7b3fa2237e5222ed70b456eb@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by michael.weirauch): False alarm, though my initial comment still applies that I had the hang described with ACPI enabled. Perhaps accidentially. Just tested: * with ACPI: reboot fine * w/o ACPI: reboot fine Sorry for disrupting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:18:22 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 18:18:22 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.8c85ed392ce872b3edee5c078c250f8a@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): Would it be possible to upload a small ISO somewhere? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:21:00 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 18:21:00 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.07b6b4b9d9d8c45777bcc10bff82bc20@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Will try and see how small a disc I can replicate that problem with, as you can see the current one is 300MB of image data so it wouldn't really compress well. If I can make a small one of just the jpegs with the same issue after work, I'll put it on Vision's sourceforge page and post the link here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:35:30 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 04 May 2009 18:35:30 -0000 Subject: [Haiku-bugs] [Haiku] #3850: don't set non-existing VESA modes? In-Reply-To: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> References: <042.bdab496ae021bc7cbc7868e9b8635c86@haiku-os.org> Message-ID: <051.52412c22be40e2e29d1b4f07bf4fab03@haiku-os.org> #3850: don't set non-existing VESA modes? -----------------------+---------------------------------------------------- Reporter: rudolfc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by rudolfc): Hi, I could get my hands on a NV25 (GF4Ti 4600). It's got the same problem: 1280x1024x32 only works on DVI on the DVI capable port, but not on analog VGA on the same port. 16bit mode works though. On the VGA-only port 32bit mode works OK as well. 32bit mode also fails if two screens are connected.. and it doesn't matter if the DVI port one is a DVI or VGA version. Looks like 32bit VESA mode (at least 1280x1024) is a troublesome one for nVidia cards?!? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:41:41 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 04 May 2009 18:41:41 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.e2653c0af5ba87faae5494592ff6c4fb@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi! Well, that's good news indeed! Meanwhile I am implementing DDC/EDID support for the driver, which requires a lot of card-testing over here. The first thing I'll activate in the driver is detecting all screen's aspect ratio so we can disable the force_ws setting again by default. If a user connects only WS screens before boot then WS-modes will automatically be enabled. If that's in place you don't need to manually tweak the settings file anymore. Until that time this tweak remains needed. I'll let you know when the driver is 'fixed'. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:43:32 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 04 May 2009 18:43:32 -0000 Subject: [Haiku-bugs] [Haiku] #2641: [nvidia] Video problems In-Reply-To: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> References: <041.5e66e5d31b4e574ab0cd37fd18661280@haiku-os.org> Message-ID: <050.a0b3846ed23f1475d381a1a2b2623f64@haiku-os.org> #2641: [nvidia] Video problems -------------------------------------+-------------------------------------- Reporter: VinDuv | Owner: rudolfc Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by rudolfc): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 20:46:01 2009 From: trac at haiku-os.org (rudolfc) Date: Mon, 04 May 2009 18:46:01 -0000 Subject: [Haiku-bugs] [Haiku] #1696: Wrong display resolution on first boot with nvidia graphic cards In-Reply-To: <041.6387ba58e5f141cd904041526245eaa4@haiku-os.org> References: <041.6387ba58e5f141cd904041526245eaa4@haiku-os.org> Message-ID: <050.bd4bd000345d1b955e656878ce724f89@haiku-os.org> #1696: Wrong display resolution on first boot with nvidia graphic cards -------------------------------------+-------------------------------------- Reporter: ekdahl | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): implementing DDC/EDID is underway. I'm now dumping EDID data into the driver's logfile, and I am collecting data from testing numerous cards.. I'll keep you posted. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:33:48 2009 From: trac at haiku-os.org (diver) Date: Mon, 04 May 2009 19:33:48 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.70997c12548b3ddde9a80905a4045243@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857 | ---------------------------+------------------------------------------------ Comment(by diver): Same here on my eeepc 900. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:35:39 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 04 May 2009 19:35:39 -0000 Subject: [Haiku-bugs] [Haiku] #3869: Error with booting Haiku ISO: PANIC: page faults, but interrupt were disabled. Touching address... Message-ID: <041.3f0082794bc45737498ff370e3f8c812@haiku-os.org> #3869: Error with booting Haiku ISO: PANIC: page faults, but interrupt were disabled. Touching address... -----------------------------------+---------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------------------+---------------------------------------- Haiku CD ISO r30626 and I have the same with cue image. [http://dev.haiku-os.org/attachment/ticket/3260/listdev-mypc.txt/ listdev] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:37:47 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 19:37:47 -0000 Subject: [Haiku-bugs] [Haiku] #3869: Error with booting Haiku ISO: PANIC: page faults, but interrupt were disabled. Touching address... In-Reply-To: <041.3f0082794bc45737498ff370e3f8c812@haiku-os.org> References: <041.3f0082794bc45737498ff370e3f8c812@haiku-os.org> Message-ID: <050.f7e5ae60b8ca207a06f50aecc0687d3a@haiku-os.org> #3869: Error with booting Haiku ISO: PANIC: page faults, but interrupt were disabled. Touching address... ------------------------------------+--------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1 development Resolution: duplicate | Blockedby: 3847 Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate * blockedby: => 3847 Comment: Duplicate of ticket #3847. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:39:47 2009 From: trac at haiku-os.org (brunobratwurst) Date: Mon, 04 May 2009 19:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #3867: intel hd audio driver (hda) using 100% of CPU 0 power. In-Reply-To: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> References: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> Message-ID: <058.ec8f8bdfa21b2a422b2d441e28b0915e@haiku-os.org> #3867: intel hd audio driver (hda) using 100% of CPU 0 power. --------------------------------+------------------------------------------- Reporter: brunobratwurst | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by brunobratwurst): I had the problem before I installed OpenSound. I think I sent the wrong syslog, then. Without moving the hda driver to the desktop the usb-devices will not work. I will try to do some more test tomorrow. Thx anyway for looking into this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:40:48 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 04 May 2009 19:40:48 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.0406a8aa985e52ef14eb42a8f6f17e24@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857, 3869 | ---------------------------+------------------------------------------------ Changes (by Hubert): * cc: HubertNG@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:53:54 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 19:53:54 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.0c4e83c530cd79ef7a4f36ddd8d900c2@haiku-os.org> #3752: CharacterMap Window is way too big. ----------------------------------------+----------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30629. The problem mentioned by Jonas is an app_server problem and should be tracked in a new ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 21:58:40 2009 From: trac at haiku-os.org (miltoncsl) Date: Mon, 04 May 2009 19:58:40 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.089f52ddaef48f9e79adf90b1ade32e7@haiku-os.org> #3847: Boot Fail ---------------------------+------------------------------------------------ Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857, 3869 | ---------------------------+------------------------------------------------ Comment(by miltoncsl): Hi, I have other notebook with the follow config: Processor: Celeron M430 1.73 GHz Cache: 1024 KB Memory: 256 MB HD: 40 GB 00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.5 PIC: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller 00:00.6 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device 00:00.7 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge 00:02.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) 00:03.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) 00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge 00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c) 00:13.0 PCI bridge: VIA Technologies, Inc. VT8237A Host Bridge 00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) 06:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) 07:04.0 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller 07:04.1 SD Host controller: ENE Technology Inc ENE PCI SmartMedia / xD Card Reader Controller 07:04.3 FLASH memory: ENE Technology Inc ENE PCI Secure Digital / MMC Card Reader Controller And show similar error (attached photo)! This error arose in r30475! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:17:56 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Mon, 04 May 2009 20:17:56 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.35163125217069a5066e954d03c1b3c0@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by jonas.kirilla): I tried toggling that boolean back. The confirmation alert is back of course, but StyledEdit and Mail still can?t successfully halt the reboot process even though their save/cancel/dont save dialogs do show up. But Pe is able to halt the shutdown, so it could be that StyledEdit and Mail are not doing things right. I had a brief look at StyledEdit but didn?t see anything obviously wrong. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:18:49 2009 From: trac at haiku-os.org (bbjimmy) Date: Mon, 04 May 2009 20:18:49 -0000 Subject: [Haiku-bugs] [Haiku] #3870: cd rom build requires mkisofs Message-ID: <042.b941729ea5578ecaeb9ec80704a36963@haiku-os.org> #3870: cd rom build requires mkisofs --------------------------+------------------------------------------------- Reporter: bbjimmy | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- r30614 To do a "jam -q haiku-cd" from within haiku, one needs to add mkisofs to the host system. mkisofs is not included in the optional packages. This needs to be included if we are relying on the file to build a cd iso file. Haiku should be self hosting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:21:43 2009 From: trac at haiku-os.org (jackburton) Date: Mon, 04 May 2009 20:21:43 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.a2d72ef2aa76494f67598cfaf4a4eb11@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by jackburton): Well, from a first look, when clicking on the item with the mouse, the code path which triggers the call to BMenuItem::Invoke() is inside MenuBar.cpp (lines 642 - 650): {{{ if (window->Lock()) { if (fSelected != NULL) _SelectItem(NULL); if (fChosenItem != NULL) fChosenItem->Invoke(); _RestoreFocus(); window->Unlock(); } }}} while when using the keyboard, the code path is completely different, and doesn't lock the looper {{{ BMenu::_InvokeItem(BMenuItem *item, bool now) { if (!item->IsEnabled()) return; // Do the "selected" animation // TODO: Doesn't work. This is supposed to highlight // and dehighlight the item, works on beos but not on haiku. if (!item->Submenu() && LockLooper()) { snooze(50000); item->Select(true); Sync(); snooze(50000); item->Select(false); Sync(); snooze(50000); item->Select(true); Sync(); snooze(50000); item->Select(false); Sync(); UnlockLooper(); } item->Invoke(); } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:27:02 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 20:27:02 -0000 Subject: [Haiku-bugs] [Haiku] #3867: intel hd audio driver (hda) using 100% of CPU 0 power. In-Reply-To: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> References: <049.cd3751ab3d8464a3ebd5b8bac08b5399@haiku-os.org> Message-ID: <058.9cd252016feb55f025aa836e7d4c0212@haiku-os.org> #3867: intel hd audio driver (hda) using 100% of CPU 0 power. --------------------------------+------------------------------------------- Reporter: brunobratwurst | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Audio/HDA | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Comment(by axeld): If the problem persists with only the HDA driver installed, please just reopen this bug with an updated syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:30:03 2009 From: trac at haiku-os.org (axeld) Date: Mon, 04 May 2009 20:30:03 -0000 Subject: [Haiku-bugs] [Haiku] #3864: rootfs renaming does not work (was: inconsistent behavior : modifying directories in Terminal and Tracker) In-Reply-To: <041.0fbc0d188f71832d31078533689d23b5@haiku-os.org> References: <041.0fbc0d188f71832d31078533689d23b5@haiku-os.org> Message-ID: <050.1a792c54232d7e32ab73ef60ad0d0a1c@haiku-os.org> #3864: rootfs renaming does not work ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * component: Applications/Tracker => System/Kernel Comment: First of all, the folders at '/' are within rootfs - you won't be able to create any files there, rootfs only supports links and directories. Second of all, it seems like rootfs currently does not support renaming correctly. You could also try to rename the file from the shell, it will fail in the same way; there is no inconsistency at all. I've changed the ticket summary to reflect the actual problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:33:42 2009 From: trac at haiku-os.org (bbjimmy) Date: Mon, 04 May 2009 20:33:42 -0000 Subject: [Haiku-bugs] [Haiku] #3871: Haiku Live CD does not boot Message-ID: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> #3871: Haiku Live CD does not boot ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ r30614 jam-q haiku-cd PANIC: page fault, but interrupts were disabled. Touching address 0xdeadbf47 from eip 0x000402be Welcome to Kernel Debugging Land... Thread 29 "sh" running on CPU0 kdebug> -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:39:00 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 20:39:00 -0000 Subject: [Haiku-bugs] [Haiku] #3871: Haiku Live CD does not boot In-Reply-To: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> References: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> Message-ID: <051.df87b20ff35a5c8a21ce9a4d02446d91@haiku-os.org> #3871: Haiku Live CD does not boot ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3847 Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate * blockedby: => 3847 Comment: Duplicate of ticket #3847. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:39:23 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Mon, 04 May 2009 20:39:23 -0000 Subject: [Haiku-bugs] [Haiku] #3872: Bottom and left window borders of CharacterMap are dysfunctional Message-ID: <048.3dc9ea4bc1a5226277802c3deaabdca2@haiku-os.org> #3872: Bottom and left window borders of CharacterMap are dysfunctional --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- In r30626 the application CharacterMap opens up with a size way beyond screen bounds. Zooming it will shrink it to fit the screen, but the left and bottom window borders look like they?re missing. Trying to move the window by its bottom border, the area available for "gripping" the window frame appears to be only 1 pixel high. The bottom 1/3 of the window does not redraw when moved around/offscreen. See screenshots. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:45:01 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Mon, 04 May 2009 20:45:01 -0000 Subject: [Haiku-bugs] [Haiku] #3752: CharacterMap Window is way too big. In-Reply-To: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> References: <038.a84fb08ec9c0eccef1248e00ec13c82a@haiku-os.org> Message-ID: <047.b134108df0c41ac5a02a27f9e09e0166@haiku-os.org> #3752: CharacterMap Window is way too big. ----------------------------------------+----------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/CharacterMap | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------+----------------------------------- Comment(by jonas.kirilla): Replying to [comment:9 axeld]: > The problem mentioned by Jonas is an app_server problem and should be tracked in a new ticket. Ticket: #3872 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:45:36 2009 From: trac at haiku-os.org (bbjimmy) Date: Mon, 04 May 2009 20:45:36 -0000 Subject: [Haiku-bugs] [Haiku] #3871: Haiku Live CD does not boot In-Reply-To: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> References: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> Message-ID: <051.c269ff3443155356a563ea1d96e8f507@haiku-os.org> #3871: Haiku Live CD does not boot ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3847 Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by bbjimmy): Replying to [comment:1 anevilyak]: > Duplicate of ticket #3847. Interesting, it only gives me the issue booting from the cd or the cd iso image ... not the regular haiku.image file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:50:25 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 04 May 2009 20:50:25 -0000 Subject: [Haiku-bugs] [Haiku] #3871: Haiku Live CD does not boot In-Reply-To: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> References: <042.0ac4206ab30242f26bd9769b09a64858@haiku-os.org> Message-ID: <051.276f463559263c1a42b4683cac640f14@haiku-os.org> #3871: Haiku Live CD does not boot ----------------------------+----------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: duplicate | Blockedby: 3847 Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by anevilyak): It's probably timing sensitive...not everyone's seeing that particular boot panic either. In any case, in the future it'd be helpful to also include the output of "bt" at that kernel debugger prompt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 22:46:05 2009 From: trac at haiku-os.org (bbjimmy) Date: Mon, 04 May 2009 20:46:05 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.c82e9177afe5deaec8dd8fcba2a56e63@haiku-os.org> #3847: Boot Fail ------------------------------+--------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857, 3869, 3871 | ------------------------------+--------------------------------------------- Changes (by bbjimmy): * cc: black.belt.jimmy@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 4 23:05:55 2009 From: trac at haiku-os.org (philcostin) Date: Mon, 04 May 2009 21:05:55 -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.5a2ff937fa62bf682e8b1e9e0fe4c360@haiku-os.org> #2273: [runtime_loader] double clicking it leads to problems ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by philcostin): I can not reproduce this in r30545 - maybe it was related to #2197 (that's what made me try it just now) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 03:28:31 2009 From: trac at haiku-os.org (bga) Date: Tue, 05 May 2009 01:28:31 -0000 Subject: [Haiku-bugs] [Haiku] #2613: Calling Minimize() in Window constructor does not work. In-Reply-To: <038.a1a7dd0860f90f5052cf4bd111637b17@haiku-os.org> References: <038.a1a7dd0860f90f5052cf4bd111637b17@haiku-os.org> Message-ID: <047.ccaa18b6e3b48b23317e42c23568bf93@haiku-os.org> #2613: Calling Minimize() in Window constructor does not work. -----------------------------+---------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: Yes, this is fixed. Thanks for the heads up. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 04:51:32 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 May 2009 02:51:32 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.96fbcf360202275fb1079d330f1e564b@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Replying to [comment:4 axeld]: > Would it be possible to upload a small ISO somewhere? http://vision.sf.net/problem.iso.zip Should be 39765799 bytes and have an md5 hash of: 1f08bfaa60286079248e3f7dc575e783 . This one displays the same characteristics in FreeBSD as the listing in the ticket description, but also has the fun property that it causes Haiku's ISO9660 add-on to KDL with a page fault when you attempt to list it (mounting does work though). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 04:52:58 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 May 2009 02:52:58 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.8578dd1205495127c48cb782b68f2f2d@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Backtrace from above mentioned panic: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0x92700000, ip 0x807a3fea Welcome to Kernel Debugging Land... Thread 210 "add poses" running on CPU 0 kdebug> bt stack trace for thread 210 "add poses" kernel stack: 0x91ba8000 to 0x91bac000 user stack: 0x781c7000 to 0x78207000 frame caller :function + offset 0 91bab910 (+ 48) 8006584d :invoke_debugger_command + 0x00f5 1 91bab940 (+ 64) 8006563d invoke_pipe_segment(debugger_command_pipe*: 0x80136b20, int32: 0, 0x0 "") + 0x0079 2 91bab980 (+ 64) 800659c4 :invoke_debugger_command_pipe + 0x009c 3 91bab9c0 (+ 48) 80066f74 ExpressionParser<0x91baba74>::_ParseCommandPipe(0x91baba70) + 0x0234 4 91bab9f0 (+ 64) 800663ae ExpressionParser<0x91baba74>::EvaluateCommand(0x80126e00 "bt", 0x91baba70) + 0x02ba 5 91baba30 (+ 224) 8006839c :evaluate_debug_command + 0x0088 6 91babb10 (+ 64) 800636c6 kernel_debugger_loop() + 0x01ae 7 91babb50 (+ 32) 800645cd :kernel_debugger + 0x004d 8 91babb70 (+ 192) 80064575 :panic + 0x0029 9 91babc30 (+ 80) 800ca16d :vm_page_fault + 0x0139 10 91babc80 (+ 64) 800dab8d :page_fault_exception + 0x00d9 11 91babcc0 (+ 12) 800de2b6 :int_bottom + 0x0036 kernel iframe at 0x91babccc (end = 0x91babd1c) eax 0x800 ebx 0x807a7418 ecx 0x926ff800 edx 0x8145d668 esi 0x800 edi 0x0 ebp 0x91babe44 esp 0x91babd00 eip 0x807a3fea eflags 0x10286 vector: 0xe, error code: 0x0 12 91babccc (+ 376) 807a3fea ISOReadDirEnt(iso9660_volume*: 0x909aa800, dircookie*: 0x8145d668, dirent*: 0x180759c5, uint32: 0x2473 (9331)) + 0x00ea 13 91babe44 (+ 48) 807a5bc0 fs_read_dir(fs_volume*: 0x8131d988, fs_vnode*: 0x813223fc, 0x8145d668, dirent*: 0x180759c5, uint32: 0x2473 (9331), 0x91babf40) + 0x0030 14 91babe74 (+ 80) 800a7683 dir_read(io_context*: 0x8126c908, vnode*: 0x813223fc, 0x8145d668, dirent*: 0x180759c5, uint32: 0x2473 (9331), 0x91babf40) + 0x004b 15 91babec4 (+ 64) 800a7417 dir_read(io_context*: 0x8126c908, file_descriptor*: 0x8145d6b8, dirent*: 0x180759c5, uint32: 0x2473 (9331), 0x91babf40) + 0x002b 16 91babf04 (+ 64) 8009644d :_user_read_dir + 0x0069 17 91babf44 (+ 100) 800de4f1 :handle_syscall + 0x00be user iframe at 0x91babfa8 (end = 0x91bac000) eax 0x86 ebx 0x456c04 ecx 0x78206a10 edx 0xffff0104 esi 0x180759c5 edi 0x1809df08 ebp 0x78206a3c esp 0x91babfdc eip 0xffff0104 eflags 0x246 user esp 0x78206a10 vector: 0x63, error code: 0x0 18 91babfa8 (+ 0) ffff0104 :commpage_syscall + 0x0004 19 78206a3c (+ 48) 0052c318 BPrivate::CachedEntryIterator<0x1809ded8>::GetNextDirents(dirent*: 0x78206b68, uint32: 0x400 (1024), int32: 1) + 0x0078 20 78206a6c (+1344) 00597fe5 BPrivate::BPoseView<0x18102b68>::AddPosesTask(NULL) + 0x0379 21 78206fac (+ 48) 00682d58 :_get_next_team_info (nearest) + 0x005c 22 78206fdc (+ 0) 78206fec 6354:add poses_210_stack at 0x781c7000 + 0x3ffec kdebug> }}} Note that while this one is in Tracker's add poses thread, the exact same panic happens with ls -la via Terminal. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 07:10:21 2009 From: trac at haiku-os.org (leavengood) Date: Tue, 05 May 2009 05:10:21 -0000 Subject: [Haiku-bugs] [Haiku] #3790: New proposal color chooser In-Reply-To: <041.61423168bc3e793ee5dc043ca4dcd7ee@haiku-os.org> References: <041.61423168bc3e793ee5dc043ca4dcd7ee@haiku-os.org> Message-ID: <050.a6b425855dd72d651a127222fb56b567@haiku-os.org> #3790: New proposal color chooser -------------------------+-------------------------------------------------- Reporter: stpere | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by leavengood): * cc: leavengood@? (added) Comment: I think this patch is pretty interesting in the behavior it introduces, but it seems to have a bug: it uses a lot of CPU from what I assume is a lot of calls to Invalidate(). Whenever a color control is showing the CPU is pegged, whenever it is hidden the CPU slows down. So there is some flaw in the logic somewhere, I believe in _DrawSelector. Unfortunately I do not have time now to figure it out, but please take a look as I think this may be a worthwhile patch! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 10:48:29 2009 From: trac at haiku-os.org (jackburton) Date: Tue, 05 May 2009 08:48:29 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.000cbe78974aef5cec17287da5e4e133@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by jackburton): Tried removing hda (audio), rtl82xx (network) and the problem is still there. Will try removing more stuff. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 10:53:11 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 08:53:11 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.7f51385ad8f4d10ab2fb8a3117a5e7b8@haiku-os.org> #3847: Boot Fail ------------------------------+--------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: assigned Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: 3857, 3869, 3871 | ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => assigned Comment: I can finally reproduce the problem with qemu and the CD build. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 12:14:16 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 10:14:16 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.f35eeadd40eecc9d5edd82a50c9ff0d9@haiku-os.org> #3847: Boot Fail ----------------------------+----------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3857, 3869, 3871 ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30632. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 13:54:08 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 11:54:08 -0000 Subject: [Haiku-bugs] [Haiku] #3864: rootfs renaming does not work In-Reply-To: <041.0fbc0d188f71832d31078533689d23b5@haiku-os.org> References: <041.0fbc0d188f71832d31078533689d23b5@haiku-os.org> Message-ID: <050.18b05a6008ec4206a17642f60be4adb8@haiku-os.org> #3864: rootfs renaming does not work ----------------------------+----------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30633. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 14:12:50 2009 From: trac at haiku-os.org (HaiColon) Date: Tue, 05 May 2009 12:12:50 -0000 Subject: [Haiku-bugs] [Haiku] #3873: BeZilla only starts when run from Terminal Message-ID: <043.c5cf8f750b4d7ccb4979a5b68f33f9c9@haiku-os.org> #3873: BeZilla only starts when run from Terminal --------------------------+------------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- When starting BeZilla from the Deskbar menu, it crashes and asks if I want to debug it every time I try to run it. When I start it from the Terminal, it starts and works fine nearly all the time, it only crashed one time while starting like it does when using the Deskbar menu. I tried it out about ten times from the Terminal. I can't say at which revision of Haiku this problem started since I used a different computer to run Haiku up to about a week ago, where I didn't have this problem. I switched computers because the harddisk or one of the fans is damaged in the other computer (it makes evil noises). I did install Haiku to this computer about two months ago though and back then BeZilla did start fine when using the Deskbar menu on this computer. I'll attach the debugger output of when BeZilla crashes when using the link in the Deskbar menu and the terminal output from the one time BeZilla crashed when started from the Terminal. I don't know if this could be related but just to be sure, I use the ATA stack instead of the IDE stack because otherwise Haiku only boots on this computer if I disable ide-dma. Id did run jam clean because I read that not doing that can cause problems when switching to the ATA stack. I'm using revision 30632 of Haiku, gcc2 built from Ubuntu 8.10, installed to an USB harddisk. The computer has a Gigabyte K8NMF-9 motherboard with an Athlon XP 64 3200+ processor and 1,5 Gb of RAM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 14:34:44 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 05 May 2009 12:34:44 -0000 Subject: [Haiku-bugs] [Haiku] #3840: CD-ROM build broken In-Reply-To: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> References: <040.998c9cacba4e68c65a868da6d58b8bcd@haiku-os.org> Message-ID: <049.3cb2ca959e13ed14a79e76c1eb83d97b@haiku-os.org> #3840: CD-ROM build broken ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Au contraire. I predicted problems at the time of the directory changes and rebuilt cleanly to a different drive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 15:49:28 2009 From: trac at haiku-os.org (beos_zealot) Date: Tue, 05 May 2009 13:49:28 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.0ece480b9ec09e74d1ae491967c7b248@haiku-os.org> #3690: Copy file to USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by beos_zealot): * cc: beos.zealot@? (added) Comment: Same problem for me, too. Tested 2 USB flash drives (PQI 512MB and SanDisk Cruser 8Gb) formated both FAT and FAT32. Reading or copying from flash drives works correctly. If I mount them as read-write and try to write to them - copying dialog shows "Copying 1 of ...", progress bar grows by 1 file and stands in that position for few seconds - then drops to KDL. Made photo of KDL with bt, will upload today... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 16:22:09 2009 From: trac at haiku-os.org (HaikuBot) Date: Tue, 05 May 2009 14:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.9bc146dd389ea76630f74eeba93e1558@haiku-os.org> #3847: Boot Fail ----------------------------+----------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3857, 3869, 3871 ----------------------------+----------------------------------------------- Comment(by HaikuBot): Thanks Axel. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 16:52:49 2009 From: trac at haiku-os.org (zooey) Date: Tue, 05 May 2009 14:52:49 -0000 Subject: [Haiku-bugs] [Haiku] #3866: Update the Locale preflet to use the layout manager In-Reply-To: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> References: <045.2261e8f94c33d19a4e4780df394f542a@haiku-os.org> Message-ID: <054.df1b4c70b6db114e6b734824dcfe9b5c@haiku-os.org> #3866: Update the Locale preflet to use the layout manager --------------------------+------------------------------------------------- Reporter: pulkomandy | Owner: zooey Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Kits | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Applied in r30634 - thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 17:04:30 2009 From: trac at haiku-os.org (zooey) Date: Tue, 05 May 2009 15:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' Message-ID: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> #3874: Zipping many files bails with 'out of memory' --------------------------+------------------------------------------------- Reporter: zooey | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- If you run zip on a large set of files (in my case: ~40000 mails), the process size grows constantly (but moderately) and finally bails with an 'out of memory' error. I did not follow the process precisely, but I doubt that the zip process did exceed 100MB in size (on my 2GB machine running haiku natively). That should not be a reason for out-of-memory, should it? Anyway, since I can reproduce it here, I will look into it later today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 17:07:59 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 05 May 2009 15:07:59 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' In-Reply-To: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> References: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> Message-ID: <049.e848b29ce7d031ace3bccdfc47b16ecf@haiku-os.org> #3874: Zipping many files bails with 'out of memory' --------------------------+------------------------------------------------- Reporter: zooey | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): i've seen this too. both with mozilla 1.8's cvs code and zipping haiku's source directory. both directories were identified, eg right click the top level directory and chose "Identify". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 18:42:37 2009 From: trac at haiku-os.org (HaikuBot) Date: Tue, 05 May 2009 16:42:37 -0000 Subject: [Haiku-bugs] [Haiku] #3847: Boot Fail In-Reply-To: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> References: <043.a0f0428bcf43d81c753bb1b197f32389@haiku-os.org> Message-ID: <052.5d28735fa8a1b280e2e0d0cfac2d6529@haiku-os.org> #3847: Boot Fail ----------------------------+----------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3857, 3869, 3871 ----------------------------+----------------------------------------------- Comment(by HaikuBot): Also close this one #3703. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 18:47:12 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 May 2009 16:47:12 -0000 Subject: [Haiku-bugs] [Haiku] #3703: Boot Fail In-Reply-To: <043.45a737c7c485975cba8b96adbbe08e7a@haiku-os.org> References: <043.45a737c7c485975cba8b96adbbe08e7a@haiku-os.org> Message-ID: <052.66311f037248ef6f7a9c287d1830a624@haiku-os.org> #3703: Boot Fail ------------------------+--------------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => fixed Comment: Thanks for the note! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 18:51:01 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 05 May 2009 16:51:01 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' In-Reply-To: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> References: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> Message-ID: <049.21b0fab87cbb1bdbb0ba50ac5cf8c839@haiku-os.org> #3874: Zipping many files bails with 'out of memory' --------------------------+------------------------------------------------- Reporter: zooey | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): This might have to do with how we reserve memory for areas. If the allocation that failed was a realloc() of a large chunk of memory, the heap area would have to be resized, involving reserving memory for the new range. If most of the available memory is bound in block caches at that time, there might not be enough memory to reserve at that time. Our current, somewhat crude strategy is to trigger the low resource manager -- which tries to free caches and the like -- and wait for at most one second. If then there's still not enough memory available, the operation just fails. I.e. if the low resource manager is a bit slow, an area creation/resize can fail although it wouldn't really have to. Anyway, the amounts of memory involved sound a bit off for that kind of problem. Normally one has one block cache block per inode. I'm not sure how BFS works with respect to attributes that don't fit the small data region of the file; I believe they get inodes of their own. But still, with 2 GB of memory one would need to use about 50 blocks per file to exhaust the memory, which doesn't sound particularly realistic. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 19:00:46 2009 From: trac at haiku-os.org (beos_zealot) Date: Tue, 05 May 2009 17:00:46 -0000 Subject: [Haiku-bugs] [Haiku] #3690: Copy file to USB flash drive causes KDL In-Reply-To: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> References: <040.e5436f6579ffd970865d8dbe8fde3535@haiku-os.org> Message-ID: <049.bea121fe5559ceff15650faba6d34719@haiku-os.org> #3690: Copy file to USB flash drive causes KDL ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by beos_zealot): ATTACHED promised photo... UPDATE: checked usb flash drive content after KDL on other computer (win xp). shows 1 copied file (the first in copying queue), even shows size of the file, but when i try to open - complains that file corrupted and size of the file becomes 0 kb. Can't delete this file (tried from win xp) only formatting of usb flash drive helps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 19:02:05 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 05 May 2009 17:02:05 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' In-Reply-To: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> References: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> Message-ID: <049.89d4c9f1be662644524fad53ce13a05d@haiku-os.org> #3874: Zipping many files bails with 'out of memory' --------------------------+------------------------------------------------- Reporter: zooey | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): as a note, tar cjf is able to compress both the mozilla 1.8 cvs branch and haiku-r30629's svn tree. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 19:55:00 2009 From: trac at haiku-os.org (kvdman) Date: Tue, 05 May 2009 17:55:00 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.c9eb46ffd6d100979423f541c26fb90e@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) --------------------------+------------------------------------------------- Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by kvdman): Since ticket #3847 has been fixed, I'm able to boot Haiku on both Macs now. This can be closed. More info here: [http://www.haikuware.com/preliminary-haiku-support-for-macs] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 20:06:38 2009 From: trac at haiku-os.org (stippi) Date: Tue, 05 May 2009 18:06:38 -0000 Subject: [Haiku-bugs] [Haiku] #1599: Haiku Booting on a MacBook Info...(gets stuck) In-Reply-To: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> References: <041.087bc019eace8c6577ade1023106e25a@haiku-os.org> Message-ID: <050.4eac626101aed36a02fd521051084745@haiku-os.org> #1599: Haiku Booting on a MacBook Info...(gets stuck) ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks for the update! Sweet! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 21:28:11 2009 From: trac at haiku-os.org (rudolfc) Date: Tue, 05 May 2009 19:28:11 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.d948b47e6112257feb6ae4b0ed8b35b0@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): yep, speaking up! I have this card here today: it actually works fine, on both a VGA screen and a DVI connected screen. I will re-enable this ID if no-one speaks up... There are some things you should know (as a user): -if a DVI connected screen doesn't work, try it the analog way. If an analog screen doesn't work on one port, try the other one. Even if that would mean using a DVI->VGA adapter. Anyhow, I saw that I can't get an VGA screen to work on the DVI connector due to false connector detection there (missing hardware spec, also mentioned in the driver's html docs I think) Also EDID channel doesn't work for this card on the DVI connector (but that's not actually used for now). This also applies for G72 (GF7300LE tested) BTW.. Greetings, Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 22:09:32 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 20:09:32 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.6cac4893f50f34359339648400bf77c3@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): The iso9660_shell (available again since r30639) does not exhibit the crash, but otherwise shows the same problem. Should be easier to debug there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 22:15:15 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 May 2009 20:15:15 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.59ee9833d598720aa426ec5a4b8ae25f@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Replying to [comment:8 axeld]: > The iso9660_shell (available again since r30639) does not exhibit the crash, but otherwise shows the same problem. Should be easier to debug there. Cool, let me know if you need anything else for reference. As far as I can tell any CD I burn via OSX Leopard's Finder shows the exact same dir structure problems, though the KDL seems to be hit or miss. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 18:41:20 2009 From: trac at haiku-os.org (HaikuBot) Date: Tue, 05 May 2009 16:41:20 -0000 Subject: [Haiku-bugs] [Haiku] #3703: Boot Fail In-Reply-To: <043.45a737c7c485975cba8b96adbbe08e7a@haiku-os.org> References: <043.45a737c7c485975cba8b96adbbe08e7a@haiku-os.org> Message-ID: <052.889801af06374f6b3d1fcb1d267fec7b@haiku-os.org> #3703: Boot Fail -----------------------+---------------------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by HaikuBot): please, close this ticket, after r30632 Haiku is loaded successfully on my main PC. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 23:10:13 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 21:10:13 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.357b1cf7dd9f5d561fb3624faef9ba79@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): The crashing part is fixed in r30640 - this bug was probably hidden by the userland allocator. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 23:14:26 2009 From: trac at haiku-os.org (axeld) Date: Tue, 05 May 2009 21:14:26 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.23bee6bcd1a75d4e5e11cd9a14385de8@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): The data accessible from Haiku looks like the MacOS resouce forks, at least that's what I would assume. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 5 23:16:15 2009 From: trac at haiku-os.org (anevilyak) Date: Tue, 05 May 2009 21:16:15 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.6e80c80793714d03248009b7de4d0c25@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Replying to [comment:11 axeld]: > The data accessible from Haiku looks like the MacOS resouce forks, at least that's what I would assume. Ahh, that's entirely possible. Is the function that sanitizes filenames by any chance stripping out a filename prefix character that OSX uses to differentiate between the file and the resource data here by any chance? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 00:59:40 2009 From: trac at haiku-os.org (bga) Date: Tue, 05 May 2009 22:59:40 -0000 Subject: [Haiku-bugs] [Haiku] #3875: "copyattr -d -r" results in attempts to write to read-only source partition. Message-ID: <038.c11eb449a698b1ce17726bcabf25e2b1@haiku-os.org> #3875: "copyattr -d -r" results in attempts to write to read-only source partition. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- I did a clean Haiku install in one partition and started moving the data from the old partition to the new one. For this, I mounted the old partition read-only and used copyattr -d -r to copy specific directories. From time to time, I would get messaged like the following in my syslog: {{{ 2009-05-05 19:38:59 KERN: bfs: bfs_open:1183: Read-only file system 2009-05-05 19:39:01 KERN: Last message repeated 729 times. }}} Looking at BFS's kernel_interface.cpp file, I see this: {{{ // opening a directory read-only is allowed, although you can't read // any data from it. if (inode->IsDirectory() && (openMode & O_RWMASK) != 0) { openMode = openMode & ~O_RWMASK; // TODO: for compatibility reasons, we don't return an error here... // e.g. "copyattr" tries to do that //return B_IS_A_DIRECTORY; } status_t status = inode->CheckPermissions(open_mode_to_access(openMode) | (openMode & O_TRUNC ? W_OK : 0)); if (status < B_OK) RETURN_ERROR(status); }}} Some questions about this: 1 - Why does copyattr need that? Can't we simply fix it? 2 - Although if the volume is read/write this will allow copyattr to do whatever it does, when it is read-only it will bail out on the following error (which results in the messages I mentioned in the syslog). Does this mean that the copy operation does not really work when the source is a read-only volume? 4 - If it does work even with the error being returned, why is it a problem to return the error in the pointed commented out above? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 01:09:36 2009 From: trac at haiku-os.org (bga) Date: Tue, 05 May 2009 23:09:36 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. Message-ID: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> #3876: DHCP does not work. -------------------------------------+-------------------------------------- Reporter: bga | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Since a long time ago, DHCP stopped working on my machine (it used to work). I have worked this around by assigning a static IP but I decided to open a ticket anyway. Here is what I see on syslog: {{{ ~> grep DAEMON /var/log/syslog DAEMON 'DHCP': DHCP for /dev/net/marvell_yukon/1, status: Address already in use DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 0) DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 0) DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 1) DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 1) DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 1) DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 2) DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 2) DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 2) DAEMON 'DHCP': DHCP for /dev/net/marvell_yukon/0, status: Operation timed out 2009-05-05 19:30:46 DAEMON 'DHCP': DHCP for /dev/net/marvell_yukon/1, status: Address already in use 2009-05-05 19:30:46 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 0) 2009-05-05 19:30:50 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 0) 2009-05-05 19:30:58 DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 1) 2009-05-05 19:31:00 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 1) 2009-05-05 19:31:04 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 1) 2009-05-05 19:31:12 DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 2) 2009-05-05 19:31:14 DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 2) 2009-05-05 19:31:18 DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 2) 2009-05-05 19:31:26 DAEMON 'DHCP': DHCP for /dev/net/marvell_yukon/0, status: Operation timed out }}} The line that says "Address already in use" is fishy. Specially considering that /dev/net/marvell_yukon/1 is the card that is actually plugged in to a cable while /dev/net/marvell_yukon/0 is disconnected (yes, I have 2 network cards). As a reference: {{{ ~> ifconfig loop Hardware Type: Local Loopback, Address: none inet addr: 127.0.0.1, Mask: 255.0.0.0 MTU: 16384, Metric: 0, up loopback link Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0 /dev/net/marvell_yukon/0 Hardware Type: Ethernet, Address: 00:1e:8c:3a:6c:64 inet addr: 169.254.0.160, Bcast: 169.254.255.255, Mask: 255.255.0.0 MTU: 1500, Metric: 0, up broadcast auto-configured Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 9 packets, 0 errors, 2664 bytes, 0 mcasts, 0 dropped Collisions: 0 /dev/net/marvell_yukon/1 Hardware Type: Ethernet, Address: 00:1e:8c:3a:65:24 Media Type: 100 MBit, 100BASE-TX inet addr: 192.168.0.2, Bcast: 192.168.0.255, Mask: 255.255.255.0 MTU: 1500, Metric: 0, up broadcast link auto-configured Receive: 932 packets, 0 errors, 599744 bytes, 0 mcasts, 0 dropped Transmit: 809 packets, 0 errors, 113448 bytes, 0 mcasts, 0 dropped Collisions: 0 }}} The card ending with a 0 has no cable connected to it so it is expected that it gets a IP like the one it gets. The card ending with 1 has a cable connected and has a valid IP only because it is statically configured. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 05:40:59 2009 From: trac at haiku-os.org (shinta) Date: Wed, 06 May 2009 03:40:59 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab In-Reply-To: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> References: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> Message-ID: <050.5f12c1bd2e02a2bfd2cc3b0d0082ebd9@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab --------------------------------+------------------------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by shinta): Oh! Thank you for advice! I can get desired result by Adding B_DRAW_ON_CHILDREN flag to the parent BView. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 07:21:02 2009 From: trac at haiku-os.org (michael.weirauch) Date: Wed, 06 May 2009 05:21:02 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. In-Reply-To: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> References: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> Message-ID: <047.4b46a99fec2eb21002c4e257452d3b32@haiku-os.org> #3876: DHCP does not work. -------------------------------------+-------------------------------------- Reporter: bga | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by michael.weirauch): I can confirm seeing the DHCP timeout shifts occassionally. Sometimes my ipro1000 (fbsd_compat) just works (c), and sometimes it won't get an IP address via DHCP. Mostly it gets one assigned, though. (Only one NIC as opposed to Bruno) Can't recall having seen the "address already in use", my remembrance might fool me, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 08:54:39 2009 From: trac at haiku-os.org (jackburton) Date: Wed, 06 May 2009 06:54:39 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.e8fc7d5a1788aee521ce668ccac70be8@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by jackburton): Looks like the problematic driver is the touchpad one. If I comment out the whole synaptics_close() implementation, the laptop reboots correctly. Now I'll try to find what exactly hangs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 09:00:10 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 07:00:10 -0000 Subject: [Haiku-bugs] [Haiku] #3865: DrawAfterChildren() isn't called after changing of tab In-Reply-To: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> References: <041.49ab06983c991722c3e778a88eb0fc10@haiku-os.org> Message-ID: <050.e1ce9ca7927eee0ab56562e01c591462@haiku-os.org> #3865: DrawAfterChildren() isn't called after changing of tab ---------------------------------+------------------------------------------ Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => invalid Comment: Thanks for the note. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 10:09:10 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 08:09:10 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works Message-ID: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- $ jam -q install-haiku build/jam/UserBuildConfig: line 19: parse error at keyword : warning: unknown rule /boot/system/data/timezones/Australia/Melbourne Build system is BeOS 5.1d0 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 10:11:32 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 08:11:32 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.36fe582f94c30ee4b2906312ca629f9f@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by stippi): Did you really open a bug report for a syntax error you made in your own UserBuildConfig? Please at least post the respective lines. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 11:33:05 2009 From: trac at haiku-os.org (axeld) Date: Wed, 06 May 2009 09:33:05 -0000 Subject: [Haiku-bugs] [Haiku] #3868: Hang on shutdown/reboot In-Reply-To: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> References: <045.9e528d586baca033044aa11c0b2dbdb3@haiku-os.org> Message-ID: <054.83904faad1a2f3f0122c74d624c5c040@haiku-os.org> #3868: Hang on shutdown/reboot ------------------------+--------------------------------------------------- Reporter: jackburton | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------+--------------------------------------------------- Comment(by axeld): That's not even too surprising considering that the reboot is usually triggered via the keyboard controller. Eventually, the driver needs to reset the controller when it's closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 11:48:16 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 09:48:16 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target Message-ID: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> #3878: Faults in haiku-cd build target --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Just tried `jam -q haiku-cd` for the first time. The build was missing the whole /boot/system directory, and also contained entries in each directory that looked like `_HAIKU`. This doesn't look right to me. Of course, because the systems files were missing it couldn't boot either. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 11:52:07 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 09:52:07 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.433f209f1a4995594e6cffc629d666e7@haiku-os.org> #3878: Faults in haiku-cd build target --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): I forgot to mention that during the build process there was a warning about the imahe being built not being an iso9660 compatible image. The image could not be mounted within Dano, using `mount generated/haiku- cd.iso /image` -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 12:20:08 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 10:20:08 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works Message-ID: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- I guess that summarizes it all... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 12:35:36 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 10:35:36 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.1239e611386cc289aa86c99c24f3201a@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by stippi): No, unfortunately, it doesn't summarize it enough at all. I am pretty sure that HAIKU_IMAGE_SIZE works, but it may be that it doesn't work for the specific target you are trying to build. So please be more specific about what you are trying to do and about the circumstances that this doesn't work in. (Or rather doesn't work in your opinion...) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:02:13 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 06 May 2009 11:02:13 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.be9fabaac1d60f71bcff4c47c3453400@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:10:47 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 11:10:47 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.af55aa19ec1b65a6be128700a81fdc76@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by haiqu): * status: closed => reopened * resolution: invalid => Comment: I may be dumb, Stippi, but I'm not stupid. To be stupid AND dumb you'd have to be brilliant... # Add symlink/file (timezone and keymap settings) to the image. AddSymlinkToHaikuImage home config settings : /boot/system/data/timezones/Australia/Melbourne : timezone ; AddFilesToHaikuImage home config settings : American : Key_map ; -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:12:10 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 11:12:10 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.df03c7868e9868479350be403ec69120@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Woops, I don't remember commenting that out. Invalid, please close again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:16:30 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 11:16:30 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.5a2ecb6fceaeb24bfe2439077e593f81@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Naah, wait a minute. That's just Trac's crappy quoting problem. It looks like this: {{{ # Add symlink/file (timezone and keymap settings) to the image. AddSymlinkToHaikuImage home config settings : /boot/system/data/timezones/Australia/Melbourne : timezone ; AddFilesToHaikuImage home config settings : American : Key_map ; }}} VALID. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:29:50 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 11:29:50 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.70290f017da895ac91e2a137ca6f9a2d@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => invalid Comment: Please run an svn diff and check that you don't have any conflicts or changes in your build system. Building the CD works just fine here, under Haiku as well as under BeOS R5 and I know that others build it successfully under Linux as well. It looks perfectly fine when there are _HAIKU directories. Those are the attribute stores that contain the attributes for the corresponding files. Also the image is perfectly fine not being fully iso9660 compliant. It just means that the extremely narrowly defined naming and directory depths are not followed strictly. In practice this is not a problem for any system I know of. At least it is not a problem for Haiku, and that's the only real target this CD must work with as you can't really do much with the files on other systems anyway. That it doesn't mount in BeOS has nothing to do with the image being invalid, but with not using the command correctly. Mounting on BeOS doesn't do filesystem detection. So for anything non-BFS you'll have to provide a "-t " argument. Mounting the CD with "mount -t iso9660 generated/haiku-cd.iso" will therefore work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:37:11 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 11:37:11 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.df9f6d2d7779de0e801daf8b2cf094ae@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): This is how it looks for me: {{{ # overwrite default timezone and keymap AddSymlinkToHaikuImage home config settings : /boot/system/data/timezones/Europe/Berlin : timezone ; AddFilesToHaikuImage home config settings : German : Key_map ; }}} And that certainly works. Can you please show your entire UserBuildConfig, specifically line 19? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:41:53 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 11:41:53 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.dc378105245eb66f9a78ea44ef7d58c0@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Your syntax error obviously starts at the lines above those as jam tries to use the symlink target path as a rule. You probably miss a closing ";" on a line above those. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 13:45:14 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 06 May 2009 11:45:14 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.b78d718a68e26962aa3626661414c0d5@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: reopened => closed * resolution: => invalid Comment: If jam reports a syntax error in your UserBuildConfig, it's a syntax error in your UserBuildConfig and not a build system problem. My guess is you missed a ";" or "}" (respectively the delimiting spaces) earlier in the file. At any rate adding the time zone symlink works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 14:24:56 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 12:24:56 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.f486a182e8eb55049a6dca2837e07588@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): # Create a 100 MB image at /tmp/walter.image. HAIKU_IMAGE_SIZE = 320 ; The image created was 128Mb and changing the value UserBuildConfig didn't alter that. This worked on my last build within the past 2 days, so something changed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 14:25:29 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 12:25:29 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.12264dec2a49609d004b34b3718765e1@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): {{{ # Create a 100 MB image at /tmp/walter.image. HAIKU_IMAGE_SIZE = 320 ; }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 14:40:42 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 12:40:42 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.ebde43bb89c93d511eb287d9f5cda867@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by stippi): Are you using '''jam haiku-image''' or are you using '''jam haiku-cd'''? Because only for the first of these two, the image size is supposed to be settable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 14:47:07 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 12:47:07 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.72deb83d2ec3a48ad1466357fe602dc2@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Yes, I knew that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 14:57:17 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 12:57:17 -0000 Subject: [Haiku-bugs] [Haiku] #3880: Can't switch terminals with function keys Message-ID: <040.6cf6e9e92ae28f5e611614f08f7664f9@haiku-os.org> #3880: Can't switch terminals with function keys -----------------------------------+---------------------------------------- Reporter: haiqu | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------------------+---------------------------------------- Trying to switch to one of the other three terminals I have set up but the function keys don't do what I expected. Also tried Command-G which I read about in the Trac database, same issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 15:04:31 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 13:04:31 -0000 Subject: [Haiku-bugs] [Haiku] #3880: Can't switch terminals with function keys In-Reply-To: <040.6cf6e9e92ae28f5e611614f08f7664f9@haiku-os.org> References: <040.6cf6e9e92ae28f5e611614f08f7664f9@haiku-os.org> Message-ID: <049.a75a7a65b98b04c03535ffe9458cc240@haiku-os.org> #3880: Can't switch terminals with function keys -----------------------------------+---------------------------------------- Reporter: haiqu | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------------------+---------------------------------------- Comment(by haiqu): That wasn't very clear. I'm trying to switch SCREENS, not between terminals. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 15:39:47 2009 From: trac at haiku-os.org (bga) Date: Wed, 06 May 2009 13:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. In-Reply-To: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> References: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> Message-ID: <047.9563398dbc5a4691a017afb1af5b163a@haiku-os.org> #3876: DHCP does not work. -------------------------------------+-------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by bga): * owner: zooey => bga Comment: I am on it. Michael, your problems is different from mine. Mine happens exactkly because I have multiple interfaces. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 15:46:52 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 13:46:52 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.601c9c5c3c10956c69f251d4674697e2@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by mmlr): I don't know what you did to your build system, but FWIW it works fine here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 16:25:51 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 14:25:51 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.c0b3ce7a7984a5c99d3e3d30794c1882@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Thanks Michael. The problem was indeed a missing semicolon above that point. I'm used to build tools that report on the line in which the error occurs, I guess jam isn't able to be that exact. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 16:34:40 2009 From: trac at haiku-os.org (axeld) Date: Wed, 06 May 2009 14:34:40 -0000 Subject: [Haiku-bugs] [Haiku] #3880: Can't switch terminals with function keys In-Reply-To: <040.6cf6e9e92ae28f5e611614f08f7664f9@haiku-os.org> References: <040.6cf6e9e92ae28f5e611614f08f7664f9@haiku-os.org> Message-ID: <049.4fbdde60dbab6182dc477345b4147b90@haiku-os.org> #3880: Can't switch terminals with function keys ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: It's still not clear as Alt-G is indeed for switching Terminals. To switch between workspaces, use Alt-Fx, where x is a number between 1 and the number of workspaces you defined. No clue what you call SCREENS here. In any case, if you're not sure how something should work - that's what the "haiku" mailing list is for, not the bug tracker. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 16:35:31 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 14:35:31 -0000 Subject: [Haiku-bugs] [Haiku] #3877: Setting timezone in UserBuildConfig no longer works In-Reply-To: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> References: <040.2cb794aff8e499f451edc0f27267aece@haiku-os.org> Message-ID: <049.0b18175bed2ef8b05dd34edf6174c4b4@haiku-os.org> #3877: Setting timezone in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Multiple points: * It was obvious from the beginning that the error must be in your UserBuildConfig, see my very first comment. * Your insisting and inability to provide sufficient info has dragged this out much longer than necessary. It costs us all time, as you no doubt know. * Even build tools like GCC will choke on the next statement if you forget a semicolon. If you forget it in a header after the last class declaration, it will even choke in a different file (the file where you include the header...) * Next time you encounter a bug that has a very high likeliness of being on your side, please double check everything before reporting it. And yes, a reported syntax error in a file you created yourself does count as very likely to be an error on your side. ;-) * Remember that we are an open source project where you want us to code and fix real issues, instead of spending our limited spare time on invalid bug reports. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 17:04:36 2009 From: trac at haiku-os.org (bga) Date: Wed, 06 May 2009 15:04:36 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. In-Reply-To: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> References: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> Message-ID: <047.5117200e475cdd176adbf96740539bf1@haiku-os.org> #3876: DHCP does not work. -------------------------------------+-------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by bga): So, the problem is that when you have 2 interfaces, bind will be called twice for the same port and using INADDR_ANY. This is why it complains address is already in use. It seems the correct way to go about it would be to binding to a specific device instead of binding to INADDR_ANY. As the devices have no IP yet, there must be a way to bind to them without the need for an IP. Is this implemented in our stack? If so, how would one go about doing this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 17:11:19 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 06 May 2009 15:11:19 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.a5d9a6d819cac54f73ff05414b87ac75@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): "svn stat" would probably be a bit faster way to find out :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 17:49:54 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 15:49:54 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.9a2772f16d3256c515f560ba20d7ffd1@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by haiqu): * status: closed => reopened * resolution: invalid => Comment: {{{ $ svn stat M build/jam/HaikuImage M ReadMe $ }}} I'm going to have to insist that this is a fault. I did it again after fixing a minor syntax error that threw JAM into a complete spin (causing three bogus reports, I might add) but this CD build STILL has no /boot/system directory. Re comments: Usage details for the `mount` command aren't very useful, especially when you don't actually know the filetype for the -t switch. And `mkisofs` issuing a warning when simply building with Rock Ridge or Joliet extensions doesn't make much sense either, especially since plain ISO-9660 is so broken. 8.3 filenames, are they kidding? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 17:55:39 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 15:55:39 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.2d58d96daaf0eed4bc01268b41cc1923@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): OK, this was the result of a minor syntax error in UserBuildConfig in a line AFTER the size was set. Jam evidently lost the plot completely. Close, invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 17:57:43 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 06 May 2009 15:57:43 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.e12663b2223c5cea416ad0f383a01874@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by mmadia): * status: new => closed * resolution: => invalid -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:00:48 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 16:00:48 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.7f83164d1e8dcfcc03ee12702c86d575@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Ok, then please post the output of '''svn diff build/jam/HaikuImage''' here. This may either be a fault in your HaikuImage changes, or a problem with using this jam target on BeOS/Dano. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:02:51 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 06 May 2009 16:02:51 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.8cbd9b173dfdd68b5d23fe7a41719668@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): I implore you to please discuss your UserBuildConfig issues on the mailing list(s) rather than on Trac. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:20:17 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 16:20:17 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.5ad10bf4b493196e7f52f0d2cf56eda2@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): There are two minor differences. One is some missing white space, the other is a build target I added, but which is commented out. {{{ ~> svn diff /BeOS\ 5.1d0/src/haiku/build/jam/HaikuImage Index: /BeOS 5.1d0/src/haiku/build/jam/HaikuImage =================================================================== --- /BeOS 5.1d0/src/haiku/build/jam/HaikuImage (revision 30645) +++ /BeOS 5.1d0/src/haiku/build/jam/HaikuImage (working copy) @@ -252,7 +252,7 @@ AddFilesToHaikuImage system servers : $(SYSTEM_SERVERS) ; # apps -AddFilesToHaikuImage system : runtime_loader Deskbar Tracker ; +AddFilesToHaikuImage system : runtime_loader Deskbar Tracker ; AddFilesToHaikuImage system bin : $(SYSTEM_BIN) consoled ; AddFilesToHaikuImage system apps : $(SYSTEM_APPS) ; AddFilesToHaikuImage system preferences : $(SYSTEM_PREFERENCES) ; @@ -460,6 +460,7 @@ : $(SYSTEM_ADD_ONS_MEDIA_PLUGINS) ; AddFilesToHaikuImage system add-ons Tracker : FileType-F ZipOMatic-Z Open\ Target\ Folder-T ; +# : FileType-F ZipOMatic-Z TarNFeather-R Open\ Target\ Folder-T ; AddSymlinkToHaikuImage system add-ons Tracker : /boot/system/preferences/Backgrounds : Background-B ; AddSymlinkToHaikuImage system add-ons Tracker ~> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:24:05 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 06 May 2009 16:24:05 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.b67b50cf302d34ff03a2cde0beb73bd3@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by umccullough): Do you possibly have another UserBuildConfig hanging out in your generated folder as well as the trunk/build/jam folder? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:28:02 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 16:28:02 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.3baaf9c8001db53dd2648db6be240add@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): If it didn't look like a build bug to me I wouldn't report it, Urias. In my own defence, about 8 out of *every* 10 updates I do is rife with bugs included by people who don't actually test code before they upload it. I might add that I was up all night writing a TV card driver, so may not have been as focused as usual. However, I am getting mighty tired of Trac maintainers assuming I'm an idiot, that all bug reports are automatically wrong (and closing them before investigation) and being condescending. These comments are not specifically aimed at you, btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:36:13 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 16:36:13 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.ba4bb83c4dac4d98475a0ae016ea80f3@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Nope, and I did a `find` on that to be absolutely sure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 18:57:37 2009 From: trac at haiku-os.org (zooey) Date: Wed, 06 May 2009 16:57:37 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' In-Reply-To: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> References: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> Message-ID: <049.d83d43fecd544fc45364398a102b794d@haiku-os.org> #3874: Zipping many files bails with 'out of memory' --------------------------+------------------------------------------------- Reporter: zooey | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by zooey): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:06:28 2009 From: trac at haiku-os.org (fano) Date: Wed, 06 May 2009 19:06:28 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key Message-ID: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- I've try to use the installer to create a bootable usb key. These are the things I've done: 1. Using the "Setup partions" I inizialized all the USB drive (that is only a single partion big as the whole drive) 2. Then I started the installer... all files are copied 3. The installer make the drive bootable and ask me to reboot 4. After reboot I choose in the bios boot menu my key as bootable device 5. Only a blinking " _ " appears... forever! I'm using Hailu rev. 30637 My system is composed by: Cpu Athlon X2 3600+ Motherboard Asus M2NPV-VM with integrated NVIDIA 6150 GPU SoundCard SuondBlase Audigy USB Key Sandisk Cruzer Micro 8 GB -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:12:46 2009 From: trac at haiku-os.org (bbjimmy) Date: Wed, 06 May 2009 19:12:46 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file Message-ID: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> #3882: system freezes opening file -----------------------+---------------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- f12 and bt indicates "Tracker Status" is the thead causing the problem. r30641 opening the attatched file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:16:13 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 06 May 2009 19:16:13 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.59ebeb7df3ddbbf59cc88b6d1561f8c6@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by mmadia): Since USB booting tends to be hit or miss with some system, can you try using `dd` to write the image directly to the device, making certain that it is the raw device and not a partition on it? This would help to pinpoint the problem being with Installer and not somewhere else. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:16:41 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 19:16:41 -0000 Subject: [Haiku-bugs] [Haiku] #2435: [Media] volume slider is flickering when moving In-Reply-To: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> References: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> Message-ID: <049.21e1180dd4f98296d17c10d1c1d5f210@haiku-os.org> #2435: [Media] volume slider is flickering when moving -------------------------------+-------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by korli): Is it still valid with latest UI changes ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:22:40 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 19:22:40 -0000 Subject: [Haiku-bugs] [Haiku] #3613: Does not rememeber the selected partitions In-Reply-To: <041.a295b70575e63fffacf34ce2d6eccc13@haiku-os.org> References: <041.a295b70575e63fffacf34ce2d6eccc13@haiku-os.org> Message-ID: <050.3c07851bb99bd5f6545cc42de83b7c20@haiku-os.org> #3613: Does not rememeber the selected partitions ------------------------------------+--------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by korli): Is this bug still valid ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:22:45 2009 From: trac at haiku-os.org (diver) Date: Wed, 06 May 2009 19:22:45 -0000 Subject: [Haiku-bugs] [Haiku] #2435: [Media] volume slider is flickering when moving In-Reply-To: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> References: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> Message-ID: <049.741daf9d2ef837e58607b557cda3da34@haiku-os.org> #2435: [Media] volume slider is flickering when moving -------------------------------+-------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by diver): Nope, please close. But I liked the old gui much more :-( oh, well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:55:34 2009 From: trac at haiku-os.org (mjw) Date: Wed, 06 May 2009 19:55:34 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() Message-ID: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- I have created a patch to implement pthread_attr_getstack(). It also implements pthread_getattr_np() as a supporting function. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:04:39 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 06 May 2009 20:04:39 -0000 Subject: [Haiku-bugs] [Haiku] #3633: get ARM-Toolchain to compile In-Reply-To: <045.f8f3684cf7522d30c480d1b9e4f2e0a4@haiku-os.org> References: <045.f8f3684cf7522d30c480d1b9e4f2e0a4@haiku-os.org> Message-ID: <054.c4f924018270807bb1bb785a5b0bdfba@haiku-os.org> #3633: get ARM-Toolchain to compile --------------------------+------------------------------------------------- Reporter: pfoetchen_ | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by umccullough): * cc: umccullough (added) Comment: Is it a good time to apply this patch yet? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:21:06 2009 From: trac at haiku-os.org (bga) Date: Wed, 06 May 2009 20:21:06 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. In-Reply-To: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> References: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> Message-ID: <047.49132466bb8d59df0df6dbb02c96425f@haiku-os.org> #3876: DHCP does not work. -------------------------------------+-------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by bga): Forget it, already figured it out. Fix coming up later today. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:24:40 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 20:24:40 -0000 Subject: [Haiku-bugs] [Haiku] #3613: Does not rememeber the selected partitions In-Reply-To: <041.a295b70575e63fffacf34ce2d6eccc13@haiku-os.org> References: <041.a295b70575e63fffacf34ce2d6eccc13@haiku-os.org> Message-ID: <050.e85e33b47c43d521c98b848baf446fab@haiku-os.org> #3613: Does not rememeber the selected partitions ------------------------------------+--------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): For Onto, it's in the moment intended to lose the selection and revert to "Please Choose Target". For "Install From", Installer could try to remember the partition. So I'd leave the ticket open. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:36:25 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 20:36:25 -0000 Subject: [Haiku-bugs] [Haiku] #3633: get ARM-Toolchain to compile In-Reply-To: <045.f8f3684cf7522d30c480d1b9e4f2e0a4@haiku-os.org> References: <045.f8f3684cf7522d30c480d1b9e4f2e0a4@haiku-os.org> Message-ID: <054.ab737569c0a6bde6ac36bf329b78aa71@haiku-os.org> #3633: get ARM-Toolchain to compile ---------------------------+------------------------------------------------ Reporter: pfoetchen_ | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed Comment: Checked that it now broke on arm specific headers in haiku. Applied in r30652. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:37:18 2009 From: trac at haiku-os.org (zooey) Date: Wed, 06 May 2009 20:37:18 -0000 Subject: [Haiku-bugs] [Haiku] #3874: Zipping many files bails with 'out of memory' In-Reply-To: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> References: <040.c74a7c015d0dd9eabb9a879af9703acd@haiku-os.org> Message-ID: <049.341e3f529a0311ff5f7e5fef1e3d346b@haiku-os.org> #3874: Zipping many files bails with 'out of memory' ---------------------------+------------------------------------------------ Reporter: zooey | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Should be fixed by r30653 - at least I could now zip up all my mails. mmadia: please reopen if you still experience problems -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:39:44 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 20:39:44 -0000 Subject: [Haiku-bugs] [Haiku] #2435: [Media] volume slider is flickering when moving In-Reply-To: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> References: <040.25498fe725cdf760a5ee0ce0932bf5cf@haiku-os.org> Message-ID: <049.a8587fa364dfd322d468667bf5f1f011@haiku-os.org> #2435: [Media] volume slider is flickering when moving --------------------------------+------------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Thanks for the feedback ! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:43:26 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 20:43:26 -0000 Subject: [Haiku-bugs] [Haiku] #3361: [InstallCD] Opening DriveSetup changes target partition In-Reply-To: <042.3a316a2a295115adf11b80d6b846b130@haiku-os.org> References: <042.3a316a2a295115adf11b80d6b846b130@haiku-os.org> Message-ID: <051.69e21e6d41df29824b8a41cbb525bd5d@haiku-os.org> #3361: [InstallCD] Opening DriveSetup changes target partition ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by korli): Is this still valid with the UI changes ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:45:13 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 20:45:13 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.7122b680a66f4946b5b27f880ef80386@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Look Rob, I fully understand that feedback to some of your bug reports was frustrating to you overall, but please acknowledge that it may also have been frustrating for the other people involved. I also understand that it's frustrating if there are regressions when you update, though I personally think your "8 out of 10" estimate is totally out of proportion and your reasoning that people don't actually test code is a low blow. It simply so happens that stuff just isn't reproducable on some peoples hardware. For example, the two pre-fetching regressions were not reproducable at first and Axel fixed the issues as soon as he found a setup to reproduce them. In the future, make it easier on yourself and put more effort into guessing what information may be necessary to look into an issue you report. Instead of assuming/insisting that a particular problem you have must be reproducable on anyones setup, assume that the problem is only reproducable on your specific setup, and then try to provide as much info as possible to replicate that setup, so that the problem becomes reproducable for other people. I am happy to hear you are working on a TV card driver and am very much looking forward to that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:51:13 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 06 May 2009 20:51:13 -0000 Subject: [Haiku-bugs] [Haiku] #3884: IP adress format Message-ID: <050.c2b61cf26763f49ed7ece41e8d1cb8b2@haiku-os.org> #3884: IP adress format -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Specifying the DNS address as 10.1 in Network preferences, and thus also in /etc/resolv.conf doesn't work. It has to be written as 10.0.0.1 "ftp 10.1" or "telnet 10.1" in Terminal doesn't work, using "ftp 10.0.0.1" or "telnet 10.0.0.1" works. Using http://10.1 in Firefox however does work. 10.1 is a valid address. Something is wrong, please fix. a -- 32 bits a.b -- 8.24 bits a.b.c -- 8.8.16 bits a.b.c.d -- 8.8.8.8 bits -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:52:47 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 06 May 2009 20:52:47 -0000 Subject: [Haiku-bugs] [Haiku] #3884: IP adress format In-Reply-To: <050.c2b61cf26763f49ed7ece41e8d1cb8b2@haiku-os.org> References: <050.c2b61cf26763f49ed7ece41e8d1cb8b2@haiku-os.org> Message-ID: <059.4ecebc54d04045014168c59b67841b7d@haiku-os.org> #3884: IP adress format -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Description changed by marcusoverhagen: Old description: > Specifying the DNS address as 10.1 in Network preferences, and thus also > in /etc/resolv.conf doesn't work. It has to be written as 10.0.0.1 > > "ftp 10.1" or "telnet 10.1" in Terminal doesn't work, using "ftp > 10.0.0.1" or "telnet 10.0.0.1" works. > > Using http://10.1 in Firefox however does work. > > 10.1 is a valid address. Something is wrong, please fix. > > a -- 32 bits > a.b -- 8.24 bits > a.b.c -- 8.8.16 bits > a.b.c.d -- 8.8.8.8 bits New description: Specifying the DNS address as 10.1 in Network preferences, and thus also in /etc/resolv.conf doesn't work. It has to be written as 10.0.0.1 "ftp 10.1" or "telnet 10.1" in Terminal doesn't work, using "ftp 10.0.0.1" or "telnet 10.0.0.1" works. Using http://10.1 in Firefox however does work. 10.1 is a valid address. Something is wrong, please fix. a -- 32 bits a.b -- 8.24 bits a.b.c -- 8.8.16 bits a.b.c.d -- 8.8.8.8 bits -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:55:22 2009 From: trac at haiku-os.org (stippi) Date: Wed, 06 May 2009 20:55:22 -0000 Subject: [Haiku-bugs] [Haiku] #3361: [InstallCD] Opening DriveSetup changes target partition In-Reply-To: <042.3a316a2a295115adf11b80d6b846b130@haiku-os.org> References: <042.3a316a2a295115adf11b80d6b846b130@haiku-os.org> Message-ID: <051.c38edb6761ea8111c62cbc41a6032d2a@haiku-os.org> #3361: [InstallCD] Opening DriveSetup changes target partition -------------------------------------+-------------------------------------- Reporter: Adek336 | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Yes, the main point of this ticket is that you accidentally install to the wrong partition, but that's not the case anymore. Instead, the Begin button is disabled again and you have to conciously choose your old/new target partition. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 23:00:40 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 06 May 2009 21:00:40 -0000 Subject: [Haiku-bugs] [Haiku] #3884: short-form IP adress format broken (was: IP adress format) In-Reply-To: <050.c2b61cf26763f49ed7ece41e8d1cb8b2@haiku-os.org> References: <050.c2b61cf26763f49ed7ece41e8d1cb8b2@haiku-os.org> Message-ID: <059.f56774c323c5182887081326c7262554@haiku-os.org> #3884: short-form IP adress format broken -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by marcusoverhagen): "There are four forms of the standard numbers-and-dots notation for Internet addresses" http://www.gnu.org/software/hello/manual/libc/Abstract-Host-Addresses.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 23:09:04 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 06 May 2009 21:09:04 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.ad8aac7acd25a82b5e7377001ac415bc@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Stefan, Most of the code faults I'm talking about in updates are not system-specific at all. I'm talking about missing header declarations, missing semicolons (yes, even from your updates) and pretty obvious stuff. And they do happen with great regularity, I wasn't over-estimating the ratio of clean builds to faults. There are also outstanding reports of numerous system-crippling and crashing bugs which apparently no-one has tackled as yet. If you insist on building and operating in a Linux environment, you probably never *will* see them, but I'm using Haiku as a day-to-day development environment now. It's all very well to take a superior attitude if you're perfect, but none of us are. Going on about how YOUR time is being wasted is ridiculous when you realize that one error in the repository affects everyone who downloads it. Thus, if I see what I think is a fault I report it immediately. Even if I regularly got it wrong 50% of the time the payback in lost developer time would be well worth the effort. On that note, and having already pointed out several times that I'm providing as much information as I either: a) have available, or b) think is relevant to the faults being described, all I can say is that you are again browbeating and lecturing. You have a choice, either accept bug reports or don't, but knock off the damned whining. On another note: I'm working on a lot more than just a TV card, but don't usually make announcements until I have a working product. But since one of my specialities is DSP and software-defined radio I've been looking into porting an MP4 Enhanced HE-AAC+ (or if you prefer, AAC v2) decoder library. Australia has settled on the DAB standard for radio so I'm going to need that soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 23:19:44 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Wed, 06 May 2009 21:19:44 -0000 Subject: [Haiku-bugs] [Haiku] #3885: Live CD crash in attribute_overlay filesystem Message-ID: <048.07107e720c186eb5af2baf05c5ddb26e@haiku-os.org> #3885: Live CD crash in attribute_overlay filesystem ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I was just fooling around with the live CD and dragged some text out of AboutSystem to the desktop, and soon thereafter selected the resulting file and pressed delete, resulting in a crash. It seems to me that the system KDLs in the attribute_overlay fs when Tracker tries to move the file to trash. See attached backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:15:42 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 19:15:42 -0000 Subject: [Haiku-bugs] [Haiku] #3369: [Installer] scrollbar should be disabled if there are no additional options In-Reply-To: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> References: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> Message-ID: <049.dde9d3938c7a4180870fdfc7dd35c30e@haiku-os.org> #3369: [Installer] scrollbar should be disabled if there are no additional options ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by korli): Is this still valid with latest UI changes ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 21:28:42 2009 From: trac at haiku-os.org (diver) Date: Wed, 06 May 2009 19:28:42 -0000 Subject: [Haiku-bugs] [Haiku] #3369: [Installer] scrollbar should be disabled if there are no additional options In-Reply-To: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> References: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> Message-ID: <049.f7758f0ab4bd04bd81dbf9345da6eed8@haiku-os.org> #3369: [Installer] scrollbar should be disabled if there are no additional options ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by diver): Please close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 22:40:12 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 20:40:12 -0000 Subject: [Haiku-bugs] [Haiku] #3369: [Installer] scrollbar should be disabled if there are no additional options In-Reply-To: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> References: <040.e623ad14c2bf7e5c6ba52c557ecd1950@haiku-os.org> Message-ID: <049.ea1c24f733f2d5929cae26b575dceedb@haiku-os.org> #3369: [Installer] scrollbar should be disabled if there are no additional options -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:13:45 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 22:13:45 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.56436f92df86d6a789e64e0f13ad771b@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Old description: > I've try to use the installer to create a bootable usb key. > > These are the things I've done: > > 1. Using the "Setup partions" I inizialized all the USB drive (that is > only a single partion big as the whole drive) > 2. Then I started the installer... all files are copied > 3. The installer make the drive bootable and ask me to reboot > 4. After reboot I choose in the bios boot menu my key as bootable device > 5. Only a blinking " _ " appears... forever! > > I'm using Hailu rev. 30637 > > My system is composed by: > Cpu Athlon X2 3600+ > Motherboard Asus M2NPV-VM with integrated NVIDIA 6150 GPU > SoundCard SuondBlase Audigy > USB Key Sandisk Cruzer Micro 8 GB New description: I've try to use the installer to create a bootable usb key. These are the things I've done: {{{ 1. Using the "Setup partions" I inizialized all the USB drive (that is only a single partion big as the whole drive) 2. Then I started the installer... all files are copied 3. The installer make the drive bootable and ask me to reboot 4. After reboot I choose in the bios boot menu my key as bootable device 5. Only a blinking " _ " appears... forever! }}} I'm using Hailu rev. 30637 My system is composed by: Cpu Athlon X2 3600+ Motherboard Asus M2NPV-VM with integrated NVIDIA 6150 GPU SoundCard SuondBlase Audigy USB Key Sandisk Cruzer Micro 8 GB -- Comment(by mmlr): It's a big difference between a device with a single partition on it and a device that has no partition at all. The approach you took can only work when there is no partition on the device, meaning that the raw device directly contains the filesystem with no partition table before it. If you have a master boot record with a partition table and then a single partition then only the partition will be made bootable. What is missing is a bootloader, in the same sense as you would need one when installing to a harddisk. Installing to the raw device directly only happens to work because the partition boot code that makes the partition bootable will then be written to the first sector so that the BIOS can turn over the control to it. If indeed have an MBR and a single partition on that device, then this is not a bug. You're then just missing a bootloader. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 20:09:10 2009 From: trac at haiku-os.org (rudolfc) Date: Wed, 06 May 2009 18:09:10 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.04b56c6cb6b100c7093babf832b00ddd@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi again, For completeness, I am posting the 'malfunctioning' monitor's relevant specs here: HP LP2465 Display, Maximum Pixel Rate 202 MHz (VGA input), 162 MHz (DVI input) Horizontal scan rates Horizontal Frequency: 30-94 kHz (VGA input), 30 to 92 KHz (DVI input); Vertical Frequency: 48-85 Hz (VGA and DVI input) Display resolution 1920 x 1200 @ 60 Hz (analog and digital) Video input connector Two DVI-I (VGA analog and digital) inputs Input signal VGA to DVI-I, DVI-D to DVI-D, cables included Seeing the resolution, probably a dual-link DVI cable is needed to display the panel's native resolution over DVI. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 6 20:01:26 2009 From: trac at haiku-os.org (korli) Date: Wed, 06 May 2009 18:01:26 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.2d90421d2a5742de2c6cfe6a3502e7dc@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by korli): Just tried myself for the first time, booted correctly in qemu. Fishy. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:32:59 2009 From: trac at haiku-os.org (fano) Date: Wed, 06 May 2009 22:32:59 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.97f4853a2f2d20a15676bc6193631694@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by fano): So using the "Inizialize" command in Setup Partition I have created a partition on it? Or no? This is a little unclear for me... How can I "reset" the usb key to have no partition on hit and using the installer in the right way? I think I must use a third party partitioner... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:37:15 2009 From: trac at haiku-os.org (fano) Date: Wed, 06 May 2009 22:37:15 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.81cd03f7f80ee76fd0a7705b9f3e3d5a@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by fano): I forgotten to say for the dd thing I have to use the haiku.image file, right? I can't dd from the Live CD to USB directly (the CD should be in iso) so the command is: dd bs=512 if=haiku.image of=/dev/disk/usb/0/0/raw -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:46:12 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 22:46:12 -0000 Subject: [Haiku-bugs] [Haiku] #3885: Live CD crash in attribute_overlay filesystem In-Reply-To: <048.07107e720c186eb5af2baf05c5ddb26e@haiku-os.org> References: <048.07107e720c186eb5af2baf05c5ddb26e@haiku-os.org> Message-ID: <057.6245a112236508e64e5ff03ef559c8af@haiku-os.org> #3885: Live CD crash in attribute_overlay filesystem ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: It's probably due to the complete lack of locking in both attribute and write overlay. It's a todo on my list. BTW the crash happens in write_overlay below the attribute_overlay, it doesn't really matter though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:49:47 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 06 May 2009 22:49:47 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.3b593f6863771ec69fe7dbd97df3ceb6@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): pthread_getattr_np() is a non-standard GNU extension. I'm unsure whether we should provide it. Besides I wouldn't implement it by using the cached pthread creation attributes, but rather by collecting the info at that time. Most attributes we don't really support anyway -- so those can get the default values -- the stack address and size can be retrieved via get_thread_info(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 00:55:57 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 06 May 2009 22:55:57 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.874ba6433c6b098471d563d3f36f3137@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by mmlr): It probably already had a partition on the device before. In DriveSetup you may be able to select the whole device instead of the partition and do the initialization on that instead. Not sure DriveSetup allows that though. And yeah, for dd you'd use the haiku.image file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 02:39:47 2009 From: trac at haiku-os.org (HaikuBot) Date: Thu, 07 May 2009 00:39:47 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT Message-ID: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Can't boot haiku on my PC without safe-mode option "use fail-safe video mode". I can't run a resolution of 1680x1050 on my PC and so I'm using Vesa instead. Graphic Card - PCI-E MSI GeForce 7300 GT 256Mb. "listdev" and "syslog" in attachments. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 03:22:29 2009 From: trac at haiku-os.org (bga) Date: Thu, 07 May 2009 01:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.bb4c9a2c39159bdb2f3b29847e0b9620@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bga): FYI, my problem is indeed exactly the same as the one reported by stippi: {{{ 2009-05-06 22:01:57 KERN: usb uhci: process error 2009-05-06 22:01:57 KERN: usb uhci: host controller halted 2009-05-06 22:01:59 KERN: usb error control pipe 65: timeout waiting for queued request to complete 2009-05-06 22:01:59 KERN: usb error hub 64: error updating port status 2009-05-06 22:02:00 KERN: usb error control pipe 65: timeout waiting for queued request to complete 2009-05-06 22:02:00 KERN: usb error hub 64: error updating port status 2009-05-06 22:02:01 KERN: usb error control pipe 65: timeout waiting for queued request to complete }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 03:23:30 2009 From: trac at haiku-os.org (bga) Date: Thu, 07 May 2009 01:23:30 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.b66af7f79f06a5a613b47474cfedd79a@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bga): BTW, this time it happened with a 30 minute uptime more or less. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 04:38:36 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 02:38:36 -0000 Subject: [Haiku-bugs] [Haiku] #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY Message-ID: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- BMenuItem contains glyph definitions and such for B_CONTROL_KEY, B_COMMAND_KEY and B_SHIFT_KEY, but not B_OPTION_KEY. As a consequence, any menu item using the key in its modifiers has its shortcut misrepresented, most notably tracker add-ons, as those use opt+cmd+letter. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 04:49:05 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 02:49:05 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.392f4d04479be7b89998393a55e175da@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Replying to [comment:7 jackburton]: > Well, from a first look, when clicking on the item with the mouse, the code path which triggers the call to BMenuItem::Invoke() is inside MenuBar.cpp (lines 642 - 650): > while when using the keyboard, the code path is completely different, and doesn't lock the looper That's to be expected though, BView::KeyDown is called with the looper locked implicitly. The problem here though is that deskbar's WindowMenuItem is calling an operation on the *parent* menu's window, not the window it's sitting in. In the mouse case the parent also appears to be locked, while in the keydown case it isn't, which causes the debugger() call to be triggered. What I can't figure out is what's locking the parent window in the mouse case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 09:34:00 2009 From: trac at haiku-os.org (stippi) Date: Thu, 07 May 2009 07:34:00 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.1afb530f8a2aa23354f776e0ab1108ce@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): In theory yes, 1920x1200 would require a dual link cable, but in practice, this resolution is supported by single link connections anyways. I don't remember exactly what, but "something" is reduced to make this possible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 09:36:09 2009 From: trac at haiku-os.org (umccullough) Date: Thu, 07 May 2009 07:36:09 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.31335867a0301c789f870019e9931e8e@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by umccullough): And I even run 1920x1200 via analog VGA through a KVM switch using a multitude of various machines ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 09:52:16 2009 From: trac at haiku-os.org (stippi) Date: Thu, 07 May 2009 07:52:16 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.9ca65a1c828ad80c2119482f4dd82abb@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Rob, you obviously lack the mental flexibility to realize that you are even more of a whiner than me. Also, you repeatedly don't give me credit for trying to be polite, so I won't even bother anymore. It only comes across as lecturing to you. My fault for even trying to point out something you could do better. Old people almost never take that well, they are always right and everyone else is the idiot. So if someone forgets to commit a header it means he has not tested his work? If someone breaks the GCC4 build it means he has not tested his changes on his GCC2 build either, right? And boy how embarrassed I am for commiting that DriveSetup change where I forgot the semicolon. Happens all the time for me personally, I think it's even more than 8 out of 10 times. I should just stop coding, I make life miserable for everyone else by commiting the crap I produce. -Ste*ph*an. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 10:02:15 2009 From: trac at haiku-os.org (stippi) Date: Thu, 07 May 2009 08:02:15 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.f0c3db0c632f0ba1e0fb141e1cf78623@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): Yes DriveSetup allows you to initialize the whole device, but for that, no partition table needs to exist. DriveSetup is incapable of any change that would change the table, including deleting an existing table or creating one when there is none yet. When you dd an image onto the stick raw device, you also delete the partition table, IIRC. So that would be an option. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 10:02:24 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 08:02:24 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.173c1e9a7c344a4ced9aeee60bee26b2@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): Some issues with this ISO image are fixed in r30655. However, the file data and length is still bogus - apparently, we don't support ISO level 3 extents. The archive manager/mounter combo under Ubuntu also has its problems with this ISO, btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 10:06:24 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 08:06:24 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.8b45ae22e789d3da30bc6778563fd8aa@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): On second thought, though, it can't really be an ISO level 3 problem, as the highest bit of the flags field is not set. Maybe something with the block size; the files are not just too small, they also seem to have the wrong contents; the actual file content does not contain whatever we see in Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 10:29:38 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Thu, 07 May 2009 08:29:38 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.203adee4bf369edd6e2cd12be3fd2b2a@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by marcusoverhagen): Umccullough please don't make unrelevant bullshit comments. Rudolf I replaced the card with a ATI X300 inbetween, but I still have it somewhere and can probably run a test at the weekend. The resolution of 1920x1200 does indeed only need a single link cable as both card and TFT support reduced blanking. The setup was working well with Linux and Windows. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 15:01:04 2009 From: trac at haiku-os.org (bga) Date: Thu, 07 May 2009 13:01:04 -0000 Subject: [Haiku-bugs] [Haiku] #3876: DHCP does not work. In-Reply-To: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> References: <038.347e4edc8281c4e05b8c6297fe9ea074@haiku-os.org> Message-ID: <047.95bb57e76479bbe7dffde01d402b5aab@haiku-os.org> #3876: DHCP does not work. --------------------------------------+------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/IPv4 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: Fixed in r30656. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 15:49:38 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 13:49:38 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.f193ed86af6d7b97c2d99299b9dd78d5@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): Hey Marcus, behave yourself! Even if VGA has little to do with DVI, no need for insults. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 16:19:12 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 14:19:12 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.e2c3fa24542a25461999b839f582b0e6@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): Replying to [comment:14 axeld]: > On second thought, though, it can't really be an ISO level 3 problem, as the highest bit of the flags field is not set. Maybe something with the block size; the files are not just too small, they also seem to have the wrong contents; the actual file content does not contain whatever we see in Haiku. Would it help debugging at all to have another ISO to compare against with a different set of files? Nice work so far in any case :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 16:20:05 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 14:20:05 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.a1989c76a316180ad57a14c123924405@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by anevilyak): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 16:30:23 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 14:30:23 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.90a64b0d80586f8d5d7a09b5782e001a@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac -----------------------------------+---------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): No thanks, I guess besides time I have everything I need :-) Maybe someone else comes along with a fix in the mean time ;-)) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 17:33:36 2009 From: trac at haiku-os.org (bbjimmy) Date: Thu, 07 May 2009 15:33:36 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file In-Reply-To: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> References: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> Message-ID: <051.69b943f0c4a27750d9a40f331ac1b1cb@haiku-os.org> #3882: system freezes opening file ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by bbjimmy): * component: - General => Applications/Tracker Comment: This same error happens randomly while using tracker to copy or move files. I beleive this has to do with identifying the file type. This file that will always cause the problem is bytes and holds program information for an old dos application. The data is all ascii text. In this case about spaces (20) followed by all 00 to fill out the 100 bytes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 19:45:05 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 07 May 2009 17:45:05 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.33024c8bc28c8f3d539d733231197582@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi guys! Glad to hear that Marcus! I would be curious to the results. For isntance: - Would the driver nowadays 'just work'for your setup? - would the driver work if you tell Haiku to use another resolution via the VESA call by the kernel during boot-up (iconscreen), like use 16 bit instead of 32, use say 1024x768x18 instead of the default resolution. - What resolution is used by haiku as default during bootup? - I'd love to see a full logfile from the driver (have nvidia.settings in the home folder and enable 'full logging', reboot and grab resulting logfile from home folder. - Would your monitor work using the VGA connection? - Could you send me a photo of what your screen looks like when trouble arises? Shall I re-enable the card already? I mean, it's indeed working OK. Apparantly it's the combination of your screen and the driver that causes the trouble. Maybe specifically because of the high resolution.. Things might go wrong because the card BIOS sets a lower than native modeline for your card, and if you instruct the driver to do above that: it won't work. And maybe, because haiku now switches the card during bootup, it's now set to the native modeline and might just work OK as a sideeffect of that. As you see: lots of questions from my part :-) If you find some time to do at least some tests, that would be helpfull. So let me know if I should re-enable the card, or someone else just do it :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 20:02:24 2009 From: trac at haiku-os.org (bbjimmy) Date: Thu, 07 May 2009 18:02:24 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file In-Reply-To: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> References: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> Message-ID: <051.04d6c6b79d2bca16767b4121fb0fb9e7@haiku-os.org> #3882: system freezes opening file ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by bbjimmy): r30656 seems to have corrected the issue. Now I get a pannel that says"Could not open "TACT2008.ROP" with application "Tracker" (Invalid Argument). Would you like to find another application? [Cancel] [Find] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 20:26:27 2009 From: trac at haiku-os.org (fano) Date: Thu, 07 May 2009 18:26:27 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.6bb6108eb969393997a8e4bda2b60e1e@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by fano): Nothing to do... I've started the compilation of the r30637 in my VmWare system this morning... but when I returned home the VM-System was frozed!!! I've rebooted and the compiler says "No space left on device!" But df says that i have 12 Gb of free space was 12 GB... This is the log: {{{ jam haiku-image [...] BuildHaikuImage1 generated/haiku.image build/scripts/build_haiku_image: line 38: [: /boot/home/Desktop/Haiku: unary operator expected Creating image ... Writing boot code to "generated/haiku.image" (partition offset: 0 bytes, start offset = 0) ... Populating image ... Unzipping generated/download/Beam.zip ... Unzipping generated/download/BePDF-1.1.1b1.x86.zip ... Error while writing to file `/myfs/apps/BePDF/encodings/xpdf-chinese- simplified/CMap/UniGB-UCS2-H': No space left on device Error: Command failed: No space left on device Error: Command was: cp -f -r :generated/tmp/unzip/. /myfs/apps Unzipping generated/download/BeZillaBrowser-gcc2-20090218.zip ... Error while writing to file `/myfs/apps/BeZillaBrowser/BeZillaBrowser': No space left on device Error: Command failed: No space left on device Error: Command was: cp -f -r :generated/tmp/unzip/. /myfs/apps [...OMITTED] mkdir -p /myfs/home/config/settings/beos_mime Installing MIME database ... Error: Failed to create `/myfs/home/config/settings/beos_mime': No space left on device Error: Command failed: No space left on device Error: Command was: cp -f -r :generated/tmp/mime/db/. /myfs/home/config/settings/beos_mime Error while writing to attribute `COPYRIGHTS' of file `/myfs/system/apps/AboutSystem': No space left on device Error: Command failed: No space left on device Error: Command was: cp -a :generated/tmp/copyrightAttrs /myfs/system/apps/AboutSystem Unmounting ... ...updated 480 target(s)... }}} I could download the r30637 raw image but is not present... maybe I could use the last raw image (I thing nothing is changed in this front) but I think that in this way (maybe) the test is not reliable.. What you think? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 20:29:15 2009 From: trac at haiku-os.org (bga) Date: Thu, 07 May 2009 18:29:15 -0000 Subject: [Haiku-bugs] [Haiku] #3882: system freezes opening file In-Reply-To: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> References: <042.8b5271b603816af96e44d8cef2ab0581@haiku-os.org> Message-ID: <051.a5385e96dc882ef84c2b8e702f3f7d31@haiku-os.org> #3882: system freezes opening file ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by bga): That is really not possible. :) It is a completely unrelated change. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:10:30 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:10:30 -0000 Subject: [Haiku-bugs] [Haiku] #1728: PANIC: supposed to be free page 0x95b76524 has cache In-Reply-To: <050.ab9679fe9213399a00e837924ca42738@haiku-os.org> References: <050.ab9679fe9213399a00e837924ca42738@haiku-os.org> Message-ID: <059.fff76eb3ea95f55beaa850f89598c2ad@haiku-os.org> #1728: PANIC: supposed to be free page 0x95b76524 has cache ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: I guess this one can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:12:16 2009 From: trac at haiku-os.org (jackburton) Date: Thu, 07 May 2009 19:12:16 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.e647c0c32524c5c03b2a1de7baa51f14@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by jackburton): But it's still caused by the different code path, see: In the first case, the BMenuBar is the one which calls InvokeItem(), and in that case, it locks the BMenuBar's window, not the BMenu window. In the latter case, InvokeItem() is called by BMenu itself, and the BMenuBar window is not locked, since BMenuBar::_Track() explicitly unlocks the BMenuBar window before calling _track() on the submenu. I guess we should change something in BMenu::Keydown() or in BMenu::InvokeItem(). I'll try to have a look, but we best would have to look at how beos handled this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:17:10 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:17:10 -0000 Subject: [Haiku-bugs] [Haiku] #1515: Pagefault in arch_thread_init_kthread_stack In-Reply-To: <050.23857671f43e493322603210ef192649@haiku-os.org> References: <050.23857671f43e493322603210ef192649@haiku-os.org> Message-ID: <059.d2537333d802db18146f258071c64b40@haiku-os.org> #1515: Pagefault in arch_thread_init_kthread_stack ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This one has probably been fixed in the mean time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:17:36 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:17:36 -0000 Subject: [Haiku-bugs] [Haiku] #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 In-Reply-To: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> References: <050.cf5d1b9f443466d42054d4cd33038454@haiku-os.org> Message-ID: <059.8a1ae9ef4fcbb503362af13e864428f7@haiku-os.org> #1511: PANIC: ASSERT FAILED (src/system/kernel/arch/x86/arch_thread.c:68): stack->index < 4 ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Seems to be gone, too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:17:43 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #1514: PANIC: no range for address 0xffd283ff In-Reply-To: <050.a35e9f7b51b0b82a7728f60871f0e762@haiku-os.org> References: <050.a35e9f7b51b0b82a7728f60871f0e762@haiku-os.org> Message-ID: <059.c7a4c4a4579c6899f19b1244865494f3@haiku-os.org> #1514: PANIC: no range for address 0xffd283ff ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This one has probably been fixed in the mean time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:18:22 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:18:22 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.4474aa9daa828cfd00ae83104811646b@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by axeld): Unfortunately I don't have a USB KVM, and I also haven't seen this bug yet. Feel free to investigate :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:19:54 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:19:54 -0000 Subject: [Haiku-bugs] [Haiku] #1452: Sudoku locks up when trying to solve puzzle I entered from a book In-Reply-To: <042.8c34e6b972f6f38fab6ce591c15273fe@haiku-os.org> References: <042.8c34e6b972f6f38fab6ce591c15273fe@haiku-os.org> Message-ID: <051.40d5699076b813cd874999cd1a50f661@haiku-os.org> #1452: Sudoku locks up when trying to solve puzzle I entered from a book ----------------------------------+----------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: low | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:23:44 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:23:44 -0000 Subject: [Haiku-bugs] [Haiku] #3320: [CodyCam] display alert in a video view In-Reply-To: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> References: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> Message-ID: <049.ab4e4fc9517d0217e9886c1be0ace45e@haiku-os.org> #3320: [CodyCam] display alert in a video view -----------------------------------+---------------------------------------- Reporter: diver | Owner: mmu_man Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CodyCam | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Changes (by axeld): * owner: axeld => mmu_man * status: reopened => new Comment: mmu_man will more likely work on that one than me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:27:43 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:27:43 -0000 Subject: [Haiku-bugs] [Haiku] #3812: Icons are often invisible when dragging In-Reply-To: <040.0a387b8a8ef66fa3785d21e84237dfc1@haiku-os.org> References: <040.0a387b8a8ef66fa3785d21e84237dfc1@haiku-os.org> Message-ID: <049.71a6c7ae7e11797c29f6731c937fe8fb@haiku-os.org> #3812: Icons are often invisible when dragging ----------------------------------+----------------------------------------- Reporter: axeld | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by axeld): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:27:53 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:27:53 -0000 Subject: [Haiku-bugs] [Haiku] #3828: Icon positioning/selection got screwed up. In-Reply-To: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> References: <038.25572c08b2bff5b5bc56843e7ea4daf8@haiku-os.org> Message-ID: <047.0a0f11c63b0c32fde88d854c364943b2@haiku-os.org> #3828: Icon positioning/selection got screwed up. ----------------------------------+----------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by axeld): * owner: axeld => stippi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:29:23 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 19:29:23 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.a21895e829055d0521fa708674173d6c@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): The Deskbar code in question worked in BeOS, but yeah, I'm not sure either. It seems as if we'd need to guarantee that the whole menu chain is locked when calling Invoke(). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:29:44 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:29:44 -0000 Subject: [Haiku-bugs] [Haiku] #3316: [Workspaces] window moves on workspaces switch In-Reply-To: <040.03b6282dcf5e455d6cef89c795a7d922@haiku-os.org> References: <040.03b6282dcf5e455d6cef89c795a7d922@haiku-os.org> Message-ID: <049.8b375ce157fd0a744ac2f816cc97acb7@haiku-os.org> #3316: [Workspaces] window moves on workspaces switch --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Workspaces | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Workspaces has (like almost any other window) a position per workspace (which is also needed, since workspaces can have different resolutions). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:32:12 2009 From: trac at haiku-os.org (mjw) Date: Thu, 07 May 2009 19:32:12 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.f9e1a7eb72bc6a027549d1de3c15537a@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by mjw): Not quite an absolute "no", then. Would it be more acceptable if I were to re-work the patch, removing pthread_getattr_np() and not caching the pthread_attr in pthread_create()? So, the following would be valid: pthread_attr_init(attr) pthread_create(..., &attr, ...) pthread_attr_getstack(&attr) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:34:06 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:34:06 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder In-Reply-To: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> References: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> Message-ID: <050.7e070d0ee1b75dded1d08a911024cf9c@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): From the output it looks like some index is messed up. You could check your B+trees using the chkindex tool (part from the BFS tools). Also, turning on BFS + block cache tracing might help when we're on the same location next time :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:34:36 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:34:36 -0000 Subject: [Haiku-bugs] [Haiku] #2707: cannot mount ext3 file system In-Reply-To: <042.b4da1de607c6ce627ee5312c112cccb1@haiku-os.org> References: <042.b4da1de607c6ce627ee5312c112cccb1@haiku-os.org> Message-ID: <051.da949e8f7b27b6f66581eb9ef6136557@haiku-os.org> #2707: cannot mount ext3 file system --------------------------------+------------------------------------------- Reporter: Adek336 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/ext2 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:35:06 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:35:06 -0000 Subject: [Haiku-bugs] [Haiku] #1589: Fat file system recognized by mount, but NOT mountvolume and tracker In-Reply-To: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> References: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> Message-ID: <053.78b30e9e3edf680eca3bebf914c413a9@haiku-os.org> #1589: Fat file system recognized by mount, but NOT mountvolume and tracker ------------------------------+--------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Can you still reproduce this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:36:19 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:36:19 -0000 Subject: [Haiku-bugs] [Haiku] #3152: Mouse (trackpad) used to work fine - now unreliable. In-Reply-To: <040.6c347bd01e6c99b2176a300de431e6aa@haiku-os.org> References: <040.6c347bd01e6c99b2176a300de431e6aa@haiku-os.org> Message-ID: <049.317ffcabc5ce48a2b356aa9c6fa80228@haiku-os.org> #3152: Mouse (trackpad) used to work fine - now unreliable. -------------------------------+-------------------------------------------- Reporter: alban | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by axeld): * owner: axeld => marcusoverhagen * component: - General => Drivers/Mouse/PS2 Old description: > The mouse (trackpad) is much less reliable in very recent Haiku releases. > The mouse pointer sometimes hangs or freezes during or shortly after > startup. > mouse buttons are not responsive; there is a delay between clicking a > button and the action taking place. This makes the user interface hard to > use. > > Syslog shows:- > KERN: ps2_hid: init_hardware > KERN: ps2_hid: init_driver > KERN: ps2: active multiplexing v1.1 enabled > 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: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff > KERN: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff > KERN: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff > KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = > 0x00000000 > KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 > KERN: ps2: keyboard found > KERN: ps2: probe_mouse Standard PS/2 mouse found > KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = > 0x00000000 > KERN: ps2_hid: init_hardware > KERN: ps2_hid: init_driver > KERN: ps2: active multiplexing v1.1 enabled > 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: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff > KERN: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff > KERN: ps2: reset failed > KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff > KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = > 0x00000000 > KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 > KERN: ps2: keyboard found > KERN: ps2: probe_mouse Standard PS/2 mouse found > KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = > 0x00000000 New description: The mouse (trackpad) is much less reliable in very recent Haiku releases. The mouse pointer sometimes hangs or freezes during or shortly after startup. mouse buttons are not responsive; there is a delay between clicking a button and the action taking place. This makes the user interface hard to use. Syslog shows:- {{{ KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2: active multiplexing v1.1 enabled 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: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000 KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000 KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2: active multiplexing v1.1 enabled 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: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000 KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000 }}} -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:40:29 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:40:29 -0000 Subject: [Haiku-bugs] [Haiku] #3714: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:467): fFirst != __null && fLast != __null && (fFirst != fLast || In-Reply-To: <044.b895a903feeac90c24ca3a36c14db02e@haiku-os.org> References: <044.b895a903feeac90c24ca3a36c14db02e@haiku-os.org> Message-ID: <053.01a2fc2e551f506cc71c959e5d9c170f@haiku-os.org> #3714: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:467): fFirst != __null && fLast != __null && (fFirst != fLast || ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3748 ---------------------------------------+------------------------------------ Changes (by axeld): * status: new => closed * resolution: => fixed Comment: IIRC I've fixed this already, but if not, please reopen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:41:06 2009 From: trac at haiku-os.org (jackburton) Date: Thu, 07 May 2009 19:41:06 -0000 Subject: [Haiku-bugs] [Haiku] #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY In-Reply-To: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> References: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> Message-ID: <053.6e0cf9999c2619b5959eda7c60253f0e@haiku-os.org> #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by jackburton): * owner: axeld => jackburton Comment: I'm on it -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:41:15 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:41:15 -0000 Subject: [Haiku-bugs] [Haiku] #3259: Bug in setting "Always Show Triggers" In-Reply-To: <044.436c3cc1535113e8a7c256482ab1fc16@haiku-os.org> References: <044.436c3cc1535113e8a7c256482ab1fc16@haiku-os.org> Message-ID: <053.19edca426a83c2bcbf77ea9fca085e99@haiku-os.org> #3259: Bug in setting "Always Show Triggers" -------------------------------+-------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Menu preferences are gone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:41:14 2009 From: trac at haiku-os.org (jackburton) Date: Thu, 07 May 2009 19:41:14 -0000 Subject: [Haiku-bugs] [Haiku] #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY In-Reply-To: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> References: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> Message-ID: <053.7b936b11f41cc5c96863eccc382b0f65@haiku-os.org> #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY --------------------------------+------------------------------------------- Reporter: anevilyak | Owner: jackburton Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by jackburton): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:41:19 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 07 May 2009 19:41:19 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.3ff27383d99fd8739cfc0cd49a32c620@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, Could you grab the file nvidia.settings from the source (nvidia kernel driver) and place that in your home folder, and disable the acceleration engine? If you do that and reboot without using failsafe video, the driver will attempt to run without using hardware acceleration for the desktop. Does that work? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:42:07 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 19:42:07 -0000 Subject: [Haiku-bugs] [Haiku] #3714: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:467): fFirst != __null && fLast != __null && (fFirst != fLast || In-Reply-To: <044.b895a903feeac90c24ca3a36c14db02e@haiku-os.org> References: <044.b895a903feeac90c24ca3a36c14db02e@haiku-os.org> Message-ID: <053.6bf59caaa59bfe71ccd99b9bdb6273f0@haiku-os.org> #3714: PANIC: ASSERT FAILED (headers/private/kernel/util/DoublyLinkedList.h:467): fFirst != __null && fLast != __null && (fFirst != fLast || ---------------------------------------+------------------------------------ Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3748 ---------------------------------------+------------------------------------ Comment(by anevilyak): I haven't seen it in ages either so most likely fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:47:02 2009 From: trac at haiku-os.org (jackburton) Date: Thu, 07 May 2009 19:47:02 -0000 Subject: [Haiku-bugs] [Haiku] #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY In-Reply-To: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> References: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> Message-ID: <053.461a8bf8d2902f5389691f5050b060b1@haiku-os.org> #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY ---------------------------------+------------------------------------------ Reporter: anevilyak | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by jackburton): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30661. The look of the labels could be improved, though. Even better would be to draw them using drawing commands instead of bitmaps, so they would scale with the font size. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:49:04 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 19:49:04 -0000 Subject: [Haiku-bugs] [Haiku] #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY In-Reply-To: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> References: <044.0f37b0ad25ca4c971d26cd39e63e1b0f@haiku-os.org> Message-ID: <053.a7262347121c09b87fdb9182bd416277@haiku-os.org> #3887: BMenuItem is missing the ability to draw the modifier indicator for B_OPTION_KEY ---------------------------------+------------------------------------------ Reporter: anevilyak | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Comment(by anevilyak): Replying to [comment:3 jackburton]: > Fixed in r30661. The look of the labels could be improved, though. Even better would be to draw them using drawing commands instead of bitmaps, so they would scale with the font size. Thanks! And yeah, I was thinking that too, but my skills with drawing code that actually looks eye pleasing leave some to be desired. That probably also be desirable for the internationalization GSoC project, since that'd allow us to draw localized names for the different keys. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:49:23 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:49:23 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.0c74b56e6fb7b4c6c0742d3c96ea405f@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): AFAIK BeOS R5 had the same problem, it might have been fixed in Dano, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 21:58:40 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 19:58:40 -0000 Subject: [Haiku-bugs] [Haiku] #3281: ffs() arch optimization In-Reply-To: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> References: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> Message-ID: <047.bc92d0fc1ae6a519c086facc55da74fd@haiku-os.org> #3281: ffs() arch optimization -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by axeld): * priority: normal => low * type: bug => enhancement -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:14:55 2009 From: trac at haiku-os.org (jackburton) Date: Thu, 07 May 2009 21:14:55 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.d8599b363e89795192c70581597d4853@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by jackburton): I fixed the problem in r30662 by locking the root menu's looper before Invoke(). Somehow, though, I don't feel it's so nice, since it could introduce deadlocks in some cases... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:15:56 2009 From: trac at haiku-os.org (PieterPanman) Date: Thu, 07 May 2009 21:15:56 -0000 Subject: [Haiku-bugs] [Haiku] #1589: Fat file system recognized by mount, but NOT mountvolume and tracker In-Reply-To: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> References: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> Message-ID: <053.8984d327452147c07b3c0452bae9a1a4@haiku-os.org> #1589: Fat file system recognized by mount, but NOT mountvolume and tracker ------------------------------+--------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by PieterPanman): Ow heh, this is old... A few days ago I was able to mount a freshly created fat32 compact flash through a usb reader, so it works now. Can't test it now, but this must also mean it works with mountvolume. I believe it can be closed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:38:35 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Thu, 07 May 2009 21:38:35 -0000 Subject: [Haiku-bugs] [Haiku] #3152: Mouse (trackpad) used to work fine - now unreliable. In-Reply-To: <040.6c347bd01e6c99b2176a300de431e6aa@haiku-os.org> References: <040.6c347bd01e6c99b2176a300de431e6aa@haiku-os.org> Message-ID: <049.cd3fda071bc8b03365f91497141eae50@haiku-os.org> #3152: Mouse (trackpad) used to work fine - now unreliable. -------------------------------+-------------------------------------------- Reporter: alban | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/PS2 | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by marcusoverhagen): * owner: marcusoverhagen => stippi Comment: I don't understand this. Why are we publishing a standard and a synaptics mouse at the same time and at the same index? Is this even supported? I only did the standard mouse part. Because stippi committed the patch with r28643 I'm reassigning it KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000 KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:39:11 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 21:39:11 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.9b727fd69c012e35f503128fb016581d@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac ------------------------------------+--------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30663. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:39:27 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Thu, 07 May 2009 21:39:27 -0000 Subject: [Haiku-bugs] [Haiku] #1728: PANIC: supposed to be free page 0x95b76524 has cache In-Reply-To: <050.ab9679fe9213399a00e837924ca42738@haiku-os.org> References: <050.ab9679fe9213399a00e837924ca42738@haiku-os.org> Message-ID: <059.809cf7eecad999bb4fb4112839b20e68@haiku-os.org> #1728: PANIC: supposed to be free page 0x95b76524 has cache ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: blocker | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by marcusoverhagen): yes, wasn't reproduceable anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 7 23:50:27 2009 From: trac at haiku-os.org (axeld) Date: Thu, 07 May 2009 21:50:27 -0000 Subject: [Haiku-bugs] [Haiku] #1589: Fat file system recognized by mount, but NOT mountvolume and tracker In-Reply-To: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> References: <044.49c7240888e2cbfa457e079b98c2cf51@haiku-os.org> Message-ID: <053.c9038830539f4c85eb0ae098e29a0bca@haiku-os.org> #1589: Fat file system recognized by mount, but NOT mountvolume and tracker -------------------------------+-------------------------------------------- Reporter: pieterpan | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/FAT | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Okay, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 00:11:17 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 22:11:17 -0000 Subject: [Haiku-bugs] [Haiku] #3861: iso9660 has issues with various discs burned on a mac In-Reply-To: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> References: <044.1ee563a7e13da53ee9ba873738f15ee3@haiku-os.org> Message-ID: <053.c9b4e91ca2c81e98dd0541944b6a25f6@haiku-os.org> #3861: iso9660 has issues with various discs burned on a mac ------------------------------------+--------------------------------------- Reporter: anevilyak | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/ISO 9660 | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by anevilyak): Nice work! Thanks Axel :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 00:36:26 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 22:36:26 -0000 Subject: [Haiku-bugs] [Haiku] #3888: [Tracker] file list flickering on window resize Message-ID: <040.1d4c13236d33b209fdde5964ea72425a@haiku-os.org> #3888: [Tracker] file list flickering on window resize ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- To reproduce: Leaf menu->Find...[Enter] While list is populating start windows resizing. You should see lots of flickering here. When population is done there will no more flickering. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 00:45:59 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 22:45:59 -0000 Subject: [Haiku-bugs] [Haiku] #3889: [Tracker] "Open with" window redraw issue Message-ID: <040.fcb6f909c9c0452fd05273b4a97a51da@haiku-os.org> #3889: [Tracker] "Open with" window redraw issue ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Right click Home icon on desktop and select "Open with..."[[BR]] Resize "Open with" window horizontally until bottom scrollbar disappear.[[BR]] Double click column separator between "Relation" and "Location"[[BR]] Double click column separator between "Location" and "Version"[[BR]] r30663 in vbox. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 00:50:43 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 22:50:43 -0000 Subject: [Haiku-bugs] [Haiku] #3890: [Interface Kit] color picker have some drawing bugs Message-ID: <040.261e06ee84b5e1654555740a8d0b41a6@haiku-os.org> #3890: [Interface Kit] color picker have some drawing bugs --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Color picker have some drawing bugs, see screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 00:56:10 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 22:56:10 -0000 Subject: [Haiku-bugs] [Haiku] #3891: [Terminal] Settings window ask to save settings if font was changed to itself Message-ID: <040.e49811a8e70fdb33a0686b031d700504@haiku-os.org> #3891: [Terminal] Settings window ask to save settings if font was changed to itself -----------------------------------+---------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Settings window in Terminal ask to save settings if font was changed to itself.[[BR]] On a related note, shouldn't there be Defaults and Revert buttons? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:00:17 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:00:17 -0000 Subject: [Haiku-bugs] [Haiku] #3892: [Keymap] return key should have transparent background Message-ID: <040.307f0e2350314406056c2d951750b06f@haiku-os.org> #3892: [Keymap] return key should have transparent background --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Return key should have transparent background while moving. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:03:45 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:03:45 -0000 Subject: [Haiku-bugs] [Haiku] #3893: [Installer] "Please Choose Target" menu item is truncated Message-ID: <040.d33713ecdd3e8632fa208ee0d40849e6@haiku-os.org> #3893: [Installer] "Please Choose Target" menu item is truncated ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- "Please Choose Target" menu item is truncated. See screenshot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:06:02 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:06:02 -0000 Subject: [Haiku-bugs] [Haiku] #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" Message-ID: <040.b451842dd8542696e0492ce6de14f7f4@haiku-os.org> #3894: [Installer] Haiku logo shifts after toggling "Show Optional Packages" ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Haiku logo shifts after toggling "Show Optional Packages" -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:08:00 2009 From: trac at haiku-os.org (HaikuBot) Date: Thu, 07 May 2009 23:08:00 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.d8f5791b1dbdcadf63a8a50f89c0486a@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Hello. I put it in home directory and disabled acceleration. Unfortunately, does not work, says same as before "No signal" then "Input not supported". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:09:55 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:09:55 -0000 Subject: [Haiku-bugs] [Haiku] #3895: [Terminal] jumping text after font change Message-ID: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> #3895: [Terminal] jumping text after font change ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- I changed font from "DejaVu Sans Mono" to "DejaVu Sans" and terminal output became a mess. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:12:40 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:12:40 -0000 Subject: [Haiku-bugs] [Haiku] #3320: [CodyCam] display alert in a video view In-Reply-To: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> References: <040.5c3f491aaf76a33aaed4f0e9875b56d9@haiku-os.org> Message-ID: <049.ef21a9ae23e6b0d473f8299163f90113@haiku-os.org> #3320: [CodyCam] display alert in a video view -----------------------------------+---------------------------------------- Reporter: diver | Owner: mmu_man Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/CodyCam | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by diver): On a related note: I think video view could use a tiny border. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:13:33 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:13:33 -0000 Subject: [Haiku-bugs] [Haiku] #3896: [DeskCalc] initial window is too small Message-ID: <040.f056a1da918675767af017c2fbd23cfd@haiku-os.org> #3896: [DeskCalc] initial window is too small -----------------------------------+---------------------------------------- Reporter: diver | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DeskCalc | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:15:44 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 07 May 2009 23:15:44 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.49649d6b5830a2ad1f24e72469f0fea1@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): Replying to [comment:2 mjw]: > Not quite an absolute "no", then. > > Would it be more acceptable if I were to re-work the patch, removing pthread_getattr_np() and not caching the pthread_attr in pthread_create()? Sure. Even better, if you also implemented the other stack-related attribute functions. > So, the following would be valid: > pthread_attr_init(attr) > pthread_create(..., &attr, ...) > pthread_attr_getstack(&attr) It would be valid, but I'm not sure that it would do what you expect. That is if you expect, that the pthread_attr_getstack() returns the stack address of the newly created thread. pthread_create() doesn't modify the supplied attributes -- it must not do that, since they are "const" and can't do that anyway, since that would prevent the attributes to be used for creating multiple threads. So, unless one explicitly sets the stack address, pthread_attr_getstack() should return NULL or some other placeholder. Is there a special use case/ported software where the stack address and/or size is needed? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:17:43 2009 From: trac at haiku-os.org (diver) Date: Thu, 07 May 2009 23:17:43 -0000 Subject: [Haiku-bugs] [Haiku] #3897: [DriveSetup] Rescan menu increase vertical scrollbar Message-ID: <040.df0def5232555c85aca9fc57d7c863a6@haiku-os.org> #3897: [DriveSetup] Rescan menu increase vertical scrollbar -------------------------------------+-------------------------------------- Reporter: diver | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Disk->Rescan menu increase vertical scrollbar -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 01:46:15 2009 From: trac at haiku-os.org (anevilyak) Date: Thu, 07 May 2009 23:46:15 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.131d4061a8908baf0d6aa6af57242264@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. --------------------------------+------------------------------------------- Reporter: timeless | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): Yeah, doesn't seem ideal but then, the design of BMenu's API kinda sucks as a whole :/ Maybe some of this would be easier to handle by reviving/finishing that patch to make BMenu entirely mouse/keyboard event driven instead of the polling loop? Since that still needs to be done anyways in order to make keyboard navigation workable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 08:38:21 2009 From: trac at haiku-os.org (jackburton) Date: Fri, 08 May 2009 06:38:21 -0000 Subject: [Haiku-bugs] [Haiku] #3842: pressing enter in window list for app triggers Looper must be locked. In-Reply-To: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> References: <043.896c6e4922090ccfe4764ebee390e44f@haiku-os.org> Message-ID: <052.0c4ad45a0f6b60542addcc7b0fb12fe9@haiku-os.org> #3842: pressing enter in window list for app triggers Looper must be locked. ---------------------------------+------------------------------------------ Reporter: timeless | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by jackburton): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 08:41:09 2009 From: trac at haiku-os.org (jackburton) Date: Fri, 08 May 2009 06:41:09 -0000 Subject: [Haiku-bugs] [Haiku] #3895: [Terminal] jumping text after font change In-Reply-To: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> References: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> Message-ID: <049.6ced494aa9a799f6611ca9ba0c8376ab@haiku-os.org> #3895: [Terminal] jumping text after font change ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by jackburton): What do you mean ? I can't see anything wrong in the screenshot. Moreover, why did you put "Terminal" in the bug summary, when the bug has "Application/Installer" as component ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:03:40 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:03:40 -0000 Subject: [Haiku-bugs] [Haiku] #2503: ftp crashed In-Reply-To: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> References: <042.890d1b7dde529b9ff7531064a290c2da@haiku-os.org> Message-ID: <051.6c839d880f986926901e5d20bc17c7b1@haiku-os.org> #2503: ftp crashed ---------------------------------------------+------------------------------ Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by axeld): * owner: jackburton => axeld * component: Applications/Terminal => Applications/Command Line Tools -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:06:06 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:06:06 -0000 Subject: [Haiku-bugs] [Haiku] #3771: 'info' in terminal crashes. In-Reply-To: <041.dcb3c64e413e579a4ab8de0a90b6e18b@haiku-os.org> References: <041.dcb3c64e413e579a4ab8de0a90b6e18b@haiku-os.org> Message-ID: <050.7f94d4f2036a7ff3ea7a9b92363f656d@haiku-os.org> #3771: 'info' in terminal crashes. ---------------------------------------------+------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by axeld): * owner: jackburton => axeld * component: Applications/Terminal => Applications/Command Line Tools -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:07:07 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:07:07 -0000 Subject: [Haiku-bugs] [Haiku] #3891: [Terminal] Settings window ask to save settings if font was changed to itself In-Reply-To: <040.e49811a8e70fdb33a0686b031d700504@haiku-os.org> References: <040.e49811a8e70fdb33a0686b031d700504@haiku-os.org> Message-ID: <049.7de47b52f05f500622c9bc2d25dae790@haiku-os.org> #3891: [Terminal] Settings window ask to save settings if font was changed to itself ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: duplicate | Blockedby: 3348 Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => duplicate * blockedby: => 3348 Comment: I guess we're all getting senile :-) Duplicate of bug #3348 - always a good idea to look for those bugs first. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:11:42 2009 From: trac at haiku-os.org (fano) Date: Fri, 08 May 2009 07:11:42 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.b18d3df5ba79dcf3c28dc67be34fe715@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by fano): I've installed Haiku on my usb key using the last raw image using dd and it works! Now that thanks to dd the eventually partition table is gone I could install r30637 using DriveSetup on the raw device and use the installer, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:15:12 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:15:12 -0000 Subject: [Haiku-bugs] [Haiku] #3895: [Terminal] jumping text after font change In-Reply-To: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> References: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> Message-ID: <049.17ccb6f9c96bfae017f5a400c5a113ac@haiku-os.org> #3895: [Terminal] jumping text after font change -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30670, if I understood you correctly, at least :-) Non-fixed fonts shouldn't be settable in the first place. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:17:57 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:17:57 -0000 Subject: [Haiku-bugs] [Haiku] #3301: Fullscreen terminal doesn't cover the bottom of screen In-Reply-To: <042.3ff56afeec45424ae5770afdb59e6cfc@haiku-os.org> References: <042.3ff56afeec45424ae5770afdb59e6cfc@haiku-os.org> Message-ID: <051.81458d7afda84bc116f17180aa6564ba@haiku-os.org> #3301: Fullscreen terminal doesn't cover the bottom of screen ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This has already been fixed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:19:50 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:19:50 -0000 Subject: [Haiku-bugs] [Haiku] #3202: Conflicting shortcuts in Text Encoding In-Reply-To: <044.cfc41470247fea5270acf7a8b55dc470@haiku-os.org> References: <044.cfc41470247fea5270acf7a8b55dc470@haiku-os.org> Message-ID: <053.f92f668b28c2c775d6a64ee5e3c13cb5@haiku-os.org> #3202: Conflicting shortcuts in Text Encoding ------------------------------------+--------------------------------------- Reporter: humdinger | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * type: enhancement => bug * resolution: => fixed Comment: Since something not working counts as a bug, this shouldn't be an enhancement. But anyway, since switching encodings isn't happening that often (and there even were other conflicts, like Command-G), I've removed the shortcuts from the encodings menu a while ago. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:21:45 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:21:45 -0000 Subject: [Haiku-bugs] [Haiku] #3302: Terminal in full screen too big In-Reply-To: <042.1fd983a8a9c085b8e9abf8076e59bd5b@haiku-os.org> References: <042.1fd983a8a9c085b8e9abf8076e59bd5b@haiku-os.org> Message-ID: <051.0b649fa7431e490d035db11f6d5d14cc@haiku-os.org> #3302: Terminal in full screen too big ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This has been fixed as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:22:53 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:22:53 -0000 Subject: [Haiku-bugs] [Haiku] #3575: [Terminal] "Copy Here" context menu doesn't work In-Reply-To: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> References: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> Message-ID: <049.f824ed38e7bec9a2f79c49a9e55d606c@haiku-os.org> #3575: [Terminal] "Copy Here" context menu doesn't work ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: This seems to have been fixed, at least I can't reproduce it anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:25:49 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:25:49 -0000 Subject: [Haiku-bugs] [Haiku] #3304: Terminal disables scrollbar when program run from bash crashes In-Reply-To: <042.a79100ef419c0a5a9ff51ed7bc97c4af@haiku-os.org> References: <042.a79100ef419c0a5a9ff51ed7bc97c4af@haiku-os.org> Message-ID: <051.9295c06e60c1176703325fa517f01338@haiku-os.org> #3304: Terminal disables scrollbar when program run from bash crashes -----------------------------------+---------------------------------------- Reporter: Adek336 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by axeld): * owner: jackburton => bonefish Comment: The problem here is that "info" switches to another Terminal "screen", and the old one is not recovered when "info" crashes - this does not happen with every crashing app. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:27:25 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:27:25 -0000 Subject: [Haiku-bugs] [Haiku] #3803: Random characters displayed in Terminal In-Reply-To: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> References: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> Message-ID: <049.68d779768f09f382ffdc7245673e670e@haiku-os.org> #3803: Random characters displayed in Terminal --------------------------------+------------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: jackburton => stippi * component: Applications/Terminal => Servers/app_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:28:04 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:28:04 -0000 Subject: [Haiku-bugs] [Haiku] #3803: Random characters displayed in Terminal In-Reply-To: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> References: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> Message-ID: <049.c9a09546280ba7323deb8e2eb1a2b8d6@haiku-os.org> #3803: Random characters displayed in Terminal --------------------------------+------------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:51:21 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:51:21 -0000 Subject: [Haiku-bugs] [Haiku] #3090: termhere operation In-Reply-To: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> References: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> Message-ID: <050.2a15b919d1b1926b26bb31ff0d3a0927@haiku-os.org> #3090: termhere operation -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): It does have a side effect, since Terminal would then launch with the directory you started it from - ie. if you run Tracker from someplace else, and then launch a Terminal, you would get that other directory as a starting point. Which is not really that bad, IMO. BTW the TermHere (now OpenTerminal) docs clearly state that you have to remove that line from /etc/profile -- it's the same thing on BeOS, in case you wondered. Any other opinions on the matter? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:53:56 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:53:56 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut Message-ID: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- The current method of having a context menu over the tab is a bit hidden - why not have that entry in the menu as well? Also, there doesn't seem to be a way to close a terminal using a shortcut. I think Command-W should close the tab not the window, as it does in other tabbed apps (like Firefox) - we have already Command-Q for this, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:51:36 2009 From: trac at haiku-os.org (diver) Date: Fri, 08 May 2009 07:51:36 -0000 Subject: [Haiku-bugs] [Haiku] #3895: [Terminal] jumping text after font change In-Reply-To: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> References: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> Message-ID: <049.511297e5653204d1a921fa27e5fbe29d@haiku-os.org> #3895: [Terminal] jumping text after font change -------------------------------------+-------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Comment(by diver): Sorry, I added wrong screenshot. See terminal.png. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:54:38 2009 From: trac at haiku-os.org (diver) Date: Fri, 08 May 2009 07:54:38 -0000 Subject: [Haiku-bugs] [Haiku] #3895: [Terminal] jumping text after font change In-Reply-To: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> References: <040.5073fe00e0d9243a3accf27779a378bc@haiku-os.org> Message-ID: <049.bd74cb44a53d05b8de4782b711d38fd1@haiku-os.org> #3895: [Terminal] jumping text after font change ------------------------------------+--------------------------------------- Reporter: diver | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by diver): * component: Applications/Installer => Applications/Terminal -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:56:37 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:56:37 -0000 Subject: [Haiku-bugs] [Haiku] #3719: Terminal: visual glitch in color preferences In-Reply-To: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> References: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> Message-ID: <049.d71b807e6295ea5dd0f2e8d4df8fd34e@haiku-os.org> #3719: Terminal: visual glitch in color preferences --------------------------------+------------------------------------------- Reporter: rossi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * owner: jackburton => stippi * component: Applications/Terminal => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:56:44 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:56:44 -0000 Subject: [Haiku-bugs] [Haiku] #3719: Terminal: visual glitch in color preferences In-Reply-To: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> References: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> Message-ID: <049.9b4c22d193eab81ead3036c025cc28d8@haiku-os.org> #3719: Terminal: visual glitch in color preferences --------------------------------+------------------------------------------- Reporter: rossi | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * milestone: R1 => R1/alpha1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:57:27 2009 From: trac at haiku-os.org (diver) Date: Fri, 08 May 2009 07:57:27 -0000 Subject: [Haiku-bugs] [Haiku] #3891: [Terminal] Settings window ask to save settings if font was changed to itself In-Reply-To: <040.e49811a8e70fdb33a0686b031d700504@haiku-os.org> References: <040.e49811a8e70fdb33a0686b031d700504@haiku-os.org> Message-ID: <049.8757aebcb3dd7ad6e53c18e2743c4ab1@haiku-os.org> #3891: [Terminal] Settings window ask to save settings if font was changed to itself ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: duplicate | Blockedby: 3348 Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by diver): Damn, my bad :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:57:41 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:57:41 -0000 Subject: [Haiku-bugs] [Haiku] #3090: termhere operation In-Reply-To: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> References: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> Message-ID: <050.afb092d4ba828d524e4cfa00f9fac2ba@haiku-os.org> #3090: termhere operation -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): BTW it currently has a side effect anyway, as Tracker is obviously started from the root directory, and such is the Terminal - but that could be easily changed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 09:59:43 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 07:59:43 -0000 Subject: [Haiku-bugs] [Haiku] #3194: [Terminal] crash on close/quit In-Reply-To: <041.59a3d6942ebb218be440f12674e73c3e@haiku-os.org> References: <041.59a3d6942ebb218be440f12674e73c3e@haiku-os.org> Message-ID: <050.ee9cf6cac47a175f98d3e1f6b6612915@haiku-os.org> #3194: [Terminal] crash on close/quit -----------------------------------+---------------------------------------- Reporter: karmak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------------------+---------------------------------------- Changes (by axeld): * owner: jackburton => bonefish Comment: This could be a memory shortage related bug in the terminal buffer implementation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 10:01:36 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 08:01:36 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.505a40cd603259c9ca1f5f58601249ee@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by axeld): * owner: jackburton => bonefish -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 10:04:30 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 08:04:30 -0000 Subject: [Haiku-bugs] [Haiku] #3430: Terminal : incorrect redraw when resizing In-Reply-To: <041.b28fcb400390dbffdc5070ac30da50fb@haiku-os.org> References: <041.b28fcb400390dbffdc5070ac30da50fb@haiku-os.org> Message-ID: <050.0b99dd81c3b912627a42163df7c8a86c@haiku-os.org> #3430: Terminal : incorrect redraw when resizing -----------------------------------+---------------------------------------- Reporter: mmadia | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): This is actually mostly a bash problem, and can be reproduced with other Terminals (on other systems) as well. However, the "/bin/ls" should stay at the same line, not be there twice. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 10:04:46 2009 From: trac at haiku-os.org (diver) Date: Fri, 08 May 2009 08:04:46 -0000 Subject: [Haiku-bugs] [Haiku] #3890: [Interface Kit] color picker have some drawing bugs In-Reply-To: <040.261e06ee84b5e1654555740a8d0b41a6@haiku-os.org> References: <040.261e06ee84b5e1654555740a8d0b41a6@haiku-os.org> Message-ID: <049.58adbad00493ed938ba29cbdb5d1dee3@haiku-os.org> #3890: [Interface Kit] color picker have some drawing bugs --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by diver): Looks like a dup of #3719 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 10:25:21 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 08 May 2009 08:25:21 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.c0454eea3c0ba26ab5da0b43407769b9@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): Stephan, It's always obvious when someone is faking at being polite, so I'm glad to see some honesty at last. I don't know about the old people you associate with, but THIS old person has probably been programming since before you were born, and that you would presume to know enough to advise him is laughable. If someone breaks the GCC4 build it doesn't matter one whit, that isn't the official compiler right now. You not only forgot a semicolon, you forgot a header DECLARATION (which is different from forgetting to upload the header) in the same file. But I haven't accused you personally of causing 8/10 builds to fail, there are a lot of other people uploading code. The guy working on libavcodec has made a few goofs as well. As for giving up coding, well maybe ritual suicide would be better. Obviously you don't mean to be taken seriously. p.s. Sorry about mis-spelling your name, it was unintentional. I had begun to think of you as Stippi, but using your informal name didn't seem appropriate under the circumstances. You see, I even know something about German culture. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 10:25:56 2009 From: trac at haiku-os.org (stippi) Date: Fri, 08 May 2009 08:25:56 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.74bcb3616e3796386c706559dfd624f9@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): Yes, it should work now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 11:10:11 2009 From: trac at haiku-os.org (stippi) Date: Fri, 08 May 2009 09:10:11 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.d2236475caaa8da15870766ab057815d@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by stippi): Thanks for the reply, I was a bit worried I may have went to far... It is clear to me from your replies that you cannot take critique or even honest polite suggestions at all. It just comes across as lecturing to you and you will not move a millimeter. I am actually a person with great desire for harmony and resolving conflicts. So when I try to be polite it may be because I am trying to discuss on a reasonable level and take away some of the heated emotions so that I may get my point across. Obviously doesn't work with you and I get no credit for it and are just being insulted for feeling superior over others. Your attitude that I couldn't possibly know more than you just says it all. Don't take me wrong, I am not saying that I actually do know more than you, but your attitude just makes it clear why you would never take any advice from me on how you could do something better. Boy, I sure hope I will not be that arrogant and stubborn when I am older. It probably doesn't work when I try to tell you that my honest intentions were to tell you what you could improve in your communication in the future. Which is that you try to put yourself into other peoples place and try to give them all the information which you can guess they may need, when you try really hard to guess. Like when there is possibly a syntax error in a file you created that you actually post the complete file in the first place and not make other people write three or more comments until they finally get something from you that they can work with. That sort of stuff. And I think with this background, my remark about you wasting precious time with this behavior was long overdue. But instead of simply acknowledging that, you come back with your 8/10 insult and how we morons waste everyones time with our untested work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 11:14:24 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 09:14:24 -0000 Subject: [Haiku-bugs] [Haiku] #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works In-Reply-To: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> References: <040.3ba7a0df540c7aa16880801006dfaa35@haiku-os.org> Message-ID: <049.33f5da66d5b500de4555095c17da8d76@haiku-os.org> #3879: HAIKU_IMAGE_SIZE option in UserBuildConfig no longer works ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): As entertaining as this dispute is, could you guys please stop using the bug tracker as a message forum? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 11:16:58 2009 From: trac at haiku-os.org (diver) Date: Fri, 08 May 2009 09:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #3575: [Terminal] "Copy Here" context menu doesn't always work (was: [Terminal] "Copy Here" context menu doesn't work) In-Reply-To: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> References: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> Message-ID: <049.095a0a8929bb2c9bb60f5719cd62b4f6@haiku-os.org> #3575: [Terminal] "Copy Here" context menu doesn't always work ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: To reproduce:[[BR]] Create a new folder on Desktop[[BR]] Drag it to terminal window using right mouse button and choose Copy Here from context menu[[BR]] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 12:14:52 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 10:14:52 -0000 Subject: [Haiku-bugs] [Haiku] #3575: [Terminal] "Copy Here" context menu doesn't always work In-Reply-To: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> References: <040.1ede1b0ae5a967a60c3b164600cd25ee@haiku-os.org> Message-ID: <049.5acdba28d60a2252d5330a657dfb8791@haiku-os.org> #3575: [Terminal] "Copy Here" context menu doesn't always work ------------------------------------+--------------------------------------- Reporter: diver | Owner: jackburton Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: reopened => closed * resolution: => fixed Comment: The original bug has been fixed indeed, so please open a new ticket next time! Anyway, fixed that new issue in r30672, thanks for the note. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 13:32:32 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 08 May 2009 11:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #3808: Copying or creating large files causes General System Error In-Reply-To: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> References: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> Message-ID: <049.86065dcaba8e3685d8f6d287e0fe125f@haiku-os.org> #3808: Copying or creating large files causes General System Error ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by haiqu): Can now copy large files onto Haiku from other drives, but still cannot create a CD image using: jam -q haiku-image The build freezes the machine at the beginning of the write, with CPU at maximum smoke. Only a hard reboot will cure it. My copy of `mkisofs` creates boot images just fine and a build of mkisofs from the same sources works in BeOS 5.1d0 to create a full image. May not be a file system problem, I'm suspecting memory management, which underwent a lot of changes just prior to this fault arising. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 14:25:50 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 12:25:50 -0000 Subject: [Haiku-bugs] [Haiku] #3304: Terminal disables scrollbar when program run from bash crashes In-Reply-To: <042.a79100ef419c0a5a9ff51ed7bc97c4af@haiku-os.org> References: <042.a79100ef419c0a5a9ff51ed7bc97c4af@haiku-os.org> Message-ID: <051.81a2066b9ce903c1b96d44f8f8d8bf70@haiku-os.org> #3304: Terminal disables scrollbar when program run from bash crashes ------------------------------------+--------------------------------------- Reporter: Adek336 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: This could be considered a bash bug, then. Or rather a missing feature. The same happens in Linux with bash 3.x, if you e.g. run vim and "kill -9" it. Regarding apps that restore the terminal on crash, I suppose they have signal handlers for the deadly signals. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 15:12:01 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 13:12:01 -0000 Subject: [Haiku-bugs] [Haiku] #3090: termhere operation In-Reply-To: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> References: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> Message-ID: <050.e74ee069f7666a6b83feb939b15a6447@haiku-os.org> #3090: termhere operation -----------------------------------+---------------------------------------- Reporter: kvdman | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): +1 for removing the "cd" in /etc/profile and starting Tracker and Deskbar in the home directory. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 15:24:50 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 13:24:50 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.8a3300e8c082a0358dc60ee51f46d943@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): I find the Firefox behavior a bit annoying. Command-Q doesn't close the window, it quits the application (in case of Terminal it's the same). How about Command-Shift-W for closing tabs instead? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 15:54:00 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 13:54:00 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.a39aaae4625a443385fb5159475850dd@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): It's not actually the same, as Terminal does not open more than one window. What you propose is the reverse of how Firefox handles this, btw. I don't care that much, but I would lean towards the Firefox solution, as that's something people are already familiar with as it's the common solution on other platforms. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 16:25:18 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 14:25:18 -0000 Subject: [Haiku-bugs] [Haiku] #3194: [Terminal] crash on close/quit In-Reply-To: <041.59a3d6942ebb218be440f12674e73c3e@haiku-os.org> References: <041.59a3d6942ebb218be440f12674e73c3e@haiku-os.org> Message-ID: <050.4ddc7d8f3a1d6079a9d0ab4e89743ebe@haiku-os.org> #3194: [Terminal] crash on close/quit -----------------------------------+---------------------------------------- Reporter: karmak | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------------------+---------------------------------------- Changes (by bonefish): * owner: bonefish => nobody Comment: Replying to [comment:2 axeld]: > This could be a memory shortage related bug in the terminal buffer implementation. The terminal buffer implementation is one of the few places in the terminal code that does deal with failed memory allocations. Besides, unless you resize the terminal it doesn't need to do anymore allocations. Anyway, an assert in the memory allocator could be caused by double frees or overwritten memory. Impossible to pinpoint from just the back trace. @karmak: Among the stuff gdb initially prints there's at least one interesting line giving the reason for entering the debugger. Usually something like "Thread ... caused an exception:..." or "Thread ... called debugger:...". Please always also give this line in a bug report (in doubt copy the whole output). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 16:29:51 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 14:29:51 -0000 Subject: [Haiku-bugs] [Haiku] #3090: termhere operation In-Reply-To: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> References: <041.eda3cf9e809afae0ea381363addd85df@haiku-os.org> Message-ID: <050.8fcd96a556a189fba78d9f19eafe77e5@haiku-os.org> #3090: termhere operation ------------------------------------+--------------------------------------- Reporter: kvdman | Owner: jackburton Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Changed in r30674. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 16:35:54 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 14:35:54 -0000 Subject: [Haiku-bugs] [Haiku] #2851: [Terminal] resizing terminal window could crash it In-Reply-To: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> References: <040.3e866c5b5a0ef3b7c6fc4cd8ab8f5f36@haiku-os.org> Message-ID: <049.f95312355a59b90e5f9188d0843219b8@haiku-os.org> #2851: [Terminal] resizing terminal window could crash it -----------------------------------+---------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): I've tried to reproduce this by frantically resizing the window in various situations (with/without lots of output, with primary/alternative screen buffer, etc.). Without success. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 16:41:25 2009 From: trac at haiku-os.org (axeld) Date: Fri, 08 May 2009 14:41:25 -0000 Subject: [Haiku-bugs] [Haiku] #3875: "copyattr -d -r" results in attempts to write to read-only source partition. In-Reply-To: <038.c11eb449a698b1ce17726bcabf25e2b1@haiku-os.org> References: <038.c11eb449a698b1ce17726bcabf25e2b1@haiku-os.org> Message-ID: <047.49e6d747d6df93a557e5ffbb36a41159@haiku-os.org> #3875: "copyattr -d -r" results in attempts to write to read-only source partition. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): I would think these are two separate issues. The BeOS copyattr needed this, so we might want to revert that change - however, I am not sure if we currently require a writable file handle in case one wants to change the attributes of a file; that might also be the source of that problem, btw. If you find the time, you could do an "strace copyattr ..." to see where the failure actually happens. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 16:45:03 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 14:45:03 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.deab3345b62cbfa216847b208526fd5b@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): Replying to [comment:2 axeld]: > It's not actually the same, as Terminal does not open more than one window. Hence closing the window and quitting the app is the same. :-) > What you propose is the reverse of how Firefox handles this, btw. I don't care that much, but I would lean towards the Firefox solution, as that's something people are already familiar with as it's the common solution on other platforms. It's just somewhat inconsistent. In every other app Command-W closes the window, in Firefox it closes the tab. In Firefox Command-Shift-W closes the window, which it doesn't in any other app. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 17:18:11 2009 From: trac at haiku-os.org (stippi) Date: Fri, 08 May 2009 15:18:11 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.3760e797a080c5d41adb1c3f620f072d@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by stippi): Would be a nice subject for some field research... how many apps out there treat Command-W to close the current *document* regardless of whether it's in a window by itself or inside a tab? From a user's point of view, closing the document instead of literally the window is more convenient, no? Since otherwise you have two shortcuts for the same thing in a single window application. As far as Terminal goes, it's like Firefox from a user's point of view. You can have multiple windows, but inside each could be more than one "document". For consistency with true single window applications, I'd vote to let Command-W always mean to close the current document, not the current window. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 17:59:29 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 15:59:29 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.19154b721849ff50b9ded8381c5ae530@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): You are mistaken -- Command-W is the system-wide shortcut to close a window. Be it a file panel, a settings window, or whatever window has a "close" button. That's why the Firefox behavior is irritating me (and I ran into that several times already) -- I want to close the window and therefore press Command-W. If Command-Shift-W would generally close a window, the Firefox behavior would be somewhat more consistent. Since "other platforms" were mentioned: On Windows windows are closed with Alt-F4, Linux mimics that. MacOS X behaves the same way as Haiku, i.e. Command-W closes windows, save in Safari. CU, Ingo -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 18:16:22 2009 From: trac at haiku-os.org (stippi) Date: Fri, 08 May 2009 16:16:22 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.63b5e0c97434b370f15a74df274b8d59@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by stippi): I think I do get your point, it's a pragmatic approach, but I am not convinced yet. There are tons of examples where an action may have different "literal" meaning depending on context. Take for example the Escape key. It may mean to cancel a process, in other context it could mean to close a window. If you want to go to the extreme, even clicking with the mouse itself could serve as an example. It definitely depends on context what happens, or even on your following action. It could be "activate" or "grab and drag". I hope you don't think this argument is silly, I am just saying that your applied level or pragmatism is arbitrary. Command-W could simply also have a more flexible meaning than to literally close a window only. If it serves a sensible purpose and makes things more convenient, why not? My argument becomes even stronger when there is prior use in widespread applications, like certain popular tabbed browsers. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 18:57:29 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 May 2009 16:57:29 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.f7a91889519545378764629fc8be2096@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by anevilyak): OTOH, Firefox isn't consistent in its behavior across platforms either: for instance, on windows alt+f4 still closes the whole FF window, while ctrl+w closes a tab. At least last I checked. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 21:27:10 2009 From: trac at haiku-os.org (mjw) Date: Fri, 08 May 2009 19:27:10 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.4fece8b996146e3025997c67a2caeba1@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by mjw): Yes, you are right. I was working to old docs. It looks as though pthread_attr_getstack() should return either NULL for the address base, or the address you passed into pthread_attr_setstack(). The only way to get a thread's stack base out of it is to call pthread_getattr_np() to get the actual thread's attributes before calling pthread_attr_getstack(). I was porting Kaffe Java VM which uses pthread_attr_getstack() in its unix pthreads code. I believe mono needs to know the thread stack base as well. With that in mind, get_thread_info() looks like the correct thing to use, so this can be closed as invalid if you like. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 21:51:23 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 08 May 2009 19:51:23 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.c0a518251bc207edbde74c7677e5b874@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Can you enable 'full logging' in the nvidia.settings file, reboot, grab the resulting driver logfile from your home folder and upload it here? (the file remains intact if you are able to blindly fall back to KDL and type 'reboot'. If you then use failsafe video mode you should find the logfile from the previous boot. Thanks in advance! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 22:20:53 2009 From: trac at haiku-os.org (fano) Date: Fri, 08 May 2009 20:20:53 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.14a00a2255bf0a8bb59641b936e8abcd@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by fano): And indeed It works! But there is no way to facilitate this? I - ingenuously - thought that Installer can install Haiku in a usb key without hassle... indeed I've to destroy may partition table then do the dd thing (very slow process!!!) and I think with dd the space of the drive is reduced at the size of the image... so dd'ing is not a real solution... the installer should do this! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 22:25:12 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 08 May 2009 20:25:12 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.d0578584b0d09ef64e695ac75dcfe63c@haiku-os.org> #3881: Installer doesn't create bootable USB key --------------------------------+------------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by anevilyak): One of the summer of code projects aims to fix that deficiency, it's a known issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 22:37:43 2009 From: trac at haiku-os.org (HaiColon) Date: Fri, 08 May 2009 20:37:43 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.8aae03e354624f694197763fd6c851af@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by HaiColon): Don't know if that helps with locating the problem, I was playing around with curl and the Twitter API and had the same connection trouble there that I have with YouTube but when I started accessing Twitter through the https link instead of the http link there were no connection errors at all, works fine all the time with SSL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 8 23:08:29 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Fri, 08 May 2009 21:08:29 -0000 Subject: [Haiku-bugs] [Haiku] #824: Booting from CD causes the floppy to constantly be polled In-Reply-To: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> References: <049.f76a2f3c01bcff3c5c5fb7411b6345c2@haiku-os.org> Message-ID: <058.6f74aed05b12de1b18d8024598210e07@haiku-os.org> #824: Booting from CD causes the floppy to constantly be polled ----------------------------+----------------------------------------------- Reporter: johndrinkwater | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: Blockedby: | Platform: x86 Blocking: | ----------------------------+----------------------------------------------- Comment(by jonas.kirilla): The following was suggested on the haiku-development mailinglist as a fix to #824: http://www.freelists.org/post/haiku-development/xicon-and-executable- scripts,18 (Just recording this for posterity, in case the bug is still with us.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 00:23:40 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 22:23:40 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.a26d7246c9d362b5534fbc20a7fc9534@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): Replying to [comment:7 anevilyak]: > OTOH, Firefox isn't consistent in its behavior across platforms either: for instance, on windows alt+f4 still closes the whole FF window, while ctrl+w closes a tab. At least last I checked. Yep, Control-Shift-W also closes the window. Which actually makes Firefox' behavior consistent across platforms. But that's exactly the problem -- I guess the Control-W shortcut originates from a platform where it didn't have any global meaning (supposedly Windows). On BeOS/Haiku it simply clashes with the pre-existing global "close window" shortcut. If I were a regular Windows user and if Firefox would override Alt-F4 to close tabs, I would argue just the same as now for Command-W under Haiku. Regarding context-dependent meanings of shortcuts or actions in general, that is certainly true for a lot of actions, but there there are a few actions that are universally the same, like the cut, copy, paste, quit application, and close window shortcuts. Those are already established by the BWindow implementation for exactly that reason. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 00:37:42 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 08 May 2009 22:37:42 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.f7464d6e9ece95907c2043d3b241a90e@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): Replying to [comment:4 mjw]: > Yes, you are right. I was working to old docs. It looks as though pthread_attr_getstack() should return either NULL for the address base, or the address you passed into pthread_attr_setstack(). The only way to get a thread's stack base out of it is to call pthread_getattr_np() to get the actual thread's attributes before calling pthread_attr_getstack(). > > I was porting Kaffe Java VM which uses pthread_attr_getstack() in its unix pthreads code. I believe mono needs to know the thread stack base as well. Don't misunderstand me. I'm generally not opposed to adding non-POSIX functionality. It just seems pthread_getattr_np() is really GNU-only and not supported by other platforms. How is this solved for other non-GNU platforms (e.g. the BSDs)? Maybe there's another, more portable feature we could provide. > With that in mind, get_thread_info() looks like the correct thing to use, so this can be closed as invalid if you like. The summary is valid at any rate. We should implement the missing pthread attribute functions earlier or later. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 06:29:27 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 04:29:27 -0000 Subject: [Haiku-bugs] [Haiku] #3899: Commandline argument doesn't override UserBuildConfig Message-ID: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> #3899: Commandline argument doesn't override UserBuildConfig --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- This seems to be an issue with Jam. I have just done a complete build targeting a blank partition with: HAIKU_INSTALL_DIR=/Haiku2 jam -q install-haiku but the setting in my UserBuildConfig was HAIKU_INSTALL_DIR=/Haiku and the build tried to install to /Haiku which was unexpected behaviour. I fully realize this may be the default behaviour for Jam, but if there's a way to fix it I'd like that, since it goes against proper safe program behaviour. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 07:32:08 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 09 May 2009 05:32:08 -0000 Subject: [Haiku-bugs] [Haiku] #3900: [patch] Update to OpenSSL 0.9.8k Message-ID: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> #3900: [patch] Update to OpenSSL 0.9.8k --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Attached is a patch for OptionalBuildFeatures. It updates OpenSSL to version 0.9.8k. On http://www.openssl.org/ they have a 1.0.0 beta2 available, which may be worth keeping an eye on for the 1.0.0 release. '''note:'''The file referenced in this patch is not yet uploaded to haiku- files.org. Please do not commit this patch until a comment indicates that this has been done. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 07:44:03 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 09 May 2009 05:44:03 -0000 Subject: [Haiku-bugs] [Haiku] #3900: [patch] Update to OpenSSL 0.9.8k In-Reply-To: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> References: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> Message-ID: <050.6f1154c5c7a553f3c045a51367297b77@haiku-os.org> #3900: [patch] Update to OpenSSL 0.9.8k --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): For record keeping, here is the portlog http://ports.haiku-files.org/wiki /dev-libs/openssl/0.9.8k/1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 09:29:46 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 09 May 2009 07:29:46 -0000 Subject: [Haiku-bugs] [Haiku] #3899: Commandline argument doesn't override UserBuildConfig In-Reply-To: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> References: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> Message-ID: <049.28970d3f48135c350b4fca81e2db1ca9@haiku-os.org> #3899: Commandline argument doesn't override UserBuildConfig --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by VinDuv): Replying to [ticket:3899 haiqu]: > since it goes against proper safe program behaviour. I don't really agree with this. [[BR]] What if Haiku was using variable names like IMAGE_SIZE, INSTALL_DIR, ROOT_USER_NAME... in the build system ? They could be easily overriden by some environment variables, resulting in platform-dependant misbehaviour. [[BR]] Also, Jam works on many platforms, and I'm not sure if there is a portable way to get every environment variables on all of them. So IMHO, the current behaviour of jam ? overriding build variables with -s, for instance like this : jam -sHAIKU_INSTALL_DIR=/Haiku2 ... ? is fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 09:32:54 2009 From: trac at haiku-os.org (stippi) Date: Sat, 09 May 2009 07:32:54 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.51beabcf639e234b7dfb77a834cd1aef@haiku-os.org> #3881: Installer doesn't create bootable USB key ---------------------------------+------------------------------------------ Reporter: fano | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => duplicate Comment: Yes, the Installer should eventually do it of course, but this problem is already tracked, so I am closing the bug. Thanks for your feedback and testing! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 09:55:17 2009 From: trac at haiku-os.org (stippi) Date: Sat, 09 May 2009 07:55:17 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.70bfcb7ce7692cdd35f8f6be3af882b7@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by stippi): Ok, let me try one more time, then I will shut up... The implementation of Command-W in the BWindow is of course also a convenience. For the vast amount of situations it will do exactly what the intention is, so it makes sense to implement it there already. Most interfaces/panels/windows shown by applications will be one "entity" you can close. BeOS was designed that one window was supposed to map to one document. Now we have multiple applications were the designers thought a single application window which holds multiple documents is also pretty convenient. So isn't it a logical consequence to "tweak" a default behavior/implementation in way that it still makes sense and offers the same convenience in the changed situation? If I have a single window app, Command-W could either still close the window and thereby the whole app, making it essentially useless, because that's what Command-Q already does, or I could tweak the default behavior, which was not designed to accomodate this situation, and offer the same thing semantically. It's only logical that I do it this way around, not the other way which would mean I drop single window applications completely and stick to the original intention of having one document per window. Designing interfaces and behavior in applications allows to think about what the user most likely meant to do. I realize the difference here is how you look at it: Command-W to you means strictly to close "a window" and that was your intention and you want it to do always this for consistency. My argument is simply that I find it more likely that the intention of the user is to close the document, whatever it is, not necessarily a window -- *if* we are in the respective context. And on top of that, Command-W would duplicate Command-Q anyways, and implementing it to close only the active document also means it's less destructive for a viewing application like a browser which doesn't (need to) ask you if you have unsaved changes. Same holds true for the Terminal, it has no mechanism to figure out if closing other tabs means something destructive. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 10:01:49 2009 From: trac at haiku-os.org (stippi) Date: Sat, 09 May 2009 08:01:49 -0000 Subject: [Haiku-bugs] [Haiku] #3899: Commandline argument doesn't override UserBuildConfig In-Reply-To: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> References: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> Message-ID: <049.c548b6ce72686ba0b5f53a5145a49e9b@haiku-os.org> #3899: Commandline argument doesn't override UserBuildConfig --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by stippi): I think there is an assignment statement in jam which only assigns the variable if it doesn't already have a value. I would need to look up some Jamfiles we have, but maybe someone else can chime in... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 13:23:07 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 11:23:07 -0000 Subject: [Haiku-bugs] [Haiku] #3899: Commandline argument doesn't override UserBuildConfig In-Reply-To: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> References: <040.88b8ecc4147c8ae2a42701f80b54ad72@haiku-os.org> Message-ID: <049.548747d2f471adbd8045032a6cec24f0@haiku-os.org> #3899: Commandline argument doesn't override UserBuildConfig ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: If you want jam variables to be overridable via environmental vars, you have to use the "?=" assignment operator in your UserBuildConfig -- it assigns only, if the variable isn't set yet. Build profiles always set the HAIKU_{IMAGE,INSTALL}_* variables, not allowing overrides. It should be possible to work around by saving the original environment variable and restoring its value after defining the build profile like this: {{{ local savedInstallDir = $(HAIKU_INSTALL_DIR) ; ... DefineBuildProfile ... ... if $(savedInstallDir) { HAIKU_INSTALL_DIR = $(savedInstallDir) ; } }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 13:26:36 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 11:26:36 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.e3c989e198a533da580b25f718ad140f@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by jonas.kirilla): I'm happy with Command-W closing merely one tab, and then the window when closing its last tab. Command-W closes single things and Command-Q closes everything. Maybe it helps if one sees tabs as merely stacked windows. I would hate to have a third shortcut to close tabs. Perhaps tabbed applications could update the text in their menu option to say "Close tab" in the presence of multiple tabs, and "Close window" when there is only one tab. If a distinction in keyboard shortcuts really has to be made for tabbed windows, I would say Shift-Alt-W should close the window with all its tabs. Its the odd case. Closing a tab is likely the common case. I don?t mind that it somewhat breaks the W == Window. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 13:50:07 2009 From: trac at haiku-os.org (HaiColon) Date: Sat, 09 May 2009 11:50:07 -0000 Subject: [Haiku-bugs] [Haiku] #3823: Haiku has trouble to connect to some webservers In-Reply-To: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> References: <043.df1e55bb8d76aa3a3ad8aa95598f050c@haiku-os.org> Message-ID: <052.4b7435eb68718c4e7a3d2014e2cae08c@haiku-os.org> #3823: Haiku has trouble to connect to some webservers --------------------------------+------------------------------------------- Reporter: HaiColon | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by HaiColon): Looks like I just had a good day yesterday, now I have the same trouble when using SSL. But it does at least work better (more often) with SSL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 13:50:45 2009 From: trac at haiku-os.org (philcostin) Date: Sat, 09 May 2009 11:50:45 -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.2c5e935c5eb8dc3f39c078dabb9fb89b@haiku-os.org> #2273: [runtime_loader] double clicking it leads to problems ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by philcostin): Can anyone else still reproduce this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 13:56:22 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 11:56:22 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.4b2bcea74580fe8691fca280a74f1d70@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by bonefish): Stippi, I totally understand your interpretation of Command-W closing an entity. I just think it is a reinterpretation. For me Command-W has always been the convenient keyboard equivalent of clicking the window's close button. By now redefining its semantics this convenient universal shortcut is lost. Regarding the argument that Control-W is useless in a single-window app: Firefox is not a single-window app. And why Terminal is multi launch (and thus single-window), I cannot say -- probably just for the additional challenge of still getting the window titles right. I don't think in general there's a good reason why applications with a tabbed interface should be single-window -- thinking of multi workspaces use I guess even the opposite is the case. Anyway, if everyone else likes the modified Command-W behavior, I would at least suggest to introduce Command-Shift-W as the universal window close shortcut. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 17:07:57 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 15:07:57 -0000 Subject: [Haiku-bugs] [Haiku] #3896: [DeskCalc] initial window is too small In-Reply-To: <040.f056a1da918675767af017c2fbd23cfd@haiku-os.org> References: <040.f056a1da918675767af017c2fbd23cfd@haiku-os.org> Message-ID: <049.245840048c73296d72431509b38f943e@haiku-os.org> #3896: [DeskCalc] initial window is too small -----------------------------------+---------------------------------------- Reporter: diver | Owner: stpere Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/DeskCalc | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by stpere): * owner: stippi => stpere * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 17:24:58 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 15:24:58 -0000 Subject: [Haiku-bugs] [Haiku] #3896: [DeskCalc] initial window is too small In-Reply-To: <040.f056a1da918675767af017c2fbd23cfd@haiku-os.org> References: <040.f056a1da918675767af017c2fbd23cfd@haiku-os.org> Message-ID: <049.c04d71b9fc65b8b17c9f02138c2ca151@haiku-os.org> #3896: [DeskCalc] initial window is too small ------------------------------------+--------------------------------------- Reporter: diver | Owner: stpere Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/DeskCalc | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: Hi, this is fixed in r30679. The window was resized to the size of the dragger :) The frame variable was wrongly re-used. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 17:40:32 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 15:40:32 -0000 Subject: [Haiku-bugs] [Haiku] #3890: [Interface Kit] color picker have some drawing bugs In-Reply-To: <040.261e06ee84b5e1654555740a8d0b41a6@haiku-os.org> References: <040.261e06ee84b5e1654555740a8d0b41a6@haiku-os.org> Message-ID: <049.25f4ec41a9b64ddae19d03b78e50ee60@haiku-os.org> #3890: [Interface Kit] color picker have some drawing bugs ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stpere): * status: new => closed * resolution: => duplicate Comment: Yes, it is indeed a duplicate. Thanks for the report though! :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:22:39 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 09 May 2009 16:22:39 -0000 Subject: [Haiku-bugs] [Haiku] #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only Message-ID: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- This needs to be fixed to also handle licenses that are added to /boot/common/etc/licenses -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:28:41 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 16:28:41 -0000 Subject: [Haiku-bugs] [Haiku] #3902: Netscript over-written during upgrade installation Message-ID: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> #3902: Netscript over-written during upgrade installation --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- The file /boot/system/boot/netscript contains examples of how to set up some network parameters. If this file is actually set up, it will be over- written next time the system is upgraded from sources. Suggest changing the filename to netscript.sample and thus allowing the actual netscript to remain available without re-editing every time. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:36:24 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 09 May 2009 16:36:24 -0000 Subject: [Haiku-bugs] [Haiku] #3902: Netscript over-written during upgrade installation In-Reply-To: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> References: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> Message-ID: <049.ceb0a301bc686db3e2977ba2e9e18833@haiku-os.org> #3902: Netscript over-written during upgrade installation --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by scottmc): Shouldn't users not be changing things in the /boot/system folders? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:42:14 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 16:42:14 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offest between local and GMT wrong on Clock application (easy) Message-ID: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> #3903: Time offest between local and GMT wrong on Clock application (easy) --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- The Clock application allows the user to set and show local time, but also allows a quick check of GMT from the "Date & Time" panel, and also a preview of any timezone from the "Timezone" panel. When local time is set correctly, selecting GMT from the "Date & Time panel ADDS the offset where it should be SUBTRACTED. Example: I'm at GMT +10 (Australia, East Coast). It's now 2:33am and if I select GMT I should see 4:33pm YESTERDAY on the clock. Instead I see 12:33pm TODAY. This means that the offset is being added instead of subtracted. If I preview GMT from the "Timezone" panel it is shown correctly. Simple sign error somewhere in the application's code. BTW, the correct terminology is UTC (Coordinated Universal Time, Temps Universel Coordonn?). The old term Greenwich Mean Time has been out of date since the 1970's. Since so many people don't know that, displaying UTC/GMT next to the checkbox would be a happy compromise. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:48:13 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 16:48:13 -0000 Subject: [Haiku-bugs] [Haiku] #3904: "Save MBR" option pointless during CD install Message-ID: <040.5a4ee4866917546d06c56b3155180306@haiku-os.org> #3904: "Save MBR" option pointless during CD install ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- When making an installation from a CD, the option to save the Master Boot Record is irrelevant, and possibly confusing to new users. It therefore should be skipped during CD installations, preferrably not even shown. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:50:01 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 09 May 2009 16:50:01 -0000 Subject: [Haiku-bugs] [Haiku] #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only In-Reply-To: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> References: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> Message-ID: <051.29e0c817615e45a9bf6e3f4eb5ed8939@haiku-os.org> #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmadia): probably safe to assume that /boot/home/config/etc/licenses should also be included. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:50:13 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 16:50:13 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offest between local and GMT wrong on Clock application (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.190dd3a7359118ae990950af3e0ee43d@haiku-os.org> #3903: Time offest between local and GMT wrong on Clock application (easy) -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by haiqu): * component: Applications => Preferences/Time & Date -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:51:46 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 16:51:46 -0000 Subject: [Haiku-bugs] [Haiku] #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only In-Reply-To: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> References: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> Message-ID: <051.c848e7ac057b0c8986d81e846238c0ba@haiku-os.org> #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: bonefish Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 18:54:00 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 16:54:00 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) (was: Time offest between local and GMT wrong on Clock application (easy)) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.58345b6c6d3d167de3080337822ff097@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) -------------------------------------+-------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 19:01:58 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 17:01:58 -0000 Subject: [Haiku-bugs] [Haiku] #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only In-Reply-To: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> References: <042.d9fd1559d44e2891ae38712ad0881cd9@haiku-os.org> Message-ID: <051.3970e777a41ab95f40458f900121448a@haiku-os.org> #3901: AboutSystem supports licenses in the B_SYSTEM_DATA_DIRECTORY directory only --------------------------+------------------------------------------------- Reporter: scottmc | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30681. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 19:16:22 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 17:16:22 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.7b82899fc0b9444146cb2dd3e7eafb7f@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) --------------------------------------+------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: You misunderstood what the "Local Time"/"GMT" option is about. It lets you specify what time zone your hardware clock is supposed to be set to. If it is set to GMT and your local time zone is +10, the system assumes your time is hardware clock +10h. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 19:29:18 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 17:29:18 -0000 Subject: [Haiku-bugs] [Haiku] #3905: Erroneous/unusable code in BeBook Message-ID: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> #3905: Erroneous/unusable code in BeBook ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: nielx Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ The BeBook examples need to be checked and tested to ensure they compile and work as expected/advertised. A great example of the junk that has been included is in "System Overview->Application Kit->Be Application" where the example of how to create a Be Application doesn't work, and didn't work as long ago as R4. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 19:32:40 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 09 May 2009 17:32:40 -0000 Subject: [Haiku-bugs] [Haiku] #3905: Erroneous/unusable code in BeBook In-Reply-To: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> References: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> Message-ID: <049.8a7842fb438b251049b9705d2c5a18de@haiku-os.org> #3905: Erroneous/unusable code in BeBook ----------------------------+----------------------------------------------- Reporter: haiqu | Owner: nielx Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => invalid Comment: We can't change that. The BeBook is provided as is and the copyright belongs to ACCESS. We're only authorized to redistribute it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 19:53:40 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 09 May 2009 17:53:40 -0000 Subject: [Haiku-bugs] [Haiku] #3906: lseek64/llseek routine missing from libroot.so Message-ID: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> #3906: lseek64/llseek routine missing from libroot.so -------------------------------+-------------------------------------------- Reporter: haiqu | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- The lseek64 routine (also known in Linux as llseek) is not yet implemented. This is required for any access to EFI/GPT, especially being able to read modern MacOS X or Windows Vista drives. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 20:02:14 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 18:02:14 -0000 Subject: [Haiku-bugs] [Haiku] #3906: lseek64/llseek routine missing from libroot.so In-Reply-To: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> References: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> Message-ID: <049.d71d0ff0601033ee909655cc69c7cee5@haiku-os.org> #3906: lseek64/llseek routine missing from libroot.so --------------------------------+------------------------------------------- Reporter: haiqu | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: BeOS's off_t has been 64 bit forever, so lseek() does fully suffice. Neither lseek64() nor llseek() are portable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 20:13:29 2009 From: trac at haiku-os.org (bbjimmy) Date: Sat, 09 May 2009 18:13:29 -0000 Subject: [Haiku-bugs] [Haiku] #3881: Installer doesn't create bootable USB key In-Reply-To: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> References: <039.9cec1edc127c0882dcaa716e9ca4e7f9@haiku-os.org> Message-ID: <048.60cba1850ed81c235c008e2333bfb181@haiku-os.org> #3881: Installer doesn't create bootable USB key ---------------------------------+------------------------------------------ Reporter: fano | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Boot Loader | Version: R1 development Resolution: duplicate | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Comment(by bbjimmy): Replying to [comment:12 stippi]: > Yes, the Installer should eventually do it of course, but this problem is already tracked, so I am closing the bug. Thanks for your feedback and testing! What ticket is tracking this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 20:34:39 2009 From: trac at haiku-os.org (fano) Date: Sat, 09 May 2009 18:34:39 -0000 Subject: [Haiku-bugs] [Haiku] #3907: Avisynth compatibility Message-ID: <039.9f7208e7678d0b2799420f63ee050345@haiku-os.org> #3907: Avisynth compatibility ---------------------------+------------------------------------------------ Reporter: fano | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I think to be the real successor of the "Media OS" we have to support the Avisynth scripting language... sadly it is heavily based on DirectShow and some filters are in form of Windows binary (dll). There was a try to create a multiplatform version of it: Avisinth 3... but sadly the project is died 2 years ago: http://avisynth3.unite-video.com/download.html It's a shame as finally they not rely in ffdshow anymore and it partially worked on Linux, too! At this point or we can try to port Avisynth 3 to Haiku but I think the support will be limited as it will be not supported in Windows or try to support the actual Avisynth 2.5 version in some way. I think Avisynth is a really important from the HTPC side with all filter to enhance SD content and resize with very high quality to HD resolution and is heavily used too, to compress file from a format to another to achieve the best quality you can't simply encode the files as is! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 20:56:35 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 18:56:35 -0000 Subject: [Haiku-bugs] [Haiku] #3908: Too easy to accidentally select first item off a popup menu Message-ID: <048.f6f8be390ec60b95e97f2f50f935568d@haiku-os.org> #3908: Too easy to accidentally select first item off a popup menu --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- E.g. in Tracker its easier in Haiku than in BeOS to accidentally select the first item off a popup menu, possibly since the first menu item starts directly at the upper menu border. In BeOS menus there is a thin stripe before the first menu item starts. Compare right-clicking your desktop 10 times in BeOS and in Haiku. In BeOS the menu usually comes up with no menu item selected, whereas in Haiku it usually comes up with the first menu item selected. In Haiku I find myself often accidentally selecting the first menu item in Tracker?s context menus. Perhaps I move the mouse too soon after having released the right mouse button (when opening the menu), and the mouse button release message gets wrongly interpreted as being from the new location? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 22:41:08 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 09 May 2009 20:41:08 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.a492780e3b98255163bf25280e88a68b@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by bonefish): I've seen that too in r30603 while unplugging my Kinesis keyboard to which a mouse was attached. As for a possible cause: The there are several places in legacy_drivers.cpp where the device is deleted right after a devfs_unpublish_device(, true). It is not guaranteed that after vfs_disconnect_vnode() returns there won't be anymore calls using that node, though, since it only marks the FDs disconnected. Any thread that is in put_fd() past the check could cause this problem. Unless I'm mistaken even more generally, anyone who has already acquired a reference to the vnode (or even a file_descriptor) at this point can still call into the devfs with the "stale" node. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 22:51:22 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 20:51:22 -0000 Subject: [Haiku-bugs] [Haiku] #278: [FileTypes] disappearing menu items In-Reply-To: <040.bdf3beac2ec9a354075afbcd20dd0640@haiku-os.org> References: <040.bdf3beac2ec9a354075afbcd20dd0640@haiku-os.org> Message-ID: <049.758371d1f19da0beb51c67331623b708@haiku-os.org> #278: [FileTypes] disappearing menu items ------------------------------------+--------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Preferences/FileTypes | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by stpere): * version: => R1 development Old description: > This could be due linux build image, but anyway: > Start FyleTypes and expand application > select Be Application and go to Preferred application box > click on popup menu and select None > now click there again and you'll see that Tracker disappeared from menu > list. > Tested with rev16685 under vmware. New description: This could be due linux build image, but anyway: Start FyleTypes and expand application select Be Application and go to Preferred application box click on popup menu and select None now click there again and you'll see that Tracker disappeared from menu list. Tested with rev16685 under vmware. -- Comment: Here are some observations I made while investigating this ticket : First, sorry for the novel >.< I open FileTypes, I select the Be Application Mimetype, set the preferred app. to None and Tracker's item disappear from the menu, as mentioned. I went to FileTypes's source code (PreferredAppMenu.cpp) and requested the message listing the supporting applications message to print on stream. I was puzzled to discover it wasn't returning Tracker. So I found out Tracker was first shown simply because it was the current Preferred App. So changing the preferred app had for effect to remove Tracker from this menu on next update (since it wasn't even listed as a supporting app) Next, FileTypes > Application Types. I select Tracker, remove its support for Be Application Mimetype, and re-add it. Close (and save) the window. Back in FileTypes main window, I can now see Tracker in the menu for the preferred App of Be Applications. Selecting None doesn't make tracker disappear now. And the supporting Apps message returns Tracker now. Next, I close and reopen FileTypes. The "fix" is still effective, the support of Be Applications files from Tracker is still recognized. Next, I reboot. It returns to the old behaviour where selecting None makes Tracker disappears from the preferred app. menu. So, there must be something wrong with the way the mime database is loaded on boot. I'm trying to figure it out, but can't promise anything, since I'm learning how it works while trying to fix it :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 23:13:27 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 21:13:27 -0000 Subject: [Haiku-bugs] [Haiku] #3909: Set urlwrapper to initially handle all URL types - this enables a better system-user dialog Message-ID: <048.4ad8da9e47cf87c35a2b274c79d1292a@haiku-os.org> #3909: Set urlwrapper to initially handle all URL types - this enables a better system-user dialog ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: jonas.kirilla Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ One might want to make urlwrapper the preferred app of all the URL types in spite of which ones it supports, to communicate better with the user. For the URL types urlwrapper does not support itself and for which no other supporting application exists, it would have to tell the user that no application is present to handle the URL. (BAlert-style) For URL types is does not handle but there are other applications present, it should open a dialog asking the user which application to handle the URL (now/always). (Open with...-style) For URL types it handles "itself" (e.g. ftp or telnet) just handle them. Or maybe the first time for each such URL type - if there is another application present - ask the user which application is preferred. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 9 23:54:39 2009 From: trac at haiku-os.org (fano) Date: Sat, 09 May 2009 21:54:39 -0000 Subject: [Haiku-bugs] [Haiku] #3907: Avisynth compatibility In-Reply-To: <039.9f7208e7678d0b2799420f63ee050345@haiku-os.org> References: <039.9f7208e7678d0b2799420f63ee050345@haiku-os.org> Message-ID: <048.b5195704ff6086a17e93799a72098780@haiku-os.org> #3907: Avisynth compatibility ---------------------------+------------------------------------------------ Reporter: fano | Owner: marcusoverhagen Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Audio & Video | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by fano): There is yet a little hope, maybe: http://socghop.appspot.com/student_project/show/google/gsoc2009/uraeus/t124025048258 This is gstreamer based... that I think Haiku hasn't it... Haiku "Avisynth" should link with Media Kit, right? Well I think if it is in some way ported to Linux it became more simple to port to Haiku! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 00:13:19 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 22:13:19 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd Message-ID: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Booting a Haiku CD built using the haiku-cd jam target, two of the Deskbar entries show the application icon even though they?re folders. Catattr BEOS:TYPE indeed shows an application mime type on all 4 folders in Deskbar. (Folders Applications and Preferences have their icons swapped for overlayed ones, otherwise they would show with the three-blocks executable icon too.) IIRC /boot/home/config/be and /boot/home/config/boot too have the application mime type and opening Filetypes on them reveals that one of these (dont recall which) has some resource attributes belonging to some UHCI binary. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 00:23:23 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 22:23:23 -0000 Subject: [Haiku-bugs] [Haiku] #3203: Add menu "Font Size" In-Reply-To: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> References: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> Message-ID: <053.910542ddf08e530211883973cf93b305@haiku-os.org> #3203: Add menu "Font Size" -----------------------------------+---------------------------------------- Reporter: humdinger | Owner: stpere Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Changes (by stpere): * owner: jackburton => stpere * status: new => assigned Comment: Hmm, on an not totally unrelated note, how one could type [ COMMAND + ] ? It doesn't seem to work on several keymaps I tried (including US- International).. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 00:50:33 2009 From: trac at haiku-os.org (stpere) Date: Sat, 09 May 2009 22:50:33 -0000 Subject: [Haiku-bugs] [Haiku] #3203: Add menu "Font Size" In-Reply-To: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> References: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> Message-ID: <053.e7ec0183804f0af5c2bd7250c761849d@haiku-os.org> #3203: Add menu "Font Size" ------------------------------------+--------------------------------------- Reporter: humdinger | Owner: stpere Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: This is implemented in r30687. Thanks! (my question still stands, btw.. :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 00:57:03 2009 From: trac at haiku-os.org (stippi) Date: Sat, 09 May 2009 22:57:03 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.271c0dc93576d2a5abdc65f020196654@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by stippi): If you don't have xattr support enabled on your Linux system, in case you use Linux, you should see a generated/attributes folder. What happens if you delete that folder and do a clean build? Can you still reproduce the problem then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 01:38:44 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 23:38:44 -0000 Subject: [Haiku-bugs] [Haiku] #3911: DiskProbe cascades windows off screen Message-ID: <048.b2cded3f0d39fdb7bc401f7e51033ea1@haiku-os.org> #3911: DiskProbe cascades windows off screen ------------------------------------+--------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DiskProbe | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- When launched with enough entries DiskProbe eventually cascades windows off screen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 01:49:52 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sat, 09 May 2009 23:49:52 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.8fd65c178a0777d881c152ad19fc0125@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by jonas.kirilla): Yes, I?m using Linux but without xattr support. I have remove generated/attributes and I am currently rebuilding. It seems that my _HAIKU entries were wrongly populated. Mounting a haiku- cd.iso image as plain iso9660 revealed that the _HAIKU entries of directories actually had a be-executable type and something about Developer Build in them. The few other _HAIKU entries I looked at seem to be correct, e.g. those of mime type and those of true applications. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 01:55:49 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 09 May 2009 23:55:49 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.1492d8ff16fb2e564611f042a7f9bddf@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): The reason he asked that is because issues like that have been seen in the past with the attribute emulation on non-xattr volumes. I used to get this bug every now and then with regular builds until I switched over to using xattr. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 02:36:59 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 10 May 2009 00:36:59 -0000 Subject: [Haiku-bugs] [Haiku] #3818: GPL binaries without source code In-Reply-To: <040.c8c5cd0083f515c0c578f9f4ae186615@haiku-os.org> References: <040.c8c5cd0083f515c0c578f9f4ae186615@haiku-os.org> Message-ID: <049.e012ec659319cfa1b8469e4634796f0a@haiku-os.org> #3818: GPL binaries without source code -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by mmadia): Would it be possible to support a new directory for OptionalPackages? [[BR]] possibly something like "/path/etc/gpl-source-code" [[BR]] This file, would be a plain text file that provides a direct download link to the GPL source code and patches. [[BR]] file: "OpenSSL" : {{{ http://www.haiku-files.org/files/gpl-source-code/openssl.0.9.8k.zip http://www.haiku-files.org/files/gpl-source-code/openssl.0.9.8.patch }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 03:18:51 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 10 May 2009 01:18:51 -0000 Subject: [Haiku-bugs] [Haiku] #3654: selected area disappear, if you click the menu to edit them In-Reply-To: <040.996cf08423a1e10ac5013593cf14fd4f@haiku-os.org> References: <040.996cf08423a1e10ac5013593cf14fd4f@haiku-os.org> Message-ID: <049.0b5e4bacb5863f09fd95aefb3939e3b2@haiku-os.org> #3654: selected area disappear, if you click the menu to edit them --------------------------------------+------------------------------------- Reporter: chico | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => invalid Comment: Tested on R5Bone, native. Haiku exhibits the same behavior as BeOS. When the menu is activated, the highlighted section will appear to become non- highlighted. This is only a visual effect. Once the menu loses focus, the selected region automatically regains its highlighted visual appearance. Closing as invalid. Feel free to re-open if R5's behavior is undesirable in this particular case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 03:22:42 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 10 May 2009 01:22:42 -0000 Subject: [Haiku-bugs] [Haiku] #3654: selected area disappear, if you click the menu to edit them In-Reply-To: <040.996cf08423a1e10ac5013593cf14fd4f@haiku-os.org> References: <040.996cf08423a1e10ac5013593cf14fd4f@haiku-os.org> Message-ID: <049.5ccafcd9cbb1d97370909f9790dfb0c4@haiku-os.org> #3654: selected area disappear, if you click the menu to edit them --------------------------------------+------------------------------------- Reporter: chico | Owner: korli Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by mmadia): Forgot.. Thanks to stpere for pointing this ticket out! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 03:25:39 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 01:25:39 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.4bce1fbd6c97388598e4d89effcd49e1@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by jonas.kirilla): A clean build showed the same thing. Will try a GCC4 build tomorrow. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 03:41:25 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 01:41:25 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.ff9fa5eb1e77eb6cdea8f37569b6e6d1@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by jonas.kirilla): Looking at the build system (which I can?t say I have a decent grasp of) I got the impression that attributes get built from resources and that these are built/processed somehow. Maybe there are some kind of resource defaults (in some Jam rule or action?) that cater to executables, or those things get added somewhere along the way. Or maybe data from some previous resources/attributes creation spills over into the next. The numbers used in the generated/attributes folder, where do they come from? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 02:20:24 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 00:20:24 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.3c6e505db1ccb74ffab87f0cbd3077e4@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by jonas.kirilla): I?ve never seen this issue with the disk target. What I think was a clean haiku-cd build showed the same error. But I did a disk build in between jam clean and the haiku-cd build. Will try again doing a straight "sudo rm -rf generated/attributes; sudo jam clean; sudo jam -q haiku-cd;" and see how that goes. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 06:05:49 2009 From: trac at haiku-os.org (stpere) Date: Sun, 10 May 2009 04:05:49 -0000 Subject: [Haiku-bugs] [Haiku] #1820: [DataTranslations] Scrollbar don't move on End key press (easy) In-Reply-To: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> References: <040.5f752054ecf723e47469863bb7570dab@haiku-os.org> Message-ID: <049.fc7b5aee3a0846ac58b3197c04b83319@haiku-os.org> #1820: [DataTranslations] Scrollbar don't move on End key press (easy) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stpere): * status: reopened => closed * resolution: => fixed Comment: Hi, I committed a fix for this in r30689. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 06:05:57 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 10 May 2009 04:05:57 -0000 Subject: [Haiku-bugs] [Haiku] #3203: Add menu "Font Size" In-Reply-To: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> References: <044.56de895a4cbd3b1c851eabbc7c896bc9@haiku-os.org> Message-ID: <053.59564bb1c0b4023a2c2490faaf6d94cd@haiku-os.org> #3203: Add menu "Font Size" ------------------------------------+--------------------------------------- Reporter: humdinger | Owner: stpere Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------------+--------------------------------------- Comment(by humdinger): Thanks, Philippe![[BR]] WRT the shortcuts: It works with the German keymap. :)[[BR]] And, for the few people not working with a notebook, there's also the numberpad, I guess. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 06:18:52 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 10 May 2009 04:18:52 -0000 Subject: [Haiku-bugs] [Haiku] #3900: [patch] Update to OpenSSL 0.9.8k In-Reply-To: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> References: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> Message-ID: <050.c84fca84b1b40bbc8091f87b9b656662@haiku-os.org> #3900: [patch] Update to OpenSSL 0.9.8k --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): The file has been uploaded, Thank you Urias! To note, .OptionalPackageDescription and common/etc/licenses/OpenSSL is included in the archive. Tested in a custom build. As such, this patch can now be committed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 12:11:28 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 10 May 2009 10:11:28 -0000 Subject: [Haiku-bugs] [Haiku] #3912: Issues changing from DHCP to Static Message-ID: <043.8682d06e296dcf4e2edbdb22f5a5b476@haiku-os.org> #3912: Issues changing from DHCP to Static ---------------------------------+------------------------------------------ Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Network | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------------+------------------------------------------ I just gave my SiS900 built-in network another try with DHCP (#1744), no luck, so I select 'Static' and enter all the info (except for DNS 2) and press 'Apply', then close the preflet. i. `ifconfig` has the right IP address, broadcast address and mask. i. {{{/boot/system/etc/resolv.conf}}} has the right nameserver. i. Network preflet still shows DHCP, reproducibly. i. A newly opened BeZillaBrowser doesn't use the new, static DNS server. After a reboot, the preflet does show 'Static', and the correct DNS server is used. Note that the opposite direction (from Static to DHCP) worked as expected as far as preflet and browser are concerned. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:26:47 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 10 May 2009 11:26:47 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.b22e666e080d04e67179bd20d24654f2@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by haiqu): At r30690 today and the `jam -q haiku-cd` target worked fine, all files included in the build and installing to a real HDD also went OK. Resolved, please close. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:51:28 2009 From: trac at haiku-os.org (diver) Date: Sun, 10 May 2009 11:51:28 -0000 Subject: [Haiku-bugs] [Haiku] #3913: [net_server] DHCP client doesn't add domain name to resolv.conf Message-ID: <040.1bb7ab38d76f9fa6e530aabc12f561c6@haiku-os.org> #3913: [net_server] DHCP client doesn't add domain name to resolv.conf --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/net_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- DHCP client built in net_server should support putting domain name to resolv.conf.[[BR]]man resolv.conf {{{ search Search list for host-name lookup. The search list is nor- mally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Most resolver queries will be attempted using each component of the search path in turn until a match is found. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:54:03 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 10 May 2009 11:54:03 -0000 Subject: [Haiku-bugs] [Haiku] #3914: Tracker crash Message-ID: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> #3914: Tracker crash ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- After opening a .c file via Open With with Pe: {{{ GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-pc-haiku"...(no debugging symbols found) [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 26235 caused an exception: Segment violation Reading symbols from /boot/system/runtime_loader...done. Loaded symbols for /boot/system/runtime_loader Reading symbols from /boot/system/lib/libbe.so...done. Loaded symbols for /boot/system/lib/libbe.so Reading symbols from /boot/system/lib/libtracker.so...done. Loaded symbols for /boot/system/lib/libtracker.so Reading symbols from /boot/system/lib/libroot.so...done. Loaded symbols for /boot/system/lib/libroot.so Reading symbols from /boot/system/lib/libtranslation.so...done. Loaded symbols for /boot/system/lib/libtranslation.so Reading symbols from /boot/system/lib/libtextencoding.so...done. Loaded symbols for /boot/system/lib/libtextencoding.so Reading symbols from /boot/system/lib/libiconv.so...done. Loaded symbols for /boot/system/lib/libiconv.so Reading symbols from /boot/system/add- ons/Translators/BMPTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/BMPTranslator Reading symbols from /boot/system/add- ons/Translators/EXRTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/EXRTranslator Reading symbols from /boot/system/lib/libilmimf.so...done. Loaded symbols for /boot/system/lib/libilmimf.so Reading symbols from /boot/system/lib/libz.so...done. Loaded symbols for /boot/system/lib/libz.so Reading symbols from /boot/system/add- ons/Translators/GIFTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/GIFTranslator Reading symbols from /boot/system/add- ons/Translators/JPEG2000Translator...done. Loaded symbols for /boot/system/add-ons/Translators/JPEG2000Translator Reading symbols from /boot/system/add- ons/Translators/JPEGTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/JPEGTranslator Reading symbols from /boot/system/add- ons/Translators/PCXTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PCXTranslator Reading symbols from /boot/system/add- ons/Translators/PNGTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PNGTranslator Reading symbols from /boot/system/add- ons/Translators/PPMTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/PPMTranslator Reading symbols from /boot/system/add- ons/Translators/RAWTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/RAWTranslator Reading symbols from /boot/system/add-ons/Translators/RTF- Translator...done. Loaded symbols for /boot/system/add-ons/Translators/RTF-Translator Reading symbols from /boot/system/add- ons/Translators/SGITranslator...done. Loaded symbols for /boot/system/add-ons/Translators/SGITranslator Reading symbols from /boot/system/add- ons/Translators/STXTTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/STXTTranslator Reading symbols from /boot/system/add- ons/Translators/TGATranslator...done. Loaded symbols for /boot/system/add-ons/Translators/TGATranslator Reading symbols from /boot/system/add- ons/Translators/TIFFTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/TIFFTranslator Reading symbols from /boot/system/add- ons/Translators/WonderBrushTranslator...done. Loaded symbols for /boot/system/add-ons/Translators/WonderBrushTranslator [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/system/Tracker (89) thread w>git (26235)] 0x003b52ec in BString::BString () from /boot/system/lib/libbe.so (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:55:40 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 11:55:40 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.b9d3e649186a2330e8cf85699d47635d@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by jonas.kirilla): * owner: axeld => bonefish * component: File Systems => Build System Comment: A clean x86/gcc4 haiku-cd build shows the same thing. Random folders with a BEOS:TYPE attribute of the executable mime type. "svn status" shows nothing but a few of my uncommitted changes to source and header files - no changes to any files related to jam or the buildtools. Changing component. Looking at the _HAIKU folders its plain to see that its not the attribute overlay that misinterprets anything, so I think its safe to blame the build system. The folders are likely not random. I will enumerate them shortly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:58:42 2009 From: trac at haiku-os.org (diver) Date: Sun, 10 May 2009 11:58:42 -0000 Subject: [Haiku-bugs] [Haiku] #3915: [net_server] DHCP client should support Classless Static Routes Message-ID: <040.7b0954b67ba3604d3421e68f04b81db1@haiku-os.org> #3915: [net_server] DHCP client should support Classless Static Routes -----------------------+---------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- In our network we are using DHCP option 121 and 249 to supply static routes to our users.[[BR]] http://www.faqs.org/rfcs/rfc3442.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 13:59:10 2009 From: trac at haiku-os.org (diver) Date: Sun, 10 May 2009 11:59:10 -0000 Subject: [Haiku-bugs] [Haiku] #3915: [net_server] DHCP client should support Classless Static Routes In-Reply-To: <040.7b0954b67ba3604d3421e68f04b81db1@haiku-os.org> References: <040.7b0954b67ba3604d3421e68f04b81db1@haiku-os.org> Message-ID: <049.e3e13e7621cc99ae852352d428be3c32@haiku-os.org> #3915: [net_server] DHCP client should support Classless Static Routes --------------------------------+------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/net_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by diver): * component: - General => Servers/net_server -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:13:30 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 10 May 2009 12:13:30 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue Message-ID: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> #3916: struct stat POSIX naming issue -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- According to Open Group, {{{struct stat}}} has mandatory members {{{st_mtim}}} etc. http://www.opengroup.org/onlinepubs/9699919799/basedefs/sys_stat.h.html In [browser:haiku/trunk/headers/posix/sys/stat.h posix/sys/stat.h] they are called {{{st_mtime}}} etc. instead. Notice the extra letter. This breaks recent Git builds. Is this POSIX deviation for BeOS compatibility, or did simply no one complain yet? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:15:53 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 10 May 2009 12:15:53 -0000 Subject: [Haiku-bugs] [Haiku] #3902: Netscript over-written during upgrade installation In-Reply-To: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> References: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> Message-ID: <049.ea52e09b524867fafc742fb8742d64ad@haiku-os.org> #3902: Netscript over-written during upgrade installation --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Usually, except that this file needs to be configured for the specific NIC in the user's system. In fact I'm unsure whether it's even used with the current networking stack, maybe someone should check into that first. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:19:16 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 10 May 2009 12:19:16 -0000 Subject: [Haiku-bugs] [Haiku] #3905: Erroneous/unusable code in BeBook In-Reply-To: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> References: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> Message-ID: <049.7c5e6d75dc53e6e469b30dd9f8919f34@haiku-os.org> #3905: Erroneous/unusable code in BeBook ----------------------------+----------------------------------------------- Reporter: haiqu | Owner: nielx Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by haiqu): So we can't even update the API reference? Might as well junk the thing then. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:24:39 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 10 May 2009 12:24:39 -0000 Subject: [Haiku-bugs] [Haiku] #3906: lseek64/llseek routine missing from libroot.so In-Reply-To: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> References: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> Message-ID: <049.5dbbdad3072fd8666b3d131002472762@haiku-os.org> #3906: lseek64/llseek routine missing from libroot.so --------------------------------+------------------------------------------- Reporter: haiqu | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by haiqu): Great, so can they be mapped to lseek() in unistd.h then? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:30:38 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 10 May 2009 12:30:38 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.90cc7bc83d720cfbcc9673c4da6bf16c@haiku-os.org> #3916: struct stat POSIX naming issue -----------------------+---------------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by andreasf): I replaced {{{time_t st_mtime}}} with {{{struct timespec st_mtim}}} and added compatibility macro {{{st_mtime st_mtim.tv_sec}}}, as outlined above. Makes Git happy there. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:38:06 2009 From: trac at haiku-os.org (stippi) Date: Sun, 10 May 2009 12:38:06 -0000 Subject: [Haiku-bugs] [Haiku] #3878: Faults in haiku-cd build target In-Reply-To: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> References: <040.b06412e27c85cccdfd41fb20d28cfa8e@haiku-os.org> Message-ID: <049.6bbf9a56c0978a5c2ba4e85f3a7bc2da@haiku-os.org> #3878: Faults in haiku-cd build target ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Maybe it was r30671 which fixed the old IDE stack installation. Thanks for the update. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:42:45 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 10 May 2009 12:42:45 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.24e08d244a9d399ee54d87dc167f1e5c@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) --------------------------------------+------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by haiqu): Maybe you can explain why anyone would want to set their hardware clock to GMT, that one eludes me totally. I'm pretty sure that updating from a time server would cause problems with that setup. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 14:56:22 2009 From: trac at haiku-os.org (andreasf) Date: Sun, 10 May 2009 12:56:22 -0000 Subject: [Haiku-bugs] [Haiku] #3481: libio.h troubles on gcc4 Haiku In-Reply-To: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> References: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> Message-ID: <051.945a89deb9fb6bdad96ff9e6b3114af6@haiku-os.org> #3481: libio.h troubles on gcc4 Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by andreasf): * status: closed => reopened * resolution: fixed => Comment: Nope, still with us: Building expat with gcc 4.3 continues to complain about multiple definitions of the functions. The following workaround fixes the expat build for me: i. Comment out the initial declarations of the three affected functions. i. After the {{{__INLINE}}} wizardry, simply define {{{__INLINE}}} to {{{static inline}}}. Could it be that this error is caused by the GCC 4.3 special handling section in libio.h? No special options for c99 or gnu99 are being passed afaict. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 15:06:57 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 13:06:57 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.0d1dce3121a1db2386fd99e2a1cfc561@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by jonas.kirilla): This could be a comprehensive list of the folders that get _HAIKU entries: {{{ ./home/Desktop ./home/config/be ./home/config ./home/config/be/Applications ./home/config/be/Demos ./home/config/be/Desktop Applets ./home/config/be/Preferences ./home/config/settings/Mail/ProviderInfo ./home/config/settings/Mail ./home/config/settings/printers/Preview ./home/config/settings/printers/Save as PDF ./system/apps ./system/bin ./system ./system/data ./system/demos ./system/etc ./system/lib ./system/preferences ./system/servers ./system/add-ons/kernel/drivers/dev/bus ./system/add-ons/kernel/drivers/dev/disk ./system/add-ons/kernel/drivers/dev/dvb ./system/add-ons/kernel/drivers/dev/graphics ./system/add-ons/kernel/drivers/dev/input ./system/add-ons/kernel/drivers/dev/misc ./system/add-ons/kernel/drivers/dev/net ./system/add-ons/kernel/drivers/dev/disk/floppy ./system/add-ons/kernel/drivers/dev/disk/usb ./system/add-ons/kernel/drivers/dev/disk/virtual ./system/data/artwork ./system/data/sounds ./system/data/locale/languages ./system/etc/word_dictionary }}} FWIW: in /boot/system ./add-ons and ./fonts don?t get _HAIKU entries. It looks like "word_dictionary" gets the resources of the kernel. Am I the only one seeing this? ?:) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 15:30:34 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 13:30:34 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.9209b351ea802fee2541610025bdc27f@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) --------------------------------------+------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by jonas.kirilla): Various systems do it differently. (I think local time in the hardware clock is an old PC thing, whereas GMT is the unix/server way.) Being able to specify which method is in use is needed when alternating between multiple different operating systems on the same hardware. I believe some systems maintain filesystem timestamps in universal time and offset the presentation instead. This might be good when traveling. Imagine compiling when crossing over to a new timezone, and suddenly some of your timestamps went back or forward one hour! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 15:41:45 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 13:41:45 -0000 Subject: [Haiku-bugs] [Haiku] #3917: (real) Live CD crash in attribute_overlay filesystem Message-ID: <048.3429f9e610b8874371cbac5b9347da33@haiku-os.org> #3917: (real) Live CD crash in attribute_overlay filesystem ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I was opening and closing folders and opening files with DiskProbe. I don?t recall exactly what I was doing when Haiku crashed. See attached file. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 18:40:14 2009 From: trac at haiku-os.org (bga) Date: Sun, 10 May 2009 16:40:14 -0000 Subject: [Haiku-bugs] [Haiku] #3918: Keymap preferences should save selected keyboard layout. Message-ID: <038.8b7294b5b87499f0d605e7d899716e57@haiku-os.org> #3918: Keymap preferences should save selected keyboard layout. --------------------------------+------------------------------------------- Reporter: bga | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- 1 - Open Keymap Preferences. 2 - Switch to a keyboard layout different from the default one. 3 - Close Keymap and re-open it. 4 - Keyboard layout reset to the default. I would expect it to stick to the user selection as that is probably the layout the user has. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 18:52:21 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 10 May 2009 16:52:21 -0000 Subject: [Haiku-bugs] [Haiku] #3917: (real) Live CD crash in attribute_overlay filesystem In-Reply-To: <048.3429f9e610b8874371cbac5b9347da33@haiku-os.org> References: <048.3429f9e610b8874371cbac5b9347da33@haiku-os.org> Message-ID: <057.e265733837029d6dffbb149a48836eab@haiku-os.org> #3917: (real) Live CD crash in attribute_overlay filesystem ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: Probably the same overall reason as #3885 being that there is no locking done in either overlay. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 21:49:05 2009 From: trac at haiku-os.org (romain) Date: Sun, 10 May 2009 19:49:05 -0000 Subject: [Haiku-bugs] [Haiku] #3919: BListView does not Invoke when double cliking Message-ID: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> #3919: BListView does not Invoke when double cliking --------------------------------+------------------------------------------- Reporter: romain | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- seen in rev30699 Double clicking on an item of a BListView does not trigger invocation. This probably appeared with changes in rev30149, but the problem comes from the reset of fTrack->item_index in MouseUp. Releasing the mouse does not mean that the selected item is no more active. Also we do not need this to handle dragndrop status since try_drag is used for that. The attached patch should fix this I reproduce this very easily on a vmware install in the printer preference app: double click on one printer does not make it the default one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 23:14:54 2009 From: trac at haiku-os.org (luroh) Date: Sun, 10 May 2009 21:14:54 -0000 Subject: [Haiku-bugs] [Haiku] #3920: [Screen] cannot set workspace count for all resolutions Message-ID: <040.e7fb9d20fb925ddd709c1042598467e7@haiku-os.org> #3920: [Screen] cannot set workspace count for all resolutions --------------------------------+------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- The selection list doesn't scroll upwards, making it impossible to set a lower workspace count when using 800x480, 640x480 or 640x400, see attached picture.[[BR]] Tested with rev 30700. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 10 23:37:00 2009 From: trac at haiku-os.org (axeld) Date: Sun, 10 May 2009 21:37:00 -0000 Subject: [Haiku-bugs] [Haiku] #3905: Erroneous/unusable code in BeBook In-Reply-To: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> References: <040.167dfaecc2b49eaaa797b04ad3b9041f@haiku-os.org> Message-ID: <049.ef7129e35ab9ec5e8a5b41e5b1581703@haiku-os.org> #3905: Erroneous/unusable code in BeBook ----------------------------+----------------------------------------------- Reporter: haiqu | Owner: nielx Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Documentation | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by axeld): There is work in progress towards a new "Haiku book" - but since that is obviously a lot of work, and only very few people work on this, it'll take some time. Until then, the outdated BeBook is a lot better than nothing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 00:18:15 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 10 May 2009 22:18:15 -0000 Subject: [Haiku-bugs] [Haiku] #3906: lseek64/llseek routine missing from libroot.so In-Reply-To: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> References: <040.ba895146b7bfd443555a9811ae8c94ed@haiku-os.org> Message-ID: <049.c5936cc101280933d343f86838f84ccc@haiku-os.org> #3906: lseek64/llseek routine missing from libroot.so --------------------------------+------------------------------------------- Reporter: haiqu | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by bonefish): Replying to [comment:2 haiqu]: > Great, so can they be mapped to lseek() in unistd.h then? No, portable applications should just use lseek() instead of the non- portable functions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 00:24:25 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Sun, 10 May 2009 22:24:25 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing In-Reply-To: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> References: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> Message-ID: <053.83b0b079f88f1e34a4969426bbc825f2@haiku-os.org> #1583: Fallback when Preferred App is missing --------------------------------+------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by jonas.kirilla): * status: new => closed * resolution: => fixed Comment: This appears to have been fixed by bga in [30438]. Closing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 00:25:00 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 10 May 2009 22:25:00 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.aa60d796a5a6a804c2d0fab6293079b7@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) --------------------------------------+------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by bonefish): I find setting the hardware clock to GMT handy for laptops. When you're traveling, instead of meddling with the time, you can just set the timezone to your actual location. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 01:22:16 2009 From: trac at haiku-os.org (bga) Date: Sun, 10 May 2009 23:22:16 -0000 Subject: [Haiku-bugs] [Haiku] #3921: New ATA stack and audio CD problem. Message-ID: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> #3921: New ATA stack and audio CD problem. --------------------------+------------------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Whenever I try to mount an audio CD (with cdda-fs), I get the following in syslog: {{{ 2009-05-10 20:17:19 KERN: Media changed from /dev/disk/atapi/1/master/raw 2009-05-10 20:17:19 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/1/master/raw) 2009-05-10 20:17:19 KERN: trying: partitioning_systems/intel/extended/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: partitioning_systems/intel/map/v1 2009-05-10 20:17:19 KERN: intel: pm_identify_partition(11, 1: 0, 367243264, 2048) 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/bfs/v1 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/devfs/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/rootfs/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: partitioning_systems/session/v1 2009-05-10 20:17:19 KERN: raw_command: 2009-05-10 20:17:19 KERN: returned: 0.699 2009-05-10 20:17:19 KERN: trying: file_systems/attribute_overlay/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/cdda/v1 2009-05-10 20:17:19 KERN: raw_command: 2009-05-10 20:17:19 KERN: 01. 00:02.33 (length 02:02.32) 2009-05-10 20:17:19 KERN: 02. 02:04.65 (length 02:44.00) 2009-05-10 20:17:19 KERN: 03. 04:48.65 (length 03:28.33) 2009-05-10 20:17:19 KERN: 04. 08:17.23 (length 02:47.65) 2009-05-10 20:17:19 KERN: 05. 11:05.13 (length 02:36.47) 2009-05-10 20:17:19 KERN: 06. 13:41.60 (length 03:35.03) 2009-05-10 20:17:19 KERN: 07. 17:16.63 (length 02:37.07) 2009-05-10 20:17:19 KERN: 08. 19:53.70 (length 05:05.05) 2009-05-10 20:17:19 KERN: 09. 24:59.00 (length 02:37.53) 2009-05-10 20:17:19 KERN: 10. 27:36.53 (length 02:42.07) 2009-05-10 20:17:19 KERN: 11. 30:18.60 (length 02:41.23) 2009-05-10 20:17:19 KERN: 12. 33:00.08 (length 01:18.67) 2009-05-10 20:17:19 KERN: 13. 34:19.00 (length 05:33.68) 2009-05-10 20:17:19 KERN: returned: 0.8 2009-05-10 20:17:19 KERN: trying: file_systems/ext2/v1 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -2147483648 2009-05-10 20:17:19 KERN: trying: file_systems/fat/v1 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/iso9660/v1 2009-05-10 20:17:19 KERN: identify(11, 0x81404d80) 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/nfs/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/ntfs/v1 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/reiserfs/v1 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:19 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:19 KERN: check_sense: Illegal request 2009-05-10 20:17:19 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/userlandfs/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: trying: file_systems/write_overlay/v1 2009-05-10 20:17:19 KERN: returned: -1 2009-05-10 20:17:19 KERN: scanning with: file_systems/cdda/v1 2009-05-10 20:17:19 KERN: raw_command: 2009-05-10 20:17:21 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:21 KERN: raw_command: 2009-05-10 20:17:23 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:23 KERN: raw_command: 2009-05-10 20:17:23 KERN: 01. 00:02.33 (length 02:02.32) 2009-05-10 20:17:23 KERN: 02. 02:04.65 (length 02:44.00) 2009-05-10 20:17:23 KERN: 03. 04:48.65 (length 03:28.33) 2009-05-10 20:17:23 KERN: 04. 08:17.23 (length 02:47.65) 2009-05-10 20:17:23 KERN: 05. 11:05.13 (length 02:36.47) 2009-05-10 20:17:23 KERN: 06. 13:41.60 (length 03:35.03) 2009-05-10 20:17:23 KERN: 07. 17:16.63 (length 02:37.07) 2009-05-10 20:17:23 KERN: 08. 19:53.70 (length 05:05.05) 2009-05-10 20:17:23 KERN: 09. 24:59.00 (length 02:37.53) 2009-05-10 20:17:23 KERN: 10. 27:36.53 (length 02:42.07) 2009-05-10 20:17:23 KERN: 11. 30:18.60 (length 02:41.23) 2009-05-10 20:17:23 KERN: 12. 33:00.08 (length 01:18.67) 2009-05-10 20:17:23 KERN: 13. 34:19.00 (length 05:33.68) 2009-05-10 20:17:24 KERN: Media changed from /dev/disk/atapi/1/master/raw 2009-05-10 20:17:24 KERN: KDiskDeviceManager::_ScanPartition(/dev/disk/atapi/1/master/raw) 2009-05-10 20:17:24 KERN: trying: partitioning_systems/intel/extended/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: partitioning_systems/intel/map/v1 2009-05-10 20:17:24 KERN: intel: pm_identify_partition(11, 1: 0, 367243264, 2048) 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/bfs/v1 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/devfs/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/rootfs/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: partitioning_systems/session/v1 2009-05-10 20:17:24 KERN: raw_command: 2009-05-10 20:17:24 KERN: returned: 0.699 2009-05-10 20:17:24 KERN: trying: file_systems/attribute_overlay/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/cdda/v1 2009-05-10 20:17:24 KERN: raw_command: 2009-05-10 20:17:24 KERN: 01. 00:02.33 (length 02:02.32) 2009-05-10 20:17:24 KERN: 02. 02:04.65 (length 02:44.00) 2009-05-10 20:17:24 KERN: 03. 04:48.65 (length 03:28.33) 2009-05-10 20:17:24 KERN: 04. 08:17.23 (length 02:47.65) 2009-05-10 20:17:24 KERN: 05. 11:05.13 (length 02:36.47) 2009-05-10 20:17:24 KERN: 06. 13:41.60 (length 03:35.03) 2009-05-10 20:17:24 KERN: 07. 17:16.63 (length 02:37.07) 2009-05-10 20:17:24 KERN: 08. 19:53.70 (length 05:05.05) 2009-05-10 20:17:24 KERN: 09. 24:59.00 (length 02:37.53) 2009-05-10 20:17:24 KERN: 10. 27:36.53 (length 02:42.07) 2009-05-10 20:17:24 KERN: 11. 30:18.60 (length 02:41.23) 2009-05-10 20:17:24 KERN: 12. 33:00.08 (length 01:18.67) 2009-05-10 20:17:24 KERN: 13. 34:19.00 (length 05:33.68) 2009-05-10 20:17:24 KERN: returned: 0.8 2009-05-10 20:17:24 KERN: trying: file_systems/ext2/v1 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -2147483648 2009-05-10 20:17:24 KERN: trying: file_systems/fat/v1 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/iso9660/v1 2009-05-10 20:17:24 KERN: identify(11, 0x81404f00) 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/nfs/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/ntfs/v1 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/reiserfs/v1 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:24 KERN: atapi 1-0 error: device indicates transfer error after dma 2009-05-10 20:17:24 KERN: check_sense: Illegal request 2009-05-10 20:17:24 KERN: cd_read(): request.Wait() returned: General system error 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/userlandfs/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: trying: file_systems/write_overlay/v1 2009-05-10 20:17:24 KERN: returned: -1 2009-05-10 20:17:24 KERN: scanning with: file_systems/cdda/v1 2009-05-10 20:17:24 KERN: raw_command: 2009-05-10 20:17:26 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:26 KERN: raw_command: 2009-05-10 20:17:28 KERN: ata 1 error: command failed, error bit is set: 0x50 2009-05-10 20:17:28 KERN: raw_command: 2009-05-10 20:17:28 KERN: 01. 00:02.33 (length 02:02.32) 2009-05-10 20:17:28 KERN: 02. 02:04.65 (length 02:44.00) 2009-05-10 20:17:28 KERN: 03. 04:48.65 (length 03:28.33) 2009-05-10 20:17:28 KERN: 04. 08:17.23 (length 02:47.65) 2009-05-10 20:17:28 KERN: 05. 11:05.13 (length 02:36.47) 2009-05-10 20:17:28 KERN: 06. 13:41.60 (length 03:35.03) 2009-05-10 20:17:28 KERN: 07. 17:16.63 (length 02:37.07) 2009-05-10 20:17:28 KERN: 08. 19:53.70 (length 05:05.05) 2009-05-10 20:17:28 KERN: 09. 24:59.00 (length 02:37.53) 2009-05-10 20:17:28 KERN: 10. 27:36.53 (length 02:42.07) 2009-05-10 20:17:28 KERN: 11. 30:18.60 (length 02:41.23) 2009-05-10 20:17:28 KERN: 12. 33:00.08 (length 01:18.67) 2009-05-10 20:17:28 KERN: 13. 34:19.00 (length 05:33.68) }}} Also, in the root dir I can see 2 directories that were created: "Audio CD" and "Audio CD1". The second one is where the CD is actually mounted, but the first one was created by mounting the CD too (in fact, I see the CD icon show in the Desktop, disappear and show again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 01:26:48 2009 From: trac at haiku-os.org (bga) Date: Sun, 10 May 2009 23:26:48 -0000 Subject: [Haiku-bugs] [Haiku] #1583: Fallback when Preferred App is missing In-Reply-To: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> References: <044.f6960a6d8a01aa853e5029e1d3f97db2@haiku-os.org> Message-ID: <053.f028adc4cfa5a828204994a081bf51fa@haiku-os.org> #1583: Fallback when Preferred App is missing --------------------------------+------------------------------------------- Reporter: humdinger | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Comment(by bga): Yes, I didn't see this ticket but my fix indeed fixes this. Thanks. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 02:09:19 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 11 May 2009 00:09:19 -0000 Subject: [Haiku-bugs] [Haiku] #3921: New ATA stack and audio CD problem. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.f3f0a8b64e9ff0b14de806c6e7d0b6df@haiku-os.org> #3921: New ATA stack and audio CD problem. --------------------------+------------------------------------------------- Reporter: bga | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmlr): The errors can be ignored. They stem from the normal read commands that are not valid for the audio cd and are therefore aborted. The errors are handled correctly and the other filesystems that do not support audio cds get back the errors. The cdda fs, using the audio cd specific commands works however (indicated by the track list that is dumped). I have seen the double mount as well but I think it is not related to the ATA stack. Can you verify that this doesn't happen with the old IDE stack? I think I remember seeing it there as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 02:12:30 2009 From: trac at haiku-os.org (bga) Date: Mon, 11 May 2009 00:12:30 -0000 Subject: [Haiku-bugs] [Haiku] #3921: New ATA stack and audio CD problem. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.bac50f7fde8dd607e4c380afcc778c33@haiku-os.org> #3921: New ATA stack and audio CD problem. --------------------------+------------------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by bga): * owner: marcusoverhagen => bga * status: new => assigned Comment: Yes, I did some more testing and this seems to be a cdda-fs bug. I am on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 02:12:55 2009 From: trac at haiku-os.org (bga) Date: Mon, 11 May 2009 00:12:55 -0000 Subject: [Haiku-bugs] [Haiku] #3921: Problem mounting audio CD. (was: New ATA stack and audio CD problem.) In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.cd59f8f2fb2ce92977e7fba2e742ea8e@haiku-os.org> #3921: Problem mounting audio CD. --------------------------+------------------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 03:38:54 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 11 May 2009 01:38:54 -0000 Subject: [Haiku-bugs] [Haiku] #3902: Netscript over-written during upgrade installation In-Reply-To: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> References: <040.e3be958c70fdf9bcb64e652799ac1d1f@haiku-os.org> Message-ID: <049.038419b1f1996caafd86b0ace2d4d84b@haiku-os.org> #3902: Netscript over-written during upgrade installation --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Replying to [comment:1 scottmc]: > Shouldn't users not be changing things in the /boot/system folders? This is 100% correct. The system folder is off limits to 3rd party applications and the end user. Granted, this is currently done by convention and is not enforced by the system. While one could argue that the system folder needs to be modified in the case of sound drivers conflicting with OSS, I would point out that the desired functionality -- preventing such collision, has not yet been implemented. Rob, looking at Haiku's /boot/system/boot/Netscript file, the example commands appear to be CLI commands. In addition to this, looking at R5Bone's Netscript, it explicitly states to not edit the file and to instead add the commands to /boot/home/config/boot/UserBootScript. Could you try placing your customizations in UserBootScript? If it works, then Haiku's Netscript file should include a similar explanatory text comment to help avoid future confusion. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 05:51:40 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 11 May 2009 03:51:40 -0000 Subject: [Haiku-bugs] [Haiku] #3900: [patch] Update to OpenSSL 0.9.8k In-Reply-To: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> References: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> Message-ID: <050.4038997dfe11a6b7f26ba7a630a41d33@haiku-os.org> #3900: [patch] Update to OpenSSL 0.9.8k --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Axel noticed the licenses belong in /path/'''data'''/licenses and not /path/etc/licenses. This -v2.diff file points to an updated (and yet-to- be uploaded) archive that contains the license file in the correct location. Once again, I'll make an update once the file has been uploaded. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 08:13:14 2009 From: trac at haiku-os.org (kaliber) Date: Mon, 11 May 2009 06:13:14 -0000 Subject: [Haiku-bugs] [Haiku] #3481: libio.h troubles on gcc4 Haiku In-Reply-To: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> References: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> Message-ID: <051.e0bfb29fd5385ef759db788b67e60019@haiku-os.org> #3481: libio.h troubles on gcc4 Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by kaliber): If you want you can extract a correct patch for libio.h from TiltOS' patch http://svn.gna.org/viewcvs/pingwinek/trunk/projects/tiltos/tiltos.patch It is based on a newer code from glibc. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 09:34:17 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 07:34:17 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 Message-ID: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- In r.29857 connect with DHCP -while boot Haiku- working correctly but between r.29857 and r.30012 create changes which prevented the connection with DHCP on my desktop (btw. on my laptop dhcp work correctly) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 09:46:25 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 11 May 2009 07:46:25 -0000 Subject: [Haiku-bugs] [Haiku] #3923: Web links in Thunderbird email client no longer work when clicked Message-ID: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> #3923: Web links in Thunderbird email client no longer work when clicked -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Since yesterday's update on my system I can no longer click a link in email and get to the browser automagically. There was a big upgrade in mime types around that time, maybe something there caused it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 09:50:16 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 11 May 2009 07:50:16 -0000 Subject: [Haiku-bugs] [Haiku] #3924: Automount of USB stick crashes system to KDL Message-ID: <040.52bab368db01681c87b5deec7892bcbb@haiku-os.org> #3924: Automount of USB stick crashes system to KDL -------------------------+-------------------------------------------------- Reporter: haiqu | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Assertion failed: headers/private/kernel/util/DoublyLinkedList.h: 467 fFirst != __null && fLast != __null && (fFirst != fLast ... Thread 164 "Automounter" At the time I was installing a large file using the Expander, this might be relevant. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 09:52:15 2009 From: trac at haiku-os.org (stippi) Date: Mon, 11 May 2009 07:52:15 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.45c255e6cf3715a900427bd114bc00ca@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by stippi): Hubert, we are already 550 revisions later! This problem has long been fixed. Please try again with a current revision and report if it works again for you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 09:57:54 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Mon, 11 May 2009 07:57:54 -0000 Subject: [Haiku-bugs] [Haiku] #3923: Web links in Thunderbird email client no longer work when clicked In-Reply-To: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> References: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> Message-ID: <049.737a281cd826e0b3b0126796a4bff06d@haiku-os.org> #3923: Web links in Thunderbird email client no longer work when clicked --------------------+------------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------+------------------------------------------------------- Changes (by jonas.kirilla): * component: - General => System Comment: If it?s related it should improve soon. There were no URL mime types included before, but are now. In the meantime you can try setting BeZilla as the Preferred Application for the HTTP URL in the FileTypes preferences. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 10:05:40 2009 From: trac at haiku-os.org (axeld) Date: Mon, 11 May 2009 08:05:40 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.512085016b09540fb2e939d9d41d61c8@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by axeld): * component: - General => System/libroot.so Comment: This change would break binary compatibility, though. This change has been made in Issue 7 of the specs. Through the BeOS API detection, we could change this, but this would then require us to recompile all optional packages. Wouldn't it be POSIX, I also wonder why they didn't adopt the BSD version of this, and called them st_mtimespec etc. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 10:10:18 2009 From: trac at haiku-os.org (axeld) Date: Mon, 11 May 2009 08:10:18 -0000 Subject: [Haiku-bugs] [Haiku] #3914: Tracker crash In-Reply-To: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> References: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> Message-ID: <052.7de78d3481498789141ef18944f14a36@haiku-os.org> #3914: Tracker crash ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by axeld): Without a stack trace, I'm afraid this report is pretty useless. When in "gdb", please execute the "bt" command, at the very least. Also, always report the revision you experienced the problem with. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 10:12:47 2009 From: trac at haiku-os.org (axeld) Date: Mon, 11 May 2009 08:12:47 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.56ccb97d73330f19164559816a71ab1b@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by axeld): Yes, indeed, the legacy device must not be deleted before the vnode has been released. This is also what makes the whole disconnect mechanism work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 10:23:51 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 08:23:51 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.dd58cf91d2c4587f14bb361dbe50bf76@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): stippi you have right but I tested last revision ~30680 (I don't rebember now) and the same problem, but I searching (building) last working correctly revision and now I have 2 revision on HDD: r.29857 (working DHCP) and r30150 (DHCP failed on my desktop). Today I compile newest revision and upload syslog. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 11:02:20 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 11 May 2009 09:02:20 -0000 Subject: [Haiku-bugs] [Haiku] #3903: Time offset between local and GMT wrong in Clock preflet (easy) In-Reply-To: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> References: <040.7afe145abc8e68503cae128a7faf3e54@haiku-os.org> Message-ID: <049.c41993c9857cc7a5b58ce4ccf01ca585@haiku-os.org> #3903: Time offset between local and GMT wrong in Clock preflet (easy) --------------------------------------+------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Time & Date | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Comment(by haiqu): Hmmm. Well I don't travel between timezones a lot, and don't own a laptop. And this PC also has Win2k on it, which requires the RTC to be set to the local time. I guess I'll just leave it on local. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 11:07:56 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 11 May 2009 09:07:56 -0000 Subject: [Haiku-bugs] [Haiku] #3923: Web links in Thunderbird email client no longer work when clicked In-Reply-To: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> References: <040.5b350d19a4f41ea331b82b871b407555@haiku-os.org> Message-ID: <049.40214743d24ef1cb2d4fad5d18667f66@haiku-os.org> #3923: Web links in Thunderbird email client no longer work when clicked --------------------+------------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------+------------------------------------------------------- Comment(by haiqu): Yep, that worked. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 12:27:25 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 10:27:25 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.0fab4f6931afb6ce99b4a89ff0ec4d42@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): I checked r30704 (gcc4 hybrid) and the same. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 13:23:50 2009 From: trac at haiku-os.org (bga) Date: Mon, 11 May 2009 11:23:50 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.211c99c158cce785ad3c080efda8683f@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by bga): Unfortunatelly I can not help much with this but at least I can say that my recent change to DHCP should not be the cause of this as it is only relevnt to machines with more than one network card. Does manually configuring an IP work? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 13:58:36 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 11 May 2009 11:58:36 -0000 Subject: [Haiku-bugs] [Haiku] #3924: Automount of USB stick crashes system to KDL In-Reply-To: <040.52bab368db01681c87b5deec7892bcbb@haiku-os.org> References: <040.52bab368db01681c87b5deec7892bcbb@haiku-os.org> Message-ID: <049.e0032a5690aa44b91b4f49956b4f891f@haiku-os.org> #3924: Automount of USB stick crashes system to KDL -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Changes (by mmlr): * owner: mmlr => nobody * component: Drivers/USB => - General Old description: > Assertion failed: > > headers/private/kernel/util/DoublyLinkedList.h: 467 > > fFirst != __null && fLast != __null && (fFirst != fLast ... > > Thread 164 "Automounter" > > At the time I was installing a large file using the Expander, this might > be relevant. New description: Assertion failed: {{{ headers/private/kernel/util/DoublyLinkedList.h: 467 fFirst != __null && fLast != __null && (fFirst != fLast ... Thread 164 "Automounter" }}} At the time I was installing a large file using the Expander, this might be relevant. -- Comment: We really need stack traces for things like that. This is an assertion that is triggered by some code path, but just from the assertion message you cannot tell which. Is this reproducible? In any case it's not inside USB as USB doesn't use any doubly linked lists. It could be the legacy driver code or filesystem/partitioning related. Without a stack trace it's impossible to tell though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 15:04:49 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 13:04:49 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.225024f75b605d6b7d79090af3c6215d@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): Static IP don't work too. This only presumption. But problem from DHCP is since moment of change in structure of folders(/boot/beos/system on /boot/system) in Haiku, just after revision 29857... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 15:10:47 2009 From: trac at haiku-os.org (stippi) Date: Mon, 11 May 2009 13:10:47 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.8bcaa5cf210f4d5d993500c8a05a1729@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by stippi): Hm. Can you explain your method if installation? What network driver do you use? This begins to sound like a problem of an "unclean" installation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 16:19:21 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 11 May 2009 14:19:21 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.d803101d8a87109ea64bcf9d3685fdac@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): I think I've found the cause of this. It's probably not a wrongly set descriptor field at all, but a descriptor leak. This leak only happens on control transfers apparently and this explains why you all saw it and I couldn't. Control transfers are usually only used in initial device setup and for some rare later configuration. But in the case of hubs (and the KVM is a hub) it is used to poll the port status. This means that when there are hubs involved it would leak about 3 descriptors per second. In the end, if the controller lived long enough, it would have exhausted the physical memory pool, but it seems that way before that the controller stops with a process error. Probably because the queue gets too long after some time (the descriptors are inactive but still part of the queue that the controller has to parse through on every iteration). It's possible that when the linked descriptor list becomes too long that the controller simply doesn't have enough time to skim through all of them and then throws a process error. Going to fix the leak in any case (not sure where it happens yet) and then check if the other host controller drivers contain the same error. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 16:36:08 2009 From: trac at haiku-os.org (bga) Date: Mon, 11 May 2009 14:36:08 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.228bd35dc0f3763f739a89308e17b2d8@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bga): Hi Michael. Great that you are looking into this. Does your theory account for the fact that sometimes I see the problem after 5 minutes and sometimes after several hours? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 17:06:36 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 15:06:36 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.3e0960fbe0caac9971e26dc6b44fa276@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): Hmm, with Haiku, Zeta (necessary makebootable with Haiku or change zbeos with haiku_loader) or Linux (precisely on USB Flash by dd). I remove old folder and transfer new. I use default driver for Realtek 8139. Image with haiku-files don't work correctly too. Interesting because when use the same usb flash with laptop (realtek 8139 too) dhcp and net work fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 17:11:50 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 11 May 2009 15:11:50 -0000 Subject: [Haiku-bugs] [Haiku] #3924: Automount of USB stick crashes system to KDL In-Reply-To: <040.52bab368db01681c87b5deec7892bcbb@haiku-os.org> References: <040.52bab368db01681c87b5deec7892bcbb@haiku-os.org> Message-ID: <049.96a3823139a7fe22ed4f32ab4d64cdf5@haiku-os.org> #3924: Automount of USB stick crashes system to KDL -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by haiqu): Easily reproduced here on my Gigabyte GA-7IXE4 mobo. I've had no trouble at all with USB on my Athlon system, but then again I haven't used it much since installing Haiku on the weekend. Love to help with a stack trace but no way to set that up right now, I'd need a debug terminal because it locks the machine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 17:22:33 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 11 May 2009 15:22:33 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.3bfc22500eaa476042551fb23f6571c3@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): I take it back. The leak is actually a symptom of the process error, not the other way around. And it's not even a leak at all because canceling correctly cleans up. Since all values that according to specs could cause that process error look fine I'm back to the start. I'm clueless. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 17:58:09 2009 From: trac at haiku-os.org (bga) Date: Mon, 11 May 2009 15:58:09 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.7ebf883901168806de4f507d72ccdf4c@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by bga): Just to make this clear, your problem is obviously not DHCP, but networking in general. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 18:05:53 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 16:05:53 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.1a8305e9bbff420804fe90e2226c1065@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): Yes, this is very possible. Can was somehow (config files etc.) extort launch of system from DHCP? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 18:09:19 2009 From: trac at haiku-os.org (Hubert) Date: Mon, 11 May 2009 16:09:19 -0000 Subject: [Haiku-bugs] [Haiku] #2445: error with boot of SATA In-Reply-To: <041.16f039f4734e90f4abebd39280112309@haiku-os.org> References: <041.16f039f4734e90f4abebd39280112309@haiku-os.org> Message-ID: <050.7a1303c22b8f546dda770dba5ff15223@haiku-os.org> #2445: error with boot of SATA --------------------------+------------------------------------------------- Reporter: Hubert | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by Hubert): Working now. Please closed this ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 18:17:07 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 11 May 2009 16:17:07 -0000 Subject: [Haiku-bugs] [Haiku] #2445: error with boot of SATA In-Reply-To: <041.16f039f4734e90f4abebd39280112309@haiku-os.org> References: <041.16f039f4734e90f4abebd39280112309@haiku-os.org> Message-ID: <050.f3ad43fe18df91cd2d11dba4a107cdde@haiku-os.org> #2445: error with boot of SATA ---------------------------+------------------------------------------------ Reporter: Hubert | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by mmadia): * status: new => closed * resolution: => invalid Comment: As no changeset was mentioned as the cause of resolution, this ticket is being closed as invalid. Thanks for following through, Hubert. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 21:11:04 2009 From: trac at haiku-os.org (mjw) Date: Mon, 11 May 2009 19:11:04 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.82bff297dcb5bcac76b9ea9639082b9a@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by mjw): I had an investigate and found that the BSDs implement their own function called pthread_attr_get_np(). NetBSD code is here: http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libpthread/pthread_attr.c?rev=1.12 &content-type=text/plain&only_with_tag=MAIN FreeBSD core is here: http://svn.freebsd.org/viewvc/base/head/lib/libthr/thread/thr_attr.c?revision=178446&view=markup Man page is here: http://www.gsp.com/cgi-bin/man.cgi?section=3&topic=pthread_attr_get_np This is almost identical to the GNU version, except that you must call pthread_attr_init() before calling these functions. Looking at the complexity of the mono code, I don't think there is a nice cross platform way of doing this. If you do: pthread_attr_init(attr); pthread_create(..., attr, ...); pthread_attr_getstack(attr, ...); then Linux, OpenSolaris and FreeBSD (and, I assume, other BSDs) return default values for stack base and stack size. So, implementing pthread_attr_getstack() so that it returns the default values is simple. The only question is whether it is worth implementing either pthread_getattr_np() or pthread_attr_get_np(). If so, the argument comes down to whether you prefer BSD or GNU. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 11 23:08:56 2009 From: trac at haiku-os.org (smashIt) Date: Mon, 11 May 2009 21:08:56 -0000 Subject: [Haiku-bugs] [Haiku] #3925: swap-file size Message-ID: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> #3925: swap-file size -------------------------+-------------------------------------------------- Reporter: smashIt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- just got haiku to boot natively on my laptop to my surprise haiku used ~4gb of the 8gb partition for the swapfile (2x the physical ram) does that even make sense for a 32bit system when swap-file + physical ram exceed the adressspace of 4gb? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 00:32:33 2009 From: trac at haiku-os.org (umccullough) Date: Mon, 11 May 2009 22:32:33 -0000 Subject: [Haiku-bugs] [Haiku] #3925: swap-file size In-Reply-To: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> References: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> Message-ID: <051.ec7f225979b51a4e20ba6674e79e06c3@haiku-os.org> #3925: swap-file size -------------------------+-------------------------------------------------- Reporter: smashIt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): At some point, I think the Virtual Memory preferences were changed to default to 1 mb or something - but I think the system still defaults to 2x physical RAM if no preferences have been set? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 00:40:28 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 11 May 2009 22:40:28 -0000 Subject: [Haiku-bugs] [Haiku] #3925: swap-file size In-Reply-To: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> References: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> Message-ID: <051.fb8eac3c1ef6e4afc18d772f30f35be8@haiku-os.org> #3925: swap-file size -------------------------+-------------------------------------------------- Reporter: smashIt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): Not quite sure what this ticket is about. What shall be enhanced in what way? Regarding the technical facts: - There's no direct swap space related limit imposed by the size of the address space. Each process has its own address space, so the total amount of data that might need to be paged out is merely limited by the number of running processes. - We address pages with 32 bit indices, i.e. the current swap space limit is 16 TB. This limit could be lifted, if the need arises, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 01:02:55 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 11 May 2009 23:02:55 -0000 Subject: [Haiku-bugs] [Haiku] #3883: [patch] please implement pthread_attr_getstack() In-Reply-To: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> References: <038.c820c82e7afb76f42ddd9ec701f0856a@haiku-os.org> Message-ID: <047.a176533a4b3bd5c88e337e36e2f2d9bb@haiku-os.org> #3883: [patch] please implement pthread_attr_getstack() -------------------------------+-------------------------------------------- Reporter: mjw | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): I'd go with the GNU function for the time being. We can still decide to add the BSD function to our BSD compatibility library later. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 01:46:12 2009 From: trac at haiku-os.org (anevilyak) Date: Mon, 11 May 2009 23:46:12 -0000 Subject: [Haiku-bugs] [Haiku] #3925: swap-file size In-Reply-To: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> References: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> Message-ID: <051.910b438f9a8507b6fa24808ce8c93df0@haiku-os.org> #3925: swap-file size -------------------------+-------------------------------------------------- Reporter: smashIt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by anevilyak): With respect to the swap space + physical RAM adding up to > 4GB, this is entirely irrelevant. The 4GB address space limit is virtual per app (with the usual 2GB user / 2GB kernel split applying). As such you could hypothetically have, say, 6 apps all completely using their 2GB of userspace address area completely. This is perfectly acceptable and possible, but obviously you wouldn't be able to fit all that into RAM since on a 32-bit sys you can't have > 4GB physical without resorting to PAE hacks. As such you'd need at least 8GB of swap, probably more to support the above setup, and this is entirely possible, though you likely wouldn't do this in practice since saying it wouldn't be fun to use a system under such a load is a mild understatement. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 03:56:20 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 12 May 2009 01:56:20 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.50a59f3851f42117dd62f441cfdb74d8@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Hopefully fixed in r30714, please test. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 04:57:38 2009 From: trac at haiku-os.org (mmadia) Date: Tue, 12 May 2009 02:57:38 -0000 Subject: [Haiku-bugs] [Haiku] #3900: [patch] Update to OpenSSL 0.9.8k In-Reply-To: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> References: <041.908f81ec36c5e6ec9361371c60264858@haiku-os.org> Message-ID: <050.a97cd850107d582254466fedf03f3889@haiku-os.org> #3900: [patch] Update to OpenSSL 0.9.8k ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: applied in changeset [30708] Thanks Rene! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 09:55:53 2009 From: trac at haiku-os.org (_-Caleb-_) Date: Tue, 12 May 2009 07:55:53 -0000 Subject: [Haiku-bugs] [Haiku] #3926: The telnet application is not working properly on gcc4 builds Message-ID: <044.d43d36a0bcbf3afc501158a88d2e2635@haiku-os.org> #3926: The telnet application is not working properly on gcc4 builds --------------------------------+------------------------------------------- Reporter: _-Caleb-_ | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Not working properly and if it works compilations gcc2 (test on r30710) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 10:03:20 2009 From: trac at haiku-os.org (zooey) Date: Tue, 12 May 2009 08:03:20 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.0e813a873f640b48b03e01ce066edcba@haiku-os.org> #2327: Please add langinfo.h as a public header -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Old description: > [http://www.opengroup.org/onlinepubs/009695399/basedefs/langinfo.h.html] > > [http://dev.haiku- > os.org/browser/haiku/trunk/src/system/libroot/posix/glibc/locale/langinfo.h] New description: [http://www.opengroup.org/onlinepubs/009695399/basedefs/langinfo.h.html] [http://dev.haiku- os.org/browser/haiku/trunk/src/system/libroot/posix/glibc/locale/langinfo.h] -- Comment(by zooey): Since r30545 there now is a langinfo.h public header (that has come in with the locale kit), but I have no idea whether this is enough to solve the problems mentioned. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 10:40:45 2009 From: trac at haiku-os.org (_-Caleb-_) Date: Tue, 12 May 2009 08:40:45 -0000 Subject: [Haiku-bugs] [Haiku] #3776: The user account is unprotected In-Reply-To: <044.fdf0c96a34b00a5f7543bbd9834f057b@haiku-os.org> References: <044.fdf0c96a34b00a5f7543bbd9834f057b@haiku-os.org> Message-ID: <053.e062641b00292b002b0601feb0a63f31@haiku-os.org> #3776: The user account is unprotected --------------------------------+------------------------------------------- Reporter: _-Caleb-_ | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/net_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by _-Caleb-_): In gcc4 builds telnet program not work. ( Ticket #3296 ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 10:42:17 2009 From: trac at haiku-os.org (_-Caleb-_) Date: Tue, 12 May 2009 08:42:17 -0000 Subject: [Haiku-bugs] [Haiku] #3776: The user account is unprotected In-Reply-To: <044.fdf0c96a34b00a5f7543bbd9834f057b@haiku-os.org> References: <044.fdf0c96a34b00a5f7543bbd9834f057b@haiku-os.org> Message-ID: <053.1fbdc9af54456d1456e820ec33702b17@haiku-os.org> #3776: The user account is unprotected --------------------------------+------------------------------------------- Reporter: _-Caleb-_ | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Servers/net_server | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by _-Caleb-_): Replying to [comment:2 _-Caleb-_]: > In gcc4 builds telnet program not work. ( Ticket #3926 ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 10:59:30 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 08:59:30 -0000 Subject: [Haiku-bugs] [Haiku] #3925: swap-file size In-Reply-To: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> References: <042.e20bbb42b3c2aa794114362822b4723e@haiku-os.org> Message-ID: <051.2e5c2e958a70b8e1e76ab80a7cf4da7f@haiku-os.org> #3925: swap-file size -------------------------+-------------------------------------------------- Reporter: smashIt | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by axeld): What we could do is to limit the default swap size to some percentage of the volume it's on, like not more than 10% or 25%. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 11:35:17 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 09:35:17 -0000 Subject: [Haiku-bugs] [Haiku] #3875: "copyattr -d -r" results in attempts to write to read-only source partition. In-Reply-To: <038.c11eb449a698b1ce17726bcabf25e2b1@haiku-os.org> References: <038.c11eb449a698b1ce17726bcabf25e2b1@haiku-os.org> Message-ID: <047.654d93b11a3349055a50c7614e105ad3@haiku-os.org> #3875: "copyattr -d -r" results in attempts to write to read-only source partition. -------------------------------+-------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------+-------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Whatever the problem was, it doesn't seem to happen anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 13:26:39 2009 From: trac at haiku-os.org (modeenf) Date: Tue, 12 May 2009 11:26:39 -0000 Subject: [Haiku-bugs] [Haiku] #2132: AMD Geode Audio controller needs a driver In-Reply-To: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> References: <042.d10344523a2ec4cef3a9c264c525b477@haiku-os.org> Message-ID: <051.0a3b031a1598dbf883f8a0708039f063@haiku-os.org> #2132: AMD Geode Audio controller needs a driver ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: Component: Drivers/Audio | Version: Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by modeenf): * cc: fredrik@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 19:01:07 2009 From: trac at haiku-os.org (Disreali) Date: Tue, 12 May 2009 17:01:07 -0000 Subject: [Haiku-bugs] [Haiku] #3914: Tracker crash In-Reply-To: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> References: <043.3028db74f062fdbc0707741025d9c245@haiku-os.org> Message-ID: <052.bfbad42b296e4e246df9f6bf3ab6f3b6@haiku-os.org> #3914: Tracker crash ----------------------------------+----------------------------------------- Reporter: andreasf | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by Disreali): * cc: mdisreali@? (added) Comment: I experienced the same thing on r30676. Attached back trace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 20:49:04 2009 From: trac at haiku-os.org (stippi) Date: Tue, 12 May 2009 18:49:04 -0000 Subject: [Haiku-bugs] [Haiku] #2629: Automatic disk mounting not working. In-Reply-To: <038.a69687c7fc33e3e0b9d21ea4fc8dfaba@haiku-os.org> References: <038.a69687c7fc33e3e0b9d21ea4fc8dfaba@haiku-os.org> Message-ID: <047.e25149dc2a9246341a8032b926835c28@haiku-os.org> #2629: Automatic disk mounting not working. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: 1052 Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by stippi): This may be fixed in r30720. The automounter was using the wrong mount mode for removable media during the initial scan. I am not quite sure if your specific case is what I fixed along the way by fixing a couple of other problems, but please re-test in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 21:37:41 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 19:37:41 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.6390f004b0e78a835aac6499dcec5a2a@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 22:05:13 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 20:05:13 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.3cbc08b9b327a9ce080ed8fa796a2ad7@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by axeld): Should be fixed in r30726. I'm keeping this bug open until I got a confirmation (at least for a few weeks, that is), as I can't reproduce this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 22:13:24 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 20:13:24 -0000 Subject: [Haiku-bugs] [Haiku] #1739: Include a build system script to generate a proper 'develop' directory on Haiku In-Reply-To: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> References: <040.f743ba11ad5fa7b10c54bfab1bdaea69@haiku-os.org> Message-ID: <049.90078359f8b8c40b3e15cdaeab250aa0@haiku-os.org> #1739: Include a build system script to generate a proper 'develop' directory on Haiku ---------------------------+------------------------------------------------ Reporter: nielx | Owner: bonefish Type: enhancement | Status: closed Priority: blocker | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: So I guess this one can be closed, then, right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 22:48:39 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 20:48:39 -0000 Subject: [Haiku-bugs] [Haiku] #3898: Add a close tab menu item and shortcut In-Reply-To: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> References: <040.6987b6e95052a1152321fcc84f6cfd7a@haiku-os.org> Message-ID: <049.6845768bb9ccb98dd4fc221e13fd3dce@haiku-os.org> #3898: Add a close tab menu item and shortcut -----------------------------------+---------------------------------------- Reporter: axeld | Owner: jackburton Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------------+---------------------------------------- Comment(by axeld): In Mail, Command-Shift-W will close the window and keep the mail's status (ie. will leave it to "New"). I guess we could add that additional shortcut (as it can and may be overridden by apps), although I don't know if that will get much use. I would also like to add default shortcuts for minimizing/zooming. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 23:00:46 2009 From: trac at haiku-os.org (axeld) Date: Tue, 12 May 2009 21:00:46 -0000 Subject: [Haiku-bugs] [Haiku] #2629: Automatic disk mounting not working. In-Reply-To: <038.a69687c7fc33e3e0b9d21ea4fc8dfaba@haiku-os.org> References: <038.a69687c7fc33e3e0b9d21ea4fc8dfaba@haiku-os.org> Message-ID: <047.51c4ce0cb31841f53918cd7076beccc3@haiku-os.org> #2629: Automatic disk mounting not working. -----------------------------------+---------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Resolution: | Blockedby: 1052 Platform: All | Blocking: -----------------------------------+---------------------------------------- Comment(by axeld): I can still reproduce it here - I found a system of mine that still has an ext2 partition :-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 12 23:12:50 2009 From: trac at haiku-os.org (bga) Date: Tue, 12 May 2009 21:12:50 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.e21cad219279f352ae099b2c0d84c297@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by bga): Hy Axel. As I sent on an email to haiku-development, it is now crashing for me (sorry, no KDL image as I have no camera with me right now). The culprit seems to be the ps2 bus manager and the crash is in LegacyDevice::Remove(). It is obviously related to not having any ps2 devices connected to the machine as when I plug in a PS2 keyboard it works. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 00:49:32 2009 From: trac at haiku-os.org (bga) Date: Tue, 12 May 2009 22:49:32 -0000 Subject: [Haiku-bugs] [Haiku] #3921: Problem mounting audio CD. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.c0678020fa298c1f29f7a477674d93b4@haiku-os.org> #3921: Problem mounting audio CD. --------------------------+------------------------------------------------- Reporter: bga | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by bga): * owner: bga => stippi * status: assigned => new Comment: This is actually a automounter bug. If automatic disk mounting is disable and you manually mount the disk (via Tracker, not the command line), the double mounting does not happen. If automatic disk mounting is enabled, then it will be mounted, unmounted and mounted again. Assigning to stippi as he has been playing with automounter. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 01:26:32 2009 From: trac at haiku-os.org (awpeter) Date: Tue, 12 May 2009 23:26:32 -0000 Subject: [Haiku-bugs] [Haiku] #3927: MacBook keyboard/trackpad doesn't work Message-ID: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> #3927: MacBook keyboard/trackpad doesn't work -----------------------+---------------------------------------------------- Reporter: awpeter | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Just like in summary, i remember someone said that i should change the usb mode to polling (i compile haiku myself) and it worked then, but that's not really a solution. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 02:00:08 2009 From: trac at haiku-os.org (anevilyak) Date: Wed, 13 May 2009 00:00:08 -0000 Subject: [Haiku-bugs] [Haiku] #3927: MacBook keyboard/trackpad doesn't work In-Reply-To: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> References: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> Message-ID: <051.685b92d88d3570eec9abc0202d3e01bc@haiku-os.org> #3927: MacBook keyboard/trackpad doesn't work -------------------------+-------------------------------------------------- Reporter: awpeter | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Changes (by anevilyak): * owner: axeld => mmlr * component: - General => Drivers/USB Comment: If I'm not mistaken, this is a victim of ticket #5. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 02:14:24 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 13 May 2009 00:14:24 -0000 Subject: [Haiku-bugs] [Haiku] #3927: MacBook keyboard/trackpad doesn't work In-Reply-To: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> References: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> Message-ID: <051.c210fc7c09174cee6db660c746fa1bae@haiku-os.org> #3927: MacBook keyboard/trackpad doesn't work ---------------------------+------------------------------------------------ Reporter: awpeter | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by mmlr): * owner: mmlr => nobody * component: Drivers/USB => System/Kernel Comment: It's another victim of not using the IO-APIC. I thought we had this already? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 08:20:53 2009 From: trac at haiku-os.org (awpeter) Date: Wed, 13 May 2009 06:20:53 -0000 Subject: [Haiku-bugs] [Haiku] #3927: MacBook keyboard/trackpad doesn't work In-Reply-To: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> References: <042.4d20a1e8335e885e79d374bb1aed7a30@haiku-os.org> Message-ID: <051.55502cf9b5b593584750f27efbcc00a3@haiku-os.org> #3927: MacBook keyboard/trackpad doesn't work ---------------------------+------------------------------------------------ Reporter: awpeter | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by awpeter): Sorry if it's already present, i didn't find this bug though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 09:22:14 2009 From: trac at haiku-os.org (stippi) Date: Wed, 13 May 2009 07:22:14 -0000 Subject: [Haiku-bugs] [Haiku] #3921: Problem mounting audio CD. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.f48c37a2c12481a2140db10d7a605fa2@haiku-os.org> #3921: Problem mounting audio CD. --------------------------+------------------------------------------------- Reporter: bga | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by stippi): * owner: stippi => nobody Comment: No, it is not an auto mounter bug. It's a bug in the device manager or CDDA FS, there are two notifications "device added" when inserting an audio CD. The reason you don't see the bug when mounting manually is that nobody listens to the double notifications in this situation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 12:39:45 2009 From: trac at haiku-os.org (idefix) Date: Wed, 13 May 2009 10:39:45 -0000 Subject: [Haiku-bugs] [Haiku] #3908: Too easy to accidentally select first item off a popup menu In-Reply-To: <048.f6f8be390ec60b95e97f2f50f935568d@haiku-os.org> References: <048.f6f8be390ec60b95e97f2f50f935568d@haiku-os.org> Message-ID: <057.06ed75834e81fd1354563113acc5e1c4@haiku-os.org> #3908: Too easy to accidentally select first item off a popup menu --------------------------------+------------------------------------------- Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by idefix): Replying to [ticket:3908 jonas.kirilla]: > In Haiku I find myself often accidentally selecting the first menu item in Tracker?s context menus. Perhaps I move the mouse too soon after having released the right mouse button (when opening the menu), and the mouse button release message gets wrongly interpreted as being from the new location? This could be related to bug #3267 and #3373. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 12:50:46 2009 From: trac at haiku-os.org (bga) Date: Wed, 13 May 2009 10:50:46 -0000 Subject: [Haiku-bugs] [Haiku] #3921: Problem mounting audio CD. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.46b10dade45bfa6b000326a547ec8b95@haiku-os.org> #3921: Problem mounting audio CD. --------------------------+------------------------------------------------- Reporter: bga | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by bga): * owner: nobody => bga Comment: Interesting. I will take a second look at it then. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 13:35:13 2009 From: trac at haiku-os.org (haiqu) Date: Wed, 13 May 2009 11:35:13 -0000 Subject: [Haiku-bugs] [Haiku] #3839: Thunderbird crashes if attaching files to email In-Reply-To: <040.f354711a08343ad3c0c9b83ab3f6cfd1@haiku-os.org> References: <040.f354711a08343ad3c0c9b83ab3f6cfd1@haiku-os.org> Message-ID: <049.324ce6ed1818c7ed2417984c85fa6777@haiku-os.org> #3839: Thunderbird crashes if attaching files to email --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Problem resolved as at r30739, please close. Nice work, whoever fixed that one! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 14:52:46 2009 From: trac at haiku-os.org (stippi) Date: Wed, 13 May 2009 12:52:46 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.bfcc584aa092b1cdb28b4f60c1b4d4c6@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by stippi): I am very happy to report that I have run Haiku in three sessions that lasted longer than 5 to 6 hours each and have not seen this problem again. Usually, I would see it after 30 minutes to 2 hours at most. Awesome! What about you, BGA? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 15:11:33 2009 From: trac at haiku-os.org (bga) Date: Wed, 13 May 2009 13:11:33 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.fe3c08db0d7fa823124b5f8b1e69e93e@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by bga): Sorry, I forgot to comment here. Yes, I used haiku yesterday for several hours and saw no problem. The only reason I can not say for sure that this is fixed is because it used to happen wuite randomly but based on stippi's report I guess this is really sorted up. Thanks Michael. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 16:21:11 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 13 May 2009 14:21:11 -0000 Subject: [Haiku-bugs] [Haiku] #3928: volume control as replicant blocks windows from having focus Message-ID: <042.93215fe06f2f359792bd761ed3a46cba@haiku-os.org> #3928: volume control as replicant blocks windows from having focus -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- When the volume control is set as a replicant the any open windows start to act strangely, not allowing the user to select them, move them or even close them, their tabs remain grey. Removing the volume control replicant and they work like normal again. I've seen this happen on two different systems, both on real hardware, but non-working audio. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 16:27:39 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 13 May 2009 14:27:39 -0000 Subject: [Haiku-bugs] [Haiku] #3929: Strange desktop icon behavior Message-ID: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> #3929: Strange desktop icon behavior -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- In recent builds I've been seeing the desktop icons change to mini-icon mode on reboot. When i check to see what mode they are set at, nothing is checkmarked, so i change them back to normal default, icon 32 size and that seems to fix it, until the next reboot that is. I've only noticed this happening in the past couple weeks or so, builds newer than r30500 or so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 16:36:25 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 13 May 2009 14:36:25 -0000 Subject: [Haiku-bugs] [Haiku] #3803: Random characters displayed in Terminal In-Reply-To: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> References: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> Message-ID: <049.43cc0c21e0b230e0f789cf599582c69b@haiku-os.org> #3803: Random characters displayed in Terminal --------------------------------+------------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by scottmc): IIRC this seems to only happen to the last char on a line, and only when you are near the bottom of the terminal where it needs to scroll up. And the char it gets replaced with it a copy of the same char that is under it, so it's almost as if it's scrolling up the wrong char. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 16:45:09 2009 From: trac at haiku-os.org (fishpond) Date: Wed, 13 May 2009 14:45:09 -0000 Subject: [Haiku-bugs] [Haiku] #3594: PS2 Keyboard/Mouse problems on HP Compaq NX7400 Notebook In-Reply-To: <043.31d7b84a03010bbfa8abb11831290f5a@haiku-os.org> References: <043.31d7b84a03010bbfa8abb11831290f5a@haiku-os.org> Message-ID: <052.07497b1d889f23a240387f03c9b0e565@haiku-os.org> #3594: PS2 Keyboard/Mouse problems on HP Compaq NX7400 Notebook ----------------------------------+----------------------------------------- Reporter: siarzhuk | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: Unscheduled Component: Drivers/Keyboard/PS2 | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by fishpond): * platform: All => x86 * version: => R1 development Comment: Keyboard reset seems to go into timeout. Same problem on HP nx9420. Have run modified code where the missing acknowledgement on the reset is being ignored and got a working keyboard. Behaviour still unclear to me, timeout is 4 seconds which should be sufficient. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 16:50:26 2009 From: trac at haiku-os.org (axeld) Date: Wed, 13 May 2009 14:50:26 -0000 Subject: [Haiku-bugs] [Haiku] #3929: Strange desktop icon behavior In-Reply-To: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> References: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> Message-ID: <051.6a97ca13ea39665f0684f6aaec90c5cc@haiku-os.org> #3929: Strange desktop icon behavior ----------------------------------+----------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by axeld): * owner: axeld => stippi * component: - General => Applications/Tracker -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 17:35:59 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 13 May 2009 15:35:59 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.e6382fe069b2c4926df492737abf6656@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Since we generally support BeOS drivers, this change will also require API remapping in the kernel. Also, file systems should fill in the tv_nsec field correctly. Will look into this later tonight. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 17:53:34 2009 From: trac at haiku-os.org (michael.weirauch) Date: Wed, 13 May 2009 15:53:34 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.182f8298d2e74f8223c0f71ec39fc042@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): r30772; ata-stack; For reproduction, I wen't on and wrote a little script which dd's 10 images 100MB each to disk. When setting all safe mode options, or just "Disable IDE-DMA" and "Disable SMP" I can run the dd writes several times without freeze. What is reproduceable is that after the images have been written, the "scsi scheduler" kernel thread sucks up one cpu core 100% for about 3-5minutes and then reliefs again. During that high load of the thread a "sync" or system shutdown is not possible. The UI (Deskbar + ActivityMonitor replicants on Desktop) are frozen for a bit of time. The Terminal cursor blinks, and I can move windows around. When letting SMP enabled, I could produce a total freeze on third run of the dd writes. (Mileage on subsequent test might vary I guess, though.) Perhaps there is some other fix required as done in r30454 as I do have ICH9M running in compat mode? (This rev btw helped a lot regarding uptime until freeze for me.) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 20:01:05 2009 From: trac at haiku-os.org (schmedly) Date: Wed, 13 May 2009 18:01:05 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.b3271cf2390e9138943a8b5f5c06bdef@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by schmedly): Been running for nearly 24 hours here and no problem at all with the dedicated keyboard or mouse ports. I did however notice that the shared USB ports exhibit behavior similar to the original problem. Can anyone else verify this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 20:49:43 2009 From: trac at haiku-os.org (Hubert) Date: Wed, 13 May 2009 18:49:43 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.c98470bafcbb8ffa792f7515f2f3010b@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): I made test: I replace all folders and files from /boot/system/addons/kernel/network with rev. 30751 on files (and folders) from /boot/beos/system/addons/kernel/network with rev. 29857 (last revision with workong network at me), next I reboot system and I have DHCP and working network in r.30751. What was introduced or change in source between rev.29857 and rev.30751 ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 13 21:32:25 2009 From: trac at haiku-os.org (HaikuBot) Date: Wed, 13 May 2009 19:32:25 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.9556956361df4cd8350071d21c127a8a@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): I hope it helped you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 02:11:14 2009 From: trac at haiku-os.org (mmadia) Date: Thu, 14 May 2009 00:11:14 -0000 Subject: [Haiku-bugs] [Haiku] #3930: AboutSystem - manage duplicate OptionalPackageDescriptions Message-ID: <041.058ac659e2925af5287d3156ef3cf52e@haiku-os.org> #3930: AboutSystem - manage duplicate OptionalPackageDescriptions --------------------------------------+------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Applications/AboutSystem | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- This [http://www.freelists.org/post/haiku-development/OptionalPackages- how-to-properly-package-its-dependencies,1 haiku-development mailing list thread] raised the issue of having .OptionalPackageDescriptions for the same piece of software. Such a situation may occur when giving attribution to an OptionalPackage's included dependencies. A specific example is libxml2. Currently it is listed in AboutSystem. Once NetSurf is repackaged to include a more complete .OptionalPackageDescription, it will also give recognition to libxml2. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 04:01:23 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 14 May 2009 02:01:23 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.233333123ee0038788b411f99189e3b1@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Replying to [comment:27 schmedly]: > Been running for nearly 24 hours here and no problem at all with the dedicated keyboard or mouse ports. I did however notice that the shared USB ports exhibit behavior similar to the original problem. Can anyone else verify this? I don't quite understand. What do you mean by 'shared ports' and what behaviour do you mean exactly? The one of the original report or your initial comment? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 04:22:09 2009 From: trac at haiku-os.org (schmedly) Date: Thu, 14 May 2009 02:22:09 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.c2738fbd7337d13896a87a96342ef286@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by schmedly): On this KVM model (ATEN CS-1764) there are four USB ports. Two are the dedicated console (keyboard and mouse) and two are extra ports for device sharing. I'm assuming the distinction is that PS/2 emulation may be done for the console ports. While the most recent changes allowed those dedicated console ports to work for more than 24 hours in my test.. the original behavior of the 'keyboard or mouse dropping off randomly' still occurs with other items which are attached to the device sharing ports. In this case I have two keyboards. One older Apple keyboard attached to the console port (which now works perfectly) and another (the new aluminum Apple keyboard) attached to a device sharing port. This is because I prefer the aluminum keyboard BUT the console ports do not provide enough power for it to work. Odd situation I know, but it allowed me to notice the 'dropping off' behavior continue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 04:59:03 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 14 May 2009 02:59:03 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.ab2002478c653efc9eeb243345fe5d06@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmlr): Replying to [comment:29 schmedly]: > I'm assuming the distinction is that PS/2 emulation may be done for the console ports. That makes no real sense, there's no emulation going on anywhere. > While the most recent changes allowed those dedicated console ports to work for more than 24 hours in my test.. the original behavior of the 'keyboard or mouse dropping off randomly' still occurs with other items which are attached to the device sharing ports. What does the syslog say when this happens? Also does this really happen randomely or is it related to switching? A listusb -v output would make sense in any case to judge what device topology is present. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 02:20:59 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 14 May 2009 00:20:59 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.986c29bd8880ccd2fe2d360119b893ae@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): Unfortunately this turns out to be seriously non-trivial, since the stat structure is not only passed to a handful of POSIX functions, but is also used in the Be API -- worst of all virtual methods like BRefFilter::Filter() and BStatable::GetStat(). ATM I don't see a solution other than forking off compatibility versions of the concerned libraries. Suggestions welcome. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 08:40:32 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 14 May 2009 06:40:32 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.c012a48bf2d6ab96f23e544baafc29ef@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Good morning :-) Good you posted that last thing, I did not get notified of the added logfile by itself. Anyhow: you have a widescreen panel 1680x1050 on head2, and a VGA screen on head1 according to the log. The mode you are actually setting when starting Haiku is 1280x1024 in 32bit color. The log seems OK. During this bootup, you did not disable the acceleration engine BTW. A few questions: - do you have indeed two screens connected? - if you specify failsafe mode, do you also specify 1280x1024? or is this the default resolution that will be used then? - if you don't specify failsafe mode: do you see the icons screen or does the monitor shut-off in the beginning of that bootup-phase? Things you can try: - modify the settings file for the next items (one by one) pgm_panel true (could help) and after a next failed boot maybe try: switchhead true (not likely the problem) -does your digital screen have a VGA connector? try using it via that connector. You could try both connectors on the gfx card: the VGA one and the DVI one using a DVI to VGA adaptor. Would it work then? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 11:12:35 2009 From: trac at haiku-os.org (axeld) Date: Thu, 14 May 2009 09:12:35 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.183ced0142405f5691b07e4c995d1587@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by axeld): I've probably overseen something, but can't we just call BRefFilter::Filter() with the stat as suggested by the binaries ABI version? And for GetStat(), we would use the "right" version of fstat() again depending on the ABI version of the caller? The former might still be problematic in mixed environments (add-ons vs. app), but that shouldn't happen very often, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 13:49:34 2009 From: trac at haiku-os.org (haiqu) Date: Thu, 14 May 2009 11:49:34 -0000 Subject: [Haiku-bugs] [Haiku] #3688: C-Media CMI8738 sound driver needed In-Reply-To: <040.b818ba1dd2ca667b8f8baed07629af8f@haiku-os.org> References: <040.b818ba1dd2ca667b8f8baed07629af8f@haiku-os.org> Message-ID: <049.82885b35f3b3f99d005a8d78434de9d2@haiku-os.org> #3688: C-Media CMI8738 sound driver needed ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Drivers/Audio | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Comment(by haiqu): Attaching my current work on this driver, now suspended due to lack of ISA memory support. Included in the zipfile is diff against the cmedia directory and one missing header file required by the driver. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 14:34:36 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 14 May 2009 12:34:36 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.782ac35684dce5650d20a84a45897522@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by bonefish): Replying to [comment:5 axeld]: > I've probably overseen something, but can't we just call BRefFilter::Filter() with the stat as suggested by the binaries ABI version? And for GetStat(), we would use the "right" version of fstat() again depending on the ABI version of the caller? > > The former might still be problematic in mixed environments (add-ons vs. app), but that shouldn't happen very often, anyway. Not only add-ons would be a problem, but also libraries. And we don't control who calls BRefFilter::Filter() -- I believe it's only BFilePanel in the Be API, but an application or library could use the class for its own purposes as well. BStatable::GetStat() is really the lesser problem, since one can't even derive classes from BStatable. A safe solution (besides compatibility libraries) would be to introduce a {{{struct stat_beos}}} which resembles the old {{{struct stat}}}, and use it in BRefFilter::Filter() and BStatable::GetStat(). In case of BRefFilter this would break source compatibility, in case of BStatable we could use a reserved virtual slot to prevent that, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 16:16:24 2009 From: trac at haiku-os.org (schmedly) Date: Thu, 14 May 2009 14:16:24 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.9f535b3def2dbeaabb9f3656d162f530@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by schmedly): Replying to [comment:30 mmlr]: > Replying to [comment:29 schmedly]: > > I'm assuming the distinction is that PS/2 emulation may be done for the console ports. > > That makes no real sense, there's no emulation going on anywhere. Sorry, I was told when USB KVM's first started showing up that they still used a form of PS/2 emulation internally. My point was just that the console ports are separate from the shared device port. > What does the syslog say when this happens? > > Also does this really happen randomely or is it related to switching? > > A listusb -v output would make sense in any case to judge what device topology is present. And sorry for the double post of the file, BeZilla errored. That's what I get for doing it in Haiku. I'll do more switching and add syslog next. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 17:54:46 2009 From: trac at haiku-os.org (stippi) Date: Thu, 14 May 2009 15:54:46 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder In-Reply-To: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> References: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> Message-ID: <050.77382615568e609de140e3c8d2a56475@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by stippi): Now I have the situation, that the files in the folder must have disappeared again, back to those lucky 13, but Beam shows 33 messages in that folder still. I assume this is because of it's cache. But what's weird is that I can still read all 33 mails in Beam. How is that possible? I assume Beam caches entry_refs or maybe even node_refs. So the file data must still be accessible through some means other than iterating the directory. I don't know if that's maybe a hint to look for the error in a certain direction. And look at the Terminal, ls gives "reading directory .: Bad data". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 19:48:42 2009 From: trac at haiku-os.org (HaikuBot) Date: Thu, 14 May 2009 17:48:42 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.da43445b1417bfc65281e31c8bf53a90@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Greeting again :) I have good news. With "pgm_panel true" and "switchhead false" doesn`t work. But when i try boot with "true" for both variable, Haiku booted sucessfull. Thanks for help. Close ticket, please. Good Luck. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 19:53:36 2009 From: trac at haiku-os.org (stippi) Date: Thu, 14 May 2009 17:53:36 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.f13414e3ff0bd728809087775aaff332@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): I would keep the ticket open until the driver doesn't need tweaking via the settings like this. IMHO, it should work out of the box. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 14 21:03:12 2009 From: trac at haiku-os.org (Hubert) Date: Thu, 14 May 2009 19:03:12 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.527ce998b8a1bd254038253c1b13657b@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): I tested precisely: last working rev.29984; frist not correct rev.30008; http://dev.haiku-os.org/changeset?old_path=%2Fhaiku%2Ftrunk%2Fsrc%2Fadd- ons%2Fkernel%2Fnetwork&old=29984&new_path=%2Fhaiku%2Ftrunk%2Fsrc%2Fadd- ons%2Fkernel%2Fnetwork&new=30008 http://dev.haiku-os.org/changeset?new=30008%40haiku%2Ftrunk%2Fsrc%2Fadd- ons%2Fkernel%2Fnetwork&old=29986%40haiku%2Ftrunk%2Fsrc%2Fadd- ons%2Fkernel%2Fnetwork -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 01:34:07 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 14 May 2009 23:34:07 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.571cc72b339f9bba1ab31cde3bd208e6@haiku-os.org> #2327: Please add langinfo.h as a public header -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): With r30665 configuring python-2.6.2, checking for langinfo.h fails, here's the config.log for it: {{{ configure:6142: checking langinfo.h usability configure:6159: gcc -c -g -O2 conftest.c >&5 In file included from /boot/home/Python-2.6.2-haiku-test/conftest.c:65: /boot/common/include/langinfo.h:4: LocaleStrings.h: No such file or directory }}} Seems we need LocaleStrings.h to exist, perhaps it can be stubbed in for now? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 01:55:32 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 14 May 2009 23:55:32 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.9d61d95549558271b4044b66fd38ed13@haiku-os.org> #2327: Please add langinfo.h as a public header -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): I just tried to comment out the #include line for LocalStrings.h and it then allowed configure to find and use langinfo.h but then it fails during make: {{{ gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o Python/pythonrun.o Python/pythonrun.c /boot/home/Python-2.6.2-haiku-test/Python/pythonrun.c: In function `Py_InitializeEx': /boot/home/Python-2.6.2-haiku-test/Python/pythonrun.c:275: `B_CODESET' undeclared (first use in this function) /boot/home/Python-2.6.2-haiku-test/Python/pythonrun.c:275: (Each undeclared identifier is reported only once /boot/home/Python-2.6.2-haiku-test/Python/pythonrun.c:275: for each function it appears in.) make: *** [Python/pythonrun.o] Error 1 ~/Python-2.6.2-haiku-test> }}} Line 275 refers to CODESET which gets set (I assume) to B_CODESET, but B_CODESET is undeclared -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 09:06:54 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 15 May 2009 07:06:54 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.e2854443720d87c4a8e9e7b1cc5d7e53@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi again HaikuBot, I have some questions left, can you help out please? Can you delete the driver's logfile and reboot with the working settings? Please upload the logfile resulting from that so I get a bit more info about what's going on... And please answer these questions: -How many monitors are connected? just one, or two? (connect each monitor using just one cable please) - are you using a DVI cable or a VGA cable for the monitor(s)? Thanks! (good to hear you have a picture BTW :-) @ Stippi: Hi Stephan! In theory you are right of course. But in practice this is unreachable. There will always be systems that won't run Haiku: whatever the reason. Anyhow, let's leave this ticket open for now awaiting at least a better understanding of what's going on. Once that's known, and the driver has been updated for the best results possible, it needs to be enough. Even though not every system out there might work out of the box.. example: the Kernel VESA call is not always succesfull. I've seen cards that don't work in VESA mode though they say they should... Solution: a manual tweak (select lower resolution) is nessesary to bootup the system succesfully. I don't think we can have a full list of all cards in the world, combined with all possible BIOS versions, combined with all monitors to see if we need to fallback to a lower mode because it's known that a certain combination won't work as it should.. :-/ Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 09:38:18 2009 From: trac at haiku-os.org (zooey) Date: Fri, 15 May 2009 07:38:18 -0000 Subject: [Haiku-bugs] [Haiku] #2327: Please add langinfo.h as a public header In-Reply-To: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> References: <042.13ce36fe49dd2ce506a6744b61adb8c8@haiku-os.org> Message-ID: <051.89275d9e0e89736574d5429283d45401@haiku-os.org> #2327: Please add langinfo.h as a public header -------------------------+-------------------------------------------------- Reporter: kaliber | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by zooey): LocaleStrings.h is part of the locale kit, so it does exist, but the required search path has not been added to BEINCLUDES yet. If you are really keen to proceed, you could add /boot/develop/headers/be/locale to BEINCLUDES manually and see where that gets you. You would then probably have to link resulting binaries against liblocale.so, too. But all those solutions are of temporary nature, since the locale kit awaits better integration - for instance it is not yet clear if it shall be part of libbe or maybe even libroot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 10:20:38 2009 From: trac at haiku-os.org (burton_) Date: Fri, 15 May 2009 08:20:38 -0000 Subject: [Haiku-bugs] [Haiku] #3806: BView with a BScrollView crashes when used as a replicant In-Reply-To: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> References: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> Message-ID: <051.3f59ded159fbf4c13d44ced984b72aa2@haiku-os.org> #3806: BView with a BScrollView crashes when used as a replicant -----------------------+---------------------------------------------------- Reporter: burton_ | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by burton_): in 30759 the replicant works, but, as you already said, the scrollbar doesn't work in the replicant view. I tried to add 'm'essage->PrintToStream()'' to the ''NoteView::MessageReceived()'' and to the ''NoteText::MessageReceived()'' of our small program (http://dev.osdrawer.net/projects/show/takenotes) but there's no output on the terminal. If I add that instruction to the ''NoteView::Archive('') I obtain the BMessage structure that contains the different views. I'll open a small OT, but in our program since the latest reviews the BColorControl object causes a lot of artifacts, should i open another ticket ? Thanks for your help. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 11:12:10 2009 From: trac at haiku-os.org (stippi) Date: Fri, 15 May 2009 09:12:10 -0000 Subject: [Haiku-bugs] [Haiku] #3806: BView with a BScrollView crashes when used as a replicant In-Reply-To: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> References: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> Message-ID: <051.ca33d8c9c452477f84e6f0c9b8481dd6@haiku-os.org> #3806: BView with a BScrollView crashes when used as a replicant -----------------------+---------------------------------------------------- Reporter: burton_ | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Wow, that was a long time ago, my memory doesn't go 3 weeks back so easily! If you want to obtain output from your replicant, you have to launch Tracker itself in a Terminal: {{{ hey Tracker quit /system/Tracker & }}} Then you can see the output from your replicant in that Terminal. Anyways, what I wanted you to do was to get the output from running your replicant in BeOS. I want to know the message format when archiving BScrollBar. If you add the message->PrintToStream() in your TextView, you should be able to drop the replicant onto your own TextView and thereby print the archive contents to the Terminal. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 13:02:52 2009 From: trac at haiku-os.org (burton_) Date: Fri, 15 May 2009 11:02:52 -0000 Subject: [Haiku-bugs] [Haiku] #3806: BView with a BScrollView crashes when used as a replicant In-Reply-To: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> References: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> Message-ID: <051.280eb87685fca3b823fc14787315196a@haiku-os.org> #3806: BView with a BScrollView crashes when used as a replicant -----------------------+---------------------------------------------------- Reporter: burton_ | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by burton_): i attached the Tracker output as you said. I put the istruction message->PrintToStream() in both the View and the TextView. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 13:08:36 2009 From: trac at haiku-os.org (stippi) Date: Fri, 15 May 2009 11:08:36 -0000 Subject: [Haiku-bugs] [Haiku] #3806: BView with a BScrollView crashes when used as a replicant In-Reply-To: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> References: <042.1442169f3aa0143b2989913e1e7739a5@haiku-os.org> Message-ID: <051.55c29a18385c62ac76abc2a605cd74e1@haiku-os.org> #3806: BView with a BScrollView crashes when used as a replicant -----------------------+---------------------------------------------------- Reporter: burton_ | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by stippi): Thanks, but sorry, this is not what I need. Don't worry about it, I will try to get my BeOS system back to work and do the tests myself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 14:40:36 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 15 May 2009 12:40:36 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.b5cb8219209413b60245d2bfa686c6d9@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): I think hurried with my conclusions. It works when display connected or via VGA cable or via DVI, but when connected both cabels, Haiku does't boot. Also when connected via DVI list of resolutions in Screen-preflet is correct (for widescreen monitor), but when connected via VGA screen in resolutions list do not contains values for widescreen monitor. And one more thing: {{{ "~> ls /dev/graphics/ 10de_0393_010000 vesa" }}} I think there must be "nv" instead of "vesa" if suppose driver works. But one pleases now I can use 1680x1050. :) Replying to [comment:6 rudolfc]: > - if you specify failsafe mode, do you also specify 1280x1024? or is this the default resolution that will be used then? Yes, I specify 1280x1024, by default it 1024x768. > - if you don't specify failsafe mode: do you see the icons screen or does the monitor shut-off in the beginning of that bootup-phase? Yes, i see all boot icons, monitor is shutting down after last icon (rocket). Replying to [comment:9 rudolfc]: > I have some questions left, can you help out please? > Can you delete the driver's logfile and reboot with the working settings? Please upload the logfile resulting from that so I get a bit more info about what's going on... As you can read above, I maked wrong conclusions, it works in VESA. > -How many monitors are connected? just one, or two? (connect each monitor using just one cable please) One monitor, 22 inches. > - are you using a DVI cable or a VGA cable for the monitor(s)? Both. P.S: sorry for my bad english. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 14:45:57 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 May 2009 12:45:57 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.fead6b75aa9620d3fa6d19b1da8a83ce@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by anevilyak): Replying to [comment:10 HaikuBot]: > And one more thing: > {{{ > "~> ls /dev/graphics/ > 10de_0393_010000 vesa" > }}} > I think there must be "nv" instead of "vesa" if suppose driver works. No, "vesa" is always there. 10de_0393_010000 is the node published by the nvidia driver (10de is nvidia's PCI vendor ID, 0393 is your card ID). So it is indeed the nvidia driver being used here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 15:04:09 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 15 May 2009 13:04:09 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.3590ef22ef1fde0b10d12cc46d4ccb1c@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Replying to [comment:6 rudolfc]: > During this bootup, you did not disable the acceleration engine BTW. I too was surprised when looked log. But in "nvidia.settings" file, acceleration engine is disable (it comment- out). Replying to [comment:11 anevilyak]: > No, "vesa" is always there. 10de_0393_010000 is the node published by the nvidia driver (10de is nvidia's PCI vendor ID, 0393 is your card ID). So it is indeed the nvidia driver being used here. But why there no logs in home dir? (in nvidia.settings full-logging is turned on ) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 15:36:54 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 May 2009 13:36:54 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.4bc0e3c2239447ff25705d705bf2e550@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by anevilyak): Replying to [comment:12 HaikuBot]: > But why there no logs in home dir? (in nvidia.settings full-logging is turned on ) Where are you putting nvidia.settings? It should be in ~/config/settings/kernel/drivers/ -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 15:52:55 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 May 2009 13:52:55 -0000 Subject: [Haiku-bugs] [Haiku] #3931: IMAP doesn't inform the server when messages have been read Message-ID: <044.2ae0976d5858af71c22b352dc512eb8a@haiku-os.org> #3931: IMAP doesn't inform the server when messages have been read ---------------------------------+------------------------------------------ Reporter: anevilyak | Owner: bga Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------+------------------------------------------ If you download a new message via IMAP and then proceed to read it in BeMail or whatnot, it is correctly marked as read locally. However, it continues to register as new on the server since MDR appears to not tell the server that the message was read. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 20:28:32 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 15 May 2009 18:28:32 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.cb6f756a7cf587ebb3ea0570ebc52a8f@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, Thanks for the update. Another question please: Did you tweak the driver's sourcecode by any chance? I don't have an explanation why I see switchhead set to true in the new logfile while the corresponding activating logline is missing! This shouldn't happen... Other things I see: - the acceleration engine is apparantly working OK, as you did not disable it. - On this boot only the DVI cable was connected. Thanks. About the switchhead parameter: As I don't see the driver responding to this parameter, I'd say you can disable the parameter again. Would you test that for me please to be sure it indeed has no influence? Thanks. @ Stephan: Stephan, could we have a compiling problem here with variable sizes in shared info or something?? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 20:38:25 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 15 May 2009 18:38:25 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.cad4c95ec5c1da3c9be44675d0c1ba01@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): HaikuBot: Another strange thing: apparantly the driver does not export the acceleration hooks, or exports them without mentioning. Either case is impossible if the driver has been compiled correctly. So did you tweak the driver? I am very curious... If you did, please delete it and re-checkout the correct source, recompile, and redo the test... Otherwise I can't draw any valid conclusions I'm afraid. Thanks in advance for any info you might have! Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:01:12 2009 From: trac at haiku-os.org (tqh) Date: Fri, 15 May 2009 19:01:12 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.03fb59f6faa25e349a2cd156aef6cdd7@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Changes (by tqh): * cc: fredrik.holmqvist@? (added) Comment: That revision broke it for me as well with a kdl for ps2 service. I used auto_stack_trace but it didn't list anything except the header for stack traces. Either the computer hang, auto_stack_trace is broken or there is none. Reverting the files from r30726 at least proves that it is to blame. No ps2 here as well, just usb mouse and keyboard connected to a hub. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:23:07 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 15 May 2009 19:23:07 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.8f7faeb9aace5ba798571befa7559e88@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Stephan, Can you tell me if you disabled the use of the acceleration engine in the app_server? I now see the same thing in my own logs: acceleration engine hook messages aren't written. Please tell me what's going on: I am unable to further test the acceleration engine if you disabled the use of it. If you did: since when did you disable it, and when will you re-enable it again? Thanks for any info you might have.. Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:27:49 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 May 2009 19:27:49 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.c5d088cc07fff7d87145f6a2e1a8b1cb@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by anevilyak): Hi Rudolf, That was disabled in r30278, with accompanying explanation. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:38:54 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 15 May 2009 19:38:54 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build Message-ID: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> #3932: BFS corrupted during very large project build --------------------------+------------------------------------------------- Reporter: haiqu | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- I have a repeatable fault when at the linking stage of a very large project. The GNU linker `LD` reports that the filesystem has become R/O at the final linking stage and I have to run chkbfs on the drive from Dano to correct the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:44:28 2009 From: trac at haiku-os.org (anevilyak) Date: Fri, 15 May 2009 19:44:28 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build In-Reply-To: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> References: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> Message-ID: <049.e5167aa084d13607781761519a5b18f9@haiku-os.org> #3932: BFS corrupted during very large project build ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by anevilyak): * owner: marcusoverhagen => axeld * component: Drivers/Disk => File Systems/BFS -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 15 21:51:57 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 15 May 2009 19:51:57 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.032ab08820742b6e105613a658b01421@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Sorry, it was my fail, in previos log with "switchhead 1", I inadvertently left first line from old log (when deleting entries from old sessions). Here new one clean log. And not, i`m did not tweak driver`s source, my knowledges in writing drivers field negligible. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 00:25:18 2009 From: trac at haiku-os.org (haiqu) Date: Fri, 15 May 2009 22:25:18 -0000 Subject: [Haiku-bugs] [Haiku] #3808: Copying or creating large files causes General System Error In-Reply-To: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> References: <040.9bda2357c8c6b5edf0d0801bd351d2d8@haiku-os.org> Message-ID: <049.851d5078025600e0fa4e9b2e1d95d9c9@haiku-os.org> #3808: Copying or creating large files causes General System Error ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by haiqu): See also #3932 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 11:02:59 2009 From: trac at haiku-os.org (rudolfc) Date: Sat, 16 May 2009 09:02:59 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.438923ca853f066ff8e6bb25310ab6f2@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi again, @ anevilyak: Hmm, I was already beginning to suspect that. Back then I read the doublebuffereing was gone, but I did not think he'd actually disable accelerated drawing! I'm curious if that won't create scrolling and moving difficulties on AGP or even old-style PCI cards. I'll test that I think. If it works smoothly, then I'm impressed by the app_server software drawing code and/or whatever combination is responsible. My personal setup with not use this doublebuffering (that's dead slow if no acceleration is available for one thing). But I would without any doubt use hardware accelerated drawing! This is the reason it never came to me stephan disabled accelerated drawing along with the doublebuffering.. I'm still curious if we get accelerated drawing back or not BTW! @ Haikubot: Thanks for the new log and explanation. The log looks normal now we know accelerated drawing isn't performed by the app_server anymore, combined with your explanation. So, you can now use the driver without any tweak? Do I get that right? If so, the only remaining thing might be the acc engine if it were actually used by the app_server. Though I am under the impression that it only fails on G72, so not your G73. Please tell me if you still use tweaks? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 12:11:00 2009 From: trac at haiku-os.org (stippi) Date: Sat, 16 May 2009 10:11:00 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.15c26f9bc56bc6875518f2980615ead9@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): Hi Rudolf, there are several things which led me to disable the acceleration engine: * On my two computers which have native drivers, Haiku worked much smoother when acceleration was disabled. Haiku uses a lot more blending operations than BeOS did. So it needs to read the frame buffer a lot more. This is insanely slow. Using a frame shadow buffer in main memory and performing write operations on the frame buffer only is much faster. * I do not really want to go back to the 90ish style user interface look and use no gradients and thereby less B_OP_OVER for text rendering for example. * When dragging icons or dragging the selection rect in Tracker, it performs alpha blending. It flickers in BeOS when stuff redraws underneath, not in Haiku. * When repainting windows, Haiku uses double buffering, which means a whole lot less flickering in all sorts of situations, especially when repainting. * I cannot believe that when something feels slower on a fast computer, that it doesn't also feel slower on a slow computer. For the way in which the Haiku app_server currently works, using acceleration made it feel slower. It may be a problem of how it uses the acceleration, but I have no time or motivation to investigate. And blending will still feel slower. * I don't like the BeOS accelerant API. It is totally inflexible. Instead of performing commands with frame buffer coordinates, it should instead allow me to specify frame buffer (and offscreen!) memory addresses. * Eventually, the app_server should use 3D acceleration to do window compositing and use a lot less CPU, because there wouldn't be anymore redraws because of exposing previously covered up window regions. * This task is way too big for me to tackle right now. On all my computers, Haiku feels reasonably fast without any acceleration, including one pretty slowish computer. I see much more pressing needs in Haiku, like MediaKit encoding and the like. * If you want to figure out what I am doing wrong in the Haiku app_server which triggers weird lock ups of the NVidea driver when acceleration is used, please help analyze the app_server code. It is all pretty well written and should be easy to follow. There are only very few classes involved with repainting. It's DrawingEngine, HWInterface and AccelerantHWInterface. One needs to know that there is one DrawingEngine per Window, and one global AccelerantHWInterface instance. So there might be issues with locking when using acceleration. It does use locking, but it may use the wrong kind. I have no idea. I hope you have a better understanding now of why I think I did the right thing for the time being. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 12:20:57 2009 From: trac at haiku-os.org (rudolfc) Date: Sat, 16 May 2009 10:20:57 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.132ab756063b587a855086fdfda9a86a@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi Stephan Thanks for your response/clarification. I'll test Haiku on a PCI card to see what happens when moving windows around or scrolling. About these lockups: What gfx cards do you have there from nVidia? Do you have cardID's or at least Gxx number or something? A question: If I setup a function in the acc engine that fetches a chunck of main memory and copies it in the card memory, would that make you use acc again? (I am curious if I can speedup overlay this way for instance.. ;-) I guess you also want the other way around: a chunk of gfx mem back to main mem.. Would these two functions combined with the current acc functions be enough? Would you say the current functions can be deleted from the drivers? (Even without knowledge of the inner workings of the app_server: I can hardly believe that the current blit and fill function are useless...(!). I mean if I scroll down in a text you can use that right? And when I move a window: the same? If not, why not?) BTW Currently I am in the process of changing providers, so my mail is very uncertain atm. Once that's completed, we could take this subject to regular mail. Would that be better? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 14:25:57 2009 From: trac at haiku-os.org (HaikuBot) Date: Sat, 16 May 2009 12:25:57 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.8c0687ba76a5baba2deb5de9ca8926ea@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Replying to [comment:19 rudolfc]: > So, you can now use the driver without any tweak? Do I get that right? Yep, when connected via DVI only. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 14:35:52 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 12:35:52 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.0f3218f04f9dabda125b184f78045390@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by axeld): Stippi, about acceleration in general on older systems: unlike new systems, they have, in today's standards, an insanely limited memory bandwidth. So many things, most notably moving windows around, or scrolling, can still be done a lot faster using the hardware acceleration than you could do via software. This is where we might want to improve our acceleration usage (if possible) - this will definitely be faster on "slow" machines. The other stuff isn't so bad when ignored. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 18:33:06 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 16 May 2009 16:33:06 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.ded3407daee935e318317b3df1acc788@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by anevilyak): I can reproduce this also if I boot with my ps2 keyboard unplugged, backtrace as follows: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0x2c, ip 0x8007f9bc stack trace for thread 136 "ps2 service" kernel stack: 0x9157c000 to 0x91580000 frame caller :function + offset 0 9157fa34 (+ 48) 800659f1 :invoke_debugger_command + 0x00f5 1 9157fa64 (+ 64) 800657e1 invoke_pipe_segment(debugger_command_pipe*: 0x80136b20, int32: 0, 0x0 "") + 0x0079 2 9157faa4 (+ 64) 80065b68 :invoke_debugger_command_pipe + 0x009c 3 9157fae4 (+ 48) 80067118 ExpressionParser<0x9157fb98>::_ParseCommandPipe(0x9157fb94) + 0x0234 4 9157fb14 (+ 64) 80066552 ExpressionParser<0x9157fb98>::EvaluateCommand(0x80127200 "bt", 0x9157fb94) + 0x02ba 5 9157fb54 (+ 224) 80068540 :evaluate_debug_command + 0x0088 6 9157fc34 (+ 64) 8006386a kernel_debugger_loop() + 0x01ae 7 9157fc74 (+ 32) 80064771 :kernel_debugger + 0x004d 8 9157fc94 (+ 192) 80064719 :panic + 0x0029 9 9157fd54 (+ 80) 800ca551 :vm_page_fault + 0x0139 10 9157fda4 (+ 64) 800daf65 :page_fault_exception + 0x00d9 11 9157fde4 (+ 12) 800de696 :int_bottom + 0x0036 kernel iframe at 0x9157fdf0 (end = 0x9157fe40) eax 0x1 ebx 0x2c ecx 0x8012bd60 edx 0x0 esi 0x8132c3b8 edi 0x8119f398 ebp 0x9157fe58 esp 0x9157fe24 eip 0x8007f9bc eflags 0x10286 vector: 0xe, error code: 0x0 12 9157fdf0 (+ 104) 8007f9bc LegacyDevice<0x8132c3b8>::Removed(0x812de780, 0x9157fe98) + 0x004c 13 9157fe58 (+ 48) 80076f14 devfs_delete_vnode(devfs*: 0x8119f3c0, devfs_vnode*: 0x812de780, false) + 0x006c 14 9157fe88 (+ 48) 8007807c devfs_remove_vnode(fs_volume*: 0x8119f398, fs_vnode*: 0x81330d8c, true) + 0x005c 15 9157feb8 (+ 48) 8009fea8 free_vnode(vnode*: 0x81330d8c, true) + 0x00ac 16 9157fee8 (+ 48) 800a00a4 dec_vnode_ref_count(vnode*: 0x81330d8c, false, true) + 0x0140 17 9157ff18 (+ 48) 800a4105 :put_vnode + 0x0069 18 9157ff48 (+ 48) 80079986 :devfs_unpublish_device + 0x0086 19 9157ff78 (+ 48) 91576c23 :ps2_dev_unpublish + 0x002f 20 9157ffa8 (+ 48) 915794c0 :ps2_service_thread + 0x00d8 21 9157ffd8 (+ 32) 800592ab _create_kernel_thread_kentry() + 0x001b 22 9157fff8 (+1856503816) 80059248 thread_kthread_exit() + 0x0000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 18:41:15 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 16 May 2009 16:41:15 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.fdd229fff96e17c641579fa3e5ab11da@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by anevilyak): After some further tracing, I see why it's crashing, but not what leads to this condition: fRemovedFromParent is false, but fDriver is NULL. Thus fDriver->devices.Remove(this); causes the above mentioned panic, since this condition isn't checked. Should it be possible for this to occur at all, or is something more drastic wrong if fDriver is NULL at that point? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 18:50:52 2009 From: trac at haiku-os.org (anevilyak) Date: Sat, 16 May 2009 16:50:52 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.da5973c30effab53d8401999439d33b6@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by anevilyak): Boots and seems to correctly handle device replugging/unplugging properly for me with the following diff: {{{ Index: src/system/kernel/device_manager/legacy_drivers.cpp =================================================================== --- src/system/kernel/device_manager/legacy_drivers.cpp (revision 30769) +++ src/system/kernel/device_manager/legacy_drivers.cpp (working copy) @@ -1184,7 +1184,7 @@ { RecursiveLocker _(sLock); - if (!fRemovedFromParent) + if (!fRemovedFromParent && fDriver != NULL) fDriver->devices.Remove(this); delete this; }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 19:40:03 2009 From: trac at haiku-os.org (Hubert) Date: Sat, 16 May 2009 17:40:03 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.90a2cc4e980d2f037302e44bc19aa0ba@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): Found guilty: rev. 30000 and higer. Propably when Axel sockety changed to inherit from WeakRef then started to burst dhcp / network. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 20:01:06 2009 From: trac at haiku-os.org (zooey) Date: Sat, 16 May 2009 18:01:06 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.f4815938f00c79d262a8821dbb620923@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by zooey): As mentioned earlier by Stephan, we already new that r30000 is broken. That particular bug has been fixed in r30175. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 20:28:13 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 18:28:13 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.4d686827777664de7081ac11692169de@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice -----------------------------+---------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------------+---------------------------------------------- Comment(by axeld): Thanks Rene! I wanted to investigate this today, but didn't find the time. I'll have a look if fDriver is allowed to be NULL at that point; it sounds a bit odd indeed, at least. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 20:46:11 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 18:46:11 -0000 Subject: [Haiku-bugs] [Haiku] #3933: ATA locks up on the EeePC Message-ID: <040.02b998b4b756de7d89239b64fdce83ad@haiku-os.org> #3933: ATA locks up on the EeePC --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- When trying to boot using the new ATA stack (but from USB), the system locks up. I've investigated the issue a bit, but didn't get far before my only USB stick (128 MB!) died (obviously doesn't like being completely rewritten that often). Anyway, when I added some debug output in on-screen-debug-output-mode, I noticed the system could sometimes boot. In fact, adding a spin(10000) at various locations in ATAChannel::Reset() (within the for loop) solved the issue. I'll buy a new stick on Monday, and see if I can find out more. In the mean time, maybe someone knowing the specs has an idea :-) In any case, the system seems to work fine when booting with IDE DMA off, but maybe that was just luck. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 21:01:50 2009 From: trac at haiku-os.org (rudolfc) Date: Sat, 16 May 2009 19:01:50 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.5bf9dc074506269bd4e0f3520215a8e1@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi guys, Haikubot, And what if you connect your monitor _only_ with the VGA cable (so disconnect the DVI cable): would it work without a tweak then as well? Hi Axel,Stephan, Do we have a small (command line) tool to measure the RAM read/write access bandwidth for graphicscards? I remember a tool that did 8/16/32 bit transfers to measure the speed if I am correct. (Write combining had different optimation results for different size accesses) I also remember that on AGP this is very limited (for the CPU accessing gfx ram): writing was faster than reading due to the fastwrites feature AGP supports. In effect, reading went at PCI bus speed (133Mb/sec). Writing was in practice around 4 times faster with FW support I think? I also remember that on my first PCIe cards using this tool the write speed was lower, and the read speed was still around 133Mb/sec (I think I tested both a GF6600 and a 4300 or so: the latter was an AGP card with PCIe bridge onboard). Probably some settings weren't enabled by default ('legacy PCIe mode') and reading could be slow because the GPU's weren't designed to give you access to their RAM fast. They were designed to do these things fast if done by the GPU - not the CPU. I would like to test with my current system to get an estimate on this. In other words: are the current systems indeed much faster accessible on Haiku or is it still a slow connection? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 22:01:51 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 20:01:51 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.53fc89495fdec204f5a22c1562fe3826@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Legacy drivers can be published without an actual driver, with the hooks only - so it's indeed perfectly okay that fDriver is NULL. I've applied your patch, thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 22:02:19 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 20:02:19 -0000 Subject: [Haiku-bugs] [Haiku] #3856: page fault in LegacyDevice::UninitDevice In-Reply-To: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> References: <050.b0e25ea6d250ba03347ee4382aa50cb0@haiku-os.org> Message-ID: <059.ce585a771c55f41b1dbf9d1a454c8c09@haiku-os.org> #3856: page fault in LegacyDevice::UninitDevice ------------------------------+--------------------------------------------- Reporter: marcusoverhagen | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------------+--------------------------------------------- Comment(by axeld): In r30770, btw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 22:46:01 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 16 May 2009 20:46:01 -0000 Subject: [Haiku-bugs] [Haiku] #3934: Unable to unmount a filesystem after two mounts on the same mount point Message-ID: <041.ac9502b2605409b2b18d668355e480ca@haiku-os.org> #3934: Unable to unmount a filesystem after two mounts on the same mount point ---------------------------+------------------------------------------------ Reporter: VinDuv | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Haiku does not allows mounting two filesystems on the same directory : the second mount fails with "Device/File/Resource busy". But after this, unmounting the filesystem also fails with the same error. {{{ > mount -t fat mydisk1.img /fat > unmount /fat > mount -t fat mydisk1.img /fat > mount -t fat mydisk2.img /fat mount: Device/File/Resource busy > unmount /fat unmount: unmounting failed: Device/File/Resource busy }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:09:46 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 21:09:46 -0000 Subject: [Haiku-bugs] [Haiku] #3928: volume control as replicant blocks windows from having focus In-Reply-To: <042.93215fe06f2f359792bd761ed3a46cba@haiku-os.org> References: <042.93215fe06f2f359792bd761ed3a46cba@haiku-os.org> Message-ID: <051.c0c2c95e3cfeaef2c8ffb5db6fe12d3b@haiku-os.org> #3928: volume control as replicant blocks windows from having focus ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => fixed Comment: Fixed in r30772. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:09:55 2009 From: trac at haiku-os.org (schmedly) Date: Sat, 16 May 2009 21:09:55 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.dafb2cffae7a1d803ae03d08d6b2a33d@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by schmedly): Okay it's more than 2 days of uptime, and the problem isn't exactly what I thought. Sometimes when switching back to Haiku, if the screensaver is active the screen will stay blank. However, if I switch away and switch back again, the display comes up. This behavior does not occur when the screensaver is not enabled. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:17:38 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 21:17:38 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build In-Reply-To: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> References: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> Message-ID: <049.6a3822f2c53ed632df281c3c1002de8c@haiku-os.org> #3932: BFS corrupted during very large project build ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by axeld): Can you provide at least a bit more info? Like what project it is, and maybe a link to it in case it's freely available. A reproducible file system bug would really be nice! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:22:43 2009 From: trac at haiku-os.org (fano) Date: Sat, 16 May 2009 21:22:43 -0000 Subject: [Haiku-bugs] [Haiku] #3935: NVIDIA GeForce 6150 Integrated GPU support Message-ID: <039.f74cf177fefb4216e7e3405f65e76a3d@haiku-os.org> #3935: NVIDIA GeForce 6150 Integrated GPU support -------------------------------------+-------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- I've created a usb bootable key and after the boot process I obtain a black screen the only way to see the Haiku desktop is to choose "Failsafe video mode" (VESA) from the boot menu. My NVIDIA 6150 is integrated in a ASUS M2NPV-VM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:27:05 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 21:27:05 -0000 Subject: [Haiku-bugs] [Haiku] #3934: Unable to unmount a filesystem after two mounts on the same mount point In-Reply-To: <041.ac9502b2605409b2b18d668355e480ca@haiku-os.org> References: <041.ac9502b2605409b2b18d668355e480ca@haiku-os.org> Message-ID: <050.f6b46c0de11c696c2f1307a2eff4ce3b@haiku-os.org> #3934: Unable to unmount a filesystem after two mounts on the same mount point ---------------------------+------------------------------------------------ Reporter: VinDuv | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:28:08 2009 From: trac at haiku-os.org (fano) Date: Sat, 16 May 2009 21:28:08 -0000 Subject: [Haiku-bugs] [Haiku] #3936: Microsoft Wireless Optical mouse 2000 Message-ID: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> #3936: Microsoft Wireless Optical mouse 2000 -------------------------------+-------------------------------------------- Reporter: fano | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- This wireless mouse is sold in kit with a wireless keyboard... and use the same base linked via USB to communicate with the PC... the strange thing is that the keyboard works and the mouse not! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:28:37 2009 From: trac at haiku-os.org (fano) Date: Sat, 16 May 2009 21:28:37 -0000 Subject: [Haiku-bugs] [Haiku] #3936: Microsoft Wireless Optical mouse 2000 doesn't work (was: Microsoft Wireless Optical mouse 2000) In-Reply-To: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> References: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> Message-ID: <048.b6b5d6e368d8c9395a22c558c3b44597@haiku-os.org> #3936: Microsoft Wireless Optical mouse 2000 doesn't work -------------------------------+-------------------------------------------- Reporter: fano | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:29:45 2009 From: trac at haiku-os.org (axeld) Date: Sat, 16 May 2009 21:29:45 -0000 Subject: [Haiku-bugs] [Haiku] #3934: Unable to unmount a filesystem after two mounts on the same mount point In-Reply-To: <041.ac9502b2605409b2b18d668355e480ca@haiku-os.org> References: <041.ac9502b2605409b2b18d668355e480ca@haiku-os.org> Message-ID: <050.e7494ef0a8e4686aeb5f2bd53008f526@haiku-os.org> #3934: Unable to unmount a filesystem after two mounts on the same mount point ----------------------------+----------------------------------------------- Reporter: VinDuv | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ----------------------------+----------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30773. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 16 23:42:28 2009 From: trac at haiku-os.org (bga) Date: Sat, 16 May 2009 21:42:28 -0000 Subject: [Haiku-bugs] [Haiku] #3921: Problem mounting audio CD. In-Reply-To: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> References: <038.8a80311c3775123ba4d53763426abb77@haiku-os.org> Message-ID: <047.55ae972c8018563a209ad058d89bdc11@haiku-os.org> #3921: Problem mounting audio CD. ---------------------------+------------------------------------------------ Reporter: bga | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Disk | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bga): * status: new => closed * resolution: => fixed Comment: It was really a disk device manager problem. Fixed in r30774. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 04:51:05 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 02:51:05 -0000 Subject: [Haiku-bugs] [Haiku] #3547: cc fails when compiling bfs_disk_system.cpp In-Reply-To: <045.6326640b4403f81a09029368d72329d2@haiku-os.org> References: <045.6326640b4403f81a09029368d72329d2@haiku-os.org> Message-ID: <054.5c57cc613ba4638a60257763ee26974b@haiku-os.org> #3547: cc fails when compiling bfs_disk_system.cpp --------------------------+------------------------------------------------- Reporter: Phoenix137 | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x64 Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): This should be resolved with changeset:30779 , which removed the incomplete 64bit host detection. "gcc-multilib" and "g++-multilib" need to be installed and then `linux32 configure --use-32bit ` should work as expected. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 10:54:13 2009 From: trac at haiku-os.org (Hubert) Date: Sun, 17 May 2009 08:54:13 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.bf62b32402199586494fb11546e1426b@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): This didn't repair my problem. I have the same in r30680, r30704 and r30775. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 11:54:45 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 09:54:45 -0000 Subject: [Haiku-bugs] [Haiku] #3935: NVIDIA GeForce 6150 Integrated GPU support In-Reply-To: <039.f74cf177fefb4216e7e3405f65e76a3d@haiku-os.org> References: <039.f74cf177fefb4216e7e3405f65e76a3d@haiku-os.org> Message-ID: <048.2d138253426f2545d572e5a2f1210239@haiku-os.org> #3935: NVIDIA GeForce 6150 Integrated GPU support --------------------------------------+------------------------------------- Reporter: fano | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => duplicate Comment: duplicate of #1026 Thanks for noticing, Richie Nyhus ! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 11:56:34 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 09:56:34 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.6144d6c11d7147b8027cdb3cba119008@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by mmadia): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 11:57:03 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 09:57:03 -0000 Subject: [Haiku-bugs] [Haiku] #1557: Frequency out of range In-Reply-To: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> References: <044.15236cb511ee12c72ec612ed24aea2ba@haiku-os.org> Message-ID: <053.5a14e240065699e28a4246168b7c0577@haiku-os.org> #1557: Frequency out of range -------------------------------------+-------------------------------------- Reporter: plfiorini | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by mmadia): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 11:57:23 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 09:57:23 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.b8283d03ced469ffff74f1e09683eb7e@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by mmadia): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 12:02:34 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 10:02:34 -0000 Subject: [Haiku-bugs] [Haiku] #1023: Monitor switches off on app_server start up In-Reply-To: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> References: <038.b7d9719427420a975add0da34af3d849@haiku-os.org> Message-ID: <047.fb6b9e37a1986eed27f118ba558f1b41@haiku-os.org> #1023: Monitor switches off on app_server start up -------------------------------------+-------------------------------------- Reporter: k2s | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Changes (by mmadia): * owner: axeld => rudolfc -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 12:35:21 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 17 May 2009 10:35:21 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build In-Reply-To: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> References: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> Message-ID: <049.46b15123fe610011353de1d6d687c30d@haiku-os.org> #3932: BFS corrupted during very large project build ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by haiqu): Tried to add data to this report yesterday but the ticket was locked somehow, sorry. The project was in Pascal so the tools aren't readily available for you to test a build. What I *can* add is that the crash hit EXACTLY as the file size passed a size of 64Mb, which is starting to look like a boundary condition problem. I might also add that my earlier report #3808 about problems creating and copying files and/or writing to CD-ROM occurs at around 32Mb. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 12:42:59 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 17 May 2009 10:42:59 -0000 Subject: [Haiku-bugs] [Haiku] #3932: BFS corrupted during very large project build In-Reply-To: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> References: <040.2a461ce783aeb3db853260b52cdefadd@haiku-os.org> Message-ID: <049.1ac7c8c9a9c090f6173f5043888e0025@haiku-os.org> #3932: BFS corrupted during very large project build ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by haiqu): While I'm here, I should add that `chkbfs` run from Dano reported that there were NULL inodes and it took a bit of work to fix the drive. I had to delete large chunks of my work and run `chkbfs` three times to be sure it was all good again. I was ready to init the partition and start again at one point. Re-running the compilation on a faster machine caused NO p[roblems, and the eventual executable file size was a whopping 84Mb, is that a record? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 14:48:40 2009 From: trac at haiku-os.org (bga) Date: Sun, 17 May 2009 12:48:40 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.65184a4349fb47e400bcb2948dc6f414@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by bga): Hubert, did you d a *FULL* clean install to check? You mentioned erasing directories and recreating them again. This is not the best way to go for checking this. Also, did you try in recent version to see if you could configure a static IP? Based on your comments early in this ticket it seems DHCO is not the problem at all. The problem is simply that your network stack is not working (so, DHCP would not work either). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 16:15:51 2009 From: trac at haiku-os.org (bga) Date: Sun, 17 May 2009 14:15:51 -0000 Subject: [Haiku-bugs] [Haiku] #3446: AudioCD doesn't autoname the audio tracks like BeOS does In-Reply-To: <042.539d8e92e1c986b6356f6f1481fdcf12@haiku-os.org> References: <042.539d8e92e1c986b6356f6f1481fdcf12@haiku-os.org> Message-ID: <051.3b8c13a3477e5df0a1939be9e8bf0543@haiku-os.org> #3446: AudioCD doesn't autoname the audio tracks like BeOS does --------------------------------+------------------------------------------- Reporter: scottmc | Owner: bga Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: File Systems/cdda | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: CDDB Daemon has been implemented and is now auto started during boot (r30781). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 16:17:00 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 17 May 2009 14:17:00 -0000 Subject: [Haiku-bugs] [Haiku] #3937: userguide/en/installation.html displays as code and not as end-product Message-ID: <041.319b08ce3a884040ebb37c84d9e77301@haiku-os.org> #3937: userguide/en/installation.html displays as code and not as end-product -----------------------+---------------------------------------------------- Reporter: mmadia | Owner: humdinger Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- After the recent mixup of removing userguide documents, userguide/en/installation.html displays as a text document and not as html anymore. [http://svn.berlios.de/svnroot/repos/haiku/haiku/trunk/docs/userguide/en/installation.html] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 16:23:45 2009 From: trac at haiku-os.org (bga) Date: Sun, 17 May 2009 14:23:45 -0000 Subject: [Haiku-bugs] [Haiku] #3833: IMAP background thread does not appear to work correctly In-Reply-To: <044.9d56a674ebe30fac08b29197735434a6@haiku-os.org> References: <044.9d56a674ebe30fac08b29197735434a6@haiku-os.org> Message-ID: <053.e72b2241b5fd30cb2a3504f18ed42d96@haiku-os.org> #3833: IMAP background thread does not appear to work correctly ----------------------------------+----------------------------------------- Reporter: anevilyak | Owner: bga Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Servers/mail_server | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by bga): * status: new => closed * resolution: => fixed Comment: This has been reported as fixed by Rene. Closing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 16:49:46 2009 From: trac at haiku-os.org (Hubert) Date: Sun, 17 May 2009 14:49:46 -0000 Subject: [Haiku-bugs] [Haiku] #3922: I can't connect with DHCP from ~r.30012 In-Reply-To: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> References: <041.6b813697b3c65f2e2973c642525de3b4@haiku-os.org> Message-ID: <050.f81c95f9885fac628a6b5948d0a48a72@haiku-os.org> #3922: I can't connect with DHCP from ~r.30012 --------------------------------------+------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by Hubert): Now, I clear install r30780 with dd on USB stick. I will upload syslog. Configure with static IP doesn't give effect. The problem appear from r30000 and fixed with r30175 didn't help. Network not work. I have r29996 on HDD and his network work correctly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 17:18:41 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 17 May 2009 15:18:41 -0000 Subject: [Haiku-bugs] [Haiku] #2481: USB mouse and keyboard sometimes stop working In-Reply-To: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> References: <041.e27b67ec0dca7fb5b40f990c6c5599c8@haiku-os.org> Message-ID: <050.d1b126879f35d64c4aa29760c6b977f5@haiku-os.org> #2481: USB mouse and keyboard sometimes stop working --------------------------+------------------------------------------------- Reporter: stippi | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by mmlr): * status: reopened => closed * resolution: => fixed Comment: So I take this as a "fixed". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 17:19:44 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 17 May 2009 15:19:44 -0000 Subject: [Haiku-bugs] [Haiku] #3936: Microsoft Wireless Optical mouse 2000 doesn't work In-Reply-To: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> References: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> Message-ID: <048.094d51690b1b92cfafe45dc62bf342cb@haiku-os.org> #3936: Microsoft Wireless Optical mouse 2000 doesn't work -------------------------------+-------------------------------------------- Reporter: fano | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by mmlr): Can you please run "listusb -v" in the Terminal and attach the output here? I suspect that the mouse simply isn't a boot protocol mouse. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 17:44:45 2009 From: trac at haiku-os.org (fano) Date: Sun, 17 May 2009 15:44:45 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.b719d5ffb88a31e8860587717bd7ff26@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by fano): Sorry to have opened a another copy of this! I've done a search but not found this... However I've the DVI connected to a HDTV display and the VGA connected to a monitor. During the Haiku boot the image in is in all the screens in "clone" mode... when Haiku boot finish the monitor goes black and turns off while the HDTV is black saying "frequency not supported". So the problem is present in all the output DVI or VGA! If I use VESA mode the desktop is showed in all screens but at only 800*600 the quality is ugly as you can imagine... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 18:07:47 2009 From: trac at haiku-os.org (axeld) Date: Sun, 17 May 2009 16:07:47 -0000 Subject: [Haiku-bugs] [Haiku] #3919: BListView does not Invoke when double cliking In-Reply-To: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> References: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> Message-ID: <050.084b6f68cef5a44225c31fa8b615992c@haiku-os.org> #3919: BListView does not Invoke when double cliking --------------------------------+------------------------------------------- Reporter: romain | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Old description: > seen in rev30699 > > Double clicking on an item of a BListView does not trigger invocation. > This probably appeared with changes in rev30149, but the problem comes > from the reset of fTrack->item_index in MouseUp. Releasing the mouse does > not mean that the selected item is no more active. Also we do not need > this to handle dragndrop status since try_drag is used for that. > The attached patch should fix this > > I reproduce this very easily on a vmware install in the printer > preference app: double click on one printer does not make it the default > one. New description: seen in r30699 Double clicking on an item of a BListView does not trigger invocation. This probably appeared with changes in r30149, but the problem comes from the reset of fTrack->item_index in MouseUp. Releasing the mouse does not mean that the selected item is no more active. Also we do not need this to handle dragndrop status since try_drag is used for that. The attached patch should fix this I reproduce this very easily on a vmware install in the printer preference app: double click on one printer does not make it the default one. -- Comment(by axeld): A small tip: if you write "rev30699" as r30699, Trac is smart enough to create a link to the actual changes (I've already changed your description, in case you wonder). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 18:14:39 2009 From: trac at haiku-os.org (axeld) Date: Sun, 17 May 2009 16:14:39 -0000 Subject: [Haiku-bugs] [Haiku] #3919: BListView does not Invoke when double cliking In-Reply-To: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> References: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> Message-ID: <050.ed303cb5a075330d348c807b5751cb9a@haiku-os.org> #3919: BListView does not Invoke when double cliking --------------------------------+------------------------------------------- Reporter: romain | Owner: axeld Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by axeld): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 18:50:23 2009 From: trac at haiku-os.org (axeld) Date: Sun, 17 May 2009 16:50:23 -0000 Subject: [Haiku-bugs] [Haiku] #3919: BListView does not Invoke when double cliking In-Reply-To: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> References: <041.65edc16d07fd4ba5636ba02ddb8f789a@haiku-os.org> Message-ID: <050.daeb4c07b2e3c22018d4769729d59796@haiku-os.org> #3919: BListView does not Invoke when double cliking ---------------------------------+------------------------------------------ Reporter: romain | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Thanks for your patch! The problem is fixed in r30782. Technically, only the part in MouseUp() would have been needed to fix the problem, but the check you removed in MouseMoved() was actually done twice (again in _TryInitiateDrag() which I removed), but you probably noticed that yourself. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 19:26:40 2009 From: trac at haiku-os.org (Hubert) Date: Sun, 17 May 2009 17:26:40 -0000 Subject: [Haiku-bugs] [Haiku] #3530: nForce (MCP61 Ethernet) not work correctly In-Reply-To: <041.a5f379237c17937911a9a26f8fc8f251@haiku-os.org> References: <041.a5f379237c17937911a9a26f8fc8f251@haiku-os.org> Message-ID: <050.969fa3b2b1f69e834fb8b7775d378453@haiku-os.org> #3530: nForce (MCP61 Ethernet) not work correctly ------------------------------------+--------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by Hubert): I tested in r30780 and nforce work now. Please closed ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 21:58:08 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 19:58:08 -0000 Subject: [Haiku-bugs] [Haiku] #1530: Nvidia GeForce FX 6600 doesn't work In-Reply-To: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> References: <050.4cc60a9924bb833736e176bdc0211f65@haiku-os.org> Message-ID: <059.e9c60bf70db1ab2cd5ef7749a0d241ab@haiku-os.org> #1530: Nvidia GeForce FX 6600 doesn't work -------------------------------------+-------------------------------------- Reporter: marcusoverhagen | Owner: rudolfc Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by rudolfc): * status: new => assigned Comment: I re-enabled this card. It's working OK over here. If I don't hear otherwise, I'll close this ticket sometime. Thanks :) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:00:41 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:00: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.91fd7f0d49a12b9789ee323f4a1b7bce@haiku-os.org> #1950: Garbled screen contents with true colour mode on nvidia gf2mx ------------------------+--------------------------------------------------- Reporter: jopadan | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Closing as the card works these days. (MTRR fixed somehow.) Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:06:34 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:06:34 -0000 Subject: [Haiku-bugs] [Haiku] #2465: nvidia driver does not work with GeForce 7600GT In-Reply-To: <038.0de46c7c697ad8843caf1de95d1ecb34@haiku-os.org> References: <038.0de46c7c697ad8843caf1de95d1ecb34@haiku-os.org> Message-ID: <047.f71bfcc99c96cfead7533dd165f71885@haiku-os.org> #2465: nvidia driver does not work with GeForce 7600GT -------------------------------------+-------------------------------------- Reporter: n3s | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, It's a bit later I know.. Anyhow: looks like the force_ws option is a troublemaker on non-ws screens. Maybe you're suffering from that concerning the timing. About CRTC not working on G72 (7300LE card tested now): it's simply nolonger implemented on the DVI connector! This card has one DVI-D and one VGA connection options. Although a DVI-A connector sits on it... I'll add this ID after fixing EDID/ddc handling so ws screens are better detected. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:08:26 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:08:26 -0000 Subject: [Haiku-bugs] [Haiku] #2545: [kernel] GeForce MX420 lots of stability issues In-Reply-To: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> References: <040.4e30d608cc4ca7654053cf6c2360b9a9@haiku-os.org> Message-ID: <049.46419b54fcae8116429cb789a03e56e8@haiku-os.org> #2545: [kernel] GeForce MX420 lots of stability issues -------------------------------------+-------------------------------------- Reporter: diver | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there, I doubt this is an nvidia driver issue.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:16:17 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:16:17 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.60ee5df93f20ce811d87eacba2c18339@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there, If the screens you use are 4:3 types, try setting the resolution of Haiku to the native one of your screen in failsafe video mode. Then reboot with the driver active. Problem solved? (would be nice ;-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:40:09 2009 From: trac at haiku-os.org (Disreali) Date: Sun, 17 May 2009 20:40:09 -0000 Subject: [Haiku-bugs] [Haiku] #3710: Tracker crashes with BColumnTitle::Draw In-Reply-To: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> References: <047.45ec7c67a6168c00a026aea0bbd3cb8f@haiku-os.org> Message-ID: <056.cbd3cc9c655ace5f7bd1d99e533e612d@haiku-os.org> #3710: Tracker crashes with BColumnTitle::Draw ----------------------------------+----------------------------------------- Reporter: PieterPanman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by Disreali): Also experiencing this issue. Not able to reproduce consistently. bt attached -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:41:07 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:41:07 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.bf64b200caf35bbacd61265c2c5074db@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Info update: Since R30783 acceleration with the nvidia driver using G72 cards (Geforce 7300, 7400 and 7500) is fixed. Testable with old Haiku versions: pre- R30278. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:44:30 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:44:30 -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.a0d241d4d04703357c2e8e246f4b6c57@haiku-os.org> #927: [nvidia] stability problems with GeForce 7300 --------------------------------------+------------------------------------- Reporter: diver | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Hi, The acceleration engine wasn't properly powered up up for G72 cards (Geforce 7300, 7400 and 7500) at least. Fixed since R30783, so closing ticket. Testable only with pre-R30278 builds, since app_server unfortunately nolonger uses acceleration since then.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:45:38 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:45:38 -0000 Subject: [Haiku-bugs] [Haiku] #1535: Lock up on system while using regular NVIDIA driver. In-Reply-To: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> References: <044.4082ffe10b795944b4e385a40a5610ea@haiku-os.org> Message-ID: <053.3e0bdd2167ff6fe1069adb487a503a5a@haiku-os.org> #1535: Lock up on system while using regular NVIDIA driver. --------------------------------------+------------------------------------- Reporter: etteyafed | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Hi, The acceleration engine wasn't properly powered up up for G72 cards (Geforce 7300, 7400 and 7500) at least. Fixed since R30783, so closing ticket. Testable only with pre-R30278 builds, since app_server unfortunately nolonger uses acceleration since then.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 22:46:39 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 17 May 2009 20:46:39 -0000 Subject: [Haiku-bugs] [Haiku] #3482: nVidia evga PCI-E 7200GS (256MB) distorted video/hang on boot In-Reply-To: <044.277e8e8a7c2b11753acef5134e36d6b7@haiku-os.org> References: <044.277e8e8a7c2b11753acef5134e36d6b7@haiku-os.org> Message-ID: <053.fd40b6d0dc3fce67e87c7ce6cbc8bf2a@haiku-os.org> #3482: nVidia evga PCI-E 7200GS (256MB) distorted video/hang on boot --------------------------------------+------------------------------------- Reporter: masopmac1 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Hi, The acceleration engine wasn't properly powered up up for G72 cards (Geforce 7300, 7400 and 7500) at least. Fixed since R30783, so closing ticket. Testable only with pre-R30278 builds, since app_server unfortunately nolonger uses acceleration since then.. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 23:21:12 2009 From: trac at haiku-os.org (axeld) Date: Sun, 17 May 2009 21:21:12 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.84d23beda2344c17e3a2093f60b9e5eb@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: bonefish Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by axeld): The registrar only checks whether or not the application is waiting on a modal panel. Maybe there is something wrong with how it detects this, or StyledEdit/Mail actually aren't using a modal panel for this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 17 23:25:50 2009 From: trac at haiku-os.org (axeld) Date: Sun, 17 May 2009 21:25:50 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.6d833b8e147412e77b07faeac7b42174@haiku-os.org> #3862: Shutdown doesn't wait for user input -------------------------------+-------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by axeld): * owner: bonefish => axeld * status: new => assigned Comment: Hm, interesting: actually BPrivate::is_app_showing_modal_window() is currently not implemented, and always returns true. IOW the registrar should currently never quit an app without questioning - looks like there is an actual bug hidden. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 00:44:52 2009 From: trac at haiku-os.org (stippi) Date: Sun, 17 May 2009 22:44:52 -0000 Subject: [Haiku-bugs] [Haiku] #347: Imposible to boot from CD In-Reply-To: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> References: <054.b7543cd2da05e105ad49b5d2c2877e4d@haiku-os.org> Message-ID: <063.2c83f3eb8ae9f94196f0dca179853e07@haiku-os.org> #347: Imposible to boot from CD ----------------------------------+----------------------------------------- Reporter: daneel@? | Owner: axeld Type: bug | Status: reopened Priority: high | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by stippi): * milestone: R1/alpha1 => R1 Comment: No feedback, I am moving it out of the milestone anyways, since Haiku definitely boots on at least all my computers from CD. So this should not be a blocker. See my comment above. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 02:20:38 2009 From: trac at haiku-os.org (stippi) Date: Mon, 18 May 2009 00:20:38 -0000 Subject: [Haiku-bugs] [Haiku] #3719: Terminal: visual glitch in color preferences In-Reply-To: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> References: <040.32ccd751677bb9a63c3d4d27f24ae39d@haiku-os.org> Message-ID: <049.ac8ae84b830c70760f5f3381515142da@haiku-os.org> #3719: Terminal: visual glitch in color preferences ---------------------------------+------------------------------------------ Reporter: rossi | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Fixed in r30784. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 06:23:30 2009 From: trac at haiku-os.org (dlmcpaul) Date: Mon, 18 May 2009 04:23:30 -0000 Subject: [Haiku-bugs] [Haiku] #2665: Donating codes: APE reader In-Reply-To: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> References: <041.e0e43b22fa9aa8c855e1bb1de35ece8c@haiku-os.org> Message-ID: <050.57d9eefc34d61b3a1828e94eeff312a7@haiku-os.org> #2665: Donating codes: APE reader -----------------------------------+---------------------------------------- Reporter: shinta | Owner: dlmcpaul Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by dlmcpaul): * status: reopened => closed * resolution: => fixed Comment: Should be all ok now -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 07:04:57 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 18 May 2009 05:04:57 -0000 Subject: [Haiku-bugs] [Haiku] #3217: MCP78S [GeForce 8200] Ethernet networking very slow with 2 CPUs enabled In-Reply-To: <042.ba9004ec552d7542855524cb7aac57f5@haiku-os.org> References: <042.ba9004ec552d7542855524cb7aac57f5@haiku-os.org> Message-ID: <051.54c363f293e67bc19f58c9a669abbd0c@haiku-os.org> #3217: MCP78S [GeForce 8200] Ethernet networking very slow with 2 CPUs enabled -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): Not sure when this got fixed but with r30679 I'm seeing normal download speeds even with both cores on my AMDX2 enabled. So this ticket can be closed. Not sure about the other two tickets though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 07:12:19 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 18 May 2009 05:12:19 -0000 Subject: [Haiku-bugs] [Haiku] #3217: MCP78S [GeForce 8200] Ethernet networking very slow with 2 CPUs enabled In-Reply-To: <042.ba9004ec552d7542855524cb7aac57f5@haiku-os.org> References: <042.ba9004ec552d7542855524cb7aac57f5@haiku-os.org> Message-ID: <051.b8d0d1951d8bf482e6e16ca58f4dc243@haiku-os.org> #3217: MCP78S [GeForce 8200] Ethernet networking very slow with 2 CPUs enabled ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: closing --> fixed. see previous comments. Thanks for the follow-up, scott! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 08:01:57 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 18 May 2009 06:01:57 -0000 Subject: [Haiku-bugs] [Haiku] #3938: SegFault at unmount of USB-Stick Message-ID: <042.898092470d7406deb5168041f7350951@haiku-os.org> #3938: SegFault at unmount of USB-Stick ---------------------------+------------------------------------------------ Reporter: jahaiku | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ If I unmount a mounted USB-Stick in Tracker over the right mouse menu I get the attached SegFault. This is version from Friday from haiku-files. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 08:49:18 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 18 May 2009 06:49:18 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.31a4a1dba5f97a8d25abb5aad7af2263@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by mmlr): I can reproduce this with kqemu. I've re-ported the current qemu version (0.10.4, using native APIs) and the corresponding kqemu. QEMU and kqemu work fine as long as they are running, but as soon as I close QEMU this panic happens. This package is hacked up a bit (QEMU requiring a more current GCC I compiled everything of QEMU with GCC4 but then used GCC2 for the native stuff, since QEMU is pure C however this does work). It's of course also possible that my kqemu driver is bogus, but I don't exactly understand how a driver would provoke this panic. The driver does use create/delete_area, lock/unlock_memory and get_memory_map. Could a lock_memory without a matching unlock_memory trigger this? You can get the package at http://haiku.mlotz.ch/qemu-0.10.4-haiku.zip for testing. You can view the driver source at http://haiku.mlotz.ch/kqemu-haiku.c . It is based on the previous BeOS version and doesn't make use of any Haiku specifics except for user_memcpy(). Just tell me if you want me to test anything in that regard. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 09:01:14 2009 From: trac at haiku-os.org (jahaiku) Date: Mon, 18 May 2009 07:01:14 -0000 Subject: [Haiku-bugs] [Haiku] #3939: IBM z60m backlight not enabled Message-ID: <042.09007f86455d525cd1344ef646f5f800@haiku-os.org> #3939: IBM z60m backlight not enabled -------------------------------------+-------------------------------------- Reporter: jahaiku | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- If I boot haiku on my z60m with a mobile radeon x600 the backlight is not enabled. The backlight will get disabled after the bootup icons have finished and the normal desktop is shown. The shown resolution and picture is OK. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 10:04:46 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 18 May 2009 08:04:46 -0000 Subject: [Haiku-bugs] [Haiku] #3939: IBM z60m backlight not enabled In-Reply-To: <042.09007f86455d525cd1344ef646f5f800@haiku-os.org> References: <042.09007f86455d525cd1344ef646f5f800@haiku-os.org> Message-ID: <051.46b6b218c1463b085ed84d317de2d9a7@haiku-os.org> #3939: IBM z60m backlight not enabled -------------------------------------+-------------------------------------- Reporter: jahaiku | Owner: euan Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/radeon | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by scottmc): Here's a similar report on a linux mailing list that might help in debugging this: http://osdir.com/ml/linux.acpi.ibm-acpi.devel/2007-11/msg00033.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 10:39:50 2009 From: trac at haiku-os.org (korli) Date: Mon, 18 May 2009 08:39:50 -0000 Subject: [Haiku-bugs] [Haiku] #3530: nForce (MCP61 Ethernet) not work correctly In-Reply-To: <041.a5f379237c17937911a9a26f8fc8f251@haiku-os.org> References: <041.a5f379237c17937911a9a26f8fc8f251@haiku-os.org> Message-ID: <050.ba07ac3bc90a07e8418d28044bed1edc@haiku-os.org> #3530: nForce (MCP61 Ethernet) not work correctly -------------------------------------+-------------------------------------- Reporter: Hubert | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/TCP | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 11:11:11 2009 From: trac at haiku-os.org (axeld) Date: Mon, 18 May 2009 09:11:11 -0000 Subject: [Haiku-bugs] [Haiku] #3862: Shutdown doesn't wait for user input In-Reply-To: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> References: <040.9e9d50e0a20bd55d5c9e6c66ee692ecb@haiku-os.org> Message-ID: <049.674c336be7dd9cbb62fe28e5277364ac@haiku-os.org> #3862: Shutdown doesn't wait for user input --------------------------------+------------------------------------------- Reporter: zooey | Owner: axeld Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: Servers/registrar | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by axeld): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30788. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 11:58:51 2009 From: trac at haiku-os.org (mmlr) Date: Mon, 18 May 2009 09:58:51 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.6c752bcea5bebfaccb1f1debbc579f9b@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by mmlr): Never mind, it's of course a bug in my kqemu. The initial lock_memory() runs in the context of the QEMU team, but later when the driver is closed the unlock_memory() is triggered from the kernel. Therefore the team_id has to be stored and unlock_memory_etc() has to be used. The strange thing is that this exact same (broken) method worked before with the old kqemu of the old QEMU. My theory is that previously the driver was properly closed by QEMU when shutting down the emulation (so again inside the QEMU team context). This would also explain why this panic would occure when the emulation crashed (I think I remember to have seen it in that context). Right now it seems that the driver is not properly closed but instead the kernel cleans it up when the team goes down. This is probably related to some changes I need to adapt my port to again. Sorry for the noise. The same kind of error could be responsible for this bug though. Seeing that it seems to always be triggered on program termination where the kernel would potentially clean up open handles. In case this is really the case debug output in unlock_memory() indicating the failed unlock should reveal that. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 15:31:58 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 18 May 2009 13:31:58 -0000 Subject: [Haiku-bugs] [Haiku] #3930: AboutSystem - manage duplicate OptionalPackageDescriptions In-Reply-To: <041.058ac659e2925af5287d3156ef3cf52e@haiku-os.org> References: <041.058ac659e2925af5287d3156ef3cf52e@haiku-os.org> Message-ID: <050.3072c7f23eb0ab15950a8b7fa5d56b1b@haiku-os.org> #3930: AboutSystem - manage duplicate OptionalPackageDescriptions --------------------------------------+------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1/alpha1 Component: Applications/AboutSystem | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Changes (by bonefish): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 15:47:19 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 18 May 2009 13:47:19 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.ab668d60f5ed8a9c0151caa456f674c2@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:15 mmlr]: > The same kind of error could be responsible for this bug though. Seeing that it seems to always be triggered on program termination where the kernel would potentially clean up open handles. In case this is really the case debug output in unlock_memory() indicating the failed unlock should reveal that. lock_memory() increments the page's wired_count. In the instances of this bug where we've had a closer look at the page, it still had a mapping in a completely unrelated area, though, so they can't be lock_memory() related. That aside, there are also still TODO's in lock_memory_etc() which should be tackled eventually. E.g. currently it is possible to delete or shrink an area with locked memory, which will create wired free pages. Unless caused on purpose, it's rather unlikely that this happens in practice, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 17:47:25 2009 From: trac at haiku-os.org (humdinger) Date: Mon, 18 May 2009 15:47:25 -0000 Subject: [Haiku-bugs] [Haiku] #3937: userguide/en/installation.html displays as code and not as end-product In-Reply-To: <041.319b08ce3a884040ebb37c84d9e77301@haiku-os.org> References: <041.319b08ce3a884040ebb37c84d9e77301@haiku-os.org> Message-ID: <050.ea00c05550b125e3f2c4f80d3e3188bc@haiku-os.org> #3937: userguide/en/installation.html displays as code and not as end-product ------------------------+--------------------------------------------------- Reporter: mmadia | Owner: humdinger Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by humdinger): * status: new => closed * resolution: => fixed Comment: Should be fixed with r30790. Thanks for noticing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 17:55:48 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 18 May 2009 15:55:48 -0000 Subject: [Haiku-bugs] [Haiku] #3930: AboutSystem - manage duplicate OptionalPackageDescriptions In-Reply-To: <041.058ac659e2925af5287d3156ef3cf52e@haiku-os.org> References: <041.058ac659e2925af5287d3156ef3cf52e@haiku-os.org> Message-ID: <050.eefa739fcb5dea92dd6bda14b58d5d13@haiku-os.org> #3930: AboutSystem - manage duplicate OptionalPackageDescriptions ---------------------------------------+------------------------------------ Reporter: mmadia | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Applications/AboutSystem | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30791. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 18:29:56 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 18 May 2009 16:29:56 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 Message-ID: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> #3940: Can't install from CD at r30790 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Just did my first native build on an Athlon 64 3000+ at r30790 and the CD wouldn't get past the rocketship icon, even using Safe Boot. I reverted my code to the last known good build which is r30782 here, and retried with success. Recent changes to Path.cpp might be the cause. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 19:55:19 2009 From: trac at haiku-os.org (axeld) Date: Mon, 18 May 2009 17:55:19 -0000 Subject: [Haiku-bugs] [Haiku] #3933: ATA locks up on the EeePC In-Reply-To: <040.02b998b4b756de7d89239b64fdce83ad@haiku-os.org> References: <040.02b998b4b756de7d89239b64fdce83ad@haiku-os.org> Message-ID: <049.fc8917022cafedcb896be8b4a766e586@haiku-os.org> #3933: ATA locks up on the EeePC --------------------------+------------------------------------------------- Reporter: axeld | Owner: mmlr Type: bug | Status: new Priority: critical | Milestone: R1 Component: Drivers/Disk | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by axeld): * priority: normal => critical Comment: I bought a new stick, and I cannot reproduce my earlier results anymore with this one; the system always locks up now, no matter if I put snooze() in there, or turn off IDE DMA. Therefore bumping the bug's relevance. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 21:27:26 2009 From: trac at haiku-os.org (diver) Date: Mon, 18 May 2009 19:27:26 -0000 Subject: [Haiku-bugs] [Haiku] #2497: [AboutSystem] right textview is not selectable (easy) In-Reply-To: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> References: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> Message-ID: <049.ec27e20bad2abc1cbce5ead4853dd7e8@haiku-os.org> #2497: [AboutSystem] right textview is not selectable (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by diver): * status: closed => reopened * resolution: fixed => Comment: Seems like recent changes broke it again, reopening. Tested in r30793 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 22:43:26 2009 From: trac at haiku-os.org (zooey) Date: Mon, 18 May 2009 20:43:26 -0000 Subject: [Haiku-bugs] [Haiku] #2497: [AboutSystem] right textview is not selectable (easy) In-Reply-To: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> References: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> Message-ID: <049.740a90891412a84376f128f5861bdd6a@haiku-os.org> #2497: [AboutSystem] right textview is not selectable (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: zooey Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by zooey): * owner: axeld => zooey * status: reopened => new -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 22:50:42 2009 From: trac at haiku-os.org (zooey) Date: Mon, 18 May 2009 20:50:42 -0000 Subject: [Haiku-bugs] [Haiku] #2497: [AboutSystem] right textview is not selectable (easy) In-Reply-To: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> References: <040.f4632fc7d182c2facaf7ee332be9915b@haiku-os.org> Message-ID: <049.4ffd124e7927ef0762765d84a3196ac1@haiku-os.org> #2497: [AboutSystem] right textview is not selectable (easy) ---------------------------+------------------------------------------------ Reporter: diver | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by zooey): * status: new => closed * resolution: => fixed Comment: Fixed again in r30796. Ingo's recent changes removed the invocation of MakeSelectable(true), but the credits view was explicitly made non- selectable upon creation - why, I don't know. Now the credits view falls back to the default, which is to be selectable. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 18 23:06:17 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 18 May 2009 21:06:17 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.1ebfaccd30696af0455279418f8f8596@haiku-os.org> #3940: Can't install from CD at r30790 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Changes (by bonefish): * owner: bonefish => axeld * component: Build System => - General Comment: Please only select a component, if it might actually have something to do with the reported bug. If your best guess is BPath changes, then "Build System" is definitely the wrong component. And no, "Build System" is not the fallback component, just because everything is built by the build system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 03:01:52 2009 From: trac at haiku-os.org (masopmac1) Date: Tue, 19 May 2009 01:01:52 -0000 Subject: [Haiku-bugs] [Haiku] #3482: nVidia evga PCI-E 7200GS (256MB) distorted video/hang on boot In-Reply-To: <044.277e8e8a7c2b11753acef5134e36d6b7@haiku-os.org> References: <044.277e8e8a7c2b11753acef5134e36d6b7@haiku-os.org> Message-ID: <053.9d3fdcd5bb0ccdb7fa530a81cc168da9@haiku-os.org> #3482: nVidia evga PCI-E 7200GS (256MB) distorted video/hang on boot --------------------------------------+------------------------------------- Reporter: masopmac1 | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment(by masopmac1): Thank you for all of your work on this! -Sam -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 10:20:08 2009 From: trac at haiku-os.org (Hubert) Date: Tue, 19 May 2009 08:20:08 -0000 Subject: [Haiku-bugs] [Haiku] #1115: Booting in Live CD mode is slow In-Reply-To: <042.eb64b2b19c862197ed8c690874af5705@haiku-os.org> References: <042.eb64b2b19c862197ed8c690874af5705@haiku-os.org> Message-ID: <051.e308197a4b537b55c0f5e44d5ec87d70@haiku-os.org> #1115: Booting in Live CD mode is slow --------------------------------+------------------------------------------- Reporter: rdaneel | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: System/Boot Loader | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by Hubert): * cc: HubertNG@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 10:20:47 2009 From: trac at haiku-os.org (Hubert) Date: Tue, 19 May 2009 08:20:47 -0000 Subject: [Haiku-bugs] [Haiku] #3151: KDL when copying data between 2 BFS partitions. In-Reply-To: <038.c6aaad7f29e81a63b24f4c1d221b9c5a@haiku-os.org> References: <038.c6aaad7f29e81a63b24f4c1d221b9c5a@haiku-os.org> Message-ID: <047.f6dc8439f5d8960d9f24cae989caee9c@haiku-os.org> #3151: KDL when copying data between 2 BFS partitions. ---------------------------+------------------------------------------------ Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ---------------------------+------------------------------------------------ Changes (by Hubert): * cc: HubertNG@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 10:21:08 2009 From: trac at haiku-os.org (Hubert) Date: Tue, 19 May 2009 08:21:08 -0000 Subject: [Haiku-bugs] [Haiku] #3150: BFS directory corruption. In-Reply-To: <038.28292c867ae3be742393ec086836c73f@haiku-os.org> References: <038.28292c867ae3be742393ec086836c73f@haiku-os.org> Message-ID: <047.3f0ef3ed1e8b6ddfcaa2d0f8174438d8@haiku-os.org> #3150: BFS directory corruption. ------------------------------+--------------------------------------------- Reporter: bga | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by Hubert): * cc: HubertNG@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 18:38:03 2009 From: trac at haiku-os.org (Hubert) Date: Tue, 19 May 2009 16:38:03 -0000 Subject: [Haiku-bugs] [Haiku] #2296: no display graphics In-Reply-To: <040.0ed06d15561e60c2dae21df5b9ee0be8@haiku-os.org> References: <040.0ed06d15561e60c2dae21df5b9ee0be8@haiku-os.org> Message-ID: <049.9bc8d5dc36803f58bfc761c7edd4c13d@haiku-os.org> #2296: no display graphics --------------------------------------------+------------------------------- Reporter: hugen | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/intel_extreme | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------------------+------------------------------- Comment(by Hubert): I tested now: boot with USB work correctly, boot with CD: black screen - I need use safe video mode with save boot to boot further. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 19 22:26:46 2009 From: trac at haiku-os.org (bbjimmy) Date: Tue, 19 May 2009 20:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #3941: "Install anyways" Message-ID: <042.1383e7fe317e9fd2bebd4026cc70bb6a@haiku-os.org> #3941: "Install anyways" ------------------------------------+--------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- When installing onto a bfs partition that has data on it, the installer opens an alert panel warning that there is data on the partition with buttons labeled "Install anyways" or "cancel" Anyways is not proper English ... see http://grammartips.homestead.com/anyway.html "This is going to be short and simple. Do not say or write "anyways"--not ever. The word is "anyway." The form "anyways" is found in some dialects in the United States, but it is not standard English, and it should never be used in any situation where you want to be considered reasonably well educated. That's all there is to it. " -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 00:10:30 2009 From: trac at haiku-os.org (stippi) Date: Tue, 19 May 2009 22:10:30 -0000 Subject: [Haiku-bugs] [Haiku] #3941: "Install anyways" In-Reply-To: <042.1383e7fe317e9fd2bebd4026cc70bb6a@haiku-os.org> References: <042.1383e7fe317e9fd2bebd4026cc70bb6a@haiku-os.org> Message-ID: <051.6e9dcbcccd12b28bed76903608a57e62@haiku-os.org> #3941: "Install anyways" -------------------------------------+-------------------------------------- Reporter: bbjimmy | Owner: korli Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -------------------------------------+-------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Thanks a lot for noticing! Fixed in r30805. I guess I may have learned English in one of those areas in the US where they speak those dialects... :-} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 19:50:39 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 20 May 2009 17:50:39 -0000 Subject: [Haiku-bugs] [Haiku] #3942: Unable to build CD image ISO-9660 directories too deep Message-ID: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> #3942: Unable to build CD image ISO-9660 directories too deep --------------------------+------------------------------------------------- Reporter: scottmc | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- I'm getting now when I run jam -q haiku-cd: {{{ Unzipping generated/download/Subversion.zip ... Installing MIME database ... Generating attribute stores ... Copying boot image ... Building CD image ... Warning: creating filesystem that does not conform to ISO-9660. I: -input-charset not specified, using utf-8 (detected in locale settings) genisoimage: Directories too deep for 'generated/tmp/cdsource/develop/tools/gcc-2.95.3-haiku-081024/lib/gcc- lib/i586-pc-haiku/2.95.3-haiku-081024/include' (7) max is 6. ...updated 408 target(s)... }}} This was attempted on Ubuntu-8.10 IIRC, with various optional packages enabled, including the full development tools. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 19:59:00 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 20 May 2009 17:59:00 -0000 Subject: [Haiku-bugs] [Haiku] #3942: Unable to build CD image ISO-9660 directories too deep In-Reply-To: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> References: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> Message-ID: <051.73f9bfdb833daa116624637bb23fd1bf@haiku-os.org> #3942: Unable to build CD image ISO-9660 directories too deep ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by mmadia): * status: new => closed * resolution: => invalid Comment: genisoimage is not mkisofs. mkisofs is available at http://cdrecord.berlios.de/private/cdrecord.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 20:02:51 2009 From: trac at haiku-os.org (fano) Date: Wed, 20 May 2009 18:02:51 -0000 Subject: [Haiku-bugs] [Haiku] #3936: Microsoft Wireless Optical mouse 2000 doesn't work In-Reply-To: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> References: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> Message-ID: <048.4d8e7d5df4696ed7db41728c1b499338@haiku-os.org> #3936: Microsoft Wireless Optical mouse 2000 doesn't work -------------------------------+-------------------------------------------- Reporter: fano | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by fano): I've done the command the only usb recognized (for that I can understand) is the "backup" logitech usb mouse... nothing from Microsoft... but the keyboard with I'm writing is working. Well I attached you can see the result of listub I hope will be useful for you. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 20:04:31 2009 From: trac at haiku-os.org (VinDuv) Date: Wed, 20 May 2009 18:04:31 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.fc5025478d30a779b6840af0204a270e@haiku-os.org> #3940: Can't install from CD at r30790 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by VinDuv): Do you use any optional packages ? I noticed the same behaviour when creating a CD image with many of them included.[[BR]] The last line of the serial log was something like "cannot start /bin/sh, error = -1". Maybe a file number limit is hit somewhere...[[BR]] In your case, some files may have been added to the build between r30782 and r30790, and made the limit reached. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 20:11:50 2009 From: trac at haiku-os.org (fano) Date: Wed, 20 May 2009 18:11:50 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.9da85a499f193a4b85905c5caac85d82@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by fano): I don't know if it can be useful but I've attached the result of listdev command in my system. Maybe lspci give more useful infos... but in Haiku is not present... for now I've only Windows and Haiku (on usb key) installed on my PC. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 20:17:06 2009 From: trac at haiku-os.org (philcostin) Date: Wed, 20 May 2009 18:17:06 -0000 Subject: [Haiku-bugs] [Haiku] #3803: Random characters displayed in Terminal In-Reply-To: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> References: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> Message-ID: <049.fd803487003082d903a554daf9a47b21@haiku-os.org> #3803: Random characters displayed in Terminal --------------------------------+------------------------------------------- Reporter: haiqu | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------------+------------------------------------------- Comment(by philcostin): I've been playing with this for a while:- Here's the rule: - When the cursor is anywhere on the last row of the Terminal and you scroll down one line, the character position one row directly above the cursor is not being invalidated to display the character that was previously under the cursor. - If you move the cursor back up one row over that character position, THEN it invalidates and redraws the correct character. (tested using vi) I hope that helps solve it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 20 20:25:09 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 20 May 2009 18:25:09 -0000 Subject: [Haiku-bugs] [Haiku] #3942: Unable to build CD image ISO-9660 directories too deep In-Reply-To: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> References: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> Message-ID: <051.6dd1c5aca5fdc8e429648f5dad6c4b27@haiku-os.org> #3942: Unable to build CD image ISO-9660 directories too deep ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by scottmc): Could a warning be added to let us know this, such as was the case with yasm a few weeks ago? I'll try mkisofs. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 01:14:49 2009 From: trac at haiku-os.org (Bouncer) Date: Wed, 20 May 2009 23:14:49 -0000 Subject: [Haiku-bugs] [Haiku] #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. Message-ID: <042.7c7172d251d85b53b413ecbfab64fc32@haiku-os.org> #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. -----------------------+---------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This item may be related to ticket 3879. Please Note: It is been many months since I last compiled the Haiku. FIRST - I did a full download - and configured UserConfig similarly to my previous experiences. With HAIKU_IMAGE_SIZE set to 300. And HAIKU_ADD_ALL_OPTIONAL_PACKAGES = 1. The jam command was 'jam -q haiku-image'. The build was partially successfull. Creating the 300 Mb image but the optional packages were missing. Seems obvious as to what was wrong ... SECOND - I commented out the 'HAIKU_ADD_ALL_OPTIONAL_PACKAGES' and replaced it with 'AddOptionalHaikuImagePackages', specifying all of the packages that I wanted. Now - the packages were downloaded - but the image that was created was only 128 Mb. Every subsequent build attempt - always created an image that was only 128 Mb in size. I even deleted the 'image', but the next rebuild still created it with the default size - regardless of what I set HAIKU_IMAGE_SIZE to. My build environment was on Ubuntu 8.04 A POSSIBLE WORKAROUND: - I removed all optional packages from UserBuildConfig. The build then successfully created a 300 Mb image. - Next - I restored the optional packages. Using the 'AddOptionalHaikuImagePackages' method. This time the build created an image of the proper size, with all of the desired packages. - There seems to be some sort of persistent environment setting that is sensitive to the presence of optional packages. Only when I removed the optional packages - did it clear itself. After which my builds were normal, even when I re-applied the optional packages again. You may close this ticket if you wish. I submit it as a reference for others who might encounter the same issues. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 01:21:09 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 20 May 2009 23:21:09 -0000 Subject: [Haiku-bugs] [Haiku] #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. In-Reply-To: <042.7c7172d251d85b53b413ecbfab64fc32@haiku-os.org> References: <042.7c7172d251d85b53b413ecbfab64fc32@haiku-os.org> Message-ID: <051.b0669a7bb55a0a78411b231a2ef7aac9@haiku-os.org> #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmadia): * status: new => closed * resolution: => invalid Comment: First, I appreciate your interest in Haiku. It is very likely that you had a syntax error in your UserBuildConfig. Please view http://dev.haiku-os.org/wiki/BugTrackerEtiquette . That page describes where to seek assistance for such errors. closing --> invalid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 02:37:39 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 21 May 2009 00:37:39 -0000 Subject: [Haiku-bugs] [Haiku] #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. In-Reply-To: <042.7c7172d251d85b53b413ecbfab64fc32@haiku-os.org> References: <042.7c7172d251d85b53b413ecbfab64fc32@haiku-os.org> Message-ID: <051.e113595f4df9a0091ffc1a1ac28f5eae@haiku-os.org> #3943: HAIKU_IMAGE_SIZE in UserBuildConfig - behaved in inconsistent manner. ------------------------+--------------------------------------------------- Reporter: Bouncer | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by mmlr): To clarify some more. The "add all packages" functionality has been removed by now. You should not blindly install every optional package, but selectively take out those that you want. One of the reasons was that there may be incompatibilities between optional packages and default installs (like in the OpenSound vs. hda case) or that there are simply packages that make not much sense for an installation except for a few special cases (like some of the test packages). Therefore you should choose the packages you need as a conscious decision. As Matt already pointed out it is most likely that you had a syntax error when you changed your UserBuildConfig so that the image size setting was rendered useless. Most likely a missing space between a closing semicolon. But as Matt also points out we usually don't document stuff using tickets. For that case a message to an appropriate mailing list is a better fit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 10:20:34 2009 From: trac at haiku-os.org (andreasf) Date: Thu, 21 May 2009 08:20:34 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.5db5dcaa49a21ce6fa148f26fdf7e021@haiku-os.org> #3916: struct stat POSIX naming issue -------------------------------+-------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 12:55:06 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 21 May 2009 10:55:06 -0000 Subject: [Haiku-bugs] [Haiku] #3936: Microsoft Wireless Optical mouse 2000 doesn't work In-Reply-To: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> References: <039.10c8e4c141f3527213722ff38314f601@haiku-os.org> Message-ID: <048.60d30cca069a900457485498e04d99b8@haiku-os.org> #3936: Microsoft Wireless Optical mouse 2000 doesn't work --------------------------------+------------------------------------------- Reporter: fano | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Mouse/USB | Version: R1 development Resolution: duplicate | Blockedby: 2253 Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 2253 Comment: Looks fine. The very first device listed is a Microsoft HID device. It has two interfaces of which the first one is the keyboard supporting the boot protocol. The second interface could very well be the mouse, or a combined mouse/keyboard interface. Since the second one doesn't work with the boot protocol (as it can't when providing more flexible input), it isn't recognized by the Haiku usb_hid, as this one currently still lacks generic HID support. Support for that is tracked in #2253, so closing this as a duplicate. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 13:18:44 2009 From: trac at haiku-os.org (ghen) Date: Thu, 21 May 2009 11:18:44 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout Message-ID: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> #3944: support for Colemak keyboard layout --------------------------------+------------------------------------------- Reporter: ghen | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Hi, I've implemented the Colemak keyboard layout for Haiku in the attached keymap file. Colemak is an alternative, ergonomic keyboard layout (somewhat like Dvorak, but more modern), see http://colemak.com for more information. The file should go under src/data/etc/keymaps/. I tested it on my x86 laptop with PS/2 (internal) and USB external keyboards. Thanks. Geert -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 13:37:43 2009 From: trac at haiku-os.org (stippi) Date: Thu, 21 May 2009 11:37:43 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout In-Reply-To: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> References: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> Message-ID: <048.f86f3d99b468c915927d794b29894dac@haiku-os.org> #3944: support for Colemak keyboard layout --------------------------------+------------------------------------------- Reporter: ghen | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by stippi): * owner: axeld => stippi * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 13:47:13 2009 From: trac at haiku-os.org (stippi) Date: Thu, 21 May 2009 11:47:13 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout In-Reply-To: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> References: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> Message-ID: <048.82360373944e3284371248ad29edae82@haiku-os.org> #3944: support for Colemak keyboard layout --------------------------------+------------------------------------------- Reporter: ghen | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): I've looked closely at the keymap. Was this based on any other keymap, if so, which one? I am wondering about the "CapsLock = 0x00" at the beginning of the file. All other keymaps I have checked have "CapsLock = 0x3b" there. The CapsLock row also still has the normal "QWERTYUIOP" assignment. Was this intentional? Thanks for your patch and any comments! Best regards, -Stephan -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 13:50:20 2009 From: trac at haiku-os.org (rudolfc) Date: Thu, 21 May 2009 11:50:20 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.664fd64fd0c5cc263e7fc99b8e28cdd5@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, I could locate the old benchmark tool I have here, fortunately it works on Haiku as well. I tested with a G72 (GF7300) on my system: (FSB probably 1066Mhz) This is a PCIe V2 system. Don't know the busrevision a G72 has btw. ~/rudolf> GfxBusBench-0.7 --allsizes GfxBusBench 0.7 CPU: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz, Clock: 2.67 GHz, FSB: 0 MHz. Screenmode: 800x600x32, framebuffer address: 0x90000800 Write 64-bit: 1315.46 MB/s (3955.08 MB in 3.01 s) Write 32-bit: 1319.26 MB/s (3991.70 MB in 3.03 s) Write 8-bit: 1308.87 MB/s (3955.08 MB in 3.02 s) Read 64-bit: 5.66 MB/s (18.31 MB in 3.24 s) Read 32-bit: 4.41 MB/s (14.65 MB in 3.32 s) Read 8-bit: 1.11 MB/s (5.49 MB in 4.97 s) On my old P4-2800 with AGP at 4x and FW enabled: write 64/32/8 bit: 670Mb/sec read 64: 10Mb /sec read 32: 5Mb/sec read 8: 1.25Mb/sec. I remember on my old PCIe system (V1 bus) with my GF6600 that writing was much slower than with AGP+Fw. Anyhow, reading is the real problem, and must always be done with 64bit reads for 'optimum performance'. The measuring tool was written by: GfxBusBench 0.7 ? 2005 by Christian Packmann Unfortunately I don't have the sources as I would love such a tool in Haiku by default!! Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 13:55:53 2009 From: trac at haiku-os.org (ghen) Date: Thu, 21 May 2009 11:55:53 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout In-Reply-To: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> References: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> Message-ID: <048.6c7b76cb521a2f0c6463df906383498c@haiku-os.org> #3944: support for Colemak keyboard layout --------------------------------+------------------------------------------- Reporter: ghen | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by ghen): Yes, this is intentional, because in Colemak, the Caps Lock key is replaced by a second Backspace (as you can see in the keymap preview window). See http://colemak.com/ for more info about the layout. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 14:02:25 2009 From: trac at haiku-os.org (stippi) Date: Thu, 21 May 2009 12:02:25 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout In-Reply-To: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> References: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> Message-ID: <048.8f7fb855a431e5e2a51debeac9e47e08@haiku-os.org> #3944: support for Colemak keyboard layout --------------------------------+------------------------------------------- Reporter: ghen | Owner: stippi Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by stippi): Ah, sorry I missed that part. I assume the second backspace key works also with your keymap. I'll apply it in a minute... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 14:06:03 2009 From: trac at haiku-os.org (stippi) Date: Thu, 21 May 2009 12:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #3944: support for Colemak keyboard layout In-Reply-To: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> References: <039.393978619adef3cadf09f9544880a77d@haiku-os.org> Message-ID: <048.a9a6e92bdfab100436417ea7a4a2b4df@haiku-os.org> #3944: support for Colemak keyboard layout ---------------------------------+------------------------------------------ Reporter: ghen | Owner: stippi Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Keymap | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by stippi): * status: assigned => closed * resolution: => fixed Comment: Thanks a lot! Added to SVN in r30814. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 18:35:24 2009 From: trac at haiku-os.org (haiqu) Date: Thu, 21 May 2009 16:35:24 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.c5290aaf9ab9f8cb7c999492f86e6c89@haiku-os.org> #3940: Can't install from CD at r30790 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by haiqu): Invalid. Problem was caused by a faulty unused 30Gb hard drive, which is now junk. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 18:49:52 2009 From: trac at haiku-os.org (axeld) Date: Thu, 21 May 2009 16:49:52 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.0e3b5c7d854eaed0fb1d879cc9c51390@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: invalid | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by axeld): * status: new => closed * resolution: => invalid Comment: Thanks for the update! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 19:06:03 2009 From: trac at haiku-os.org (tqh) Date: Thu, 21 May 2009 17:06:03 -0000 Subject: [Haiku-bugs] [Haiku] #3281: ffs() arch optimization In-Reply-To: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> References: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> Message-ID: <047.00f33c483a0ed98decd3c3d2966e7628@haiku-os.org> #3281: ffs() arch optimization -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by tqh): Learning by doing :) Might have missed something in the patch, but it works fine here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 19:06:11 2009 From: trac at haiku-os.org (tqh) Date: Thu, 21 May 2009 17:06:11 -0000 Subject: [Haiku-bugs] [Haiku] #3281: ffs() arch optimization In-Reply-To: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> References: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> Message-ID: <047.ad61d1977bb170ae5fd9576412473f10@haiku-os.org> #3281: ffs() arch optimization -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by tqh): * cc: fredrik.holmqvist@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 19:16:55 2009 From: trac at haiku-os.org (tqh) Date: Thu, 21 May 2009 17:16:55 -0000 Subject: [Haiku-bugs] [Haiku] #3281: ffs() arch optimization In-Reply-To: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> References: <038.bfbbef4cc5baf5a6352348428218fcd3@haiku-os.org> Message-ID: <047.14609d17a84b21e09d1211ec8282e09b@haiku-os.org> #3281: ffs() arch optimization -------------------------------+-------------------------------------------- Reporter: tqh | Owner: axeld Type: enhancement | Status: new Priority: low | Milestone: R1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Comment(by tqh): This patch may be overkill though and the function just defined in the arch_string.S, I just wanted to learn to be able to go all the way to runtime cpu-optimized functions. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 21 21:42:19 2009 From: trac at haiku-os.org (kaliber) Date: Thu, 21 May 2009 19:42:19 -0000 Subject: [Haiku-bugs] [Haiku] #3945: getaddrinfo() issue Message-ID: <042.a8d241555d8a2f12a3dc7f5681aacb76@haiku-os.org> #3945: getaddrinfo() issue ------------------------------+--------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Network Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Samba daamon (smbd) doesn't work because of broken getaddrinfo(). The function return an error if a hint AI_GETADDRINFO is passed. I've made investigation and realized that AI_MASK in netdb.h is incorrect. Please look at: http://dev.haiku- os.org/browser/haiku/trunk/src/kits/network/dns/irs/getaddrinfo.c#L336 and http://dev.haiku-os.org/browser/haiku/trunk/headers/posix/netdb.h#L206 In my opinion AI_MASK should be defined as follow: {{{ #define AI_MASK (AI_PASSIVE | AI_CANONNAME | AI_NUMERICHOST | AI_ADDRCONFIG) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 22 01:13:05 2009 From: trac at haiku-os.org (jonas.kirilla) Date: Thu, 21 May 2009 23:13:05 -0000 Subject: [Haiku-bugs] [Haiku] #3946: automount weirdness: creates symlink at mount point Message-ID: <048.b2e4220462b5a9106a2b425193cfca4b@haiku-os.org> #3946: automount weirdness: creates symlink at mount point ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Running Haiku off harddisk (r30806 and r30823 on two different machines) I tried plugging a USB stick to which I had dd:ed a BFS image. (IIRC a haiku.image, from some April 12 revision, if the below output is to be trusted.) No volume appeared, but Tracker's mount menu showed the volume as mounted. I tried to unmount but the volume remained checkmarked in the mount menu. Wondering what was up I turned to Terminal and had a look at the filesystem mount points. After USB stick insertion and Tracker r/w dialog answered, the following symlink appears at /: {{{ /> ls -al ... lrwxrwxrwx 1 baron root 30 Apr 12 21:17 Haiku1 -> /boot/system/preferences/Media ... }}} A symlink is unexpected. The link target is just puzzling. Its permissions deviates from the other symlinks at the fs root. After removal of USB stick: {{{ /> ls -al ... drwxr-xr-x 1 baron root 0 May 21 22:06 Haiku1 ... /> }}} Now we're back to a folder for the mount point. (Created before the symlink and covered by it, now revealed again?) See attached file for full output. I don't think I can reproduce this anymore. Having dd:ed a later Haiku revision to the stick, Haiku crashes in the "bfs block allocator". (Worn out flash maybe?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 22 17:21:00 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 22 May 2009 15:21:00 -0000 Subject: [Haiku-bugs] [Haiku] #3916: struct stat POSIX naming issue In-Reply-To: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> References: <043.548e77c5e2c897cd8502f16e8ef45fa1@haiku-os.org> Message-ID: <052.96c4d0a7dc588123ac18f177f34495e6@haiku-os.org> #3916: struct stat POSIX naming issue --------------------------------+------------------------------------------- Reporter: andreasf | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Implemented as I proposed in r30830. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 22 18:50:37 2009 From: trac at haiku-os.org (rossi) Date: Fri, 22 May 2009 16:50:37 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions Message-ID: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- The p7zip optional package seems to contain some wrong permissions. At least the tempory files created during the build cannot be removed (unless using sudo of course). You can also see the errors generated during the build in the attached log. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 22 19:25:40 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 22 May 2009 17:25:40 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.1c654090e543538d0c7e4cac2943d349@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): I have new builds of apr-1.3.3, apr-util-1.3.4, openssh-5.2p1, and subversion-1.6.2 that I am currently testing. It appears that subversion has a handful of dependencies, so I am rechecking those as well. Should have something to add in the next week or so. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 07:12:15 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 23 May 2009 05:12:15 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.d617ba14d5cf971194267d4ac57988bd@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmadia): just to note: flex, jam, and openssh's licenses are now kept in beos/etc/licenses. They should be repackaged and use common/data/licenses or home/config/data/licenses. See [http://www.haiku-os.org/node/2525] for more info -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 13:26:38 2009 From: trac at haiku-os.org (siarzhuk) Date: Sat, 23 May 2009 11:26:38 -0000 Subject: [Haiku-bugs] [Haiku] #3399: The system reboots while running jam -q on the haiku trunk. In-Reply-To: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> References: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> Message-ID: <051.9dc7b388a4ea3cdf584e062b314cbd36@haiku-os.org> #3399: The system reboots while running jam -q on the haiku trunk. -----------------------+---------------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 13:28:49 2009 From: trac at haiku-os.org (siarzhuk) Date: Sat, 23 May 2009 11:28:49 -0000 Subject: [Haiku-bugs] [Haiku] #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit In-Reply-To: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> References: <042.c6025ee34d274254a1a3ec7d7f314c13@haiku-os.org> Message-ID: <051.a707d241fdfe2b3d0cd802928adb9d09@haiku-os.org> #2719: [bfs]: deadlock - mutex bfs inode+24.1243 not released on exit ------------------------------+--------------------------------------------- Reporter: emitrax | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 13:34:28 2009 From: trac at haiku-os.org (siarzhuk) Date: Sat, 23 May 2009 11:34:28 -0000 Subject: [Haiku-bugs] [Haiku] #2923: install-haiku target hangs when trying to install to /boot In-Reply-To: <044.c8280c4e82c0524ac79caceed639dac1@haiku-os.org> References: <044.c8280c4e82c0524ac79caceed639dac1@haiku-os.org> Message-ID: <053.c607c0a77adf28bda4b9032718c15da3@haiku-os.org> #2923: install-haiku target hangs when trying to install to /boot ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 14:07:03 2009 From: trac at haiku-os.org (luroh) Date: Sat, 23 May 2009 12:07:03 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.a5abd0173d425c2f54790ad9ce08069d@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): Confirmed. Building gcc2 on Ubuntu 9.04 32-bit. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 19:14:39 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 23 May 2009 17:14:39 -0000 Subject: [Haiku-bugs] [Haiku] #3948: WIP [patch] add @alpha-cd to jamfiles Message-ID: <041.bed64698f5c66295e3b74a8566d0523f@haiku-os.org> #3948: WIP [patch] add @alpha-cd to jamfiles --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- This is a work-in-progress patch to allow a user to run `jam -q @alpha-cd` There are some issues with this. First, the [: ] portion of DefineBuildProfile does not work. Instead "haiku-cd.iso" is used as the filename. Second, when building within Haiku, some folders do not appear. Though they exist. Eg, when mounting ISO file "system" does not appear in either Tracker or `ls`. However, cd /path/system works -- where '/path' is the mountpoint. This second issue may be a result from re-using the object folder from `jam -q @alpha-raw`, so take it with a grain of salt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 19:34:16 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 23 May 2009 17:34:16 -0000 Subject: [Haiku-bugs] [Haiku] #3949: Some Backgrounds enhancements (easy) Message-ID: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> #3949: Some Backgrounds enhancements (easy) -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- This is r30824. There are some details that are not yet perfect. :) # When I invoke the Background add-on on an image file, the selected image is shown in the preference panel for the "Default Folder". Personally, I think this function is more often used for setting a workspace's background, so it may be more useful to set "Current Workspace" here instead. # When changing from "Default folder" to "Current/All Workspaces", the image that invoked the Background panel is replaced with the current background image of the workspace. Keeping the invoking image is a better idea IMO. # The "Default Folder" shows "backgroundTexture.tga" as image file. Too nerdy IMO, and what's the difference to selecting "None"? I guess... "none"? # From an aesthetical POV, the "Preview" string above the monitor representation on the left should either have a few pixel distance to the monitor or, better IMO, forget the "Preview" sring altogether. # I don't have a working widescreen resolution under Haiku, so I can't test this: does the preview monitor change aspect according to the workspace's resolution? It should. # There's still ticket #1006, eliminating the Apply button. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 19:39:39 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 23 May 2009 17:39:39 -0000 Subject: [Haiku-bugs] [Haiku] #3950: Screen preferences: Eliminate Preview monitor (easy) Message-ID: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> #3950: Screen preferences: Eliminate Preview monitor (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- This is r30824. I can't think of a reason to keep the preview monitor to the left of the Screen preference panel. Can't we lose that thing and put the workspaces count and a button to "Set Background" under the rest of the drop-down menus to the right? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 19:59:45 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 23 May 2009 17:59:45 -0000 Subject: [Haiku-bugs] [Haiku] #3949: Some Backgrounds enhancements (easy) In-Reply-To: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> References: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> Message-ID: <053.2b71ff06655df724affe4b9e182a3ea2@haiku-os.org> #3949: Some Backgrounds enhancements (easy) -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by humdinger): Oh, one more. Most important IMO: # When using "Scale to fit" Backgrounds should really to use ShowImage's "High Quality Zoom" for filtered resizing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 20:27:14 2009 From: trac at haiku-os.org (stippi) Date: Sat, 23 May 2009 18:27:14 -0000 Subject: [Haiku-bugs] [Haiku] #3949: Some Backgrounds enhancements (easy) In-Reply-To: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> References: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> Message-ID: <053.21907eab0cb3f32a0797b59a4072bb53@haiku-os.org> #3949: Some Backgrounds enhancements (easy) -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by stippi): IIRC, I already implemented the backend for your last item. Tracker just needs to pass the bilinear filter option in the flags parameter to SetViewBitmap(). Maybe this ought to be configurable, since it uses more CPU. That's why I didn't just go ahead and did it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 20:33:13 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 23 May 2009 18:33:13 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.9adbab5427ee19dfa5174ac0f068d60f@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): never mind the license zip files i attached, i'll include them in the individual optional package zips instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 20:43:48 2009 From: trac at haiku-os.org (axeld) Date: Sat, 23 May 2009 18:43:48 -0000 Subject: [Haiku-bugs] [Haiku] #3950: Screen preferences: Eliminate Preview monitor (easy) In-Reply-To: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> References: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> Message-ID: <053.36bc14b103b992db96f212f432e113ee@haiku-os.org> #3950: Screen preferences: Eliminate Preview monitor (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by axeld): It's not really useful now, but once we have multi monitor, we will need this (and a bit more stuff) again, so I don't think it makes much sense to remove it now. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 22:23:12 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 23 May 2009 20:23:12 -0000 Subject: [Haiku-bugs] [Haiku] #3949: Some Backgrounds enhancements (easy) In-Reply-To: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> References: <044.5461c7d9ec4a65843b8903df380c11c6@haiku-os.org> Message-ID: <053.577611c02556677ce662765f03e660a0@haiku-os.org> #3949: Some Backgrounds enhancements (easy) -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by humdinger): I can see why not doing it by default in ShowImage. If you have a slow system, you may not want to wait for the filtering when browsing through some images. As a background, that would be a one time thing after pressing "Apply", right? So filtering should be the default IMO. I'm sorry, but I have one more enhancement. :) # How about commandline parameters to set backgrounds without opening the panel? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 23 22:26:53 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 23 May 2009 20:26:53 -0000 Subject: [Haiku-bugs] [Haiku] #3950: Screen preferences: Eliminate Preview monitor (easy) In-Reply-To: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> References: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> Message-ID: <053.64df0cb796a70815ddbdad30209bc5c3@haiku-os.org> #3950: Screen preferences: Eliminate Preview monitor (easy) --------------------------------+------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by humdinger): I see. Considering that multimonitors are (by far, I guess) most of the time side by side, it would be better to have the preview above the options instead of to the left. If you agree, I'll invalidate this ticket and open a fresh one. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 00:19:57 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 23 May 2009 22:19:57 -0000 Subject: [Haiku-bugs] [Haiku] #3948: WIP [patch] add @alpha-cd to jamfiles In-Reply-To: <041.bed64698f5c66295e3b74a8566d0523f@haiku-os.org> References: <041.bed64698f5c66295e3b74a8566d0523f@haiku-os.org> Message-ID: <050.1a5f21092c3b5be20db4cdfc2b905274@haiku-os.org> #3948: WIP [patch] add @alpha-cd to jamfiles ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r30832. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 02:24:26 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 24 May 2009 00:24:26 -0000 Subject: [Haiku-bugs] [Haiku] #3942: Unable to build CD image ISO-9660 directories too deep In-Reply-To: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> References: <042.712cdc1676f6d6b3618e4fa83252b86b@haiku-os.org> Message-ID: <051.7f691a39706afec07a301b8de6f51ff6@haiku-os.org> #3942: Unable to build CD image ISO-9660 directories too deep ---------------------------+------------------------------------------------ Reporter: scottmc | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:2 scottmc]: > Could a warning be added to let us know this, such as was the case with yasm a few weeks ago? I wouldn't like that, since one only needs the tool for building a CD image, which most people probably aren't interested in. Also, genisoimage is actually a fork of an older mkisofs and spoofs mkisofs when called with "--version". > I'll try mkisofs. Any success or does it suffer from the same problem? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:47:09 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 24 May 2009 06:47:09 -0000 Subject: [Haiku-bugs] [Haiku] #3951: Add "Random" feature to Backgrounds Message-ID: <044.1d092cee8ce5de5f83f29de7e27ec476@haiku-os.org> #3951: Add "Random" feature to Backgrounds -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- The "Image" drop-down menu could offer another option: "Random by folder or query". It would open a file dialog where you choose a folder or a pre- saved query which will then serve for a randomized background image source. After choosing the folder/query, the "Image" drop-down menu will show "Random: [imagename]" and beside it a slider labeled "Interval:" where you can set: Every bootup (slider far left) and while sliding to the right increasing the interval from 1 minute to 1 month with an intelligent stepping. Cursor-left/right could be used for exact positioning of the slider. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:56:08 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 24 May 2009 06:56:08 -0000 Subject: [Haiku-bugs] [Haiku] #2824: vim: no syntax highlight In-Reply-To: <042.a27c66c9fb8c5039ac597a2eced71e58@haiku-os.org> References: <042.a27c66c9fb8c5039ac597a2eced71e58@haiku-os.org> Message-ID: <051.08198fa6ac9b7f6b39d1c33c5a6e2a9a@haiku-os.org> #2824: vim: no syntax highlight ---------------------------------------------+------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:56:19 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 24 May 2009 06:56:19 -0000 Subject: [Haiku-bugs] [Haiku] #3951: Add "Random" feature to Backgrounds In-Reply-To: <044.1d092cee8ce5de5f83f29de7e27ec476@haiku-os.org> References: <044.1d092cee8ce5de5f83f29de7e27ec476@haiku-os.org> Message-ID: <053.33761923754756a31c2ddf75303dad1f@haiku-os.org> #3951: Add "Random" feature to Backgrounds -------------------------------------+-------------------------------------- Reporter: humdinger | Owner: korli Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Preferences/Backgrounds | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by humdinger): PS:[[BR]] If the slider doesn't work so well, it really is quite a spread between minutes to months, a textbox and a drop-down for unity minutes/hours/days/weeks/months and maybe "every bootup" (here ignoring the textbox value) should do. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:57:08 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 24 May 2009 06:57:08 -0000 Subject: [Haiku-bugs] [Haiku] #3279: Vim hangs when opened during shutdown In-Reply-To: <042.a23e7b4022618edb89a79f893481b197@haiku-os.org> References: <042.a23e7b4022618edb89a79f893481b197@haiku-os.org> Message-ID: <051.1aa5fadd4d7ac9fa1f71bc184e1cd433@haiku-os.org> #3279: Vim hangs when opened during shutdown ---------------------------------------------+------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:57:46 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 24 May 2009 06:57:46 -0000 Subject: [Haiku-bugs] [Haiku] #3525: [vim] memory not freed after failing to open file In-Reply-To: <042.0069c5ad11fb3494497b8ee9d6ca96a5@haiku-os.org> References: <042.0069c5ad11fb3494497b8ee9d6ca96a5@haiku-os.org> Message-ID: <051.1687f83f4958ff0027a84e875ade3f53@haiku-os.org> #3525: [vim] memory not freed after failing to open file ---------------------------------------------+------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 08:57:55 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 24 May 2009 06:57:55 -0000 Subject: [Haiku-bugs] [Haiku] #3526: [vim] cannot reliable paste with alt+v In-Reply-To: <042.7bffe2d9464a2e8d56295d9736c7f6f6@haiku-os.org> References: <042.7bffe2d9464a2e8d56295d9736c7f6f6@haiku-os.org> Message-ID: <051.578f897467d5416a3a112fe046af09cd@haiku-os.org> #3526: [vim] cannot reliable paste with alt+v ---------------------------------------------+------------------------------ Reporter: Adek336 | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Changes (by siarzhuk): * cc: imker@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 12:25:26 2009 From: trac at haiku-os.org (alban) Date: Sun, 24 May 2009 10:25:26 -0000 Subject: [Haiku-bugs] [Haiku] #1609: NetworkStatus -> No Link In-Reply-To: <044.c3485fc46adb9faa461baf3ebe86aa0c@haiku-os.org> References: <044.c3485fc46adb9faa461baf3ebe86aa0c@haiku-os.org> Message-ID: <053.9bafa734df17367a4a7412e5f69e0719@haiku-os.org> #1609: NetworkStatus -> No Link ------------------------------+--------------------------------------------- Reporter: atomozero | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: Drivers/Network | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------------+--------------------------------------------- Changes (by alban): * status: closed => reopened * platform: All => x86 * resolution: fixed => Comment: There seems to be an issue with link status in the network status app. /dev/net/rtl8169/0 Hardware Type: Ethernet, Address: 00:21:70:29:f5:c4 inet addr: 10.10.10.61, Bcast: 10.10.10.255, Mask: 255.255.255.0 MTU: 1500, Metric: 0, up broadcast auto-configured Receive: 353 packets, 0 errors, 180486 bytes, 0 mcasts, 0 dropped Transmit: 356 packets, 0 errors, 89508 bytes, 0 mcasts, 0 dropped Collisions: 0 The link is up; the interface has an address etc; the link is working; but the network status app says that there is no link - rev 30830. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 16:04:40 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 24 May 2009 14:04:40 -0000 Subject: [Haiku-bugs] [Haiku] #3952: GCC Hybrid : System fails to provide alternative Translators Message-ID: <041.b080a3daf4be1d59ee29a023a3085512@haiku-os.org> #3952: GCC Hybrid : System fails to provide alternative Translators ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Translation Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- GCC#-hybrid builds of Haiku fail to present the alternative gcc Translator to programs that are utilizing the gcc alternative libraries. One proposed solution is to provide the gcc alternative Translators and allow libtranslation to load them respectively. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 16:11:55 2009 From: trac at haiku-os.org (mmadia) Date: Sun, 24 May 2009 14:11:55 -0000 Subject: [Haiku-bugs] [Haiku] #3953: GCC Hybrid : Cannot compile programs for alternative gcc Message-ID: <041.c4c5c8799b75a281d836b0e53fede209@haiku-os.org> #3953: GCC Hybrid : Cannot compile programs for alternative gcc -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- On a GCChybrid sysetm,a user cannot compile software for the alternative gcc. One proposed solution involves modifying the BELIBRARIES variable, /boot/develop/tools/gnupro symlink and the /boot/develop/headers/cpp symlink. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 16:38:52 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 24 May 2009 14:38:52 -0000 Subject: [Haiku-bugs] [Haiku] #3803: Random characters displayed in Terminal In-Reply-To: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> References: <040.2111ed5d304128ec16a56f287d9618fe@haiku-os.org> Message-ID: <049.09cf42a71a6fa995f0cd546eb85a3396@haiku-os.org> #3803: Random characters displayed in Terminal ---------------------------------+------------------------------------------ Reporter: haiqu | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1/alpha1 Component: Servers/app_server | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------------+------------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: Should be fixed in r30840. Please reopen if you're still able to reproduce. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 17:24:13 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 24 May 2009 15:24:13 -0000 Subject: [Haiku-bugs] [Haiku] #3952: GCC Hybrid : System fails to provide alternative Translators In-Reply-To: <041.b080a3daf4be1d59ee29a023a3085512@haiku-os.org> References: <041.b080a3daf4be1d59ee29a023a3085512@haiku-os.org> Message-ID: <050.ea5bdaaf182c92539c095040d4d7e451@haiku-os.org> #3952: GCC Hybrid : System fails to provide alternative Translators ----------------------------------+----------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Translation Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Will look into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 17:25:24 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 24 May 2009 15:25:24 -0000 Subject: [Haiku-bugs] [Haiku] #3953: GCC Hybrid : Cannot compile programs for alternative gcc In-Reply-To: <041.c4c5c8799b75a281d836b0e53fede209@haiku-os.org> References: <041.c4c5c8799b75a281d836b0e53fede209@haiku-os.org> Message-ID: <050.76f1863fb527877851c9c8b9bc465c38@haiku-os.org> #3953: GCC Hybrid : Cannot compile programs for alternative gcc -------------------------+-------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Old description: > On a GCChybrid sysetm,a user cannot compile software for the alternative > gcc. > > One proposed solution involves modifying the BELIBRARIES variable, > /boot/develop/tools/gnupro symlink and the /boot/develop/headers/cpp > symlink. New description: On a GCC hybrid system, a user cannot compile software for the alternative gcc. One proposed solution involves modifying the BELIBRARIES variable, /boot/develop/tools/gnupro symlink and the /boot/develop/headers/cpp symlink. -- Comment: Will look into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 18:51:03 2009 From: trac at haiku-os.org (idefix) Date: Sun, 24 May 2009 16:51:03 -0000 Subject: [Haiku-bugs] [Haiku] #3954: mkfs reports wrong volume as initialised Message-ID: <041.e6505b06a9b7b0e9e4bc82430911cb7e@haiku-os.org> #3954: mkfs reports wrong volume as initialised ---------------------------------------------+------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Used mkfs (on r30832) to initialise ata/1/master/1, but it reported ata/1/master/2 to be successfully initialised (giving me a heart attack ;) ): {{{ ~> mountvolume -l Volume File System Size Mounted At (Device) --------------------------------------------------------------------- Haiku Alpha Be File System 4.0G /boot (ata/0/slave/0) Partition 1 (Haiku Alpha) Be File System 7.1G (ata/1/master/0) Partition 2 (Build) Be File System 7.2G (ata/1/master/1) Partition 3 (BeOS) Be File System 7.2G (ata/1/master/2) test Be File System 7.2G (ata/1/master/3) ~> mkfs -t bfs -o noindex -v /dev/disk/ata/1/master/1 test2 Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/1 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/1 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume Partition 3 (BeOS) has been initialized successfully! ~> mountvolume -l Volume File System Size Mounted At (Device) --------------------------------------------------------------------- Haiku Alpha Be File System 4.0G /boot (ata/0/slave/0) Partition 1 (Haiku Alpha) Be File System 7.1G (ata/1/master/0) test2 Be File System 7.2G (ata/1/master/1) Partition 3 (BeOS) Be File System 7.2G (ata/1/master/2) test Be File System 7.2G (ata/1/master/3) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 19:16:29 2009 From: trac at haiku-os.org (diver) Date: Sun, 24 May 2009 17:16:29 -0000 Subject: [Haiku-bugs] [Haiku] #3955: [kernel] free(): address 0x810ffd90 already exists in page free list Message-ID: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> #3955: [kernel] free(): address 0x810ffd90 already exists in page free list --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- This is observed in vbox 2.0.2 under fedora 8[[BR]] Image were created using jam @alpha-vmware[[BR]] When I launched firefox I got KDL. See attached screenshot for backtrace. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 19:30:49 2009 From: trac at haiku-os.org (humdinger) Date: Sun, 24 May 2009 17:30:49 -0000 Subject: [Haiku-bugs] [Haiku] #3956: kernel PANIC free() when booting off a install CD Message-ID: <044.d3b674fa657895d4f57c67ad4e1a5c29@haiku-os.org> #3956: kernel PANIC free() when booting off a install CD -----------------------+---------------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- This is r30833. I burnt an install CD with "jam -q haiku-cd" of a gcc4 Haiku with additional gcc2 libs. The same build works in VirtualBox and when "@disk"ing it directly on a partition. When trying the boot CD, I KDL with the attached PANIC. Before managing to build a gcc4/2-hybrid CD image, I did a gcc4-only CD, which booted into the installer alright, but after the successful installation, it would reboot into a similar PANIC (though I don't know the details, no backtrace...) Is ticket #3955 related? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 20:06:02 2009 From: trac at haiku-os.org (diver) Date: Sun, 24 May 2009 18:06:02 -0000 Subject: [Haiku-bugs] [Haiku] #3955: [kernel] free(): address 0x810ffd90 already exists in page free list In-Reply-To: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> References: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> Message-ID: <049.f40c4c481705d9dc63ed70baa2bb666d@haiku-os.org> #3955: [kernel] free(): address 0x810ffd90 already exists in page free list --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by diver): After running MyTraceRoute http://files.tiltos.com/repos/core/mtr/1/mtr-0.75-1.i686.box ported recently by kaliber, I've got a similar crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 20:12:26 2009 From: trac at haiku-os.org (diver) Date: Sun, 24 May 2009 18:12:26 -0000 Subject: [Haiku-bugs] [Haiku] #3955: [kernel] free(): address 0x810ffd90 already exists in page free list In-Reply-To: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> References: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> Message-ID: <049.5d92f3113ed648c0019255e0d4734275@haiku-os.org> #3955: [kernel] free(): address 0x810ffd90 already exists in page free list --------------------------------------+------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by diver): I've tried to scp mtr.zip and got yet another similar crash. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 20:43:49 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 24 May 2009 18:43:49 -0000 Subject: [Haiku-bugs] [Haiku] #3956: kernel PANIC free() when booting off a install CD In-Reply-To: <044.d3b674fa657895d4f57c67ad4e1a5c29@haiku-os.org> References: <044.d3b674fa657895d4f57c67ad4e1a5c29@haiku-os.org> Message-ID: <053.425b0a3a5b1f64af5ffdb34b1c21598a@haiku-os.org> #3956: kernel PANIC free() when booting off a install CD ------------------------+--------------------------------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System | Version: R1 development Resolution: duplicate | Blockedby: 3955 Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by mmlr): * status: new => closed * resolution: => duplicate * blockedby: => 3955 Comment: Yeah, it's the same as #3955 indeed. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 21:35:59 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 24 May 2009 19:35:59 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.d09bafc893b2c1e4d3e8c71e7f302e82@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by haiqu): * status: closed => reopened * resolution: invalid => Comment: Reopened. I have just done a CD install from a Dano build of r30782 to a known good drive, then built a clean installation CD (deleting generated/objects first) and tried to boot r30790. It wouldn't boot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 22:16:40 2009 From: trac at haiku-os.org (titer) Date: Sun, 24 May 2009 20:16:40 -0000 Subject: [Haiku-bugs] [Haiku] #3957: Building on OS X fails from tools not finding libroot_build.so Message-ID: <040.0e6fad1721cd47f20ab1eb6e474a4276@haiku-os.org> #3957: Building on OS X fails from tools not finding libroot_build.so --------------------------+------------------------------------------------- Reporter: titer | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- For example: {{{ SetType1 generated/objects/haiku/x86/release/add- ons/kernel/network/protocols/unix/unix export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:generated/objects/darwin/lib generated/objects/darwin/x86/release/tools/settype -t application/x-vnd .Be-elfexecutable "generated/objects/haiku/x86/release/add- ons/kernel/network/protocols/unix/unix" ; dyld: Library not loaded: ../../../../../../generated/objects/darwin/lib/libroot_build.so Referenced from: /Volumes/Haiku/haiku/generated/objects/darwin/x86/release/tools/settype Reason: image not found ...failed SetType1 generated/objects/haiku/x86/release/add- ons/kernel/network/protocols/unix/unix ... }}} Note that the tools load fine if run from inside generated/objects/darwin/x86/release/tools/, but jam runs them from the source root directory. I am attaching a patch for build/jam/BuildSetup that sets DYLD_LIBRARY_PATH on Darwin the same way it sets LD_LIBRARY_PATH on Linux, which fixes the problem for me. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 22:24:01 2009 From: trac at haiku-os.org (titer) Date: Sun, 24 May 2009 20:24:01 -0000 Subject: [Haiku-bugs] [Haiku] #3536: select() for read hangs if run with no timeout on an AF_UNIX socket that has been shutdown and has no data remaining In-Reply-To: <044.f413407de2a263b5df50fddbac83ed6b@haiku-os.org> References: <044.f413407de2a263b5df50fddbac83ed6b@haiku-os.org> Message-ID: <053.3c438b534a66c571cbd5b23416bf4574@haiku-os.org> #3536: select() for read hangs if run with no timeout on an AF_UNIX socket that has been shutdown and has no data remaining ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by titer): I attached a patch for the unix protocol add-on. It makes UnixEndpoint::Receivable() return ENOTCONN once all data has been read, if the other end shut down the connection. The testcase passes with this change. The tcp protocol add-on seems to be working the same way, yet I am not certain this is the right way to fix it - comments are welcome. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 22:27:27 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 24 May 2009 20:27:27 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.240938cd3d48e9f65702f304cf6b6cc0@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by haiqu): Reverted to r30786 and rebuilt and the CD booted. Saved Path.cpp and Path.h then did `svn up -r30805` and reinserted Path.cpp and Path.h and rebuilt. The CD booted and installed fine. The problem is definitely in that change. Over to you, Axel. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 23:25:57 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 24 May 2009 21:25:57 -0000 Subject: [Haiku-bugs] [Haiku] #3958: libio.h unbalanced #endif Message-ID: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> #3958: libio.h unbalanced #endif -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- While trying to build freetype-2.3.9 I ran into this error: {{{ In file included from /boot/develop/headers/posix/stdio_pre.h:11, from /boot/develop/headers/posix/stdio.h:56, from /boot/develop/headers/bsd/stdio.h:9, from /boot/home/freetype-2.3.9/include/freetype/config/ftstdlib.h:99, from /boot/home/freetype-2.3.9/builds/unix/ftconfig.h:43, from /boot/home/freetype-2.3.9/src/base/ftsystem.c:29: /boot/develop/headers/posix/libio.h:222: unterminated character constant /boot/develop/headers/posix/libio.h:270: unbalanced `#endif' make: *** [/boot/home/freetype-2.3.9/objs/ftsystem.lo] Error 1 }}} Changing line 222 in libio.h to use c style comments fixes this. /* comment */ rather than //ing out the line ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 23:30:41 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 24 May 2009 21:30:41 -0000 Subject: [Haiku-bugs] [Haiku] #3958: libio.h unbalanced #endif In-Reply-To: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> References: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> Message-ID: <051.c3eef14ca3e18ba70ab06463d671877a@haiku-os.org> #3958: libio.h unbalanced #endif -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): found another comment type error, this one in:[[BR]] /boot/develop/headers/be/BeBuild.h[[BR]] lines #16 and #26 With these two files fixed I'm now able to compile freetype-2.3.9. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 24 23:31:44 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 24 May 2009 21:31:44 -0000 Subject: [Haiku-bugs] [Haiku] #3958: libio.h and BeBuild.h headers using c++ style comments (easy) (was: libio.h unbalanced #endif) In-Reply-To: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> References: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> Message-ID: <051.45694fb7faac6e942d9919ca94223a61@haiku-os.org> #3958: libio.h and BeBuild.h headers using c++ style comments (easy) -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 00:07:27 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 24 May 2009 22:07:27 -0000 Subject: [Haiku-bugs] [Haiku] #3957: Building on OS X fails from tools not finding libroot_build.so In-Reply-To: <040.0e6fad1721cd47f20ab1eb6e474a4276@haiku-os.org> References: <040.0e6fad1721cd47f20ab1eb6e474a4276@haiku-os.org> Message-ID: <049.52c9304d1280c8f331f79f76a806f6b6@haiku-os.org> #3957: Building on OS X fails from tools not finding libroot_build.so ---------------------------+------------------------------------------------ Reporter: titer | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r30845. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 00:13:35 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 24 May 2009 22:13:35 -0000 Subject: [Haiku-bugs] [Haiku] #3536: select() for read hangs if run with no timeout on an AF_UNIX socket that has been shutdown and has no data remaining In-Reply-To: <044.f413407de2a263b5df50fddbac83ed6b@haiku-os.org> References: <044.f413407de2a263b5df50fddbac83ed6b@haiku-os.org> Message-ID: <053.427ffecb3dd479e7fc7333f755d9580d@haiku-os.org> #3536: select() for read hangs if run with no timeout on an AF_UNIX socket that has been shutdown and has no data remaining ----------------------------+----------------------------------------------- Reporter: anevilyak | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r30846. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 01:02:03 2009 From: trac at haiku-os.org (scottmc) Date: Sun, 24 May 2009 23:02:03 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.0d273151dba3785d19ddbdb5052dcf43@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Changes (by scottmc): * cc: haiku@? (added) Comment: Not sure what's up with this as I thought I built this the same as all the others I've done. Try applying the attached patch and see if the newer zip file is any different. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 01:13:05 2009 From: trac at haiku-os.org (mmlr) Date: Sun, 24 May 2009 23:13:05 -0000 Subject: [Haiku-bugs] [Haiku] #3955: [kernel] free(): address 0x810ffd90 already exists in page free list In-Reply-To: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> References: <040.b23324f970ba9a52e76be702b058c929@haiku-os.org> Message-ID: <049.18f4950902123711c8b8fd50c5a9f915@haiku-os.org> #3955: [kernel] free(): address 0x810ffd90 already exists in page free list ---------------------------------------+------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet/Stack | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: 3956 ---------------------------------------+------------------------------------ Changes (by mmlr): * status: new => closed * resolution: => fixed Comment: The double free should be fixed in r30848. The question why loading fails is still open. If it proves to be a further problem please create a bug report for that as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 01:14:35 2009 From: trac at haiku-os.org (luroh) Date: Sun, 24 May 2009 23:14:35 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.da5148e83602c3570c36c75ea40bad8b@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): Nope, sorry. The problem still seems to be wrong permissions of the folder generated/tmp/unzip/common/share/doc/p7zip/DOCS and the files inside it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 01:59:06 2009 From: trac at haiku-os.org (luroh) Date: Sun, 24 May 2009 23:59:06 -0000 Subject: [Haiku-bugs] [Haiku] #3947: Optional Package: p7zip - archive seems to contain wrong permissions In-Reply-To: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> References: <040.385b95fa3ba3ffb0408c9fa960511760@haiku-os.org> Message-ID: <049.ebb35ecac644b7cad20c8fc77678e9db@haiku-os.org> #3947: Optional Package: p7zip - archive seems to contain wrong permissions -----------------------+---------------------------------------------------- Reporter: rossi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): yep, that one did the trick :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 02:50:02 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 25 May 2009 00:50:02 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.e4af536d8e824d70fb0850312ac18ac6@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by scottmc): I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick. http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 03:26:40 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 25 May 2009 01:26:40 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.523af66c3ccddb98a65e488c733829fe@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by bonefish): Replying to [comment:6 scottmc]: > I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick. > http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1 Maybe that's different for freetype, but usually "--libdir" specifies the installation directory for libraries. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 05:16:58 2009 From: trac at haiku-os.org (haiqu) Date: Mon, 25 May 2009 03:16:58 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 Message-ID: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> #3960: BeIDE crashes on entry at r30849 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- {{{ [tcsetpgrp failed in terminal_inferior: Invalid Argument] Thread 38713 caused an exception: Segment violation Reading symbols from /boot/system/runtime_loader...done. Loaded symbols for /boot/system/runtime_loader Reading symbols from /boot/system/lib/libtracker.so...done. Loaded symbols for /boot/system/lib/libtracker.so Reading symbols from /boot/system/lib/libmedia.so...done. Loaded symbols for /boot/system/lib/libmedia.so Reading symbols from /boot/system/lib/libbe.so...done. Loaded symbols for /boot/system/lib/libbe.so Reading symbols from /boot/system/lib/libroot.so...done. Loaded symbols for /boot/system/lib/libroot.so Reading symbols from /boot/system/lib/libnetwork.so...done. Loaded symbols for /boot/system/lib/libnetwork.so Reading symbols from /boot/system/lib/libtranslation.so...done. Loaded symbols for /boot/system/lib/libtranslation.so Reading symbols from /boot/system/lib/libstdc++.r4.so...done. Loaded symbols for /boot/system/lib/libstdc++.r4.so Reading symbols from /boot/system/lib/libtextencoding.so...done. Loaded symbols for /boot/system/lib/libtextencoding.so Reading symbols from /boot/system/lib/libiconv.so...done. Loaded symbols for /boot/system/lib/libiconv.so Reading symbols from /boot/develop/BeIDE/plugins/Prefs_add_ons/MWBResPlugin...done. Loaded symbols for /boot/develop/BeIDE/plugins/Prefs_add_ons/MWBResPlugin Reading symbols from /boot/develop/BeIDE/plugins/Prefs_add_ons/ShellPlugin...done. Loaded symbols for /boot/develop/BeIDE/plugins/Prefs_add_ons/ShellPlugin Reading symbols from /boot/develop/BeIDE/plugins/Prefs_add_ons/gccPlugin...done. Loaded symbols for /boot/develop/BeIDE/plugins/Prefs_add_ons/gccPlugin Reading symbols from /boot/develop/BeIDE/plugins/Editor_add_ons/Commenter...done. Loaded symbols for /boot/develop/BeIDE/plugins/Editor_add_ons/Commenter [tcsetpgrp failed in terminal_inferior: Invalid Argument] [Switching to team /boot/develop/BeIDE/BeIDE (38713) thread BeIDE (38713)] 0x007b2cda in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so (gdb) bt #0 0x007b2cda in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #1 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #2 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #3 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #4 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #5 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #6 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #7 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #8 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #9 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #10 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #11 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #12 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #13 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #14 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #15 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #16 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #17 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #18 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #19 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #20 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #21 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #22 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so #23 0x007b2cdc in BStatable::_OhSoStatable1 () from /boot/system/lib/libbe.so ---Type to continue, or q to quit---q Quit (gdb) }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 09:14:06 2009 From: trac at haiku-os.org (korli) Date: Mon, 25 May 2009 07:14:06 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.003797d7cfdd22dca59899c0b3a3562a@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by korli): Replying to [comment:6 scottmc]: > I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick. > http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1 bonefish is right, you might try using --includedir=/boot/develop/headers/3rdparty instead. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 09:42:52 2009 From: trac at haiku-os.org (korli) Date: Mon, 25 May 2009 07:42:52 -0000 Subject: [Haiku-bugs] [Haiku] #3954: mkfs reports wrong volume as initialised In-Reply-To: <041.e6505b06a9b7b0e9e4bc82430911cb7e@haiku-os.org> References: <041.e6505b06a9b7b0e9e4bc82430911cb7e@haiku-os.org> Message-ID: <050.167775b1258bacc3929d5cc762bec8cc@haiku-os.org> #3954: mkfs reports wrong volume as initialised ---------------------------------------------+------------------------------ Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by korli): This one is very funny indeed ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 11:54:39 2009 From: trac at haiku-os.org (zooey) Date: Mon, 25 May 2009 09:54:39 -0000 Subject: [Haiku-bugs] [Haiku] #3013: Bad date in Beam In-Reply-To: <041.d9e957876e9635375b30cfa384e87e00@haiku-os.org> References: <041.d9e957876e9635375b30cfa384e87e00@haiku-os.org> Message-ID: <050.4e7bec1e4f5961241cd920ba4882d588@haiku-os.org> #3013: Bad date in Beam --------------------------+------------------------------------------------- Reporter: miqlas | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by zooey): * owner: axeld => zooey * status: new => assigned Comment: The underlying problem is that haiku's parsedate() function does not handle timezones other than GMT, which Beam relied upon. Beam has been changed to circumvent this problem, but parsedate() needs to be improved, too. I leave this bug open to remind me that I should improve parsedate() to cope with timezones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 13:43:14 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 25 May 2009 11:43:14 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 In-Reply-To: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> References: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> Message-ID: <049.1b1b1b286a718027a448159cfdef00c0@haiku-os.org> #3960: BeIDE crashes on entry at r30849 ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by bonefish): * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 12:48:11 2009 From: trac at haiku-os.org (korli) Date: Mon, 25 May 2009 10:48:11 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 In-Reply-To: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> References: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> Message-ID: <049.a50d15ee67bec3ac397536ffd4d174d2@haiku-os.org> #3960: BeIDE crashes on entry at r30849 ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by korli): * owner: axeld => bonefish * component: Applications => Kits/Storage Kit Comment: It seems related to r30830. Assigning to Ingo for a check. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 16:41:26 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 25 May 2009 14:41:26 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 In-Reply-To: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> References: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> Message-ID: <049.d2b38dedae5e00b843633d52d2dc04b0@haiku-os.org> #3960: BeIDE crashes on entry at r30849 ------------------------------+--------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by bonefish): Fixed in r30851. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 16:41:56 2009 From: trac at haiku-os.org (bonefish) Date: Mon, 25 May 2009 14:41:56 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 In-Reply-To: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> References: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> Message-ID: <049.ccc9a9e5ffdeeecfb54f83d1f0a21df6@haiku-os.org> #3960: BeIDE crashes on entry at r30849 -------------------------------+-------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 20:11:16 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 25 May 2009 18:11:16 -0000 Subject: [Haiku-bugs] [Haiku] #3961: vm_page_fault on less -f /dev/acpi/namespace exit Message-ID: <051.2fd0bec6a6399d1ff9dc47d48272a477@haiku-os.org> #3961: vm_page_fault on less -f /dev/acpi/namespace exit ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Just hit 'q' and it gets us to KDL. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 20:14:05 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 25 May 2009 18:14:05 -0000 Subject: [Haiku-bugs] [Haiku] #3961: vm_page_fault on less -f /dev/acpi/namespace exit In-Reply-To: <051.2fd0bec6a6399d1ff9dc47d48272a477@haiku-os.org> References: <051.2fd0bec6a6399d1ff9dc47d48272a477@haiku-os.org> Message-ID: <060.9ece602b021767c8b4b30a118e1ad6d4@haiku-os.org> #3961: vm_page_fault on less -f /dev/acpi/namespace exit ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): forgot: r30851; gcc4; ata-bm; acpi -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 20:26:46 2009 From: trac at haiku-os.org (axeld) Date: Mon, 25 May 2009 18:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #3950: Screen preferences: Eliminate Preview monitor (easy) In-Reply-To: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> References: <044.8ff5699faf8ff415aff09355d262d9eb@haiku-os.org> Message-ID: <053.051c8a47ab4c972f3f2faee8761e241c@haiku-os.org> #3950: Screen preferences: Eliminate Preview monitor (easy) ---------------------------------+------------------------------------------ Reporter: humdinger | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Screen | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by axeld): * status: new => closed * resolution: => invalid Comment: It will be worked on anyway, once the time has come. I don't think there is a need for another ticket. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 21:38:05 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 25 May 2009 19:38:05 -0000 Subject: [Haiku-bugs] [Haiku] #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount Message-ID: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- r30851; gcc4; ata-bm; acpi KDL triggered on unmount of usb-attached digital camera. (ro or rw doesn't matter) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 21:48:19 2009 From: trac at haiku-os.org (idefix) Date: Mon, 25 May 2009 19:48:19 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS Message-ID: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS ------------------------------+--------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- An volume initialised under Haiku (r30847) with mkfs or DriveSetup has block allocation mismatches according to chkbfs under BeOS. The repaired volume will crash Haiku when trying to mount it. Steps to reproduce: - Initialise (and check) a volume with Haiku: {{{ ~> mkfs -t bfs -v /dev/disk/ata/1/master/0 test0mkfs Preparing for modifications... Parameters Validation... About to initialize /dev/disk/ata/1/master/0 with Be File System Are you sure you want to do this now? ALL YOUR DATA in /dev/disk/ata/1/master/0 will be lost forever. Continue (yes|[no])? yes DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate15UninitializeJob DiskDeviceJobQueue::Execute(): executing job: Q28BPrivate13InitializeJob Volume Partition 4 (test3) has been initialized successfully! ~> checkfs /test0mkfs/ checked 9 nodes, 0 blocks not allocated, 0 blocks already set, 0 blocks could be freed files 0 directories 5 attributes 0 attr. dirs 0 indices 4 }}} - Check the volume with BeOS: {{{ $ chkbfs /test0mkfs/ bfs: /dev/disk/ide/ata/1/master/0/0_0 is read-only! Files processed: 11 BFS has 3 blocks allocated that should not be. Block allocation mismatches detected. Fixing. File system check completed. }}} - Mount the volume with Haiku: {{{ bfs: mounted "test0mkfs" (root node at 524288, device = /dev/disk/ata/1/master/0) bfs: bfs_stat_index:2020: No such file or directory bfs: AllocationBlock::Allocate(): some blocks are already allocated, start = 0, numBlocks = 4297 PANIC: blocks already set! Welcome to Kernel Debugging Land... Thread 173 "bfs block allocator" running on CPU 0 kdebug> bt stack trace for thread 173 "bfs block allocator" kernel stack: 0x80dda000 to 0x80dde000 frame caller :function + offset 0 80dddba8 (+ 48) 80062e5d :invoke_debugger_command + 0x00f5 1 80dddbd8 (+ 64) 80062c4d invoke_pipe_segment(debugger_command_pipe*: 0x80132380, int32: 0, 0x0 "") + 0x0079 2 80dddc18 (+ 64) 80062fd4 :invoke_debugger_command_pipe + 0x009c 3 80dddc58 (+ 48) 80064584 ExpressionParser<0x80dddd0c>::_ParseCommandPipe(0x80dddd08) + 0x0234 4 80dddc88 (+ 64) 800639be ExpressionParser<0x80dddd0c>::EvaluateCommand(0x80122c00 "bt", 0x80dddd08) + 0x02ba 5 80dddcc8 (+ 224) 800659ac :evaluate_debug_command + 0x0088 6 80dddda8 (+ 64) 80060cd6 kernel_debugger_loop() + 0x01ae 7 80dddde8 (+ 32) 80061bdd :kernel_debugger + 0x004d 8 80ddde08 (+ 192) 80061b85 :panic + 0x0029 9 80dddec8 (+ 96) 805c47ee AllocationGroup<0x82d2f800>::Allocate(Transaction&: 0x80dddfcc, uint16: 0x0 (0), int32: 4329) + 0x02b6 10 80dddf28 (+ 176) 805c5240 BlockAllocator<0x811c87d4>::_Initialize(BlockAllocator*: NULL) + 0x032c 11 80dddfd8 (+ 32) 80057007 _create_kernel_thread_kentry() + 0x001b 12 80dddff8 (+2132942856) 80056fa4 thread_kthread_exit() + 0x0000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 21:57:57 2009 From: trac at haiku-os.org (idefix) Date: Mon, 25 May 2009 19:57:57 -0000 Subject: [Haiku-bugs] [Haiku] #3963: Haiku wrongly initialises volume according to BeOS In-Reply-To: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> References: <041.b3a696bc8f0c7a0861a67b2a14a59895@haiku-os.org> Message-ID: <050.f21fc1bdc0491019a1d0e9a5e3696d77@haiku-os.org> #3963: Haiku wrongly initialises volume according to BeOS ------------------------------+--------------------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by idefix): Above crashlog happens when mounting the volume read/write. When mounting the volume read-only, the crash is the same as bug #3432. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 22:28:54 2009 From: trac at haiku-os.org (luroh) Date: Mon, 25 May 2009 20:28:54 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a Message-ID: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Happened when trying to unmount a FAT32 formatted 256MB USB stick via Tracker (right-click -> unmount).[[BR]] Rev 30852, gcc2, vmware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 23:09:07 2009 From: trac at haiku-os.org (michael.weirauch) Date: Mon, 25 May 2009 21:09:07 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a In-Reply-To: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> References: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> Message-ID: <049.96ff6564a5c021564a563eb2f8919290@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by michael.weirauch): Dup of #3962? Your backtrace looks more beautiful, though ;) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 23:24:04 2009 From: trac at haiku-os.org (axeld) Date: Mon, 25 May 2009 21:24:04 -0000 Subject: [Haiku-bugs] [Haiku] #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount In-Reply-To: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> References: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> Message-ID: <060.bac847cd788e3909c13027a725816d4b@haiku-os.org> #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * component: System => System/Kernel Comment: When you attach images, please always give them the proper extension, or they aren't directly viewable over the web browser. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Mon May 25 23:30:42 2009 From: trac at haiku-os.org (zooey) Date: Mon, 25 May 2009 21:30:42 -0000 Subject: [Haiku-bugs] [Haiku] #3481: libio.h troubles on gcc4 Haiku In-Reply-To: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> References: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> Message-ID: <051.f0b217dab2c6b100870731aa8d60de22@haiku-os.org> #3481: libio.h troubles on gcc4 Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by zooey): Extracted kaliber's suggested patch from TiltOS and attached it here, as libio.patch. The resulting libio.h at least allows to compile rsync on gcc4, which failed before, too. The patch requires testing with gcc2, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 00:40:32 2009 From: trac at haiku-os.org (mmadia) Date: Mon, 25 May 2009 22:40:32 -0000 Subject: [Haiku-bugs] [Haiku] #3965: reversed behavior for (un)mounted volumes Message-ID: <041.1f61470f2a8f1e568f6e8116f3c1b5b4@haiku-os.org> #3965: reversed behavior for (un)mounted volumes -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- rev30841 The Partition menu seems to have reversed behavior for most partitions. eg, Mount and Initialize are available on currently mounted BFS partitions. The reverse for unmounted. See attached images for visuals. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 00:58:00 2009 From: trac at haiku-os.org (luroh) Date: Mon, 25 May 2009 22:58:00 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a In-Reply-To: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> References: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> Message-ID: <049.f1f09c3e7159daebeb0127acfb023d9f@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): Correction: this KDL was encountered running Haiku on real hw, not in VMware.[[BR]] [[BR]] michael.weirauch: It does indeed look very similar from what I can tell. Well spotted in any case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 01:13:15 2009 From: trac at haiku-os.org (scottmc) Date: Mon, 25 May 2009 23:13:15 -0000 Subject: [Haiku-bugs] [Haiku] #3958: libio.h and BeBuild.h headers using c++ style comments (easy) In-Reply-To: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> References: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> Message-ID: <051.db85feba64a52d1866d1d39e12064596@haiku-os.org> #3958: libio.h and BeBuild.h headers using c++ style comments (easy) -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by scottmc): I've attached a patch that'll fix BeBuild.h up. For the libio.h fix, it would be covered by the patch attached to ticket #3481 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 03:07:26 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 26 May 2009 01:07:26 -0000 Subject: [Haiku-bugs] [Haiku] #3952: GCC Hybrid : System fails to provide alternative Translators In-Reply-To: <041.b080a3daf4be1d59ee29a023a3085512@haiku-os.org> References: <041.b080a3daf4be1d59ee29a023a3085512@haiku-os.org> Message-ID: <050.4b2fbcbfeccedd03b2f9421f16ba4501@haiku-os.org> #3952: GCC Hybrid : System fails to provide alternative Translators -----------------------------------+---------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Translation Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -----------------------------------+---------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30860. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 03:24:38 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 26 May 2009 01:24:38 -0000 Subject: [Haiku-bugs] [Haiku] #3481: libio.h troubles on gcc4 Haiku In-Reply-To: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> References: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> Message-ID: <051.aa7ab6df2f0e2b3b9b6aabed816365b8@haiku-os.org> #3481: libio.h troubles on gcc4 Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Comment(by scottmc): patch seems to work on gcc2 as well, at least I was able to build expat cvs head with the patched libio.h in place. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 02:30:35 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 26 May 2009 00:30:35 -0000 Subject: [Haiku-bugs] [Haiku] #3960: BeIDE crashes on entry at r30849 In-Reply-To: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> References: <040.d295137578393f82c4d711170a755dbd@haiku-os.org> Message-ID: <049.8e8f77345ed4093b30b7b5e4145500d6@haiku-os.org> #3960: BeIDE crashes on entry at r30849 -------------------------------+-------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Storage Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: -------------------------------+-------------------------------------------- Comment(by haiqu): Hey bonefish, thanks for the quick fix. ;-) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 02:32:32 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 26 May 2009 00:32:32 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.8add61926d685f9e262174a6e84a5291@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by haiqu): BTW it may be relevant that I'm still using the IDE bus manager, not the ATA manager. My hard drives are all SATA on this newer machine too. Hope that sheds some light on the issue. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 02:28:57 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 26 May 2009 00:28:57 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 Message-ID: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- At r30825 FPC works fine and can rebuild itself. By r30830 I get this: {{{ make[7]: Entering directory `/boot/home/projects/fpc/rtl/haiku' as -o /boot/home/projects/fpc/rtl/units/i386-haiku/prt0.o i386/prt0.as as -o /boot/home/projects/fpc/rtl/units/i386-haiku/cprt0.o i386/cprt0.as as -o /boot/home/projects/fpc/rtl/units/i386-haiku/func.o i386/func.as as -o /boot/home/projects/fpc/rtl/units/i386-haiku/dllprt.o i386/dllprt.as /boot/home/projects/fpc/compiler/ppc1 -Ur -dHASUNIX -n -dFPC_USE_LIBC -Si -Ur -Xs -O2 -n -Fi../inc -Fi../i386 -Fi../unix -Fii386 -FE. -FU/boot/home/projects/fpc/rtl/units/i386-haiku -di386 -dRELEASE -Us -Sg system.pp Fatal: Compilation aborted An unhandled exception occurred at $4A16F43A : EAccessViolation : Access violation $4A16F43A }}} I'm investigating it myself, since current developers probably don't use this compiler. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 07:09:10 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 26 May 2009 05:09:10 -0000 Subject: [Haiku-bugs] [Haiku] #3967: ftp cli app doesn't always list files when you use the ls command Message-ID: <042.246106c2b626351187fa8806ef7f1c6a@haiku-os.org> #3967: ftp cli app doesn't always list files when you use the ls command ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ The ftp command line app seems to have issues not showing the full output when you use the ls command. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 07:18:13 2009 From: trac at haiku-os.org (michael.weirauch) Date: Tue, 26 May 2009 05:18:13 -0000 Subject: [Haiku-bugs] [Haiku] #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount In-Reply-To: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> References: <051.7227335ff717b1b66f161b90c706409a@haiku-os.org> Message-ID: <060.f4691c75c7a06babdbaa3eaf383a02bc@haiku-os.org> #3962: vm_page_fault in media checker thread on usb-attached digital camera unmount ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): Yap, sorry for this. Didn't find a way to change that later on, nor a way to rename the attachment, or delete and re-attach. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 07:23:09 2009 From: trac at haiku-os.org (haiqu) Date: Tue, 26 May 2009 05:23:09 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 Message-ID: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> #3968: Can't install from CD at r30851 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Gets to the rocketship icon and locks up. This is not the same fault reported in #3940, I already patched that fault. Tested on two machines. Install works at r30849 so that should help narrow the problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 07:35:03 2009 From: trac at haiku-os.org (agildehaus) Date: Tue, 26 May 2009 05:35:03 -0000 Subject: [Haiku-bugs] [Haiku] #3969: Changing items on Audio Mixer Setup switches tabs unexpectedly Message-ID: <045.2e1c3456014f77fb9e6a83bb4876d9ce@haiku-os.org> #3969: Changing items on Audio Mixer Setup switches tabs unexpectedly -------------------------------+-------------------------------------------- Reporter: agildehaus | Owner: anevilyak Type: bug | Status: new Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- In the Audio Mixer settings in Media Preferences: 1. Navigate to the Setup tab. 2. Check "Use non linear gain sliders (like BeOS R5). Alternatively, change the value in the drop down box for "Input gain controls represent". Result: The tab will change from Setup back to the Gain Controls. This is unexpected behavior and has no reason to occur. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 10:47:17 2009 From: trac at haiku-os.org (korli) Date: Tue, 26 May 2009 08:47:17 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 In-Reply-To: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> References: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> Message-ID: <049.8cd0b407f1dca2a71a764f0178d1a20e@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Changes (by korli): * cc: oco (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 12:00:35 2009 From: trac at haiku-os.org (darkwyrm) Date: Tue, 26 May 2009 10:00:35 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.e932ae5f8a9b63bb254a61462828cd6f@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by darkwyrm): I can confirm that this still happens as of r30852 in the gcc2 build and can consistently reproduce the trip to KDL by compiling a project with a build of Paladin compiled from within Haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 12:02:31 2009 From: trac at haiku-os.org (darkwyrm) Date: Tue, 26 May 2009 10:02:31 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.694e5dee3110acc3dc4a1bc94f4a4191@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by darkwyrm): Replying to [comment:17 darkwyrm]: > I can confirm that this still happens as of r30852 in the gcc2 build and can consistently reproduce the trip to KDL by compiling a project with a build of Paladin compiled from within Haiku. I forgot -- I'm running this on real hardware and not in a VM. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 12:51:29 2009 From: trac at haiku-os.org (korli) Date: Tue, 26 May 2009 10:51:29 -0000 Subject: [Haiku-bugs] [Haiku] #3969: Changing items on Audio Mixer Setup switches tabs unexpectedly In-Reply-To: <045.2e1c3456014f77fb9e6a83bb4876d9ce@haiku-os.org> References: <045.2e1c3456014f77fb9e6a83bb4876d9ce@haiku-os.org> Message-ID: <054.cb005a29088cefd7c49fee5a33e24726@haiku-os.org> #3969: Changing items on Audio Mixer Setup switches tabs unexpectedly --------------------------------+------------------------------------------- Reporter: agildehaus | Owner: anevilyak Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Preferences/Media | Version: R1 development Resolution: duplicate | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => duplicate Comment: Dup of #1876 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 13:23:48 2009 From: trac at haiku-os.org (zooey) Date: Tue, 26 May 2009 11:23:48 -0000 Subject: [Haiku-bugs] [Haiku] #3481: libio.h troubles on gcc4 Haiku In-Reply-To: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> References: <042.eec677fed0860be96a4b2985e8fc865b@haiku-os.org> Message-ID: <051.241ef681a6468656f87243780e99043f@haiku-os.org> #3481: libio.h troubles on gcc4 Haiku ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by zooey): * status: reopened => closed * resolution: => fixed Comment: Fixed in r30861 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 14:25:04 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 26 May 2009 12:25:04 -0000 Subject: [Haiku-bugs] [Haiku] #3958: libio.h and BeBuild.h headers using c++ style comments (easy) In-Reply-To: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> References: <042.8d4bc194126f29f47fcecd2cd66ccdf6@haiku-os.org> Message-ID: <051.f39716a99602c4e462370a18692605be@haiku-os.org> #3958: libio.h and BeBuild.h headers using c++ style comments (easy) ------------------------+--------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ------------------------+--------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks, applied in r30863. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 14:30:57 2009 From: trac at haiku-os.org (bonefish) Date: Tue, 26 May 2009 12:30:57 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.22675181552eafa0de9088192c042ce4@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:17 darkwyrm]: > I can confirm that this still happens as of r30852 in the gcc2 build and can consistently reproduce the trip to KDL by compiling a project with a build of Paladin compiled from within Haiku. Great! Can you give detailed instructions how to reproduce it, including all the necessary files, please. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 14:43:36 2009 From: trac at haiku-os.org (darkwyrm) Date: Tue, 26 May 2009 12:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #3970: B[Outline]ListView Redraw problems Message-ID: <043.8b4ab454bc025db240754e43ff4e2404@haiku-os.org> #3970: B[Outline]ListView Redraw problems --------------------------------+------------------------------------------- Reporter: darkwyrm | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- There seems to be a problem with either BListView or BOutlineListView redraw when using BListView::InvalidateItem. It can be reproduced simply by running Paladin and compiling a project. As files are compiled, they should be lighting up in blue, but as of r30852, they are not. This has been a problem for quite a while, but I just now got around to filing the report. Clicking on Force Rebuild from the Build menu should cause all visible items in the project to be redrawn in a light gray color, and this doesn't happen either. In both instances, the code in Paladin is iterating over the items and calling InvalidateItem(). This issue does not occur in R5 or Zeta. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 17:10:35 2009 From: trac at haiku-os.org (scottmc) Date: Tue, 26 May 2009 15:10:35 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.b25ac611ba82930a2f006167000d5188@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): Attached patch new OptionalPackages: Libiconv, Neon, Python, SQLite[[BR]] And updated packages for: OpenSSH, Apr, Apr-Util, Subversion and P7Zip. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 18:31:38 2009 From: trac at haiku-os.org (franxico) Date: Tue, 26 May 2009 16:31:38 -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.09e4f6526d756b52494d70f92b87288b@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 Blockedby: | Platform: All Blocking: 3573, 3936 | ----------------------------------+----------------------------------------- Comment(by franxico): In my case I can't boot at all since Haiku doesn't like my USB wireless Logitech mouse+keyboard. IMHO, this bug is a critical one. What can I do to avoid this for the time being? My Vostro 410 doesn't have a PS/2 port and USB parameters in BIOS are very limited. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 19:02:33 2009 From: trac at haiku-os.org (stippi) Date: Tue, 26 May 2009 17:02:33 -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.58e2ca21e62083b0270f74074190358f@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 Blockedby: | Platform: All Blocking: 3573, 3936 | ----------------------------------+----------------------------------------- Comment(by stippi): Interesting. I also have a composite device which prevents Haiku from booting if attached. It's a Cherry Wireless keyboard/mouse combo ("Baracuda"?). I though it was just a pecularity and didn't give it much thought, since I don't usually need it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 21:14:07 2009 From: trac at haiku-os.org (Stef) Date: Tue, 26 May 2009 19:14:07 -0000 Subject: [Haiku-bugs] [Haiku] #3971: Patch: enable mixed mouse+keyboard input in Sudoku Message-ID: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> #3971: Patch: enable mixed mouse+keyboard input in Sudoku ---------------------------------+------------------------------------------ Reporter: Stef | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------+------------------------------------------ Currently, Sudoku supports either mouse input (point at cell, click to insert numbers) or keyboard input (arrow keys select cell, type numbers to insert them). When attempting to combine the two (point to select cells, type a number to insert it) weird things happen. The first keypress selects the cell under the mouse cursor (blue outline). The second keypress inserts the number in this cell. However, when forcing a repaint (drag the window off the screen and back), it can be seen that the first keypress inserts the number at the previous keyboard position without updating the screen. The attached patch does not address the repaint issue directly. Instead, it always sets the keyboard input position to the mouse input position (if valid). Not only does this solve this issue, it also enables mixed input as described above (point and type). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 21:22:29 2009 From: trac at haiku-os.org (HaikuBot) Date: Tue, 26 May 2009 19:22:29 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.f6bcb549e325241b457d6362e0e1492c@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Hello. Sorry for long respond. I tested Haiku with acceleration and without (with DVI only and VGA only cables), it works fine. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 21:51:02 2009 From: trac at haiku-os.org (oco) Date: Tue, 26 May 2009 19:51:02 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 In-Reply-To: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> References: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> Message-ID: <049.c55b797e0813ebfb9864ab2db7e6b1ec@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by oco): It work fine here but i am still at r30782. Also, i have some freepascal patchs here (there was some change about signal handling recently). I still have to submit them, but i am quite busy in the upcoming weeks. I am currently updating one of my haiku's partitions to test with latest Haiku revision. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 22:02:45 2009 From: trac at haiku-os.org (zooey) Date: Tue, 26 May 2009 20:02:45 -0000 Subject: [Haiku-bugs] [Haiku] #3013: Bad date in Beam In-Reply-To: <041.d9e957876e9635375b30cfa384e87e00@haiku-os.org> References: <041.d9e957876e9635375b30cfa384e87e00@haiku-os.org> Message-ID: <050.6419810561ce912ca9a6ef69b518f3e2@haiku-os.org> #3013: Bad date in Beam ---------------------------+------------------------------------------------ Reporter: miqlas | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Since r39864, parsedate() can cope with numerical and 3-letter timezones. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 22:39:20 2009 From: trac at haiku-os.org (korli) Date: Tue, 26 May 2009 20:39:20 -0000 Subject: [Haiku-bugs] [Haiku] #1542: [GLDirectMode] Crashes when resized to mininial dimension In-Reply-To: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> References: <041.1adf8a143c78face056657df69c05a58@haiku-os.org> Message-ID: <050.90b002b21b361e172156891db5d58652@haiku-os.org> #1542: [GLDirectMode] Crashes when resized to mininial dimension ---------------------------+------------------------------------------------ Reporter: hauser | Owner: phoudoin Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed Comment: Seems OK. I added a check in r30869 in the Mesa software renderer. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 23:39:25 2009 From: trac at haiku-os.org (korli) Date: Tue, 26 May 2009 21:39:25 -0000 Subject: [Haiku-bugs] [Haiku] #1896: libroot: free bug (was: /bin/bc crash) In-Reply-To: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> References: <040.da90fc9f8a86a95338db1a65efec1ae9@haiku-os.org> Message-ID: <049.7931cd627aea91351f7a771366efcdc0@haiku-os.org> #1896: libroot: free bug (was: /bin/bc crash) --------------------------------+------------------------------------------- Reporter: thorn | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r30871. Make doesn't care to regenerate bc.c and scan.c, so we do the same. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 23:52:53 2009 From: trac at haiku-os.org (mmlr) Date: Tue, 26 May 2009 21:52:53 -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.644f922929a8170b8166ae5c8dfd1fd0@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 Blockedby: | Platform: All Blocking: 3573, 3936 | ----------------------------------+----------------------------------------- Comment(by mmlr): In what way exactly do those devices prevent booting? Like an interrupt storm on controller initialization that freezes the boot process or more like a crash or panic? In any case, please create a new bug report and attach details to it. A screenshot of the last page of on-screen debug output for example. This enhancement ticket is really only about adding support for generic hid devices to usb_hid. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Tue May 26 23:54:20 2009 From: trac at haiku-os.org (luroh) Date: Tue, 26 May 2009 21:54:20 -0000 Subject: [Haiku-bugs] [Haiku] #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 In-Reply-To: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> References: <047.44f9884037bae402bb9ed1c5501bbaa1@haiku-os.org> Message-ID: <056.4b69a115a3099f8e4c1462aa3c7b8203@haiku-os.org> #1966: Panic:vm_page_fault:unhandled page fault in kernel space at 0x0, ip 0x800gcdd7 ---------------------------+------------------------------------------------ Reporter: skarmiglione | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: x64 Blocking: | ---------------------------+------------------------------------------------ Comment(by luroh): skarmiglione: is this ticket still valid, would you say? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 00:10:28 2009 From: trac at haiku-os.org (oco) Date: Tue, 26 May 2009 22:10:28 -0000 Subject: [Haiku-bugs] [Haiku] #3966: Free Pascal Compiler throwing exception at r30830 In-Reply-To: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> References: <040.02036042b038537aa308e8e9f7638df3@haiku-os.org> Message-ID: <049.d6f6cb745c76bac429b3aaf1c8015514@haiku-os.org> #3966: Free Pascal Compiler throwing exception at r30830 -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by oco): I was able to reproduce the problem with r30868. The generated exe is probably calling the wrong *stat functions and/or without the right stat struct (record). I was not able to fix it yet. I will probably look at this next weekend if you do not fix it before ;-). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 00:46:52 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 26 May 2009 22:46:52 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.afb99d612487fde9838b4f10396b1fc3@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Changes (by marcusoverhagen): * cc: marcusoverhagen (added) Comment: Please provide a dump of the partition table. Either with dd, or screenshot from DiskProbe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 00:51:50 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Tue, 26 May 2009 22:51:50 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 In-Reply-To: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> References: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> Message-ID: <049.5c293d02fdad85f46ca3170c13f88c23@haiku-os.org> #3968: Can't install from CD at r30851 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Changes (by marcusoverhagen): * cc: marcusoverhagen (added) Comment: Does reverting the r30851 changes fix it? Does removing the firewire driver fix it? Does pressing F12 drop to KDL? please provide bt. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 00:52:42 2009 From: trac at haiku-os.org (michael.weirauch) Date: Tue, 26 May 2009 22:52:42 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.d6a19e8c90926372021eb0c131237715@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): I just went on testing with r30868; gcc4; ata-bm; acpi; on the second sata disk with an installation and work partition and could reproduce the occassional UI freeze during I/O and total freeze after building the Haiku tree. But I never dared to test the old ide-bm after Marcus' changes (some or all related for me: r30443; r30454; r30475), which - if I got things right - have also been applied to the ide-bm & co after the separation of the two bus managers. I tested clean installations of r30868; gcc4; '''ide-bm'''; acpi; on the second sata disk and on my primary sata disk with full Haiku builds (jam -qaj2), SDL configures + builds and the dd write tests mentioned earlier: * No occassional UI freezes on I/O (e.g. no Deskbar or ActivityMonitor replicant updates) * No system freeze during or after compiles ... read on ... I thought I nailed it down. While writing this text, there was more or less 5 mintutes of no heavy disk I/O after the "tests" performed above and it suddenly froze again. At least the UI freezes are not reproduceable with the ide-bm. Attaching "hdparm" info for the two disks if these are of interesst: Primary: {{{ /dev/sda: ATA device, with non-removable media Model Number: WDC WD3200BEKT-00F3T0 Serial Number: WD-WXE808PN8192 Firmware Revision: 11.01A11 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 625142448 device size with M = 1024*1024: 305245 MBytes device size with M = 1000*1000: 320072 MBytes (320 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: 128 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name * IDLE_IMMEDIATE with UNLOAD * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * SATA-I signaling speed (1.5Gb/s) * SATA-II signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 84min for SECURITY ERASE UNIT. 84min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee22157687 NAA : 5 IEEE OUI : 14ee Unique ID : 22157687 Checksum: correct }}} Secondary: {{{ /dev/sdb: ATA device, with non-removable media Model Number: ST9160823AS Serial Number: 5NK1DJD1 Firmware Revision: 3.CME Standards: Supported: 7 6 5 4 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 312581808 device size with M = 1024*1024: 152627 MBytes device size with M = 1000*1000: 160041 MBytes (160 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: 128 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * IDLE_IMMEDIATE with UNLOAD * Disable Data Transfer After Error Detection Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * SATA-I signaling speed (1.5Gb/s) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 56min for SECURITY ERASE UNIT. 56min for ENHANCED SECURITY ERASE UNIT. Checksum: correct }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 02:00:21 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 27 May 2009 00:00:21 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.40a0555f3b0059f28cf1c2285a8d7c19@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by marcusoverhagen): Sorry, I just noticed that there is already Diskprobe visible in the background of your picture. The 4th partion has a size (at offset 01fa) of 0x024300ba*512byte = 18.5 GB. Please dump sector 0 of partition 4, or 0x070de407 of the harddisk. It should contain that fat bootsector. How large did you format the fat partion? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 02:02:51 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 27 May 2009 00:02:51 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.3ab4f4da3ed8aefdd2e7f54b320c80be@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by marcusoverhagen): what does "Partition 4 was not available to set up as BFS from Haiku, so it was formatted as FAT32 from WinXP." mean? why wasn't it available? what do you want to say? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 02:43:22 2009 From: trac at haiku-os.org (franxico) Date: Wed, 27 May 2009 00:43:22 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting Message-ID: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- I built Haiku (~r30800) from Linux and installed it in a partition, real hardware. I have a Vostro 410 Quad Core with SATA and no PS/2 ports. Haiku hangs at the rocket icon. Maybe http://dev.haiku-os.org/ticket/2253 related. I'm opening this ticket at mmlr's request. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 02:44:40 2009 From: trac at haiku-os.org (marcusoverhagen) Date: Wed, 27 May 2009 00:44:40 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.efc1fcc4f0c0dccf5918a882b5df49d4@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by marcusoverhagen): Please insert a panic directly after " if (sVectors[vector].ignored_count > 9900) " into src/system/kernel/int.c I'm interested to see if that code path gets executed during the freeze. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 02:50:37 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 27 May 2009 00:50:37 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.38a78fa180d68393951fe2ed4c6d2c28@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): That's not the last page of output. It's just the last page that you could reach by pressing something. Please press "p" before getting there to disable paging and take another picture of the actual last page. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 03:18:03 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 01:18:03 -0000 Subject: [Haiku-bugs] [Haiku] #3953: GCC Hybrid : Cannot compile programs for alternative gcc In-Reply-To: <041.c4c5c8799b75a281d836b0e53fede209@haiku-os.org> References: <041.c4c5c8799b75a281d836b0e53fede209@haiku-os.org> Message-ID: <050.eed7f40e3d5cd197684f347121c13614@haiku-os.org> #3953: GCC Hybrid : Cannot compile programs for alternative gcc --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Implemented in r30875. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 03:33:34 2009 From: trac at haiku-os.org (mmlr) Date: Wed, 27 May 2009 01:33:34 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 In-Reply-To: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> References: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> Message-ID: <049.5b5b69f93096d476a5b1eefaddfe771e@haiku-os.org> #3968: Can't install from CD at r30851 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by mmlr): Is this fixed by r30876? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 04:10:53 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 27 May 2009 02:10:53 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.6bb8b220c8fad77a5910cf2789fa2c95@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by scottmc): corrected.. i've updated the haikuports portlog entry to reflect this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 13:38:47 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 11:38:47 -0000 Subject: [Haiku-bugs] [Haiku] #2738: /boot/develop/headers/cpp is wrong link ? In-Reply-To: <037.06f275da2168d780e3ec5a69dacb9957@haiku-os.org> References: <037.06f275da2168d780e3ec5a69dacb9957@haiku-os.org> Message-ID: <046.42a965467775db2cdc00fcc57b448276@haiku-os.org> #2738: /boot/develop/headers/cpp is wrong link ? ---------------------------+------------------------------------------------ Reporter: mt | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Fixed in r30875 at the latest. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 13:48:04 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 11:48:04 -0000 Subject: [Haiku-bugs] [Haiku] #3021: Building gcc4 cross-compiler errors in binutils? In-Reply-To: <038.5bda3c447a9959fd90b73be56b87ebfc@haiku-os.org> References: <038.5bda3c447a9959fd90b73be56b87ebfc@haiku-os.org> Message-ID: <047.2e5f33cc3254bcce8fdc5d4c2a21331e@haiku-os.org> #3021: Building gcc4 cross-compiler errors in binutils? ---------------------------+------------------------------------------------ Reporter: tqh | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: This should have been fixed by the upgrade to gcc 4.3.3 and binutils 2.19. If it still can be reproduced, please reopen. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 13:56:52 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 11:56:52 -0000 Subject: [Haiku-bugs] [Haiku] #3433: Cosmetic change for Changeset [29161] In-Reply-To: <041.b188e7af23afa7c06d3c691a35fac45f@haiku-os.org> References: <041.b188e7af23afa7c06d3c691a35fac45f@haiku-os.org> Message-ID: <050.186164f87cfa696abe0b17adbcdc80d5@haiku-os.org> #3433: Cosmetic change for Changeset [29161] ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => invalid Comment: I don't find it particularly confusing that both are called UserBuildConfig. I assume the one in the output directory will be used rarely anyway and by people who know what they are doing. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 13:59:06 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 11:59:06 -0000 Subject: [Haiku-bugs] [Haiku] #3547: cc fails when compiling bfs_disk_system.cpp In-Reply-To: <045.6326640b4403f81a09029368d72329d2@haiku-os.org> References: <045.6326640b4403f81a09029368d72329d2@haiku-os.org> Message-ID: <054.e80c67b6952795ab9fdcab5038842606@haiku-os.org> #3547: cc fails when compiling bfs_disk_system.cpp ---------------------------+------------------------------------------------ Reporter: Phoenix137 | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: x64 | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Lacking a 64 bit Linux I can't test it myself. Trusting that Matt is right. Please reopen, if there's still a problem. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 13:59:52 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 11:59:52 -0000 Subject: [Haiku-bugs] [Haiku] #3561: Objective C not supported by gcc In-Reply-To: <037.4af84252cdb1d45fb29f07d305277aed@haiku-os.org> References: <037.4af84252cdb1d45fb29f07d305277aed@haiku-os.org> Message-ID: <046.c3c1207e327c6ff41450e1a10bafc19b@haiku-os.org> #3561: Objective C not supported by gcc --------------------------+------------------------------------------------- Reporter: js | Owner: bonefish Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Changes (by bonefish): * priority: normal => low -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 14:05:27 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 12:05:27 -0000 Subject: [Haiku-bugs] [Haiku] #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes In-Reply-To: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> References: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> Message-ID: <049.4aa281ce4c3a668654f3ad140576bcc0@haiku-os.org> #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Without further info I'm assuming this was a non-xattr build related problem. Might be fixed in r24528. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 14:26:28 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 12:26:28 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.1fe6ce985ec9896ff660c58ad56e1633@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): The new OpenSSH package does not contain a common/boot/post_install/ssh.sh script to generate the host keys on first boot. You can reuse the script from the 5.0p1 package, but the host key location has to be adjusted. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 14:35:52 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 12:35:52 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.332682b8b03d256f1de232d5c7c1da22@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): The LibIconv and SQLite packages explicitely don't install on gcc 4 Haiku. Is this intentional? If so, alternatives need to be provided for gcc 4, since without the libraries the new svn package won't work. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 14:40:02 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 27 May 2009 12:40:02 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.40ea011f80e488dffa42aa5e04fa21fd@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by mmadia): Yesterday, I asked scott about this. Basically, he, I, and others aren't confident in being able to determine if a particular piece of software is gcc agnostic. Is there a sure-fire way to be able to check if a particular binary or library can be used on both gcc2 and gcc4? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 14:43:36 2009 From: trac at haiku-os.org (bga) Date: Wed, 27 May 2009 12:43:36 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.a3817bb6883544b9e7e076315d7aeb69@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bga): Well, if it is pure C, it can. If it is C++, it can not. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:01:00 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 13:01:00 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.14758f97e96a0c5f6b1d319eeb90d224@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): Replying to [comment:7 mmadia]: > Yesterday, I asked scott about this. Basically, he, I, and others aren't confident in being able to determine if a particular piece of software is gcc agnostic. Is there a sure-fire way to be able to check if a particular binary or library can be used on both gcc2 and gcc4? Any C-only software should be fine with both gcc 2 and gcc 4, since (to my knowledge) only the C++ ABI changed between the compiler versions. As a test building with one gcc and running on a non-hybrid Haiku of the alternative version should suffice. For libraries build with one gcc version and build a program linking against (and actually using) it (maybe even the test suite) with the other gcc. Most older portable libraries are purely C. Checking for source files with extensions .cpp, .cc, or .cxx should suffice to verify that. Another note regarding the patch: SQLite should be listed after RSync in OptionalPackages. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:16:38 2009 From: trac at haiku-os.org (diver) Date: Wed, 27 May 2009 13:16:38 -0000 Subject: [Haiku-bugs] [Haiku] #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes In-Reply-To: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> References: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> Message-ID: <049.a7812e581778a4e5be3b8e1705f1f795@haiku-os.org> #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): How do I know it were built with xattr or not? And how to enable it? I used this tutorial to build images http://www.haiku-os.org/node/1781 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:28:42 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 27 May 2009 13:28:42 -0000 Subject: [Haiku-bugs] [Haiku] #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes In-Reply-To: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> References: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> Message-ID: <049.c4800d2ad949638293a4b9cc9398f531@haiku-os.org> #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by mmadia): Here's a page about --use-xattr : http://www.haiku-os.org/node/2519 It's part of the re-organization of the website documentation. As for checking if it's enabled, look in $(HAIKU_OUTPUT_DIR)/build/BuildConfig for the variable HAIKU_HOST_USE_XATTR. If it's equal to one, then it's set. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:32:16 2009 From: trac at haiku-os.org (diver) Date: Wed, 27 May 2009 13:32:16 -0000 Subject: [Haiku-bugs] [Haiku] #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes In-Reply-To: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> References: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> Message-ID: <049.0c280c3eb145c7600d94b14fa673c0ba@haiku-os.org> #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by diver): Thanks, but I get Access denied when I try to open http://www.haiku- os.org/node/2519 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:53:58 2009 From: trac at haiku-os.org (mmadia) Date: Wed, 27 May 2009 13:53:58 -0000 Subject: [Haiku-bugs] [Haiku] #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes In-Reply-To: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> References: <040.bdf72b0a8fa5c43383ccd2eea19effb4@haiku-os.org> Message-ID: <049.492dcd36cd31c6343330610949c2283f@haiku-os.org> #3590: [build system] /boot/develop/lib/x86/start_dyn.org have tracker attributes ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by mmadia): *cough* seems i never published it. Log in and try again. Just to note, the page is a work in progress. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 15:59:52 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 13:59:52 -0000 Subject: [Haiku-bugs] [Haiku] #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault In-Reply-To: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> References: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> Message-ID: <052.a186d82571ef9a2c8d87867ce4be0ba8@haiku-os.org> #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): If your deadlock happened when something crashed, it is not related to the ticket. Those deadlocks could happen due to the stack trace the kernel printed on userland crashes. I've disabled them in r30877. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 17:11:07 2009 From: trac at haiku-os.org (scottmc) Date: Wed, 27 May 2009 15:11:07 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.b7727223871def29de434f0711dec953@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): Replying to [comment:6 bonefish]: > The LibIconv and SQLite packages explicitely don't install on gcc 4 Haiku. Is this intentional? If so, alternatives need to be provided for gcc 4, since without the libraries the new svn package won't work. Perhaps someone with a GCC4 built Haiku can try these out and report back. SQLite should work ok on gcc4 as it's a C library, not sure about LibIconv, also neon needs to be verified as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 17:20:27 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 15:20:27 -0000 Subject: [Haiku-bugs] [Haiku] #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault In-Reply-To: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> References: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> Message-ID: <052.6550735709b096b02efaa5c90831476a@haiku-os.org> #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault ---------------------------+------------------------------------------------ Reporter: bonefish | Owner: bonefish Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Working on it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 18:46:39 2009 From: trac at haiku-os.org (umccullough) Date: Wed, 27 May 2009 16:46:39 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.78b4b4e0b0917ff669c2981a04c53fed@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by umccullough): iconv, neon, and sqlite all seem to work fine on gcc4 haiku. If they were used in a previous Subversion client - looks like none of them link to libstdc++... Since the previous gcc2 Subversion client worked fine on gcc4 Haiku, I wouldn't have expected the new one to fail :) On the other hand, I'd be glad to compile gcc4 versions if it would reduce the possibility that the runtime_loader will be confused when a mixture of gcc2/gcc4 libs exist on a hybrid system (does this matter?) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 21:03:54 2009 From: trac at haiku-os.org (michael.weirauch) Date: Wed, 27 May 2009 19:03:54 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.5a4f30a379519b0f825bda9aea306d76@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): Nope, that code is not taken it seems. At least it seems not taken during the occassional UI freezes. (Which then relief again) Do you think it's worth planting some more dprintf() and or panic() in the interrupt handling code? Btw, I think I need to invalidate my statement that the UI freezes don't happen with the ide-bm. Dunno what was different yesterday. Had them again with a fresh r30878 and ide-bm. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 21:16:29 2009 From: trac at haiku-os.org (bga) Date: Wed, 27 May 2009 19:16:29 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.f05504ab6028fabcf855dc822ddf9fcd@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by bga): Michael, the UI freezes (the ones where the entire system seems to freeze and then resumes working after a few seconds) is not restricted to you. AFAIK, it happens with every single person running Haiku. I get it with a Core 2 Quad Extreme at 3.6 GHz and with 3 Gb of memory. It is indeed IO related but I don't think it is the cause of your other problems. If I were you, I would focus on the other pones as this is a know problem (there is a ticket for it somewhere). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Wed May 27 21:29:41 2009 From: trac at haiku-os.org (michael.weirauch) Date: Wed, 27 May 2009 19:29:41 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.2a8176f8536adccedd1e50cb67de2e15@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by michael.weirauch): Hey Bruno, thanks for the info related to the occassional UI freezes. I just mention them as a side note. But as they aren't as dramatical, and as I am apparently not the only one experiencing these, I think can forego mentioning these until they disappear ;) What is ineed more of a pressing issue are the total freezes of which I haven't yet figured out with the help from the "others" where they might stem from. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 00:42:37 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 22:42:37 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.2dc4d339ad46044b96362d5a30802a5e@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by bonefish): Replying to [comment:17 bga]: > Michael, the UI freezes (the ones where the entire system seems to freeze and then resumes working after a few seconds) is not restricted to you. AFAIK, it happens with every single person running Haiku. Haven't seen that problem on my machines yet. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 01:21:35 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 23:21:35 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.56b4f04cec390faa1931abd75c2f9812@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): Replying to [comment:11 umccullough]: > On the other hand, I'd be glad to compile gcc4 versions if it would reduce the possibility that the runtime_loader will be confused when a mixture of gcc2/gcc4 libs exist on a hybrid system (does this matter?) No worries, the runtime loader isn't confused that easily. :-) @scottmc: I've tested the new patch, but apparently the svn executable is linked against libxml2.so.2, which is not available. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 01:31:57 2009 From: trac at haiku-os.org (bonefish) Date: Wed, 27 May 2009 23:31:57 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.d63499df80e1edd5df8c374270800e13@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by bonefish): Sorry, another note: I've noticed the APR related credits in AboutSystem appear as "apr" and "apr-util". Could you change that to "APR" and "APR- util" please, since those seem to be the official names. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 04:05:54 2009 From: trac at haiku-os.org (stpere) Date: Thu, 28 May 2009 02:05:54 -0000 Subject: [Haiku-bugs] [Haiku] #2868: [Tracker] Update directory size info In-Reply-To: <042.c36047e3cce76a5b50b1c4a04fa0ada9@haiku-os.org> References: <042.c36047e3cce76a5b50b1c4a04fa0ada9@haiku-os.org> Message-ID: <051.de6da584e58a6c1f44db014a0ec3fe1c@haiku-os.org> #2868: [Tracker] Update directory size info ----------------------------+----------------------------------------------- Reporter: Adek336 | Owner: stpere Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Changes (by stpere): * owner: stippi => stpere * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 02:50:51 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 28 May 2009 00:50:51 -0000 Subject: [Haiku-bugs] [Haiku] #3734: BFS formatted USB memory stick not found In-Reply-To: <040.d6f14de0d71fa1439e2b7387478e17d8@haiku-os.org> References: <040.d6f14de0d71fa1439e2b7387478e17d8@haiku-os.org> Message-ID: <049.ab29c9a0ac0c66e56129ee4965d6cf64@haiku-os.org> #3734: BFS formatted USB memory stick not found -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Changes (by mmlr): * owner: mmlr => nobody * status: assigned => new Comment: Any news on this? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 02:37:45 2009 From: trac at haiku-os.org (bga) Date: Thu, 28 May 2009 00:37:45 -0000 Subject: [Haiku-bugs] [Haiku] #3772: Freeze on Haiku tree compilation (reproduceable) In-Reply-To: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> References: <051.cc0063dd1702ef0a00a9391b9565c853@haiku-os.org> Message-ID: <060.10ae6f48dcb89c8f2adb12cc5fe6385e@haiku-os.org> #3772: Freeze on Haiku tree compilation (reproduceable) ------------------------------+--------------------------------------------- Reporter: michael.weirauch | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------+--------------------------------------------- Comment(by bga): Then you are lucky. :) It has been discussed several times already in the mailing lists (Axel even started looking into it once as it was even more visible in his EEE PC if I am not mistaken). It happens all the time when I do, for example, "svn up" in the Haiku tree or when compiling Haiku inside itself. It is easier to notice if you are playing an audio file for example but can also be noticed if you have "Show seconds" enabled in the Deskbar clock and you pay attention to it or if you run ActivityMonitor while doing what I mentioned as you will notice that sometimes it refuses to redraw itself for several seconds when heavy IO is going on. *BUT*, this is a subject for another ticket I guess. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 02:27:58 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 28 May 2009 00:27:58 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.b69852a3da658b4715f16bc875c0c83a@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): I'll update the APR and APR-util .OPD files as requested and will put together a package for libxml2, I seem to recall neon may rely on it as well. I'm also putting together a patch to add nano as an Optional Package as that was mentioned recently on the mailing lists as well. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 13:56:17 2009 From: trac at haiku-os.org (pacman) Date: Thu, 28 May 2009 11:56:17 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.1d7f2aa008767ad5a495d0f6ef546fb5@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by pacman): Replying to [comment:23 axeld]: > Stippi, about acceleration in general on older systems: unlike new systems, they have, in today's standards, an insanely limited memory bandwidth. So many things, most notably moving windows around, or scrolling, can still be done a lot faster using the hardware acceleration than you could do via software. This is only generally true for PCI cards, which will often be limited to 40-60 MB/s write speed or less. On very bad motherboards this may drop to 20 MB/s or so, if the PCI implementation is buggy. On AGP cards, you generally get 200+ MB/s write speed unless AGP is improperly configured. With write combining and fast writes, 200 MB/s is pretty much the lower bound (but 130MB/s has been observed on one of Rudolfs systems, a TNT-1/AGPx1 on Intel 400 BX). These low values only happen on cards so old that they will run only in very low resolutions anyway, which negates the effect from the low bandwidth. Most AGP cards can easily write 400-1000 MB/s, which is enough bandwith even for higher resolutions. Note: this only goes for writes, reads are insanely slow on AGP. 13 MB/s is the fastest I've ever seen for that; 5 MB/s seems to be normal. With 200 MB/s write, you can push 60 full 1024x768 32-bit screen updates per second; I think this should be enough for most scenarios (you'll rarely need full screen updates). One thing: to reach the maximum bandwith, write combining has to be properly configured. Without WC, write speeds depends on operand size, and there are drastic differences between using 64/32/8-bit operands. The relationships between WC/FW combinations and write speeds are a bit... strange. The only way to find optimum settings will be testing on many different machines - speeds can be influenced by hardware bugs/suboptimal implemenation of AGP specs by mainboard or graphics card manufacturer. I have some older GfxBussBench results from my own and Rudolfs machines lying around in the GfxBusBench sources; I'll see that I dust that off as soon as I find the time. I'm willing to donate GfxBusBench to Haiku (as Rudolf already stated, it runs without changes) if there's interest. There might be a need to rework the command line parameters or such, but the core should be reliable. > This is where we might want to improve our acceleration usage (if possible) - this will definitely be faster on "slow" machines. The other stuff isn't so bad when ignored. As long as support for PCI and AGPx1 cards is desired, yes. For all other cards, correct configuration of write combining and AGP fast writes should basically always give sufficient bandwith for working without hw acceleration. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 14:22:24 2009 From: trac at haiku-os.org (richienyhus) Date: Thu, 28 May 2009 12:22:24 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.f3b999baab7c6d6f26f434fbe8eef88e@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): That workaround works under r30884. :) I take it this will be fixed when EDID is fully implemented? Would this also be a dup of #1696, #1557 or #1026 then ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 14:34:35 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 28 May 2009 12:34:35 -0000 Subject: [Haiku-bugs] [Haiku] #3885: Live CD crash in attribute_overlay filesystem In-Reply-To: <048.07107e720c186eb5af2baf05c5ddb26e@haiku-os.org> References: <048.07107e720c186eb5af2baf05c5ddb26e@haiku-os.org> Message-ID: <057.f4a9e86308840bfc2827f873ddc5f1bb@haiku-os.org> #3885: Live CD crash in attribute_overlay filesystem ----------------------------+----------------------------------------------- Reporter: jonas.kirilla | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30893. Any rename/move would cause a crash. And I really though I had tested that... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 15:05:58 2009 From: trac at haiku-os.org (franxico) Date: Thu, 28 May 2009 13:05:58 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.ab9a9b523ba578227841cf9c5de38ce1@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by franxico): Following your instruction I discoverd that Haiku doesn't hang. Actually, it falls in a infinite (?) loop. The pictures dsc 1154 an 55 show the debug stage when the message "usb_disk: acquire_sem failed while waiting for data transfer" starts to repeat forever (I waited for ten minutes or so). I have a card reader, but no cards were inserted. I have also an USB printer (HP Deskjet 5550). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 15:20:56 2009 From: trac at haiku-os.org (diver) Date: Thu, 28 May 2009 13:20:56 -0000 Subject: [Haiku-bugs] [Haiku] #3910: Something wrong in attribute overlay or in the build system populating haiku-cd In-Reply-To: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> References: <048.644e7f928558e338132865d5f4ca7059@haiku-os.org> Message-ID: <057.f4e90944529f9147ae9c830f39593fce@haiku-os.org> #3910: Something wrong in attribute overlay or in the build system populating haiku-cd ---------------------------+------------------------------------------------ Reporter: jonas.kirilla | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by diver): Same here with jam @alpha-cd.[[BR]] Also with jam @alpha-vmware I started seeing recently something that could be related to this bug:[[BR]] /boot/common now have text/plain mime type. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 15:22:35 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 28 May 2009 13:22:35 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.23e95d75799277062e092c2a2f83cfea@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by mmlr): It's trapped in an interrupt storm. If you remove all USB hardware from the system, does it then boot? You should be able to simply connect the keyboard and mouse after the boot process. Can you then please enter KDL using the F12 key and post here what the "ints" command prints out? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 15:51:22 2009 From: trac at haiku-os.org (franxico) Date: Thu, 28 May 2009 13:51:22 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.e1607f4bc51f272e0e6398e4bd925d76@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by franxico): YAY! It's the first time I could boot Haiku on this computer =D \o/ So yes, removing the Cordless Desktop and then connecting it after boot works, thanks! :) I took two pictures. First, the 'int' command and second, the 'sc' command (don't know if it is useful). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 16:03:04 2009 From: trac at haiku-os.org (bga) Date: Thu, 28 May 2009 14:03:04 -0000 Subject: [Haiku-bugs] [Haiku] #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting In-Reply-To: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> References: <043.aa7069c3898bcff3a5e0837840e343e3@haiku-os.org> Message-ID: <052.3f7559abfd1e290a04c6319b850f0784@haiku-os.org> #3972: Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting -------------------------+-------------------------------------------------- Reporter: franxico | Owner: mmlr Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/USB | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------+-------------------------------------------------- Comment(by bga): BTW, I do have a similar problem. If my printer is connected and tuirned on during boot, Haiku will not boot (I didn't investigate, but as this is a lock up and not a crash, I am prety sure it is the same problem as reported here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 16:03:37 2009 From: trac at haiku-os.org (stpere) Date: Thu, 28 May 2009 14:03:37 -0000 Subject: [Haiku-bugs] [Haiku] #2868: [Tracker] Update directory size info In-Reply-To: <042.c36047e3cce76a5b50b1c4a04fa0ada9@haiku-os.org> References: <042.c36047e3cce76a5b50b1c4a04fa0ada9@haiku-os.org> Message-ID: <051.98d5ecd26987dd2665295f2b0dd85253@haiku-os.org> #2868: [Tracker] Update directory size info -----------------------------+---------------------------------------------- Reporter: Adek336 | Owner: stpere Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: User Interface | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by stpere): * status: assigned => closed * resolution: => fixed Comment: Hi, this is implemented in r30894. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 17:39:19 2009 From: trac at haiku-os.org (titer) Date: Thu, 28 May 2009 15:39:19 -0000 Subject: [Haiku-bugs] [Haiku] #3973: ioctl FIONREAD does not propagate errors Message-ID: <040.9afcfcba81665b379863be1a77d5fd7c@haiku-os.org> #3973: ioctl FIONREAD does not propagate errors --------------------------------+------------------------------------------- Reporter: titer | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Test case with a not connected socket: {{{ #include #include #include #include int main() { int fd = socket(AF_INET, SOCK_STREAM, 0); int n = 0x42; int ret = ioctl(fd, FIONREAD, &n); printf("ret %d, n %d / %X\n", ret, n, n); return 0; } }}} gives: {{{ ret 0, n -2147454946 / 8000701E }}} The ioctl should return -1 and set errno, rather than saying there are ENOTCONN bytes available for reading. I noticed this from running libevent tests - since ioctl returns 0, it (legitimately IMO) assumes the value is >= 0 and ends up trying to allocate some GBs of memory. Haiku r30805 gcc4 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 17:55:17 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 28 May 2009 15:55:17 -0000 Subject: [Haiku-bugs] [Haiku] #3973: ioctl FIONREAD does not propagate errors In-Reply-To: <040.9afcfcba81665b379863be1a77d5fd7c@haiku-os.org> References: <040.9afcfcba81665b379863be1a77d5fd7c@haiku-os.org> Message-ID: <049.00867b5d411dea195cb18865c1a166bd@haiku-os.org> #3973: ioctl FIONREAD does not propagate errors --------------------------------+------------------------------------------- Reporter: titer | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by mmlr): * owner: axeld => mmlr * status: new => assigned Comment: Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 18:04:02 2009 From: trac at haiku-os.org (mmlr) Date: Thu, 28 May 2009 16:04:02 -0000 Subject: [Haiku-bugs] [Haiku] #3973: ioctl FIONREAD does not propagate errors In-Reply-To: <040.9afcfcba81665b379863be1a77d5fd7c@haiku-os.org> References: <040.9afcfcba81665b379863be1a77d5fd7c@haiku-os.org> Message-ID: <049.f75f3c1c5a4451c43ce5809051569c36@haiku-os.org> #3973: ioctl FIONREAD does not propagate errors ---------------------------------+------------------------------------------ Reporter: titer | Owner: mmlr Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Network & Internet | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by mmlr): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30896. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 19:27:15 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 28 May 2009 17:27:15 -0000 Subject: [Haiku-bugs] [Haiku] #3230: sed needs to be freshened (easy) In-Reply-To: <042.09b5d38121938938df9116d80a5f145c@haiku-os.org> References: <042.09b5d38121938938df9116d80a5f145c@haiku-os.org> Message-ID: <051.e48d09c0d7f5d3c9840e37acb52120cf@haiku-os.org> #3230: sed needs to be freshened (easy) ---------------------------------------------+------------------------------ Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by scottmc): There is a sed-4.1.5 optional package posted now but it doesn't seem to be included with any of the OptionalPackages yet? http://haiku-files.org/files/optional-packages/ Where should it be included, in one of the Development options? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 21:18:43 2009 From: trac at haiku-os.org (scottmc) Date: Thu, 28 May 2009 19:18:43 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.9a5f6bc6eba839ac5b7b6759ea733374@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): The cdrecord zip includes both cdrecord, and mkisofs which is needed if someone wants to "jam haiku-cd" on Haiku. I am checking that all of the packages download properly on a fresh build system, and have turned up a few minor issues, better patch coming soon. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Thu May 28 23:36:13 2009 From: trac at haiku-os.org (korli) Date: Thu, 28 May 2009 21:36:13 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.98973dc7b4a0821658d956737ee0d24e@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by korli): I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 00:02:40 2009 From: trac at haiku-os.org (bonefish) Date: Thu, 28 May 2009 22:02:40 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.612b9b2b7b069f59ab4f215dcd03e416@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by bonefish): Replying to [comment:10 korli]: > I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ? Nope, that isn't a prefix path, anyway. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 02:01:47 2009 From: trac at haiku-os.org (diver) Date: Fri, 29 May 2009 00:01:47 -0000 Subject: [Haiku-bugs] [Haiku] #3974: [Tracker] opening a folder in listview is slow Message-ID: <040.8c2716b41c99d726f4a3be2cdf144ed3@haiku-os.org> #3974: [Tracker] opening a folder in listview is slow -----------------------+---------------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Opening a folder full of files is noticeably slower in listview compared to iconview. Examples:[[BR]] open /system/bin (3s vs 1s)[[BR]] open /system/documentation/bebook (5s vs 1s)[[BR]] vbox 2.0.2, Haiku r30907 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 02:02:00 2009 From: trac at haiku-os.org (diver) Date: Fri, 29 May 2009 00:02:00 -0000 Subject: [Haiku-bugs] [Haiku] #3974: [Tracker] opening a folder in listview is slow In-Reply-To: <040.8c2716b41c99d726f4a3be2cdf144ed3@haiku-os.org> References: <040.8c2716b41c99d726f4a3be2cdf144ed3@haiku-os.org> Message-ID: <049.9ce4a7a38202695a8df7d95f2f86a907@haiku-os.org> #3974: [Tracker] opening a folder in listview is slow ----------------------------------+----------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Changes (by diver): * component: - General => Applications/Tracker -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 02:07:08 2009 From: trac at haiku-os.org (diver) Date: Fri, 29 May 2009 00:07:08 -0000 Subject: [Haiku-bugs] [Haiku] #2845: [kernel] vm_page_fault: block notifier/writer In-Reply-To: <040.bb81718304eb12e166bb10537ea14f7b@haiku-os.org> References: <040.bb81718304eb12e166bb10537ea14f7b@haiku-os.org> Message-ID: <049.ec2d93b1d29d7f2c14d2b7271753e1d0@haiku-os.org> #2845: [kernel] vm_page_fault: block notifier/writer ----------------------------+----------------------------------------------- Reporter: diver | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Comment(by diver): I still can reproduce it in vbox 2.0.2, but not under vmware. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 03:08:09 2009 From: trac at haiku-os.org (darkwyrm) Date: Fri, 29 May 2009 01:08:09 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.5249a0e2dae13839124d04eb5c70ee62@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by darkwyrm): Absolutely. Tested with r30907: 1) Download and install Paladin RC6 -- http://www.bebits.com/bob/22146/Paladin1.0rc6.pkg.zip 2) Create /boot/home/projects folder 3) Open a Terminal and go to ~/projects. 4) $ unzip testproject.zip; cd BePhotoMagic 5) $ /boot/apps/Paladin/Paladin BePhotoMagic.pld 6) Hit Alt-M to run a build. Sometimes it will KDL on the first build attempt after it has progressed most of the way through the build. Sometimes Paladin craps out on an error. In such cases, restarting the build causes it to KDL almost immediately after the restart. The test rig is a P4 Xeon 3Ghz with Hyperthreading and 1GB RAM in the event SMP is a factor. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 06:52:49 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 29 May 2009 04:52:49 -0000 Subject: [Haiku-bugs] [Haiku] #3975: "GNU LGPL v3" is missing from system/data/licenses Message-ID: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> #3975: "GNU LGPL v3" is missing from system/data/licenses --------------------------------------+------------------------------------- Reporter: mmadia | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/AboutSystem | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- /boot/system/data/licenses lacks a copy of "GNU LGPL v3". This is referenced by GCC in AboutSystem. http://www.gnu.org/licenses/lgpl.html -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 07:32:37 2009 From: trac at haiku-os.org (scottmc) Date: Fri, 29 May 2009 05:32:37 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.8c97af2e0f1138a47104a03455566e99@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages -------------------------+-------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- Comment(by scottmc): the openssh zip should be checked over closer, as I'm not sure that I set the ssh.sh up properly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 08:18:52 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 29 May 2009 06:18:52 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.e1d0655c26de6f0c6163a77434d82a93@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi there Christian! Long time no speak, good to hear from you again :-) As said, I find your tool a handy one to have. Hopefully Axel or Stephan replies on this tool.. I mean, I can probably put it in svn, but I don't know if I'm supposed to do such things? BTW: I tested your tool on my new system and got these results: GeForce 7300 (G72): Write 64-bit: 1315.41 MB/s (3955.08 MB in 3.01 s) Write 32-bit: 1319.40 MB/s (3991.70 MB in 3.03 s) Write 8-bit: 1308.66 MB/s (3955.08 MB in 3.02 s) Read 64-bit: 5.66 MB/s (18.31 MB in 3.24 s) Read 32-bit: 4.42 MB/s (14.65 MB in 3.32 s) Read 8-bit: 1.10 MB/s (5.49 MB in 4.97 s) My old GeForce FX 6600 (NV43) ((id 140) which was very slow on the first PCIE system I had!!): Write 64-bit: 2507.81 MB/s (7543.95 MB in 3.01 s) Write 32-bit: 2507.94 MB/s (7543.95 MB in 3.01 s) Write 8-bit: 2281.85 MB/s (6848.14 MB in 3.00 s) Read 64-bit: 7.63 MB/s (27.47 MB in 3.60 s) Read 32-bit: 5.76 MB/s (21.97 MB in 3.81 s) Read 8-bit: 1.44 MB/s (5.49 MB in 3.82 s) And another GeForce FX 6600 (NV43): (id 141) Write 64-bit: 1631.66 MB/s (4907.23 MB in 3.01 s) Write 32-bit: 1633.97 MB/s (4907.23 MB in 3.00 s) Write 8-bit: 1625.91 MB/s (4907.23 MB in 3.02 s) Read 64-bit: 7.30 MB/s (27.47 MB in 3.76 s) Read 32-bit: 5.56 MB/s (21.97 MB in 3.95 s) Read 8-bit: 1.38 MB/s (5.49 MB in 3.97 s) I also tested a GF8500 in VESA mode and got speeds like id140: 2300Mb/sec. Reading remains dead slow these days. I hate that. :-/ Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 08:19:48 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 29 May 2009 06:19:48 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.af506fda736975364dd2fdc39517e587@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi Haikubot, Sounds like we can close this ticket. Do you agree? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 08:24:44 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 29 May 2009 06:24:44 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.f03a3b63014c32349b68a779b5b483a7@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, To loose the problem, you could place the file nvidia.settings in your home folder, and modify it in the line that reads: force_ws true to read: force_ws false If you now reboot, you should be able to use all normal 4:3 resolutions. Can you confirm this please? This problem will be gone once DDC is in use. It will probably (at least partially) solve these other bugs too. Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 10:21:03 2009 From: trac at haiku-os.org (HaikuBot) Date: Fri, 29 May 2009 08:21:03 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.2ad3998fd9ca6992263cd55c729e293d@haiku-os.org> #3886: problems with GeForce 7300 GT -------------------------------------+-------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by HaikuBot): Hi Rudolf. Sure, close ticket. And thanks for help. With best regards HaikuBot. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 11:15:18 2009 From: trac at haiku-os.org (korli) Date: Fri, 29 May 2009 09:15:18 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.280bcddb36457ac24f7acd19711c38b4@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by korli): Replying to [comment:11 bonefish]: > Replying to [comment:10 korli]: > > I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ? > > Nope, that isn't a prefix path, anyway. Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 12:16:05 2009 From: trac at haiku-os.org (richienyhus) Date: Fri, 29 May 2009 10:16:05 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.094a9511f8c456e6abf88a9dd1b6afcf@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): I downloaded nvidia.settings from here on trac (was it meant to have been in the file system?), and placed it in ~/config/settings/kernel/drivers, then rebooted as said. The list of resolutions in Screen changed, but only one extra one is usable. So 1152x864 works fine, plus 1400x1050 works too, but it only shows part of the screen (1280x1024 is the highest this screen is meant to go anyway). I can use 1024x768, 800x600 and 640x480 under other operating systems, but not with haiku. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 12:18:42 2009 From: trac at haiku-os.org (richienyhus) Date: Fri, 29 May 2009 10:18:42 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.9659b925dfb44cf44e2b909df1ac8a99@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): Fano, you should try the workaround in #2780 , and see if it works for you too. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 12:59:01 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 29 May 2009 10:59:01 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.50fe7a1686f322b9f6495963fc0a90dc@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by bonefish): Replying to [comment:12 korli]: > Replying to [comment:11 bonefish]: > > Replying to [comment:10 korli]: > > > I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ? > > > > Nope, that isn't a prefix path, anyway. > > Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ? I'm not quite sure, what the script is supposed to return. If it is the path for the linker, it should be /boot/develop/lib/x86 (for x86) or more generally /boot/develop/abi/current/lib. If it is the path where the library is located at runtime, it would be /system/lib. Other then that, I think the prefix in the script is incorrect anyway, since with don't install freetype in /boot/common, but in /system. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 15:16:30 2009 From: trac at haiku-os.org (mmadia) Date: Fri, 29 May 2009 13:16:30 -0000 Subject: [Haiku-bugs] [Haiku] #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses (was: "GNU LGPL v3" is missing from system/data/licenses) In-Reply-To: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> References: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> Message-ID: <050.b89a4811696c3b0b0485c9fa22e20b7e@haiku-os.org> #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses --------------------------------------+------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/AboutSystem | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Changes (by mmadia): * type: bug => enhancement Old description: > /boot/system/data/licenses lacks a copy of "GNU LGPL v3". This is > referenced by GCC in AboutSystem. http://www.gnu.org/licenses/lgpl.html New description: /boot/system/data/licenses lacks a copy of "GNU LGPL v3". This is referenced by GCC in AboutSystem. http://www.gnu.org/licenses/lgpl.html -- Comment: Added patch to add [http://www.gnu.org/licenses/lgpl-3.0.txt "GNU LGPL v3"] to haiku/haiku/data/system/data/licenses. Since the entire license folder appears to be copied over, no other patching is required. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 15:32:28 2009 From: trac at haiku-os.org (korli) Date: Fri, 29 May 2009 13:32:28 -0000 Subject: [Haiku-bugs] [Haiku] #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. In-Reply-To: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> References: <042.f88c10edb8ee92fd7f010a2f212aa2f2@haiku-os.org> Message-ID: <051.caaed6f5f4697aa5658a90fe9998f34d@haiku-os.org> #2949: Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing. -----------------------+---------------------------------------------------- Reporter: scottmc | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: 3167 | -----------------------+---------------------------------------------------- Comment(by korli): Replying to [comment:13 bonefish]: > > Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ? > > I'm not quite sure, what the script is supposed to return. If it is the path for the linker, it should be /boot/develop/lib/x86 (for x86) or more generally /boot/develop/abi/current/lib. If it is the path where the library is located at runtime, it would be /system/lib. When used with --libs, it's supposed to return how to link : -L/boot/develop/lib/x86 -lfreetype -lz For the time being, we could use /boot/develop/abi/current/lib then. > > Other then that, I think the prefix in the script is incorrect anyway, since with don't install freetype in /boot/common, but in /system. Agreed, I committed it as is to have an initial version. I suppose in a Linux environment, runtime and link libraries are at the same place. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 15:39:17 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 29 May 2009 13:39:17 -0000 Subject: [Haiku-bugs] [Haiku] #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault In-Reply-To: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> References: <043.f7f06558b43cc9f659156dd8ff67ea57@haiku-os.org> Message-ID: <052.4944bfb67df37175a68f2cb6916f0a9d@haiku-os.org> #2710: Deadlock between clone_area(), Kernel Area Operation, I/O, and Page Fault ----------------------------+----------------------------------------------- Reporter: bonefish | Owner: bonefish Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30911. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 16:26:46 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 29 May 2009 14:26:46 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.0c6f7613c36af434c5a61f059124134a@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Changes (by bonefish): * owner: axeld => bonefish * status: new => assigned Comment: Sweet, could just reproduce it in VMware. Looking into it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 16:55:50 2009 From: trac at haiku-os.org (bonefish) Date: Fri, 29 May 2009 14:55:50 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.f06bba94077bece7f764e20d2c100c68@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ---------------------------+------------------------------------------------ Reporter: diver | Owner: bonefish Type: bug | Status: assigned Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Can't reproduce in r30911 anymore. Might be related to the more defensive mapping in vm_soft_fault(). Trying to understand the original problem... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 17:28:19 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 29 May 2009 15:28:19 -0000 Subject: [Haiku-bugs] [Haiku] #3886: problems with GeForce 7300 GT In-Reply-To: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> References: <043.b0ab762dc163c9c159584465b5a8452b@haiku-os.org> Message-ID: <052.1b009913c541bff6ae15ce0f1e6305fc@haiku-os.org> #3886: problems with GeForce 7300 GT --------------------------------------+------------------------------------- Reporter: HaikuBot | Owner: rudolfc Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: --------------------------------------+------------------------------------- Changes (by rudolfc): * status: new => closed * resolution: => fixed Comment: Thanks, Closing :-) Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 17:35:34 2009 From: trac at haiku-os.org (rudolfc) Date: Fri, 29 May 2009 15:35:34 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.88e62e0df826e9bddaa77cb6d06cde18@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi again, What's the monitor you are using again? Can you name the brand and type? Do you connect via VGA or DVI? And: can you enable logging (modify nvidia.settings for that) and upload the driver's logfile from your homefolder after a reboot? Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 18:18:09 2009 From: trac at haiku-os.org (stippi) Date: Fri, 29 May 2009 16:18:09 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder In-Reply-To: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> References: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> Message-ID: <050.4ed88be73d514d87b79554b0496da13a@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by stippi): * milestone: R1 => R1/alpha1 Comment: I had emails disappear in a different folder now as well. In any case, since we promised to fix all bugs that cause data loss/corruption before alpha/1, I guess I should switch the milestone. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 21:04:36 2009 From: trac at haiku-os.org (miqlas) Date: Fri, 29 May 2009 19:04:36 -0000 Subject: [Haiku-bugs] [Haiku] #3859: Files disappear, always the same folder In-Reply-To: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> References: <041.216d17635db51a3e4ce7bd4a4916ec03@haiku-os.org> Message-ID: <050.09a80625f2dfec8a02296246230012c9@haiku-os.org> #3859: Files disappear, always the same folder ------------------------------+--------------------------------------------- Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: high | Milestone: R1/alpha1 Component: File Systems/BFS | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- Comment(by miqlas): This is a CVS version of BEAM? Because the latest stable don't have searchbar on the top of the window, if i know correctly. May this can be one of the problem sources? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 21:24:48 2009 From: trac at haiku-os.org (korli) Date: Fri, 29 May 2009 19:24:48 -0000 Subject: [Haiku-bugs] [Haiku] #2859: Wesnoth Issues In-Reply-To: <041.9e5a8b8277bb4e5bc43a228296db62d7@haiku-os.org> References: <041.9e5a8b8277bb4e5bc43a228296db62d7@haiku-os.org> Message-ID: <050.88368cb8af1cdef82bfb692fd4106f3b@haiku-os.org> #2859: Wesnoth Issues ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Game Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by korli): Download link fails. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 21:48:10 2009 From: trac at haiku-os.org (korli) Date: Fri, 29 May 2009 19:48:10 -0000 Subject: [Haiku-bugs] [Haiku] #3059: implement _IO_feof_unlocked and _IO_ferror_unlocked in libio.h [PATCH] In-Reply-To: <042.ea09621df08f1390e603399f9a0534ae@haiku-os.org> References: <042.ea09621df08f1390e603399f9a0534ae@haiku-os.org> Message-ID: <051.c24e391b8e9f30d730ce74956ef567c7@haiku-os.org> #3059: implement _IO_feof_unlocked and _IO_ferror_unlocked in libio.h [PATCH] --------------------------------+------------------------------------------- Reporter: kaliber | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: System/libroot.so | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------------+------------------------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Old description: > {{{ > commit 359d499fd541d6eb43b42ac96c16a008e0d436bc > Author: Grzegorz Dabrowski > Date: Sun Nov 2 14:42:36 2008 +0100 > > implemented _IO_feof_unlocked and _IO_ferror_unlocked > > diff --git a/headers/posix/libio.h b/headers/posix/libio.h > index 83caf1d..f284aec 100644 > --- a/headers/posix/libio.h > +++ b/headers/posix/libio.h > @@ -170,9 +170,9 @@ extern "C" { > #endif > > extern int _IO_feof(_IO_FILE *stream); > -extern int _IO_feof_unlocked(_IO_FILE *stream); > +#define _IO_feof_unlocked(__fp) (((__fp)->_flags & _IO_EOF_SEEN) != > 0) > extern int _IO_ferror(_IO_FILE *stream); > -extern int _IO_ferror_unlocked(_IO_FILE *stream); > +#define _IO_ferror_unlocked(__fp) (((__fp)->_flags & _IO_ERR_SEEN) != > 0) > extern int _IO_putc(int c, _IO_FILE *stream); > extern int _IO_putc_unlocked(int c, _IO_FILE *stream); > extern int _IO_getc(_IO_FILE *stream); > }}} New description: {{{ commit 359d499fd541d6eb43b42ac96c16a008e0d436bc Author: Grzegorz Dabrowski Date: Sun Nov 2 14:42:36 2008 +0100 implemented _IO_feof_unlocked and _IO_ferror_unlocked diff --git a/headers/posix/libio.h b/headers/posix/libio.h index 83caf1d..f284aec 100644 --- a/headers/posix/libio.h +++ b/headers/posix/libio.h @@ -170,9 +170,9 @@ extern "C" { #endif extern int _IO_feof(_IO_FILE *stream); -extern int _IO_feof_unlocked(_IO_FILE *stream); +#define _IO_feof_unlocked(__fp) (((__fp)->_flags & _IO_EOF_SEEN) != 0) extern int _IO_ferror(_IO_FILE *stream); -extern int _IO_ferror_unlocked(_IO_FILE *stream); +#define _IO_ferror_unlocked(__fp) (((__fp)->_flags & _IO_ERR_SEEN) != 0) extern int _IO_putc(int c, _IO_FILE *stream); extern int _IO_putc_unlocked(int c, _IO_FILE *stream); extern int _IO_getc(_IO_FILE *stream); }}} -- Comment: Applied in r30861. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Fri May 29 23:24:51 2009 From: trac at haiku-os.org (umccullough) Date: Fri, 29 May 2009 21:24:51 -0000 Subject: [Haiku-bugs] [Haiku] #2859: Wesnoth Issues In-Reply-To: <041.9e5a8b8277bb4e5bc43a228296db62d7@haiku-os.org> References: <041.9e5a8b8277bb4e5bc43a228296db62d7@haiku-os.org> Message-ID: <050.d6bf80e595eeaddbe3d1b0bd50d8dddf@haiku-os.org> #2859: Wesnoth Issues ---------------------------+------------------------------------------------ Reporter: kvdman | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Game Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by umccullough): Looks like a revised link is here: [http://haikuware.com/directory/view-details/games/strategy/wesnoth12] -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 02:09:02 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 00:09:02 -0000 Subject: [Haiku-bugs] [Haiku] #3110: [kernel] PANIC: page still has mappings In-Reply-To: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> References: <040.9e59e705f24bcc7b8f7623045e1f8c9f@haiku-os.org> Message-ID: <049.e19950d1f7b043a5909dc45b9fc2ee61@haiku-os.org> #3110: [kernel] PANIC: page still has mappings ----------------------------+----------------------------------------------- Reporter: diver | Owner: bonefish Type: bug | Status: closed Priority: high | Milestone: R1/alpha1 Component: System/Kernel | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Analyzed the problem with Paladin: Two threads of the same team simultaneously fault on the same virtual page, one write the other read. The write fault is handled first, the read fault maps the same page again, adding a second page mapping. Then do a fork(), which moves the cache one level lower and changes the page mappings to read-only. Another write fault in the original team unmaps the page -- removing only one mapping! -- and adds a fresh page in the top-most cache. When the child team exec()s, the top-most cache is merge with its source (the one with the "bad" page). Since the page is shadowed it is ignored while merging and removed when the cache is deleted, triggering the panic, since it still has the invalid mapping. Long story short: Simultaneous page faults are handled gracefully in r30911, so this problem is indeed fixed. It also seems like a good enough explanation for the other reported situations, so I'm closing this bug. Since it's already the third fixed bug which triggered the panic(), please create a new ticket, if encountered again. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 02:23:28 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 00:23:28 -0000 Subject: [Haiku-bugs] [Haiku] #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses In-Reply-To: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> References: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> Message-ID: <050.802da47df4d7b64df41db6d34f1e5d7c@haiku-os.org> #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses --------------------------------------+------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Applications/AboutSystem | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------------+------------------------------------- Comment(by bonefish): Thanks! Applied in r30912. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 02:23:51 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 00:23:51 -0000 Subject: [Haiku-bugs] [Haiku] #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses In-Reply-To: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> References: <041.13d73c17375b2393539206d4f8a057c1@haiku-os.org> Message-ID: <050.b7c946aebb5893eaf8f641e33aa5e9f5@haiku-os.org> #3975: [patch] add "GNU LGPL v3" to haiku/haiku/data/system/data/licenses ---------------------------------------+------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/AboutSystem | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------------+------------------------------------ Changes (by bonefish): * status: new => closed * resolution: => fixed -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 03:27:06 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 01:27:06 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.57cee4909b5bdee5513de139bd658e2c@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Changes (by bonefish): * status: new => closed * resolution: => fixed Comment: Thanks! Applied in r30914 and r30915. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 03:27:54 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 01:27:54 -0000 Subject: [Haiku-bugs] [Haiku] #2341: ssh host key location In-Reply-To: <048.eae264826cead436b297919bcf811f98@haiku-os.org> References: <048.eae264826cead436b297919bcf811f98@haiku-os.org> Message-ID: <057.cfdec467214feda0e370114477681086@haiku-os.org> #2341: ssh host key location ----------------------------+----------------------------------------------- Reporter: dustin howett | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------+----------------------------------------------- Changes (by bonefish): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30915. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 03:52:26 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 30 May 2009 01:52:26 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.c257a1c02093e6abfedaf9005bf92d86@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by scottmc): Replying to [comment:17 bonefish]: > Thanks! Applied in r30914 and r30915. Thanks. We just verified that ssh/sshd were working as excepted. There may be an issue with the PATH, but I think it's the same as the pervious package, so this one is as good as that one. Posted screenshot shows urias remotely logging into my laptop... -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 05:06:54 2009 From: trac at haiku-os.org (umccullough) Date: Sat, 30 May 2009 03:06:54 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.046a874b3b7e6b3cc77415a6484576d5@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by umccullough): The entire environment is missing when logging in remotely via ssh AFAICT - one must run /boot/system/boot/SetupEnvironment to fix it. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 07:18:11 2009 From: trac at haiku-os.org (humdinger) Date: Sat, 30 May 2009 05:18:11 -0000 Subject: [Haiku-bugs] [Haiku] #3976: Remove Menu preference Message-ID: <044.e68a9d80bca32a9716ad3f902fa54264@haiku-os.org> #3976: Remove Menu preference ------------------------------+--------------------------------------------- Reporter: humdinger | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Preferences/Menu | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------+--------------------------------------------- This is r30893. Since all useful functions from the Menu preferences have been moved to other panels (Appearance, Fonts, Keymap), the Menu preferences should be retired.[[BR]] I think that what was planned some time ago (see #3259), but it's still there. Don't forget to also remove "Menu" as Trac component. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 08:09:49 2009 From: trac at haiku-os.org (richienyhus) Date: Sat, 30 May 2009 06:09:49 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.9ad96a5943fdfcc32f30e65cd723a586@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): Gday, its a ViewSonic. Haiku says its a VP171b-2, the model number on the screen just says VP171b. The screen has two VGAs and one DVI, My haiku box is plugged into the first VGA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 08:54:44 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 06:54:44 -0000 Subject: [Haiku-bugs] [Haiku] #3977: [patch] Allow alpha-raw to build again. Message-ID: <041.c7033ba77a458b997d05da979e3d7c05@haiku-os.org> #3977: [patch] Allow alpha-raw to build again. --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: critical | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- With the recent additions to the OptionalPackages, the disk consumption of at least @alpha-raw has exceeded 400mb. Currently, `jam -q @alpha-raw` fails to build due to lack of diskspace when unzipping archives. @alpha- vmware is assumed to fail similarly. Attached is a patch to bump up the size to 500mb and a screenshot for good measure. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 09:15:50 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 07:15:50 -0000 Subject: [Haiku-bugs] [Haiku] #3870: [patch] cd rom build requires mkisofs (was: cd rom build requires mkisofs) In-Reply-To: <042.b941729ea5578ecaeb9ec80704a36963@haiku-os.org> References: <042.b941729ea5578ecaeb9ec80704a36963@haiku-os.org> Message-ID: <051.4c73be2cc0f199b4aafbd23ce83bd90d@haiku-os.org> #3870: [patch] cd rom build requires mkisofs --------------------------+------------------------------------------------- Reporter: bbjimmy | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Comment(by mmadia): Attached patch that adds CDRecord (and mkisofs) to DevelopmentBase's dependencies. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 10:41:38 2009 From: trac at haiku-os.org (idefix) Date: Sat, 30 May 2009 08:41:38 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.92d0fde015f7361542352f602c1dbdd4@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by idefix): Replying to [comment:18 scottmc]: > Posted screenshot shows urias remotely logging into my laptop... I noticed that you partially blanked out your ip-address in the chat-log, but you forgot the big ip-address in the bottom of the image. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 11:04:57 2009 From: trac at haiku-os.org (stippi) Date: Sat, 30 May 2009 09:04:57 -0000 Subject: [Haiku-bugs] [Haiku] #3977: [patch] Allow alpha-raw to build again. In-Reply-To: <041.c7033ba77a458b997d05da979e3d7c05@haiku-os.org> References: <041.c7033ba77a458b997d05da979e3d7c05@haiku-os.org> Message-ID: <050.5dd8233b2aae57988308efdda4109e30@haiku-os.org> #3977: [patch] Allow alpha-raw to build again. ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: bonefish Type: enhancement | Status: closed Priority: critical | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Applied in r30916. Thanks! I am wondering though why the packages use more space now. I thought Subversion for example was switched from static to shared libs, and a couple of those were duplicates. So it "should" be less now... no time to look into it, though. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 11:17:33 2009 From: trac at haiku-os.org (stippi) Date: Sat, 30 May 2009 09:17:33 -0000 Subject: [Haiku-bugs] [Haiku] #3870: [patch] cd rom build requires mkisofs In-Reply-To: <042.b941729ea5578ecaeb9ec80704a36963@haiku-os.org> References: <042.b941729ea5578ecaeb9ec80704a36963@haiku-os.org> Message-ID: <051.1ec1fdf52f30d23c756b84f04898c2d7@haiku-os.org> #3870: [patch] cd rom build requires mkisofs ---------------------------+------------------------------------------------ Reporter: bbjimmy | Owner: bonefish Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Applied in r30917. Thanks! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 11:52:22 2009 From: trac at haiku-os.org (diver) Date: Sat, 30 May 2009 09:52:22 -0000 Subject: [Haiku-bugs] [Haiku] #423: [Beezer] Segment violation (part two) In-Reply-To: <040.7e4d72961fa1d5f027c82a6bdcace28e@haiku-os.org> References: <040.7e4d72961fa1d5f027c82a6bdcace28e@haiku-os.org> Message-ID: <049.8b8601b3170a1d0caec02c2ff1abf14c@haiku-os.org> #423: [Beezer] Segment violation (part two) ---------------------------------+------------------------------------------ Reporter: diver | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: invalid | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by diver): * platform: => All * version: => R1 development * component: - General => Kits/Interface Kit Comment: Just to note, it doesn't crash anymore. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 12:40:41 2009 From: trac at haiku-os.org (stippi) Date: Sat, 30 May 2009 10:40:41 -0000 Subject: [Haiku-bugs] [Haiku] #3971: Patch: enable mixed mouse+keyboard input in Sudoku In-Reply-To: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> References: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> Message-ID: <048.42bb4e2e0b612b3a91f53fbfcfa5c71c@haiku-os.org> #3971: Patch: enable mixed mouse+keyboard input in Sudoku ----------------------------------+----------------------------------------- Reporter: Stef | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by stippi): * status: new => closed * resolution: => fixed Comment: Applied in r30918. Thanks a lot! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 13:37:53 2009 From: trac at haiku-os.org (korli) Date: Sat, 30 May 2009 11:37:53 -0000 Subject: [Haiku-bugs] [Haiku] #3493: Wrong BView scripting properties resolution In-Reply-To: <042.277d5a21d76c3d9280e63ac10d95a86e@haiku-os.org> References: <042.277d5a21d76c3d9280e63ac10d95a86e@haiku-os.org> Message-ID: <051.777d74dfd0e9ffaa912d20bfe2ca970c@haiku-os.org> #3493: Wrong BView scripting properties resolution ---------------------------------+------------------------------------------ Reporter: matjako | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r30920 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 14:20:25 2009 From: trac at haiku-os.org (korli) Date: Sat, 30 May 2009 12:20:25 -0000 Subject: [Haiku-bugs] [Haiku] #3539: cp command doesn't copy symlink's BFS attributes In-Reply-To: <041.dec3e9de3ddbfa59a36467a92b24984a@haiku-os.org> References: <041.dec3e9de3ddbfa59a36467a92b24984a@haiku-os.org> Message-ID: <050.d49626646e5268733a66786850f847b3@haiku-os.org> #3539: cp command doesn't copy symlink's BFS attributes ----------------------------------------------+----------------------------- Reporter: shinta | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------------------+----------------------------- Changes (by korli): * status: new => closed * resolution: => fixed Comment: Fixed in r30921. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 14:29:42 2009 From: trac at haiku-os.org (Stef) Date: Sat, 30 May 2009 12:29:42 -0000 Subject: [Haiku-bugs] [Haiku] #3971: Patch: enable mixed mouse+keyboard input in Sudoku In-Reply-To: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> References: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> Message-ID: <048.1a1965bba11fda8bb82096d14e9263c9@haiku-os.org> #3971: Patch: enable mixed mouse+keyboard input in Sudoku ----------------------------------+----------------------------------------- Reporter: Stef | Owner: axeld Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Resolution: | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by Stef): * status: closed => reopened * resolution: fixed => Comment: Thanks, but the modified patch applied in r30918 still fails when _GetFieldFor returns true but one of the other clauses in the if statement on lines 850-852 passes. This can be seen for instance when there is a number in the cell pointed to by the mouse; it is not possible to change this number with the point-and-type method, as any numbers typed appear in the previous empty cell pointed to. Moving the assignments above the if statement (but obviously after the _GetFieldFor call) as in my original patch allows numbers to be changed without such unexpected behavior. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 14:34:29 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 30 May 2009 12:34:29 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 Message-ID: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> #3978: Update install from CD fails at r30914 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- I'm getting a message "File or directory already exists" and the install stops. A `cp -f`, or a check for the existence of directory before creating, is required somewhere. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 14:46:48 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 12:46:48 -0000 Subject: [Haiku-bugs] [Haiku] #3489: Complete the move from /boot/home/config to /boot/common for optional packages In-Reply-To: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> References: <042.2af3bcd8fba8874f6522bcd0ef8112e7@haiku-os.org> Message-ID: <051.65d898e16a56ceac44388b10c9613a44@haiku-os.org> #3489: Complete the move from /boot/home/config to /boot/common for optional packages --------------------------+------------------------------------------------- Reporter: scottmc | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: --------------------------+------------------------------------------------- Comment(by mmadia): I deleted the attachment, assuming that scott forgot to blank out the IP address at the bottom. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 15:00:39 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 13:00:39 -0000 Subject: [Haiku-bugs] [Haiku] #3979: [patch] remove redundant Yasm from ReleaseBuildProfiles Message-ID: <041.2547f1fcdc0fe75f2f5e2e5697f79e7a@haiku-os.org> #3979: [patch] remove redundant Yasm from ReleaseBuildProfiles --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Missed this with a previous patch. Since Yasm is declared as an OptionalPackageDependencies of DevelopmentBase, it is not necessary to mention it in ReleaseBuildProfiles. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 16:13:19 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 14:13:19 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.76d2b23de1d652810f62ec47c05e39a8@haiku-os.org> #3978: Update install from CD fails at r30914 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by bonefish): How about adding the build output? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 16:32:10 2009 From: trac at haiku-os.org (korli) Date: Sat, 30 May 2009 14:32:10 -0000 Subject: [Haiku-bugs] [Haiku] #3755: [patch] fix extra ( ) in bin/zip/ttyio.h In-Reply-To: <041.233e4bc701f0fea22fa804e6269d0475@haiku-os.org> References: <041.233e4bc701f0fea22fa804e6269d0475@haiku-os.org> Message-ID: <050.97c9dba05cf797a06785f4b59641241a@haiku-os.org> #3755: [patch] fix extra ( ) in bin/zip/ttyio.h ---------------------------+------------------------------------------------ Reporter: mmadia | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Applications | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Changes (by korli): * status: reopened => closed * resolution: => fixed Comment: Applied in r30924 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 16:36:08 2009 From: trac at haiku-os.org (korli) Date: Sat, 30 May 2009 14:36:08 -0000 Subject: [Haiku-bugs] [Haiku] #3771: 'info' in terminal crashes. In-Reply-To: <041.dcb3c64e413e579a4ab8de0a90b6e18b@haiku-os.org> References: <041.dcb3c64e413e579a4ab8de0a90b6e18b@haiku-os.org> Message-ID: <050.11b9ed62219e57094e6b012278b6dd32@haiku-os.org> #3771: 'info' in terminal crashes. ---------------------------------------------+------------------------------ Reporter: kvdman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Command Line Tools | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------------------------+------------------------------ Comment(by korli): Seems to be the optional package texinfo-4.13a-gcc2-2008-11-09 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 16:37:33 2009 From: trac at haiku-os.org (luroh) Date: Sat, 30 May 2009 14:37:33 -0000 Subject: [Haiku-bugs] [Haiku] #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a In-Reply-To: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> References: <040.fdf122ddec4d454f76f81bf077b6fd75@haiku-os.org> Message-ID: <049.a8569bc3e12225d65ab9c6aa3fad1826@haiku-os.org> #3964: PANIC: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x8007481a -----------------------+---------------------------------------------------- Reporter: luroh | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): Also repeatable in VMware. Rev 30923. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:06:44 2009 From: trac at haiku-os.org (fano) Date: Sat, 30 May 2009 15:06:44 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.c079e1f599e005fbafa24eb324bc6925@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by fano): I've tried to set the nv.settings and nvidia.setting files (in my Haiku was only the nv file... to be sure I added the nvidia one, too) to not force wide screen res but nothing is changed... after reboot black screen!!! In a side note what is the right file the nv or the nvidia one? It's pretty confusing... seeing the interior of the files they seems the same! To note that usable resolution in failsafe mode are 640*480 an 800*600 and nothing more! Maybe my monitor is not recognized by Haiku too? In the screen preference there is nothing about the connected screen... how I can know if my monitor is recognized? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:08:57 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 30 May 2009 15:08:57 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.d0cdde9a1eeb1e2b44d02bf0236cc277@haiku-os.org> #3978: Update install from CD fails at r30914 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Builds fine. Problem is in the change to the directory structure. The installer is trying to create symlinks to /boot/develop/headers/cpp and /boot/develop/lib/x86 where directories already exist. These directories need to be deleted or renamed first. The new link to the compiler is also wrong, /boot/develop/tools/gnupro now points to /boot/develop/abi/current/tools/current (broken). -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:12:00 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 30 May 2009 15:12:00 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.896ce7098bdce307e84e4b8dc9d01741@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: reopened Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Comment(by haiqu): Confirmed fixed as at r30914. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:13:10 2009 From: trac at haiku-os.org (haiqu) Date: Sat, 30 May 2009 15:13:10 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 In-Reply-To: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> References: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> Message-ID: <049.8f71239c8e78909fdcec1c3d0465a53f@haiku-os.org> #3968: Can't install from CD at r30851 --------------------------+------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Blockedby: | Platform: x86 Blocking: | --------------------------+------------------------------------------------- Comment(by haiqu): Confirmed fixed as at r30914 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:26:33 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 30 May 2009 15:26:33 -0000 Subject: [Haiku-bugs] [Haiku] #3980: [patch] Keyboard shortcut icon for Apple keyboards Message-ID: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> #3980: [patch] Keyboard shortcut icon for Apple keyboards --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Depending on the keymap chosen in the Keymaps preflet, the keyboard shortcut icon in the menus shows "ALT" or "CTL". This is not appropriate when using an Apple keyboard, which has a Command key.[[BR]] The attached patch adds a "CMD" icon to the shortcut icons, and use it when an Apple keymap is used. It also disables the "Switch Shortcut Keys" in the Keymaps preflet, which does not makes much sense in that case. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:34:11 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 15:34:11 -0000 Subject: [Haiku-bugs] [Haiku] #3940: Can't install from CD at r30790 In-Reply-To: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> References: <040.046103dbbefb059f2431a697ac5ff1cc@haiku-os.org> Message-ID: <049.b7071beb6e82c5ba57cf5b6d44b76283@haiku-os.org> #3940: Can't install from CD at r30790 ------------------------+--------------------------------------------------- Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: - General | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ------------------------+--------------------------------------------------- Changes (by mmadia): * status: reopened => closed * resolution: => fixed Comment: thanks for the confirmation! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:34:27 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 15:34:27 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 In-Reply-To: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> References: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> Message-ID: <049.db8573d47b2ab8942810e01aad66efe6@haiku-os.org> #3968: Can't install from CD at r30851 ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Changes (by mmadia): * status: new => closed * resolution: => fixed Comment: Thanks for the confirmation! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 17:50:06 2009 From: trac at haiku-os.org (bonefish) Date: Sat, 30 May 2009 15:50:06 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.0a1d02f103599bc31ed3370a5f10b768@haiku-os.org> #3978: Update install from CD fails at r30914 ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------------+--------------------------------------- Changes (by bonefish): * owner: bonefish => korli * component: Build System => Applications/Installer -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 18:13:50 2009 From: trac at haiku-os.org (andreasf) Date: Sat, 30 May 2009 16:13:50 -0000 Subject: [Haiku-bugs] [Haiku] #3980: [patch] Keyboard shortcut icon for Apple keyboards In-Reply-To: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> References: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> Message-ID: <050.81f0b6589ce5f43dc51fa94cc04effc2@haiku-os.org> #3980: [patch] Keyboard shortcut icon for Apple keyboards --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by andreasf): * cc: planche2k@? (added) Comment: Your patch introduces a potential {{{NULL}}} dereference of {{{keys}}} in {{{src/kits/interface/Menu.cpp}}}. I'm less certain why in presence of the command key the alt and ctrl alternatives - present on Apple keyboards, too - should be disallowed. But the shortcut icon is a neat idea, I'll have to try it out sometime. :) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 18:15:25 2009 From: trac at haiku-os.org (mmlr) Date: Sat, 30 May 2009 16:15:25 -0000 Subject: [Haiku-bugs] [Haiku] #3968: Can't install from CD at r30851 In-Reply-To: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> References: <040.bf3097e610d8c5abcb42d0de9d347f8b@haiku-os.org> Message-ID: <049.1702bc2ba36dd3da2ecf45a960697e03@haiku-os.org> #3968: Can't install from CD at r30851 ---------------------------+------------------------------------------------ Reporter: haiqu | Owner: axeld Type: bug | Status: closed Priority: normal | Milestone: R1 Component: File Systems | Version: R1 development Resolution: fixed | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Just to clarify, this wasn't a regression. Support for relocated directories has been missing from our iso9660 fs all along. That a CD would be rendered unbootable was caused by the rr_moved pseudo-directory being placed before vital directories in the ISO root directory. This could have been caused by using a different mkisofs or by simply using different build targets or options. If you first built without perl for example it is likely that no relocated directories were created at all, as the directory depth didn't require it. In that case, mentioning those differences in build options or host tools would have been useful in pinpointing the cause down. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 18:19:59 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 16:19:59 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown Message-ID: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- To reproduce: [[BR]] * Open a very large text document. Sample file is attached. [[BR]] * Highlight first few lines. Fewer lines (3~5) allow this bug to be noticed easier.[[BR]] * Hold Shift and press PageDown a few times.[[BR]] [[BR]] Each time Shift+PageDown is pressed the bottom of the highlighted selection creeps upwards by a few pixels. Eventually the highlighted selection migrates out of view. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 18:22:37 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 16:22:37 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown In-Reply-To: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> References: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> Message-ID: <050.0937cb5454435431e84c5999a8c80eb3@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown --------------------------------+------------------------------------------- Reporter: mmadia | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by mmadia): * owner: korli => axeld * component: Applications/StyledEdit => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 18:27:26 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 16:27:26 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown In-Reply-To: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> References: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> Message-ID: <050.03875393a4b5ec5409500353975ed2a6@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by mmadia): * owner: axeld => korli * component: Kits/Interface Kit => Applications/StyledEdit Comment: To clarify, the window scrolls further than it's actually selecting. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 19:05:08 2009 From: trac at haiku-os.org (stippi) Date: Sat, 30 May 2009 17:05:08 -0000 Subject: [Haiku-bugs] [Haiku] #3971: Patch: enable mixed mouse+keyboard input in Sudoku In-Reply-To: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> References: <039.421ef8de14e55896db470bf1f6c80639@haiku-os.org> Message-ID: <048.2257cb60c13a02a38398d7a3ff4e0502@haiku-os.org> #3971: Patch: enable mixed mouse+keyboard input in Sudoku ----------------------------------+----------------------------------------- Reporter: Stef | Owner: axeld Type: enhancement | Status: closed Priority: normal | Milestone: R1 Component: Applications/Sudoku | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ----------------------------------+----------------------------------------- Changes (by stippi): * status: reopened => closed * resolution: => fixed Comment: Sorry about that! I will try to be more careful next time! -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 19:05:55 2009 From: trac at haiku-os.org (zooey) Date: Sat, 30 May 2009 17:05:55 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown In-Reply-To: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> References: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> Message-ID: <050.2a0be49943e5975df7905df737042c5f@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown -------------------------------------+-------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Applications/StyledEdit | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Changes (by zooey): * owner: korli => zooey * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 19:06:13 2009 From: trac at haiku-os.org (zooey) Date: Sat, 30 May 2009 17:06:13 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown In-Reply-To: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> References: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> Message-ID: <050.dbc43c8831fe9d82e8d11c86f9da47b5@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown --------------------------------+------------------------------------------- Reporter: mmadia | Owner: zooey Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Changes (by zooey): * component: Applications/StyledEdit => Kits/Interface Kit -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 19:40:29 2009 From: trac at haiku-os.org (scottmc) Date: Sat, 30 May 2009 17:40:29 -0000 Subject: [Haiku-bugs] [Haiku] #3929: Strange desktop icon behavior In-Reply-To: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> References: <042.10eac06220a2f555684b0e8c8acd2263@haiku-os.org> Message-ID: <051.e6910660b03af57b36f851577dc57ad7@haiku-os.org> #3929: Strange desktop icon behavior ----------------------------------+----------------------------------------- Reporter: scottmc | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Tracker | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------------+----------------------------------------- Comment(by scottmc): still with us as of r30915. This time it happened after an involuntary reboot, my PC overheated and shut itself off... so maybe some setting or something isn't being saved? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 19:59:30 2009 From: trac at haiku-os.org (zooey) Date: Sat, 30 May 2009 17:59:30 -0000 Subject: [Haiku-bugs] [Haiku] #3308: Possible floating point failures in IEEE 754 tests In-Reply-To: <042.c678ed2b992fdb50f53485f9b7f8d349@haiku-os.org> References: <042.c678ed2b992fdb50f53485f9b7f8d349@haiku-os.org> Message-ID: <051.d9bc59518a11f27098709c41fbef8530@haiku-os.org> #3308: Possible floating point failures in IEEE 754 tests -------------------------------+-------------------------------------------- Reporter: scottmc | Owner: zooey Type: bug | Status: assigned Priority: critical | Milestone: R1/alpha1 Component: System/libroot.so | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------+-------------------------------------------- Changes (by zooey): * owner: axeld => zooey * status: new => assigned -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 22:27:02 2009 From: trac at haiku-os.org (stippi) Date: Sat, 30 May 2009 20:27:02 -0000 Subject: [Haiku-bugs] [Haiku] #3978: Update install from CD fails at r30914 In-Reply-To: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> References: <040.3a52c60a95c1c4006f2f2a598f54d9c9@haiku-os.org> Message-ID: <049.758eb0ac4fcc90671271b5cb03884d63@haiku-os.org> #3978: Update install from CD fails at r30914 ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: x86 Blocking: | ------------------------------------+--------------------------------------- Comment(by stippi): I will have a look if no-one beats me to it, but possibly not soon enough. The problem will be in the "CopyEngine" in the Installer source, where it should probably special case creating symlinks. Apparently, it needs to make sure nothing is there before creating them. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 23:06:31 2009 From: trac at haiku-os.org (mmadia) Date: Sat, 30 May 2009 21:06:31 -0000 Subject: [Haiku-bugs] [Haiku] #3982: prevent non-x86 platforms from building vmware images. Message-ID: <041.bead7422b05c705bceaa542a0a5c6e71@haiku-os.org> #3982: prevent non-x86 platforms from building vmware images. --------------------------+------------------------------------------------- Reporter: mmadia | Owner: bonefish Type: enhancement | Status: new Priority: low | Milestone: R1 Component: Build System | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------+------------------------------------------------- Since VMWare only virtualizes x86 platforms, (imo) the build system should prevent a user from attempting to build targets based on 'vmware-image'. I'm not certain if HaikuImage, ImageRules, or MiscRules would be the proper place for this. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 23:08:09 2009 From: trac at haiku-os.org (zooey) Date: Sat, 30 May 2009 21:08:09 -0000 Subject: [Haiku-bugs] [Haiku] #3981: Highlighted selection creeps up when using PageDown In-Reply-To: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> References: <041.daf0c9a9056765e3661c84fd3f6637a4@haiku-os.org> Message-ID: <050.330f7be5c4cb18ac45e47766ad4179d1@haiku-os.org> #3981: Highlighted selection creeps up when using PageDown ---------------------------------+------------------------------------------ Reporter: mmadia | Owner: zooey Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Resolution: fixed | Blockedby: Platform: All | Blocking: ---------------------------------+------------------------------------------ Changes (by zooey): * status: assigned => closed * resolution: => fixed Comment: Fixed in r30933. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sat May 30 23:11:16 2009 From: trac at haiku-os.org (VinDuv) Date: Sat, 30 May 2009 21:11:16 -0000 Subject: [Haiku-bugs] [Haiku] #3980: [patch] Keyboard shortcut icon for Apple keyboards In-Reply-To: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> References: <041.57659cd928b5996efde194b08dc7bdfb@haiku-os.org> Message-ID: <050.29c21281c8633b22b43aa511ce55fcac@haiku-os.org> #3980: [patch] Keyboard shortcut icon for Apple keyboards --------------------------------+------------------------------------------- Reporter: VinDuv | Owner: axeld Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: Kits/Interface Kit | Version: R1 development Blockedby: | Platform: All Blocking: | --------------------------------+------------------------------------------- Comment(by VinDuv): Replying to [comment:1 andreasf]: > Your patch introduces a potential {{{NULL}}} dereference of {{{keys}}} in {{{src/kits/interface/Menu.cpp}}}. Whoops, fixed ;)[[BR]] > I'm less certain why in presence of the command key the alt and ctrl alternatives - present on Apple keyboards, too - should be disallowed. I wasn't sure if it was really useful... Mac users are generally accustomed to using the Command key for keyboard shortcuts, so allow switching to Control is probably not needed.[[BR]] Anyway, I reactivated the button in this new patch and fixed the mode detection so it shows "Switch Shortcut Keys To Windows/Linux Mode" or "Switch Shortcut Keys To Haiku/Mac OS Mode" instead of just "Switch Shortcut Keys" for Apple keymaps. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 07:22:12 2009 From: trac at haiku-os.org (richienyhus) Date: Sun, 31 May 2009 05:22:12 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.7dc690be7bf2878541e7cb1f30690501@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by richienyhus): Well it was worth a try. I downloaded the "nvidia.setting" file from trac as I didn't have on in my file system, so I can't help you with your side note. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 07:47:13 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 05:47:13 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD Message-ID: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ I seem to be able to quite reliably panic Haiku by ejecting an ISO CD that isn't currently mounted. Panic message: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x80078d2e }}} Backtrace: {{{ stack trace for thread 29 "media checker" kernel stack: 0x806a3000 to 0x806a7000 frame caller :function + offset 0 806a68f4 (+ 48) 80065bcd :invoke_debugger_command + 0x00f5 1 806a6924 (+ 64) 800659bd invoke_pipe_segment(debugger_command_pipe*: 0x80137b20, int32: 0, 0x0 "") + 0x0079 2 806a6964 (+ 64) 80065d44 :invoke_debugger_command_pipe + 0x009c 3 806a69a4 (+ 48) 800672f4 ExpressionParser<0x806a6a58>::_ParseCommandPipe(0x806a6a54) + 0x0234 4 806a69d4 (+ 64) 8006672e ExpressionParser<0x806a6a58>::EvaluateCommand(0x80128200 "bt", 0x806a6a54) + 0x02ba 5 806a6a14 (+ 224) 8006871c :evaluate_debug_command + 0x0088 6 806a6af4 (+ 64) 80063a82 kernel_debugger_loop() + 0x01ae 7 806a6b34 (+ 32) 8006494d :kernel_debugger + 0x004d 8 806a6b54 (+ 192) 800648f5 :panic + 0x0029 9 806a6c14 (+ 64) 800ca366 :vm_page_fault + 0x013a 10 806a6c54 (+ 64) 800da571 :page_fault_exception + 0x00d9 11 806a6c94 (+ 12) 800ddc86 :int_bottom + 0x0036 kernel iframe at 0x806a6ca0 (end = 0x806a6cf0) eax 0xdeadbeef ebx 0x811b33f8 ecx 0x811a167c edx 0x811a36d8 esi 0xf edi 0xf ebp 0x806a6e28 esp 0x806a6cd4 eip 0x80078d2e eflags 0x210287 vector: 0xe, error code: 0x0 12 806a6ca0 (+ 392) 80078d2e devfs_ioctl(fs_volume*: 0x811ad730, fs_vnode*: 0x811ae550, 0x811a36d0, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0212 13 806a6e28 (+ 64) 800a7ae4 common_ioctl(file_descriptor*: 0x811adde8, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0038 14 806a6e68 (+ 48) 8009579f fd_ioctl(true, int32: 5, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x005f 15 806a6e98 (+ 80) 80096f12 :_kern_ioctl + 0x0046 16 806a6ee8 (+ 48) 800e98bc :ioctl + 0x001c 17 806a6f18 (+ 64) 8008a5d7 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::GetMediaStatus(0x811b33f8) + 0x0023 18 806a6f58 (+ 32) 8008a2a9 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::UpdateMediaStatusIfNeeded(0x806a0001, 0x0) + 0x0025 19 806a6f78 (+ 64) 8008d731 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatus(0x81998800, 0x8005967d, 0x801276b4, 0x0, int8: 0, 0x806a6ff8, int8: -9, 0x8119faf0, 0x0, 0x0, 0x0, int8: 0, 0x0, 0x0, int32: -2147117420) + 0x008d 20 806a6fb8 (+ 32) 8008d8c2 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatusDaem(NULL) + 0x0012 21 806a6fd8 (+ 32) 800596f7 _create_kernel_thread_kentry() + 0x001b 22 806a6ff8 (+2140508168) 80059694 thread_kthread_exit() + 0x0000 }}} I'd assume this is relatively recent since I don't recall anything like this happening back when I was testing iso9660 bugs for Axel, but that was several hundred revisions ago. In any case, environment is r30933, gcc2 + gcc4 hybrid using the ata bus manager. Let me know what other information I can pull out here. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 07:49:32 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 05:49:32 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.611be3315ac9d251c668d922d7599c60@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Old description: > I seem to be able to quite reliably panic Haiku by ejecting an ISO CD > that isn't currently mounted. Panic message: > > {{{ > PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf1f, > ip 0x80078d2e > }}} > > Backtrace: > {{{ > stack trace for thread 29 "media checker" > kernel stack: 0x806a3000 to 0x806a7000 > frame caller :function + offset > 0 806a68f4 (+ 48) 80065bcd :invoke_debugger_command + > 0x00f5 > 1 806a6924 (+ 64) 800659bd > invoke_pipe_segment(debugger_command_pipe*: 0x80137b20, int32: 0, 0x0 > "") + 0x0079 > 2 806a6964 (+ 64) 80065d44 :invoke_debugger_command_pipe > + 0x009c > 3 806a69a4 (+ 48) 800672f4 > ExpressionParser<0x806a6a58>::_ParseCommandPipe(0x806a6a54) + 0x0234 > 4 806a69d4 (+ 64) 8006672e > ExpressionParser<0x806a6a58>::EvaluateCommand(0x80128200 "bt", > 0x806a6a54) + 0x02ba > 5 806a6a14 (+ 224) 8006871c :evaluate_debug_command + > 0x0088 > 6 806a6af4 (+ 64) 80063a82 kernel_debugger_loop() + > 0x01ae > 7 806a6b34 (+ 32) 8006494d :kernel_debugger + 0x004d > 8 806a6b54 (+ 192) 800648f5 :panic + 0x0029 > 9 806a6c14 (+ 64) 800ca366 :vm_page_fault + 0x013a > 10 806a6c54 (+ 64) 800da571 :page_fault_exception + 0x00d9 > 11 806a6c94 (+ 12) 800ddc86 :int_bottom + 0x0036 > kernel iframe at 0x806a6ca0 (end = 0x806a6cf0) > eax 0xdeadbeef ebx 0x811b33f8 ecx 0x811a167c edx 0x811a36d8 > esi 0xf edi 0xf ebp 0x806a6e28 esp 0x806a6cd4 > eip 0x80078d2e eflags 0x210287 > vector: 0xe, error code: 0x0 > 12 806a6ca0 (+ 392) 80078d2e devfs_ioctl(fs_volume*: > 0x811ad730, fs_vnode*: 0x811ae550, 0x811a36d0, uint32: 0xf (15), > 0x811b33f8, uint32: 0x811a167c) + 0x0212 > 13 806a6e28 (+ 64) 800a7ae4 > common_ioctl(file_descriptor*: 0x811adde8, uint32: 0xf (15), 0x811b33f8, > uint32: 0x811a167c) + 0x0038 > 14 806a6e68 (+ 48) 8009579f fd_ioctl(true, int32: 5, > uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x005f > 15 806a6e98 (+ 80) 80096f12 :_kern_ioctl + 0x0046 > 16 806a6ee8 (+ 48) 800e98bc :ioctl + 0x001c > 17 806a6f18 (+ 64) 8008a5d7 > BPrivate::DiskDevice::KDiskDevice<0x811b3300>::GetMediaStatus(0x811b33f8) > + 0x0023 > 18 806a6f58 (+ 32) 8008a2a9 > BPrivate::DiskDevice::KDiskDevice<0x811b3300>::UpdateMediaStatusIfNeeded(0x806a0001, > 0x0) + 0x0025 > 19 806a6f78 (+ 64) 8008d731 > BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatus(0x81998800, > 0x8005967d, 0x801276b4, 0x0, int8: 0, 0x806a6ff8, int8: -9, 0x8119faf0, > 0x0, 0x0, 0x0, int8: 0, 0x0, 0x0, int32: -2147117420) + 0x008d > 20 806a6fb8 (+ 32) 8008d8c2 > BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatusDaem(NULL) > + 0x0012 > 21 806a6fd8 (+ 32) 800596f7 > _create_kernel_thread_kentry() + 0x001b > 22 806a6ff8 (+2140508168) 80059694 thread_kthread_exit() + > 0x0000 > }}} > > I'd assume this is relatively recent since I don't recall anything like > this happening back when I was testing iso9660 bugs for Axel, but that > was several hundred revisions ago. In any case, environment is r30933, > gcc2 + gcc4 hybrid using the ata bus manager. Let me know what other > information I can pull out here. New description: I seem to be able to quite reliably panic Haiku by an iso9660 CD. Panic message: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x80078d2e }}} Backtrace: {{{ stack trace for thread 29 "media checker" kernel stack: 0x806a3000 to 0x806a7000 frame caller :function + offset 0 806a68f4 (+ 48) 80065bcd :invoke_debugger_command + 0x00f5 1 806a6924 (+ 64) 800659bd invoke_pipe_segment(debugger_command_pipe*: 0x80137b20, int32: 0, 0x0 "") + 0x0079 2 806a6964 (+ 64) 80065d44 :invoke_debugger_command_pipe + 0x009c 3 806a69a4 (+ 48) 800672f4 ExpressionParser<0x806a6a58>::_ParseCommandPipe(0x806a6a54) + 0x0234 4 806a69d4 (+ 64) 8006672e ExpressionParser<0x806a6a58>::EvaluateCommand(0x80128200 "bt", 0x806a6a54) + 0x02ba 5 806a6a14 (+ 224) 8006871c :evaluate_debug_command + 0x0088 6 806a6af4 (+ 64) 80063a82 kernel_debugger_loop() + 0x01ae 7 806a6b34 (+ 32) 8006494d :kernel_debugger + 0x004d 8 806a6b54 (+ 192) 800648f5 :panic + 0x0029 9 806a6c14 (+ 64) 800ca366 :vm_page_fault + 0x013a 10 806a6c54 (+ 64) 800da571 :page_fault_exception + 0x00d9 11 806a6c94 (+ 12) 800ddc86 :int_bottom + 0x0036 kernel iframe at 0x806a6ca0 (end = 0x806a6cf0) eax 0xdeadbeef ebx 0x811b33f8 ecx 0x811a167c edx 0x811a36d8 esi 0xf edi 0xf ebp 0x806a6e28 esp 0x806a6cd4 eip 0x80078d2e eflags 0x210287 vector: 0xe, error code: 0x0 12 806a6ca0 (+ 392) 80078d2e devfs_ioctl(fs_volume*: 0x811ad730, fs_vnode*: 0x811ae550, 0x811a36d0, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0212 13 806a6e28 (+ 64) 800a7ae4 common_ioctl(file_descriptor*: 0x811adde8, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0038 14 806a6e68 (+ 48) 8009579f fd_ioctl(true, int32: 5, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x005f 15 806a6e98 (+ 80) 80096f12 :_kern_ioctl + 0x0046 16 806a6ee8 (+ 48) 800e98bc :ioctl + 0x001c 17 806a6f18 (+ 64) 8008a5d7 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::GetMediaStatus(0x811b33f8) + 0x0023 18 806a6f58 (+ 32) 8008a2a9 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::UpdateMediaStatusIfNeeded(0x806a0001, 0x0) + 0x0025 19 806a6f78 (+ 64) 8008d731 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatus(0x81998800, 0x8005967d, 0x801276b4, 0x0, int8: 0, 0x806a6ff8, int8: -9, 0x8119faf0, 0x0, 0x0, 0x0, int8: 0, 0x0, 0x0, int32: -2147117420) + 0x008d 20 806a6fb8 (+ 32) 8008d8c2 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatusDaem(NULL) + 0x0012 21 806a6fd8 (+ 32) 800596f7 _create_kernel_thread_kentry() + 0x001b 22 806a6ff8 (+2140508168) 80059694 thread_kthread_exit() + 0x0000 }}} I'd assume this is relatively recent since I don't recall anything like this happening back when I was testing iso9660 bugs for Axel, but that was several hundred revisions ago. In any case, environment is r30933, gcc2 + gcc4 hybrid using the ata bus manager. Let me know what other information I can pull out here. -- Comment(by anevilyak): On second thought, it KDLs if the disc is mounted also. Updated description accordingly. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 07:50:35 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 05:50:35 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.b132ac221c066d403a8ade3f313f897b@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Description changed by anevilyak: Old description: > I seem to be able to quite reliably panic Haiku by an iso9660 CD. Panic > message: > > {{{ > PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf1f, > ip 0x80078d2e > }}} > > Backtrace: > {{{ > stack trace for thread 29 "media checker" > kernel stack: 0x806a3000 to 0x806a7000 > frame caller :function + offset > 0 806a68f4 (+ 48) 80065bcd :invoke_debugger_command + > 0x00f5 > 1 806a6924 (+ 64) 800659bd > invoke_pipe_segment(debugger_command_pipe*: 0x80137b20, int32: 0, 0x0 > "") + 0x0079 > 2 806a6964 (+ 64) 80065d44 :invoke_debugger_command_pipe > + 0x009c > 3 806a69a4 (+ 48) 800672f4 > ExpressionParser<0x806a6a58>::_ParseCommandPipe(0x806a6a54) + 0x0234 > 4 806a69d4 (+ 64) 8006672e > ExpressionParser<0x806a6a58>::EvaluateCommand(0x80128200 "bt", > 0x806a6a54) + 0x02ba > 5 806a6a14 (+ 224) 8006871c :evaluate_debug_command + > 0x0088 > 6 806a6af4 (+ 64) 80063a82 kernel_debugger_loop() + > 0x01ae > 7 806a6b34 (+ 32) 8006494d :kernel_debugger + 0x004d > 8 806a6b54 (+ 192) 800648f5 :panic + 0x0029 > 9 806a6c14 (+ 64) 800ca366 :vm_page_fault + 0x013a > 10 806a6c54 (+ 64) 800da571 :page_fault_exception + 0x00d9 > 11 806a6c94 (+ 12) 800ddc86 :int_bottom + 0x0036 > kernel iframe at 0x806a6ca0 (end = 0x806a6cf0) > eax 0xdeadbeef ebx 0x811b33f8 ecx 0x811a167c edx 0x811a36d8 > esi 0xf edi 0xf ebp 0x806a6e28 esp 0x806a6cd4 > eip 0x80078d2e eflags 0x210287 > vector: 0xe, error code: 0x0 > 12 806a6ca0 (+ 392) 80078d2e devfs_ioctl(fs_volume*: > 0x811ad730, fs_vnode*: 0x811ae550, 0x811a36d0, uint32: 0xf (15), > 0x811b33f8, uint32: 0x811a167c) + 0x0212 > 13 806a6e28 (+ 64) 800a7ae4 > common_ioctl(file_descriptor*: 0x811adde8, uint32: 0xf (15), 0x811b33f8, > uint32: 0x811a167c) + 0x0038 > 14 806a6e68 (+ 48) 8009579f fd_ioctl(true, int32: 5, > uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x005f > 15 806a6e98 (+ 80) 80096f12 :_kern_ioctl + 0x0046 > 16 806a6ee8 (+ 48) 800e98bc :ioctl + 0x001c > 17 806a6f18 (+ 64) 8008a5d7 > BPrivate::DiskDevice::KDiskDevice<0x811b3300>::GetMediaStatus(0x811b33f8) > + 0x0023 > 18 806a6f58 (+ 32) 8008a2a9 > BPrivate::DiskDevice::KDiskDevice<0x811b3300>::UpdateMediaStatusIfNeeded(0x806a0001, > 0x0) + 0x0025 > 19 806a6f78 (+ 64) 8008d731 > BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatus(0x81998800, > 0x8005967d, 0x801276b4, 0x0, int8: 0, 0x806a6ff8, int8: -9, 0x8119faf0, > 0x0, 0x0, 0x0, int8: 0, 0x0, 0x0, int32: -2147117420) + 0x008d > 20 806a6fb8 (+ 32) 8008d8c2 > BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatusDaem(NULL) > + 0x0012 > 21 806a6fd8 (+ 32) 800596f7 > _create_kernel_thread_kentry() + 0x001b > 22 806a6ff8 (+2140508168) 80059694 thread_kthread_exit() + > 0x0000 > }}} > > I'd assume this is relatively recent since I don't recall anything like > this happening back when I was testing iso9660 bugs for Axel, but that > was several hundred revisions ago. In any case, environment is r30933, > gcc2 + gcc4 hybrid using the ata bus manager. Let me know what other > information I can pull out here. New description: I seem to be able to quite reliably panic Haiku by ejecting an iso9660 CD. Panic message: {{{ PANIC: vm_page_fault: unhandled page fault in kernel space at 0xdeadbf1f, ip 0x80078d2e }}} Backtrace: {{{ stack trace for thread 29 "media checker" kernel stack: 0x806a3000 to 0x806a7000 frame caller :function + offset 0 806a68f4 (+ 48) 80065bcd :invoke_debugger_command + 0x00f5 1 806a6924 (+ 64) 800659bd invoke_pipe_segment(debugger_command_pipe*: 0x80137b20, int32: 0, 0x0 "") + 0x0079 2 806a6964 (+ 64) 80065d44 :invoke_debugger_command_pipe + 0x009c 3 806a69a4 (+ 48) 800672f4 ExpressionParser<0x806a6a58>::_ParseCommandPipe(0x806a6a54) + 0x0234 4 806a69d4 (+ 64) 8006672e ExpressionParser<0x806a6a58>::EvaluateCommand(0x80128200 "bt", 0x806a6a54) + 0x02ba 5 806a6a14 (+ 224) 8006871c :evaluate_debug_command + 0x0088 6 806a6af4 (+ 64) 80063a82 kernel_debugger_loop() + 0x01ae 7 806a6b34 (+ 32) 8006494d :kernel_debugger + 0x004d 8 806a6b54 (+ 192) 800648f5 :panic + 0x0029 9 806a6c14 (+ 64) 800ca366 :vm_page_fault + 0x013a 10 806a6c54 (+ 64) 800da571 :page_fault_exception + 0x00d9 11 806a6c94 (+ 12) 800ddc86 :int_bottom + 0x0036 kernel iframe at 0x806a6ca0 (end = 0x806a6cf0) eax 0xdeadbeef ebx 0x811b33f8 ecx 0x811a167c edx 0x811a36d8 esi 0xf edi 0xf ebp 0x806a6e28 esp 0x806a6cd4 eip 0x80078d2e eflags 0x210287 vector: 0xe, error code: 0x0 12 806a6ca0 (+ 392) 80078d2e devfs_ioctl(fs_volume*: 0x811ad730, fs_vnode*: 0x811ae550, 0x811a36d0, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0212 13 806a6e28 (+ 64) 800a7ae4 common_ioctl(file_descriptor*: 0x811adde8, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x0038 14 806a6e68 (+ 48) 8009579f fd_ioctl(true, int32: 5, uint32: 0xf (15), 0x811b33f8, uint32: 0x811a167c) + 0x005f 15 806a6e98 (+ 80) 80096f12 :_kern_ioctl + 0x0046 16 806a6ee8 (+ 48) 800e98bc :ioctl + 0x001c 17 806a6f18 (+ 64) 8008a5d7 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::GetMediaStatus(0x811b33f8) + 0x0023 18 806a6f58 (+ 32) 8008a2a9 BPrivate::DiskDevice::KDiskDevice<0x811b3300>::UpdateMediaStatusIfNeeded(0x806a0001, 0x0) + 0x0025 19 806a6f78 (+ 64) 8008d731 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatus(0x81998800, 0x8005967d, 0x801276b4, 0x0, int8: 0, 0x806a6ff8, int8: -9, 0x8119faf0, 0x0, 0x0, 0x0, int8: 0, 0x0, 0x0, int32: -2147117420) + 0x008d 20 806a6fb8 (+ 32) 8008d8c2 BPrivate::DiskDevice::KDiskDeviceManager<0x8119faf0>::_CheckMediaStatusDaem(NULL) + 0x0012 21 806a6fd8 (+ 32) 800596f7 _create_kernel_thread_kentry() + 0x001b 22 806a6ff8 (+2140508168) 80059694 thread_kthread_exit() + 0x0000 }}} I'd assume this is relatively recent since I don't recall anything like this happening back when I was testing iso9660 bugs for Axel, but that was several hundred revisions ago. In any case, environment is r30933, gcc2 + gcc4 hybrid using the ata bus manager. Let me know what other information I can pull out here. -- -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 07:52:53 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 05:52:53 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.4940cea60cd3e8febb548ac645809e1e@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): Note also, in the mounted case, the panic occurs after the CD has ejected and the volume has been removed from the desktop. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 12:42:08 2009 From: trac at haiku-os.org (rossi) Date: Sun, 31 May 2009 10:42:08 -0000 Subject: [Haiku-bugs] [Haiku] #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted Message-ID: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted ----------------------------+----------------------------------------------- Reporter: rossi | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Playback of .wav files (BeBeep.wav, BeStartup.wav from the original R5 cd) is heavily distorted. MP3 files playback fine however. This used to work in the past, however I don't recollect the revision, which broke this behaviour, sorry. Can be tested using the Sounds preference panel or MediaPlayer, both show the same behaviour (naturally). OSS is used as sound driver, since the hda driver doesn't work my hardware (Lifebook Q2010) Revision is r30934. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 12:48:11 2009 From: trac at haiku-os.org (bonefish) Date: Sun, 31 May 2009 10:48:11 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.bfe551774d547821802ab4cdd2f07f87@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by bonefish): Helpful information might be: "vnode" on the "fs_vnode*" parameter of devfs_ioctl() and a "devfs_node" for the printed "private_node". -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 13:32:23 2009 From: trac at haiku-os.org (luroh) Date: Sun, 31 May 2009 11:32:23 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.de582212efc5b13b1b2de45ed345b160@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by luroh): #3962 and #3964 look related, fwiw. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 13:44:49 2009 From: trac at haiku-os.org (luroh) Date: Sun, 31 May 2009 11:44:49 -0000 Subject: [Haiku-bugs] [Haiku] #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted In-Reply-To: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> References: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> Message-ID: <049.c1cd2aec9f0b274676d1ab6cc088629c@haiku-os.org> #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted ----------------------------+----------------------------------------------- Reporter: rossi | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by luroh): Dupe of #3849? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 13:52:13 2009 From: trac at haiku-os.org (rossi) Date: Sun, 31 May 2009 11:52:13 -0000 Subject: [Haiku-bugs] [Haiku] #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted In-Reply-To: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> References: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> Message-ID: <049.58a69d4c61f0b4563b9e6d9f13678e31@haiku-os.org> #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted ----------------------------+----------------------------------------------- Reporter: rossi | Owner: marcusoverhagen Type: bug | Status: new Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Blockedby: | Platform: All Blocking: | ----------------------------+----------------------------------------------- Comment(by rossi): Sorry, my mistake, must have overlooked that ticket, when searching for existing ti9ckets concerning this issue. Should browse all tickets and not just query the summaries for certain words (like wav) in this case ;-) Sorry, please close as dupe. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 13:53:45 2009 From: trac at haiku-os.org (rossi) Date: Sun, 31 May 2009 11:53:45 -0000 Subject: [Haiku-bugs] [Haiku] #3849: Audio files with distorted sound. In-Reply-To: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> References: <042.736e2ba5582be9d4a905b66f473ec85a@haiku-os.org> Message-ID: <051.df9b0a2725552ed842e42e3befa6d008@haiku-os.org> #3849: Audio files with distorted sound. ----------------------------------+----------------------------------------- Reporter: bbjimmy | Owner: dlmcpaul Type: bug | Status: new Priority: normal | Milestone: R1 Component: Audio & Video/Codecs | Version: R1 development Blockedby: | Platform: x86 Blocking: | ----------------------------------+----------------------------------------- Changes (by rossi): * cc: rossi@? (added) -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 14:25:25 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 31 May 2009 12:25:25 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.079d6a3db268365068c323066637f6b7@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Hi, You need nvidia.settings. With old driverversions it was nv.settings: but the driver (and accompaning settings file) was at some point renamed by Axel for clarity reasons. Please, place that file in your home folder and enable full logging. Please upload the resulting logfile from a reboot (try to restart from user-started kdl or something blindly if you have no picture.) If you have a 4:3 aspect screen also set force_ws to false please. Can you tell us what the brand and type of the screen is you are using? Also: you could upload syslog: it should have an entry for DDC/EDID for your screen and it names the nvidia card somewhere. Thanks! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 14:25:45 2009 From: trac at haiku-os.org (luroh) Date: Sun, 31 May 2009 12:25:45 -0000 Subject: [Haiku-bugs] [Haiku] #2651: KDL during startup In-Reply-To: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> References: <044.d3050de555a4cbac2a89282676c7b589@haiku-os.org> Message-ID: <053.65766c5eaa15f749ec7f6e213610946b@haiku-os.org> #2651: KDL during startup -----------------------+---------------------------------------------------- Reporter: j_freeman | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by luroh): j_freeman: is this ticket still valid? -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 14:32:34 2009 From: trac at haiku-os.org (rudolfc) Date: Sun, 31 May 2009 12:32:34 -0000 Subject: [Haiku-bugs] [Haiku] #2780: Video out of range on GeForce 6100 (KM51G-754) In-Reply-To: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> References: <046.76cb332d913612d99e9a4f2e6ef2809e@haiku-os.org> Message-ID: <055.bccdcf8088aaf05d5245f2fe791cf401@haiku-os.org> #2780: Video out of range on GeForce 6100 (KM51G-754) -------------------------------------+-------------------------------------- Reporter: richienyhus | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------------------+-------------------------------------- Comment(by rudolfc): Thanks! Your monitor looks like a ordinary type, 1280x1024 can be done at 75Hz for instance, and all normal VESA lower res modes should work. Maybe you can test connecting your screen with a DVI cable if your card has a DVI connector. If so, I'd like to hear what happens then and I'd like a logfile from that as well. On a sidenote: The driver is not able to init any I2C bus on your card. EDID will therefore not work from the driver. Strange. Looks like missing hardware specs. If I search the net I find linux users with the same sort of problem: I2C doesn't work on 6100... However: if this doesn't work that still doesn't mean the driver can't properly use your card and screen. If all is right (apart from I2C). Bye! Rudolf. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 16:11:27 2009 From: trac at haiku-os.org (idefix) Date: Sun, 31 May 2009 14:11:27 -0000 Subject: [Haiku-bugs] [Haiku] #3985: ActivityMonitor crashes when adding view with keyboard Message-ID: <041.821c2834e037a86eece8dcd38e495137@haiku-os.org> #3985: ActivityMonitor crashes when adding view with keyboard ------------------------------------------+--------------------------------- Reporter: idefix | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/ActivityMonitor | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------------+--------------------------------- When you add a view in ActivityMonitor (r30933, VMWare) with the keyboard it crashes. When you use the mouse it won't crash. Steps to reproduce: - Open ActivityMonitor - Press [Alt]-[Esc], the File-menu will open - Press [Enter] - ActivityMonitor expands and then crashes Serial-log output: {{{ void AddOnManager::MessageReceived(BMessage *) what: vdwI void AddOnManager::MessageReceived(BMessage *) what: vdwI void AddOnManager::MessageReceived(BMessage *) what: vdwI malloc() of 4294967240 bytes asked 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 0x21150d, write 1, user 1, thread 0xdf vm_page_fault: thread "w>ActivityMonitor" (223) in team "ActivityMonitor" (216) tried to write address 0x0, ip 0x21150d ("ActivityMonitor_seg0ro" +0x1150d) debug_server: Thread 223 entered the debugger: Segment violation stack trace, current PC 0x21150d Update__11ViewHistoryP11DataHistoryllxxx + 0x241: (0x70102a78) 0x216104 _DrawHistory__12ActivityViewb + 0x4d4 (0x70102b88) 0x216594 Draw__12ActivityViewG5BRect + 0x64 (0x70102c58) 0x3216d9 Draw__8BDraggerG5BRect + 0x161 (0x70102cfc) 0x399bd4 _Draw__5BViewG5BRect + 0x94 (0x70102d3c) 0x39e4b9 DispatchMessage__7BWindowP8BMessageP8BHandler + 0x145d (0x70102f1c) 0x3a2088 task_looper__7BWindow + 0x270 (0x70102f7c) 0x2e413f _task0___7BLooperPv + 0x3f (0x70102fac) 0x7caaec thread_entry + 0x20 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 16:19:18 2009 From: trac at haiku-os.org (fano) Date: Sun, 31 May 2009 14:19:18 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.a8c0a3ebfc43bfd2b4831df5d359b697@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by fano): I don't know how to enable full logging... I've tried to set all the bits of the logbitmask at 1, that is: logmask 0xFFFFFFFF But after reboot I've a very short file... maybe incomplete too... I simply don't know when exit from the "black screen" the keyboard don't respond... I've to do a hard reset! I've collected syslog too... maybe this is more useful: my monitor is correctly recognized as Sony SDM-HS95P connected via VGA. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 16:24:48 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 14:24:48 -0000 Subject: [Haiku-bugs] [Haiku] #3983: KDL when ejecting not mounted CD In-Reply-To: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> References: <044.6484782aa7b86206c1b9803b06a42318@haiku-os.org> Message-ID: <053.e769a4884e7eb607d3fbe815142c1675@haiku-os.org> #3983: KDL when ejecting not mounted CD ---------------------------+------------------------------------------------ Reporter: anevilyak | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1 development Blockedby: | Platform: All Blocking: | ---------------------------+------------------------------------------------ Comment(by anevilyak): {{{ kdebug> vnode 0x811ae550 VNODE: 0x811ae550 device: 2 id: 9 ref_count: 1 private_node: 0x811bc440 mount: 0x811bb438 covered_by: 0x00000000 cache: 0x00000000 flags: --- advisory_lock: 0x00000000 kdebug> devfs_node 0x811bc440 DEVFS NODE: 0x811bc440 id: 9 name: "raw" type: 21a4 parent: 0x811bc400 dir next: 0x00000000 device: 0x811b20b0 node: 0xdeadbeef partition: 0x00000000 }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 16:42:30 2009 From: trac at haiku-os.org (tigerdog) Date: Sun, 31 May 2009 14:42:30 -0000 Subject: [Haiku-bugs] [Haiku] #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 In-Reply-To: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> References: <039.4bfb2d61bcd7320f493569858adbe572@haiku-os.org> Message-ID: <048.2b1012d3e26a1716cbd223f6a7fd1e2b@haiku-os.org> #1026: Black screen when Haiku switch to graphical mode after bootscreen GeForce 6150 -------------------------------------+-------------------------------------- Reporter: acca | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1 development Blockedby: | Platform: x86 Blocking: | -------------------------------------+-------------------------------------- Comment(by tigerdog): This sounds similar to the trouble I have here with a 5600 card. Haiku is unable to distinguish my monitor's max supported resolution and tries to start in a mode higher than the monitor supports. I work around it by hitting space during boot, manually setting fail-safe video mode to 120x1024 then choosing safe mode options and use fail-safe video. Once the system starts, I choose a _different_ supported resolution using Screen Preferences. After this, a restart brings the system up normally and I can set my desired mode which stays permanently. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 16:44:24 2009 From: trac at haiku-os.org (anevilyak) Date: Sun, 31 May 2009 14:44:24 -0000 Subject: [Haiku-bugs] [Haiku] #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted In-Reply-To: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> References: <040.9ffd62046a510bec5a493c5bf30f10e4@haiku-os.org> Message-ID: <049.4d62a0e810812d4756104b2180d23f83@haiku-os.org> #3984: Playback of .wav files (BeBeep.wav, BeStartup.wav) is heavily distorted -----------------------------+---------------------------------------------- Reporter: rossi | Owner: marcusoverhagen Type: bug | Status: closed Priority: normal | Milestone: R1 Component: Kits/Media Kit | Version: R1 development Resolution: duplicate | Blockedby: 3849 Platform: All | Blocking: -----------------------------+---------------------------------------------- Changes (by anevilyak): * status: new => closed * resolution: => duplicate * blockedby: => 3849 -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 23:22:02 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 31 May 2009 21:22:02 -0000 Subject: [Haiku-bugs] [Haiku] #3734: BFS formatted USB memory stick not found In-Reply-To: <040.d6f14de0d71fa1439e2b7387478e17d8@haiku-os.org> References: <040.d6f14de0d71fa1439e2b7387478e17d8@haiku-os.org> Message-ID: <049.be80501b976144498003f45ce0c92df5@haiku-os.org> #3734: BFS formatted USB memory stick not found -----------------------+---------------------------------------------------- Reporter: haiqu | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: x86 Blocking: | -----------------------+---------------------------------------------------- Comment(by haiqu): It's better. I can mount, copy to and extract data from a BFS formatted USB stick now. Unmounting causes a kernel page fault. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 23:27:51 2009 From: trac at haiku-os.org (augiedoggie) Date: Sun, 31 May 2009 21:27:51 -0000 Subject: [Haiku-bugs] [Haiku] #3986: problem with ls command (symlink traversal bug?) Message-ID: <046.a6e8b822c4ad273d1c8bb258cf9fafbf@haiku-os.org> #3986: problem with ls command (symlink traversal bug?) -------------------------+-------------------------------------------------- Reporter: augiedoggie | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -------------------------+-------------------------------------------------- I've noticed that the 'ls' command is printing errors when listing certain directories, but the problem doesn't occur if you 'cd' to the directory and then list the files. (The problem also goes away if you 'unalias ls' or run /bin/ls) For example: {{{ ~> ls /boot/develop/tools/gnupro ls: cannot access /boot/develop/tools/gnupro/COPYING: Not a directory ls: cannot access /boot/develop/tools/gnupro/COPYING.LIB: Not a directory ls: cannot access /boot/develop/tools/gnupro/bin: Not a directory ls: cannot access /boot/develop/tools/gnupro/i586-pc-haiku: Not a directory ls: cannot access /boot/develop/tools/gnupro/include: Not a directory ls: cannot access /boot/develop/tools/gnupro/info: Not a directory ls: cannot access /boot/develop/tools/gnupro/lib: Not a directory ls: cannot access /boot/develop/tools/gnupro/man: Not a directory COPYING COPYING.LIB bin i586-pc-haiku include info lib man ~> }}} -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 23:31:29 2009 From: trac at haiku-os.org (haiqu) Date: Sun, 31 May 2009 21:31:29 -0000 Subject: [Haiku-bugs] [Haiku] #3959: Wrong HDD size shown In-Reply-To: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> References: <040.7c12e4d36c06863363b42809127537a3@haiku-os.org> Message-ID: <049.11a14820cb2b78b70ce9d240fc3017a3@haiku-os.org> #3959: Wrong HDD size shown ------------------------------------+--------------------------------------- Reporter: haiqu | Owner: korli Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Installer | Version: R1 development Blockedby: | Platform: All Blocking: | ------------------------------------+--------------------------------------- Comment(by haiqu): The panel "Woof Info" in the snapshot shows what the system thinks is there when doing a "right-click, Get Info" on the drive. It's seen as 18.1Gb which is correct. I'm now attaching a snapshot of the boot sector of that partition, but I don't think it will provide any further information. > what does "Partition 4 was not available to set up as BFS from Haiku, so it was formatted as FAT32 from WinXP." mean? why wasn't it available? what do you want to say? OK, that needs clarifying. If I go into DriveSetup and try to initialize that partition, the option is greyed out. I had no such problem with Partition 3 but, if you look at the first snapshot you can see that it's still narked in the partition table as type 06 (fat16, dos 3.31) which isn't right and indicates that DriveSetup only changed the bbot sector of partition 3 and not the partition table. However, since I have no problems at all with partition 3 it wasn't mentioned in the report. -- Ticket URL: Haiku The Haiku operating system. From trac at haiku-os.org Sun May 31 23:58:03 2009 From: trac at haiku-os.org (siarzhuk) Date: Sun, 31 May 2009 21:58:03 -0000 Subject: [Haiku-bugs] [Haiku] #3399: The system reboots while running jam -q on the haiku trunk. In-Reply-To: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> References: <042.61a9b9d0d71ab520cf9ea8ba1a11e169@haiku-os.org> Message-ID: <051.02908290b726e75dd5175355a0c55e8f@haiku-os.org> #3399: The system reboots while running jam -q on the haiku trunk. -----------------------+---------------------------------------------------- Reporter: bbjimmy | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1 development Blockedby: | Platform: All Blocking: | -----------------------+---------------------------------------------------- Comment(by siarzhuk): Just for information: I observe the same symptoms regularly and not only during building Haiku. Sometime it occurs during building other programs like vim or mc, sometimes during performing configure scripts of mentioned programs. At least one of three builds ends with this "unrequested" reboot. Note that for about of week working under Haiku GCC4 I have not observed this behavior at all. Looks like this is only GCC2 version issue. At least on my hardware. ;-) My system is like follow: - Intel Pentium M Prozessor 740 (1,73 GHz, 2 MB L2 Cache, FSB 533) - Intel 915 PM Chipsatz und Intel PRO/Wireless 2200 - ATI Mobility Radeon X700 XL PCI-Express mit 128 MB DDR RAM - SAMSUNG Festplatte 100 GB mit 5.400 U/min und 8 MB Cache - 1024 MB DDR II RAM (Beide Speicherb?nke belegt) Detailed description of my system is attached to ticket #1236. -- Ticket URL: Haiku The Haiku operating system.