You are not logged in.
Pages: 1
Hello, I'm very new in Linux (especially in arch), when i start my system, in couple of seconds it freezes forever (at least some parts of DE, such as Activities) and cause crash of my docky, i forced to enter r in ALT+F2 and start again my dock, further work of system looks OK. Could you not help me to find out what is causing the problem and how to fix it? Because as i said i am newbie in Linux and i don't know how to examine this problem, i don't have something else in boot list except docky (docky doesn't cause the problem, i tried to turn him off).
Offline
Hello, I'm very new in Linux (especially in arch), when i start my system, in couple of seconds it freezes forever (at least some parts of DE, such as Activities) and cause crash of my docky, i forced to enter r in ALT+F2 and start again my dock, further work of system looks OK. Could you not help me to find out what is causing the problem and how to fix it? Because as i said i am newbie in Linux and i don't know how to examine this problem, i don't have something else in boot list except docky (docky doesn't cause the problem, i tried to turn him off).
How did you install Arch?
I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.
Offline
nammidd wrote:Hello, I'm very new in Linux (especially in arch), when i start my system, in couple of seconds it freezes forever (at least some parts of DE, such as Activities) and cause crash of my docky, i forced to enter r in ALT+F2 and start again my dock, further work of system looks OK. Could you not help me to find out what is causing the problem and how to fix it? Because as i said i am newbie in Linux and i don't know how to examine this problem, i don't have something else in boot list except docky (docky doesn't cause the problem, i tried to turn him off).
How did you install Arch?
https://wiki.archlinux.org/index.php/Beginners'_guide
It pretty easy to install arch, there will be something on the topic? Or are you just come in Newbie Corner to ask a question "how did you install arch"?
Last edited by nammidd (2016-07-22 07:32:19)
Offline
It's a valid question, nammidd, no need to wet your panties over this.
Now, elaborate in an orderly fashion, what exactly happens. What DE? What are activities? How do you start X? What do the logs say? Post log outputs. Read "man journalctl".
Offline
dockland wrote:nammidd wrote:Hello, I'm very new in Linux (especially in arch), when i start my system, in couple of seconds it freezes forever (at least some parts of DE, such as Activities) and cause crash of my docky, i forced to enter r in ALT+F2 and start again my dock, further work of system looks OK. Could you not help me to find out what is causing the problem and how to fix it? Because as i said i am newbie in Linux and i don't know how to examine this problem, i don't have something else in boot list except docky (docky doesn't cause the problem, i tried to turn him off).
How did you install Arch?
https://wiki.archlinux.org/index.php/Beginners'_guide
It pretty easy to install arch, there will be something on the topic? Or are you just come in Newbie Corner to ask a question "how did you install arch"?
There are so many installers and "helpers" out there that is not supported. Thats why i asked.
Post your output of:
systemctl status
systemd-analyze blame
systemctl --failed
I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.
Offline
You should specify which DE you are using.
Usually with this kind of issues, the first thing you should check is systemd journal for any errors.
Last edited by ooo (2016-07-22 07:43:12)
Offline
I am using gnome 3.20, in systemctl everything is ok and system is up to date either.
systemd-analyze blame
956ms home-saddam-D.mount
816ms home-saddam-E.mount
272ms dnsmasq.service
169ms dev-sda2.device
121ms systemd-timesyncd.service
114ms systemd-journald.service
108ms accounts-daemon.service
101ms upower.service
60ms systemd-journal-flush.service
58ms systemd-vconsole-setup.service
46ms udisks2.service
44ms systemd-udevd.service
41ms systemd-modules-load.service
39ms polkit.service
31ms systemd-tmpfiles-setup-dev.service
31ms gdm.service
31ms user@1000.service
29ms dhcpcd.service
29ms systemd-udev-trigger.service
21ms user@120.service
13ms systemd-binfmt.service
12ms geoclue.service
11ms colord.service
10ms tmp.mount
systemctl status
● arch
State: running
Jobs: 0 queued
Failed: 0 units
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─tor.service
│ │ └─459 /usr/bin/tor -f /etc/tor/torrc
│ ├─dbus.service
│ │ └─447 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
│ ├─dhcpcd.service
│ │ └─453 /usr/bin/dhcpcd -q -b
│ ├─wpa_supplicant.service
│ │ └─665 /usr/bin/wpa_supplicant -u
│ ├─home-saddam-D.mount
│ │ └─439 /sbin/mount.ntfs-3g /dev/sdc1 /home/saddam/D -o rw,uid=1000,gid=100,umask=0
│ ├─accounts-daemon.service
│ │ └─480 /usr/lib/accountsservice/accounts-daemon
│ ├─colord.service
│ │ └─672 /usr/lib/colord/colord
│ ├─systemd-journald.service
│ │ └─224 /usr/lib/systemd/systemd-journald
│ ├─home-saddam-E.mount
│ │ └─438 /sbin/mount.ntfs-3g /dev/sdb2 /home/saddam/E -o rw,uid=1000,gid=100,umask=0
│ ├─udisks2.service
│ │ └─844 /usr/lib/udisks2/udisksd --no-debug
│ ├─dnsmasq.service
│ │ └─477 /usr/bin/dnsmasq -k --enable-dbus --user=dnsmasq --pid-file
│ ├─upower.service
│ │ └─519 /usr/lib/upower/upowerd
│ ├─systemd-timesyncd.service
│ │ └─443 /usr/lib/systemd/systemd-timesyncd
│ ├─systemd-logind.service
│ │ └─456 /usr/lib/systemd/systemd-logind
│ ├─systemd-udevd.service
│ │ └─256 /usr/lib/systemd/systemd-udevd
│ ├─polkit.service
│ │ └─484 /usr/lib/polkit-1/polkitd --no-debug
│ ├─gdm.service
│ │ └─468 /usr/bin/gdm
│ ├─geoclue.service
│ │ └─831 /usr/lib/geoclue2/geoclue -t 5
│ └─rtkit-daemon.service
│ └─645 /usr/lib/rtkit/rtkit-daemon
└─user.slice
├─user-1000.slice
│ ├─user@1000.service
│ │ ├─gvfs-daemon.service
│ │ │ ├─773 /usr/lib/gvfs/gvfsd
│ │ │ └─778 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
│ │ ├─dbus.service
│ │ │ ├─765 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
│ │ │ ├─836 /usr/lib/telepathy/mission-control-5
│ │ │ └─898 /usr/lib/GConf/gconfd-2
│ │ ├─at-spi-dbus-bus.service
│ │ │ ├─791 /usr/lib/at-spi2-core/at-spi-bus-launcher
│ │ │ ├─796 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
│ │ │ └─799 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
│ │ ├─pulseaudio.service
│ │ │ └─819 /usr/bin/pulseaudio --daemonize=no
│ │ ├─gvfs-afc-volume-monitor.service
│ │ │ └─856 /usr/lib/gvfs/gvfs-afc-volume-monitor
│ │ ├─init.scope
systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Last edited by nammidd (2016-07-22 08:18:08)
Offline
I am using gnome 3.20, in systemctl everything is ok and system is up to date either.
systemd-analyze blame
956ms home-saddam-D.mount 816ms home-saddam-E.mount 272ms dnsmasq.service 169ms dev-sda2.device 121ms systemd-timesyncd.service 114ms systemd-journald.service 108ms accounts-daemon.service 101ms upower.service 60ms systemd-journal-flush.service 58ms systemd-vconsole-setup.service 46ms udisks2.service 44ms systemd-udevd.service 41ms systemd-modules-load.service 39ms polkit.service 31ms systemd-tmpfiles-setup-dev.service 31ms gdm.service 31ms user@1000.service 29ms dhcpcd.service 29ms systemd-udev-trigger.service 21ms user@120.service 13ms systemd-binfmt.service 12ms geoclue.service 11ms colord.service 10ms tmp.mount
systemctl status
● arch State: running Jobs: 0 queued Failed: 0 units CGroup: / ├─init.scope │ └─1 /sbin/init ├─system.slice │ ├─tor.service │ │ └─459 /usr/bin/tor -f /etc/tor/torrc │ ├─dbus.service │ │ └─447 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation │ ├─dhcpcd.service │ │ └─453 /usr/bin/dhcpcd -q -b │ ├─wpa_supplicant.service │ │ └─665 /usr/bin/wpa_supplicant -u │ ├─home-saddam-D.mount │ │ └─439 /sbin/mount.ntfs-3g /dev/sdc1 /home/saddam/D -o rw,uid=1000,gid=100,umask=0 │ ├─accounts-daemon.service │ │ └─480 /usr/lib/accountsservice/accounts-daemon │ ├─colord.service │ │ └─672 /usr/lib/colord/colord │ ├─systemd-journald.service │ │ └─224 /usr/lib/systemd/systemd-journald │ ├─home-saddam-E.mount │ │ └─438 /sbin/mount.ntfs-3g /dev/sdb2 /home/saddam/E -o rw,uid=1000,gid=100,umask=0 │ ├─udisks2.service │ │ └─844 /usr/lib/udisks2/udisksd --no-debug │ ├─dnsmasq.service │ │ └─477 /usr/bin/dnsmasq -k --enable-dbus --user=dnsmasq --pid-file │ ├─upower.service │ │ └─519 /usr/lib/upower/upowerd │ ├─systemd-timesyncd.service │ │ └─443 /usr/lib/systemd/systemd-timesyncd │ ├─systemd-logind.service │ │ └─456 /usr/lib/systemd/systemd-logind │ ├─systemd-udevd.service │ │ └─256 /usr/lib/systemd/systemd-udevd │ ├─polkit.service │ │ └─484 /usr/lib/polkit-1/polkitd --no-debug │ ├─gdm.service │ │ └─468 /usr/bin/gdm │ ├─geoclue.service │ │ └─831 /usr/lib/geoclue2/geoclue -t 5 │ └─rtkit-daemon.service │ └─645 /usr/lib/rtkit/rtkit-daemon └─user.slice ├─user-1000.slice │ ├─user@1000.service │ │ ├─gvfs-daemon.service │ │ │ ├─773 /usr/lib/gvfs/gvfsd │ │ │ └─778 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes │ │ ├─dbus.service │ │ │ ├─765 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation │ │ │ ├─836 /usr/lib/telepathy/mission-control-5 │ │ │ └─898 /usr/lib/GConf/gconfd-2 │ │ ├─at-spi-dbus-bus.service │ │ │ ├─791 /usr/lib/at-spi2-core/at-spi-bus-launcher │ │ │ ├─796 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 │ │ │ └─799 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session │ │ ├─pulseaudio.service │ │ │ └─819 /usr/bin/pulseaudio --daemonize=no │ │ ├─gvfs-afc-volume-monitor.service │ │ │ └─856 /usr/lib/gvfs/gvfs-afc-volume-monitor │ │ ├─init.scope
systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.
Kan you monitor with htop or glances from start, to see what processes that might have hig CPU or RAM-load?
I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.
Offline
dockland
only gnome shell 3, 4 %, maximum 30.
Last edited by nammidd (2016-07-22 09:52:09)
Offline
Pages: 1