Confirming because it happens to several users.
** Changed in: muse (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of MOTU,
which is a bug assignee.
https://bugs.launchpad.net/bugs/41780
Title:
Muse fails to start and segfaults.
To man
The information you lack is: yes.
And I do not hesitate to say that this bug report is not invalid at all.
As of 10.04 and probably later, a corner stone of Ubuntu Studio simply does not
start.
Anyone can check this in minute(s?): apt-get install muse ; muse
I see no crash but the timer problem
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Is this symptom reproducible in 8.10 alpha?
** Changed in: muse (Ubuntu)
Status: Confirmed => Incomplete
--
Muse fails to start and segfaults.
https://bugs.launchpad.net/bugs/41780
You received this bug notification because you are a member of MOTU,
which is a bug assignee.
--
universe-
Not sure if this is the same issue as above - using edgy..
** Attachment added: "I think this is the same issue above crashes"
http://librarian.launchpad.net/4940991/_usr_bin_muse.1000.crash
--
Muse fails to start and segfaults.
https://launchpad.net/bugs/41780
--
universe-bugs mailing lis
>Muse runs fine setuid
This is not an option, isnt it considered ucool to run big beasts like Muse
setuid??
Plus: as I said, muse runs like a charm if max-user-freq can be tweaked to
1024, I now use a rt-kernel for edgy from ubuntumusique, that is more or less
configured like the older Dapper-K
on den 27.09.2006 klokka 22:26 (+) skreiv zettberlin:
> On dapper i can run muse whithout being setuid just perfectly after
> setting /proc/sys/dev/rtc/max-user-freq to 1024 - no seqfaults, no
> trouble at all.
>
> Dappers kernel is built with the option CONFIG_HZ being set at 1000 at
> least
On dapper i can run muse whithout being setuid just perfectly after
setting /proc/sys/dev/rtc/max-user-freq to 1024 - no seqfaults, no
trouble at all.
Dappers kernel is built with the option CONFIG_HZ being set at 1000 at
least, 2.6.17-7-generic on edgy is configured with only 250 Hz, wich is
too
The difficulty here is not that I cannot reproduce the bug, but that
everytime I run under gdb, whether setuid or not, I get a slightly
different backtrace from the crash. I can repeat this with the
repository version, or with a local version with debug symbols. When
running the version from the
Isn't the setuid a different issue from the segfaulting? I can also
confirm that it segfaults, running it with -a stops the segfaulting
(this is latest dapper) . I'm attaching a backtrace ...
--
Muse fails to start and segfaults.
https://launchpad.net/bugs/41780
--
universe-bugs mailing list
uni
[EMAIL PROTECTED]:~$ gdb muse
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There
MuSe upstream has added rtcap support through the --enable-rtcap
parameter to ./configure, but this 1) depends on givertcap
(http://www.tml.tkk.fi/~tilmonen/givertcap/) which is not in the
repositories, and 2) requires the entry of the root password during
compilation (prevents auto-building). Unt
You are entirely correct. It is not a duplicate. The easiest workaround
is to run `sudo dpkg-reconfigure muse` and set it to run setuid, which will
enable it to run anyway. On my system, even setting
/proc/sys/dev/rtc/max-user-freq
to 1024 still results in the following output:
AlsaTime
** This bug is no longer a duplicate of bug 33713
Segfaults on startup for AMD64
--
Muse fails to start and segfaults.
https://launchpad.net/bugs/41780
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
*** This bug is a duplicate of bug 33713 ***
on den 03.05.2006 klokka 09:21 (+) skreiv Emmet Hikory:
> *** This bug is a duplicate of bug 33713 ***
>
> ** This bug has been marked a duplicate of bug 33713
>Segfaults on startup for AMD64
>
I dissagree, as i already run the version suppose
*** This bug is a duplicate of bug 33713 ***
** This bug has been marked a duplicate of bug 33713
Segfaults on startup for AMD64
--
Muse fails to start and segfaults.
https://launchpad.net/bugs/41780
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
** Changed in: muse (Ubuntu)
Assignee: (unassigned) => MOTU
Status: Unconfirmed => Confirmed
--
Muse fails to start and segfaults.
https://launchpad.net/bugs/41780
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
17 matches
Mail list logo
