** Description changed:
Hi,
- After latest kernel upgrade on Trusty 14.04.2 LTS on two of my systems,
- the system did not boot, it was locked on Plymouth splash screen.
+ After purge of old packages with command "sudo aptitude purge ~c" on
+ Trusty 14.04.2 LTS on two of my systems, the syste
Public bug reported:
Hi,
After latest kernel upgrade on Trusty 14.04.2 LTS on two of my systems,
the system did not boot, it was locked on Plymouth splash screen.
The culprit is that for a reason I don't know symlink /etc/X11/X was
removed during the upgrade, and X failed to start.
In that case
Note that the bug only occurs when apps not compatible with PA 4.0 are
started. With other apps the issue does not occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355025
Title:
After suspend/r
Hi,
The trick is that I could reproduce exactly the same issue on my Dell
Inspiron 1525 (without HDMI sound card) before I upgraded its Skype to
version 4.3, as long as Skype was connected. So it does not seem to have
anything to see with HDMI but with something else.
** Changed in: pulseaudio (U
Hi,
Analog is always selected (but it's true that my graphics card appears
as a sound card, which might be the source of the issue).
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
HI,
I've remarked the following bug, at least under KDE :
DO : open your KDE session
DO : launch an app which has not been set compliant with pulseaudio (for
example, Skype 4.2, but in that case you need to log into the service so that
it plays a sound - issue no longer rep
Public bug reported:
Hi,
I've upgraded my KDE to version 4.13.1 from version 4.13.0 in Trusty. When I
try to send an Email, I get the following error message :
Notes : Impossible d'écrire dans le fichier de courrier électronique
/home/julien/.local/share/akonadi_akonotes_resource_0/tmp/14031260
OK looks like this has been fixed with latest KDE upgrades.
** Changed in: pulseaudio (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/1303285
Title:
No sound af
Workaround :
sudo dpkg --purge libpostproc52:i386
Then reinstall libpostproc52.
Rgds,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277552
Title:
libpostproc52 does not support multiarch
To mana
Workaround :
sudo dpkg --purge libpostproc52:i386
Then reinstall libpostproc52.
Rgds,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286836
Title:
package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 f
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303285/+attachment/4069155/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303285
Title:
No
Public bug reported:
Hi,
I'm using the following system :
Kubuntu 14.04 AMD64
AMD Phenom 9850
Mobo Asus M2N-SLI Deluxe w/ chipset NForce 570 SLI
The issue that after a resume I always have no sound. The culprit is
likely to be pulseaudio, as once I've killed it sound partially
reappears for KDE
*** This bug is a duplicate of bug 1302264 ***
https://bugs.launchpad.net/bugs/1302264
Public bug reported:
Hi
On two different computers, the first one upgraded two weeks ago to
Trusty and the second one updated today after a Saucy fresh install, the
suspend/login/restart features are disab
Same issue there
** Changed in: libpostproc (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/1277552
Title:
libpostproc52 does not support multiarch
To manage
Same issue there
** Also affects: vlc
Importance: Undecided
Status: New
** Also affects: mplayer
Importance: Undecided
Status: New
** Also affects: kaffeine
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hi,
With latest systemd updates with cgmanager support, system won't boot if
/usr is mounted on a different partition from /. The reason (that you
can see when booting system in failsafe mode and trying to launch dpkg
or anything and seeing that system is complaining) is that
Hi,
This fix causes a regression when /usr is not mounted on the same
partition as /. See bug report 1301544
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297363
Title:
[FFe] Add cgmanager support
Once I've removed libgphoto2-2 :
^Cadministrateur@pcathlon64:~$ sudo debsums -s
[sudo] password for administrateur:
debsums: invalid line (1) in md5sums for devolo-dlan-cockpit:
/mnt/repository/kolja/dune/software-packages/cockpit/obj.linux.rel/tmp.DwmJybAOOr/debian
/mnt/repository/kolja/dune/so
which pam-auth-update :
/usr/sbin/pam-auth-update
For the yabause-qt it's an error in /var/lib/dpkg/available, nothing
unofficial. I've removed it from /var/lib/dpkg/available and the warning
is gone. Probably some encoding issue.
Output of my debsums (some errors but nothing looks really critica
Attached /var/log/dpkg.log
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4053213/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi,
I was using aptitude to manage packages...
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4053212/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
And after re-running sudo pam auto-update --package everything was OK
again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
Installing i386 and amd64 PAM stacks causes shutdown/logout/e
OK so after rebooting I got the issue with the suspend feature. I attach
you the updated common-session file
** Attachment added: "common-session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4050139/+files/common-session
--
You received this bug notification be
Hi,
After reinstalling libpam-systemd:i386 systemd-logind does not start
anymore, however if I remove it it starts again.
So the issue really lies within the mix libpam:i386 and libpam:amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Hi,
I've logged out and logged in and my logind session is still in a
working state.
I've run sudo pam-auth-update --package and everything is fine.
Attached file /etc/pam.d/common-session
** Attachment added: "common-session"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+
Hi,
I've also fixed the issue for the suspend feature and lightdm feature by
removing packages libpam-modules:i386 and libpam-cap:i386, which have
the same kind of conflict as explained above. I don't know what happened
during the upgrade, but it looks like the upgrade tool was a bit lost
between
To avoid this, it might be possible to set some kind of conflict between
the i386 module and the amd64 module ? OK it smells, but this might be
an option. What do you think ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hi,
I had both libpam-systemd:i386 and libpam-sytemd:amd64 on my AMD64
system and this confused PAM.
The upstart job now works fine, I don't have the "cannot start daemon".
I didn't post the result of "sudo start systemd-logind" but it said
"started daemon systemd-logind" or something like this.
Hi,
To answer your questions :
1/
julien@pcathlon64:~$ aptitude search libpam-systemd
i libpam-systemd - system and
service manager - PAM module
i libpam-systemd:i386 - system and
service
However with the update (and a restart) I've seen that the
suspend/restart/shutdown icons are still grayed out in my lightdm, and
that the suspend menu is still missing from my KDE, but things are
better
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
After installing pamcap in 64 bits message "PAM unable to
dlopen(pam_cap.so): /lib/security/pam_cap.so" disappeared, however the
issue is still there. :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Another stuff in my auth.log which may help :
Mar 26 21:13:14 pcathlon64 sudo: PAM unable to dlopen(pam_cap.so):
/lib/security/pam_cap.so: Ne peut ouvrir le fichier d'objet p
artagé: Aucun fichier ou dossier de ce type
Mar 26 21:13:14 pcathlon64 sudo: PAM adding faulty module: pam_cap.so
-- On ev
Also tried with qdbus with the following line (as I'm using KDE) :
qdbus --system org.freedesktop.login1 /org/freedesktop/login1
org.freedesktop.login1.Manager.CanReboot
Error: org.freedesktop.DBus.Error.Spawn.ExecFailed
Cannot launch daemon, file not found or permissions invalid
--
You received
I've also found this in my syslog :
Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activating service
name='org.freedesktop.login1' (using servicehelper)
Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activated service
'org.freedesktop.login1' failed: Cannot launch daemon, file not found or
pe
Attached file.
** Attachment added: "logind.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4043358/+files/logind.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubun
** Changed in: systemd (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/1295521
Title:
cannot shutdown/suspend/restart from the GUI
To manage notificati
Hi,
For the output, it gives me the following :
administrateur@pcathlon64:~$ sudo /lib/systemd/systemd-logind
[sudo] password for administrateur:
Watching system buttons on /dev/input/event1 (Power Button)
Watching system buttons on /dev/input/event0 (Power Button)
New seat seat0.
Failed to save
Sorry posted comment to the wrong bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002981
Title:
Aptdaemon fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Oh and from my lightdm logs I also get the following messages :
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun
fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInp
Oh and from my lightdm logs I also get the following messages :
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun
fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusIn
Hi,
When launching gdbus, error is :
julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o
/org/freedesktop/login1 -m org.freedesktop.login1.Manager.CanReboot
Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch
daemon, file not found or permissions invalid
Public bug reported:
Hi,
I've upgraded to Ubuntu Trusty last week, and since the update to KDE
4.12.95 my CPU usage is extremely high. The culprit is akonadi's MySQL
process, which eats a lot of my CPU.
My system :
AMD Phenom 9850 x4
8 GB RAM
Kubuntu 14.04 AMD64
Note that I've got 12000 emails
** Also affects: lightdm
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
cannot shutdown/suspend/restart from the GUI
To manage notification
** Package changed: shadow (Ubuntu) => lightdm (Ubuntu)
** Package changed: lightdm (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
cannot shutdown/suspend
Public bug reported:
HI,
Steps to reproduce :
DO : perform an upgrade of Kubuntu with latest updates of qdbus.
DO : remark that package qdbus-qt5 is normally not installed.
DO : logout of KDE
DO : login into KDE
EXPECT : login runs fine
ACTUAL : cannot login within KDE, with message "qdbus cannot
Public bug reported:
Hi,
After I upgraded to Ubuntu Trusty, I've seen that it is no longer
possible to suspend/shutdown/restart my system from the GUI. In other
words within lightdm buttons to do so are grayed out, and within KDE it
is the same. I had the same bug in Saucy beta and the culprit wa
Same there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286836
Title:
package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch
Invalid, is actually due to a bug within my hardware which occurs after
some suspend/resume cycles.
** Changed in: glib2.0 (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.n
Public bug reported:
Hi,
After latest update of the following components from 2014-02-14 :
libglib-2.0-0 and libc-bin my X.org always crashes when resuming from a
suspend, causing a hard reboot. The strange thing is that the next
reboot causes the same thing, and afterwards everything is OK again
Public bug reported:
Hi,
Currently boinc-nvidia-cuda package depends on nvidia-current package,
which relies itself on nvidia-304 driver. This version is outdated,
especially for users who are at the same time steam users.
So please change the dependency requirements so that it depends on
nvidia
Hi,
So yes on the computer on which I reported the issue the issue is also
reproducible with Nouveau driver.
Discussion URL (actually kernel bug) :
https://bugzilla.kernel.org/show_bug.cgi?id=48951
Rgds,
** Bug watch added: Linux Kernel Bug Tracker #48951
http://bugzilla.kernel.org/show_bug
Hi Christopher,
No, this is completely unrelated to NVidia graphics. My father uses an
Intel Core i5 CPU with B75 chipset and the nvidia graphics blob, and
he's not affected.
The culprit is the NForce driver, as explained in the kernel mailing
list.
--
You received this bug notification because
Hi Christopher,
Yes this is exactly the case, the bug is still not fixed. But in case
you couldn't fix it until trusty release just publish the workaround as
a release note, as it targets a rather old chipset model.
Rgds,
--
You received this bug notification because you are a member of Ubuntu
Hi,
With the workaround I provided the bug is not there, but without it it
is still there.
Now as this bug has many duplicates you can close it, but please at
least provide the workaround in Ubuntu release notes.
Rgds
--
You received this bug notification because you are a member of Ubuntu
Bug
*** This bug is a duplicate of bug 1241101 ***
https://bugs.launchpad.net/bugs/1241101
Hi,
Actually I do not have smartgit.sh at all... Could you attach it to the
bug please ?
Rgds,
** This bug has been marked a duplicate of bug 1241101
Java crash in libglib-2.0 after upgrade from 13.04
Public bug reported:
When I start any Eclipse-based app (from Eclipse 3.x branch) I got a
crash with message :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7fb5a73ac528, pid=22497, tid=140418638948096
#
# JRE version: 7.0_25-b30
# Java VM: O
*** This bug is a duplicate of bug 1181878 ***
https://bugs.launchpad.net/bugs/1181878
Sorry, the bug is actually not a duplicate.
** This bug has been marked a duplicate of bug 1181878
[M2N-SLI DELUXE] Plugging in Western Digital Caviar Black 500 GB / 1 TB
prevents suspend
--
You recei
*** This bug is a duplicate of bug 1181878 ***
https://bugs.launchpad.net/bugs/1181878
Hi Rachelle,
Actually I've posted another bug related to this one, as linked in the
report. There I provide a workaround to the bug (issued from kernel.org)
Rgds,
--
You received this bug notification be
*** This bug is a duplicate of bug 1181878 ***
https://bugs.launchpad.net/bugs/1181878
Hi,
Actually I'm not using any longer i386 release on this computer, but it
is not fixed either on AMD64.
Bug this bug is a duplicate of bug 1237058 and marking it as duplicate
(I provide a workaround in t
Not a bug, or fixed with kernel 3.11-12. The issue could also deal with
my computer, which becomes sometimes unstable after having been switched
on for quite a long time through a suspend/resume cycle, until I shut it
down completely for a couple of hours.
** Changed in: linux (Ubuntu)
Stat
Public bug reported:
Hi,
I've noticed that after a resume, my computer often freezes or becomes
unstable, forcing me to reboot. The regression occured after update to kernel
3.11.0-11-generic, and I've set the following line in my /etc/rc.local as a WA
for bug 1181878 :
echo 0 > /sys/power/pm_
Hi,
I've unfortunately no way to get back that early, but the offending
commit is listed in the bug report I've mentioned on kernel.org, see :
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=966f1212e1ac5fe3ddf04479d21488ddb36a2608
Rgds,
** Changed in: linux (Ubuntu)
pactl list before
** Attachment added: "pactl_list_before"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851748/+files/pactl_list_before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
pactl stat after
** Attachment added: "pactl_stat_after"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851751/+files/pactl_stat_after
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
My system log from suspend to resume :
Sep 30 20:39:01 pcathlon64 CRON[5976]: (root) CMD ( [ -x
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5
$(/usr/lib/php5/maxlifetime))
Sep 30 20:39:21 pcathlon64 anacron[
pactl list after
** Attachment added: "pactl_list_after"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851749/+files/pactl_list_after
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I couldn'nt upgrade to latest adi driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232295
Title:
pulse audio does not restore sound after suspend
To manage notifications about this bug go to:
My pulse audio log file.
I've noticed that I just need to kill PA. Phonon restarts it
automatically.
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851747/+files/pulseverbose.log
--
You received this bug notification be
pactl stat before
** Attachment added: "pactl_stat_after"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851750/+files/pactl_stat_after
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Invalidated the ticket as it was related to a faultly logind shipped
with systemd packages, and after update of it everything is fine again.
** No longer affects: lightdm
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member
Hi,
The bug never occured before Quantal. It has been a regression
introduced with kernel 3.4 or 3.5 if I recall well (version mentioned in
the bug report on kernel.org)
Rgds,
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
Hi, bug is still there with upstream... :-(
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.12
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
This might be a policykit rule issue :
https://bugzilla.redhat.com/show_bug.cgi?id=872797
** Also affects: lightdm
Importance: Undecided
Status: New
** Bug watch added: Red Hat Bugzilla #872797
https://bugzilla.redhat.com/show_bug.cgi?id=872797
--
You received this bug notification
Public bug reported:
Hi,
I'm using Kubuntu 13.10 saucy 64-bits, upgraded yesterday from Raring.
During the upgrade, I got a message which broke the complete update,
i.e. libc6 failed to configure because it could not replace files within
/lib64, complaining with an error message like this :
A co
Public bug reported:
Hello,
I've a Kubuntu install from Kubuntu raring, and after upgrading Akonadi
(more specifically MySQL) started to eat a lot of CPU. Actually after
resetting Akonadi everything went fine, i.e. shutting down Akonadi and
Kontact, removing folder ~/.local/share/akonadi, restart
Public bug reported:
Hi,
I'm using lightdm with KDE team on Kubuntu Saucy.
When you click the shutdown button within Lightdm interface, the
shutdown, reboot and suspend buttons are actually grayed out so one
could not reboot without using command line. Thus, it's impossible to do
the same operat
Public bug reported:
DO : log in (at least within KDE).
DO : open an app which plays sound, and listen to sound.
DO : stop the app started in previous step.
DO : suspend
DO : after resume, reopen the app, and try to play sound.
EXPECT : sound appears, and you can listen to it.
ACTUAL : sound does
Hi,
Tested with kernel 3.11 after upgrading to saucy, and unfortunately this
does not fix the bug. :-(
** Tags removed: kernel-bug-exists-upstream-v3.10-rc2 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.11 saucy
--
You received this bug notification because you are a membe
Hi,
Actually this is corresponds to Kernel bug #48951.
Workaround is as follows :
- Put in /etc/rc.d the following line (before exit 0) :
echo 0 > /sys/power/pm_async
This works.
The issue is related to NVidia MCP55 chipset.
Rgds
--
You received this bug notification because you are a member
Hi,
Here's a workaround for the bug, from kernel.org bug mentioned above :
- Run as root :
echo 0 > /sys/power/pm_async
(added to /etc/rc.local to be permanent)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** 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/1181878
Title:
Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent
Hi,
The kernel bug actually exists upstream, which is not surprising as the bug I
referenced is marked as "won't fix". However it turns out that there's one
1-line offending commit which broke everything, as stated in comment #10 of the
bug. The commit is :
http://git.kernel.org/cgit/linux/kern
I've remarked that the change to udev rules proposed as a workaround
does not work, since attribute power/async is not even present under the
/sys tree.
My output for udevinfo for one of my HDDs :
administrateur@pcathlon64:~$ sudo udevadm info -a -p /sys/block/sda
[sudo] password for administrateu
Seems to be related to this bug :
https://bugzilla.kernel.org/show_bug.cgi?id=48951
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181878
Title:
Driver for hdd Western Digital Caviar Black 500 GB /
Actually this looks like a NVidia MCP5x bug, as explained there :
http://marc.info/?l=linux-ide&m=136297331308023&w=2
** Bug watch added: Linux Kernel Bug Tracker #48951
http://bugzilla.kernel.org/show_bug.cgi?id=48951
--
You received this bug notification because you are a member of Ubuntu
B
After re-reading the bug report I found out that the HDD brand there is
not the culprit, as /dev/sdd points to a WD Caviar Blue. Anyway there's
something fishy with the HDD driver there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This bug is actually related to bugs 1057664 and 1171560, and is an
upstream bug.
When I suspend my system to RAM, actually suspend does not work and
instead I get a blinking cursor, and after some time system turns back
again.
After some debugging, I've found this within th
Found actual workaround there :
http://ubuntuforums.org/showthread.php?t=1978290
Maybe it should be included in the default pm-utils package, as it seems
to be a fairly common issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Workaround there :
http://ubuntuforums.org/showthread.php?t=1978290
It'd be very nice that it is included within package pm-utils at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057664
Title
I upgraded my system to 64-bit and the bug no longer occurs (even
without formatting). So I've very strong suspicion around something PAE-
related...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10576
Same issue there. Maybe this is related to bug 1171560 which I affected
to the kernel. Maybe this is a mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154660
Title:
[LENOVO 7465CTO] suspend/
Yes I'm also convinced it is an upstream bug. However I don't know which driver
is faultly. I only know the following elements :
- NVidia binary driver is not faultly. (I could test the same driver on another
NVidia card and suspend fully worked)
- None of my USB devices seem to be faultly (tried
** Attachment added: "Attached my pm-suspend.log file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+attachment/3650789/+files/pm-suspend.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Hi,
On my computer suspend to RAM is actually broken. Here's my system :
AMD Phenom x4 9850
8 GB RAM
Kubuntu Raring 32bits w/ PAE
GeForce 660 Ti with NVidia 304 driver
Actually when I suspend the OS to RAM a blinking cursor appears but the
process is halted and the computer
** Bug watch added: Email to joseph.salisbury@canonical #
mailto:joseph.salisb...@canonical.com
** Also affects: linux via
mailto:joseph.salisb...@canonical.com
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Added file pm-suspend.log. You can see suspend attempts before and after
my upgrade, all failed actually.
** Attachment added: "pm-suspend.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057664/+attachment/3643229/+files/pm-suspend.log
--
You received this bug notification because
The issue was actually due to a combination of NVidia 304.XX driver with
linux-image-3.8.0-17-generic. With latest NVidia 304 driver update,
problem is gone.
However this could be good that nvidia-current actually points to
nvidia-310 instead of NVidia-304, but with latest kernel image
NVidia-310
Hi,
Tried with latest kernel snapshot (3.9.0-rc6) and the bug is still
present, so added the tag "kernel-bug-exist-upstream".
Rgds
** Tags removed: kernel-unable-to-test-upstream needs-upstream-testing
** Tags added: kernel-bug-exists-upstream raring
--
You received this bug notification becau
I also highlight the point that the bug did not appear with kernel image
3.8.0-16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1166988
Title:
With latest xserver-xorg update, switching to VT does
Hi,
Kernel bug exists upstream, actually.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-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 - 100 of 282 matches
Mail list logo
