[Bug 535394] Re: mv crashed with SIGSEGV in __libc_start_main()

2010-12-06 Thread Launchpad Bug Tracker
[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: coreutils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/535

[Bug 535394] Re: mv crashed with SIGSEGV in __libc_start_main()

2010-06-10 Thread C de-Avillez
** Visibility changed to: Public -- mv crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/535394 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://li

Re: [Bug 535394] Re: mv crashed with SIGSEGV in __libc_start_main()

2010-03-09 Thread lorde
Ok, thank you for your notice. It seems that mv is not working at all after the newest alpha-release update. I just try the command: mv anyfile anydestination and it returns: Segmentation fault (core dumped) On 03/09/2010 06:24 PM, Carlos de-Avillez wrote: > Thank you for opening this bug and

[Bug 535394] Re: mv crashed with SIGSEGV in __libc_start_main()

2010-03-09 Thread Carlos de-Avillez
Thank you for opening this bug and helping make Ubuntu better. You might want to know that, as a general rule, bugs with coredumps should not be made public for privacy reasons. The automatic coredump analyser will work on the bug, and provide nice stacktraces for us to marvel on -- and then remove

[Bug 535394] Re: mv crashed with SIGSEGV in __libc_start_main()

2010-03-09 Thread lorde
** Visibility changed to: Public -- mv crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/535394 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://l