[kcron] [Bug 367782] kcron will only accept "/" as 1st character

2016-08-24 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367782

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com
Summary|kcron will only accept  |kcron will only accept "/"
   |other than "/" to start |as 1st character

-- 
You are receiving this mail because:
You are watching all bug changes.


[kcron] [Bug 367782] New: kcron will only accept other than "/" to start

2016-08-24 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367782

Bug ID: 367782
   Summary: kcron will only accept other than "/" to start
   Product: kcron
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: g...@meyer.net
  Reporter: s093x...@rogers.com

The version number of my task scheduler is 5.0

I have a number of gui apps that I use in Kcron. In the past I have written
entries in my personal kcron as "export DISPLAY=:0 && app_name"

Due to a persistent bug in neon, I reinstalled the os and went to redo my gui
apps. It didn't work.

I tried "export DISPLAY=:0 && app_name" but the OK button remained greyed out.

The only thing that worked was putting /home as the first item and entering
"/home/. . ./bin/app_name --display :0"

The OK button was not greyed out but the app would not run.

I used "crontab -u user -e" and manually inserted the export DISPLAY=:0 && in
each of the lines. Closing the app updated cron and systemsettings showed the
updated information. As a check I Modifyied one of the lines but the OK button
remained greyed out. I had to Cancel.

I cannot reproduce this but one of my entries came up as
"/home/... export DISPLAY=:0 && /home/.../bin/app_name"
As I say I don't know how this instance happened.


Reproducible: Always

Steps to Reproduce:
1. insert export DISPLAY=:0 && before an app name in personal (and others ?)
cron in SystemSettings
2.
3.

Actual Results:  
OK button is greyed out until a "/" is entered first

Expected Results:  
Kcron should accept a none "/" starting character

The modified entries do not run when "Run Now" is clicked. They do though run
as scheduled cron jobs which I am extremely happy about.

Hope this helps.

Thank You

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-23 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

--- Comment #6 from pmb  ---
Sorry to bother you again but I have a printout that is unusual from this
issue.

I have a Bash script that is named UpDateAll. It updates and downloads and
cleans up. It has run perfectly for years and years. Now it doesn't. The
executable checkbox is marked but it will not run by itself. I must put ./ in
front.

Then it runs strangely!

It seems to open the icon as a text file with the click or Enter and when it
gets to the script itself it runs the Bash Script and continues after the
script treating the icon as a text document.

The following shows the results.

