Re: final gtk+maverick battles

2014-02-17 Thread Bric

On 02/16/2014 10:24 PM, Michael Torrie wrote:

On 02/16/2014 04:30 AM, Bric wrote:

Nonetheless, I run ./configure in gtk+ git, and I am still getting unmet
dependencies:

configure: error: Package requirements (glib-2.0 = 2.39.5atk =
2.7.5pango = 1.32.4cairo = 1.12.0 cairo-gobject = 1.12.0
gdk-pixbuf-2.0 = 2.27.1) were not met:

Requested 'glib-2.0 = 2.39.5' but version of GLib is 2.32.4
Requested 'atk = 2.7.5' but version of Atk is 2.4.0
Requested 'pango = 1.32.4' but version of Pango is 1.30.0
Requested 'gdk-pixbuf-2.0 = 2.27.1' but version of GdkPixbuf is 2.26.1



So, this is no longer an ancient system. What do I do?  (Aside from
trashing this new one with local builds, as I did the old one?)

Never upgrade system versions of glib and gtk+ in place unless you
really know what you're doing.  Instead if you need newer versions,
compile them to their own prefix.  You can set the PKG_CONFIG_PATH
variable to point to that prefix and ./configure will see them.

Also you can use jhbuild (google for it) to build the latest versions of
gtk+ to its own prefix (say /opt/gtk3).


Thank you.


If you dislike Unity, you can install the mate-desktop, which is a
continuation of the old gnome2 desktop that you are used to.


I do dislike Unity.  But I somehow managed to pull gnome back into my 
new install, so currently, i am using gnome (you are prompted to choose 
among several options, on boot)


To D. Marceau:

I'm going to take a chance and not back up everything.  I don't have 
space to back up all my stuff right now.  One would think that, after 
years of developing system installs, Ubuntu won't do me in (outside of 
my clicking erase everything... during the install because I'm going 
on two hours of sleep or something) (Word of caution to others:  the 
installer wipes out stuff in /usr and /etc, so, for example, I lost a 
painstakingly developed xkb configuration file ... painful to no end...)


I think I have to switch a couple of settings in update-manager, no?  
Like, broaden the upgrade option to all systems, rather just to 
long-term versions. Will be rebooting and re-probing shortly.


I made the mistake the first time around of NOT selecting download 
packages... during the install. (I had to upgrade from the CD). I am 
assuming that would have made the installer better match whatever I 
already had, with remote repositories, rather than simply getting rid of 
packages it couldn't match with the CD installer. (It's a pain having to 
reconstruct everything it wiped out!)


To A. Cottrell:

You are probably right; I should have tried gtk+ 3.0.12 or some such.  I 
wonder if that would have worked with the old system.  And, of course, 
you are right about not messing with glib  - i had a vague memory of 
installing gtk+ on a fedora, years ago, and the memory didn't involve 
system trashing, or any risk thereof.  So... that's what you get when 
you rely on old, vague memories - the world of linux libraries has been 
moving on rapidly :-))





___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: How to locate the 'Gtk-WARNING' line number

2014-02-17 Thread Marco Scannadinari
On Mon, 2014-02-17 at 16:44 +0800, Wiky wrote:
  Hi,all. I'm currently writing a program based Gtk+-3.0.
 When it runs, I get '(a.out:10874): Gtk-WARNING **: Failed to ...' in the 
 terminal.
 I know the problem is about GtkLabel, but I really don't know which GtkLabel.
 Is there a way to locate the line numer that give the warning?
 
 Sorry for my english
 ___
 gtk-app-devel-list mailing list
 gtk-app-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

If your UI is hand-coded, and in main() (not using GtkApplication), then
I suppose you can run it through gdb and step through each line to see
where it prints the error. Be sure to compile with -Og -g and without
optimisations though
-- 
Marco Scannadinari m...@scannadinari.co.uk

___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Fwd: Re: How to locate the 'Gtk-WARNING' line number

2014-02-17 Thread Sandro Mani


