SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

Pages: 1 2

#1 Re: News & Announcements » The end. » 2015-02-06 15:30:55

Malice

I'm saddened by this news. Unfortunately I disagree with you, that #! doesn't have anything to offer - it's still my distribution of choice, since it packs so much awesome in it. It's basically debian, set up with minimalistic environment. If I were to make my own installation, I'd surely make it look more or less like #!, but with Crunchbang existing, I don't have to.
Plus it's super easy to switch to Crunchbang unstable/testing, which makes it up-to-date great distro, that's swift, ellegant, and reliable.
This said, I understand the situation and want to thank you for your work. Crunchbang made me switch to linux, and if it wasn't for it, I would still use windows, which is crappy. Thanks for giving me this opportunity. I wish you good luck in whatever you do.

#2 Re: Help & Support (Testing/Unstable) » Xorg session killed by Steam » 2014-09-12 18:13:38

Malice

Alad - I've been using properiarity drivers for a long time, never had problem with them. Also, problem didn't occur due to change of drivers.

And when I delete xorg.conf I can't start xorg session.

#3 Re: Help & Support (Testing/Unstable) » Xorg session killed by Steam » 2014-09-11 08:42:17

Malice

Bump. Still not fixed sad

#4 Re: Help & Support (Testing/Unstable) » Xorg session killed by Steam » 2014-09-10 01:22:50

Malice

http://pastebin.com/YZkQZwW5
Here you are.

#5 Help & Support (Testing/Unstable) » Xorg session killed by Steam » 2014-09-09 21:15:07

Malice
Replies: 6

Hello, it looks like Xorg session is being killed by Steam at Steam startup.

Basically, whenever I try to run Steam, it doesn't even show up - instead, after few seconds everything's gone, and slime pops up allowing me to run new session(but tty with previous one is busy), however everything from previous session is killed, I believe - ram usage stays like after startup. It looks like segfault somewhere, but I'm not sure.
Here's syslog: http://pastebin.com/qP4cNE34
And here's Xorg.log: http://pastebin.com/X6nyauWx
I'd be glad to know how can I fix it. It came up when I was trying to fix another problem, with Thunar not allowing me to use USB, but that's different story...

#6 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2014-01-04 18:05:16

Malice

I see this problem is tough smile I decided to uninstall slime. If that's causing problem, then I'll just get rid of it... Unfortunately.
I won't mark as solved, since it wasn't really solved, but the case is closed.

#7 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-28 19:10:37

Malice

