[kcalc] [Bug 489980] uppercase exponential not understood

2024-07-17 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=489980

--- Comment #6 from S. Umar  ---
I tested the master git (not committed to 24.05 branch yet) and the capital E
exponents work now. Thanks.

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

[kcalc] [Bug 489980] uppercase exponential not understood

2024-07-09 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=489980

--- Comment #2 from S. Umar  ---
Hi, I believe most FORTRAN compilers use the upper case. I am using the latetst
Intel OneApi fortran compilers. One can code lower case e
but the output files have the upper case.

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

[kcalc] [Bug 489980] New: uppercase exponential not understood

2024-07-09 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=489980

Bug ID: 489980
   Summary: uppercase exponential not understood
Classification: Applications
   Product: kcalc
   Version: 24.05.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: evan.te...@gmail.com
  Reporter: u...@compsci.cas.vanderbilt.edu
CC: gabriel.barrantes@outlook.com
  Target Milestone: ---

If I input 3.6434E+01 into kcalc it gives me "input error" but lowercase
version  3.6434e+01 gvies 36.434. Uppercase is iseful when pasting from outputs
(like fortran) which uses the uppercase E. Thanks!

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-29 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

S. Umar  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from S. Umar  ---
per comment #6 the issue is resolved.

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-14 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #6 from S. Umar  ---
Actually the files in comment #2 were the problen. I went ahead and edited
them, removing all the extra accurances of gkrellm  and plasmashell and just
leaving one instance. After that it stopped adding additional instances, I
think what happened is that every time I got a new workstations I copied my old
home directory to the new one, which may have created multiple instances after
new login. In any case I fixed it on all my computers. I think we can close
this case.

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

