Welcome, Guest. Please login or register.
April 21, 2014, 01:40:25 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

  Show Posts
Pages: 1 [2] 3
16  Assistance / Configuring Pardus / Re: Pardus 2011 Customizing guide on: March 16, 2011, 02:01:29 AM
One of the things I found most confusing when suing Linux for the first time was the Plasma toolbox. I couldn't figure out the difference between panels, plasmoids, folder views, activities, etc. Here is a good visual tutorial from kde.org http://userbase.kde.org/Plasma

And for KDE in general:
http://linux.about.com/od/linux101/a/desktop14.htm .

And for Linux in general:
17  Assistance / Pardus for beginners / Re: Pardus review that needs your attention!! on: March 09, 2011, 02:59:23 AM
I don't know why he thinks Pardus needs 1G of ram. I left a comment saying that Pardus runs fine on my machine, which is 5 years old with only 1G. I can run several large programmes along with the OS, which would not be possible if the OS itself required 1G. I had plenty of memory issues with Vista on this machine, but not with Pardus.

He did repeatedly point out that Pardus looks very professional. I found Pardus 2011 to be disappointing after using Pardus 2009. The grey splash screens just don't show off the graphics capablilites the way 2009's beautifull reds do. Red is not my favourite colour, but Pardus reds are beautifull.
18  Assistance / Installing Pardus / Re: 2011 won't install on: February 08, 2011, 14:24:21 PM
I had a similar problem.  I successfully booted Yali from a usb stick and was in the middle of entering new partioning information when the screen suddenly shrank to 1/4 of the screen, then disappeared entirely leaving me with a blinking cursor and no system prompt. I rebooted into my hard drive and searched for the errormessage:  [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6]

I found a thread in an ArchLinux forum suggesting it may be related to the nouveau driver for the NVIDIA card, and remembered this discussion here in this thread. I tried setting xorg=safe, which didn't work, and then just used the failsafe option in the display options at the boot screen.

This caused Yali to blacklist the nouveau driver and offer me the proprietary driver a few screens later, I now have Pardus 2011 successfully installed on my machine.
19  General / General topics / Re: Another Review From LinuxBSDos on: January 30, 2011, 03:36:33 AM
Thanks for the answers, guys. I was a little unclear about whether Pardus 2011 requires LVM, and if so, how could 2009 update to 2011 with the new partitioning scheme. Further reading shows it is just an option, not a requirement. It looks like LVM has a lot of advantages; so, I'm thinking of using it anyway.
20  General / General topics / Another Review From LinuxBSDos on: January 27, 2011, 02:48:52 AM

There are several other LinuxBSDos Pardus reviews already mentioned in this forum. This one is for the personal version of Pardus 2011.

I find "glowing reviews" to be worthless. I want to be warned about possible pitfalls before I start the install. This review notes that Yali recovers nicely from possible crashes, and gives a link to instructions on LVM partitioning.

I know a fair amount about partitioning from my DOS days, when you had to figure out the partition parameters by doing the math yourself. (I've forgotten most of it due to lack of use)  But I don't know anything about LVM. The accompanying article gives me the confidence to go ahead and try it.

Does this mean that Pardus 2011 should be a fresh install and not just an update from within Pardus 2009.2? I've already created a bunch of standard partitions using whatever Mandiva 2009 had in its GUI based installer. Is it possible to install Pardus 2011 to one of these if I find problems with LVM?
21  Assistance / Pardus for beginners / My login manager is lying to me. (solved) on: January 19, 2011, 23:29:43 PM
A recent kernel upgrade solved this issue. I still don't know what happened; but, at least it's resolved.
22  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 09, 2010, 00:31:49 AM
Thank you for your heroic attempts to resolve this issue. I really did not expect anyone would go to such lengths to resolve a relatively unimportant issue.

However, I have learned a lot during this process. So, it has been usefull for me.
23  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 08, 2010, 23:27:47 PM
No luck.  My new user is the only account that can log in at the graphical login screen and shutdown or reboot from the desktop.
My root and original user can only log out from the desktop. There is a small difference between the two: root can interact with the logout notification screen, i.e. cancel logout if I choose. But original user cannot. I doubt that has any significance here.

There is an errormessage when I am logged out to konsole after choosing reboot at the desktop in root account. It says kde4 is crashing:

failed to conncet  /tmp/dbus-8wuKqv6UPt  connection refused
KUniqueApplication:Pipeclosed unexpectedly
Socket Notifier:Invalid socket 15 and type 'Read' disabling
Konqi: cannot connect to Xserver :0.0

I'm guessing that's because I set Pardus to clean out my /tmp directory on closing, as per your previous advice to tame my runaway /tmp directory.
24  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 08, 2010, 21:28:15 PM
Yes, there is. Here is the screenshot:

25  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 07, 2010, 03:06:36 AM
No luck. I followed the instructions in the HOWTO and still have the login/shutdown problems in the new account named after the old user. I gave him full privileges, as instructed. I opened Login Manager and unchecked and rechecked all the options I want but Pardus still ignores them during bootup.
26  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 06, 2010, 22:34:16 PM
Thank you dwight.

My desktop has been restored after my disaster this weekend. The issue now is: my user account no longer has the ability to login at the graphical login screen; and it no longer has the ability to shutdown or reboot from the desktop. I can login from the konsole and I can logout to the konsole and shutdown from there. I have made appropriate choices in the Login Manager in System Settings, and have checked the configuration files to ensure that those choices were saved properly. They are; but, Pardus for some reason does not recognize that those changes were made, and does not let my user boot in from the graphical login screen. I created a new user account; and this account is able to login and shutdown via the gui and desktop. So, it looks like a privileges issue of some kind.
27  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 06, 2010, 21:57:21 PM
You are right. I took a screenshot to show what I mean.
28  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 06, 2010, 20:39:44 PM
Thank you for the HOWTO.  Grin It looks like something that should go into the Pardus Wiki. Before trying this, I am making a full backup of my home directory. This will take a while; so, I will try your advice later today and report back.

When I said " put him in root group, too?" I meant choose "Main Group: root" instead of "Main group: users." According to this HOWTO which you have given me, I don't need to put him in Main group: root; so, I won't.
29  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 06, 2010, 00:41:45 AM
So far I was not successful in destroying permanently my KDE desktop.

Ctrl Alt Esc
Ctrl+Alt+Esc and
Alt SysReq R E
Alt+SysReq+R+E Huh?
(+ = simultaneously)

Yes to both.

It was the Ctrl+Alt+Esc that killed the desktop. If used properly, it will kill a programme that has frozen. If you miss the programmes's window and hit the desktop, you will kill your desktop. But it should not be permanent. If you reboot, you should see your desktop as normal. See this article in Wiki: http://en.pardus-wiki.org/Kill Look at section XKill.

As I mentioned earlier, I'm guessing that my full /tmp directory prevented X from creating temporary files needed while creating the screen. This is just a guess; because, I regained the desktop after cleaning out the /tmp directory.

The Alt+SysReq+R+E combination will stop all processes, unmount file systesm, and give you a usable system prompt. See Wikipedia article "Magic SysReq key" http://en.wikipedia.org/wiki/REISUB  I used this because Ctrl-Alt-Del would not reboot the computer.

I used this before when a bug in Mandriva crashed me to a minimal desktop with no access to a system prompt.

And after creating a new user in System Settings > User Manager (with all rights).
Does the new user has the same problems?

No, my new user does not have the login and shutdown problems  Grin . I gave him administrator privileges and put him in root group. However, when I logged back in as old user, my mouse was frozen. I just unplugged and replugged it back in.

So, maybe I need to give my old user adminstrative privileges and put him in root group, too?  I'm not too clear on the difference between adminstrator and root. This is a home computer with no children in the house so no need to worry about in house security.

30  Assistance / Pardus for beginners / Re: My login manager is lying to me. on: August 05, 2010, 19:51:48 PM

Destroying (part of) your KDE Desktop has nothing to do with  X session.

So, I'm guessing the desktop couldn't be generated because X was unable to create temporary files because root partition was full?

..... I no longer have Shutdown and Reboot options available as user
Have a look in System Settings > Advanced > Login Manager > Shutdown > Local: Everybody Huh?
And do not forget the Apply button.
But these settings are only applied after you have activated the button "Apply".

...........Autologin appears to be enabled. However, nothing has changed during the bootin process. I still get the login screen and have to login at the console.
Try the (above) button "Apply".

Yes, I had activated the "Apply" button. However, to doublecheck, I just now opened login manager again, unchecked "everybody", checked "root", activated "apply" and "OK". This did not change anything. I still had only "logout" available, and it did not ask for root password. So, I rebooted, logged back in as user, and checked again. Same result - only logout is available.

As mentioned in my previous post, I did check the configuration files kdmrc to verify that changes made in Login Manager are being saved to the configuration files. They are, but the bootin process is ignoring them.

Maybe I should try to make a small batch file to automate login from the console and forget about trying to solve this. It's only a minor irritation.
Pages: 1 [2] 3

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!