???@TheMacHine:~/Desktop/???$ sudo ./UpDateAll
[sudo] password for???: 
./UpDateAll: 1: ./UpDateAll: [Desktop: not found
./UpDateAll: 2: ./UpDateAll: Comment[en_GB]=: not found
Update:
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Hit:2 http://archive.canonical.com/ubuntu xenial InRelease  
Get:3 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease
[23.8 kB]
Hit:4 http://ca.archive.ubuntu.com/ubuntu xenial InRelease  
Get:5 http://ca.archive.ubuntu.com/ubuntu xenial-updates InRelease [95.7 kB]
Hit:6 http://ppa.launchpad.net/byobu/ppa/ubuntu xenial InRelease
Ign:3 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease
Hit:7 http://ppa.launchpad.net/gambas-team/gambas3/ubuntu xenial InRelease  
Hit:8 http://ppa.launchpad.net/mc3man/avidemux1/ubuntu xenial InRelease 
Hit:9 http://ca.archive.ubuntu.com/ubuntu xenial-backports InRelease 
Hit:10 http://ppa.launchpad.net/numix/ppa/ubuntu xenial InRelease
Hit:11 http://archive.neon.kde.org/user xenial InRelease
Fetched 214 kB in 5s (41.6 kB/s)
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial
InRelease: The following signatures couldn't be verified because the public key
is not available: NO_PUBKEY 2836CB0A8AC93F7A
W: The repository 'http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial
InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
Upgrade:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Auto-remove:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Clean:
Auto-clean:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
No kernels are eligible for removal

 Finished now . . .

./UpDateAll: 5: ./UpDateAll: GenericName[en_GB]=: not found
./UpDateAll: 9: ./UpDateAll: Name[en_GB]=UpDate: not found
./UpDateAll: 10: ./UpDateAll: All: not found
./UpDateAll: 16: ./UpDateAll: X-DBUS-ServiceName=: not found
./UpDateAll: 17: ./UpDateAll: X-DBUS-StartupType=wait: not found
./UpDateAll: 18: ./UpDateAll: X-KDE-SubstituteUID=false: not found
./UpDateAll: 19: ./UpDateAll: X-KDE-Username=root: not found

Hope this helps. This mess continued from a previous install to a new formatted
install.

Hope this helps

Thank You

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-23 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

--- Comment #4 from pmb  ---
Created attachment 100729
  --> https://bugs.kde.org/attachment.cgi?id=100729=edit
inxi folderview icon

I removed the path and substituted an ellipsis.

Hope this helps

Thank You

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-23 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

--- Comment #5 from pmb  ---
This icon is one of many that do not function properly.

It appears to be a problem with a desktop icon that opens a terminal. The
script itself runs perfectly when run directly with ./ in front. Without that
./ I get command not found even with executable mode set. It could be a Konsole
problem.

I heard nothing earlier so I reinstalled 5.7.3. There were 500+ updates. Before
the updates, the icons worked perfectly. After the problems started. I have
tried at my pay grade to diagnose the problem but it is somewhere in the back
end and far above my knowledge level.

Hope this helps

Thank You

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-22 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-22 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

--- Comment #2 from pmb  ---
Haven't heard anything so I gave up and installed a clonezilla backup from
14Aug16. One week before the issues raised by this bug report.

I tried the offending icons and ALL opened properly, opening in a terminal and
running the script.

I hoped that my problems were a one time thing so I did a full-upgrade of 313
packages.

Guess what?

The problem now exists again.

Somewhere in those packages is something screwing up my desktop.

I have tried moving an icon to another computer - it works
I have tried moving an icon to another user on the same machine - does not work
I reinstalled the plasma-desktop-* packages - no effect

Unless someone at your end can solve my problems then a complete reinstall is
the only solution.

Please help?

Thank You

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-19 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

--- Comment #1 from pmb  ---
A correction . . .

It seems that none of my icons pointing to a script or using a terminal work.

I click - they die!

I tried recreating the offending icons but they do not work.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 367582] New: 19Aug16 Updates (131) Crash Desktop Icon/Scripts

2016-08-19 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367582

Bug ID: 367582
   Summary: 19Aug16 Updates (131) Crash Desktop Icon/Scripts
   Product: plasmashell
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: s093x...@rogers.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Desktop Icon script which has run perfectly for years - today after 131 file
updates - problems

Clicked icon to run Bash script in Dolphin and also desktop icon - nothing -
dies

open terminal from Dolphin - ls directory - highlight "_UpDate_et_al" - copy -
paste into terminal - run "sudo _UpDate_et_al" - Result
"_UpDate_et_al: command not found" - executable checked - permissions have not
changed - all OK

