[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0
Thanks, GU. Your instructions worked. I did not the following dpkg errors when installing the nvidia driver: Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) over (340.106-0ubuntu3) ... Setting up nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0
I cannot get my apt system to work again. I tried adding the bionic- proposed repository as indicated in the link (above), but when I try the 'sudo apt --fix-broken install', it still wants to install the broken libgles1 and libglvnd-dev packages, which fail (as before). Please, could someone provide step by step command line instructions on how to get a working apt system again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
I have experienced this bug on a non Ubuntu system for some time. I spent some time comparing the SparkLAN DPO driver source with the main line kernel driver source and tried a couple of changes. 1) There were some places missing a lock (this change did not affect this bug, however). 2) The DPO driver performed the 32-bit register writes as two 16-bit single write commands instead of one four byte multi-write command. I suspected that this might lead to race conditions setting the registers (not atomic) which was causing the Wi-Fi chip to hang. I thought it possible that the Wi-Fi chip firmware might buffer the two 16-bit single writes and then perform a single 32-bit write to the register, thus making it atomic. I asked SparkLAN about this, but received no reply. Note that the DPO driver performs the 32-bit register reads as a single four byte multi-read, just like the main line kernel driver does. I tested the following patch and the problem went away, either because it fixes the issue or it changes the timing to cover it up. Perhaps a distinction without a difference. ** Attachment added: "rt2x00usb.pat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+attachment/4957754/+files/rt2x00usb.pat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362875 Title: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374965] Re: nvidia-setting crashes on startup
The bug appears to be a crash when unloading the vdpau library, either via a dl_close() or dl_fini() call. It also affects any application using the vdpau library, such as mplayer and mythfrontend. A backtrace from mythfrontend follows: mythfrontend crash details: *** Error in `/usr/bin/mythfrontend.real': free(): invalid pointer: 0x7ffe734bc623 *** Program received signal SIGABRT, Aborted. 0x73352bb9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x73352bb9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x73355fc8 in __GI_abort () at abort.c:89 #2 0x7338fe14 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7349e668 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #3 0x7339c0ee in malloc_printerr (ptr=optimized out, str=0x7349a759 free(): invalid pointer, action=1) at malloc.c:4996 #4 _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 #5 0x7ffe73460fb2 in ?? () from /usr/lib/vdpau/libvdpau_nvidia.so.1 #6 0x7ffe73433f3c in ?? () from /usr/lib/vdpau/libvdpau_nvidia.so.1 #7 0x77dea758 in _dl_fini () at dl-fini.c:257 #8 0x73358149 in __run_exit_handlers (status=0, listp=0x736db6c8 __exit_funcs, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #9 0x73358195 in __GI_exit (status=optimized out) at exit.c:104 #10 0x7333decc in __libc_start_main (main=0x451ca4 main(int, char**), argc=1, argv=0x7fffe238, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe228) at libc-start.c:321 #11 0x00448079 in _start () (gdb) I have observed the same with mplayer. nvidia-settings crashes in a call to dl_close(). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374965 Title: nvidia-setting crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1374965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293970] Re: bonobo-activation-server : could not associate with desktop session
I'm now seeing this problem for the first time, also after applying the latest update to 2.6.32.-25. I was in the middle of filling out a post in FireFox when the screen flashed and dumped me back to the login. Killed all of my open applications. I can't trust the computer anymore. Looking at the dates in this thread, it looks like this is a known problem for years with no fix. Does this affect other distros? -- bonobo-activation-server : could not associate with desktop session https://bugs.launchpad.net/bugs/293970 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
[Bug 587134] Re: Logitech PS2 mouse fails to initialize
I am seeing mouse detection problems that may also be related to this bug. I am using a Microsoft Intellimouse PS/2 scroll wheel mouse. Most of the time, the system fails to detect it properly, and configures it as a generic two button PS/2 mouse. The scroll wheel does not work. Sometimes, it does get it right. I haven't found the magic incantation yet. -- Logitech PS2 mouse fails to initialize https://bugs.launchpad.net/bugs/587134 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
