Latest Bugs & Tasks

Syndicate content Haiku
Trac Timeline
Updated: 1 min 35 sec ago

Ticket #12640 (Tracker's Find will search for file inside the Trash also if I uncheck ...) created

3 min 16 sec ago

Look at the attached image: if I uncheck "Include Trash", the Tracker's Find will however search also inside the Trash.

Categories: Development

Ticket #9438 (Mixer not resampling very well) reopened

Mon, 2016-02-08 22:55

I'm sorry to say that I still get this problem (hrev49993), just as it was before! Did something get regressed?

Categories: Development

Ticket #12258 ([launch_daemon] increased boot time) closed

Sat, 2016-02-06 17:57

The launch_daemon is started when the rocket icon lits up.

Categories: Development

Ticket #12258 ([launch_daemon] increased boot time) reopened

Sat, 2016-02-06 00:49


I see that this ticket is closed as fixed, but I experienced an evident boot delay with hrev50067, where the launch_daemon is present. The last time that i run Haiku on my computer (Pentium dual core E5300 @ 2.60GHz - 6 GB DDR3 of ram) was about one year ago, and the boot time was fairly quick (on my system I have the same hpkgs and the same settings).
But now, on hrev50067, I noticed that the boot screen will delay for about 12 seconds at the disk icon.This delay is also occurred when I reinstalled Haiku, so without any hpkgs and without startup items.
and is never happened for me the last time that I booted Haiku one year ago.

EDIT: the serial debug output is disabled in the kernel file.

I attempted to run the boot_time_logger, then I opened the boot_time log and there was only a message which stated "Failed to get a reply for application/x-vnd.Haiku-cddb_daemon"; in facts the cddb_daemon is not currently active on my system, although that is present in the file /boot/system/data/launch/system

Maybe is due to this bug ticket:12634 ?

Categories: Development

Ticket #12639 (spam) closed

Fri, 2016-02-05 12:54
Categories: Development

Ticket #12639 (spam) created

Fri, 2016-02-05 11:22


Categories: Development

Ticket #12638 (I'm using launch_daemon to start an application at boot, but I can no ...) created

Thu, 2016-02-04 22:03


Well, as I've said in the subject of this ticket, I'm currently using the launch daemon to run an app at startup: polipo proxy, a cli app ​