On 17.02.2014 10:36, Marco Scannadinari wrote:

On Mon, 2014-02-17 at 16:44 +0800, Wiky wrote:

  Hi,all. I'm currently writing a program based Gtk+-3.0.
When it runs, I get '(a.out:10874): Gtk-WARNING **: Failed to ...' in the 
terminal.
I know the problem is about GtkLabel, but I really don't know which GtkLabel.
Is there a way to locate the line numer that give the warning?

Sorry for my english
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

If your UI is hand-coded, and in main() (not using GtkApplication), then
I suppose you can run it through gdb and step through each line to see
where it prints the error. Be sure to compile with -Og -g and without
optimisations though

I think just setting a break-point on g_log and then asking for a
backtrace when you hit the breakpoint should also work and is possibly
quicker.



___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: How to locate the 'Gtk-WARNING' line number

2014-02-17 Thread David Nečas
On Mon, Feb 17, 2014 at 04:44:53PM +0800, Wiky wrote:
  Hi,all. I'm currently writing a program based Gtk+-3.0.
 When it runs, I get '(a.out:10874): Gtk-WARNING **: Failed to ...' in the 
 terminal.
 I know the problem is about GtkLabel, but I really don't know which GtkLabel.
 Is there a way to locate the line numer that give the warning?

Run it with G_DEBUG=fatal-warnings, let it dump core and look at the
stack trace.

Yeti

___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: final gtk+maverick battles

2014-02-17 Thread Bric

On 02/17/2014 04:30 AM, Bric wrote:

On 02/16/2014 10:24 PM, Michael Torrie wrote:

On 02/16/2014 04:30 AM, Bric wrote:
Nonetheless, I run ./configure in gtk+ git, and I am still getting 
unmet

dependencies:

configure: error: Package requirements (glib-2.0 = 2.39.5atk =
2.7.5pango = 1.32.4cairo = 1.12.0 cairo-gobject = 1.12.0
gdk-pixbuf-2.0 = 2.27.1) were not met:

Requested 'glib-2.0 = 2.39.5' but version of GLib is 2.32.4
Requested 'atk = 2.7.5' but version of Atk is 2.4.0
Requested 'pango = 1.32.4' but version of Pango is 1.30.0
Requested 'gdk-pixbuf-2.0 = 2.27.1' but version of GdkPixbuf is 2.26.1



So, this is no longer an ancient system. What do I do?  (Aside from
trashing this new one with local builds, as I did the old one?)

Never upgrade system versions of glib and gtk+ in place unless you
really know what you're doing.  Instead if you need newer versions,
compile them to their own prefix.  You can set the PKG_CONFIG_PATH
variable to point to that prefix and ./configure will see them.

Also you can use jhbuild (google for it) to build the latest versions of
gtk+ to its own prefix (say /opt/gtk3).


Thank you.


If you dislike Unity, you can install the mate-desktop, which is a
continuation of the old gnome2 desktop that you are used to.


I do dislike Unity.  But I somehow managed to pull gnome back into my 
new install, so currently, i am using gnome (you are prompted to 
choose among several options, on boot)


To D. Marceau:

I'm going to take a chance and not back up everything.  I don't have 
space to back up all my stuff right now.  One would think that, after 
years of developing system installs, Ubuntu won't do me in (outside of 
my clicking erase everything... during the install because I'm going 
on two hours of sleep or something) (Word of caution to others:  the 
installer wipes out stuff in /usr and /etc, so, for example, I lost a 
painstakingly developed xkb configuration file ... painful to no end...)


I think I have to switch a couple of settings in update-manager, no?  
Like, broaden the upgrade option to all systems, rather just to 
long-term versions. Will be rebooting and re-probing shortly.


I made the mistake the first time around of NOT selecting download 
packages... during the install. (I had to upgrade from the CD). I am 
assuming that would have made the installer better match whatever I 
already had, with remote repositories, rather than simply getting rid 
of packages it couldn't match with the CD installer. (It's a pain 
having to reconstruct everything it wiped out!)


