• Everything Black (No Theming)


    I just installed a bunch of updates (and Virtualbox stuff) and rebooted.

    Now my background is black, and everything has a very old looking design. Like its missing the icon theme and the theming for windows and all that. Everything seems to be working though (besides not being able to right click on desktop).

    I tried rebooting Cinnamon but changes nothing. Any ideas, how do I figure out which update or change caused this.

    To add, the fonts are super large in many apps (as if DPI is set larger), icons are missing or like default, black background and no clicking available, screensaver does not work…its very odd.

  • Here is from the history of it

    [2017-03-18 18:19] [ALPM] running 'update-mime-database.hook'...
    [2017-03-18 18:19] [ALPM] running 'update-desktop-database.hook'...
    [2017-03-18 18:19] [ALPM] running 'texinfo-install.hook'...
    [2017-03-18 18:19] [ALPM] running 'systemd-update.hook'...
    [2017-03-18 18:19] [ALPM] running 'gtk-update-icon-cache.hook'...
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Image generation successful
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [block]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [base]
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Starting build: 4.10.3-1-ARCH
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Image generation successful
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [block]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> Running build hook: [base]
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Starting build: 4.10.3-1-ARCH
    [2017-03-18 18:19] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2017-03-18 18:19] [ALPM] running '99-linux.hook'...
    [2017-03-18 18:19] [ALPM] transaction completed
    [2017-03-18 18:19] [ALPM] upgraded wine (2.3-1 -> 2.4-1)
    [2017-03-18 18:19] [ALPM] upgraded perl-libwww (6.19-2 -> 6.24-1)
    [2017-03-18 18:19] [ALPM] upgraded man-pages (4.09-1 -> 4.10-2)
    [2017-03-18 18:19] [ALPM] upgraded libreoffice-fresh (5.3.0-2 -> 5.3.1-1)
    [2017-03-18 18:19] [ALPM] upgraded xorg-server (1.19.2-1 -> 1.19.3-1)
    [2017-03-18 18:19] [ALPM] upgraded xorg-server-common (1.19.2-1 -> 1.19.3-1)
    [2017-03-18 18:19] [ALPM] upgraded jansson (2.9-1 -> 2.10-1)
    [2017-03-18 18:19] [ALPM] upgraded imagemagick (6.9.8.0-1 -> 6.9.8.1-1)
    [2017-03-18 18:19] [ALPM] upgraded grub (1:2.02.rc1-1 -> 1:2.02.rc2-1)
    [2017-03-18 18:19] [ALPM] upgraded ghostscript (9.20-4 -> 9.21-1)
    [2017-03-18 18:19] [ALPM] upgraded cryptsetup (1.7.3-1 -> 1.7.4-1)
    [2017-03-18 18:19] [ALPM-SCRIPTLET] ln: failed to create symbolic link '/usr/share/antergos/logo-square32.png': File exists
    [2017-03-18 18:19] [ALPM] upgraded antergos-repo-priority (1.0.6-1 -> 1.0.6-2)
    [2017-03-18 18:19] [ALPM] upgraded keyutils (1.5.9-1 -> 1.5.10-1)
    
  • I was hoping someone else had this issue and got it fixed.

    Really wondering what happened, should`t have an issue updating.

  • @noobertroon , hi.
    I can see an upgrade to the new current kernel. Have you tried using the LTS kernel to see if the problem is this?
    sudo pacman -S linux-lts
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    and reboot.

    Cheers

    @noobertroon said

    (and Virtualbox stuff)

    In case it is successful, install linux-lts-headers, too.

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • Did that and rebooted, same situation :(

    And pretty sure I was on 4.10 something, and it just went to a slightly newer version.

    Anything else. Thanks

  • @noobertroon , thanks for nothing, then…Sorry about that.

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • Better than not getting an answer :)

    The more that answer, hopefully the MORE that answer.

  • Another weird thing about this situation and that certain settings do not open, but some do. Along with that is my keyboard (so part of a settings area) is defaulted back to the original layout. Which I mean when I installed Antergos it was set to french, which I cant use the question mark and a few other items because it does some french thing…sadly i go open up the keyboard settings and its set correctly…

    Anyway…if I cant get this fixed by today, I need to do a fresh install as I can not do my job tomorrow with a messed keyboard. That is fine, but I do not want it to happen again so would love to know what caused it and why

  • @noobertroon An hour ago I started to install fresh Antergos Cinnamon 17.3, to test your case. I’m finishibng setup in these minutes.

    Everything is themed as it should. There are no “black” themes or screen areas. All Cinnamon themes components - Window borders, Controls, Desktop - may be freely set either to default or to user-added themes.

    I’m using five different keyboard layouts - English (US), English (UK), Finnish, Italian, Russian. All five work flawlessly.

    Can’t reproduce the problems you’re talking about. Antergos Cinnamon 17.3 works without a problem.

  • Thanks for doing that.

    Could a program I installed (like virtualbox and needed files) cause something like this, as if a conflict with the updated files. I guess I am not really going to know.

    I will be doing a wipe and fresh install today sometime then. Sad, I was hoping to learn what occurred.

    Side note, how does updates work with the installer. I downloaded Antergos 6 days ago or something and put the ISO on a USB stick. There have been a bunch of updates since install. Does that same Antergos grab those updated during installation, or should I grab a newer download of Antergos.

  • @noobertroon said in Everything Black (No Theming):

    Thanks for doing that.

    Could a program I installed (like virtualbox and needed files) cause something like this, as if a conflict with the updated files. I guess I am not really going to know.

    Do a clean install. I mean, choose any addons you wish in Cnchi, during instalaation, but do not install by hand any additional packages once the installation is finished. This way, you’ll get a clean Antergos Cinnamon 17.3 installation. If it works, back it up, and then start adding your pkgs - to ruin the system again :) .

    I will be doing a wipe and fresh install today sometime then. Sad, I was hoping to learn what occurred.

    Side note, how does updates work with the installer. I downloaded Antergos 6 days ago or something and put the ISO on a USB stick. There have been a bunch of updates since install. Does that same Antergos grab those updated during installation, or should I grab a newer download of Antergos.

    That’s the force of Anteros and Cnchi - you never need to download a new Antergos ISO or worry about recent Arch ugrades. The main Antergos difference from all other distros is that its ISO doesn’t contain any Arch package. Cnchi downloads and installs the most recent pkgs directly from Arch mirrors during installation.

    Moreover, Cnchi upgrades itself to the most recent release, before installation is started. And it’s not finished yet - Cnchi finds the best - fastest - Arch mirrors for you, before it starts to download pkgs.

    Briefly - if you have more or less recent Antergos ISO on a LiveMedia, you shouldn’t worry about anything. Cnchi will do all the job for you.

  • Thanks.

    When you say back it up… what are you suggesting example, imaging it or what. Do you have a suggestion :)

  • @noobertroon said in Everything Black (No Theming):


    When you say back it up… what are you suggesting example, imaging it or what. Do you have a suggestion :)

    Two tools allow to fully restore a desperately broken system into original, lovely working state:

    • clonezilla
    • fsarchiver

    If a backup of the whole / partition is done with either of two, we can experiment, destroy, and do everything we wish with our system. Clonezilla or Fsarchiver will always restore it to the working state.

  • Which one is better lol

    I never used one before. I assume you install it on a thumbdrive, make the backup, but where does the backup go. Is the thumbdrive supposed to have enough space on it

  • @noobertroon said in Everything Black (No Theming):

    Which one is better lol

    I never used one before. I assume you install it on a thumbdrive, make the backup, but where does the backup go. Is the thumbdrive supposed to have enough space on it
    I startes with clonezilla, and used it for a long time. But in last 4-5 years I use only fsarchiver. Clonezilla is for mission-critical backups. Fsarchiver is wa-a-y more flexible, perfect for everyday dackups.

    Yes, both must be started from any media, external to the partition being backed up. From LiveCD, LiveDVD, LiveUSB, from another Linux on the same computer but installed and running from other partition(s).

    I’ve run clonezilla from LiveUSB. The standard clonezilla doesn’t provide a way to be placed on LiveUSB, it should be burned onto LiveCD/DVD only. But I’ve put it on LiveUSB nevertheless. Everything is possible with Linnux :) .

    But fsarchiver is the most used tool here. It is included in every Linux distro, so I install it everywhere. Then, when I want to backup Linuxes A, B, C, D I just boot into Linux X, on the same computer, and backup A, B, C, D from X.

    I always backup to external (USB) disks. There’s no sense to do it on the computer’s disks - if the computer gets broken, how to access backups on its disks?

  • So I am up and running on the fresh system.

    Not 100% on the image software. I install Fsarchiver onto a thumb drive. It creates the image and you are saying this image is going to be saved on this thumbdrive?

    How large would the image be? I only have a 16GB thumbdrive. My SSD with Antergos on it is 500GB.

  • @noobertroon You’re going way off-topic. Please, open another thread to ask about backup | restore.

    fsarchiver has a very good help and man pages. See

    fsarchiver --help
    

    and

    man fsarchiver
    

    Back on topic. If your freshly installed Antergos Cinnamon 17.3 is not “black” anymore and is themed correctly, could you consider to close this topic?

theming1 black34 Posts 17Views 733
Log in to reply