Re: LXQt suspend not working
Posted: 11 Feb 2015, 12:12
You really have an irreverent style. Don't you? 8)
I would refer to it as being honest and direct. Though I have been criticized for being blunt at times. I try to add humor, like the beer cans comment.francois wrote:You really have an irreverent style. Don't you? 8)
Ok but there needs to be a way for non-mods to flag a thread for admin review. Maybe AAP (Admin Attention Please) would do.brokenman wrote:Here it is officially. Moderators and ONLY moderators should mark threads as FAA. That is what we requested them to do. That is the work flow we have chosen.
Ok but then you will have to have fanthom change his sig line because users won't be able to add {Solved} to their threads either. Regardless users can still PM and Email admins to get their attention when needed.If users begin marking their own threads FAA when they feel like it we will remove the ability to edit threads. Enough said.
No there doesn't. This is why we have moderators. We are handing the forum to the community which means experienced users will answer questions. If the problem can not be resolved then moderators will mark it as FAA and we will pick it up. This is the system we have chosen in order to better utilize time. Sorry if this is not convenient for you but it is the best we can do right now.Ok but there needs to be a way for non-mods to flag a thread for admin review.
hmmmm Yeah, I don't think I qualify as an "advanced linux user". I barely qualify as a beginner linux user.brokenman wrote:This is only for advanced linux users.
An impressive link, very detailed. And scary:brokenman wrote:There is documentation on the website.
http://www.porteus.org/tutorials/20-dev ... ernel.html
I not sure I understand. (nothing new) Slackware 14.1 according to this link: http://www.slackware.com/announce/14.1.php uses the 3.10.17 kernel. Porteus 3.1 is using the 3.17.x kernel so it didn't come from Slackware 14.1, again according to my understanding of what I have read. Could there be a kernel update to Porteus without doing a whole new release? A 000-kernel_alldesktops-15mmdd.xzm module that includes kernel 3.18? Or 3.19? Or a mini Porteus 3.1.1 update release like 3.0.1 was?fanthom wrote:Porteus release (4th one) based on Slackware-14.1.
Understood. And rather surprised no one else has encounter this.fanthom wrote:c) i'm not going to prepare new kernels when single user has an issue.