@ohnonot - After grub(choosing kernel), slim opens normally. I can enter login and password in GUI, but after that nothing happens.
"Window", where I wrote my login and password is gone, and nothing but background can be seen. No mouse pointer, nothing at all.
All of this happens in C-M-F7 space(so it's probably called tty7, I guess).
After that, I enter other tty(doesn't matter which one), log in there, and type "startx". It sends me to C-M-F8("tty8"?), and I am logged-in. Everything works there. However, on C-M-F7 there's still this blank login screen.

Reinstalling is not an option.
I tried solving this problem. Also, not alone - many people on IRC tried too, but it seems that this isn't so simple to fix. smile

I've found this about Slim:
https://bugs.freedesktop.org/show_bug.cgi?id=62866#c1

Where I don't understand much apart from that Slim may not be working correctly with systemd.
@ohnonot - if you are logged-in now, I'm on #crunchbang. You may come here and try to help me directly. I'm sitting on #crunchbang IRC channel quite often, it shouldn't be hard to catch me there.

As for doing first steps myself - I checked some files in /etc(slim.conf, grub), but grub seems unrelated, and in slim.conf I can't find anything wrong. I don't know what else should I look for.

Help would be appreciated.
Also, thanks for reply.

Edit:
Okay, checked /etc/X11/default-display-manager and it points to /usr/bin/slim, which exists.

#8 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-28 13:22:48

Malice

Okay. No point in creating new thread. Turns out it isn't solved, I still have to use startx to log in. It worked at the first time, and then maybe twice. Any ideas?

When I use startx, I am sent to tty8(I hope it's called so - I get there with C-M-F8). tty7(C-M-F7) is the screen where I was logging in without success - I can see only default login background there, nothing more.

#9 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 23:55:26

Malice

Okay, fixed. Thank you ohnonot, dano, and many people from #! IRC help channel for helping me.
if anyone encounter the same problem:
I kind of did the same thing as ew in this topic: http://crunchbang.org/forums/viewtopic.php?id=27309
Unfortunately, I didn't know about dependencies before, so after I installed it, I first had to (re)install nVidia drivers.
After that, I reinstalled them with smxi, and I could login using startx.
However, it threw me to gnome, so I uninstalled gnome-session, switched using update--alternatives to openbox, and rebooted.
Now It would log me to openbox... but I still had to use startx.
Then I uninstalled the things mentioned in ew's topic(gnome-bluetooth, and bluez). Reinstalled, and now it seems to be working.

#10 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 23:08:28

Malice

Links are sufficient. Thank you for that.

#11 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 16:37:30

Malice

Your commands do not show any errors. These only let me  go to login screen, where everything goes as usual.

Maybe it will tell you something, that now I have ttys at F1-F6, at F7 I have the non-working blank after-login screen, and I'm using GUI at F8.

#12 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 16:33:15

Malice

damo - I did... tongue
anyway, output from your commands:

malice@crunchbang:~$ sudo service slim start
[sudo] password for malice: 
Starting X display manager: slim already running.
malice@crunchbang:~$ sudo service slim stop
Stopping X display manager: slim.

Also, now every time I open terminator, I can see the line:

bash: /usr/lib/git-core/git-sh-prompt: No such file or directory
malice@crunchbang:~$

I just reinstalled drivers to the newest ones, and as I said - now steam isn't working at all, and alt menu isn't working as it should...

#13 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 16:27:25

Malice

Is there anyone that can help me? I'm having this trouble since yesterday, nothing seems to work, only more things are breaking. Now my alt menu doesn't work properly(it opens programs, but it doesn't list programs nor suggests anything when I input name.

Also, steam isn't working now - it says that I'm missing following 32-bit library:
libGL.so.1

Please help... If you want to contact me directly, I'm logged in on #crunchbang IRC channel, as Malice.

#14 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 16:12:14

Malice

Your command gave this output:

Usage: /etc/init.d/slim {start|stop|restart|force-reload}

So I don't see any error messages.
Other logs:

/var/log/Xorg.0.log | grep WW :

http://pastebin.com/munj6DTA

/var/log/slim.log :

http://pastebin.com/asJCCrZH

I just installed newest NVidia drivers using smxi, but nothing happened...

#15 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 15:10:52

Malice

My slim.conf:
http://pastebin.com/bMYrGkyg

Doesn't look like there's anything wrong.

#16 Re: Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 13:09:19

Malice

Maybe some suggestions what to look for or links, please? I have been looking for solution for an hour and didn't find anything...

PS. This may be caused by gnome - after upgrading to jessie I had openbox and gnome. I removed gnome-session with apt-get, but nothing more.

#17 Help & Support (Crunchbang 11 "Waldorf") » X(openbox?) won't open automatically » 2013-12-23 10:32:19

Malice
Replies: 29

At least that's my guess.
Yesterday I switched from Wheezy to jessie. It turned out that Jessie downloaded gnome and made it default. Yet it would not start - after login screen, when I enter login and password, the "login" window disappears, and nothing else happens.

If I go to tty, login, and type "startx", after a (longer then before) while, everything will load fine. Now, there are two things I would like to change:
1. I would like X(openbox?) to open automatically, so I don't have to type "startx" every time I log in.
2. In the process of switching, my mouse pointer also changed - now it's black, and looks like it's taken from gnome... I would like simple white mouse pointer back.

Output of update-alternatives:

malice@crunchbang:~$ sudo update-alternatives --config x-session-manager
[sudo] password for malice: 
There is 1 choice for the alternative x-session-manager (providing /usr/bin/x-session-manager).

  Selection    Path                      Priority   Status
------------------------------------------------------------
*  0            /usr/bin/openbox-session   40        auto mode
   1            /usr/bin/openbox-session   40        manual mode

And dpkg -l *gnome* gave me this output:

malice@crunchbang:~$ dpkg -l gnome*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  gnome          <none>                    (no description available)
ii  gnome-accessib 3.8.4-1      all          Accessibility themes for the GNOM
ii  gnome-bluetoot 3.8.1-2      amd64        GNOME Bluetooth tools
un  gnome-codec-in <none>                    (no description available)
un  gnome-color-ma <none>                    (no description available)
ii  gnome-contacts 3.8.3-1+b1   amd64        Contacts manager for GNOME
ii  gnome-control- 1:3.8.3-4    amd64        utilities to configure the GNOME 
ii  gnome-control- 1:3.8.3-4    all          configuration applets for GNOME -
ii  gnome-desktop- 2.32.1-2     all          Common files for GNOME desktop ap
ii  gnome-desktop3 3.8.4-2      all          Common files for GNOME desktop ap
un  gnome-games    <none>                    (no description available)
ii  gnome-icon-the 3.10.0-1     all          GNOME Desktop icon theme
ii  gnome-icon-the 3.6.2-3      all          GNOME Desktop icon theme (additio
ii  gnome-icon-the 3.10.1-1     all          GNOME desktop icon theme (symboli
ii  gnome-keyring  3.8.2-2      amd64        GNOME keyring services (daemon an
un  gnome-media-co <none>                    (no description available)
ii  gnome-menus    3.8.0-2      amd64        GNOME implementation of the freed
ii  gnome-mime-dat 2.18.0-1     all          base MIME and Application databas
ii  gnome-online-a 3.8.3-2      amd64        GNOME Online Accounts
un  gnome-orca     <none>                    (no description available)
un  gnome-osd      <none>                    (no description available)
un  gnome-panel    <none>                    (no description available)
un  gnome-phone-ma <none>                    (no description available)
un  gnome-power-ma <none>                    (no description available)
un  gnome-screensa <none>                    (no description available)
un  gnome-session  <none>                    (no description available)
ii  gnome-session- 3.8.4-3      amd64        GNOME Session Manager - Minimal r
ii  gnome-session- 3.8.4-3      all          GNOME Session Manager - common fi
ii  gnome-settings 3.8.5-2      amd64        daemon handling the GNOME session
ii  gnome-shell    3.8.4-5      amd64        graphical shell for the GNOME des
ii  gnome-shell-co 3.8.4-5      all          common files for the GNOME graphi
un  gnome-sudo     <none>                    (no description available)
un  gnome-terminal <none>                    (no description available)
un  gnome-themes-e <none>                    (no description available)
ii  gnome-themes-s 3.8.4-1      amd64        Standard GNOME themes
ii  gnome-themes-s 3.8.4-1      all          Data files for GNOME standard the
un  gnome-tweak-to <none>                    (no description available)
ii  gnome-user-gui 3.8.2-1      all          GNOME user's guide
ii  gnome-user-sha 3.8.3-1      amd64        User level public file sharing vi
un  gnome-utils    <none>                    (no description available)
un  gnome-www-brow <none>                    (no description available)

I would like to get rid of gnome, if it's possible.
If I didn't include some information, feel free to ask.
Thank you in advance.

#18 Help & Support (Crunchbang 11 "Waldorf") » After switching to Jessie from Wheezy, GUI doesn't work. » 2013-12-22 20:25:58

Malice
Replies: 0

Hey,
as in topic subject - I switched from Jessie to Wheezy(by commenting out #! repos and changing all "wheezy" to "jessie".
After reboot, I can't use GUI.
I have 2 different kernels, one will load GUI, but after logging in nothing happens, and in second one GUI won't load.
Any ideas or questions for additional information? It's quite urgent...
If you are willing to help me right now, you can join #! help IRC, I will be here for ~2 hours at least.

Thank you in advance.

#19 Feedback & Suggestions » Good job! » 2013-12-21 18:24:56

Malice
Replies: 6

So I have been using #! for little over 2 months, and I got to say that this is great. The only downside of linux is that many Windows programs(games) don't run on it(at least natively), but otherwise - it's great OS. I really like the simplicity - it's amazing how this system can be elegant and humble at the same time.
Just wanted to say thank you. It's great OS smile

#20 Re: Help & Support (Crunchbang 11 "Waldorf") » Clementine is not working with global hotkeys(play, etc.) » 2013-11-24 11:57:30

Malice

Okay,
guys from IRC helped me with this problem, so I'll post solution:

I edited rc.xml from Openbox. I read clementine's manual to see how can I control it from CLI.
After reading it, I came up with these lines:

    <!-- Keybindings for Media Keys -->
    <keybind key="XF86AudioMute">
      <action name="Execute">
        <command>amixer set Master toggle</command>
      </action>
    </keybind>
    <keybind key="XF86AudioLowerVolume">
      <action name="Execute">
        <command>clementine --volume-down</command>
      </action>
    </keybind>
    <keybind key="XF86AudioRaiseVolume">
      <action name="Execute">
        <command>clementine --volume-up</command>
      </action>
    </keybind>
    
     <keybind key="XF86AudioPlay">
		<action name="Execute">
			<command>clementine -t</command>
		</action>
    </keybind>
    <keybind key="XF86AudioPrev">
      <action name="Execute">
        <command>clementine --previous</command>
      </action>
    </keybind>
    <keybind key="XF86AudioNext">
      <action name="Execute">
        <command>clementine --next</command>
      </action>
    </keybind>

And it works smile Hope it will help someone

#21 Help & Support (Crunchbang 11 "Waldorf") » Clementine is not working with global hotkeys(play, etc.) » 2013-11-22 14:41:22

Malice
Replies: 1

Hello,

I recently installed clementine, and I can not get key shortcuts to work properly.
It's my first installation, keys are not working from the start.
Before Clementine, I used deadbeef, and it captured all of my hotkeys normally.

If I can't get it to work, maybe I could find a way around this problem, like setting hotkey in #! to operate on clementine? If yes, then how?

#22 Re: Introductions » Hello #! » 2013-11-16 20:01:57

Malice

Hey looba! Welcome aboard!:)

As for to-do things:  #! has after-installation setup tutorial(kind of), which will help you install some basic things that  you may want to have. As for your link - keep it as a guide. It isn't mandatory, but it has some nice features you might find useful and want to use.

Enjoy yourself! Hope you enjoy crunchbanging!

#23 Re: Help & Support (Crunchbang 11 "Waldorf") » How to copy folders without their content » 2013-11-03 17:34:01

Malice

Not sure. Figured out how IRC works, so case is solved.

I first made cp -r ~/a/* ~/b
Then, I used rm ~/b/*/*

So effectively, I first copied all folder from one directory to other, and then deleted it's content.  I don't know I could have done it easier, but this solution worked. Anyway, thanks for help!:)

#24 Help & Support (Crunchbang 11 "Waldorf") » How to copy folders without their content » 2013-11-03 17:14:01

Malice
Replies: 5

Hello,
I have 50 folders in ~/x. I want to copy these folders to ~/y, but without their content(so ls would show the same list in both ~/x and ~/y, but files in ~/y are empty).
I looked in man and --help, but I can't find the answer.
Thanks in advance!

#25 Re: Introductions » what does the fox love??? » 2013-11-03 15:08:27

Malice

Hello and welcome! Hope you have a good time smile

Pages: 1 2

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo