I've been running it since January. It's not really.
cgroup-bin breaks suspend on my computers (bug is reported and left without attention), radeon on dual-GPU notebooks has to be blacklisted, a lot of apps crash with 'ASSERT failure in : "Got an update for an invalid inteface. Investigate this.", file atspiadaptor.cpp, line 899' because of some changes in accessibility support. And so on.
Posted Apr 27, 2012 19:54 UTC (Fri) by tcourbon (subscriber, #60669)
[Link]
I beg to differ sir.
I have been also running it since Jannuary and find it quite stable. Also I second the assertion that Unity looks more like a viable shell than before. My workflow still fit better in KDE but I'm kind of fond of the HUD ("look mommy I use the drop-down menus without touching the mouse").
I never got into the Ubuntu-hate mood and that's not the release that will push me into the hating mud.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 27, 2012 21:10 UTC (Fri) by tjc (subscriber, #137)
[Link]
> In short, it's a usual Ubuntu release.
I've been running Ubuntu since Warty, and I've come to expect a certain amount of brokenness with a new release. Usually a subsequent release will fix problems with the prior, but introduce a new set of problems of its own. This has motivated me to skip about every other release. Unfortunately, I've had more problems with the LTS releases, but this may be that I'm just "unlucky at hardware" and not characteristic of other people's experiences.
I don't know if this is really avoidable, considering all the untested hardware that it runs on, or if other Linux distros are any better. I've also run Debian testing for many years, and while that is sometimes a bit rough around the edges, the problems are more incremental in nature, so I don't notice them that much (with a couple of alarming exceptions over the years).
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 28, 2012 9:52 UTC (Sat) by Pawlerson (guest, #74136)
[Link]
Ubuntu team can't do much if you're running broken drivers. If you're running nvidia or amd blob then blame them.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 28, 2012 15:02 UTC (Sat) by dlang (✭ supporter ✭, #313)
[Link]
perhaps you missed the issues a year or so ago when the Intel drivers happened to break for some (but not all) Intel cards, just in time to get into a LTS release.
It was not a fun upgrade for a lot of people, especially ones who thought they had good hardware because they weren't running a AMD or Nvidia video card.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 3, 2012 14:20 UTC (Thu) by Cato (subscriber, #7643)
[Link]
Exactly - a fixed release timeline is really a bad idea for anything that depends on hardware (including desktop environments using 3D, these days), though a flexible release date would only help if significant bugs are taken seriously.
Ubuntu often works well on lots of hardware, but getting specific hardware to work can be really painful, as with other distros.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 28, 2012 16:09 UTC (Sat) by tjc (subscriber, #137)
[Link]
I'm not using nvidia or amd drivers, and I don't know why you assumed that I was.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 28, 2012 17:40 UTC (Sat) by dlang (✭ supporter ✭, #313)
[Link]
it's a fair assumption, except for the one rough patch the Intel drivers have tended to be rock solid while the proprietary AMD and Nvidia drivers have caused problems routinely, so when someone complains of video problems, the odds are really good that it's because of this.
Unfortunantly a couple of years ago (around the time of the last LTS release), the Intel drivers got really messed up for about 6 months and broke on a lot of people's systems.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 30, 2012 16:38 UTC (Mon) by nye (guest, #51576)
[Link]
>it's a fair assumption, except for the one rough patch the Intel drivers have tended to be rock solid while the proprietary AMD and Nvidia drivers have caused problems routinely
The nvidia blob has in my experience been the only solid, dependable video driver for Linux.
Okay, to be fair to the Intel driver, it is now basically functional and you can expect that your system won't crash these days, but it's hardly bug-free - for example, I've not yet met a system using Intel graphics which doesn't need the screen resolution to be set manually in xorg.conf.
If you actually look at all the cases where people are claiming problems with the nvidia blob, the vast majority don't stand up to scrutiny - typically a developer notices that the reporter is using the nvidia blob, then jumps straight to the assumption that it must be the cause of all problems because it doesn't have the magic OSS sauce.
Basically, it's just politics.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 30, 2012 17:44 UTC (Mon) by mathstuf (subscriber, #69389)
[Link]
> The nvidia blob has in my experience been the only solid, dependable video driver for Linux.
I've had lots of issues with the blob. Mainly when dealing with multiple monitors or WM compositing. I've not used it since around Fedora 10 or so on a day-to-day machine (I have it on a work laptop in an alternate install for OpenCL testing, but that hasn't been booted in months).
> I've not yet met a system using Intel graphics which doesn't need the screen resolution to be set manually in xorg.conf.
I have a desktop (19" 1440x900 monitor) and netbook (9" 1024x600) with Intel graphics that have never needed an xorg.conf for anything.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 10:57 UTC (Tue) by nye (guest, #51576)
[Link]
>> I've not yet met a system using Intel graphics which doesn't need the screen resolution to be set manually in xorg.conf.
> I have a desktop (19" 1440x900 monitor) and netbook (9" 1024x600) with Intel graphics that have never needed an xorg.conf for anything.
Interesting - does that also hold for GDM/KDM/WhateverDM, or do you not use one? Did it need any special kind of configuration?
In fact I can use KDE's system settings to configure the right resolution each time I log in, rather than writing an xorg.conf from scratch, but that doesn't help for the login manager so I wonder if there might be a way to configure that.
This was all so much easier in the days when all you had to do was uncomment the right line in the provided XF86Config.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 18:39 UTC (Tue) by dlang (✭ supporter ✭, #313)
[Link]
for at least some versions of KDE there is a bug that causes it to loose it's monitor settings each boot. This is not a kernel/driver problem, strictly a KDE problem
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 11:28 UTC (Wed) by nye (guest, #51576)
[Link]
The problem I'm talking about is not specific to KDE. KDM simply uses the auto-detected resolution which is always wrong if I don't have an xorg.conf.
I can live with it since I don't re-log very often and I haven't motivated myself to write the xorg.conf yet. On the one system I have that's running Gnome though I couldn't figure out how to set the resolution (it comes with what seems to be a preconfigured list of useless options) so there I did have to resort to writing an xorg.conf.
Note that at least one machine detected the resolution correctly on 2.6.32, but no kernels I've tried before or since.
I haven't tried any kernel versions that are particularly recent since the rate of regressions in Linux has conditioned me to upgrade only when it's completely unavoidable.
(And as for monitor *hotplugging* in KDE...that's a pretty guaranteed way to render this laptop non-responsive and require a power cycle)
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 13:51 UTC (Wed) by nye (guest, #51576)
[Link]
>Note that at least one machine detected the resolution correctly on 2.6.32, but no kernels I've tried before or since.
Actually now that I think about it, I believe it was 2.6.26 which worked. Before that was probably the era of massive breakage, and from there I skipped to 2.6.29 which was apparently when KMS was introduced for Intel, which seems a likely candidate for the breakage.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 16:09 UTC (Wed) by mathstuf (subscriber, #69389)
[Link]
Sounds like the modelines aren't being detected properly and you may be getting vesa's standard list of resolutions. What model is it? Mine are an X4500 HD and some mobile chip I can't remember off the top of my head (it's a System76 machine).
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 10, 2012 13:15 UTC (Thu) by nye (guest, #51576)
[Link]
>What model is it?
The two I currently have access to are an Atom integrated system with an 'N10 Family Integrated Graphics Controller', and a more standard laptop with a 'Mobile GM965/GL960 Integrated Graphics Controller'.
Those don't really mean a great deal to me, to be honest. I just know that they're both very low-performance and seemingly not brilliantly supported.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 19:05 UTC (Tue) by mathstuf (subscriber, #69389)
[Link]
These days I use "exec startx" from a TTY, but when I did use a login manager (only KDM AFAIR), I don't remember any issues (KDE 4.2.x to KDE 4.4.x before I stopped using KDE on the Intel machine). An older netbook was the same way (since donated). My current netbook has never run KDM.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 19:29 UTC (Tue) by dlang (✭ supporter ✭, #313)
[Link]
I started running into the issue about a year ago when I switched to a multi-monitor setup and discovered that every boot I had to reconfigure the monitors. I did some searching and discovered that it was a known KDE problem with no documented fix.
It doesn't require you to use KDM, it's a problem in the KDE screen management after KDE starts.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 19:56 UTC (Tue) by mathstuf (subscriber, #69389)
[Link]
I've noticed that KDE's RandR configuration tool is…oddly behaved at times (even recently when helping a coworker set up 3 monitors). The command line is much better for RandR configuration (I've found no GUI that is faster to get what I want or more convenient) and I have a script in ~/.config/xinit which gets sourced to set up rotation and positioning upon login (no modeline commands though, just relative placement).
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 1, 2012 16:19 UTC (Tue) by juliank (subscriber, #45896)
[Link]
> I've not yet met a system using Intel graphics
> which doesn't need the screen resolution to be
> set manually in xorg.conf.
On all 4 laptops that I own or administrate, none needs an xorg.conf; and all of them use intel graphics (and 3 different generations of intel graphics).
On boot, the kernel detects the correct screen resolution for the panels and automatically sets the correct mode. When plugging in a screen, the screen is detected, and the correct mode is set automatically.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 11:29 UTC (Wed) by nye (guest, #51576)
[Link]
>On boot, the kernel detects the correct screen resolution for the panels and automatically sets the correct mode
Okay, you're making me feel motivated to take the risk of trying a new kernel version - what version are you using to get that?
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 13:00 UTC (Wed) by juliank (subscriber, #45896)
[Link]
Anything since 2.6.32 (in Debian squeeze) works fine here. I should say I never needed any xorg.conf with the intel driver, not even before KMS. Everything just worked (well, not on my Core i5 System, that one crashed during the first 6 months I had it, as the driver was unstable back then [one or two years ago]).
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted May 2, 2012 13:53 UTC (Wed) by nye (guest, #51576)
[Link]
>Anything since 2.6.32 (in Debian squeeze) works fine here
So the same versions that get it wrong on all my machines then :(. Oh well.
Ubuntu 12.04 LTS "Precise Pangolin" released
Posted Apr 30, 2012 14:21 UTC (Mon) by muwlgr (guest, #35359)
[Link]
squid3 does not start properly on bootup due to incorrect interaction between upstart, ifupdown and resolvconf
lp:978356