Run sudo ./_UpDate_et_al - Result
[sudo] password for ???: 
./_UpDate_et_al: 1: ./_UpDate_et_al: [Desktop: not found
./_UpDate_et_al: 2: ./_UpDate_et_al: Comment[en_GB]=: not found
Update:
. . .
Bash script runs
. . .
./_UpDate_et_al: 5: ./_UpDate_et_al: GenericName[en_GB]=: not found
./_UpDate_et_al: 9: ./_UpDate_et_al: Name[en_GB]=: not found
./_UpDate_et_al: 16: ./_UpDate_et_al: X-DBUS-ServiceName=: not found
./_UpDate_et_al: 17: ./_UpDate_et_al: X-DBUS-StartupType=: not found
./_UpDate_et_al: 18: ./_UpDate_et_al: X-KDE-SubstituteUID=false: not found
./_UpDate_et_al: 19: ./_UpDate_et_al: X-KDE-Username=root: not found

tried another Desktop icon Bash script - copy from ls - paste in terminal

???@???:~/Desktop//???$ "Clean Up"
Clean Up: command not found
???@???:~/Desktop//???$ ./"Clean Up"
./Clean Up: line 1: [Desktop: command not found
./Clean Up: line 12: Up: command not found
./Clean Up: line 13: Up: command not found
./Clean Up: line 14: Up: command not found
./Clean Up: line 23: X-DBUS-ServiceName=: command not found
./Clean Up: line 24: X-DBUS-StartupType=none: command not found
./Clean Up: line 25: X-DCOP-ServiceType=: command not found
./Clean Up: line 26: X-KDE-SubstituteUID=false: command not found
./Clean Up: line 27: X-KDE-Username=: command not found

renamed "Clean Up" as Clean_Up and then CleanUp - identical results

Was running good yesterday - used _UpDate_et_al to download 131 updates today -
few minutes later Discover advises one more update - tried to run same icon
script could not.

Tried a few icons in gui - inxi runs OK


Reproducible: Always

Steps to Reproduce:
1. run desktop icon holding Bash script
2. will not run
3.

Actual Results:  
Crash info in terminal

Expected Results:  
Bash script should run like it has for years

I apologise if this is in the wrong pigeon hole - about my pay grade - please
forward this report to the correct department.

The crash is for the icons that crash - plasma itself appears to work as before
- if that sounds OK

If you need anything else - please contact me

Hope this helps

-- 
You are receiving this mail because:
You are watching all bug changes.


[Discover] [Bug 366536] Updater says packages available - discover reports up to date

2016-08-08 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366536

--- Comment #2 from pmb  ---
Yes
My updater script uses
apt-get update
apt-get -y --force-yes dist-upgrade
apt-get -y --force-yes autoremove
apt-get clean
apt-get autoclean
then
/var/run/reboot-required (if required)

I have used it for years without any problems.

Hope this didn't screw you/me up?

Thanx

-- 
You are receiving this mail because:
You are watching all bug changes.


[Discover] [Bug 366536] New: Updater says packages available - discover reports up to date

2016-08-08 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366536

Bug ID: 366536
   Summary: Updater says packages available - discover reports up
to date
   Product: Discover
   Version: 5.7.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: s093x...@rogers.com

I am using neon 5.7.3 which is up to date.

An icon in the system tray advises me that 13 updates plus 1 security update
are available.

Discover appears after clicking icon and reports, system up to date - no
further activity

Using my update script I download 13 plus packages.

I cannot find a report about this issue, one or two close but nothing exact.


Reproducible: Always

Steps to Reproduce:
1. Click system tray update available icon when updates become available
2.
3.

Actual Results:  
Discover reports that my system is up to date

Expected Results:  
Discover should display the updates and allow me to download

One of the close reporters mentioned that they tried Muon and it worked. I have
not done that but I will try it next time and report back. My updater script
and Muon should be spot on. They both worked in the past.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 366306] New: Click App Close activates Icon under the Close Button

2016-07-31 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366306

Bug ID: 366306
   Summary: Click App Close activates Icon under the Close Button
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: s093x...@rogers.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I am using KDE neon 5.7.2 which is up-to-date. The desktop theme is the
default, Breeze. The icons are kumic-circle.

A reminder app shows frequently on my desktop. The Close button is directly
over an icon on the desktop. When I click the Close button, the underlying icon
is usually activated and the associated app starts.


Reproducible: Sometimes

Steps to Reproduce:
1. Close an app with Close button over a desktop icon and do the click slowly
2.
3.

Actual Results:  
Clicking the Close button activates the desktop icon which is under it

Expected Results:  
The opened app should close with no other desktop activity

OK, I think I know what is going on but I don't understand why it happens.

If I click to Close an open app and the click is not quick enough then the
click is 'carried' over to the desktop icon. I tried keeping the rodent button
down after a click but the underlying icon is highlighted but not activated. If
I click quickly then the desktop icon is unaffected. If I click longer then the
desktop icon is activated.

I tried this on a few open apps and different desktop icons and it shows the
same results.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365950] Neon 5.7.2 - Desktop icons stay highlighted

2016-07-21 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365950

pmb  changed:

   What|Removed |Added

Product|plasma4 |plasmashell
   Target Milestone|--- |1.0
  Component|desktop |Desktop Containment
Version|unspecified |5.7.2

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 365950] Neon 5.7.2 - Desktop icons stay highlighted

2016-07-21 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365950

--- Comment #2 from pmb  ---
Created attachment 100238
  --> https://bugs.kde.org/attachment.cgi?id=100238=edit
graphic of icon after closing app

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 365950] Neon 5.7.2 - Desktop icons stay highlighted

2016-07-21 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365950

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com

--- Comment #1 from pmb  ---
Created attachment 100237
  --> https://bugs.kde.org/attachment.cgi?id=100237=edit
