[frameworks-solid] [Bug 361785] processor cores are shown in incorrect sequence is > 10

2016-10-24 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361785

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Gabriel C  ---
Same bug exists in 5.27.0

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


[ksmserver] [Bug 371221] New: Restored maximized windows can't be minimized

2016-10-19 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371221

Bug ID: 371221
   Summary: Restored maximized windows can't be minimized
   Product: ksmserver
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: nix.or@gmail.com

When any kind window is saved maximized on restore there is no way to minimize
it again.

I noticed the following in journalctl:

"\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
(  https://bugs.kde.org/show_bug.cgi?id=306898 marked solved but is not )

also starting as example from a already running session:
konsole --session some_session works just fine.

Reproducible: Always

Steps to Reproduce:
1. Make sure SM is on 
2.  Open some apps and mazimize the windows ( systemsetting , konsole etc )
3. Logut / Login and try to mininize

Actual Results:  
No way to minimize

Expected Results:  
Minimize the windows

Tested on :
Neon
Arch Linux
KaOS
Frugalware Linux

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


[user-manager] [Bug 371216] Users added from user-manager are useless right now

2016-10-19 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371216

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com

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


[user-manager] [Bug 371216] New: Users added from user-manager are useless right now

2016-10-19 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371216

Bug ID: 371216
   Summary: Users added from user-manager are useless right now
   Product: user-manager
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: nix.or@gmail.com

>From a Distro point of view a new user need to be in some groups like video ,
audio , network 
and so on.. to have working thing.

Right now we can have an default user or an admin one.

This is because accountsservice just define 2 types of users:

 ACCOUNT_TYPE_STANDARD
 defaults taken from useradd -> group users

ACCOUNT_TYPE_ADMINISTRATOR
taken from internal default wheel or taken form command line at compile

Without a way to modify the user users with just groups 'users' can't do much
in any kind Distro.

This could be fixed in 2 ways:

1) offer a option to modify users and run usermod on these
 hacky right now since you need offer a UI option to put the user in groups a ,
b ,c
 run accountsservice default and run usermod on the user..
2) get an patch ustream to allow additional groups for  ACCOUNT_TYPE_STANDARD

3) a mix of both :)

Reproducible: Always

Steps to Reproduce:
1. add some user with user-manager
2.
3.

Actual Results:  
User has just users as group or user+admin group without a way to modify

Expected Results:  
option to add users with other groups

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


[user-manager] [Bug 342722] Auto Login non persistent and immutable

2016-10-19 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342722

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com

--- Comment #1 from Gabriel C  ---
Auto login does not work for SDDM is a GDM thing only in accountsservice.

Also I don't think we need this since sddm-kcm has *working* autologin..

1) remove that option from user-manager
or
2) hide it when DM !=  GDM ( I'm not so sure GDM works at all with a kde
session )

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


[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9

2016-05-09 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362805

--- Comment #16 from Gabriel C  ---
yes , now is again broken in the way it was broken before your first fix. ( and
this one was right )

I don't think there is a way to fix it and remain compatible with <=5.21.0 ..
however you guys have to decide the right 'point' to break older installs ..

Best Regards

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


[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9

2016-05-09 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362805

--- Comment #14 from Gabriel C  ---
Allen ,

this commit :

https://quickgit.kde.org/?p=kwallet.git=commitdiff=0d56c68d7a2204a987a5255096d004d5a696c0e5=87e774825b779ba846315a8b2ffe6479dd9f9814

is not really right..

It does not matter how close one will look at it right now you get BIG ENDIAN
algo on LITTLE ENDIAN becuase you are missing to include the header file..

the build  has now again lots :

warning: "Q_BIG_ENDIAN" is not defined [-Wundef]
 #if Q_BYTE_ORDER == Q_BIG_ENDIAN
 ^

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


[kwalletmanager] [Bug 362805] KF5Wallet can't open previuosly created wallet with error code -9

2016-05-09 Thread Gabriel C via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362805

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com

--- Comment #13 from Gabriel C  ---
Hello Allen ,

well I cannot see how this can work .. 

from my tests this breaks kwallet <=5.21.0.

meaning 

5.21.0 -> master is broken always gives you a -9 error
master setup and back to 5.21.0 is broken gives always -9 error

The Q_BYTE_ORDER == .. in code was right just br0ken by missing header files on
<=5.21.0 so I cannot see how this can be fixed to keep compatibility..

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