[Bug 908233] Re: cal -M (start week on Monday) don't work

2011-12-27 Thread Ivan Sorokin
Yes but both cal -M and ncal -M works perfectly in cygwin (I'm almost
sure, I can check this later). So I think this is problem in code, not
in manpage.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908233

Title:
  cal -M (start week on Monday) don't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/908233/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 908233] [NEW] cal -M (start week on Monday) don't work

2011-12-23 Thread Ivan Sorokin
Public bug reported:

man page says:

 -M  Weeks start on Monday.

But when I run

$ cal -M
Usage: cal [general options] [-hjy] [[month] year]
   cal [general options] [-hj] [-m month] [year]
   ncal [general options] [-bhJjpwySM] [-s country_code] [[month] year]
   ncal [general options] [-bhJeoSM] [year]
General options: [-NC3] [-A months] [-B months]
For debug the highlighting: [-H -mm-dd] [-d -mm]

** Affects: bsdmainutils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908233

Title:
  cal -M (start week on Monday) don't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/908233/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 883775] Re: non cumulative memory leak in dlopen/dlclose

2011-11-14 Thread Ivan Sorokin
Thank you, Martin. Suppression seems to be the only feasible solution,
because libc6 code is really complicated in this function.

Should we report this bug upstream or let it stay here? eglibc
(http://www.eglibc.org/issues/) bug-tracker seems to be not very
popular.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883775

Title:
  non cumulative memory leak in dlopen/dlclose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/883775/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 883775] [NEW] non cumulative memory leak in dlopen/dlclose

2011-10-30 Thread Ivan Sorokin
Public bug reported:

Ubuntu 11.10, libc6 2.13-20ubuntu5.

After calling dlopen/dlclose few blocks of memory left unfreed. They
number is not grow when dlopen/dlclose are called several times.

This is not fatal bug, but it makes it harder to find memory leaks in
other parts of program.

Source code:

#include dlfcn.h
#include stdio.h
#include stdlib.h

void print_dlerror()
{
  char const* msg = dlerror();
  if (msg == NULL)
 fprintf(stderr, unknown error at dynamic linking);
  else
 fprintf(stderr, dynamic linking error: %s, msg);
}

int main()
{
   void* asound = dlopen(/usr/lib/x86_64-linux-gnu/libasound.so.2, RTLD_LAZY);
   if (asound == NULL)
   {
  print_dlerror();
  return EXIT_FAILURE;
   }

   printf(module is loaded successfully: %p\n, asound);

   dlclose(asound);
   
   return EXIT_SUCCESS;
}

Valgrind output:

valgrind --leak-check=full --show-reachable=yes -v ./a.out

==2114== HEAP SUMMARY:
==2114== in use at exit: 3,361 bytes in 12 blocks
==2114==   total heap usage: 22 allocs, 10 frees, 6,638 bytes allocated
==2114== 
==2114== Searching for pointers to 12 not-freed blocks
==2114== Checked 114,056 bytes
==2114== 
==2114== 64 bytes in 2 blocks are still reachable in loss record 1 of 6
==2114==at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==2114==by 0x40141B6: _dl_close_worker (dl-close.c:374)
==2114==by 0x401469D: _dl_close (dl-close.c:754)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4E3052E: _dlerror_run (dlerror.c:164)
==2114==by 0x4E3000E: dlclose (dlclose.c:48)
==2114==by 0x4007AA: main (in /home/ivan/a.out)
==2114== 
==2114== 71 bytes in 2 blocks are still reachable in loss record 2 of 6
==2114==at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==2114==by 0x40085B3: _dl_map_object (dl-load.c:162)
==2114==by 0x400C8A1: openaux (dl-deps.c:65)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x400CF65: _dl_map_object_deps (dl-deps.c:247)
==2114==by 0x4012BA6: dl_open_worker (dl-open.c:263)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4013379: _dl_open (dl-open.c:569)
==2114==by 0x4E2FF25: dlopen_doit (dlopen.c:67)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4E3052E: _dlerror_run (dlerror.c:164)
==2114==by 0x4E2FFC0: dlopen@@GLIBC_2.2.5 (dlopen.c:88)
==2114== 
==2114== 71 bytes in 2 blocks are still reachable in loss record 3 of 6
==2114==at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==2114==by 0x400B42C: _dl_new_object (dl-object.c:161)
==2114==by 0x40065B5: _dl_map_object_from_fd (dl-load.c:957)
==2114==by 0x400831C: _dl_map_object (dl-load.c:2250)
==2114==by 0x400C8A1: openaux (dl-deps.c:65)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x400CF65: _dl_map_object_deps (dl-deps.c:247)
==2114==by 0x4012BA6: dl_open_worker (dl-open.c:263)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4013379: _dl_open (dl-open.c:569)
==2114==by 0x4E2FF25: dlopen_doit (dlopen.c:67)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114== 
==2114== 112 bytes in 2 blocks are still reachable in loss record 4 of 6
==2114==at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==2114==by 0x400D016: _dl_map_object_deps (dl-deps.c:470)
==2114==by 0x4012BA6: dl_open_worker (dl-open.c:263)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4013379: _dl_open (dl-open.c:569)
==2114==by 0x4E2FF25: dlopen_doit (dlopen.c:67)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4E3052E: _dlerror_run (dlerror.c:164)
==2114==by 0x4E2FFC0: dlopen@@GLIBC_2.2.5 (dlopen.c:88)
==2114==by 0x400771: main (in /home/ivan/a.out)
==2114== 
==2114== 696 bytes in 2 blocks are still reachable in loss record 5 of 6
==2114==at 0x4C279F2: calloc (vg_replace_malloc.c:467)
==2114==by 0x4010329: _dl_check_map_versions (dl-version.c:300)
==2114==by 0x4012EC0: dl_open_worker (dl-open.c:269)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4013379: _dl_open (dl-open.c:569)
==2114==by 0x4E2FF25: dlopen_doit (dlopen.c:67)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x4E3052E: _dlerror_run (dlerror.c:164)
==2114==by 0x4E2FFC0: dlopen@@GLIBC_2.2.5 (dlopen.c:88)
==2114==by 0x400771: main (in /home/ivan/a.out)
==2114== 
==2114== 2,347 bytes in 2 blocks are still reachable in loss record 6 of 6
==2114==at 0x4C279F2: calloc (vg_replace_malloc.c:467)
==2114==by 0x400B1BD: _dl_new_object (dl-object.c:77)
==2114==by 0x40065B5: _dl_map_object_from_fd (dl-load.c:957)
==2114==by 0x400831C: _dl_map_object (dl-load.c:2250)
==2114==by 0x400C8A1: openaux (dl-deps.c:65)
==2114==by 0x400E995: _dl_catch_error (dl-error.c:178)
==2114==by 0x400CF65: _dl_map_object_deps (dl-deps.c:247)
==2114==by 