To A. Cottrell:

You are probably right; I should have tried gtk+ 3.0.12 or some such.  
I wonder if that would have worked with the old system. And, of 
course, you are right about not messing with glib  - i had a vague 
memory of installing gtk+ on a fedora, years ago, and the memory 
didn't involve system trashing, or any risk thereof.  So... that's 
what you get when you rely on old, vague memories - the world of linux 
libraries has been moving on rapidly :-))


FWIF:  with this drive to keep upgrading, I just lost a critical hour of 
sleep (I start new class material today and needed to be rested) because 
I messed up the one and only thing you should NEVER mess up in your 
system:  network (wifi) connection (if you are out and about and have no 
way of plugging into ethernet):  With my eye on the 14.04 prize, I 
checked unsupported and pre-release packages in Update Manager, so 
it went ahead and installed newer linux-firmware, which screwed up my 
wifi connection.  Luckily, I was still near an ethernet port, and 
downgraded.  Again, just a caveat/caution for anyone who might try to 
draw from this experience.


___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: How to locate the 'Gtk-WARNING' line number

2014-02-17 Thread David Marceau
On 02/17/2014 03:44 AM, Wiky wrote:
  Hi,all. I'm currently writing a program based Gtk+-3.0.
 When it runs, I get '(a.out:10874): Gtk-WARNING **: Failed to ...' in the 
 terminal.
 I know the problem is about GtkLabel, but I really don't know which GtkLabel.
 Is there a way to locate the line numer that give the warning?
 
 Sorry for my english
 ___
 gtk-app-devel-list mailing list
 gtk-app-devel-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
 
Being that it's a warning, you may disregard it.

Still to this day I also get Gtk-WARNING from synaptic.
(synaptic:19289): Gtk-WARNING **: GtkNotebook 0x22f3510 is mapped but
visible child GtkLabel 0x2382cc0 is not mapped

emacs has a trick to remove this annoying warning:
http://code.ohloh.net/file?fid=oEG5UBbvy8a3udXaR1-LNWIHNrQcid=u98OF8Evg70s=gtk-WARNING#L14

If you are adamant about seeing the exact source for this warning, it's
in the gtk sources.  Install the gnome-dbg and anything gtk -dbg.  That
will help to point to source files and line numbers.

Cheers,
David Marceau



___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: final gtk+maverick battles

2014-02-17 Thread Chris Angelico
On Mon, Feb 17, 2014 at 11:05 PM, Bric b...@flight.us wrote:
 FWIF:  with this drive to keep upgrading, I just lost a critical hour of
 sleep (I start new class material today and needed to be rested) because I
 messed up the one and only thing you should NEVER mess up in your system:
 network (wifi) connection (if you are out and about and have no way of
 plugging into ethernet):  With my eye on the 14.04 prize, I checked
 unsupported and pre-release packages in Update Manager, so it went ahead
 and installed newer linux-firmware, which screwed up my wifi connection.
 Luckily, I was still near an ethernet port, and downgraded.  Again, just a
 caveat/caution for anyone who might try to draw from this experience.

Hey, it's a lot easier than back when I first started playing with
networking, in the 1990s. Granted, it was normal then to install off a
CD, but on the flip side, it was normal to need to get specific
drivers for your actual card. We got to know a few reliable cards
(Realtek network cards, ET6000 video cards, and such) that would
always work with our beloved OS/2, and if anything went wrong, I'd go
to my stash and grab one. Otherwise, it was a matter of transfer by
floppy disk, or pulling out the LinkWiz cable and moving data through
the computers' parallel ports. (Or their serial ports, if we didn't
feel like unplugging the ol' noisy. So much slower that way, even
though LinkWiz would (ab)use quite a few of the pins for extra data.)

These days, the face-palm DOH! moment usually comes from ssh'ing to a
box and then ifconfigging the network interface down. Yeah, that one
gets annoying.

ChrisA
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list