Public bug reported:
The current shipped version is unfortunately badly out of date. 4.1.6 is
from 2011 and has no Python 3 compatibility. The current version is
4.2.2 and supports Python 3.6 (and 2.7).
** Affects: omniorb-dfsg (Ubuntu)
Importance: Undecided
Status: New
--
You
How can this be invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389159
Title:
Clicking on search results doesn't take you to the corresponding page
To manage notifications about this bug
It's actually a bug in the plugin not pidgin itself
** Package changed: pidgin (Ubuntu) = pidgin-skype (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when
So it looks like triggering a simple rebuild would fix this problem
right? So how can one trigger it for the repo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when
current version is 20130613+svn660+dfsg-1 which basically contains
the upstream fix mentioned here.
** Changed in: pidgin-skype (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Simply compiling libskype64.so from source and then placing that in the
local plugins directory worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379713
Title:
Pidgin crashes when pidgin-skype
Public bug reported:
It seems the pidgin-skype extension causes a
Attempt to unlock mutex that was not locked
Aborted
error and pidgin crashes immediatly. Deinstalling skype-pidgin solves
the problem but then I can no longer access my skype chats of course.
ProblemType: Bug
DistroRelease:
The same here. After upgrade I can not run Unity any longer. Even the
fallback via llvm does only partly work since the menues (dash?) are not
loaded. So basically it's desktop background without any window manager.
I had to fall back to XFCE in order to get this working.
Kernel: Version:
Christopher,
thanks removing all nvidia related packages that had no other
dependencies attached helped. So also in my case the Virtual Box package
update seemed to have caused the damage. Though I didn't need to remove
the Virtual Box package.
Thanks again for finding out,
Dietmar
--
You
** Also affects: auctex
Importance: Undecided
Status: New
** No longer affects: auctex
** Also affects: ecb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Although it says there was a fix released it occurred again last week.
See also log attached
** Attachment added: crash.log
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1028388/+attachment/3435329/+files/crash.log
--
You received this bug notification because you are
I can reproduce this just as described. In addition the rescaling steps
which for example work for ControlAltKP3 (i.e., 2/3, 1/2, 1/3, 1/4
width) no longer work for ControlAltKP4/6. This used to work
flawlessly in 11.04.
** Changed in: unity
Status: Incomplete = Confirmed
** Changed in:
I can just confirm that this (comment #4) is _not_ yet fixed by:
Installed: 1:0.9.6-0ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/862260
Title:
Grid plugin behaviour random
To manage
@Alessandro: Avidemux was not removed as such but simply had build
problems up to today. Just now a fix was released to oneiric-proposed
and if things go well it will hit the updates and some point. You can
follow the status of that in Bug #831096
--
You received this bug notification because
I also got 0.75.2ubuntu8 installed and I tried switching screen-reader
and screen-keyboard on and off again. The result stays the same:
Synaptic is starting up and showing for about a tenth of a second just
to terminate again.
--
You received this bug notification because you are a member of
BTW dmesg tells me:
[ 1056.663423] synaptic[3747]: segfault at dae4b2a8 ip b68e5410 sp bfc76b8c
error 5 in libc-2.13.so[b68a2000+176000]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
OK I got it working but only when switching to a Theme different from
ambience. I got the idea from
https://bbs.archlinux.org/viewtopic.php?id=118331 which describes a
similar error in that libc-2.13.so
Actually I like the ambience theme and would love to switch back to
it. Only Synaptic then
So I played a bit more and unfortunately simply switching the theme away from
ambiance is not enough since although synaptic started at first it crashed
later on when applying changes and could not be started again even after
changing the themes again.
Here is a serious of the error synaptic
OK I think I could figure what is kind of causing the segfault at least
for me. It's the language environment I'm using.
Steps to reproduce:
~$ export LANG=nb_NO.UTF-8
~$ sudo gdb synaptic
(gdb) run
Starting program: /usr/sbin/synaptic
[Thread debugging using libthread_db enabled]
Program
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug has been marked a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug is no longer a duplicate of bug 839219
synaptic crashes immediately on startup with SIGABRT in raise() [Only when
accessibility is enabled, e.g. screen reader]
** This bug has been marked a
** This bug is no longer a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately
Alan, sorry you are right. I thought that that was the same problem. I
just reverted the duplication note of #839219 again (btw I never did
anything to #874078 which doesn't even exist) so that that bug can be
handled by itself.
I hope that clears things up again.
--
You received this bug
So we have the final release without a working proper gui package
manager (I don't count software center as such) :( Any development on
this segfault issue at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The new version 2.4.0-3 of this package (libsundials-serial-dev) is
missing the statically linked versions of the following libs:
/usr/lib/libsundials_cvode.a
/usr/lib/libsundials_cvodes.a
/usr/lib/libsundials_fnvecserial.a
/usr/lib/libsundials_ida.a
** Description changed:
- The new version 2.4.0-3 of this package is missing the statically linked
- versions of the following libs:
+ The new version 2.4.0-3 of this package (libsundials-serial-dev) is
+ missing the statically linked versions of the following libs:
Sylvestre, I was actually looking at the debian package first but the
debian bugtracker was kind of putting me off despite it being
inaccessible at the time. So I hoped that maybe one of the Debian
maintainers is also listening to the bugs reported here. I just tried to
access bugs.debian.org
** Changed in: synaptic (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857869
Title:
synaptic crashed with SIGSEGV in debListParser::LoadReleaseInfo()
To
** Changed in: ipe (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785869
Title:
IPE cannot be executed from launcher
--
ubuntu-bugs mailing list
OK, I've attached the current NEWS file of ipe 7.0.14 which impressively
shows the improvements and bugfixes over the up to now version 7.0.10
(which was already released about 17 month (!) ago). I hope this might
justify the simple synch to the current debian version.
** Attachment added: NEWS
Public bug reported:
Binary package hint: ipe
Debian Unstable is currently at version 7.0.14. It would be great if
this can be synced even before the final Natty release.
** Affects: ipe (Ubuntu)
Importance: Undecided
Status: New
** Tags: whishlist
--
You received this bug
Robert, the package where this typo occurs is only the kvm (dummy)
package!
** Package changed: qemu-kvm (Ubuntu) = kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
https://bugs.launchpad.net/bugs/719174
OK, I see :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/719174
Title:
Typo in package description string
--
Ubuntu-server-bugs mailing list
OK, I see :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719174
Title:
Typo in package description string
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Robert, the package where this typo occurs is only the kvm (dummy)
package!
** Package changed: qemu-kvm (Ubuntu) = kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719174
Title:
Typo
Public bug reported:
Binary package hint: kvm
There is a typo in the package description string:
- dummy transitional pacakge from kvm to qemu-kvm
+ dummy transitional package from kvm to qemu-kvm
** Affects: kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
Binary package hint: kvm
There is a typo in the package description string:
- dummy transitional pacakge from kvm to qemu-kvm
+ dummy transitional package from kvm to qemu-kvm
** Affects: kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
Binary package hint: myspell-nb
When myspell-nb package is installed (currently automatically when
Norwegian language support is activated). Any application that will use
a dict file out of that package will raise errors in the shape of
error: line 321989: bad flagvector
I can also confirm this for the LaTeX mode (in addition to the ones
named above). It looks somehow any major mode with its own menus does
not work properly.
** Changed in: emacs23 (Ubuntu)
Status: New = Confirmed
--
org and tbl menus are missing in org-mode
I forgot: ECB mode the same
--
org and tbl menus are missing in org-mode
https://bugs.launchpad.net/bugs/640504
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
I can confirm this on 10.10. final release when using Tilda.
** Changed in: tilda
Status: Invalid = Confirmed
--
Embedded Terminal Emulator isn't giving a TERM variable
https://bugs.launchpad.net/bugs/621927
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks Dario, exactly what I thought. Just because it's reported to
upstream doesn't mean that it's already fixed for the application that
this also impacts. For me it as just logical to report this as not fixed
yet for this application.
--
Embedded Terminal Emulator isn't giving a TERM variable
*** This bug is a duplicate of bug 287824 ***
https://bugs.launchpad.net/bugs/287824
** This bug has been marked a duplicate of bug 287824
Photoprint can't print, printer model and driver incorrect
--
No photoprint support for HP Deskjet F4180
https://bugs.launchpad.net/bugs/309874
You
Unfortunately this bug is still around in 10.04 :(
--
Photoprint can't print, printer model and driver incorrect
https://bugs.launchpad.net/bugs/287824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
+1 confirmed this just like the others on a Intel GM45 (Dell Inspiron
1545) but it seems to be independent on usage of compiz
** Summary changed:
- [gm45] Irregular sync flashes with compiz on (Lenovo T500)
+ [Intel GM45] Irregular sync flashes (Lenovo T500, Dell Insp. 1545)
--
[Intel GM45]
** Changed in: sundials (Ubuntu)
Status: New = Confirmed
--
Please update to SUNDIALS 2.4.0
https://bugs.launchpad.net/bugs/439195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here another ping. There are a couple of projects out there that rely on
2.4.x version of sundials and it would be really nice to have an updated
version shipped with Ubuntu. Perhaps there is still a chance to get it
into back-ports of lucid?
--
Please update to SUNDIALS 2.4.0
** Tags added: karmic
--
Keyboard indicator shows additional layout null
https://bugs.launchpad.net/bugs/283128
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
Exactly the same on 32-bit machine.
** Changed in: impressive (Ubuntu)
Status: New = Confirmed
--
hyperlinks do not work
https://bugs.launchpad.net/bugs/437074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- broken menus at Ubuntu LInux 9.04 with intel-2.8.1
+ broken menus at Ubuntu Linux 9.04/9.10 with intel-2.8.1/2.9
--
broken menus at Ubuntu Linux 9.04/9.10 with intel-2.8.1/2.9
https://bugs.launchpad.net/bugs/426417
You received this bug notification because you are a
Daniel, I had to reinstall my system (for some other reason) and not I
can no longer verify this issue. So I guess at some point some package
configuration had a hickup and left something behind. Anyway since
nobody else confirmed this issue please fee free to simply close this as
invalid. (btw my
This seems to be solved in Karmic. At least I no longer have this issue
(and neither need a workaround).
--
Audio not working on Dell E-Port docking station in Jaunty (9.04); was OK in
8.10
https://bugs.launchpad.net/bugs/387866
You received this bug notification because you are a member of
I can confirm that using a fresh install (on a different machine but
with exactly the same audio card as mineIntel 82801I) the internal mic
will works. Strange and I wouldn't really want to reinstall my machine.
There must be another way ;-)
--
[Karmic] Internal microphone does not record sound
OK this workaround works for now:
In the /usr/share/alsa/alsa.conf comment out the line that says:
/usr/share/alsa/pulse.conf
Then one can start alsamixer and also set properties with amixer
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification
Daniel, I found another bug (closed though) which showed the same
problem: bug #329460 Maybe you can make something out of it and why this
reappeared in my case.
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of
I found a comment in the changelog of alsa-utils:
alsa-utils (1.0.20-2ubuntu1) karmic; urgency=low
* Merge from debian unstable, remaining changes:
[...]
+ Default Digital Input Source to be Digital Mic 1 so that users
with digital mic will be able to use it out of the box
Daniel should I also create an extra bugreport following your comment
here
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/409819/comments/34
or should this report here set to also affects alsa-base?
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this
Just a little update: The latest update to 1:0.9.19-0ubuntu4 didn't
change the situation. Digital Microphone still can't be selected as
input device and alsamixer also still refuses to start.
--
Microphone stopped working
https://bugs.launchpad.net/bugs/450861
You received this bug notification
*** This bug is a duplicate of bug 409819 ***
https://bugs.launchpad.net/bugs/409819
** This bug has been marked a duplicate of bug 409819
[regression] Built-in mic not working after pulse updates on Karmic. Intel
82801H (ICH8 Family) sound card.
--
Microphone stopped working
Well in the meantime I found the possible reason. The preferences of
pulse audio don't let you choose a Digital Microphone 1 such as is
installed in my machine as input device. It only gives you a choice of
two *analog* Microphone 1 and Microphone 2. Now getting around this
by using alsamixer to
OK I could start alsamixer after I removed the pulseaudio package
(which also means that ubuntu-desktop is removed). Not really a nice
solution. If a solution at all. So it looks like that pulseaudio somehow
blocks the alsamixer alltogether.
--
alsamixer does not start
MIchal, I've linked it for you (simple go to the also affects
dirtribution link on the top next time). I had to actually remove
pulseaudio in order to get alsa-mixer running. At least now I could set
the digital mic and confirm that the mic itself works it's really just
the problem that it can not
I tried to nail this down further and it looks like this update caused the
problem:
pulseaudio (1:0.9.19-0ubuntu2) to 1:0.9.19-0ubuntu3
Looking at the ChangeLog I guess that either the removeal of rtkit of the
mentioned patch might be the reason:
[ Tony Espy ]
* debian/control: Add a
Public bug reported:
Binary package hint: alsa-utils
When trying to start alsamixer (in order to fix my mic problem by following
this work around
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/449781/comments/2 )
all I get is:
ALSA lib conf.c:2700:(snd_config_hooks_call) Cannot open
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34249569/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34249570/XsessionErrors.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug
Did this (and even a restart) but the result is exactly the same. I
checked and there doesn't exist any /etc/asound.conf of ~/.asoundrc
file.
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK here is the strace of
$ strace alsamixer
** Attachment added: strace_alsamixer.txt
http://launchpadlibrarian.net/34251778/strace_alsamixer.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34253415/AlsaDevices.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Card0.Codecs.codec.2.txt
http://launchpadlibrarian.net/34253418/Card0.Codecs.codec.2.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34253421/Dependencies.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/34253423/PciMultimedia.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34253416/BootDmesg.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/34253417/Card0.Codecs.codec.0.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34253420/CurrentDmesg.txt
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34253424/XsessionErrors.txt
** Tags added: apport-collected
--
alsamixer does not start
https://bugs.launchpad.net/bugs/459064
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 170 matches
Mail list logo