Before of the introduction of the launch daemon, I usually launch polipo using a bash script placed in /boot/home/config/settings/boot/launch.
Now, instead, I made a configuration file called "polipo", placed inside /boot/system/data/user_launch with the following content:

	service x-vnd.Polipo-Proxy {
		launch /bin/polipo

Everything works fine except for the fact that when I attempt to reboot or shutdown Haiku, an alert window told me that "polipo might be blocked on a modal panel during shutdown". I also tried to make a shutdown script where I try to pass the command "kill polipo", but the situation is always the same. I properly set the signature for polipo "application/x-vnd.Polipo-Proxy".
Inside the syslog I don't see anything related to polipo or to the launch_daemon.
I miss something?

Categories: Development

Ticket #12636 (The notification server starts to peg one core of the cpu) created

Wed, 2016-02-03 14:44


Hi, is the second time in three days which I see this behaviour from the notification server: suddenly, regardless from the presence of active notifications, the notification server starts to peg one core of the cpu.

If i quit the notification_server (eg. using "hey") after the issue and then I start it again, notifications no longer work: I have to reboot Haiku to see again the notifications (I can confirm this behaviour by using the "notify" command).

Unfortunately, due to the ticket:12634 I am not able to investigate into the syslog file.

IIRC (I'm back on Haiku recently) under "/home/config/settings" there was some setting/preference file of the notification server, but I don't see nothing of related (maybe I'm wrong).

Categories: Development

Ticket #12632 (My /home/.profile file (with Terminal's customizations) is ignored.) closed

Wed, 2016-02-03 07:12
no change required:

Some time back all the dot-files in "home" moved to ~/config/settings/ and lost their ".". Move your .profile to ~/config/settings/profile and it should work.

Categories: Development

Ticket #12633 (Kernel fails to load on OptiPlex 960) closed

Wed, 2016-02-03 00:52

resolved in hrev50070. Let me know if anyone knows why :-\

Categories: Development

Ticket #12635 (An old BeOS app (source files attached) which no longer properly works on ...) created

Wed, 2016-02-03 00:29


The last time that I succesfully run this app called Replitext, was about one year ago, on Haiku.

Replitxt is a transparent text desktop replicant which can display various and dynamic text messages using scripting.

eg: print the current date inside the replicant:

~> time=$(date +"%d/%b/%Y - %R %p ")

Get IDs from the replicants:

~> replitxt --list

Insert the current date into Replitxt:

~> replitxt --text $ReplicantID "Current time: ${time} "

and we'll see:

And so on: as I've said is - was - possible send various inputs, via scripting, to the replicant.
I say *was possible* since in the latest nightly builds, when I attempt to run the command

~> replitxt --list

All that I get is the following error:

shelf_messenger not found (Bad port ID)
There are 0 replitxt replicants out of 0 replicants

I also tried to recompile this app from the source code (it correctly compiles, using setarch x86_gcc2), but the above error is still here.

I attach the zip file with the source code and the binary, maybe someone would be able to fix the code?

Categories: Development

Ticket #12634 (The syslog is continuously flooded with the same messages.) created

Tue, 2016-02-02 22:49

Yesterday I was looking at the folder /var/log/ and I noticed that the syslog file is continuously growing: it never stops. I made a short explicative video (attached to this ticket): in this video we can see the output of "tail -f /var/log/syslog" and the syslog file which continuously grows. It quickly reach the size of 512 KB, the file is created again, and then this strange behaviour is incessantly repeated.
I also attach the syslog itself.

I choose "General" as Component, because I have no idea about the culprit.


Categories: Development

Ticket #12633 (Kernel fails to load on OptiPlex 960) created

Tue, 2016-02-02 22:46

The kernel fails to load on the Dell OptiPlex 960.

Serial connected shows:

size: 37.6 cm x 30.1 cm
border: 0 cm x 0 cm
Serial Number: G434H87FGB2U
Monitor Name: DELL 1908FP
Horizontal frequency range = 30..81 kHz
Vertical frequency range = 56..76 Hz
Maximum pixel clock = 140 MHz
crtc: h 1328/1440/1688, v 1025/1028/1066, pixel clock 108000000, refresh 6064
Welcome to the Haiku boot loader!
number of drives: 2
add_partitions_for(0x00105420, mountFS = no)
add_partitions_for(fd = 0, mountFS = no)
0x00105648 Partition::Partition
0x00105648 Partition::Scan()
check for partitioning_system: GUID Partition Map
check for partitioning_system: Intel Partition Map
  priority: 810
check for partitioning_system: Intel Extended Partition
0x001057c0 Partition::Partition
0x00105648 Partition::AddChild 0x001057c0
0x001057c0 Partition::SetParent 0x00105648
new child partition!
0x00105648 Partition::Scan(): scan child 0x001057c0 (start = 4194304, size = 629145600, parent = 0x00105648)!
0x001057c0 Partition::Scan()
check for partitioning_system: GUID Partition Map
check for partitioning_system: Intel Partition Map
check for partitioning_system: Intel Extended Partition
0x00105648 Partition::~Partition
0x001057c0 Partition::SetParent 0x00000000
boot partition offset: 4194304
0x001057c0 Partition::_Mount check for file_system: BFS Filesystem
PackageVolumeInfo::_InitState(): failed to parse activated-packages: No such file or directory
load kernel kernel_x86_64...

A random mixture of BIOS / boot options tried.

Intel Core 2 vPro

Boot was attempted with intel_extreme driver blacklisted for good measure, no changes.

32-bit and 64-bit kernels both fail with same issue

Categories: Development

Ticket #12632 (My /home/.profile file (with Terminal's customizations) is ignored.) created

Tue, 2016-02-02 22:28

I recently updated Haiku to hrev50067 (previously I had an old nightly image from one year ago; I don't remember the exact hrev, however)

I always had a .profile file under /home, which contains some Terminal customizations (prompt and colors). Well, after the recent update, the /home/.profile file is being ignored: when I open a Terminal window, in fact, my customizations aren't displayed. I can affirm that the content of such .profile is valid, since if I insert the content in the other profile file (the other, the one which is located as /boot/system/settings/etc/profile) I can see my customization.

The following is the content of my .profile file:

Yellow='\e[0;33m\]'        # Yellow
Red='\e[0;31m\]'          # Red
Gray='\e[0;37m\]'         #Gray
export PS1="\[$(tput setaf 7)\][\A]\[$(tput setaf 1)\] « \[$(tput setaf 3)\]baron\[$(tput setaf 7)\]@\[$(tput setaf 3)\]haiku\[$(tput setaf 1)\] » \[$(tput sgr0)\]"
Categories: Development

Ticket #12631 (UDP serial debug interface) created

Tue, 2016-02-02 21:36

This ticket logs some ideas PulkoMandy and landonf had in irc about solutions to the "no serial on a lot of new devices" issue.

Debugging Haiku on new hardware can be troublesome, especially if no serial interface is available (common on most modern hardware)

Other operating systems like OS X and windows offer serial debugging via UDP packets. Debugging over UDP would greatly assist users in troubleshooting KDL's, boot issues, or Debugger on system kits.

15:22 < landonf> Ethernet debugging for FreeBSD is actually on my TODO list, so if that coincides with FreeBSD compat driver support on the Haiku side ...                                                          |
15:22 <@kallisti5> landonf: any specs out there for serial over ethernet?                                                                                                                                           |
15:22 <@kallisti5> something next to tcp                                                                                                                                                                            |
15:23 <@PulkoMandy> just use UDP frames, broadcast on some random port                                                                                                                                              |
15:23 < landonf> Most implementations just send ethernet frames                                                                                                                                                     |
15:23 <@PulkoMandy> or I've seen it done with ARP or ICMP headers or whatever                                                                                                                                       |
15:23 <@PulkoMandy> just raw ethernet works as well with appropriate software on the other side of the link anyway                                                                                                  |
15:23 <@kallisti5>                                                                                                               |
15:23 < bslsk05> ​ Serial data over UDP Sockets in Python - Stack Overflow                                                                                                                         |
15:24 <@PulkoMandy> so… python in the kernel? :D                                                                                                                                                                    |
15:24 <@kallisti5>                                   |
15:24 < bslsk05> ​ Setting up a UDP based network serial port on a Linksys WRT54GS router. | Andrew Hazelden's Blog                                                                           |
15:27 < landonf>                                                                                                                     |
15:27 < landonf> This is the kernel-side implementation of the protocol OS X uses                                                                                                                                   |
15:28 <@kallisti5> I think just getting kdl into that would be a huge jump                                                                                                                                          |
15:28 <@kallisti5> you can extract syslogs from there                                                                                                                                                               |
15:28 <@PulkoMandy> well, if you get the basic frame send/receive working you could even plug our gdb stub to it                                                                                                    |
15:30 <@kallisti5> what about ethernet drivers after kdl?                                                                                                                                                           |
15:30 <@kallisti5> don't they lock up?                                                                                                                                                                              |
15:30 < landonf> kdp_udp.c provides the UDP implementation of the Kernel Debugging Protocol (KDP). The network driver is polled for packets, on top of which is implemented a *very* minimal ARP/IP/UDP stack.      |
15:31 < landonf> This is what the driver interface looks like:                                              |
15:31 < landonf> kallisti5: You have to provide direct/pollled access to read/write of ethernet frames                                                                                                              |
15:32 < landonf> So ethernet drivers have to be extended.                                                                                                                                                           |
15:32 < landonf> And it's not a great solution for debugging the ethernet driver you're using for the debugging interface :)
Categories: Development

Ticket #12630 (Late notices are sent continuously even when no audio playing) created

Tue, 2016-02-02 05:57
  1. Enable tracing in MediaPlayer's AudioProducer.
  2. Run MediaPlayer and start then stop playing something.
  3. "LateNoticeRecieved" prints forever
Categories: Development

Ticket #12629 (MediaPlayer audio output refuses to restart after disconnect) created

Tue, 2016-02-02 05:53

After disconnecting MediaPlayer's output in Cortex and reconnecting it to the input of an Equalizer, MediaPlayer refuses to play anything again.

Categories: Development