When will bug fixes be available for updating

As one of the bugs seems to be a "single-timer"... and nobody (of the Ubuntu-developers) seems to care about... nobody knows.

But:
Did you tryed to create a new clean User and look if it works in that account?
(If not... give it a try please.)

Greetings

The glib bug is fixed upstream and already available on other distributions. I have never seen a gnome bug actually fixed.

The glib bug involved getting the wrong display value, and is user independent.

Ubuntu is quite strict... love it or hate it.
Unless it is a secutity-bug... maybe you will have to wait until the next Versions of Ubuntu. (Karmic or even later)

I'm following a bug that is in Ubuntu for years and fixed by upstream (The real upstram, not Debian) also years ago.

Sometimes it's pain.

Great

A major error severely limiting the usefulness of a Unbuntu desktop system not fixed because of strict "security only" fixes allowed policy.

What about a strict no release policy for distributions that have major errors?

It's just another point of view...

If there is a let's call error or glitch in a Distri... and you know about that one... it's some kind of OK, because you can rely on that bug. You might have heard the saying: "It's not a bug, it's a feature!"
In enterprise-editions mainly for servers this is really OK!!! Beleave me.
You know about the glitch... you know how to handle it. Imagine if you did this "workaround" and then comes an update and the workaround is not working anymore... instead you have a broken server inside the Internet.

But I indeed don't see the benefits for a desktop-mainstream-distro like Ubuntu. Those strict "feature-freezes" are really annoying. No... not for the 18-month-support-versions.

They could split this for the LTS-ones maybe? Amight be a thing for brainstorm...

Greetings

When you have a bug/feature that severely limits the usefulness of a desktop⋯and here I specifically mean the failure of major operations on a second monitor⋯that was known before release, not mentioned in the release notes, not fixed as a part of the update process, did not exist in the prior version, and you do not offer a reasonable work around―then you have broken the promise of continued improvement to the user.

It is my understanding that this is the concern and domain of the Ubuntu Technical Board. http://www.ubuntu.com/community/processes/techboard

With regard to this see: https://wiki.edubuntu.org/TechnicalBoard/JauntyAssessment

Now I have been in the IT business since John F. Kennedy was president. I have seen many enterprises, some as magnificent as Canonical/Ubuntu (said without sarcasm), rise and fall. Most descents involve broken promises.

After following and using Linux since Wm J Clinton was president, I adopted Ubuntu as the first desktop I would recommend to my many non-technical friends and acquaintances. While the vast majority of these users would not experience the problems with a second monitor―I consider it a harbinger of thing to come. To wit: Ubuntu is willing to break a promise of continued improvement that only affect a few in order to sustain our endeavor. Now while Microsoft can survive with this approach, I suspect Canonical/Ubuntu may not.

So let me restate my question. I have a problem that severely restricts the usefulness of my system not present in the prior release with a known solution and will the Ubuntu community help me solve it even though it affects a relatively small number of users?

You are peaching to the converted/choir...
I'm totally and absolutely with you, as I see Ubuntu mainly in the Desktop-section. (And btw. I'm IT-Professional too.)

Because of this I mainly distribute Linux-Boxes with Ubuntu-LTS desktops... those tend to be a bit better tested (from the dot1-version to say... as Hardy 8.04.1).

But for you:
https://launchpad.net/~intuitivenipple/+archive/ppa?field.name_filter=&field.status_filter=published&field.series_filter=jaunty

There is a patched version of glib2 for your problem. :-)
You know how to handle with PPAs?

Let me see…

Are you saying I should go to the page https://launchpad.net/~intuitivenipple/+archive/ppa?field.name_filter=&field.status_filter=published&field.series_filter=jaunty

Add the system sources and authenication listed there for PPA for TJ per: https://launchpad.net/+help/soyuz/ppa-sources-list.html

then update my system with "glib2.0 - 2.20.1-0ubuntu3~tj~ppa1j"

I have no problem if there is a reasonable chance of success and the update can backed out given problems occur.

