[Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
I had the latest DisplayLink driver and it still did the same thing to me. And it gets worse than that. No errors are generated but the speed is so slow it is almost unbearable whenever the DisplayLink device is in use. I could click the icon for Files to launch Nautilus from the Unity favorites bar, and it would not appear for almost two whole minutes! Disconnect the device and reboot, and all was fine with the world-- except that it wasn't. I could not use my third monitor to do editing work. Unfortunately, it became easier just to remove Ubuntu from my system and move to another distribution that does work with DisplayLink devices. There were serious problems with power saving, too. Suspend would crash the machine rather than suspend to memory, and this was on a system that I purchased because it was certified for Ubuntu! In Fedora, the distribution I now am using exclusively, I still see flickering when the mouse is moved to the top of the screen but the flickering is bearable compared to the ungodly slowness on the screen with that flickering, in Ubuntu 16.04.2. I do not know what the problem is on Ubuntu with DisplayLink devices but it was too unbearable, and that is unfortunate because I really liked working in Ubuntu, with Unity being my chosen interface. But I hear that even Unity will be going away. I hope that one day the display bugs involving DisplayLink displays will be fixed. Until then, if I want to get work done, and not have to spend time waiting between mouse clicks and app launches, I have to go elsewhere for at least the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1278223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443203] Re: GUFW blocks all incoming VNC connections even if rules allow
Unfortunately, I have ceased using Windows XP, and the computer from which I used VNC connections also has ceased to function. I am now using a DisplayLink device to give me a third screen rather than using VNC to access a virtual machine from another machine to do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443203 Title: GUFW blocks all incoming VNC connections even if rules allow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1443203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
Same here. Ubuntu 16.04. ASUSTek Radeon HD 5750 Formula card and Sabrent DisplayLink, with Dual Dell S2440L monitors connected to the ASUSTek card and a ViewSonic VX922 monitor connected to the Sabrent device via native DVI. Heavy flickering on the mouse cursor with updating of the DisplayLink device. I have it set up so I can see the blinking light and notice that when it flickers the mouse cursor flickers on both the primary display and the secondary display, but not the one connected to the DisplayLink device. No flickering there at all. Another problem is that responsiveness seems slower on the other displays since connecting the DisplayLink device. I ran the Unity Support test and it shows that Unity is supported. $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.8.0) OpenGL version string: 3.0 Mesa 11.2.0 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes It is really seeming to bog down the performance of the system's other displays. It does not do that on Mac OS X or on Windows 7 or on Windows 10. Even typing has been slowed down noticeably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608311] Re: Really, really, really, really long logouts in 16.04
Just noticed something different happens if I wait. I did the log out thing once, and when Unity reappeared I did something else thinking it would stay open anyway. After a few minutes the session logged me off while in the middle of looking for potential solutions to this problem. Not expected but that is another aspect of this same situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608311 Title: Really, really, really, really long logouts in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608311] Re: Really, really, really, really long logouts in 16.04
Updates added a new behavior in addition to the one reported above. If I click the logout item, there is a delay in action as before, and it appears to logout the Unity Desktop after that, but then Unity reappears forcing me to click the menu item again to logout. The second logout attempt then logs out immediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608311 Title: Really, really, really, really long logouts in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
OK, final posting (I could not find a way to edit older posts or I would have just done that instead of multi-posting). A whole lot was wrong (some my fault; got a splitting headache at the moment giving me a bit of brain fog) but I am also attaching a text file of the weather stations listed in a file from the NOAA. The four letter code for the weather station at Baghdad International Airport is ORBB, which I took out of that file just now. The snippet of text to use in instruction number 3 is as follows: Baghdad 33.2625008 44.2346001 Baghdad International Airport ORBB 33.2625008 44.2346001 This should work with both the gnome-clocks app and the gnome-weather app. Information in the NOAA list I attach to this post can be used to make a few more additional Iraqi locations with a little bit of effort at converting the coordinates data. ** Attachment added: "NOAA Weather stations list" https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/204908/+attachment/4723809/+files/nsd_bbsss.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Yet another search gave the following: 33.2625008 44.2346001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Corrected attachment with corrected coordinates (sorry about all the posts). Don't use the other one (although it still worked on my system). ** Attachment added: "Corrected coordinates in xml file" https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/204908/+attachment/4723760/+files/Baghdad%2C%20Iraq%20Location%20xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
The other search also turned up a different latitude and longitude for that airport, too. The second search gave the following coordinates (which differ from the ones given above in the code snippet): 29.56 34.951667 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
The result in comment # 13 is way off. It's actually in Israel. Have no idea how that happened or why that result showed up in the search. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
One thing else. I saw search results that have SDA as an airport code for that airport, but another search turned up the code BGW. Not sure which one is right at this moment. Anyone on the ground know the right one so that I can update the code? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Sorry. That should be tz-hint in comment #9 rather than tx-hint in instruction item 3. The xml coding is correct in the actual code snippet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Here is the attached file. This is working on my system as I write this. ** Attachment added: "Attachment containing modified XML coding" https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/204908/+attachment/4723757/+files/Baghdad%2C%20Iraq%20Location%20xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Here is a workaround: 1. Open /usr/share/libgweather/Locations.xml as an Administrator using gedit or your other favorite text editor. 2. Find the following text: Iraq IQ IZ Asia/Baghdad 3. Insert the following just between Asia/Baghdad and : Baghdad 29.56 34.951667 Baghdad International Air SDA 33.318279 44.416667 4. Save the file. This will give you at least Baghdad and gnome-clocks will display the correct time and allow you to find the city in the list. Others can be created and inserted as needed. I am also adding the XML Iraq entry in my location file as an attachment in case the text does not display correctly above when posted. ** Attachment added: "Location information for Baghdad" https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/204908/+attachment/4723756/+files/Baghdad%2C%20Iraq%20Location%20xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204908] Re: World clock applet lacks country Iraq
Bug still affects me on Ubuntu Xenial 16.04.1. Any Iraqi city used automatically gets set to Iran. This has been going on for quite a while? Is there a fix in the pipeline? Workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204908 Title: World clock applet lacks country Iraq To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/204908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608311] Re: Really, really, really, really long logouts in 16.04
The minimum logout time was 1 minute and 30 seconds just a few seconds ago (timed it using gnome-clocks app in stopwatch mode). Sometimes it is a lot more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608311 Title: Really, really, really, really long logouts in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1608311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608311] [NEW] Really, really, really, really long logouts in 16.04
Public bug reported: Have 16.04 running, and it gives new meaning to really, really, really, really long logouts. I have to hit Log Out... twice to accelerate things a bit. But, if I just hit Log Out... once, I have to wait for a really long time before the system logs out. I have tried past workarounds to fix this but no cigar. Nothing I have tried works. This is a fresh install since upgrading from 14.04.4 to 16.04 failed so badly that I could not keep a stable system without a fresh install. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy unity unity: Installed: 7.4.0+16.04.20160715-0ubuntu1 Candidate: 7.4.0+16.04.20160715-0ubuntu1 Version table: *** 7.4.0+16.04.20160715-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.4.0+16.04.20160415-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Expect that Logging out should be almost instantaneous like previous releases. What is happening instead is that logouts take a very long time. I can click Log Out... and go do something else while waiting. This delays me in leaving my machine for security reasons, and costs man-hours as the time adds up. Luckily, I can work around this by clicking the Log Out... menu item twice but that is a serious annoyance (and possibly a security risk in some environments) in the event that I forget to click the Log Out... menu item twice. ** Affects: unity (Ubuntu) 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/1608311 Title: Really, really, really, really long logouts in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1608311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577246] Re: window has no shadow when run through (gk)sudo
Definitely happening to me on Ubuntu 16.04 with all the latest updates. ** Attachment added: "Screenshot of shadowless gksudo gedit bug" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1577246/+attachment/4676657/+files/Screenshot%20from%202016-06-04%2004-24-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577246 Title: window has no shadow when run through (gk)sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1577246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526537] Re: blk_update_request: I/O error
Still seeing this in 4.4.0 kernels on Ubuntu 16.04. $ dmesg | grep -i blk [5.660121] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 60.473635] blk_update_request: I/O error, dev loop0, sector 151271776 [ 64.663131] blk_update_request: I/O error, dev loop0, sector 193202168 [ 67.053226] blk_update_request: I/O error, dev loop0, sector 155758640 [ 67.119192] blk_update_request: I/O error, dev loop0, sector 155758648 [ 67.189707] blk_update_request: I/O error, dev loop0, sector 155758656 [ 67.353011] blk_update_request: I/O error, dev loop0, sector 154296456 [ 67.411390] blk_update_request: I/O error, dev loop0, sector 155758664 [ 67.469595] blk_update_request: I/O error, dev loop0, sector 154296464 [ 67.529317] blk_update_request: I/O error, dev loop0, sector 155758672 [ 67.586518] blk_update_request: I/O error, dev loop0, sector 155758680 [ 67.669838] blk_update_request: I/O error, dev loop0, sector 155758688 [ 67.746886] blk_update_request: I/O error, dev loop0, sector 155758696 [ 72.829706] blk_update_request: 8 callbacks suppressed [ 72.829712] blk_update_request: I/O error, dev loop0, sector 155758768 [ 73.164340] blk_update_request: I/O error, dev loop0, sector 155758776 [ 73.672569] blk_update_request: I/O error, dev loop0, sector 155758784 [ 80.571864] blk_update_request: I/O error, dev loop0, sector 155758792 [ 80.660314] blk_update_request: I/O error, dev loop0, sector 67514472 [ 80.735506] blk_update_request: I/O error, dev loop0, sector 158408744 [ 80.789497] blk_update_request: I/O error, dev loop0, sector 67514480 [ 80.843609] blk_update_request: I/O error, dev loop0, sector 67514488 [ 80.898603] blk_update_request: I/O error, dev loop0, sector 67514496 [ 80.957007] blk_update_request: I/O error, dev loop0, sector 67514504 [ 99.165416] blk_update_request: I/O error, dev loop0, sector 158408720 [ 100.452488] blk_update_request: I/O error, dev loop0, sector 158409144 [ 100.452497] blk_update_request: I/O error, dev loop0, sector 158409184 [ 106.492835] blk_update_request: I/O error, dev loop0, sector 67515384 [ 107.409988] blk_update_request: I/O error, dev loop0, sector 155760968 [ 705.902224] blk_update_request: I/O error, dev loop0, sector 158410984 [ 707.433389] blk_update_request: I/O error, dev loop0, sector 158411328 [ 710.156894] blk_update_request: I/O error, dev loop0, sector 154299240 [ 711.846610] blk_update_request: I/O error, dev loop0, sector 158411440 [ 712.162845] blk_update_request: I/O error, dev loop0, sector 158411664 [ 713.730702] blk_update_request: I/O error, dev loop0, sector 158411680 [ 800.300872] blk_update_request: I/O error, dev loop0, sector 154299328 [ 880.661945] blk_update_request: I/O error, dev loop0, sector 155762080 [ 881.002646] blk_update_request: I/O error, dev loop0, sector 158411848 [ 883.469054] blk_update_request: I/O error, dev loop0, sector 158411968 [ 1489.772068] blk_update_request: I/O error, dev loop0, sector 158412376 [ 2018.027178] blk_update_request: I/O error, dev loop0, sector 130638328 [ 2031.753835] blk_update_request: I/O error, dev loop0, sector 160431360 [ 2031.774355] blk_update_request: I/O error, dev loop0, sector 160431384 [ 2031.786216] blk_update_request: I/O error, dev loop0, sector 160431496 [ 2031.786916] blk_update_request: I/O error, dev loop0, sector 160431544 [ 2031.788537] blk_update_request: I/O error, dev loop0, sector 160431696 [ 2031.801450] blk_update_request: I/O error, dev loop0, sector 130638544 [ 2031.803146] blk_update_request: I/O error, dev loop0, sector 130638672 [ 2031.803366] blk_update_request: I/O error, dev loop0, sector 130638680 [ 2041.632516] blk_update_request: I/O error, dev loop0, sector 130638800 [ 2041.633634] blk_update_request: I/O error, dev loop0, sector 130638928 [ 2041.633845] blk_update_request: I/O error, dev loop0, sector 130638936 [ 2104.926648] blk_update_request: I/O error, dev loop0, sector 130640656 [ 2104.926911] blk_update_request: I/O error, dev loop0, sector 130640664 [ 2113.298548] blk_update_request: I/O error, dev loop0, sector 116244168 [ 2113.300456] blk_update_request: I/O error, dev loop0, sector 152088160 [ 2113.300827] blk_update_request: I/O error, dev loop0, sector 152088168 [ 2113.301032] blk_update_request: I/O error, dev loop0, sector 152088176 [ 2113.301396] blk_update_request: I/O error, dev loop0, sector 152088192 [ 2113.302102] blk_update_request: I/O error, dev loop0, sector 152088256 [ 2113.302301] blk_update_request: I/O error, dev loop0, sector 152088264 [ 2113.302506] blk_update_request: I/O error, dev loop0, sector 152088272 [ 2113.302812] blk_update_request: I/O error, dev loop0, sector 152088288 [ 2114.032757] blk_update_request: I/O error, dev loop0, sector 130640832 [ 2119.398439] blk_update_request: 4 callbacks suppressed [ 2119.398443]
[Bug 1511735] Re: libnl: fail to bind() netlink sockets
Same problems as above hit me today after an update on my Ubuntu 14.04.3 LTS machine. After applying updates, networking ceased to function. Downgraded libnl* and now networking is working again. Luckily I was able to do the downgrade by first using recovery options at boot from GRuB. From there I enabled networking, and then I resumed booting. Networking lasted long enough to do the downgrade (per instructions above), followed by a reboot of the system. All is working now, and I am waiting for the coming network-manager update to fix the problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1511735] Re: libnl: fail to bind() netlink sockets
Same problems as above hit me today after an update on my Ubuntu 14.04.3 LTS machine. After applying updates, networking ceased to function. Downgraded libnl* and now networking is working again. Luckily I was able to do the downgrade by first using recovery options at boot from GRuB. From there I enabled networking, and then I resumed booting. Networking lasted long enough to do the downgrade (per instructions above), followed by a reboot of the system. All is working now, and I am waiting for the coming network-manager update to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
Just realized I needed to add that I am not using proprietary drivers. ATi Radeon HD 5750, using identical Dell S2440L monitors using identical HDMI cables. I tried to use the proprietary drivers but the problem remained, although with some improvement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/931967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
Has been happening and still happens since the first install of 12.04. I am now at 14.04.3 and the bug still is there. The difference is that I see millions of little cubes, which then jump into big ones that show my previous session from Windows or Fedora, depending on what I was using just prior to Ubuntu! Any way to introduce code into lightDM that flushes the buffers in ATi/AMD cards so that previous contents don't show up? I don't have this problem with GDM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/931967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:p rinting-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/931967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439343] Re: package libgl1-mesa-dri-lts-utopic (not installed) failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-
lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:p rinting-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439343 Title: package libgl1-mesa-dri-lts-utopic (not installed) failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri-lts- utopic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-lts-utopic/+bug/1439343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439343] [NEW] package libgl1-mesa-dri-lts-utopic (not installed) failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-me
Public bug reported: It says that I have modified this file and does not delete the file or overwrite the /etc/drirc file when instructed to do so during the install of this package. The package installation then fails and I am now seeing the driver say that I am running gallium 0.4 on llvmpipe. I checked the file the installer claimed I modified and it has no modifications from me in the file whatsoever. I checked the original file itself in the package and it is a match for what is installed. Not sure what is going but but this is pretty serious if I cannot manage to get anything but llvmpipe to work with a supported card. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri-lts-utopic (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 1 02:46:57 2015 DuplicateSignature: package:libgl1-mesa-dri-lts-utopic:(not installed):trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri-lts-utopic:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri-lts-utopic:amd64 SourcePackage: mesa-lts-utopic Title: package libgl1-mesa-dri-lts-utopic (not installed) failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri-lts-utopic:amd64 UpgradeStatus: Upgraded to trusty on 2014-12-10 (112 days ago) mtime.conffile..etc.drirc: 2015-03-11T16:47:11 ** Affects: mesa-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439343 Title: package libgl1-mesa-dri-lts-utopic (not installed) failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri-lts- utopic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-lts-utopic/+bug/1439343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425304] Re: Plymouth does not display correctly
When I run the 3.16 kernel in 14.04.2, both monitors on my dual monitor setup shut down with loss of signal until the system comes to the Unity login screen. When I run either 3.13 or 3.14 kernels there is no problem. I have found that commenting out lines in the /etc/grub.d/10_lupin file and setting vt_handoff=1 to vt_handoff=0 in the /etc/grub.d/10_linux file will allow the plymouth screen to display properly on a 3.16 kernel. Whatever the 3.16 kernels do differently seems to prevent the plymouth screen from displaying on boot unless vt_handoff is disabled in a file (two files if the user is running Ubuntu in a Wubi install). The relevant lines in the /etc/grub.d/10_lupin file to disable by commenting them out are as follows: #for word in $GRUB_CMDLINE_LINUX_DEFAULT; do # if [ $word = splash ]; then #GRUB_CMDLINE_LINUX_DEFAULT=$GRUB_CMDLINE_LINUX_DEFAULT \$vt_handoff # fi #done After that, plymouth displays correctly every bootup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425304 Title: Plymouth does not display correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-utopic/+bug/1425304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425304] Re: Plymouth does not display correctly
Don't forget to run sudo update-grub before rebooting or you will see no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425304 Title: Plymouth does not display correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-utopic/+bug/1425304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370707] Re: Plymouth does not display the graphical boot splash
Seeing the same in Trusty 14.04 LTS with kernel 3.16. I am now at 3.16.0-34 and still see the same behavior. Every fix I have tried fails to make it work as it did work in as late as 3.14 kernels, and did work in all the 3.13 series. I think that the problem is kernel configuration in the 3.16 kernels. I do not know about 3.15 kernels as none of those I attempted to use would boot my system properly at all. I have yet to build my own 3.16 kernels to try to track this down but I have noticed that one of the differences between the 3.13 and 3.14 series kernels, and the 3.16 series kernels, is that CONFIG_DRM_RADEON_UMS is commented out in 3.16 kernels, but not in either 3.13 or 3.14 series kernels from Ubuntu (at least not the ones I used, and I have not been building too many of my own kernels this LTS release, as that kind of defeats the purpose of an LTS release). I am using a Radeon HD 5750 card with dual, Dell S2440L monitors. Any further information needed, let me know. I am going to attempt to use apport to send up my configuration, and so forth, in a couple minutes. Last time I tried it failed in another bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370707 Title: Plymouth does not display the graphical boot splash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1370707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370707] Re: Plymouth does not display the graphical boot splash
Tried and apport-collect failed again. Just let me know if any other information is necessary and I will do what I can to provide it to help track this down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370707 Title: Plymouth does not display the graphical boot splash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1370707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370707] Re: Plymouth does not display the graphical boot splash
Per comment #3 I can confirm that manual deletion of $vt_handoff or vt_handoff=7 from the grub kernel line allows the plymouth splash screen to display on a 3.16 series kernel. Changing vt_handoff=1 to vt_handoff=0 in the /etc/grub.d/10_linux file does not change the behavior or omit this kernel parameter from the grub menu if you are running Ubuntu in a Wubi installation, as the parameter on the kernel line is replaced with $vt_handoff by the /etc/grub.d/10_lupin script. Whatever is going on there with vt_handoff is affecting plymouth splash screen only when running a 3.16 series kernel. It does not affect 3.13 or 3.14 series kernels. Hope this additional information helps track down this bug. In my configuration, leaving $vt_handoff in the kernel line causes both monitors to shut down with no signal from the video card until it reaches the lightDM/Unity screen while also running on a 3.16 series kernel, so this bug is more severe than just a cosmetic issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370707 Title: Plymouth does not display the graphical boot splash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1370707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
I am seeing the same things as reported above, and I am seeing this in 14.04 LTS. I switched to fglrx to try to get rid of the corruption and still saw it, although it was less than while using the Open Source drivers for AMD/ATi. Tearfree created other problems so I went back to Open Source. Now the video corruption is back again, and sometimes it includes bits of desktop from a previous session even after a reboot. I even tried switching to another ppa to get the latest and greatest versions from git and still see the corruption while waiting for the greeter to be ready for logon, and between greeter screen and logon to desktop, as well as when I log off and wait for the greeter to return to ready. ASUS/ATi Radeon HD 5750, dual head with a pair of Dell S2440L LCD monitors. Ubuntu 14.04.2 LTS. Wanted to try the above workaround but this system does not use GDM, so no directory or files on which to do the same edits. $ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:p rinting-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty $ apt-show-versions unity-greeter unity-greeter:amd64/trusty-updates 14.04.11-0ubuntu1 uptodate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/931967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069350] Re: suspicious /.rpmdb root directory
Just found this same abovementioned /.rpmdb directory on my install. It wasn't there before and hasn't ever been there before this morning. I did not do anything involving a kernel. Although vmware player uses dkms when a new kernel is installed, no new kernel was installed today. When will 4.11.2-2.1 be made available for Trusty? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069350 Title: suspicious /.rpmdb root directory To manage notifications about this bug go to: https://bugs.launchpad.net/rpm/+bug/1069350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874146] Re: Multimonitor: New windows open on the wrong monitor, Place Plugin settings silently ignored
Same here, with identical monitors at identical resolutions. The only difference is that one is using a DVI-VGA adapter. I see this whenever I open LibreOffice. The splash screen comes up on the secondary monitor and the application comes up on the primary. Using an ATI Radeon HD 5750. I tried modifying settings in compiz but no effect. Using 14.04 LTS. Same problem as in 12.04 LTS. Other applications will load on the primary but open dialogs on the secondary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874146 Title: Multimonitor: New windows open on the wrong monitor, Place Plugin settings silently ignored To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/874146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Similar problem here. Seeing 50% CPU when running Chromium. Using fglrx, because FOSS drivers gave horrid responsiveness and bad video corruption at login screen and while watching video. However, I am not using 14.04 LTS in a virtual machine. I am using it in a Wubi install, however, until I can buy a new computer next year. $ sudo dmidecode | head -15 # dmidecode 2.12 SMBIOS 2.6 present. 48 structures occupying 1785 bytes. Table at 0x0009F400. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: A06 Release Date: 12/01/2010 Address: 0xF Runtime Size: 64 kB ROM Size: 1024 kB Characteristics: PCI is supported $ sudo lshw -C cpu *-cpu description: CPU product: Pentium(R) Dual-Core CPU E6700 @ 3.20GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: Pentium(R) Dual-Core CPU E6700 @ 3.20GHz serial: To Be Filled By O.E.M. slot: CPU 1 size: 3203MHz capacity: 3203MHz width: 64 bits clock: 266MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm tpr_shadow vnmi flexpriority cpufreq configuration: cores=2 enabledcores=2 threads=2 $ sudo lshw -C video *-display description: VGA compatible controller product: Juniper PRO [Radeon HD 5750] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=fglrx_pci latency=0 resources: irq:47 memory:d000-dfff memory:f7ee-f7ef ioport:d000(size=256) memory:f7ec-f7ed $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 5700 Series OpenGL version string: 4.3.12798 Compatibility Profile Context 13.35.1005 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