graphic of icon during app running

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 365950] New: Neon 5.7.2 - Desktop icons stay highlighted

2016-07-21 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365950

Bug ID: 365950
   Summary: Neon 5.7.2 - Desktop icons stay highlighted
   Product: plasma4
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: desktop
  Assignee: plasma-b...@kde.org
  Reporter: s093x...@rogers.com

First - transfer this where ever you choose - I don't know the correct area.
Thank You
And also this report's area maybe Plasma5

Clicking an icon on the desktop starts a program and simultaneously changes the
icon to an activated icon. This action has not changed except now the
background colour changes also. Personally, I don't like that but just ignore
that comment.

Also the changed desktop icon does not revert back to a 'normal' icon until
another icon on the desktop is clicked. The closing of the started app has no
effect on the modified icon. Opening a desktop folder and clicking an icon does
not in anyway affect the modified desktop icon.

If this action is intentional on behalf of KDE then end this bug report.

I apologise, I do not know the correct terminology.


Reproducible: Always

Steps to Reproduce:
1. Click on a desktop icon
2. Close the resultant app or open a desktop folder icon
3

Actual Results:  
The icon remains highlighted long after the icon's opening and closing action

Expected Results:  
Closing the associated app should return the highlighted desktop icon to
'normal'

My workaround is to click any open space on the desktop and all icons return to
'normal'

Hope this helps.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 365446] Desktop settings widget vibrates forcefully at bottom left of screen

2016-07-11 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365446

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com

--- Comment #1 from pmb  ---
Created attachment 100027
  --> https://bugs.kde.org/attachment.cgi?id=100027=edit
avi video of bouncing desktop widget

The widget is that 'thing' that starts off at the top left of the screen - I
don't know what it is called.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 365446] New: Desktop settings widget vibrates forcefully at bottom left of screen

2016-07-11 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365446

Bug ID: 365446
   Summary: Desktop settings widget vibrates forcefully at bottom
left of screen
   Product: plasma4
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: desktop
  Assignee: plasma-b...@kde.org
  Reporter: s093x...@rogers.com

I moved the desktop widget (little rectangular icon for settings) from the top
left to the bottom right above the Menu button.

Started to bounce around like it was in an endless loop - didn't stop till I
moved it

see attached video

Reproducible: Always

Steps to Reproduce:
1. Move the desktop widget from the top left to bottom left above menu button
2.
3.

Actual Results:  
Widget starts bouncing around quickly

Expected Results:  
should have just stayed there

I have Neon 5.7.0 on a separate removable hard drive - not on this machine - I
need time to exchange drives it you want more information

-- 
You are receiving this mail because:
You are watching all bug changes.


[dolphin] [Bug 365444] "The process for the file protocol died unexpectedly" during root operation

2016-07-11 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365444

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com

--- Comment #1 from pmb  ---
I am using KDE Neon 5.7.0 downloaded within the past few days - two downloads

I am using Dolphin 16.04.2

-- 
You are receiving this mail because:
You are watching all bug changes.


[dolphin] [Bug 365444] New: "The process for the file protocol died unexpectedly" during root operation

2016-07-11 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365444

Bug ID: 365444
   Summary: "The process for the file protocol died unexpectedly"
during root operation
   Product: dolphin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: s093x...@rogers.com

Dolphin as user works well

Dolphin as root does not - as soon as it is opened the above message displays

kdesudo kwrite / kate / konsole as generate the error message

If I logout then back in again by chance (?) the first try of kdesudo dolphin
does not get the message.

Reproducible: Always

Steps to Reproduce:
1. start su dolphin as kdesudo dolphin or sudo dolphin from konsole or icon
2.
3.

Actual Results:  
above message displays - no further activity possible

Expected Results:  
no message

this is about the 4th or 5th time that I have installed Neon 5.7.0 - all
problems - consistently not shutting down at shutdown - no icons in root
dolphin (solved) - this error message

I must access root to modify one of the root text files

Anyone know what is causing it?

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365213] Installed/reinstalled cron but not found in system settings

2016-07-08 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365213

--- Comment #5 from pmb  ---
Harold Sitter - Thank You for the reply

I was looking in the right place in systemsettings.

What I did not do was load kcron with cron. I suppose that the other way around
would have worked. Load kcron and cron is loaded also.

Live and learn.

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365212] Neon 5.7 - Shutdown fails - hangs

