Bug is still present in kernel 4.11.0-041100rc8-generic from ubuntu's
mainline kernel ppa. Latest kernel that is unaffected are all kernels
from the ubuntu 16.10 repos, and from the mainline kernel ppa
4.8.17-040817-generic .
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
Of the kernels in the mainline ppa i can at the moment confirm that none above
v4.8.17 works (ie 4.8.17-040817-generic), and all of
- v4.9.24
- v4.9.25
- v4.10-rc1
- v4.10.8
- v4.10.12
- v4.10.13
have the bug present.
I'll come back with an update after I've tested the proposed v4.11-rc8 (
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1687130/+attachment/4869437/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1687130/+attachment/4869436/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected zesty
** Description changed:
I'm experiencing input/output errors on mounting NFS-shares, starting
from kernel 4.9 and above.
No errors logged to syslog, but the system reports IO-errors when
reading from the mount after only a few
Public bug reported:
I'm experiencing input/output errors on mounting NFS-shares, starting
from kernel 4.9 and above.
No errors logged to syslog, but the system reports IO-errors when
reading from the mount after only a few seconds. Doesn't matter which
program that are accessing the disk.
My
Public bug reported:
Similar to the noplymouth kernel parameter it is useful[0] for many
people[1],[2],[3], etc. to have _one_ _simple_ mechanism to turn off _any_ and
_all_ MOTD output.
Not just ssh configuration, but pam, ~/.hushlogin and the hilarious
~/.sudo_as_admin_successful.
**
References:
[0] https://github.com/jedi4ever/veewee/issues/159
[1] https://github.com/mitchellh/vagrant/issues/391
[2] https://github.com/mitchellh/vagrant/issues/455
[3]
http://groups.google.com/group/vagrant-up/browse_thread/thread/e951417f59e74b9c
--
You received this bug notification
Public bug reported:
The update packages hung at 'Preconfiguring packages
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libpam-modules 1.1.1-2ubuntu5.3
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic x86_64
NonfreeKernelModules:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881791
Title:
package libpam-modules 1.1.1-2ubuntu5.3 failed to install/upgrade:
subprocess new pre-installation script returned error exit status 1
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/dsp1',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/by-path',
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/230/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/574307
apport information
** Attachment added: ArecordDevices.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302224/+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: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302236/+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/574307
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302237/+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/574307
Title:
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302227/+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: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302225/+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/574307
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302232/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302223/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302234/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302229/+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/574307
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302226/+files/Card0.Amixer.values.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.edge.launchpad.net/bugs/574307/+attachment/2302228/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302230/+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/574307
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302231/+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/574307
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302233/+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/574307
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302242/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/574307
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/574307/+attachment/2302235/+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/574307
I'd like to reopen this bug - properly.
I'm seeing matecity deteriorate and then break after some period of usage.
I've tried reinstalling ubuntu-dektop package and all pulse* packages to
no effect.
The strace is after having done all these re-installs.
This will give you some clue about that
I'd like to reopen this bug - properly.
I'm seeing matecity deteriorate and then break after some period of usage.
I've tried reinstalling ubuntu-dektop package and all pulse* packages to
no effect.
The strace is after having done all these re-installs.
This will give you some clue about that
Public bug reported:
Binary package hint: xorg
When logining in the are no windows frames. This problme has been
occuring for some time. Previously I have just done a complete
reinstall of video drivers and gnome. The xession-errors file seems to
give some useful information.
ProblemType:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772980
Title:
metacity does not launch on login
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: .xsession-errors
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/772980/+attachment/2094795/+files/.xsession-errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772980
Public bug reported:
Binary package hint: xfs
every 20-30 minutes I see this:
Mar 31 11:54:36 desktop kernel: [350328.293617] usb 1-8: USB disconnect,
address 74
Mar 31 11:54:36 desktop kernel: [350328.392821] xfs_force_shutdown(sdb1,0x1)
called from line 335 of file
I have almost the same problem as SW (old hardware that dont work with
grub1 or 2) and the bug is still present in ubuntu 10.04. As installning
any grub package breaks my installation this workaround makes kernel
upgrades configure properly:
sudo -s
ln -s /bin/true /sbin/update-grub
apt-get
Public bug reported:
Binary package hint: chromium-browser
Chromium browser process is orphaned and consumes 1.5GB memory.
This has happened twice for the same page - attached.
The ps reported command line was:
/usr/lib/chromium-browser/chromium-browser
** Attachment added: html page cited
https://bugs.launchpad.net/bugs/671181/+attachment/1723331/+files/index.html
--
Chrome browser pids orphaned +1.5 GB memory
https://bugs.launchpad.net/bugs/671181
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK despite the Nvidia SLI site clearly showing two monitors connected in
SLI mode it seems that only one can be connected.
The xorg says:
Failed to set DisplayPort power state.
may be a bug but I can't see any side efforts. Will open another bug if
that changes.
Please mark as closed/invalid.
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: xorg
Two monitors work fine, one plugged in to GPU0 and the other GPU1 -
Xinerama
Both monitors plugged in to GPU0 work fine.
Now set
sudo nvidia-xconfig --sli=on
Logout,
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716584/+files/CurrentDmesg.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716585/+files/Dependencies.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you
apport information
** Attachment added: DkmsStatus.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716586/+files/DkmsStatus.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716587/+files/GdmLog.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a member
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716588/+files/GdmLog1.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716589/+files/GdmLog2.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716591/+files/Lsusb.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a member
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716590/+files/Lspci.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a member
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716592/+files/PciDisplay.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716594/+files/ProcInterrupts.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716595/+files/ProcModules.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716596/+files/RelatedPackageVersions.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716597/+files/UdevDb.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a member
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716598/+files/UdevLog.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: XorgConf.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716599/+files/XorgConf.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716600/+files/XorgLog.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716601/+files/XorgLogOld.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716602/+files/setxkbmap.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716603/+files/xdpyinfo.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716604/+files/xkbcomp.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a
updates after booting with kernel option:
drm.debug=15
log_buf_len=32M
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/667683/+attachment/1716593/+files/ProcCpuinfo.txt
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
You received this bug notification because you
This very simple fix worked for me:
[URL=http://ubuntuforums.org/showpost.php?p=9555086postcount=9][B]sentinella86[/B][/URL]
HTH?
--
boot fails [...] ureadahead [...] terminated with status 5
https://bugs.launchpad.net/bugs/542334
You received this bug notification because you are a member of
This **very** simple fix worked for me:
[URL=http://ubuntuforums.org/showpost.php?p=9555086postcount=9][B]sentinella86[/B][/URL]
and if you want to track another bug report:
[URL=https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/542334][B]boot
fails [...] ureadahead [...] terminated
Public bug reported:
Binary package hint: xorg
Two monitors work fine, one plugged in to GPU0 and the other GPU1 -
Xinerama
Both monitors plugged in to GPU0 work fine.
Now set
sudo nvidia-xconfig --sli=on
Logout, logon and one one monitor comes up, the other, xorg says:
Failed to set
--
Nvidia SLI active: Failed to set DisplayPort power state
https://bugs.launchpad.net/bugs/667683
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 am happy to revert to the std Ubuntu sound stack and trouble shoot but
would like some assurance that I won't be left hanging - I don't mean to
cast aspertions, but my experience in OpenSUSE/Novell was terrible with
bugs left hanging. By hanging I mean not even told - give up for the
moment and
Changing device to usb in :
Preferences Sound Hardware Profile would not 'take'
In the output tab there was no USB device listed.
For the moment I have OSS working after very manual process, but would like to
get back to having a fully functional sound sub-system
On reflection, this broke
Public bug reported:
No sound is coming from any speaker: neither PC nor USB headset.
Debug information collected from running:
# ubuntu-bug audio
I var log messages I do see:
Oct 26 21:23:49 desktop pulseaudio[3184]: module-x11-publish.c:
PulseAudio information vanished from X11!
--
[Realtek ALC262] ALSA test tone not correctly played back
https://bugs.launchpad.net/bugs/666713
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
In case it helps I also see this in /var/log/messages
Oct 23 20:57:27 desktop kernel: [10274.479608] type=1503
audit(1287827847.361:21): operation=open pid=30983 parent=1
profile=/usr/bin/evince requested_mask=r:: denied_mask=r::
fsuid=1000 ouid=1000
Correction to my last comment:
Using the generic printer driver, as described in the thread cited, does
in fact speed up printing.
--
Slow printer processing for HP Laserjet 2100
https://bugs.launchpad.net/bugs/598919
You received this bug notification because you are a member of Ubuntu
Bugs,
Sample file:
http://www.lawrencedrycleaners.com.au/pdf/lawrence-coupons-edgecliff.pdf
Application: evince 2.30.3
Top output:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
19669 lp20 0 127m 92m 3828 R 100 0.4 0:24.21 pdftops
$ ps auxwww | grep 19669
I tried printer set-up described in comment #13 here:
http://ubuntuforums.org/showthread.php?t=1482510page=2
There was no difference :(
--
Slow printer processing for HP Laserjet 2100
https://bugs.launchpad.net/bugs/598919
You received this bug notification because you are a member of Ubuntu
I have the exact same problem with a Pinnacle PCTV Hybrid stick (330e) on
Ubuntu 10.04
The em28xx modules are loaded, but the only devices created are /dev/video0,
/dev/vbi0.
The dvb device (/dev/dvb/adapter0) is not created.
The site
http://jiemeb.free.fr/pinnacle/
does not, currently, have a
I had this same experience. PDF files were not opening in evince.
Desktop is a nomachine client connected to neatx server. Example:
$ evince
No protocol specified
Cannot parse arguments: Cannot open display:
$
Workaround, in the same terminal as above:
$ xhost +
I have never been able to connect but I think that is due to my router
expecting a 64bit WEP key:
every time I try to connect it asks for the passkey, which I input, it
then has the icon of the wireless trying to connect in the tool bar, it
tries to connect for a few minutes until it asks for the
I think this can be marked as confirmed?
I have a fresh install of Ubuntu Lucid, AMD desktop (Opteron/Tyan):
he...@desktop:~ $ uname -r -s -v
Linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010
he...@desktop:~ $ modinfo rt2860sta
filename:
On Lucid 10.04 installing bacula-console-qt does not place any desktop
file in /usr/share/applications
$ dpkg --list|grep -i bacula
ii bacula-client5.0.1-1ubuntu1
network backup, recovery and verification -
ii bacula-common
On Lucid 10.04 installing bacula-console-qt does not place any desktop
file in /usr/share/applications
$ dpkg --list|grep -i bacula
ii bacula-client5.0.1-1ubuntu1
network backup, recovery and verification -
ii bacula-common
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: ubuntuone-client (Ubuntu)
Status: Fix Released = Fix Committed
--
Renaming an UDF and restarting the client generates an endless loop in the SD
https://bugs.launchpad.net/bugs/544499
You
The bug was fixed in the .30 or maybe .31-version of the et131x-driver
in the linux kernel. Another bug is still there though which causes the
module to crash on high network loads (around 100 mbit/sec) which forces
the user to reload the kernel module to make the wired network respond
again. I
I too can confirm this on a LG R200 laptop with the same ethernet
controller as mentioned above. Getting 250.2 wakeups / sec both with the
cable in and out with the latest jaunty kernel in the repositories
(2.6.28-12-generic). The same thing off course goes with the vanilla
jaunty kernel
Public bug reported:
Problem can be reproduced in Gusty and Feisty (ubuntu).
When trying to add a new user:
- Click System - Administration - Users and Groups
- Click Add User
- In the Real Name field, type a name including an apostrophe, for example,
O'Neill
- Fill in the password, etc
- Click
83 matches
Mail list logo
