[Bug 1182999] Re: package nvidia-304-updates 304.88-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Hai, Same error here, update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvidia-experimental-310/ld.so.conf because link group i386-linux-gnu_gl_conf is broken. update-alternatives: warning: skip creation of /usr/lib32/libOpenCL.so because associated file /usr/lib32/nvidia-experimental-310/libOpenCL.so (of link group i386-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-experimental-310/vdpau/libvdpau_nvidia.so.1 (of link group i386-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-experimental-310/vdpau/libvdpau_nvidia.so (of link group i386-linux-gnu_gl_conf) doesn't exist. tried default nvidia driver, current-updates, -310, newer kernel etc. my system is fucked up.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182999 Title: package nvidia-304-updates 304.88-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1182999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178292] Re: Ubuntu 12.04 with linux-generic-lts-raring: nvidia-experimental-310 kernel module failed to build
*** This bug is a duplicate of bug 576648 *** https://bugs.launchpad.net/bugs/576648 same here, no reply, had to reinstall my pc again. Was unable to fix this, after upgrade of the nvidia driver my system went whoo... Never had this with debian... back to debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178292 Title: Ubuntu 12.04 with linux-generic-lts-raring: nvidia-experimental-310 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-raring/+bug/1178292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992424] Re: ext4 filesystem errors on SSD disk
1, always check if powermanagement is of for the sata /SSD's 2. always use AHCI Im having multiple systems. different SSDS ( ADATA 510, VERTEX 3, CRUCIAL V4 ). Running Debian Wheezy ( kernel 3.2) of ubuntu kernel 3.2 and 3.8 only 1 problem found. My OCZ Vertex 3 is running more than 1 year now. 0 problems. latest firmware ) Adata ssd, for 2 weeks now, 0 problems. ( firmware 5.06) Crucial V4, 32Gb, 2 SSD in 2 different machines. 1 disk has errors, upgraded to latest firmware, few days ok, and now again errors, , disk wil go back for repair. Bad SSD's. Faulty firmwares are most of the problems. always check if TRIM is working. Simple test. wget -O /tmp/test_trim.sh "https://sites.google.com/site/lightrush/random-1/checkiftrimonext4isenabledandworking/test_trim.sh?attredirects=0&d=1"; chmod +x /tmp/test_trim.sh sudo /tmp/test_trim.sh tempfile 50 /dev/sdX -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992424] Re: ext4 filesystem errors on SSD disk
and for the users : 99Sono (nuno-godinhomatos) wrote on 2013-03-03: missing the option discard in fstab this is what you should have. /dev/sda1 /noatime,discard,errors=remount-ro 0 1 and yes, you can optimze a lot more but it's not needed, try this like above, reboot and test TRIM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921431] Re: TCP receiver doesn't start
*** This bug is a duplicate of bug 789174 *** https://bugs.launchpad.net/bugs/789174 This problem is still here.. for "Server LTS " this is bad.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921431 Title: TCP receiver doesn't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/921431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789174] Re: rsyslog fails to create tcp socket.
This problem is still here.. for "Server LTS " this is bad.. i tried also the raring version, and... GOOD WORK !! Mar 5 21:37:09 oms kernel: imklog 5.8.11, log source = /proc/kmsg started. Mar 5 21:37:09 oms rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="25002" x-info="http://www.rsyslog.com";] start Mar 5 21:37:09 oms rsyslogd: rsyslogd's userid changed to 101 Mar 5 21:37:09 oms rsyslogd-2077: Could not create tcp listener, ignoring port 514. [try http://www.rsyslog.com/e/2077 ] 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/789174 Title: rsyslog fails to create tcp socket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951087] Re: Samba non-functional on boot.
This bug should be reopend. Not being able to set the interfaces in the samba config files is very bad. I recommend everybody to skip Ubuntu and change to Debian instead. This is not te way to handle Bugs reports. There are lots op people use the interfaces setting. What i you have 2-4-8 Nics and only 1 should use samba. Ive had this problem on 5 server now, and all are running fine now with Debian Squeeze. Ubuntu is slow compaired to debian, just the whole OS is slow, test is your self... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951087 Title: Samba non-functional on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906873] Re: mpt2sas driver is unusable
Hai, while formating the first 512k of my tape. Running ubuntu 12.04 LTS, kernel -40 , everything up2date, only LTO4 tapedrive on sas controller. [588841.364868] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [588841.375947] dd D 81806240 0 26843 26827 0x [588841.375952] 881048fe1cd8 0082 881048fe1c98 a0039318 [588841.375968] 881048fe1fd8 881048fe1fd8 881048fe1fd8 000137c0 [588841.375983] 81c0d020 881049f58000 00a43c794a10 7fff [588841.375998] Call Trace: [588841.376023] [] ? mpt2sas_base_get_smid_scsiio+0x88/0xd0 [mpt2sas] [588841.376034] [] schedule+0x3f/0x60 [588841.376042] [] schedule_timeout+0x2a5/0x320 [588841.376050] [] ? kobject_put+0x27/0x60 [588841.376059] [] ? _raw_spin_lock_irq+0x15/0x20 [588841.376067] [] wait_for_common+0xdf/0x180 [588841.376076] [] ? try_to_wake_up+0x200/0x200 [588841.376083] [] wait_for_completion+0x1d/0x20 [588841.376092] [] st_do_scsi.constprop.17+0x12a/0x280 [st] [588841.376100] [] st_flush+0x218/0x360 [st] [588841.376110] [] ? __fput+0x153/0x210 [588841.376117] [] filp_close+0x3f/0x90 [588841.376124] [] sys_close+0xb2/0x120 [588841.376133] [] system_call_fastpath+0x16/0x1b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906873 Title: mpt2sas driver is unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/906873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789174] Re: rsyslog fails to create tcp socket.
an easy fix... http://www.rsyslog.com/ubuntu-repository/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789174 Title: rsyslog fails to create tcp socket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
