| Server IP : 85.214.239.14 / Your IP : 18.119.116.77 Web Server : Apache/2.4.62 (Debian) System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.18 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/self/root/proc/2/cwd/proc/self/root/usr/share/bug/fonts-noto-mono/ |
Upload File : |
When reporting bugs in the fonts themselves (i.e. not just in the packaging) please be sure to include the following information as far as applicable: - the versions of your libfreetype6, libxft2 and fontconfig packages (these should be automatically appended by reportbug), - all relevant configuration (especially anti-aliasing and hinting), - the application being used, - the affected unicode code points. It may also be helpful if you can provide a screen shot demonstrating the problem, however please don't attach it to the initial bug report (especially not if it is large). Please also try to make sure that it is actually a bug in the fonts and not e.g. in freetype (if a problem appears after a freetype update or if other fonts exhibit similar problems it is a sure sign that the problem is in freetype).