[Bug 710144] Re: Xsession: unable to launch X session --- not found; falling back to default session.

2011-05-10 Thread Ivan Sorokin
This helps for me: http://forum.kde.org/viewtopic.php?f=66t=91936

1) Set in /etc/kde4/kdm/kdmrc AutoLoginEnable = false
2) reboot
3) select default session as kde

At login you'll get the following message:
Your saved Gnome session isn't valid anymore.
Please, choose a new one or the default one will be used

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710144

Title:
  Xsession: unable to launch  X session ---  not found; falling back
  to default session.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 579005] Re: misleading russian translation

2010-05-12 Thread Ivan Sorokin
Спасибо всем кто откликнулся.

Строчка по которую я говорю является фильтром пакетов. Название фильтра
пакетов отвечает на вопрос какие?

Какие? Все
Какие? Обновляемые
Какие? Пакеты с поддержкой Debconf
Какие? Поддерживаемые сообществом
Какие? С ошибками

Ясно что это очень плохо согласуется с

Какие? Нет рекомендованных пакетов

Поэтому я предлагал переименовать этот пункт меню в Отсутствующие
рекомендуемые.

Надо или не надо писать слово пакеты я не знаю, но в англоязычной
версии слово пакеты не пишется.

** Attachment added: synaptic-translation.png
   http://launchpadlibrarian.net/48342278/synaptic-translation.png

-- 
misleading russian translation
https://bugs.launchpad.net/bugs/579005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 579005] Re: misleading russian translation

2010-05-12 Thread Ivan Sorokin
Artem Karimov:
 Fix committed in Lucid translation branch.
Спасибо огромное!

Sergey Shnatsel Davidoff:
 Какие? Без рекомендуемых пакетов
 Какие? Без рекомендаций

Нет, там не в смысле, что у пакетов нет рекомендаций, а в смысле, что
пакеты рекомендуются, но не установлены.

-- 
misleading russian translation
https://bugs.launchpad.net/bugs/579005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 579005] [NEW] misleading russian translation

2010-05-11 Thread Ivan Sorokin
Public bug reported:

Binary package hint: synaptic

In the lastest version of Synaptic in Ubuntu 10.04 string missing
recommends has misleading translation Нет рекомендованых пакетов.

I suggest to replace it with Отсутствующие рекомендуемые. It is more
clearly. Note that the word пакеты is omitted in all other items of
this list.

In any case the word рекомендованых is misspelled and should be
written as рекомендованных.

Also I can help with russian translation. I wanted to create the patch
against .po file. I checked out several branches from
https://code.launchpad.net/ubuntu/+source/synaptic from sections Lucid
and Maverick. But none of po/ru.po files in this branches correspond
with synaptic.mo installed in my system (Ubuntu 10.04 latest update).

If I will be told which branch I should pull, and which .po file I
should translate, I will create a patch and send it wherever you want
(not only with synaptic, but with any other package).

** Affects: synaptic (Ubuntu)
 Importance: Undecided
 Status: New

-- 
misleading russian translation
https://bugs.launchpad.net/bugs/579005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs