[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-10-02 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #80 from nicholas  ---
Modifying the qml gets tedious due to updates, especially tumbleweed

On 2 Oct 2016 11:49, "Simone Gaiarin via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=356479
>
> --- Comment #78 from Simone Gaiarin  ---
> My workaround for the spinning file transfer is to modify the qml code and
> make
> it not spin. What other  "animated task manager (?) icons"  are causing the
> problem beside the file transfer spinner?
>
> I still haven't tried your patch for the system tray icon. Can I just
> recompile
> the system tray or does it require to recompile the whole plasma?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-10-02 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #76 from nicholas  ---
(In reply to Fabian Vogt from comment #74)
> (In reply to Simone Gaiarin from comment #72)
> > Is it there any progress on this? Plasma 5.8 is LTS and still has this bug,
> > that seems quite critical to  me. There are multiple animated icons in the
> > task bar and some of them keep the animation running for a long time causing
> > the CPU to be always on.
> > 
> > 
> > - File transfer
> > - Skype
> > - Update notification on Manjaro (I need to kill this or update the system,
> > or my CPU is always on).
> 
> As far as I can tell there are actually two separate bugs: The one is for
> system tray icons (such as skype or your update notification) and my patch
> fixes that and the other one is with animated task manager (?) icons, such
> as file transfer.

1. your patch does not seem to have progressed since proposal?, or could you
update on status?

2. instead of trying to fix this why not bypass the issue, use a static graphic
e.g. a "cloud" around the icon instead of animated spinners? using half my
system resources to indicate a file is transferring is an extremely poor
trade-off.

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-10-02 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #75 from nicholas  ---
(In reply to Fabian Vogt from comment #74)
> (In reply to Simone Gaiarin from comment #72)
> > Is it there any progress on this? Plasma 5.8 is LTS and still has this bug,
> > that seems quite critical to  me. There are multiple animated icons in the
> > task bar and some of them keep the animation running for a long time causing
> > the CPU to be always on.
> > 
> > 
> > - File transfer
> > - Skype
> > - Update notification on Manjaro (I need to kill this or update the system,
> > or my CPU is always on).
> 
> As far as I can tell there are actually two separate bugs: The one is for
> system tray icons (such as skype or your update notification) and my patch
> fixes that and the other one is with animated task manager (?) icons, such
> as file transfer.

1. your patch does not seem to have progressed since proposal?, or could you
update on status?

2. instead of trying to fix this why not bypass the issue, use a static graphic
e.g. a "cloud" around the icon instead of animated spinners? using half my
system resources to indicate a file is transferring is an extremely poor
trade-off.

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


[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)

2016-09-24 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362038

--- Comment #6 from nicholas  ---
sorry, all this framework stuff outside of my scope of expertise.

On 24 September 2016 at 15:00, Ahmed Hussein via KDE Bugzilla
 wrote:
> https://bugs.kde.org/show_bug.cgi?id=362038
>
> --- Comment #5 from Ahmed Hussein  ---
> Sorry, It just work Friday and Saturday. While I was working on this project I
> use Shell project as start project and parse argument to get search string.
> Then I pass QString to Shell::openDocument - I override openDocument to take
> two arguments. Now I want to pass search text to Okular::Document after 
> opening
> url. I am stuck here. Should I access Okular::part using singal same as
> "enableStartWithPrint" then use m_document or that is wrong?!
>
> --
> You are receiving this mail because:
> You reported the bug.

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


[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)

2016-09-17 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362038

--- Comment #4 from nicholas  ---
Sure, here to help, good luck with your first bug!

On 17 Sep 2016 8:28 p.m., "Ahmed Hussein via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=362038
>
> --- Comment #3 from Ahmed Hussein  ---
> Great thank you. I will continue and if I have question I will ask here.
> Is it
> ok?!
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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


[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)

2016-09-17 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362038

--- Comment #2 from nicholas  ---
so the command instructs evince to open on the specified page and
highlight/move to the first occurrence of the word

from http://manpages.ubuntu.com/manpages/wily/man1/evince.1.html

*--page-index=NUMBER*
  Open the document on the page  with  the  specified  page  index
  (this is the exact page number, not a page label).

*--find=string*
  You  can  pass  a word or phrase here. If it exists, evince will
  display the document and the first match.


the actual command "evince --page-index=%p --find=%s %f" is copied from
recoll (http://www.lesbonscomptes.com/recoll/)
in "user preferences"-> "choose editor applications" i can use okular here,
but cannot get the same functionality which is very important (i have had
to install evince for this single use case!)

since you have documentation and application (evince) to benchmark, I
assume this is clear?

Nicholas

On 17 September 2016 at 14:01, Ahmed Hussein via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=362038
>
> Ahmed Hussein  changed:
>
>What|Removed |Added
> 
> 
>  CC||
> thelastrealde...@gmail.com
>
> --- Comment #1 from Ahmed Hussein  ---
> This is my first Bug. I want more info for this bug.
> 1. I implement find Arg and read it "--find ". What do you mean
> with
> --page-index?
> 2. I don't understand what should i do with page Arg. Should I highlight
> search
> only or force to first selected word.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-08-25 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #70 from nicholas  ---
Glad you found the patch.

Just thinking of alternate approach to identify the source of this:
1. someone who knows QT writes a small app containing spinner.
2. spinner can now be triggered in a controlled manner, we can test the effect
of controlling parameters. 
3. uses on different systems can compare behaviour in a quantitative manner
4. push this back up through KDE/QT to find the source of the issue.
At a guess i assume it is something relatively simple like excessive/duplicate
screen updates

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


[systemsettings] [Bug 367074] mouse single/double-click preferences not propagated to kde4 applications

2016-08-18 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367074

--- Comment #4 from nicholas  ---
just a note: konquerer settings affect kde4 but not kde5. This means that e.g.
changing mouse settings in konquerer will affect all kde4 dialogues etc,
possibly in contradiction to the true global setting (kde5). would it not be
better to remove duplicated settings options?

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


[systemsettings] [Bug 367074] New: mouse single/double-click preferences not propagated to kde4 applications

2016-08-16 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367074

Bug ID: 367074
   Summary: mouse single/double-click preferences not propagated
to kde4 applications
   Product: systemsettings
   Version: 5.7.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: ndcunli...@gmail.com
CC: unassigned-b...@kde.org

changing preferences for single or double click for opening files/folders is
not propagated to kde4 applications. 
~/.config/kdeglobals -> [kde] "SingleClick=" is correctly modified with user
selection
~/.kde4/share/config/kdeglobals -> [kde] "SingleClick=" is NOT correctly
modified with user selection

Reproducible: Always

Steps to Reproduce:
1. changie preferences from/to single or double click
2. open ~/.config/kdeglobals and view [kde] "SingleClick=" setting
3. open ~/.kde4/share/config/kdeglobals and view [kde] "SingleClick=" setting

Actual Results:  
kde4  "SingleClick=" setting not same as kde5 setting

Expected Results:  
should have same settings

This bug manifests for example in using kdialog file selector.
looks similar to Bug 343418 (have checked libkde.so is present)
# locate libkde.so 
/usr/lib64/kde4/plugins/gui_platform/libkde.so

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-08-01 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #60 from nicholas  ---
not sure what to make of all this, im a dumb python programmer! do you
actually have high cpu with spinners going?

On 1 August 2016 at 15:10, Samantha McVey via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=356479
>
> --- Comment #59 from Samantha McVey  ---
> Created attachment 100407
>   --> https://bugs.kde.org/attachment.cgi?id=100407&action=edit
> strace of plasmashell
>
> Here is an strace.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-07-29 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #57 from nicholas  ---
I don't thing think the solution to this I tweaking this or that or hoping
that every time there is an update or the wind changes direction it might
be fixed. There is something fundamentally wrong which I assume should not
be that difficult to find via profiling. I did some comparisons of CPU
usage for things like scrolling a PDF and CPU usage was an order of
magnitude less than any of the many instances of status/spinner
requirements.

On 30 Jul 2016 3:21 a.m., "Trevor Parsons via KDE Bugzilla" <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=356479
>
> --- Comment #56 from Trevor Parsons  ---
> As others have observed, copying files in Dolphin, particularly across the
> network, results in this plasmashell CPU overload.
>
> But it turns out that, for me, the most frequent source of this problem is
> the
> tray icon of Amarok (the audio player). A few days ago, I disabled Amarok's
> (very useful but oh well) tray icon in Settings > Configure Amarok >
> General.
> Since then, plasmashell's CPU overload problem has not recurred.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-07-28 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

--- Comment #54 from nicholas  ---
proliferation: 

To note i can also  get 2 bugs regarding the spinner cpu problem by adding an
extra "task manager" on the desktop. The first is as usual, 1 full core used by
spinner. In addition i get random spinners that never stop. This often occurs
opening pdfs with okular, sometimes with Ksysguard, sometimes by having more
than 1 instance of a program eg Dolphin. The spinner continues indefinitely
regardless of application state.  Further observations: 
* the cpu usage continues even if the spinner graphic is covered by another
application window. 
* if the offending app is closed the spinner can jump to another app in the
view.
* turning off "show status on icon" control option makes no difference.
If you can reproduce this behaviour perhaps this could also provide a reliable
source for profiling/debugging.

(for info i changed the lower panel to icon only, then placed the full task
manager on the desktop)

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


[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

2016-07-27 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356479

nicholas  changed:

   What|Removed |Added

 CC||ndcunli...@gmail.com

--- Comment #50 from nicholas  ---
this bug (or its many variants) has been ongoing since 2012 (im currently on
plasma 5.7.0). It is a big problem for the use of laptops on battery. I cannot
understand a design descision which prioritises  "graphical fluff" over system
functionality and the sanity and time of your users. 

The modification of .../NotificationIcon.qml only appears to work for
notifications regarding file coying etc and not network connections, which as i
found out today can go on for a very long time in a workspace with tempromental
 wifi. 

If, (as it would seem) it cannot be fixed, could we have either a formal
(control option) or informal (edit files etc) to silence the problem?

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


[okular] [Bug 362038] New: feature request for "find" functionality from console startup (CLI)

2016-04-21 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362038

Bug ID: 362038
   Summary: feature request for "find" functionality from console
startup (CLI)
   Product: okular
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: ndcunli...@gmail.com

please add "find" option to command line interface such that it can be used
with library search packages i.e. recoll. for example "evince --page-index=%p
--find=%s %f" allows recoll to open on the matching page and highlight/find the
requested string. 

Reproducible: Always

Steps to Reproduce:
1. feature request
2.
3.

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


[plasmashell] [Bug 348050] Launcher in Icon-Only Task Manager Did Not Correspond To Launcher Executed

2016-03-02 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348050

nicholas  changed:

   What|Removed |Added

 CC||ndcunli...@gmail.com

--- Comment #7 from nicholas  ---
could an explanation follow of how to specify launcher icon?

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


[dolphin] [Bug 359581] wrong file permissions (umask 000) when using right click -> create new file

2016-02-25 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359581

--- Comment #4 from nicholas  ---
solution (maybe) causes new problem.

now any file i create is unable to be searched, unless baloo is disabled.

(i have spend all day) creating files etc and testing. if i copy an old file
remove contents and write qwerty and search for string all is good. If i try to
create a new file with same word content, search from dolphin, will not find.

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


[Baloo] [Bug 359672] baloo constantly crashing

2016-02-23 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359672

nicholas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from nicholas  ---
I believe the problem is fixed. I suspect the use of 'chrome>tools>add to
desktop' was the root cause (it created a file with a very garbled name)

The fix was to simply flush the baloo database:
[completely remove the bad file first]
balooctl status (check baloo responds, reboot if not)
balooctl disable
balooctl enable
balooctl status (to check it is indeed rebuilding)

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


[kio] [Bug 356198] Creating new link to application is missing the Application tab (KNewFileMenu, KPropertiesDialog)

2016-02-23 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356198

nicholas  changed:

   What|Removed |Added

 CC||ndcunli...@gmail.com

--- Comment #7 from nicholas  ---
*** Bug 359581 has been marked as a duplicate of this bug. ***

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


[dolphin] [Bug 359581] wrong file permissions (umask 000) when using right click -> create new file

2016-02-23 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359581

nicholas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from nicholas  ---
Solved! 
I Did as you say and can confirm permissions are now set correctly, and in
addition (wrt to  Bug#356198) the files are now 'formed correctly' as e.g. text
etc.
Thanks!

*** This bug has been marked as a duplicate of bug 356198 ***

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


[Baloo] [Bug 359672] New: baloo constantly crashing

2016-02-22 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359672

Bug ID: 359672
   Summary: baloo constantly crashing
   Product: Baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: ndcunli...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.16.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
if i delete a file, rename, sometimes download baloo crashes

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3d6a711780 (LWP 1458))]

Thread 2 (Thread 0x7f3c1f72e700 (LWP 1521)):
#0  0x7fff848f49a2 in clock_gettime ()
#1  0x7f3d6825fc3d in clock_gettime () from /lib64/libc.so.6
#2  0x7f3d68cf57d6 in qt_clock_gettime (ts=0x7f3c1f72d9e0, clock=) at tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#5  0x7f3d68e753b9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f3c180030d0) at kernel/qtimerinfo_unix.cpp:84
#6  0x7f3d68e75945 in QTimerInfoList::timerWait (this=0x7f3c180030d0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#7  0x7f3d68e76b5e in timerSourcePrepareHelper (timeout=0x7f3c1f72da94,
src=) at kernel/qeventdispatcher_glib.cpp:127
#8  timerSourcePrepare (source=, timeout=0x7f3c1f72da94) at
kernel/qeventdispatcher_glib.cpp:160
#9  0x7f3d64c8a4ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f3d64c8ad80 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f3d64c8af7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f3d68e76d8b in QEventDispatcherGlib::processEvents
(this=0x7f3c180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#13 0x7f3d68e1dd53 in QEventLoop::exec (this=this@entry=0x7f3c1f72dd20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#14 0x00422845 in Baloo::FileContentIndexer::run (this=0x13d3370) at
/usr/src/debug/baloo-5.16.0/src/file/filecontentindexer.cpp:71
#15 0x7f3d68c41382 in QThreadPoolThread::run (this=0x142a260) at
thread/qthreadpool.cpp:93
#16 0x7f3d68c4432f in QThreadPrivate::start (arg=0x142a260) at
thread/qthread_unix.cpp:331
#17 0x7f3d672850a4 in start_thread () from /lib64/libpthread.so.0
#18 0x7f3d68252fed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f3d6a711780 (LWP 1458)):
[KCrash Handler]
#6  0x7f3d65f7625c in mdb_get (txn=0x7f3d68e76ab0
, dbi=7,
key=0x7fff8482fdf0, data=0x7fff8482fe00) at mdb.c:5286
#7  0x7f3d6950f92d in Baloo::IdTreeDB::get (this=this@entry=0x7fff8482fe70,
docId=docId@entry=0) at /usr/src/debug/baloo-5.16.0/src/engine/idtreedb.cpp:82
#8  0x7f3d6950cca0 in Baloo::DocumentUrlDB::getId
(this=this@entry=0x7fff8482fee0, docId=0, fileName=...) at
/usr/src/debug/baloo-5.16.0/src/engine/documenturldb.cpp:186
#9  0x7f3d6951e3e9 in Baloo::Transaction::documentId
(this=this@entry=0x7fff8482ff60, path=...) at
/usr/src/debug/baloo-5.16.0/src/engine/transaction.cpp:121
#10 0x0042a923 in Baloo::MetadataMover::removeMetadata
(this=this@entry=0x138b800, tr=tr@entry=0x7fff8482ff60, url=...) at
/usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:74
#11 0x0042a9dd in Baloo::MetadataMover::removeFileMetadata
(this=0x138b800, file=...) at
/usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:66
#12 0x7f3d68e4f73f in call (a=0x7fff848300c0, r=0x138b800, this=0x136e100)
at ../../src/corelib/kernel/qobject_impl.h:124
#13 QMetaObject::activate (sender=sender@entry=0x1370490,
signalOffset=, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7fff848300c0) at kernel/qobject.cpp:3698
#14 0x7f3d68e502e7 in QMetaObject::activate (sender=sender@entry=0x1370490,
m=m@entry=0x646860 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff848300c0)
at kernel/qobject.cpp:3578
#15 0x00434405 in Baloo::PendingFileQueue::removeFileIndex
(this=this@entry=0x1370490, _t1=...) at
/usr/src/debug/baloo-5.16.0/build/src/file/moc_pendingfilequeue.cpp:217
#16 0x00428bc6 in Baloo::PendingFileQueue::processCache
(this=0x1370490) at
/usr/src/debug/baloo-5.16.0/src/file/pendingfilequeue.cpp:89
#17 0x7f3d68e4f73f in call (a=0x7fff84830200, r=0x1370490, this=0x1394480)
at ../../src/corelib/kernel/qobject_impl.h:124
#18 QMetaObject::activate (sender=sender@entry=0x13704a8,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3698
#19 0x7f3d68e502e7 in QMetaObject::activate (sender=sender@entry=0x13704a8,
m=m@entry=0x7f3d6926e8

[dolphin] [Bug 359581] New: wrong file permissions (umask 000) when using right click -> create new file

2016-02-19 Thread nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359581

Bug ID: 359581
   Summary: wrong file permissions (umask 000) when using right
click -> create new file
   Product: dolphin
   Version: 15.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ndcunli...@gmail.com

If new text or html document is created using the right click menu, then ALL
permissions are set to read and write (my default umask is 022). Have tested
touch from shell, kwrite (from shell and menu) etc and they give the correct
permissions.

Reproducible: Always

Steps to Reproduce:
1. start dolphin
2. right click in any home folder -> create new text file
3. right click - view properties/permissions

Actual Results:  
mask 000

Expected Results:  
mask 022

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


[systemsettings] [Bug 359517] New: Can't extend onto second screen in VMWare

2016-02-17 Thread Nicholas via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359517

Bug ID: 359517
   Summary: Can't extend onto second screen in VMWare
   Product: systemsettings
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nicho...@nshiell.com

Can't extend desktop onto secondary screen on VMWare (Plasma 5)

Given I am running Kubuntu inside VMWare fusion
 When I connect a second physical screen
   And I see VMware fullscreen the guest OS onto the screen
  Then I should be able to extend my desktop onto the second screen in system
settings

(Sorry if this bug is filed into the wrong place)

Reproducible: Always

Steps to Reproduce:
1. Run Kubuntu 15.10 inside VMWare Fusion (I have OSX as a host)
2. Plug in a second screen
3. Goto system settings > Display Configuration

Actual Results:  
Observe you can't extend the screen, second screen doesn't appear to be
detected

Expected Results:  
I should be able to extend my screen

This works with Plasma 4, on the same host OS, with the same install of VMWare
fusion

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