[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login

2024-06-06 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #25 from S. Umar  ---
Fedora 40 included these patches in a new version. However, it seems to break
the logout from KDE plasma. When I select logout (on multiple computers) I get
a black screen with the mouse cursor showing only.

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #4 from S. Umar  ---
The logout works with Plasma Wayland. The problem  seems to be with Plasma(X1).
However, I can't use Wayland because some apps are very jittery, like chrome
and linreoffice.

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #3 from S. Umar  ---
Also in, .local/share/plasmasessionrestore/plasmasessionrestorestaterc 

[0]
appId=gnome-gkrellm.desktop

[1]
appId=gnome-gkrellm.desktop

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

[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login

2024-06-05 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

--- Comment #2 from S. Umar  ---
No, it is not. There is nothing in .config/autostart. Is there another place
for autostart? I see it in .config/ksmserverrc as:

[LegacySession: saved at previous logout]
clientMachine1=localhost
clientMachine2=localhost
command1=gkrellm
command2=gkrellm
count=2
--
I also see multiple instances I (after logging in and out) in kwin_saved\ at\
previous\ logout_
resourceClass1=Gkrellm
resourceClass2=Gkrellm
resourceClass3=plasmashell
resourceClass4=Gkrellm
resourceClass5=gkrellm
resourceClass6=plasmashell
resourceName1=gkrellm
resourceName2=gkrellm
resourceName3=plasmashell
resourceName4=gkrellm
resourceName5=gkrellm
resourceName6=plasmashell

..


wmCommand1=gkrellm\s
wmCommand2=gkrellm\s
wmCommand3=
wmCommand4=gkrellm\s
wmCommand5=gkrellm\s
wmCommand6=

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

[plasmashell] [Bug 488022] New: Multiple instances of gkrellm upon reboot or logout/login

2024-06-04 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=488022

Bug ID: 488022
   Summary: Multiple instances of gkrellm upon reboot or
logout/login
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Session Management
  Assignee: plasma-b...@kde.org
  Reporter: u...@compsci.cas.vanderbilt.edu
CC: natalie_clar...@yahoo.de
  Target Milestone: 1.0

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

I have gtk app gkrellm on my desktop. I just noticed that everytime I
login/logout OR even after every reboot there is an extra session of gkrellm
running. It just keeps growing. I have done a killall -HUP gkrelmm and tested
again multiple times with the same result. Eventually they start consuming
significant amount of CPU.
PS: I am running plasma-X11. I have not tested with Wayland.


STEPS TO REPRODUCE
1.  start gkrellm on desktop
2. login/logout or reboot
3. ps -e |grep gkrellm

OBSERVED RESULT
multiple instances of gkrellm upon reboot or login/logout

EXPECTED RESULT
Single instance of gkrellm

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0 (some 6.2.1 and 6.2.2)
Qt Version: 6.7.1

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login

2024-06-04 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #23 from S. Umar  ---
No it did not. I will open a new case

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

[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login

2024-06-04 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=487912

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #22 from S. Umar  ---
I have also noticed that gtk apps that are on the desktop (I use gkrellm)
multiply after logout/login or reboot. I have gkrellm on the desktop and I
noticed many copies of it running. I killed them all started one and tested
again and they keep multiplying. I will test to see if this patch fixes that
too.

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

[kwin] [Bug 485609] cpu usage at 100% when moving the mouse on wayland but not on X11

2024-04-26 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=485609

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #1 from S. Umar  ---
I can confirm this on the new Fedora 40. kwin_wayland both on laptop Intel HD
graphics and Workstaion with NVIDIA drivers use 2-3% of CPU when nothing is
done. When one moves the mouse it goes up to 15-17%. Fedora 40 no longer
provides the X11 option for Plasma 6 so we need a solution for this.

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2024-03-23 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

S. Umar  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2024-03-23 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

--- Comment #8 from S. Umar  ---
No, it is resolved. Thanks!

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

[kio-extras] [Bug 462381] KIO-Extras AFC URL error

2023-04-25 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=462381

--- Comment #4 from S. Umar  ---
This fix is not applied to 23.04.0 even though afc support is now formal. The
problem still exists as explained below. Applying the below patch to kio-extras
fixes the issue. This is also true on Fedora.

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

[Powerdevil] [Bug 468807] New: Monitors not going to sleep with Fedora 38

2023-04-22 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=468807

Bug ID: 468807
   Summary: Monitors not going to sleep with Fedora 38
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: u...@compsci.cas.vanderbilt.edu
CC: m...@ratijas.tk
  Target Milestone: ---

Hi, I just updated some of my workstations to Fedora 38 and noticed that when
logged out the monitors do not go to powersave mode. When I am logged in the
powersave mode works fine.

I am running plasma under X11 and noticed that in FC38 the sddm is using
kwin_wayland so perhaps that is the issue because previously we were using
sddm-x11 but that is no longer possible in Fedora 38.

Also, sometimes the effected machines are using 100%cpu with kwin_wayland when
no one is logged in (I ssh'ed into
the machine remotely) but this is not always reproducible.

KDE-Plasma versions 5.27.4, KF5 5.105.0. Thanks!

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

[ksmserver] [Bug 466385] Logout hangs

2023-03-03 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=466385

--- Comment #3 from S. Umar  ---
The latest sddm git build for Fedora 37 resolved this problem...should be
coming up in updates.

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

[kscreenlocker] [Bug 466385] Logout hangs

2023-02-25 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=466385

--- Comment #2 from S. Umar  ---
PS: I am not sure this is kscreenlocker issue or not. Screen lock is working
fine. This has been confirmed on multiple workstations and laptops.

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

[kscreenlocker] [Bug 466385] Logout hangs

2023-02-25 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=466385

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #1 from S. Umar  ---
I can confirm this on Fedora 37 with plasma desktop 5.27.1 and plasma 5.103. On
systems using nvidia drivers the hang occurs but the keybaord/mouse is still
functional in the sense that ctrl+alt+backspace restarts X11 to new sddm login
screen. On systems not using
nvidia drivers (intel HD graphics on Lenovo laptop) the keyboard also dies and
only the mouse moves on a black screen. Hard power on/off is required to
restart.

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

[kio-extras] [Bug 462381] KIO-Extras AFC URL error

2022-12-14 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=462381

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #3 from S. Umar  ---
I was having the same problem (applied all the afc patches to various
components) but the changes mentioned in
https://invent.kde.org/network/kio-extras/-/merge_requests/214 solved the
problem.

A naive question! Is there a way to access the photos saved in the icloud? I
seem to only see the photos that are on the iphone.

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

[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region

2021-12-13 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=413361

S. Umar  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region

2021-12-13 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=413361

S. Umar  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #9 from S. Umar  ---
It is resolved in updated versions...

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

[okular] [Bug 444902] okular tool stuck on digital signature

2021-11-03 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=444902

--- Comment #1 from S. Umar  ---
Sorry, the 21.08.0 is the poppler version, below. Okular is as states 21.08.2

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

[okular] [Bug 444902] New: okular tool stuck on digital signature

2021-11-03 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=444902

Bug ID: 444902
   Summary: okular tool stuck on digital signature
   Product: okular
   Version: 21.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

SUMMARY
When one chooses the Digitally sign... option from the tools menu and draws a
box but then cancels the signing
and switched the tool to anything else e.g. underline the signature option
remains active no matter what one chooses.

STEPS TO REPRODUCE
1. Open a pdf file
2. Choose Digitally sign...from tools menu and draw a box
3. Cancel signing
4. Try to use another annotation tool

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35 with 21.08.0
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2021-09-09 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

--- Comment #6 from S. Umar  ---
Ctrl-Q works fine on my desktop machines too, so the only problem is with my
laptop for some reason.

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2021-09-08 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

--- Comment #5 from S. Umar  ---
Found a suggestion via google search:  ctrl-alt-Q works! Not sure what is going
on as ctrl-Q works on xterm.

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2021-09-08 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

--- Comment #4 from S. Umar  ---
No change in profile and ctrl-S/ctrl-Q works in xterm

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

[konsole] [Bug 442194] konsole ctrl-Q not working

2021-09-08 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

--- Comment #2 from S. Umar  ---
It shows correct ^S and ^Q. ^S works and gives the message to use ctrl-Q to go
back but doing so has no effect. This is on a Lenovo laptop

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

[konsole] [Bug 442194] New: konsole ctrl-Q not working

2021-09-08 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=442194

Bug ID: 442194
   Summary: konsole ctrl-Q not working
   Product: konsole
   Version: 21.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

After suspending with ctrl-S, which works, ctrl-Q does nothing and one cannot
restore a working terminal.

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

[konsole] [Bug 441176] Mouse hover activation for split konsole

2021-08-19 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=441176

S. Umar  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from S. Umar  ---
Sorry, this could be fixed in Settings to functionclosing!

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

[konsole] [Bug 441176] New: Mouse hover activation for split konsole

2021-08-19 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=441176

Bug ID: 441176
   Summary: Mouse hover activation for split konsole
   Product: konsole
   Version: 21.08.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: split-view
  Assignee: konsole-de...@kde.org
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

With the new konsole using split screens the mouse hover activation is not
working for individual screens. It does work for multiple console windows but
not for split windows. This makes switching between split windows difficult as
it requires a mouse click

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

[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region

2020-01-27 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=413361

--- Comment #6 from S. Umar  ---
Another possibility is that my desktop has 3 monitors connected to it whereas
the laptop is naturally one.

What happens is that the spectacle keeps running in the background but the
entire gui is gone. If one chooses a full screen shot it works fine.

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

[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region

2020-01-27 Thread S. Umar
https://bugs.kde.org/show_bug.cgi?id=413361

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #5 from S. Umar  ---
I can confirm this on Fedora 31 with 19.08.3 and 19.12.1 using X11.
It works fine on my Lenovo laptop with Intel HD graphics but the
reported bug happens on my desktop with Nvidia propriety drivers.

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

--- Comment #15 from S. Umar  ---
That fixes it!

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

--- Comment #12 from S. Umar  ---
Exactly...I configured firefox to open pdf using okular.

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

--- Comment #10 from S. Umar  ---
No annotations but I am doing Save as...to save it to my home directory.
It appears in /tmp/mozilla_umar0/ by default. It would be nice if one
tries to save it defaults to home directory.

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

--- Comment #8 from S. Umar  ---
Created attachment 115859
  --> https://bugs.kde.org/attachment.cgi?id=115859=edit
Screenshot

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

--- Comment #6 from S. Umar  ---
I am not sure what you mean? I apply all the patches on 18.08 git
and rebuild okular rpm for my system. When I remove this I can save
again. Do you have all the patches applied?

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=399870

S. Umar  changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from S. Umar  ---
I am not able to save any file after this patch! Please check.

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

[kcalc] [Bug 398849] Unusual behavior with pasted numbers starting with zero

2018-09-20 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=398849

--- Comment #3 from S. Umar  ---
OK. I see that but as you say I am in Science Mode. Obviously manuall entering
02700 gives the correct 2700 so the problem is with the interpretation of
pasted numbers only. Whatever logic is applied to manual entry should also
apply to pasted entries.

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

[kcalc] [Bug 398849] New: Unusual behavior with pasted numbers starting with zero

2018-09-19 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=398849

Bug ID: 398849
   Summary: Unusual behavior with pasted numbers starting with
zero
   Product: kcalc
   Version: 18.04
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

I just noticed that if I cut/paste some numbers that start with a zero,
e.g. 02700 into kcalc the display shows 1472. This does not happen if you
actually type in 02700, then you get 2700. Pasted numbers higher than some
starting with zero, e.g. 02800 gives nan. Lower numbers give more weird
stuff, e.g. 01200 gives 640.

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

[kile] [Bug 390842] Latest git commits crash kile

2018-02-25 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=390842

--- Comment #7 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Just tested the latest commit and that also worked. Thanks.

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

[kile] [Bug 390842] Latest git commits crash kile

2018-02-25 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=390842

--- Comment #6 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Hi, I had solved this by starting kile with the old working version, closed
all files (since even if kile was called without a name it opened the last
document), updated to new version and started it. It started fine. Then I
opened the same tex file and it did not crash any more. I hope this is
related to your change. Something certainly that had to do with opening
files.

I will try the latest one shortly as well. Thanks.

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

[kile] [Bug 390842] Latest git commits crash kile

2018-02-21 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=390842

--- Comment #4 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Hi, I am not sure what test case would be. It happens even if I just issue
the kile command with no arguments at the command line.

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

[kile] [Bug 390842] Latest git commits crash kile

2018-02-21 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=390842

--- Comment #2 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Created attachment 110879
  --> https://bugs.kde.org/attachment.cgi?id=110879=edit
Crash report

I attached it. I don't have debug messages so I hope it is useful.

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

[kile] [Bug 390842] New: Latest git commits crash kile

2018-02-21 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=390842

Bug ID: 390842
   Summary: Latest git commits crash kile
   Product: kile
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

Something in the latest 4 commits is crashing kile immediately at startup. I
build kile rpm from git on Fedora 27. It is not the last dbus commit but the 3
commits
before that. Removing these works fine. FYI

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

[kile] [Bug 364238] cite command not showing bibliography entries

2018-01-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #10 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Hi, that worked with one caveat. Hitting ctrl+space brings up the bibtexkeys
from the bib file but after the last bibtexkey the other unrelated things
follow.

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

[kile] [Bug 364238] cite command not showing bibliography entries

2018-01-23 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #8 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
A single file. Am I not using it correctly?

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

[kile] [Bug 364238] cite command not showing bibliography entries

2018-01-22 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #6 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
As seen in the image I am still seeing this with the git just pulled (after the
biblatex.cwl fi correction). I use revtex style that uses natbib and I am on
Fedora Linux.

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

[kile] [Bug 364238] cite command not showing bibliography entries

2018-01-22 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #5 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Created attachment 110058
  --> https://bugs.kde.org/attachment.cgi?id=110058=edit
screen image

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

[kile] [Bug 377250] Warning/Error message from Kile

2017-03-08 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=377250

--- Comment #1 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
The last part of my report concerning clicking "Do not show this message again"
and seeing no effect in subsequent start seems to be fixed with plasma
framework 5.32.0. The main error message still appeared though.

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

[kile] [Bug 377250] New: Warning/Error message from Kile

2017-03-05 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=377250

Bug ID: 377250
   Summary: Warning/Error message from Kile
   Product: kile
   Version: 2.9.60
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

Running the latest git I started getting the following message:

"There are two actions (Find in Files..., Normal Fraction - \frac{}{}) that
want to use the same shortcut (Alt+Shift+F). This is most probably a bug.
Please report it in bugs.kde.org"

Plasma desktop: 5.8.6
Plasma-framework: 5.31.0
Applications: 16.12.2

In addition, if you click the box "Do not show this message again" it has no
effect and shows up next time again.

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

[kile] [Bug 373586] Kile crashes with Statistics

2016-12-16 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=373586

--- Comment #2 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Thanks, that worked. It would also be nice if the citation problem can be
fixed, namely after typing \cite{ if you hit ctrl+space you don't get the
citations from the bib file but a list of every word in the tex file.

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

[plasmashell] [Bug 359220] Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

2016-12-13 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=359220

S. Umar <u...@compsci.cas.vanderbilt.edu> changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #11 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
I can confirm that with plasma 5.8.4, breeze icons, and the option in #2 on
nothing happens when right clicking on the desktop icons (widgets do show
handles
when right clicked bu not other icons, Home, Trash etc.).

Also, when you go the desktop configuration and choose icons the slider bar
for icon resizing only moves from one notch to the next and not continously.

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

[kile] [Bug 373469] File-Statistics crashes kile

2016-12-12 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=373469

--- Comment #2 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Yes...I just went through report the bug option.

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

[kile] [Bug 373586] New: Kile crashes with Statistics

2016-12-12 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=373586

Bug ID: 373586
   Summary: Kile crashes with Statistics
   Product: kile
   Version: 2.9.60
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

Application: kile (2.9.60)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.14-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:

Used Statistics from File menu. While using kile I am interested in Statistics
such
as number of words etc.

The crash can be reproduced every time.

-- Backtrace:
Application: Kile (kile), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9791858940 (LWP 13042))]

Thread 5 (Thread 0x7f977d613700 (LWP 13046)):
#0  0x7f97a02f4460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f97a352a0ca in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f97a9cc2319 in KileParser::ParserThread::run() () at
/lib64/libkdeinit5_kile.so
#3  0x7f97a3529a4a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f97a02ee6ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f97a2202f6f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f977de14700 (LWP 13045)):
#0  0x7f97a02f4460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f97a352a0ca in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f97a9cc2319 in KileParser::ParserThread::run() () at
/lib64/libkdeinit5_kile.so
#3  0x7f97a3529a4a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f97a02ee6ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f97a2202f6f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9785c23700 (LWP 13044)):
#0  0x7f97a21f2bdd in read () at /lib64/libc.so.6
#1  0x7f979ae5e450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f979ae19c60 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f979ae1a0f4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f979ae1a26c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f97a3716d7b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f97a36c807a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f97a3525673 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f97a48b57a9 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#9  0x7f97a3529a4a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f97a02ee6ca in start_thread () at /lib64/libpthread.so.0
#11 0x7f97a2202f6f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f97873b7700 (LWP 13043)):
#0  0x7f97a21f700d in poll () at /lib64/libc.so.6
#1  0x7f979e943d10 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f979e945aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f978ab98a19 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f97a3529a4a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f97a02ee6ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f97a2202f6f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9791858940 (LWP 13042)):
[KCrash Handler]
#6  0x7f97a9b98942 in
KileDialog::StatisticsDialog::StatisticsDialog(KileProject*,
KileDocument::TextInfo*, QWidget*, KTextEditor::View*, char const*, QString
const&) () at /lib64/libkdeinit5_kile.so
#7  0x7f97a9c062a2 in Kile::showDocInfo(KTextEditor::View*) () at
/lib64/libkdeinit5_kile.so
#8  0x7f97a36effc1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#9  0x7f97a3f0af52 in QAction::triggered(bool) () at
/lib64/libQt5Widgets.so.5
#10 0x7f97a3f0d982 in QAction::activate(QAction::ActionEvent) () at
/lib64/libQt5Widgets.so.5
#11 0x7f97a407c0aa in
QMenuPrivate::activateCausedStack(QVector const&, QAction*,
QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5
#12 0x7f97a408231c in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5
#13 0x7f97a4086390 in QMenu::mouseReleaseEvent(QMouseEvent*) () at
/lib64/libQt5Widgets.so.5
#14 0x7f97a3f58c40 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#15 0x7f97a4086e3b in QMenu::event(QEvent*) () at /lib64/libQt5Widgets.so.5
#16 0x7f97a3f1196c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#17 0x7f97a3f19fcd in QApplication::notify(QObject*, 

[kile] [Bug 373469] New: File-Statistics crashes kile

2016-12-09 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=373469

Bug ID: 373469
   Summary: File-Statistics crashes kile
   Product: kile
   Version: 2.9.60
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu
  Target Milestone: ---

Hi. Using the latest git snapshot pulling down Statistics from the File menu
crashes kile every time.

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

[kile] [Bug 364238] cite command not showing bibliography entries

2016-12-09 Thread S . Umar
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #2 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
This issue is still there in latest git snapshot.

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

[kmail2] [Bug 358679] kmail5 crash on reload when config to empty trash on exit

2016-07-06 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358679

S. Umar <u...@compsci.cas.vanderbilt.edu> changed:

   What|Removed |Added

 CC||u...@compsci.cas.vanderbilt
   ||.edu

--- Comment #18 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
There is still a bug that kmail does not stop running when you select quit from
file menu. 
This is only when empty trash on exit selected. When empty trash on exit is
unselected
it quits properly.

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


[kile] [Bug 364238] cite command not showing bibliography entries

2016-06-20 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364238

--- Comment #1 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Hi, as a side note, in biblatex.cwl file in three instances the "fi" of "file"
is in a different
character set. I don't think this is intentional.

Forgot to say that I am using natbib.sty.
Thanks

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


[kile] [Bug 364238] New: cite command not showing bibliography entries

2016-06-12 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364238

Bug ID: 364238
   Summary: cite command not showing bibliography entries
   Product: kile
   Version: 2.9.60
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu

I am using the development version of kile updated from git. The problem is
when I use
a bibliogrpahy file and type \cite{ and use ctrl+space I am getting a long list
of irrelevant words
and sprinkled in between just a few of the real bib entries. The words shown
seem to be from the tex file and tex comands e.g. abstract, etc. The same file
works fine under texstudio and typing \cite{ shows all the bib entries. I am
using revtex style that imports natbib.

Reproducible: Always

Steps to Reproduce:
1. type \cite{
2. press ctrl+space
3. list of words appear

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


[kile] [Bug 358877] Kile finding the wrong poppler

2016-02-01 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358877

--- Comment #1 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Created attachment 96957
  --> https://bugs.kde.org/attachment.cgi?id=96957=edit
Poppler patch

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


[kile] [Bug 358877] New: Kile finding the wrong poppler

2016-02-01 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358877

Bug ID: 358877
   Summary: Kile finding the wrong poppler
   Product: kile
   Version: 2.9.60
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: u...@compsci.cas.vanderbilt.edu

Using the latest plasma/framework the building of kile 2.9.60 from git is no
longer finding the
correct poppler, should find poppler-qt5. Okular5 git have recently fixed this
problem. That
patch can be adopted to Kile, which I tested and it works.

For some reason though while these patches find the correct poppler-qt5 and it
works it is
still issuing a message that the optional poppler is not found.

Reproducible: Always

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


[plasmashell] [Bug 356018] Entries stay highlighted after closing context menu

2016-01-28 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356018

--- Comment #9 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Yes. It is fine now. Thanks.

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


[plasmashell] [Bug 356018] Entries stay highlighted after closing context menu

2016-01-28 Thread S . Umar via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356018

--- Comment #6 from S. Umar <u...@compsci.cas.vanderbilt.edu> ---
Nopestill the same and there is an error in the taskbar (looks like a
window on the panel!)

Error loading QML file:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:220:19:
Type Task unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:157:5:
Cannot assign to non-existent property "onSmartLauncherEnabledChanged"

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