[Bug 1071388] Re: UnicodeDecodeError in askYesNoQuestion of DistUpgradeViewText.py

2012-12-14 Thread Коскин Илья
ok :) waiting for approval. for now (12/15/2012) error still exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071388 Title: UnicodeDecodeError in askYesNoQuestion of DistUpgradeViewText.py To

[Bug 1071388] Re: UnicodeDecodeError in askYesNoQuestion of DistUpgradeViewText.py

2012-10-28 Thread Коскин Илья
i have tried to upgrade through ssh and directly through console, i have 4 ubuntu servers and all of them have ru_RU locale, and none of them can update, so I think that bug is reproducable on every ru_RU precise server -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1068389] Re: P->Q - do-release-upgrade crashed with UnicodeEncodeError: 'ascii' codec can't encode character u'\xbb' in position 1: ordinal not in range(128) in DistUpgrade/DistUpgradeViewText.py

2012-10-25 Thread Коскин Илья
I jist run "do-release-upgrade" and wait until i see Чтение временных файлов Проверка менеджера пакетов Продолжить работу через SSH? Этот сеанс запущен через ssh. Не рекомендуется выполнять обновление через ssh, так как в случае неудачи восстановление будет очень сложным. Если вы продолжите

[Bug 1068389] Re: P->Q - do-release-upgrade crashed with UnicodeEncodeError: 'ascii' codec can't encode character u'\xbb' in position 1: ordinal not in range(128) in DistUpgrade/DistUpgradeViewText.py

2012-10-22 Thread Коскин Илья
i confirm bug with LANG=ru_RU.UTF-8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068389 Title: P->Q - do-release-upgrade crashed with UnicodeEncodeError: 'ascii' codec can't encode character u'\

[Bug 918827] Re: vsftpd running on non-standart port by inetd failing after inetd restart

2012-01-24 Thread Коскин Илья
I solved the problem by removing openbsd-inetd and installing xinetd. With xinetd my ftp works perfect. Expect the ltdb: tdb(/var/lib/samba/group_mapping.ldb): tdb_mmap failed for size 77824 (Cannot allocate memory) error, but it is not so important for me. ** Changed in: vsftpd (Ubuntu)

[Bug 918827] Re: vsftpd running on non-standart port by inetd failing after inetd restart

2012-01-24 Thread Коскин Илья
I tryed to switch both daemons to 21 port, and discovered that second daemon flailing again ftp> ls 200 PORT command successful. Consider using PASV. 150 Here comes the directory listing. drwxr-xr-x 11 1000 1000 4096 ??. 24 10:32 Maildir drwxrwxr-x4 1000 1000 4096

[Bug 918827] Re: vsftpd running on non-standart port by inetd failing after inetd restart

2012-01-19 Thread Коскин Илья
** Package changed: ubuntu => vsftpd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918827 Title: vsftpd running on non-standart port by inetd failing after inetd restart To manage notifi

[Bug 918827] Re: vsftpd running on non-standart port by inetd failing after inetd restart

2012-01-19 Thread Коскин Илья
** Summary changed: - vsftpd running on non-standart port by inetd shows me crap after inetd restart + vsftpd running on non-standart port by inetd failing after inetd restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bu

[Bug 918827] [NEW] vsftpd running on non-standart port by inetd shows me crap after inetd restart

2012-01-19 Thread Коскин Илья
Public bug reported: I have an openbsd-inetd installed and vsftpd launched by this lines in /etc/inetd.conf 192.168.0.1:ftp stream tcp nowait root/usr/sbin/tcpd vsftpd x.x.x.x:2121 stream tcp nowait root/usr/sbin/tcpd vsftpd /etc/vsftpd.conf.local where x.x.x.x is my

[Bug 810732] Re: Netatalk shows kernel panic in syslog when trying to connect to server in OS X 10.6.8. Worked fine before upgrade to ocelot

2011-10-17 Thread Коскин Илья
Same bug. Mac OS 10.6.8, on 11.04 worked fine, on 11.10 this bug appeared: Oct 17 19:52:50 mx afpd[8768]: === Oct 17 19:52:50 mx afpd[8768]: INTERNAL ERROR: Signal 11 in pid 8768 (2.2-beta4) Oct 17 19:52:50 mx afpd[8768]: ===