Ubuntu 12.04 Unity 2D Stuck Issue


Recommended Posts

So I have started a thread over on the Ubuntu forums but it does not seem to be going anywhere. I thought I'd try and post here and see what happens.

http://ubuntuforums.org/showthread.php?t=2106308 is the thread.

Basically, twice now, I have rebooted and came into Unity 2D mode. The first time seemed like it could have been something I did, so I re-installed. Though this time I didn't do anything that could have caused this, and yet it still happened. No matter what I do, logging out and choosing something else, the only thing that works is Gnome Classic (no effects), and Unity 2D.

Please read the thread fully to get the conversation. There is a lot of info over there.

Link to comment
https://www.neowin.net/forum/topic/1132498-ubuntu-1204-unity-2d-stuck-issue/
Share on other sites

After reading your other thread, it definitely sounds like your problem is related to the proprietary AMD graphics drivers. fglrx has never worked well in my experience; I recommend that you try the open-source driver instead. (I realize that someone in the other thread pointed that out as well, but I'm not sure you configured it properly.) Try the instructions I posted here.

Edit: You may also want to read through this thread. It appears to be unrelated to your problem based on the first post, but it devolved into Mindovermaster and I discussing how to get his Radeon HD graphics card working in Ubuntu. I recommend that you read the whole thread, but pay special attention to this post in particular.

  • Like 1

Is different versions of Ubuntu that different?

I know awhile ago I was running Ubuntu 11.04 I believe on the exact same system, and never had issues. Now this keeps happening for no reason? Kinda crazy.

Will read through all that and post back.

**So I went through it, and it's hard to see what is relevant to me and whats not since it's not exactly related. Obviously it's video related, be it hardware or software. It makes sense it's software since I am pretty sure the last time I used Windows it ran all ok.

So ok, it's the new 13.1 AMD drivers that just give up after awhile. Why is Ubuntu 12.04 so much different (in that respect) then 11.04. Kinda annoying.

The main reason I installed the proprietary drivers is because since Steam came to Linux, I wanted to try and play some games, like Skyrim under Wine, and with the open source it's not possible.

Of course I don't really play that many games anymore, and care all that much, playing HD videos is what I mainly do. It's just kinda annoying.

So, how do I go about COMPLETELY removing all of the 13.1 drivers I installed, and putting back the opensource? Every time I have done this before, tried, I end up being stuck outside Ubuntu on a black screen or console mode.

So, how do I go about COMPLETELY removing all of the 13.1 drivers I installed, and putting back the opensource? Every time I have done this before, tried, I end up being stuck outside Ubuntu on a black screen or console mode.

The very first post I linked to has explicit instructions for how to do this.

Follow the instructions below to remove fglrx and revert to radeon.


# Remove the proprietary AMD graphics driver.
sudo apt-get purge $(dpkg --get-selections | awk '{if($1 ~ /fglrx/) print $1}')

# Backup and remove your X configuration file (if one exists).
[ -e /etc/X11/xorg.conf ] && sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.fglrx.0

# Install the necessary packages necessary to get full graphical acceleration.
# Some (or all) of these packages may already be installed.
sudo apt-get install libgl1-mesa-dri-experimental libgl1-mesa-glx linux-firmware-nonfree xserver-xorg-video-radeon

# Reboot to apply changes.
sudo reboot
[/CODE]

[size=4]Is different versions of Ubuntu that different?

I know awhile ago I was running Ubuntu 11.04 I believe on the exact same system, and never had issues. Now this keeps happening for no reason? Kinda crazy.[/size]

Newer versions of Ubuntu ship with newer versions of virtually every package on the system. Sometimes those newer versions add new features, sometimes they fix bugs, sometimes they depreciate or remove outdated functionality, and sometimes, unfortunately, they introduce new bugs. With regard to your graphics driver problem, the issue is most likely the result of Ubuntu 12.04 shipping with a newer version of X which the proprietary AMD graphics driver was not properly tested against.

[size=4]So ok, it's the new 13.1 AMD drivers that just give up after awhile. Why is Ubuntu 12.04 so much different (in that respect) then 11.04. Kinda annoying.[/size]

[size=4]The main reason I installed the proprietary drivers is because since Steam came to Linux, I wanted to try and play some games, like Skyrim under Wine, and with the open source it's not possi[font=Segoe UI, Segoe, Helvetica, Arial, FreeSans, sans-serif][color=#282828]ble.[/color][/font][/size]

[size=4][font=Segoe UI, Segoe, Helvetica, Arial, FreeSans, sans-serif][color=#282828]Of course I don't really play that many games anymore, and care all that much, playing HD videos is what I mainly do. It's just kinda annoying.[/color][/font][/size]

If you were getting poor framerates with the open-source [i]radeon[/i] driver, its most likely because you didn't have the proper firmware and/or MESA 3D libraries installed. Although the driver is open-source, it requires binary firmware to use some of the advanced features of the graphics card. Due to potential legal problems with its distribution, the firmware is not installed by default. The instructions I quoted above involve installing both of the aforementioned components.

  • Like 2

When I put in the first code this is what I got.

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.2.0-29 libgnutls-openssl27 linux-headers-3.2.0-29-generic
  libpython3.2 libc6-i386 lib32gcc1 libntlm0
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Is that normal?

So I went ahead and did the rest of the steps anyway, and rebooted and nothing has changed.

So to me seemed like nothing was removed or changed from that command, I can even still see the AMD Control Center in my menu, so....?

Apparently nothing was removed because the proprietary AMD graphics drivers were not installed in the first place. If you followed the remainder of the steps and you are still stuck in Unity 2D, you must have another problem. At this point, the contents of your /var/log/Xorg.0.log would probably help more than anything else. (Also, running sudo apt-get autoremove is a safe operation. It will remove any packages that were installed as dependencies to packages which are no longer installed.)

Based on that screenshot, you don't have the proprietary Radeon HD graphics drivers installed, only the open-source one. That's exactly what you want. However, if you're still stuck in Unity 2D, that's obviously not your problem. If you post your /var/log/Xorg.0.log I might be able to help you more, otherwise I don't have enough information to help you troubleshoot your problem.

Your Xorg log highlighted something odd: although APT indicates that the proprietary AMD graphics driver is not installed, it is in use on your system. Did you install the driver directly from the binary blob on AMD's website at any point?

Also, fglrx is falling back to 2D acceleration only. That's why you can't load anything but Unity 2D and GNOME Fallback. The relevant lines from your log are the following:


[ 47.871] (II) Loading extension DRI2
[ 47.871] (==) Matched fglrx as autoconfigured driver 0

[ 47.871] (II) LoadModule: "fglrx"
[ 47.871] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 47.885] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[ 47.885] compiled for 1.4.99.906, module version = 9.1.11
[ 47.885] Module class: X.Org Video Driver

[ 47.903] (**) fglrx(0): NoAccel = NO
[ 47.903] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
[ 47.903] (--) fglrx(0): Chipset: "ATI Radeon HD 5800 Series " (Chipset = 0x6899)
[/CODE]

For manual removal of [i]fglrx[/i], try the following:

[CODE]
sudo rm -rf /usr/src/fglrx*
sudo rm -rf /usr/src/modules/fglrx
[/CODE]

Once I do those commands, then what? I installed it from there website, the .run file you download, thats how I installed them.

I'm sorry, still quite new to linux and all that. I don't want to be stuck outside Ubuntu again lol

After you get the driver uninstalled, you need to reboot.

Also, as a rule of thumb, NEVER install software outside of the repository! There are exceptions to this rule, of course, but you should have a very good reason for installing something directly. If you need newer versions of software or something that is not in the repository, use an Ubuntu PPA with the package. If there is none available, try to at least find a deb of the software. Ignoring the repository negates one of the biggest advantages of using Ubuntu.

You won't be stuck in console mode because there is still a graphics driver, just not the proprietary driver. fglrx is the name of the proprietary graphics driver. radeon is the name of the open-source graphics driver. The proprietary driver is a module produced by AMD while the open-source driver is built into the Linux kernel. The only way you could break the open-source driver and force X to revert to the basic vesa driver would be if you removed all the radeon driver support packages. (Namely, libdrm-radeon1 radeontool xserver-xorg-video-radeon libgl1-mesa-dri libgl1-mesa-glx) According to the Aptitude output you posted already, you have not done that, and I did not instruct you to do that before or since. So, your display should still come up.

Alright, so I did those commands and rebooted, still stuck in 2D.

So I guess I am out of luck. My system just does not want to work.

Is the AMD control centre still suppose to be there? Also, when I click on it (admin) asks for password, I enter it and then nothing happens, doesn't open.

**

Let me ask you this, if I wipe the system again, and do a fresh install. If I leave the open-source drivers as they are, you don't think this will happen again, you think it is caused by the AMD drivers?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Stellarium 26.2 by Razvan Serea Stellarium is a free open source planetarium for your computer. It shows a realistic sky in 3D, just like what you see with the naked eye, binoculars or a telescope. It is being used in planetarium projectors. Just set your coordinates and go. Stellarium key features: Realistic simulation of the sky, sunrise and sunset Default catalogue of over 600,000 stars Downloadable additional catalogues for up to 210 million stars Catalog data for all New General Catalogue (NGC) objects Images of almost all Messier objects and the Milky Way Artistic illustrations for all 88 modern constellations More than a dozen different cultures with their constellations Solar and lunar eclipse simulation Photorealistic landscapes (more are available on the website) Scripting support with ECMAScript (a few demo scripts are included) Extendable with plug-ins: 8 plug-ins installed by default, including: artificial satellites plug-in (updated from an on-line TLE database) ocular simulation plug-in (shows how objects look like in a given ocular) Solar System editor plug-in (imports comet and asteroid data from the MPC) telescope control plug-in (Meade LX200 and Celestron NexStar compatible) The major changes of this version: Added new sky culture Added new plugin: Planes Many improvements in plugins Many improvements in Core and GUI Many updates in sky cultures. [full release notes] Download: Stellarium 26.2 (64-bit) | 456.0 MB (Open Source) View: Stellarium Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NASA: This asteroid may not kill us but it probably won't be far off either by Sayan Sen Image by Zelch Csaba via Pexels New observations by NASA's James Webb Space Telescope have eliminated the last remaining impact threat posed by asteroid 2024 YR4, ruling out the possibility that the near-Earth object could strike the Moon in December 2032. NASA said observations collected by Webb on February 18 and 26, 2026, enabled scientists to refine the asteroid's orbit enough to "rule out a chance of lunar impact on Dec. 22, 2032." Instead, asteroid 2024 YR4 is now expected to pass the Moon at a distance of about 13,200 miles (21,200 km). The agency stressed that the update "reflects improved precision in our understanding of where the asteroid is expected to be in 2032 rather than a shift in its orbital path." The announcement closes a remarkable chapter in planetary defence that began in late 2024, when the approximately 60-metre-wide asteroid briefly became the most closely watched near-Earth object in the world. Discovered on December 27, 2024, by the ATLAS telescope in Chile, 2024 YR4 initially appeared to have a small chance of colliding with Earth on December 22, 2032. As astronomers gathered more observations, the impact probability briefly climbed to around 3%—the highest ever recorded for an asteroid of its size—before steadily falling as its orbit became better understood. By early 2025, international observations had ruled out any significant risk to Earth. However, astronomers were left with another possibility: a roughly 4% chance that the asteroid could instead strike the Moon. "The probability that asteroid 2024 YR4 will strike the Moon on 22 December 2032 is now approximately 4%," the European Space Agency (ESA) had said last year, noting that "there is a 96% chance that the asteroid will not impact the Moon." ESA said such an impact, while unlikely, would have presented an extraordinary scientific opportunity. "It is a very rare event for an asteroid this large to impact the Moon – and it is rarer still that we know about it in advance. The impact would likely be visible from Earth, and so scientists will be very excited by the prospect of observing and analysing it," said Richard Moissl, Head of ESA's Planetary Defence Office. "It would certainly leave a new crater on the surface. However, we wouldn't be able to accurately predict in advance how much material would be thrown into space, or whether any would reach Earth," he added. The asteroid also exposed an important blind spot in planetary defence. Because 2024 YR4 approached Earth from the direction of the Sun, it remained hidden from ground-based telescopes until after its closest approach. "We looked into how Neomir would have performed in this situation, and the simulations surprised even us," Moissl said. "Neomir would have detected asteroid 2024 YR4 about a month earlier than ground-based telescopes did. This would have given astronomers more time to study the asteroid's trajectory and allowed them to much sooner rule out any chance of Earth impact in 2032." He added, "As an infrared telescope, like Webb, Neomir would have also immediately given us a much better estimate for the asteroid's size, which is very important for assessing the significance of the hazard." The latest NASA observations underscore the value of space-based infrared telescopes in tracking faint asteroids. According to NASA, Webb made "among the faintest ever observations of an asteroid," extending the object's observational record by nearly eight months at a time when it had become too faint for other telescopes. That additional data allowed scientists to eliminate the remaining uncertainty surrounding its 2032 flyby. Although asteroid 2024 YR4 is now confirmed to pose no threat to either Earth or the Moon, scientists say its discovery remains one of the most significant real-world tests of the international planetary defence system, demonstrating how continued observations can rapidly transform an object once considered hazardous into one whose future path is known with high confidence. Source: NASA, ESA This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Yup. Google is just scraping the entire internet for their own ad profits without sharing revenue with the sources. It's obviously stealing, but since these sites depend upon Google's search scraps to survive... As for me, I just stopped using Google for anything except Reddit searches. If Reddit's own search wasn't complete crapola, I'd never use Google search again.
  • Recent Achievements

    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
    • Apprentice
      daryld went up a rank
      Apprentice
    • Contributor
      Carltonbar went up a rank
      Contributor
    • One Month Later
      The_Focal_Point earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      418
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      130
    4. 4
      Xenon
      69
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!