Gnome 2.24 packaging

At what point is gnome 2.24 packaging?
Last edited by piccolotux (2008-10-02 13:19:43)

piccolotux wrote:At what point is gnome 2.24 packaging?
http://bbs.archlinux.org/viewtopic.php?id=55670

Similar Messages

  • Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database?  If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

    Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database?  If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

    While I agree with the direction of the suggestions with installing packages for X-windows, we do not have a blanket 'apply any package' recommendation.
    In particular we do not support altering the kernel (although we do have exceptions which we review on a case by case basis).
    Basically, if the you want to alter functionality that would not impact core functionality you are usually fine.
    A good guideling is : The more dependencies that there are between the package / rpm you are considering using the higher the potential impact on functionality - meaning higher chance for problems
    Note: We do use VNC including Real and Tiger regularly , but we have no hard recommendation on how you may want to use X-windows. I have never seen a limitation other than comments on bugs
    or incompatibility within the X-window product itself with certain kernel levels.
    Patching may overwrite some packages that you may install, however,  _depending on packages/rpms added_ there is also the possibility that you will break existing functionality to the point
    that patching itself will fail ( we have already seen a few cases of this in which case the proper mitigation is to remove / roll-back any alterations to the ODA before patching, and then adding the packages/rpms
    back after the patching is completed.
    From what you are discussing the impact should be low without conflicts, but please consider the above, and if you have specific packages which you consider potential problems
    please create an SR so that we can review packages / rpms on an individual basis.
    Once again: the main criteria for not supporting rpms is regarding the kernel itself
    Chuck

  • Problems installing gnome-extra meta package

    I have not been able to intstall the gnome-extra meta package.   I receive an error that the dasher package file size cannot be calculated and pacman crashes.  I've tried different mirrors with the same result.
    Any ideas?

    Yes, dasher is corrupted, It has been reported as a bug so it should be fixed soon.

  • Gnome packages shouldn't depend on archlinux-menus

    Yes, I know... A lot of people want their menus customized to fit their distro. But some don't, and they should be able to remove the custom menus items that vex them. I'm fine with archlinux-menus being in the 'gnome' group, but packages like gnome-menus and control-center should not depend on it!

    If you don't like the archlinux menu, just pacman -Rd the archlinux-menus package, it's gone from KDE and every XDG compliant menu system then also.
    Other option: rightclick panel -> edit menus -> uncheck the archlinux menu.

  • [SOLVED]problem with GNOME and wireless connection

    Hi!
    I'm new to Arch Linux, and have run into a few problems after installation.
    My computer is a HP Pavilion dv6000.
    I installed using "xf86-video-nouveau" driver, as i understand this is the best choice for "Nvidia Geforce Go 7400". Is it?
    I also installed the complete "gnome", "gnome-extra", "gdm", "gnome-tweak-tool" and "gnome-shell-extensions" packages, but when I boot into gdm login, it automatically starts in fallback mode (the one who has "applications" and "places" in the top panel instead of "activities". What am I doing wrong here?
    Btw, when I go to System settings - system info - graphics, there are three lines; "Driver", "Experience", "Forced Fallback Mode". "Driver" line only says driver, and is blank after. "Experience" line says "Fallback".  "Forced Fallback Mode" is set to OFF.
    Also, I cannot figure out how to get my wireless network set up correctly.
    When i open System Settings - Network, I get an error saying System network is not compatible with this version.
    Any help with this woill be greatly appreciated!
    $ iwconfig
    lo        no wireless extensions.
    wlan0     IEEE 802.11abg  ESSID:off/any 
              Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
              Retry  long limit:7   RTS thr:off   Fragment thr:off
              Power Management:on
    eth0      no wireless extensions.
    Last edited by pkuvaas (2012-01-18 21:57:46)

    pkuvaas wrote:
    Thanks!
    -dri driver worked. But if the NVIDIA driver works better, I should probably consider using that one.
    I tried to install the NVIDIA binary driver, but when i tried to run
    # chmod -X NVIDIA-Linux-x86-290.10.run
    # ./NVIDIA-Linux-x86-290.10.run
    I got a message telling me to close x first.
    How can I do this?
    Ho ho ho buddy, I see you're trying to install the nvidia driver from the website. Have another look here:
    https://wiki.archlinux.org/index.php/Nvidia#Installing
    the drivers are available through pacman Installing the driver through pacman will automatically take care of removing things that conflict and installing things you need to ge t the NVIDIA driver to work.
    NVIDIA _might_ be better, 3d support in nouveau is still somewhat experimental and nouveau doesn't have all the power management features yet. It'll be something to experiment with. Have a good read of the NVIDIA and NOUVEAU wiki articles
    pkuvaas wrote:
    As for the wireless issue, I googled around a bit and found that the driver I need is ilw3945.
    I added this to /etc/rc.conf:
    DAEMONS=(...ilw3945...)
    as it seems the drivers are included in udev.
    However, when i try to open System Settings -> Network, it says
    The system network services are not compatible with this version.
    So I'm getting a little restless to find out what I can do to get the wireless network configurated properly, and how I can do it.
    Any ideas?
    First I think you've fundamentally misunderstood something. Drivers for linux come in module form, not in DAEMON form. A DAEMON is an application that runs in the background (sound server, network service, etc etc).
    ilw3945 would have to be added to your MODULES section in /etc/rc.conf if that is the module you need.
    humor me and post the output of this command:
    $ lspci

  • [SOLVED]Gnome 3.10 Icons are broken

    I upgraded earlier to Gnome 3.10. Although I've had a lot of problems.. I'm working on them one at a time.
    Most of the default icons are not showing anymore. My Nautilus looks like this:
    Some of the applications icons do still exist.
    If I create a new user and log in, the icons are all fine. But I cannot figure out how to bring back icons on my own user account.
    I tried running the command on http://askubuntu.com/questions/56313/ho … e-defaults, which set my favourites and wallpaper back to default. Icons still aren't fixed.
    I tried running gtk-update-icon-cache on my icons folder. Tried running xdg-user-dirs-update. Tried sudo pacman -S $(pacman -Ssq gnome-icon-theme). Tried running /usr/bin/gdk-pixbuf-query-loaders --update-cache and tried reinstalling librsvg. None of these have helped.
    Thanks.
    Last edited by themusicalduck (2013-10-08 01:07:05)

    Not solved for me I'm afraid. I'm running Openbox + Tint2 setup, with quite a few Gnome applications. I use the Oxygen icon theme.
    Since the upgrade to the Gnome 3.10 packages, my GTK3 applications have missing icons which only reappear if I choose the GNOME icon theme using lxappearance, which modifies ~/.config/gtk-3.0/settings.ini. Here's my normal settings.ini:
    [Settings]
    gtk-theme-name=Clearlooks-Phenix
    gtk-icon-theme-name=oxygen
    gtk-font-name=Arimo 9
    gtk-cursor-theme-name=aero-drop
    gtk-cursor-theme-size=0
    gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
    gtk-toolbar-icon-size=GTK_ICON_SIZE_MENU
    gtk-button-images=1
    gtk-menu-images=1
    gtk-enable-event-sounds=1
    gtk-enable-input-feedback-sounds=1
    gtk-xft-antialias=1
    gtk-xft-hinting=1
    gtk-xft-hintstyle=hintfull
    gtk-xft-rgba=rgb
    When 'gtk-icon-theme-name=gnome' is used instead, the icons display in GTK3 applications.
    Any ideas please how I can get the Oxygen theme to play nicely with Gnome 3.10 applications?

  • [solved]Menu Text in Libreoffice gone (with gnome 3.4?)

    I see a really strange behavior with libreoffice from the testing repos. I can't see text in my menus anymore. It's like all text has a white overlay. If i turn on icons, it gets a bit better and I can see some letters. It's a bit hard to describe, so i attached an image.
    I tried to downgrade some packages (not all gnome 3.4 packages), but it didn't get better. When i try --debug i get:
    (soffice:3000): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    Any thoughts on this?
    Edit: I just installed enlightenment to see if it gets better, but same problem there. So probably not a gnome related problem.
    Last edited by steffinger (2012-04-12 14:47:52)

    Hi.
    Same problem here.
    Changing font antialiasing from grayscale to rgba makes the text appear for me.
    Just a tip till the problem gets fixed.
    EDIT:
    Just tried downgrading to Cairo-1.10.2-3. Works well with grayscale font antialias setting.
    Last edited by kryo (2012-04-13 03:51:48)

  • [solved] error: gnome-doc-utils = 0.3.2 not found during configuring

    When configuring libdbusmenu after downloading the PKGBUILD from AUR, I get the following error:
    [tharriso@localhost libdbusmenu]$ makepkg
    ==> Making package: libdbusmenu 12.10.2-1 (Tue Feb 26 21:04:56 CST 2013)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
    -> Found libdbusmenu-12.10.2.tar.gz
    ==> Validating source files with md5sums...
    libdbusmenu-12.10.2.tar.gz ... Passed
    ==> Extracting Sources...
    -> Extracting libdbusmenu-12.10.2.tar.gz with bsdtar
    ==> Removing existing pkg/ directory...
    ==> Starting build()...
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking whether NLS is requested... yes
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking dependency style of gcc... gcc3
    checking for intltool >= 0.35.0... 0.50.2 found
    checking for intltool-update... /usr/bin/intltool-update
    checking for intltool-merge... /usr/bin/intltool-merge
    checking for intltool-extract... /usr/bin/intltool-extract
    checking for xgettext... /usr/bin/xgettext
    checking for msgmerge... /usr/bin/msgmerge
    checking for msgfmt... /usr/bin/msgfmt
    checking for gmsgfmt... /usr/bin/msgfmt
    checking for perl... /usr/bin/perl
    checking for perl >= 5.8.1... 5.16.2
    checking for XML::Parser... ok
    checking for library containing strerror... none required
    checking for gcc... (cached) gcc
    checking whether we are using the GNU C compiler... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for gcc option to accept ISO C89... (cached) none needed
    checking dependency style of gcc... (cached) gcc3
    checking whether gcc and cc understand -c and -o together... yes
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /usr/bin/grep
    checking for egrep... /usr/bin/grep -E
    checking for ANSI C header files... yes
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking how to print strings... printf
    checking for a sed that does not truncate output... /usr/bin/sed
    checking for fgrep... /usr/bin/grep -F
    checking for ld used by gcc... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
    checking the name lister (/usr/bin/nm -B) interface... BSD nm
    checking whether ln -s works... yes
    checking the maximum length of command line arguments... 1572864
    checking whether the shell understands some XSI constructs... yes
    checking whether the shell understands "+="... yes
    checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
    checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
    checking for /usr/bin/ld option to reload object files... -r
    checking for objdump... objdump
    checking how to recognize dependent libraries... pass_all
    checking for dlltool... no
    checking how to associate runtime and link libraries... printf %s\n
    checking for ar... ar
    checking for archiver @FILE support... @
    checking for strip... strip
    checking for ranlib... ranlib
    checking command to parse /usr/bin/nm -B output from gcc object... ok
    checking for sysroot... no
    checking for mt... no
    checking if : is a manifest tool... no
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking for dlfcn.h... yes
    checking for objdir... .libs
    checking if gcc supports -fno-rtti -fno-exceptions... no
    checking for gcc option to produce PIC... -fPIC -DPIC
    checking if gcc PIC flag -fPIC -DPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking if gcc supports -c -o file.o... (cached) yes
    checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... no
    checking whether make supports nested variables... yes
    checking for glib-mkenums... /usr/bin/glib-mkenums
    checking for pkg-config... /home/tharriso/ApeInstalled/External/pkg-config/0.22/bin/pkg-config
    checking pkg-config is at least version 0.9.0... yes
    checking for gtkdoc-check... /usr/bin/gtkdoc-check
    checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase
    checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf
    checking whether to build gtk-doc documentation... no
    checking gnome-doc-utils >= 0.3.2... no
    configure: error: gnome-doc-utils >= 0.3.2 not found
    ==> ERROR: A failure occurred in build().
    Aborting...
    Some things I've tried -
    [tharriso@localhost libdbusmenu]$ pkg-config --modversion gnome-doc-utils
    Package gnome-doc-utils was not found in the pkg-config search path.
    Perhaps you should add the directory containing `gnome-doc-utils.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'gnome-doc-utils' found
    [tharriso@localhost libdbusmenu]$ pacman -Q gnome-doc-utils
    gnome-doc-utils 0.20.10-1
    Found a few results on Google where people mention the same error with a different package, but haven't found any solutions.
    Last edited by harro112 (2013-02-26 12:37:33)

    checking for pkg-config... /home/tharriso/ApeInstalled/External/pkg-config/0.22/bin/pkg-config
    current pkg-config version in arch is 0.28-1 , and should be found as /usr/bin/pkg-config .

  • [Gnome 3.8] Recommended way for upgrade? [SOLVED]

    Hi folks,
    upgrading Gnome from version 3.6 to 3.8 by using "pacman -Syu" doesn't seem to be the best way to do this. When I gave it a try yesterday, pacman asked me on a lot of packages (Gnome 3.6) if I want to replace them with different packages from Gnome 3.8 (looks as if the packages are arranged/renamed in a new way). In the end, pacman stopped because of some conflicting dependencies.
    So, would it be better to re-install Gnome using
    # pacman -S gnome gnome-extra
    although Gnome is already installed on my system?
    Or do you know any other appropriate way to upgrade from 3.6 to 3.8?
    Thanks
    Last edited by swordfish (2013-04-12 20:35:45)

    Inxsible wrote:
    WRONG! !
    pacman -Syu is the only way you should be upgrading. Remember, partial upgrades are not supported and will lead to a clusterfuck
    Actually, like the OP, I originally tried #pacman -Syu, which because of at least some Gnome 3.8 packages hitting testing, which I have enabled, would not succeed mainly because of the changes made within gnome-games and it's dependency with gnome-games-extra-data. I had to manually remove gnome-games-extra-data first before running #pacman -Syu again and answering yes to all the name changed gnome-games to be replaced by the new counterparts. I rebooted after that and ran the pacman upgrade command again which came up clean. I was still experiencing some little issues here and there and it didn't seem like everything 3.8 got pulled in and subsequent pacman runs were wanting to downgrade some of the packages I just upgraded. I read in this thread below, where folks had been testing gnome 3.8 from unstable, a suggestion after it hit testing, that running #pacman -S testing/gnome-extra was necessary to get everything working:
    https://bbs.archlinux.org/viewtopic.php … 1#p1257391
    When I later ran #pacman -S testing/gnome testing/gnome-extra, it wasn't really a matter of cherry-picking anything anymore than running that without testing enabled would be. In this case, it was merely reinstalling all the gnome and gnome-extra newest stuff (and maybe pulling in anything that somehow got missed) because of the quirks I was seeing with pacman's behavior. Normally, pacman seems to pull from testing fine if something newer is there. I keep the testing repos enabled and, at least once a day, run #pacman -Syu to obtain my updates / upgrades. I also install packages that are new to my system with #pacman -S pkgname, normally allowing pacman to pull in whatever it decides per it's conf file. I wasn't recommending that the OP turn on testing, grab what he wanted without doing a full upgrade first, then turn off testing, because I know that will quickly lead to a borked system.
    Last edited by sidneyk (2013-04-12 16:27:40)

  • [SOLVED]fail to build package: no such file or directory error

    EDIT1: read my last post
    I'm getting an error while installing pacman-color from the aur repository. I'm still a newbie so my only guess is to make such directory? why should I have to do that? anyone help?
    ==> Validating source files with md5sums...
        pacman-3.4.2.tar.gz ... Passed
        pacman-color-3.4.2-1.patch ... Passed
        color.conf ... Passed
    ==> Extracting Sources...
    ==> Removing existing pkg/ directory...
    ==> Starting build()...
    /tmp/yaourt-tmp-root/aur-pacman-color/./PKGBUILD: line 21: cd: pacman-3.4.2: No such file or directory
        Aborting...
    ==> ERROR: Makepkg was unable to build pacman-color.
    Last edited by aluser (2011-01-21 04:48:16)

    Here once again a failed attempt after removing pacman-color. I am beginning to think that maybe running yaourt as sudo is probably a bad idea. I think that may have had something to do with it.
    archuser@archws ~ % sudo yaourt -S abiword-light <11:54>
    Password:
    ==> Downloading abiword-light PKGBUILD from AUR...
    x PKGBUILD
    Comment by: mango on Thu, 25 Mar 2010 21:53:12 +0000
    ./configure --prefix=/usr \
    --disable-spell \
    --disable-print
    Comment by: chessboxing on Wed, 19 May 2010 14:33:51 +0000
    doesn't want to build
    rule 23: make: command not found
    == ERROR: Build Failed.
    Aborting...
    Eventhough I Had to install flex psiconv, it didn't help.
    Its a minefield man.
    Comment by: sHyLoCk on Wed, 02 Jun 2010 13:54:43 +0000
    http://aur.archlinux.org/packages.php?ID=37738
    Comment by: zenny on Thu, 02 Sep 2010 05:59:05 +0000
    Quite confusing statements. Below sHyLoCk recommends http://aur.archlinux.org/packages.php?ID=37738 on June 2 2010 and on June 27 he declares his recommended package obsolet and ask a TU to delete! The problem with the sHyLoCk package is there is not page setup option. So I installed this package, it has got the page setup menu, but once I click the option, the application dies with the following output (Maybe helpful to debug for the maintainer, I am not an expert):
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_markup: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_spin_button_set_value: assertion `GTK_IS_SPIN_BUTTON (spin_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): GLib-GObject-WARNING **: invalid (NULL) pointer instance
    (abiword:32455): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_clear: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_pack_start: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_set_attributes: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_set_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_clear: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_pack_start: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_cell_layout_set_attributes: assertion `GTK_IS_CELL_LAYOUT (cell_layout)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_combo_box_get_model: assertion `GTK_IS_COMBO_BOX (combo_box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_widget_get_colormap: assertion `GTK_IS_WIDGET (widget)' failed
    (abiword:32455): Gdk-CRITICAL **: gdk_pixmap_colormap_create_from_xpm_d: assertion `drawable != NULL || colormap != NULL' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_image_set_from_pixmap: assertion `mask == NULL || GDK_IS_PIXMAP (mask)' failed
    (abiword:32455): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    (abiword:32455): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
    (abiword:32455): Gtk-CRITICAL **: gtk_widget_get_colormap: assertion `GTK_IS_WIDGET (widget)' failed
    (abiword:32455): Gdk-CRITICAL **: gdk_pixmap_colormap_create_from_xpm_d: assertion `drawable != NULL || colormap != NULL' failed
    Aborted
    First Submitted: Wed, 15 Apr 2009 17:01:46 +0000
    abiword-light 2.8.6-2 : A fully-featured word processor without some gnome dependencies
    ( Unsupported package: Potentially dangerous ! )
    ==> Edit PKGBUILD ? [Y/n] ("A" to abort)
    ==> ------------------------------------
    ==> n
    ==> abiword-light dependencies:
    - fribidi>=0.10.9 (already installed)
    - wv>=1.2.4 (already installed)
    - libglade>=2.0 (already installed)
    - pkgconfig (already installed)
    ==> Continue building abiword-light ? [Y/n]
    ==> ---------------------------------------
    ==>
    ==> Building and installing package
    ==> WARNING: Building package as root is dangerous.
    Please run yaourt as a non-privileged user.
    ==> Making package: abiword-light 2.8.6-2 (Fri Jan 21 11:54:35 JST 2011)
    ==> Checking Runtime Dependencies...
    ==> Checking Buildtime Dependencies...
    ==> Retrieving Sources...
    -> Downloading abiword-2.8.6.tar.gz...
    --2011-01-21 11:54:35-- http://www.abisource.com/downloads/abiword/2.8.6/source/abiword-2.8.6.tar.gz
    Resolving www.abisource.com... 130.89.149.216
    Connecting to www.abisource.com|130.89.149.216|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 9218827 (8.8M) [application/x-gzip]
    Saving to: "abiword-2.8.6.tar.gz.part"
    100%[=======================================>] 9,218,827 414K/s in 28s
    2011-01-21 11:55:04 (325 KB/s) - "abiword-2.8.6.tar.gz.part" saved [9218827/9218827]
    ==> Validating source files with md5sums...
    abiword-2.8.6.tar.gz ... Passed
    ==> Extracting Sources...
    ==> Starting build()...
    /tmp/yaourt-tmp-root/aur-abiword-light/./PKGBUILD: line 16: cd: /tmp/yaourt-tmp-root/aur-abiword-light/src/abiword-2.8.6/: No such file or directory
    Aborting...
    ==> ERROR: Makepkg was unable to build abiword-light.
    ==> Restart building abiword-light ? [y/N]
    ==> --------------------------------------
    ==> archuser@archws ~ % <11:find /usr/{bin,lib} -type f -size 0
    /usr/lib/python3.1/tkinter/test/__init__.py
    /usr/lib/python3.1/tkinter/test/test_ttk/__init__.py
    /usr/lib/python3.1/tkinter/test/test_tkinter/__init__.py
    /usr/lib/python3.1/test/nullcert.pem
    /usr/lib/python3.1/site-packages/ranger/gui/__init__.py
    /usr/lib/python3.1/email/mime/__init__.py
    /usr/lib/python3.1/email/test/__init__.py
    /usr/lib/python3.1/urllib/__init__.py
    /usr/lib/python3.1/sqlite3/test/__init__.py
    /usr/lib/python3.1/pydoc_data/__init__.py
    /usr/lib/python3.1/lib2to3/tests/data/fixers/myfixes/__init__.py
    /usr/lib/python2.7/test/nullcert.pem
    /usr/lib/python2.7/site-packages/git_remote_helpers/git/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GL/MESAX/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GL/VERSION/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/GLU/EXT/__init__.py
    /usr/lib/python2.7/site-packages/OpenGL/AGL/__init__.py
    /usr/lib/python2.7/site-packages/pychess/__init__.py
    /usr/lib/python2.7/site-packages/pychess/widgets/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Utils/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Utils/lutils/__init__.py
    /usr/lib/python2.7/site-packages/pychess/ic/__init__.py
    /usr/lib/python2.7/site-packages/pychess/ic/managers/__init__.py
    /usr/lib/python2.7/site-packages/pychess/System/__init__.py
    /usr/lib/python2.7/site-packages/pychess/Players/__init__.py
    /usr/lib/python2.7/site-packages/pychess/gfx/__init__.py
    /usr/lib/python2.7/site-packages/xml2po/modes/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/gen_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/f2py_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/pyrex_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/swig_ext/__init__.py
    /usr/lib/python2.7/site-packages/numpy/distutils/tests/f2py_f90_ext/__init__.py
    /usr/lib/python2.7/site-packages/bzrlib/util/__init__.py
    /usr/lib/python2.7/site-packages/bzrlib/util/configobj/__init__.py
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/__init__.py
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_LINK_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_EXCEPTION
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_UNPARSEABLE
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/TESTS_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/TESTS_INVALID
    /usr/lib/python2.7/site-packages/pygame/tests/util/build_page/libs/build_client/test_fixtures/BUILD_FAILED_UNKNOWN
    /usr/lib/python2.7/site-packages/pygame/examples/__init__.py
    /usr/lib/python2.7/site-packages/gtk-2.0/egg/__init__.py
    /usr/lib/python2.7/site-packages/gtk-2.0/gi/overrides/__init__.py
    /usr/lib/python2.7/site-packages/sonata/__init__.py
    /usr/lib/python2.7/site-packages/sonata/plugins/__init__.py
    /usr/lib/python2.7/email/mime/__init__.py
    /usr/lib/python2.7/email/test/__init__.py
    /usr/lib/python2.7/sqlite3/test/__init__.py
    /usr/lib/python2.7/pydoc_data/__init__.py
    /usr/lib/python2.7/bsddb/test/__init__.py
    /usr/lib/python2.7/lib-tk/test/test_ttk/__init__.py
    /usr/lib/python2.7/lib-tk/test/test_tkinter/__init__.py
    /usr/lib/python2.7/lib2to3/tests/data/fixers/myfixes/__init__.py
    /usr/lib/purple-2/perl/auto/Purple/Purple.bs
    /usr/lib/perl5/vendor_perl/auto/HTML/Parser/Parser.bs
    /usr/lib/perl5/vendor_perl/auto/XML/Parser/Expat/Expat.bs
    /usr/lib/perl5/vendor_perl/auto/Crypt/SSLeay/SSLeay.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/Irssi.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/UI/UI.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/Irc/Irc.bs
    /usr/lib/perl5/vendor_perl/auto/Irssi/TextUI/TextUI.bs
    /usr/lib/pidgin/perl/auto/Pidgin/Pidgin.bs
    /usr/lib/firefox-3.6/.autoreg
    archuser@archws ~ %
    Last edited by aluser (2011-01-21 03:02:22)

  • [SOLVED]Gnome Wayland won't start

    Hello everyone.
    I was hoping to try out gnome with wayland but i have problem. I normally install gnome-shell package and dependencies from official source with gdm, than i follow Wayland thread on ArchWiki, XWayland-git installed so is mutter-wayland. I normally kill Lightdm and start GDM with systemctl but when i choose Gnome Wayland session screen blacks out and i am after a few seconds on GDM screen. GDM starts diffrent sessions mostly with no problem (but session chooser not always appears and  after fail to login to Gnome Wayland it have problem with different session- however not always, it's basically random). If it matters- i have Intel iGPU 2500 with Asus UEFI board- rest is not relevent. My primary desktop is XFCE with lightdm but in past I've got almost every desktop and maybe wayland doesn't like some files on my hard drive.
    Peace.
    Last edited by maslascher (2014-07-12 15:44:19)

    Yes. Everything appears to be right in place.
    Edit. Never mind. I've reinstalled gnome and wayland packages and it works like charm.
    Thread solved.
    Last edited by maslascher (2014-07-12 15:43:29)

  • Gdm depends on gnome-desktop [SOLVED]

    I have xfce and want to have a display manager so that I can automatically boot to the desktop. In (X)ubuntu I used to have gdm, so I would like to have that now too. The problem is that when I try to install gdm with pacman, gnome-desktop becomes a target. How come? Xubuntu uses gdm without having Gnome installed.
    If it isn't possible I guess I will have to install SLiM, but gdm would be my first choice.
    Last edited by jeypeyy (2010-01-24 10:21:51)

    jeypeyy wrote:
    I have xfce and want to have a display manager so that I can automatically boot to the desktop. In (X)ubuntu I used to have gdm, so I would like to have that now too. The problem is that when I try to install gdm with pacman, gnome-desktop becomes a target. How come? Xubuntu uses gdm without having Gnome installed.
    If it isn't possible I guess I will have to install SLiM, but gdm would be my first choice.
    gdm has the same depedencies in ubuntu as in arch but the thing is they have split packages. they split gnome-panel in libpanel-applet2-0  etc. the same can be on gnome-desktop.
    http://packages.ubuntu.com/karmic/gdm
    if you really want to get rid of gnome-desktop, i recommend abs and recompile it and see if is working without gnome-desktop and his dependencies

  • Install gnome/kde/xfce to /usr?

    Why don't we just put everything into /usr? The /opt serves no purpose since all apps are installed/removed by pacman and not untar/rm. And where should you install an app that needs both of kde and gnome?? /opt/kde+gnome?
    The reasons people are against this are summarized below:
    · The standard says "Large software packages must not use a direct subdirectory under the /usr hierarchy": BUT kde and gnome are not large packages (like openoffice), but many small packages, just like the rest of linux. The "GNOME" or "KDE" is just a conceptual name for end-users. Any app or user could use 1% of gnome/kde packages and keep away from the other 99%.
    · Puting all files into /usr is slow: There isn't any benchmark to confirm that. And a nearly-complete gnome 2.14 installation contains only about 100-200 files in /opt/gnome/bin/, compared to more than 1000 in /usr/bin. It just can't cause any slow down on modern linux filesystems. (it's 1,100+ not 11,000+)

    once upon a time, it was simpler and certainly cleaner to put things in opt as we do, and we didnt have a standard telling us what to do. Time have changed since, and it's quite a monumental and time consuming task to move all of gnome, all of kde, and all of the various programs back to /usr, something that just doesnt seem like it will reap any benefit for all the effort.  That's the sole reason why things are in opt. Simple.
    Sure, there's the standard -- but because there's a standard, doesnt mean we must follow it. Plenty of people get caught up in the word 'standard' and instagib-flame-kinghit-ko-up-left-right-right-down anyone who speaks against a standard irrelevant of the quality or applicability of the standard.
    It's not like most distros actually observe the standard anyway. I havn't seen a single distro having httpd serve out of /srv. The standard itself is out of date and contradictory. Xorg moved from X11R6 to /usr a while back now. Besides, why seperate  X into X11R6? what makes it so special that it must be seperated yet kde and gnome cannot?
    And is having kde and gnome seperate actually a violation of the standard?
    It's no difficult stretch of the mind to consider them "Add-on application software packages" after all, they're not required for a system to run, and nor are they installed by default, they are addons after installation.
    If we now look at the /usr section of the FHS, we see that:
    /usr is the second major section of the filesystem. /usr is shareable, read-only data ..... Large software packages must not use a direct subdirectory under the /usr hierarchy.
    It isnt difficult to consider KDE and GNOME large software packages. Saying they aren't large because they're split, is like calling OOo small if we split it up into each of it's components, libraries and programs. If you do decide to use any particular KDE and GNOME app, there exists something known as dependencies. For kde, you'll get a minimum of 30mb from kdebase, and that's just the tarball, not the extracted size.
    The desktops themselves are quite large anyway. pacman -S gnome. I havn't got a clean install on me here, but it's surely a reasonable size to install to get a functioning GNOME desktop, KDE is definitely quite big, with kdebase alone being 30mb.
    If you look at the actual standard, it's pretty flexible, and it's definition of /opt's purpose is very lofty. The rationale for it, is that "The use of /opt for add-on software is a well-established practice in the UNIX community"
    http://www.pathname.com/fhs/pub/fhs-2.3 … REPACKAGES
    And we can take their approach here too, not only is it fine to put kde and gnome in opt as they are addon packages, but we can use their own rationale and say "that's how we've always done it"
    By no means do I remotely agree with the standard, but if you can use it to argue for putting them in /usr, you can also use it to argue for putting them in /opt. Either way, it negates this standard because of the ambiguity in this area and doesnt change the sole reason why things are in /opt in arch, which I explained first.
    James

  • Qustions about Package "Groups"

    Hello,
    I have some general questions about package "groups" in Pacman. Mainly, I'm curious about who is responsible for deciding when a group will be made and what packages will be included. For example, I type in "pacman -S gnome" and get this:
    gnome package not found, searching for group...
    :: group gnome (including ignored packages):
    epiphany gnome-applets gnome-backgrounds gnome-control-center
    gnome-desktop gnome-icon-theme gnome-media gnome-mime-data gnome-mount
    gnome-panel gnome-screensaver gnome-session gnome-settings-daemon
    gnome-themes gnome2-user-docs libgail-gnome metacity nautilus
    notification-daemon yelp
    :: Install whole content? [Y/n]
    Who decides what all those packages will be? Is there a place where users can provide input about what should be included? I realize a big part of package groups by be simply ease of dependecy managent, but it seems it would be a useful tool for users to get a system up and running quickly. For example, there are several basic things that one would need to get a usable "desktop" up and running (not counting the WM or DM). For example, xorg, alsa, etc.
    I understand that Arch is all about simplicity and building a system from the ground up, which I totally love, but many of us are still going to have the same core goals in mind when setting up a "desktop" system.  We're all going to need xorg, want sound, desire pretty fonts, and have some common useful apps. So, for anyone that falls into that category, a package group called something like "arch-desktop" could include some of these core components. We could even eventually have additional groups tailored towards specific DMs like "arch-desktop-xfce" or "arch-desktop-gnome".
    Now, I realize I've totally spun this specifically for this propsed "arch-desktop" group but I guess my main point was to find out where one could provide official input for such things.
    Thanks!
    Swill

    Mr. Swillis wrote:It seems to me like something that could make things "quicker" for an advanced user to get setup (less stuff to remember) and perhaps "easier" for teaching new Arch users.
    Since pacman will resolve all dependencies, all you need is to do a
    # pacman -Syu
    # pacman -S gnome
    after a core-install. Everything else you would need, could be clutter to someone else. I don't believe there is something as a 'sane default of packages'. Maybe if you're a fan of a particular windowmanager, then you might be interested in what the majority uses for a panel, a taskbar, a background-image-viewer, but also then there are so many choices and personal preferences that everyone could make his or her own group of packages.
    my 0.02€

  • [SOLVED]How I can prevent gnome from updating?

    Hi there!
    Currently I use Gnome 3.4
    The last time I did full system updated to Gnome 3.6, everything went very bad. Currently I have a lot of packages waiting for update, and I do not update because it includes a lot of Gnome 3.6 packages as well. Is there a way to ignore the whole gnome group from updating? Currently I do not have time to mess with the stupid things they did in Gnome 3.6, but I do want my system up to date.
    Thank you!
    Last edited by skwo (2012-12-10 14:51:41)

    You can use IgnoreGroup in the [options] section of pacman.conf:
    IgnoreGroup = gnome
    For more info, see the wiki: https://wiki.archlinux.org/index.php/Pa … g_upgraded
    Personally never used the feature, so I'm not sure about the implications of ignoring an entire group.

Maybe you are looking for