I can confirm that 3.19.0-13-generic fixes the issue with HDMI Audio!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440392
Title:
kernel 3.19.0-12 breaks HDMI Audio
To manage notifications about t
Public bug reported:
it's not yet clear to me what is wrong. I know that if I fail back to
the previous kernel 3.19.0-11 everything works just fine.
The output produced by ubuntu-bug is attached. Please let me know if you
think of any relevant command that might help to troubleshoot the issue.
P
** Summary changed:
- 3.19.0-12 brakes HDMI Audio
+ kernel 3.19.0-12 brakes HDMI Audio
** Description changed:
- it's not yet clear to me what is wrong. I know that if I fail back to
- the previous kernel 3.19.0-11 everything works just fine.
+ it's not yet clear to me what is wrong. But I know
All,
first of all I have AMD E-350D, you have AMD E-350.
I don't know what the "D" stands for, but we don't have the same identical CPU.
I give you the feedback from the kernel developers and from the MainBoard
vendor.
I had already tried the above command (rdmsr). It says "1" ... DISABLED.
@Serge ... I am an experienced sysadmin, I work with Cloudstack ...
therefore I work with a lot of KVM machines.
I don't want to prove anything about myself, but now can you be better
ensured that I am able to access a Computer BIOS and switch a feature
from ON to OFF and viceversa? :)
I've also
don't want to argue, but may I ask why you decided to tag the urgency of this
issue as "low"?
One can stop 30 containers and the host machine and the host machine, by
issuing a simple command on one of the containers and you say urgency is just
"low"? Wasn't it at least "medium", if not "high"?
It's correct what you wrote.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645625
Title:
lxc container can power-off host machine
To manage notifications about this bug go to:
https://bugs.
This the workaround:
apt-get install apparmor-utils
aa-complain /usr/bin/lxc-start
here, I think, there should be the solution:
https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-October/010662.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Rodney, I would say that part of "Ubuntu One" service is on sale, while its
development it's clearly not completed yet.
I would never pay the extra storage space for something that it's missing such
a basic functionality, whereas the competitor (dropbox) started working
perfectly from the very b
it doesn't matter if you have two OS installed. I have a brand new disk and
fails as well.
In my case, it happens when I select BTRFS instead of EXT4.
Crapware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Bad luck. Tested against all those version, and the bug is present.
Added Tag: kernel-bug-reported-upstream
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Just OT.
Yes, the workaround fixes the issue.
OT: Troubles came from the day when Network Manager was invented.
It has never been reliable and - as we can see in every day experience - it has
never been tested properly.
My favorite method for network configuration is the one used in Red Hat 5
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737220/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737217/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Cann
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737224/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737213/+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/1201092
Titl
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737216/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737221/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737215/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
PLEASE NOTE: AMD-V extension on Virtualbox works correctly.
Therefore the extension works properly but it's not recognized by KVM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Canno
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737222/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737223/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Ca
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737219/+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/1201092
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737214/+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/1201092
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1201092/+attachment/3737218/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Cann
apport information
** Tags added: apport-collected package-from-proposed third-party-
packages
** Description changed:
- Firt of all I would like to mention that this bug as been also raised for
Red Hat.
Here is the link: https://bugzilla.redhat.com/show_bug.cgi?id=978608
- I am runnin
Sorry no. I understand that it would be easier to revert a regression bug, but
I bought this motherboard right now.
I can tell is that on Fedora 18 (in the bug mentioned above) they guy tried the
kernels 3.6.10-4.fc18.x86_64 and 3.9.6-200.fc18.x86_64
** Changed in: linux (Ubuntu)
Status
** Description changed:
- - Firt of all I would like to mention that this bug as been also raised for
Red Hat.
+ - Firt of all I would like to mention that this bug as been also raised for
Fedora 18.
Here is the link: https://bugzilla.redhat.com/show_bug.cgi?id=978608
- I am running Ubunt
Tested with latest upstream kernel: the problem is still there.
# uname -a
Linux yasna 3.11.0-031100rc1-generic #201307141935 SMP Sun Jul 14 23:36:57 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
#
# kvm-ok
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm_amd
INFO: Your CPU supports KVM extensi
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201092
Title:
Cannot load kvm_amd modul
Public bug reported:
Binary package hint: sudo-ldap
sorry. I was only getting warnings. There isn't any bug.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: sudo-ldap 1.7.2p7-1ubuntu2.1
ProcVersionSignature: Ubuntu 2.6.38-5.32~lucid1-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i68
** Changed in: sudo (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729735
Title:
sudo-ldap attempts removal of other metapackages
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: sudo-ldap
sudo-ldap, in order to work correctly must have the ability to use the
parameter "sudoOrder" which is only available from versions higher than 1.75
>From the author website it's possible to download the latest deb for Ubuntu
>Lucid and the lat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729795
Title:
sudo-ldap: required version higher than 1.75
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
bug still present in Maverick 10.10
this is the output with debug option enabled:
$ sudo -u news /usr/sbin/fetchnews
LDAP Config Summary
===
uri ldap://127.0.0.1/
ldap_version 3
sudoers_base ou=sudoers,dc=homelinux,dc=doma
binddn (anonymous)
bindpw
did any of you find a workaround?
I have seen that Gnome 3 works properly in Fedora and I think we're missing
some package in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734563
Title:
[g
--
evolution 2.30 is an out of date version
https://bugs.launchpad.net/bugs/678203
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/ubunt
Public bug reported:
Binary package hint: gnome-system-tools
on Ubuntu Maverick,
when trying to create a user, I get a windows which says that I can use special
characters, such as: '.' '-' '_'
In other words, the tools says that I am allowed to use the dot, but this is
slightly wrong.
The dot
--
users-admin has problem when username contains a dot
https://bugs.launchpad.net/bugs/678230
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/li
Public bug reported:
Binary package hint: evolution
Evolution 2.30 in Ubuntu Maverick is outdated.
As Novell suggests Evolution 2.32 is the latest stable and, most important,
Fedora 14 is using Evolution 2.32
You can check it here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=205101
We
Milan, I don't know if the urgency of this issue is low.
Ubuntu installer is affected as well, and I've read on forums about some novice
user not being able to perform the installation as of this issue.
Anyway, as I wrote in my bug report, perhaps the dot should be removed because
it's used by t
Milan, first of all, as I can see the "adduser" command has a switch
"--force-badname" that can be used in this case.
But, if you use this option every kind of strange character will be used. In
other words, if you want to use the dot, you need to pass this option only when
dot(s) appear in the
Public bug reported:
Binary package hint: yelp
I am getting the following error when trying to start yelp:
$ yelp
(yelp:6427): Gtk-CRITICAL **: IA__gtk_tool_button_new: assertion `icon_widget
== NULL || GTK_IS_MISC (icon_widget)' failed
(yelp:6427): GLib-GObject-WARNING **: invalid (NULL) point
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710219
Title:
yelp throws a segfault error and it doesn't start
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
After six months this is the first answer that I receive.
By the way, I don't have maverick anymore, and you can do whatever you wish
with this bug who cares, but those people who still uses maverick still
have this issue, and you shouldn't have to close this bug, but you had to ask
somebody
450]: DEBUG Loaded device Computer (4 presets)
arista.queue [185]: DEBUG Found item in queue! Queue is Transcode queue: [Queue
entry /home/maxadamo/Scrivania/aa/b/test.wmv -> PAL DVD ffmux_dvd ->
/home/maxadamo/Scrivania/aa/b/test.mpg]
arista.discoverer [230]: DEBUG Discovering
/home/maxadamo/
--
cannot convert videos to MPG
https://bugs.launchpad.net/bugs/672243
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
Hi.
This is not a bug in my opinion. This is happening because LXC does not support
udev, it has some extra trouble with upstart, and I suspect you didn't disable
udev on your container.
For the moment just try to disable these upstart jobs located in /etc/init/:
udev.conf
udev-finish.conf
udevm
Public bug reported:
Hi.
sorry for opening this bug here, but I don't where to report it, and the
website is down since two days.
The website https://launchpad.net/ubuntu/+ppas is accessible but it's not
possible to run any query.
The result for a query that you try to run is the following erro
** Description changed:
Hi.
- sorry for opening this bug here, but I don't where to report it, but the
website is down since two days.
+ sorry for opening this bug here, but I don't where to report it, and the
website is down since two days.
The website https://launchpad.net/ubuntu/+ppas is
Hi there.
in the list of "notified" people I can see "launchpad bug Contacts" (if you see
my same page, just have a look on the right)
Is this the recipient for this kind of issues?
In this case I suspect that we can re-open the bug.
Otherwise, is anybody able to provide any link to file this issu
Hi Macarena,
This is issue is solved, and I am changing its status to "fix-released".
Anyway, in the file /etc/modprobe.d/alsa-base.conf I have the following
statement:
options snd-hda-intel power_save=10 power_save_controller=N model=3stack-6ch
I think "power save" options where not inserted by
well: perhaps karmic is still affected and I don't have karmic anymore.
I'll leave the issue as is
--
audio surround 5.1 stopped working after updating
https://bugs.launchpad.net/bugs/450336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: lxc
Bug related information:
# lsb_release -rd
Description:Ubuntu 10.04.1 LTS
Release:10.04
# apt-cache policy lxc
lxc:
Installed: 0.7.2-1~10.04~csz1
Candidate: 0.7.2-1~10.04~csz1
Ve
These tools are not included even in 0.7.2.1 (from PPA) and I suspect
they are not included in 0.7.2.1 from Maverick as well.
--
no lxc-priority tool
https://bugs.launchpad.net/bugs/619148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- lxc container can power-off the host machine
+ lxc container can power-off host machine
** Description changed:
Binary package hint: lxc
Bug related information:
# lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
# apt-cache policy lxc
l
Public bug reported:
Binary package hint: gnome-power-manager
$ lsb_release -rd
Description:Ubuntu maverick (development branch)
Release:10.10
$ apt-cache policy gnome-power-manager
gnome-power-manager:
Installed: 2.31.92-0ubunntu1
Candidate: 2.31.92-0ubunntu1
Version table:
*
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/646405/+attachment/1629057/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/646405/+attachment/1629058/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
Ciao.
Dovrebbe essere risolto da un bel po' di tempo.
Era un problema con il power-manager di gnome, che con questo hardware
interagiva in maniera non corretta.
Adesso funziona perfettamente
Ciao
Massimiliano
2010/8/23 Fabio Marconi
> Hello maxdamo
> is this problem present with the latest upd
Hi all.
This bug report is duplicated (I can't remember which one is the original), and
it's also fixed.
gnome-power-manager was broken with this hardware and we have been using an
alternate power-manager.
Now it works without problems.
cheers
** Changed in: ubuntu
Status: Incomplete =>
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/649478/+attachment/1646842/+files/Dependencies.txt
--
move sudo script to upstart
https://bugs.launchpad.net/bugs/649478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: sudo
I think the lines below can be used in /etc/init/sudo.conf in order to replace
the old sysv script:
# ensure sudo privileges don't persist across reboots
#
description "ensure sudo privileges don't persist across reboots"
start on local-filesy
Public bug reported:
Binary package hint: ppp
Hi.
I created the following ppp-dns.conf for upstart:
# Restore /etc/resolv.conf if the system crashed before the ppp link
# was shut down.
#
description "Restore /etc/resolv.conf if system crashed"
start on (local-filesystems
and gdm
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/651039/+attachment/1652939/+files/Dependencies.txt
--
move ppp script to upstart
https://bugs.launchpad.net/bugs/651039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
thanks Giacomo Tazzari. I am going to test the workaround.
This is an LTS release, we hope that this bug does not stand here forever until
the coming release will be out.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
101 - 165 of 165 matches
Mail list logo