Exactly!
Here is a little changelog to this glib2-version:

  * Use correct DISPLAY when using multiple screens (LP: #290935)

From: http://launchpadlibrarian.net/28166037/glib2.0_2.20.1-0ubuntu3~tj~ppa1j_source.changes

Might be the right one for you and some others.

This is what I did to fix the dual monitor problem, thanks to the invaluable assistance of midnightflash!

Opened:
https://launchpad.net/~intuitivenipple/+archive/ppa?field.name_filter=&field.status_filter=published&field.series_filter=jaunty

Opened:
https://launchpad.net/+help/soyuz/ppa-sources-list.html

Followed the instructions for PPA and authenication on ppa-sources-list.html

Opened update manager.

Selected only
 libglib2.0-0
 libglib2.0-0-dbg

Installed updates

Restarted

Verified installation using Sunaptic Package Manager File>History

Commit Log for Mon Jul 20 09:27:41 2009
 Upgraded the following packages:
  libglib2.0-0 (2.20.1-0ubuntu2) to 2.20.1-0ubuntu3~tj~ppa1j
  libglib2.0-0-dbg (2.20.1-0ubuntu2) to 2.20.1-0ubuntu3~tj~ppa1j

Tested menu items on screen 1 and they opened properly on screen 1 rather than screen 0. Note: some of the icon on the panel failed so I removed and replaced those.

Opened Software sources (see ppa-sources-list.html above) and unchecked
 http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu
 http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu
(I did this to avoid unintentional updates from this repository)

Great! I'm glad my little help could be of worth for you.

Greetings

ps: It's the right and safe way to disable such a PPA afterwards. Very true...

Well I tried all this (keepitsimpleengr instructions based upon midnightflash's help), but somehow I had no luck. The Synaptic package Manager, F-Spot Photo manager, KeePass, Skype, Gimp, Filezilla, and most other programs - open in my laptop screen and my mouse pointer in my secondary LCD screen (which is where it should be as well).
Thank God the terminal, Firefox and Gedit (still) open in my secondary LCD screen where my mouse is at.
I am getting pretty desperate here. Maybe I should abandon Twin View in Ubuntu all together until the next Ubuntu version is available in October. Keepitsimpleengr did mention that I might need to change some icons on the panel. I just don't know how...

!st make sure you actually have glin2 patched installed.

Open Synaptic Package manager and search for: "libglib2.0-0" in name (not using quick search).

If show libglib2.0-0 Current version 2.20.1-0ubuntu3~tj~ppa1j
and libglib2.0-0-dbg Current version 2.20.1-0ubuntu3~tj~ppa1j
then you have the patched version. If you do not have the patched version, then retry and get it.

The comment about the icons refers to that some icons created using add this launcher to panel/desktop (right mouse button when on menu item) before the the patched glib2 will still open in screen 0, Just delete them and recreate them after the patched glib is installed.

Yes I have them and after a retry all seems to be working well. Thanks for your help Keepitsimpleengr.

thanks for your instructions!
finally works, sighhhh.
I never expected this to happen, always had good experience with Ubuntu.
I also works as an IT Engineer and recommended Ubuntu many times as a complete and pretty much flawless desktop.
Such a shame this bug is in, and I really do not understand it is not being fixed?

The bug I opened also shows code with a fix, but no package to install.
Well, it works now, wish I found this before.
I will link on the other places to this page, so more people will find it.
Thanks a bunch!

I believe I'm doing something wrong here. I have the same dual monitor problem, but when I get to the step involving 'Telling Ubuntu How to Authenticate the PPA' on this page: https://launchpad.net/+help/soyuz/ppa-sources-list.html , I recieve the following error:

W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7D2C7A23BF810CD5
W: You may want to run apt-get update to correct these problems

And as it turns out, running apt-get update turns up the same error. Any ideas?

Hi NotKeith…

These two commands should place repository information for the patch in Software Sources. This tells the package manager where to find the patch update on the internet.…

 deb http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu jaunty main
 deb-src http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu jaunty main

After running these successfully, you should have the following two lines in
MENU: System / Administration / Software Sources / WINDOW-TAB: Third-Party Software LIST (with check boxes).…

 http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu
 http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu (Soource Code)

These two should be checked to allow the patch to be applied, and unchecked after the patch is applied.

To allow the authentication of the above repository, run (shown is what I ran). Authentication tells the package manager that the repository source is the one you want (as opposed to some nefarious stuff).…

 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 29047922

The identifier "29047922" here is from "Signing key: 1024R/29047922" on https://launchpad.net/~intuitivenipple/+archive/ppa?field.name_filter=&field.status_filter=published&field.series_filter=jaunty

After this is successfully run the following should appear (from mine) in MENU: System / Administration / Software Sources / WINDOW-TAB: Authentication LIST: Trusted Software Providers

 29047922 2009-01-19
 Launchpad PPA for TJ

Instead of "Telling Ubuntu how to authenticate the PPA / Step 3 sudo apt-get update", you should be able to run update manager and get the patch update.

If these two do not match as shown, you will get an error when updating. I checked today, and the authentication is still valid for this repository.

Hope this helps⋯Good luck

Well I appreciate the quick reply, but unfortunately I'm kind of at a loss here.

29047922 2009-01-19
Launchpad PPA for TJ

shows up in my list of Trusted Software Providers, and I do get a number of new options under both important security and recommended updates, none of which are libglib-2.0.0! Also, if I try to reload from either update manager or synaptic, I get the same error message I received when I tried the sudo apt-get update command. Can you think of any other system information I might need to post which might be helpful?

Hi NotKeith…

Perplexing, yes.

Please check http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu/dists/ using a browser
and see if you distribution is there as a subdirectory, I presume "jaunty".

Open your distribution index subdirectory, then open "main" subdirectory. Find your processor type, mine is "amd64", I presume yours is "i386". Open this subdirectory, then open the text file "Packages".

In this text file look for "Package: libglib2.0-0" and package "Package: libglib2.0-0-dbg". Make a note of the "Filename: ·····" for both Packages. These filenames will include a path, "Filename: pool/main/g/glib2.0/libglib2.0-0_2.20.1-0ubuntu3~tj~ppa1j_amd64.deb" for mine where "pool/main/g/glib2.0/" is the path.

In another browser window open http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu/

Check to see if the files in the "Filename: ·····" are there, you will need to follow the path to get to the proper subdirectory.

If these files do not exist, then there is not a patch for your distribution and processor. This solution will not work for you.

If these files do exist, then there is a problem with updating packages. I would suggest a new question along the lines of "Updating from a 3rd party repository fails…". Be sure to include pertinent information such as distribution, processor, &c. It might also be helpful to include a log from the terminal showing an attempt to update the package. Also a link to this question might be helpful.

Good luck, hope this helps.

Hey NotKeith…

I presume you are using Gnome 2.26.1. Please run Synaptic Package Manager and search by name for "libglib2.0-0" and let us know the what the "Installed versions" and "Latest version" are.

This does not fix the problem from my installation of Jaunty.

And I *definitely* followed ALL the directions correctly.

I can verify that version 2.20.1-0ubuntu3~tj~ppa1j is installed for libglib2.0-0 and libglib2.0-0-dbg.

I rebooted several times. I creating new launchers. Still everything launches on the first screen (except for apps like Firefox that always worked correctly).

Even the volume icon in the taskbar launches only on the first screen! Sheesh!

However, the only improvement I do see is that, when I right-click, the context menu opens in the proper screen (whereas in the past that TOO would open on the first screen.) But that's not much of a concession.

I'm seriously considering "downgrading" back to Hardy Heron, where things worked correctly. "Upgrading" to Jaunty was the worst mistake I've ever made. It's been months of headaches that make me question whether to use Ubuntu (and even Linux) anymore.

Dimitri…

Bummer... The only thing I could suggest is a new question in answers along the lines of "jaunty dual monitor problem not fixed by patch to libglib2". Be sure to include pertinent information such as distribution, processor, &c.

"Stoneface" seems to have a similar problem, thread at http://ubuntuforums.org/showthread.php?t=1218980&page=3

And if you haven't, check out http://www.ublug.org/ubuntu/twinview/twinview-howto-breezy.html and/or http://www.ublug.org/howtos/ubuntu/twinview/twinview-howto-laptop.html

My system is not a laptop, and I have had dual monitors, long before jaunty. I recall some difficulty in getting them set up properly, so when jaunty broke it, the patch fixed it nicely. Now I use compiz and emerald city with good results (although "update manager" crashes emerald city sometimes, it's easy to restart using Compiz Fusion Icon.)

There is a copy of my xorg.conf at https://answers.launchpad.net/ubuntu/+source/xserver-xorg-driver-nv/+question/82529 if that will help.

I to found jaunty to be a VERY PROBLEMATIC distribution, and they are changing nvidia drivers for karmic and I am very nervous about it, fearing months of not working monitors again. Testing was obviously inadequate for jaunty.

Please post here you results, I am very interested in this issue.

I was having the same problem as keepitsimpleengr (windows opening on Screen0 being launched from menu on Screen1) and replacing libglib2.0-0 libglib2.0-0-dbg (just installed the .deb's instead of messing with sources.list) fixed the problem, but only with Compiz turned off. If I enable it it, the only problem is I get a big black bar to right of Screen1 (which probable takes up 25% of the screen, basically unusable for me). I wonder how this part can be fixed when Compiz is running? Also,I'm thinking of using KDE desktop to see if this problem wouldn't exist at all.

My compiz problems disappeared whin I applied the ppa patch.

See https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/392850

It actually worked normal besides the vertical black bar running on the far right on screen1. Screen1 is a widescreen and screen0 is not, with different resolutions. It almost like it wasn't using the whole screen and the resolutions and configurations were fine to my knowledge. The mouse pointer could go over the black bar but windows and applications could not. I tried just about every solution posted. Reading a thread at ubuntuforums about the black bar, I eventually downgraded to Nvidia driver 173 from 180 and there is no vertical black bar anymore on screen1. Not sure what disadvantage there is to downgrading to 173 driver and I'm curious what the problem was with using 180, I will have test further when I have time to make sure it wasn't just a configuration in compiz. Thanks for all the tips this has helped me alot!

My screen resolutions are 2560x1600 & 1440x900. I use 180.44 without problems.

Did you try "sudo /usr/bin/nvidia-settings" from a terminal? Without running it as a super-user, the xorg.conf cannot be saved. Other setting are stored in "~/.nvidia-settings-rc". Settings regarding basic screen layout are stored in the "/etc/X11/xorg.conf" file

X Server Display Configuration should not have xinerama enabled.

Here are the video settings from my xorg.conf file. I have nvidia GTX260x2 in SLI. Both monitors are connected to one of the cards. Careful examination of the xorg.conf file can reveal a great deal.

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection
…
Section "Module"
    Load "dbe"
    Load "extmod"
    Load "type1"
    Load "freetype"
    Load "glx"
EndSection
Section "ServerFlags"
    Option "Xinerama" "0"
EndSection
…
Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "HP LP3065"
    HorizSync 49.3 - 98.5
    VertRefresh 60.0
    Option "DPMS"
EndSection
Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
EndSection
Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 260"
    BusID "PCI:3:0:0"
    Screen 0
EndSection
Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 260"
    BusID "PCI:3:0:0"
    Screen 1
EndSection
Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "DFP-1: nvidia-auto-select +0+0"
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection
Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "DFP-0: nvidia-auto-select +0+0"
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection

Additional note:

I use Compiz Fusion with Emerald. Occasionally the window manager will cease operation (No frames on windows). I installed the Compiz Fusion Icon. It allows me to easily restart the proper window manager.

So far this only happens occasionally when I use "Update Manager".

Also I have found Compiz settting manager works best when open on the screen for which changes are to be made.

Good luck.

I confirm that the update in my case it worked. I do not use Compiz
Thank you for your contributions.

I find that after the update occurs the following behavior:

Applications like Chromium and Opera use "gnome-open" to open the downloaded files. Failure occurs and the files are not opened by the system.

If I run Chromium or Opera on a terminal I get the following error if I try to open a pdf file:
 "(acroread:5958): Gtk-WARNING **: " cannot open display:".

It is the same error as if I run in a terminal: "gnome-open file.pdf" .

Could be confirmed if the same applies to you.

This is just information about the buggy libglib2 package, and its upgrade and patch.

The package libglib2.0-0 version 2.20.1-0ubuntu2(jaunty) originally supplied with 9.04 jaunty has been upgraded to libglib2.0-0 version 2.20.1-0ubuntu2.1(jaunty-security).

This upgrade DOES NOT FIX the bug fixed by libglib2.0-0 version 2.20.1-0ubuntu2~tj~ppa1, for which the instructions are given above, and which patches the dual monitor bug.

Update manager will not replace the patched version with the upgrade.

A note to let you know I've just repackaged my previous Jaunty libglibc package to use yakovlev's patch since it seems to perform better than my original upstream-backport patch (which came from grossly refactored code). This package is based on the latest security/update package from Jaunty.

In particular, yakolev's patch doesn't cause the launching of external applications to fail (e.g. double-click of a .deb inside a .tar.gz in file-roller, or a downloaded file on Chromium-browser) as the previous patch did.

See my comment in the bug report:

https://bugs.launchpad.net/glib/+bug/346964/comments/59

¡Thanks! to TJ for both doing the work to produce the patch and letting us know in this question.

If you have applied the patch as I described above, you can use Synaptic Package Manager to remove the previous patch and apply TJ's new, improved one.

Step by step the way I did it…

Open: Menu>"System">"Administration">"Synaptic Package Manager"

{Here enable the repositories so Synaptic can see the packages}

Menu "Settings">"Repositories"

Tab> "Third-Party Software"

Check (check boxes on line):
"http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu main (Source code)" &
"http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu main"

Close, Close Message, Press "Reload" button

{Here find the packages and "mark" the necessary actions}

Search for (by Name); "libglib2.0"

Mark for removal Package: "libglib2.0-0-dbg" with Installed Version: "2.20.1-0ubuntu3~tj~ppalj" with left mouse button & drop down menu at the check-box.

Select (highlight) the line Package: "libglib2.0-0" with Installed Version: "2.20.1-0ubuntu3~tj~ppalj

{Force is not on the left muse button drop down menu, so use the Synaptic menu}

Menu "Package">"Force Version…"
{Since the older patch has a higher version number, this will 'force' the desired, newer patch}
  Force version[Drop down Selection List]: "2.20.1-0ubuntu2.2~tj~ppalj"

Mark the following for installation:
libglib2.0-data, libglib2.0-dev, libglib2.0-doc
  with left mouse button & drop down menu at the check-box.

Select "Apply" button from tool bar, expand the text box lines and check to see that the following are present
To be DOWNGRADED: libglib2.0
To be completely removed: libglib2.0.0-dbg
To be installed: libglib2.0-data libglib2.0-dev libglib2.0-doc

If so, select "Apply" button
If not, cancel, close "Synaptic Package Manager", accept clear changes and start over.

After the installation is finished, go to Synaptic's Menu "File">"History"

Under today's date you should see the following:
Commit Log for Sat … … …:…:… …

Downgraded the following packages:
libglib2.0-0

Removed the following packages:
libglib2.0-0-dbg

Installed the following packages:
libglib2.0-data (2.20.1-0ubuntu2.2~tj~ppa1j)
libglib2.0-dev (2.20.1-0ubuntu2.2~tj~ppa1j)
libglib2.0-doc (2.20.1-0ubuntu2.2~tj~ppa1j)

{Now turn off the repositories to avoid untoward changes}

Synaptic's Menu "Settings">"Repositories"

Tab> "Third-Party Software"

Uncheck:
"http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu main (Source code)" &
"http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu main"

Close, Close Message, Press "Reload" button

You are done.

Thanks, TJ and others; it worked for me in Jaunty. Now if I can only find the PPA to stop the freezing. :-)

I lost my preferred dual monitor settings (xinerama-xserver) yesterday in an upgrade Ubuntu 8.10 to 9.04. I was directed to your topic from the forums -lost the thread in all the searching. With your excellent help I can now move the from the CRT monitor to the laptop screen. but I can only move the cursor to the CRT with a USB mouse - then I can use the touchpad on that display and then move the cursor back to the laptop.

I did discover if I set the CRT to 1400x1024 it leaves a bit of overlap with the laptop and I can squeak the cursor back and forth without resorting the the USB mouse.

I run with no compriz; tried both restricted nvidia drivers 180 and 173; replaced xorg.conf with previously working backup...googled - & searched forum - yours appears to me the best hope out there, I see no way to attach a copy of my xorg.conf but will if you wish

Hopefully you will be able to point me in the right direction to get this straightened out.
In appreciation for getting me this far.

I lost my preferred dual monitor settings (xinerama-xserver) yesterday in an upgrade Ubuntu 8.10 to 9.04. I was directed to your topic from the forums -lost the thread in all the searching. With your excellent help I can now move the from the CRT monitor to the laptop screen. but I can only move the cursor to the CRT with a USB mouse - then I can use the touchpad on that display and then move the cursor back to the laptop.

I did discover if I set the CRT to 1400x1024 it leaves a bit of overlap with the laptop and I can squeak the cursor back and forth without resorting the the USB mouse.

I run with no compriz; tried both restricted nvidia drivers 180 and 173; replaced xorg.conf with previously working backup...googled - & searched forum - yours appears to me the best hope out there, I see no way to attach a copy of my xorg.conf but will if you wish

Hopefully you will be able to point me in the right direction to get this straightened out.
In appreciation for getting me this far.

sorry for double post, this just isn't my day

Suzanne...

Your absolute best bet is to ask a new question, and provide as much information about your system as possible.

Since there is a lot of activity regarding the 9.10 release currently, there may be some sluggishness in response.

If you post back here with your new question number, I will see what I can do. Also there are several very knowledgeable subscribers to this question who may also be helpful, quite possibly more than me.

Thanks, TJ and others; it worked for me in Jaunty as well.