2016-07-08 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365212

--- Comment #2 from pmb  ---
Harald Sitter  - Thank You for the reply

The power down happened quite a few times over several hours and Yes I did wait
longer than 5 minutes. Actually I made a cup of tea during the interval. I
wanted to make sure that the post hard drive activity was stopped for sure.

I followed your link and the techie information is above my pay grade but I
will try to muddle through it.

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365213] Installed/reinstalled cron but not found in system settings

2016-07-08 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365213

--- Comment #3 from pmb  ---
 Burkhard Lueck - Thank You for the reply

The reply is
"???@???:~$ kcmshell5 kcm_cron
kcron: Error when executing command "crontab -l > /tmp/kcmshell5.TJ2313" 

kcron: Standard output : "" 

kcron: Standard error : "no crontab for ???\n" 

kcron: Setup actions 

kcron: Actions initialized 

kcron: Begin view refresh 

kcron: Creating Tasks list... 

kcron: Generic list created 

kcron: Tasks list created 

kcron: Generic list created 

kcron: Variables list created 

kcron: Enabling view... 

kcron: Clipboard Status  false 

kcron: Change selection... 

kcron: Crontab Widget initialized 

kcron: Calling load"

Harald Sitter  - Thank You for the reply

Yes, my fault, I missed the 'k'. The kcron package was is an old version of
KDE. Cron is the underlying app while kcron is the frontend (I think, maybe).
Both were installed(?).

Hope this helps

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365213] New: Installed/reinstalled cron but not found in system settings

2016-07-07 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365213

Bug ID: 365213
   Summary: Installed/reinstalled cron but not found in system
settings
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: stable packaging
  Assignee: neon-b...@kde.org
  Reporter: s093x...@rogers.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

Just downloaded Neon 5.7 today and installed. Installed all updates.

Downloaded from the repositories cron. Went to system settings looked inside
'StartUp / ShutDown' - no cron.

Searched - app highlighted 'StartUp / ShutDown' but no cron.

I reinstalled cron and again no cron.

The reinstall has some errors that I cannot understand but here is the text,

"The following packages will be REINSTALLED:
  cron 
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0 B/68.4 kB of archives. After unpacking 0 B will be used.
(Reading database ... 186076 files and directories currently installed.)
Preparing to unpack .../cron_3.0pl1-128ubuntu2_amd64.deb ...
Unpacking cron (3.0pl1-128ubuntu2) over (3.0pl1-128ubuntu2) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up cron (3.0pl1-128ubuntu2) ...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match cron
Default-Stop values (none)"

Hope this helps.



Reproducible: Always

Steps to Reproduce:
1. Install cron from repositories
2. open system settings
3.

Actual Results:  
No cron in StartUp / Shutdown


Expected Results:  
A panel entry should display cron for setup

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365212] Neon 5.7 - Shutdown fails - hangs

2016-07-07 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365212

pmb  changed:

   What|Removed |Added

 CC||s093x...@rogers.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 365212] New: Neon 5.7 - Shutdown fails - hangs

2016-07-07 Thread pmb via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365212

Bug ID: 365212
   Summary: Neon 5.7 - Shutdown fails - hangs
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: stable packaging
  Assignee: neon-b...@kde.org
  Reporter: s093x...@rogers.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

Just downloaded and installed Neon 5.7 today - looking good!

I finished the install and clicked 'Restart' (from memory) and the 5.7 spinning
logo continued on and on.

I logged into the installed version, downloaded the updates, and clicked
'Shutdown'. The same action happened again. The logo continued to spin. I
waited 5 minutes and manually powered down from an electrical switch.

I am somewhat lost here because I cannot tell you if any hard drive activity
was happening because I do not have a hard drive activity light.

Hope this helps.


Reproducible: Always

Steps to Reproduce:
1. Open a hard drive session
2. Click 'Shutdown'.
3.


Actual Results:  
 5.7 logo keeps spinning with no other apparent activity


Expected Results:  
After Neon writes whatever to the hard drive then the screen should go blank
and the computer powers down


I do not see any negative effects to the next KDE power up session

I changed the severity because the software does hang. I do not think that this
is really applicable here but it fits the description.

If you can advise me how to capture this in a log file or where a log file
maybe then I would forward you the information.

-- 
You are receiving this mail because:
You are watching all bug changes.