Kubuntu 13.04 Raring Ringtail

[wakeup]

I am currently translating documents into Turkish.

When I follow the link Help Translate on Launchpad, it suggested me translating oneiric templates. I almost complete translations, but today I saw another translations of kubuntu-docs on Raring trunk list.

Should I continue the translation with oneiric (https://translations.launchpad.net/k...eiric/+lang/tr) or did I waste my time by not translating Raring files (https://translations.launchpad.net/u...50&start=150)? Because I cannot see my old translations in Raring files.

[oshunluvr]

Yeah, I think it popped up around mid-dec. I can still get the Dec 5 iso. What was the date on yours? If you still have it around....

[dequire]

12/17/2012

Yeah, I think it popped up around mid-dec. I can still get the Dec 5 iso. What was the date on yours? If you still have it around....

[Jose Manuel]

Dear: I would like had more prominence and more publicity for Kubuntu in this wonderful world of Linux. Would be possible for to get a little publicity for the next release of Kubuntu 13.04 its make for inserting a regressive countdowns (counters) on websites or forums, if not too much to ask ..... I'll make the same suggestion in the Spanish part of the forum to see if someone is on the idea. I clarify that I do not know how, but would be good to have more advertising how they do Ubuntu or Fedora.....Best regards.-

[wakeup]

Hello,

I already reported this as a bug, but did not get any answers, so I would like to post here as well:

I have Samsung NP300V5A with Windows 7 installed. I wanted to install Kubuntu alongside Windows 7, but noticed that Ubiquity does not see my Windows installation and would like to install itself into my all disk (Please see screenshot here http://s3.postimage.org/yr10wn25t/IM...207_203301.jpg).

The suggestion was disabling UEFI in BIOS, but this was already disabled. I also created a partition for Kubuntu (approx. 20gb), but this also did not solve the problem.

I asked on kubuntu-devel mailing list, but would like to report is as a bug to be checked.
I asked to askubuntu.com and got a reply to install Ubuntu and then installing Kubuntu desktop, or using WUBI. But maybe this is a hardware problem.

Last week, I tried the same thing with Ubuntu and ... It saw my Windows 7 installation and asked me if I would like to install it alongide...

I also tested this Alpha 2, but it still did not work.

If you change anything, I can help you with the testing...

Bug link here: https://bugs.launchpad.net/ubuntu/+s...y/+bug/1126525

[unheeding]

Yes, currently the maximum grace period seems to be 5 minutes, but I meant setting a longer time in screen saver activation (which effectively delays the locking by the same time [if you set the activation time to 20 minutes the screen will lock after 20+ minutes of inactivity]...or alternatively disable automatic activation of screen saver altogether, which then doesn't lock the screen at all)...this is just a workaround waiting it to be fixed, of course, not a permanent solution.

You can also blank screen with xset (this is actually what I do on one of machines that I don't need to lock based on activity...I've never been a fan of "screensavers"). On this setup, I have disabled automatic activation of screen saver in systemsettings, and use xset to set screen blanking in 10 minutes (you can also use xset to control DPMS settings, that is monitor standby,suspend or off at designated time intervals)...this machine blanks the screen nicely after 10 minutes and doesn't lock the screen.

Kscreenlocker is bugged since it doesn't work as expected in this regard, but I'm sure it will get fixed eventually. Kscreenlocker is new and regressions are fairly common in new software (especially pre-release software).

Has this bug been reported? If so, I would like to +1 myself to this as it's a rather important bug.

[unheeding]

Here's my workaround:

Install xscreensaver

sudo apt-get install xscreensaver

Move kscreenlocker_greet

sudo mv /usr/lib/kde4/libexec/kscreenlocker_greet  /usr/lib/kde4/libexec/kscreenlocker_greet.old
sudo nano /usr/lib/kde4/libexec/kscreenlocker_greet

Create a replacement file with this inside of it:

#!/bin/sh
xscreensaver-command -lock

Make it executable:

sudo chmod +x /usr/lib/kde4/libexec/kscreenlocker_greet

Test it by clicking the Kicker/K-Menu and locking screen, it should bring up xscreensaver's lock screen.

Change xscreensaver settings with:

xscreensaver-demo

I prefer to have blank screen only.

I'm going to test sleeping/locking when i submit this post, expect an edit!

Edit: works! Little glitchy, but I think that's because KWin is applying effects to xscreensaver. I'll see if I can disable that.

[kubicle]

Has this bug been reported? If so, I would like to +1 myself to this as it's a rather important bug.

Didn't check the source to confirm, but the issues seems fixed (I'm on KDE 4.10.1)...after a quick test, the screen doesn't lock if "require password" is un-ticked. I can check the source or run more tests if you're still experiencing the issue (in 4.10.1).

The Lock grace period maximum is still 5 minutes (this makes sense in the way that people that *do* want to lock their screen usually want to do it fairly quickly after the screenlocker activates...I'm not a big fan of hard-coded limits, but I can understand why this in place).

[unheeding]

Didn't check the source to confirm, but the issues seems fixed (I'm on KDE 4.10.1)...after a quick test, the screen doesn't lock if "require password" is un-ticked. I can check the source or run more tests if you're still experiencing the issue (in 4.10.1).

The Lock grace period maximum is still 5 minutes (this makes sense in the way that people that *do* want to lock their screen usually want to do it fairly quickly after the screenlocker activates...I'm not a big fan of hard-coded limits, but I can understand why this in place).

Oh, I'm experiencing a different issue then. The lock screen is just black, with no way to unlock the screen (even typing the password and hitting enter does nothing). Hence I replaced it with xscreensaver....

[kubicle]

Oh, I'm experiencing a different issue then. The lock screen is just black, with no way to unlock the screen (even typing the password and hitting enter does nothing). Hence I replaced it with xscreensaver....

Yes, that's a different bug :P ...screen locker works okay here, but you can search bugs.kde.org if anyone has reported your bug.

EDIT:
quick check, do you have these installed?:
kscreensaver
kde-workspace-bin
kde-workspace-data
kde-workspace-kgreet-plugins

[unheeding]

Yes, that's a different bug :P ...screen locker works okay here, but you can search bugs.kde.org if anyone has reported your bug.

EDIT:
quick check, do you have these installed?:
kscreensaver
kde-workspace-bin
kde-workspace-data
kde-workspace-kgreet-plugins

I attempted to install all, kscreensaver wasn't installed but I installed it and it pulled in some other packages. I think the problem is that Simple Locker is broken, I've attached my name to a bug. This bug to be exact. Using Desktop Widgets as the screen locker works as expected, plus it's kind of pretty. So ignore my workaround above, it's not really necessary (plus it logged me out after I put it to sleep last time!)

[kubicle]

I think the problem is that Simple Locker is broken

The simple locker works here, and the screensaver locker...could still be a valid bug, but my setup seems to be unaffected (so it's probably not a universal bug)

[caryb]

I have a issue in 4.10 where I cant add a script or a program in the Autostart (System settings -> Statup and shutdown -> Autostart) there is no apply button & if you navigate away the application added disapears. Am I on my own with this or should I report a bug?


Cary

BTW OS = Kubuntu 13.04 64bit current

[claydoh]

No problem here, there is no "apply" button, but one apparently is not needed. Maybe check permissions on your ~/.config/autostart folder? Perhaps it can't be written to for some reason.

[STiAT]

Well, installing from scratch on UEFI hardware did work pretty fine for me.

One thing I noticed, I managed to initially screw up my manual partition setup (I did forget to set the EFI partition), and the installer recognized that, but instead of that toe "go back" button actually taking me back, he continued the installation - and threw a few more errors. Maybe worth fixing.