*** This bug is a duplicate of bug 930568 ***
https://bugs.launchpad.net/bugs/930568
This has nothing to do with valatoys plugin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940291
Title:
Public bug reported:
(testing from the ubuntu audio dev ppa)
Running sudo alsa force-reload seems to be current workaround to get it
to work
hardware info (when sound is working):
Code:
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
Please update the description to include mouse as well (see Bug #932624)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931927
Title:
[regression] customized keyboard shortcuts don't work in compiz
Haven't had a chance to test it yet, but I am curious about how the
manual testing is conducted, which shortcuts have been tested to be
working as a direct result of the fix? (i.e. they weren't working
before)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Tested on Precise Alpha 2 with 0.4.90-0ubuntu1 of indicator-applet-
complete
Expected result: Sound Settings.. should have the same functionality as
System Settings - Sound
Actual result: Sound Setting is like System Settings with the wrong name
** Affects:
apport information
** Tags added: apport-collected precise
** Description changed:
(testing from the ubuntu audio dev ppa)
Running sudo alsa force-reload seems to be current workaround to get it
to work
hardware info (when sound is working):
Code:
00:1b.0 Audio device:
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747500/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
apport information
** Attachment added: ArecordDevices.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747501/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747504/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747505/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747502/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747506/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747507/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
apport information
** Attachment added: PulseSinks.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747508/+files/PulseSinks.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
apport information
** Attachment added: PulseSources.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747509/+files/PulseSources.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
added pulseaudio log (following the steps to produce the log actually
got the sound working)
** Attachment added: pulseverbose.log
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/933209/+attachment/2747510/+files/pulseverbose.log
--
You received this bug notification because you
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/933209/+attachment/2747503/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On a setup with two screens with icons on both of them, when the second
monitor is not present or unplugged, icons on that screen are not
relocated properly onto the first screen in any reasonable fashion.
Instead they appear as a clump of overlapping icons at the edge of the
** Attachment added: added screenshot depicting right edge of first screen
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/936041/+attachment/2756853/+files/messed-up.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
same, it just crashed in a fresh session (maybe triggered by auto
update)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930657
Title:
synaptic crashed with SIGSEGV
To manage notifications about
this error can be seen in the console when attempting to install Adobe
Air 2.6 onto Precise 12.04 (Alpha 2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859512
Title:
Please convert libdbusmenu to
*** This bug is a duplicate of bug 859512 ***
https://bugs.launchpad.net/bugs/859512
this error can be seen in the console when attempting to install Adobe
Air 2.6 onto Precise 12.04 (Alpha 2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This could be an isolated incident, but I managed to connect at 802.11n
speeds starting today after several system updates I made to a MBP 8.2
that is tri-booting Snow Leopard, Ubuntu 12.04 and Windows 7. These
updates include the latest Kernel 3.5.0.29 and Airport updates
# so wl was loaded for
oops this should be the network I meant to paste
0
Cell 24 - Address: 20:37:06:7C:F2:1C
Channel:161
Frequency:5.805 GHz (Channel 161)
Quality=22/70 Signal level=-88 dBm
Encryption key:on
I find it funny that developers think they are doing users a favour by
removing existing features then tagging them as 'wishlist'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969657
Title:
No way
+1, forced to set num of workspaces to 2 because having just 1 causes 4
to be shown instead
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996604
Title:
When number of workspaces is set to 1, the
This is what I see when I had to do a killall, I thought the pcm devices
are interfering but they seem to be started again after the killall,
with sound playing.
/dev/snd/controlC0: 11048
/dev/snd/pcmC0D0c: 11048m
/dev/snd/pcmC0D0p: 11048m
user@user-laptop:~/Desktop/Support/r8168-8.027.00$
I also tried to hunt down the errant process (using the idea from
http://askubuntu.com/questions/25622/my-sound-stopped-working-today-how-
can-i-fix-it):
user@user-laptop:~/Desktop$ sudo fuser -f /dev/snd/*
/dev/snd/controlC0: 1075
/dev/snd/pcmC0D0p:1075m
user@user-laptop:~/Desktop$ ps aux
I noted that pulseaudio is started by 106 on startup, is this normal?
After the kill it is started by my userid:
user 3404 4.2 0.1 399304 5576 ?Sl 11:41 0:01
/usr/bin/pulseaudio --start --log-target=syslog
--
You received this bug notification because you are a member of Ubuntu
If it matters, the lines below were added to /var/log/syslog after kill
pulseaudio (new process is 3404)
Apr 12 11:41:30 user-laptop rtkit-daemon[1077]: Successfully made thread 3397
of process 1758 (n/a) owned by '1000' RT at priority 5.
Apr 12 11:41:30 user-laptop rtkit-daemon[1077]:
** Project changed: null = dbus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about this bug go
** Project changed: dbus = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about this bug go
** Package changed: ubuntu = dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933209
Title:
No sound after startup (audio device shown as Dummy Output)
To manage notifications about
recently discovered that `sudo killall pulseaudio` seems to get the
sound back somehow. Not sure if problem lies with pulseaudio or alsa-
driver
** Also affects: pulseaudio
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
(testing from the ubuntu audio dev ppa)
-
- Running sudo alsa force-reload seems to be current workaround to get it
- to work
-
+ Running sudo alsa force-reload (or sudo killall pulseaudio) seems to be
+ current workaround to get it to work
hardware info (when
Please also refer to https://bugs.launchpad.net/pulseaudio/+bug/933209,
where the symptoms suggest that the problem is caused by pulseaudio
rather than alsa-driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nope, no sound in login session. I do hope this gets fixed (I agree it
is probably a matter of looking into the right places) even though the
crude workaround is available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Upgraded from 14.04 to 16.04 Beta 2
one of the errors that appear on startup (after GUI has been loaded)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: aspell-en 7.1-0-1.1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
Public bug reported:
just upgraded from 14.04 to 16.04 Beta 2
error appeared after startup login (GUI has been loaded)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wbritish (not installed)
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
Can this ever be fixed at the system package level? Otherwise it makes
more sense to recommend people to use the prebuilt binary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605628
Title:
upload
Public bug reported:
Description:
The system was previously on 22.04, then upgraded to 23.10 to the
current daily 24.04. System will freeze up a few minutes after startup
(with no apparent related crashes). After various trial and error, the
possible cause is isolated to indicator-keyboard when
42 matches
Mail list logo
