[krita] [Bug 464182] New: krita crashed when i absent mindedly pasted plaintext
https://bugs.kde.org/show_bug.cgi?id=464182 Bug ID: 464182 Summary: krita crashed when i absent mindedly pasted plaintext Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: unkemptn...@gmail.com Target Milestone: --- i dunno where to post the githash number so ill just post it here (git e753d24) STEPS TO REPRODUCE 1. copy plaintext without creating a vector layer 2. paste OBSERVED RESULT it crashed lol EXPECTED RESULT I did it by complete accident I normally would have made a text on a vector layer SOFTWARE/OS VERSIONS Windows: x macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464182] pasting plaintext without a vector layer causes crash
https://bugs.kde.org/show_bug.cgi?id=464182 LIAM changed: What|Removed |Added Summary|krita crashed when i absent |pasting plaintext without a |mindedly pasted plaintext |vector layer causes crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373532] New: [UGEE] All strokes connect
https://bugs.kde.org/show_bug.cgi?id=373532 Bug ID: 373532 Summary: [UGEE] All strokes connect Product: krita Version: 3.0.1.1 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: lordlia...@gmail.com Target Milestone: --- Created attachment 102730 --> https://bugs.kde.org/attachment.cgi?id=102730&action=edit Debug view of scribbling with both pen and mouse. Recently got the Ugee 2150 drawing monitor and once I got past the annoying set up I got it to work really nicely with SAI but in Krita it doesnt really work at all. Each line is connected to the previous, except for occasional random ones where it doesnt seem to. Occasionally they share the same point of origin instead of going after the previous stroke, as if its stuck at the end of an older stroke. Here is a puu.sh screenshot of the lines it makes+debugview https://puu.sh/sLZPM.png -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 Liam Dawe changed: What|Removed |Added CC||liamd...@gmail.com --- Comment #12 from Liam Dawe --- I just upgraded Fedora 37, and I am seeing this exact issue. Driving me insane. This is on Plasma 5.26.5 so it's not just on 5.27 that this happens. I can confirm disabling my 60Hz monitor and sticking to my 180Hz monitor solves it, but obviously that's not an actual fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #14 from Liam Dawe --- Yes this also on KDE Frameworks 5.103.0. I also tried kscreen-console monitor, and keeping it open while seeing the black screen flashing it doesn't seem to report anything. This is all it gave me while I saw it do it many times: [liam@desktop-f7tu9t7 ~]$ kscreen-console monitor kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "(c) 2012 KScreen Team" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KScreen Console" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KScreen Console" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Maintainer" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Alejandro Fiestas Olivares" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "KScreen Console is a CLI tool to query KScreen status\n\nCommands:\n bug Show information needed for a bug report\n config Show KScreen config files\n outputs Show output information\n monitor Monitor for changes\n jsonShow current KScreen config" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Command to execute" msgid_plural: "" msgctxt: "" kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "Arguments for the specified command" msgid_plural: "" msgctxt: "" Remember to enable KSRandR or KSRandR11 in kdebugdialog So that's not a way to detect it happening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] Periodic black screens on main monitor with 144Hz refresh rate after upgrade to 5.27
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #15 from Liam Dawe --- I can also confirm that matching the refresh rate on both monitors also fixes it, in addition to turning off one monitor. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 466698] New: Welcome Center Page 1 shows incorrect description of Debian
https://bugs.kde.org/show_bug.cgi?id=466698 Bug ID: 466698 Summary: Welcome Center Page 1 shows incorrect description of Debian Classification: Applications Product: Welcome Center Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: liam.crabb...@gmail.com CC: n...@kde.org Target Milestone: --- Created attachment 156910 --> https://bugs.kde.org/attachment.cgi?id=156910&action=edit Image showing Plasma Welcome SUMMARY When launching Welcome Center from the plasma-welcome package on Debian Testing, it displays "Debian is a free and open-source desktop environment created by KDE, an international software community of volunteers." on the first page. The link to "Learn more about the Debian community" links to the KDE Community site. STEPS TO REPRODUCE 1. Install plasma-welcome from Debian testing (version 5.27.0-1) 2. Launch Welcome Center OBSERVED RESULT "Debian is a free and open-source desktop environment created by KDE, an international software community of volunteers." EXPECTED RESULT Display information about Debian or do not display the first page SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] New: Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 Bug ID: 468949 Summary: Loses logins constantly Classification: Applications Product: Tokodon Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: liamd...@gmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY Trying out Tokodon in the latest release from Flathub, and it just seems after a while of closing it that all logins just vanish. It's making the app somewhat useless to have to constantly add the accounts back in. STEPS TO REPRODUCE 1. Test it on Fedora 38 with Flathub 2. Watch as accounts vanish after you close and leave it closed a while. SOFTWARE/OS VERSIONS Fedora 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] After upgrade to 5.27, periodic visual glitches when monitors' refresh rates don't match
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #19 from Liam Dawe --- I can confirm that as of now it does seem to work properly :) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 --- Comment #2 from Liam Dawe --- We're talking probably less than an hour before it loses the logins. Since I keep closing and re-opening it (as it seems to not close to tray). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446308] New: Maximize windows does not fill to the
https://bugs.kde.org/show_bug.cgi?id=446308 Bug ID: 446308 Summary: Maximize windows does not fill to the Product: kwin Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l...@phmurphy.com Target Milestone: --- Created attachment 144107 --> https://bugs.kde.org/attachment.cgi?id=144107&action=edit Image shows a maximized window that is not filling to the bottom of the desktop. SUMMARY On my secondary monitor, attempting to maximize any window is resulting in a "gap" between the bottom of the window, and the bottom of the desktop. My guess is that Kwin (or whatever component this should apply to) believes that a panel exists, even though it doesn't. This can be seen in the attached image. Note: this could be a plasma shell bug as well, wasn't sure the best place to put it. STEPS TO REPRODUCE UNKNOWN. OBSERVED RESULT This started occurring randomly. Does not occur on my primary monitor where a bottom panel does exist. Have attempted to restart plasmashell and kwin / restarting my whole PC, no change. EXPECTED RESULT A maximize window would fill to the bottom of the screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.5 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have an RTX 3070, driver version 495.44 (in case that makes a difference). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446308] Maximize windows does not fill to the bottom of the screen on secondary display
https://bugs.kde.org/show_bug.cgi?id=446308 Liam Murphy changed: What|Removed |Added Summary|Maximize windows does not |Maximize windows does not |fill to the |fill to the bottom of the ||screen on secondary display -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446308] Maximize windows does not fill to the bottom of the screen on secondary display
https://bugs.kde.org/show_bug.cgi?id=446308 --- Comment #2 from Liam Murphy --- (In reply to Nate Graham from comment #1) > X11 or Wayland? Any scaling in use? X11, scaling is set to default (100%). Primary monitor is DisplayPort, secondary is HDMI, both are 2560x1440 FWIW. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446308] Maximize windows does not fill to the bottom of the screen on secondary display
https://bugs.kde.org/show_bug.cgi?id=446308 --- Comment #4 from Liam Murphy --- (In reply to Nate Graham from comment #3) > Thanks. How strange. After some digging I believe this is a plasmashell issue (apologies for putting it in the wrong spot). Running plasmashell from the shell with `plasmashell --replace` and then quitting that process (presumably shutting down plasmashell) resulted in the windows on my second screen to be properly maximized. So I looked in `~/.config/plasmashellrc` and found these entries: ``` [PlasmaViews][Panel 26][Defaults] thickness=20 [PlasmaViews][Panel 26][Horizontal2560] thickness=20 [PlasmaViews][Panel 26][Vertical1440] thickness=54 [PlasmaViews][Panel 3][Defaults] thickness=30 [PlasmaViews][Panel 3][Horizontal2560] thickness=30 ``` Panel 3 is the panel on my main display, so I thought it was strange this "Panel 26" existed. So I deleted that, rebooted my system, and now it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445720] audio damaged for one/two syllables after beginning
https://bugs.kde.org/show_bug.cgi?id=445720 --- Comment #6 from Liam Dawe --- Just to confirm, the suggestion of exporting Audacity to 16-bit PCM WAV seems to entirely solved it. I've done lots of videos with it recently, and no issue when doing that. So hopefully that does point you towards the issue with the mp3 files. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Liam Coogan changed: What|Removed |Added CC||lcoo...@pm.me --- Comment #33 from Liam Coogan --- I am experiencing this exact issue. STEPS TO REPRODUCE 1. Define Meta+3 as a shortcut for the 'Firefox' entry in KDE Menu Editor 2. Type Meta+3 OBSERVED RESULT Firefox does not launch after pressing Meta+3 EXPECTED RESULT Firefox launches after pressing Meta+3 SOFTWARE VERSIONS KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 When I set Meta+3 as the launcher for a native KDE app that initially had a different shortcut, e.g. Dolphin, it works as expected. I have now tried Meta+3 on a variety of non-KDE applications, and none launch with the shortcut. I have also tried a variety of other keyboard shortcuts, including shortcuts not involving the Meta key, and none launch Firefox. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] New: Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 Bug ID: 443055 Summary: Pdf File's Size Changed to 0 Bytes After Sudden Power Outage Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jlame...@gmail.com Target Milestone: --- I was reading a book using Okular. I made some annotations and then pressed Ctrl+S to save the changes. Just 2 seconds after i pressed Ctrl+S there was a power outage and my pc powered off(note pc didn't have any UPS). Next when the power came back on i started my pc and found that the same pdf file is now occupying 0 bytes of space. Unfortunately, i was not using git in this case so i cannot get the old file back. I have found that there are some xml files under the folder /home/username/.local/share/okular/docdata/ that correspond to my old pdf. For example the files are named like: /home/username/.local/share/okular/docdata/4297319.NetworkProgramming.pdf.xml /home/username/.local/share/okular/docdata/4298415.NetworkProgramming.pdf.xml ... My question is that Is there a way to get back my old pdf file back using these above xml files? For example, i have an old pdf which is the same as the old pdf except that this one doesn't have any annotations in it. So Will it be possible to add these xml information into that file(that doesn't have any annotation)? I am using Ubuntu 18.04 x86_64 and Okular 1.3.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #2 from Jason Liam --- (In reply to David Hurka from comment #1) > > My question is that Is there a way to get back my old pdf file back > > using these above xml files? > > No, but... > > > For example, i have an old pdf which is the same as the old pdf > > except that this one doesn't have any annotations in it. So Will > > it be possible to add these xml information into that file(that > > doesn't have any annotation)? > > > > I am using Ubuntu 18.04 x86_64 and Okular 1.3.3 > > This old Okular version stored annotations in these XML files. So if you > find that one of these XML files contains your annotations, you only need to > get the original PDF file back. Then the annotations will either appear > magically in the PDF file, or you can figure out which new XML file is > created for this new PDF file, and copy the annotations from the old XML > file to the new XML file. > I tried this but this doesn't seem to work. I have the following things: 1) NetworkProgramming.pdf . This file is the replica of the file that i lost except that this old version doesn't have any annotations in it. Actually when i downloaded this file then i copied this file to another folder and then started adding annotation in that file. So this is the file i started with. 2) I have the xml files for the version that had a lot of annotations in it and which i lost. But i checked these xml files and almost all of them(AFAIK) have a very similar content inside them. For example the xml file contains information like the following: I had a lot of annotations in my pdf around 2 MB or so and looking at the content of the xml files it looks like they have very little to do with those annotations. Is this how Okular's xml format save annotation information for like underline, text etc? Each of these xml files takes around 800 bytes of space. This is what i did next: Step 1) I put the pdf file(with not annotation) in the same folder that i lost. Step 2) I opened a xml file from yesterday since i added a lot of annotations yesterday. The content of this xml file is what i have pasted above. Step 3) Next i opened the new version(that doesn't have any annotation) of the pdf with okular and found out the xml file that is created. Actually there were 4 new xml files that were created for this new version of pdf. Step 4) I pasted the content that i copied from yesterday's xml to this new xml and then save this xml file and closed the application(text editor). Step 5) I opened the pdf version with okular to see whether the yesterday's annotations were added but they aren't. What am i doing wrong? > To get the annotations actually in the PDF file, you will need to install a > newer version of Okular. It should offer you to migrate the annotations from > the XML file to the PDF file. > > I am surprised that the PDF file has been lost. Your Okular version should > theoretically not modify it... Yes if instead a temporary file were used to write and checked if the write was successful this problem could have been avoided. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #4 from Jason Liam --- (In reply to David Hurka from comment #3) > If you say you created at least X bytes worth of annotations, but you can’t > find a docdata file which is bigger than X bytes, I am afraid, you can not > recover the annotations. :( > These are the things i noticed: 1) I have 976 number of files correspoinding to the pdf i lost. By looking at the date/time of their modification i see that they range from 26 August 2021 to 28 September 2021. During this one month i added a lot of annotations every day. The pdf file that i started with originally(without annotation) is of 3.2 MB. Now when i was adding annotations everyday i noticed that the size of the pdf gets bigger and bigger everyday. And at the last day(28 August 2021) it was taking around 4.3 MB of space. So the size increased by around 1 MB during a span of one month. 2) Whenever i added some text annotation into my pdf lets say i added a text annotation saying "this is some example text annotation inside the pdf", i was able to press Ctrl+F and search for this particular string "this is some example text annotation inside the pdf" or "this is some" etc etc. This makes me wonder if the annotations that i was adding day by day were actually embedded inside the pdf instead of being in the xml files. I am not sure if the version of okular that i am using (1.3.3) have this embedded annotations feature. 3) Now to confirm that the xml files that i have have nothing to do with the annotations that i add and the annotations are actually embedded inside the pdf itself, i took this pdf lets say named MyBook.pdf. Now i checked the docdata folder to see(make sure) that there are no xml files corresponding to this pdf. So at this point i had no xml files corresponding to MyBook.pdf. Now i opened the MyBook.pdf using Okular and added some annotation like created a rectagle and added a text annotation saying "some xyz text for testing" and pressed Ctrl+S. Now i went back to the docdata folder and found that there are now 4 xml files corresponding to MyBook.pdf. When i right click on any of these xml files and see how much space each takes it is around 943 bytes(each). Now when i open all of them simultaneously in sublime text i see that they all have almost the same content and there is no tag for rectangle or the text annotations that i made. Below is the content inside one of the xml files: Now i am confused that if there is no need for xml files since they do not have anything to do with the annotations i add in the pdf then why are they created in the first place? What is the need of these xml files they do not correspond to the actual annotations that i make? Is this a bug in this version of okular 1.3.3. Just FYI the 4 files are named like follows: 3187327.MyBook.pdf.xml ... ... Moreover these files takes around 900 bytes each so they waste memory unnecessarily it seems. > Except there is another location where Okular stored annotations in these > days. It was definitifely an XML file. But as far as I remember, it was > these docdata files. > > > > I am surprised that the PDF file has been lost. Your Okular version should > > > theoretically not modify it... > > > > Yes if instead a temporary file were used to write and checked if the write > > was successful this problem could have been avoided. > > Okular should theoretically open a PDF file only for reading, not for > writing. So it should stay in its state on disk. > > But actually I remember a bug report where a PDF file has shrunken to 0 > bytes after a power outage. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445720] audio damaged for one/two syllables after beginning
https://bugs.kde.org/show_bug.cgi?id=445720 Liam Dawe changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||liamd...@gmail.com --- Comment #1 from Liam Dawe --- I'm damn sure this is the problem I have been having. Add video clips, record voice over in Audacity, add voice over clip and Kdenlive adds a random stutter/crack to the audio that is not in the source files. It makes it quite unusable and forced me to learn another video editor to get around it until it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445720] audio damaged for one/two syllables after beginning
https://bugs.kde.org/show_bug.cgi?id=445720 --- Comment #3 from Liam Dawe --- For me it happens with all packages. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445720] audio damaged for one/two syllables after beginning
https://bugs.kde.org/show_bug.cgi?id=445720 --- Comment #5 from Liam Dawe --- Okay same audio file in the same project, one being the suggested 16-bit PCM and I can confirm at least in this case, that newer file does not have the random crack in the audio. Would need plenty more testing though ofc but that's a good sign. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440405] Add the ability to copy & paste annotations
https://bugs.kde.org/show_bug.cgi?id=440405 --- Comment #4 from Jason Liam --- Hi, has this feature been added to okular? Maybe to a new testing branch. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440405] New: Feature Request: Copy-Past Different graphical Objects
https://bugs.kde.org/show_bug.cgi?id=440405 Bug ID: 440405 Summary: Feature Request: Copy-Past Different graphical Objects Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: New backend wishes Assignee: okular-de...@kde.org Reporter: jlame...@gmail.com Target Milestone: --- SUMMARY Hi i am using Okular 1.3.3 on Ubuntu 18.04. I have a feature request that i think will enhance users productivity while using Okular. Currently, when the user creates a graphical object lets say an ellipse or an underline obect then if he/she right clicks on that object then there is no "copy" option. Instead i(user) can see only three options which are "open popup note", "delete" and "properties". There should also be a copy option. After clicking on this "copy" option the user can/should be able to press Ctrl+V or "paste" and then that copied object should be pasted at that location. I am a regular user of Okular and use it very very frequently. Sometimes i create a lot of objects. And currently i have to create these object again and again, moreover the sizes of these object differ. So i have to manually change their size. Instead i want to be able to just copy and paste the object that i want. SOFTWARE/OS VERSIONS Ubuntu 18.04 OS: Linux (x86_64) release 5.4.0-77-generic -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440405] Feature Request: Copy-Paste Different graphical Objects
https://bugs.kde.org/show_bug.cgi?id=440405 Jason Liam changed: What|Removed |Added Summary|Feature Request: Copy-Past |Feature Request: Copy-Paste |Different graphical Objects |Different graphical Objects -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] New: Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 Bug ID: 435246 Summary: Okular Crashing While Opening pdf file with annotations Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jlame...@gmail.com Target Milestone: --- Created attachment 137256 --> https://bugs.kde.org/attachment.cgi?id=137256&action=edit No review F6 option t Hi i am used to working with pdfs in Okular. And everything was working fine but suddenly okular is not able to open the pdf file that i regularly make changes to. For example,just this morning i used okular to open my pdf file and added some annotations and stuff. And then after saving the file i closed the file. Now( afternoon) when i am trying to open the same file in okular, the file is not opening and i am getting the option to either force quit the app or wait. This is happening with this pdf only. Other pdfs are openings correctly. Also, the same pdf is also not opening in Document Viewer. Note that the size of the pdf is around 68 MB.Is there a way to see what is going wrong?, like debug okular. Also i installed okular through Ubuntu Software center. I am using Ubuntu 18.04. I have used okular regularly on the same file for a long time and i have never faced any issues but only today i am not able to open the file? How can i resolve this? Now i uninstalled okular by going to ubuntu software and then reinstalled it from there. But now i am facing one additional problem. Now there is no option to even annotate. Before there was F6 shortcut or we can go to Tools->Review but now F6 is not working, i am attaching the screenshot of this. Also the same old pdf is still not opening. Why is this issue happeing and how can i resolve this? I have very important annotations in the concerned pdfs. As you can see in the screenshot the review option is not selectable. Now i opened the same pdf file with okular and waited for a long time(around 1 hour) and noticed that some part(very little) like some annotations and other things are starting to appear. So why suddenly okular is not able to load the annotations and other things for this file? That is why is it taking so much time to load the annotations corresponding to this file? Edit: I guess i know what is the issue. The original file(without any annotations) is of size 50 MB and my annotated version is of 68 MB. So the problem seems to be with the large size of the file. For example i had saved a previous version of the same file(with annotations) which was of size 59 MB and okular is able to open that file correctly. But okular is not able to open the 68 MB file, i think the problem is with the too much annotations(around 18MB). How can i resolve this problem? I guess my final question is can i revert back the changes that i made today. Because in the morning the file and okular both seems to be working correctly. After adding some annotations the file size got larger and stopped working so i guess if i can delete the annotations that i made today i can still use the file. For this i will need to know where are those annotations files saved. And also in which format so that i can either delete or edit them accordingly. Also note that there is no F6 or review option in the newly downloaded version of okular to add annotations. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 Jason Liam changed: What|Removed |Added URL||https://askubuntu.com/quest ||ions/1328618/okular-not-abl ||e-to-display-pdf-file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 --- Comment #2 from Jason Liam --- It turns out that the pdf file was corrupt. When i tried to copy the file to an external drive or upload it to gmail, both failed. Also, i uninstalled and reinstalled okular and now F6 option is available again. More is described at https://askubuntu.com/questions/1328618/okular-not-able-to-display-pdf-file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 --- Comment #4 from Jason Liam --- The pdf file cannot be attached for 2 reasons: 1) Since it was corrupted, so it was not possible to attach that file or send or transfer it to anyone. The copy/paste operation itself failed. 2) Finally after trying many times to transfer that file to my other PC to see if it opens there and failing, i deleted that file. By the way, the error that i was getting was a standard error in Ubuntu 18.04 which opened a prompt saying "Okular isn't responding" Force quit or Wait. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 --- Comment #5 from Jason Liam --- Originally, the pdf file was of 50 MB, after adding annotations worth of 18MB, the pdf size was around 68.5 MB. Also, just before the file became corrupt, i was adding an inline note that contained a lot of text.For example that one particular inline note had around 38 numbered points. Like step 1) this is step one blah blah blah. step 2) this is step two blah blah blah. ... ... ... step 38).Some explanation here as well. And each step has a lot of explanations as well . Can this be the cause of corruption of the pdf? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435246] Okular Crashing While Opening pdf file with annotations
https://bugs.kde.org/show_bug.cgi?id=435246 --- Comment #7 from Jason Liam --- I think i accidentally reproduced the bug. I had previously backed up my pdf file. I remember that when i downloaded the original pdf file from web (without any annotations) it was of size 50 MB. Also my backedup up pdf file (with annotations) is around 67 MB. So no after downloading the backed up file(67 MB) i started adding annotations in it. When this file reached around 67.8 MB i clicked Ctrl+S to save the file. But for some reason my Ubuntu 18.04 started freezing and the file was not saved(which i can see from the * shown at the top). So i had to close okular midway with unsaved changes. Next, after closing okular i tried to open the pdf but to my surprise when the pdf opened, all of its pages were blank. The second thing i noticed was that the same pdf was now of size 50MB instead of 67MB. So i do not know why the pdf got smaller in size(around its original size) and had all of its pages blank. This could be the fault of freezing up of the PC or an okular bug. I have no idea. Maybe if there's a way to debug okular so that i can see what happens when i click Ctrl+S , that can shed some light on this. Is there a way to use okular from command line. I know that i can use the command okular somedpdf.pdf to open the pdf in okular.But this command does not give much info about what happens when i click Ctrl+S. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 447015] New: Ability to Increase(increment) Inline Note's Height Graphically
https://bugs.kde.org/show_bug.cgi?id=447015 Bug ID: 447015 Summary: Ability to Increase(increment) Inline Note's Height Graphically Product: okular Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: New backend wishes Assignee: okular-de...@kde.org Reporter: jlame...@gmail.com Target Milestone: --- SUMMARY *** I want to know if there is a way to increase(change) the height of the inline note's box programatically. For example, currently to increase the height of the inline note's box, i drag the upper or lower part of the inline note's box according to my needs. The problem with this approach is that i am not able to make the height of the inline note's box equal to the the size of the current page. So i want to know if there is any other way of increasing the height by entering some numbers like 455 or 200. Maybe there is some graphical way of doing this. By graphical way i mean that by right clicking on the inline note's box and then going into the Properties option, there may be a option to increment the height by 1px or 2px just like there is option to increment the Border width. And if this is not possible with graphical way then can we do this programatically? *** I am using Okular version 1.3.3 with Ubuntu 18.04 x86-64. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490853] New: Stop applications stealing focus when typing
https://bugs.kde.org/show_bug.cgi?id=490853 Bug ID: 490853 Summary: Stop applications stealing focus when typing Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: liamd...@gmail.com Target Milestone: --- Happens across an KDE version. Say you click a bunch of programs from your panel to load, and then you go back to typing away in your web browser. Those applications will come to the front, in the way of what you were doing and steal focus. It's incredibly annoying from a usability point of view, and could even end up causing security issues. Say you're entering a password into something but you loaded a chat app, and boom it arrives to the front and you've sent your password to the chat instead. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=364593 Liam Dawe changed: What|Removed |Added CC||liamd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=364593 Liam Dawe changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- --- Comment #20 from Liam Dawe --- Not sure why this was set as resolved, it's clearly not. I would also like to track this, as it's such a crazy issue to have. Forcing people to use terminal to shut down, after updating NVIDIA is not going to win us over an users. Something really needs to be done about this. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 397931] New: Windows download link on main site 404s
https://bugs.kde.org/show_bug.cgi?id=397931 Bug ID: 397931 Summary: Windows download link on main site 404s Product: konversation Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: l...@ldaws.com Target Milestone: --- Binary factory now only has an unstable build for Windows - the download link for Windows from the Konversation site points to the stable build job which no longer exists. (https://binary-factory.kde.org/job/konversation-stable-win32/) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM
https://bugs.kde.org/show_bug.cgi?id=359327 Liam Dawe changed: What|Removed |Added CC||liamd...@gmail.com --- Comment #25 from Liam Dawe --- To confirm I also have this same issue, here's a video to show you it happening: https://www.youtube.com/watch?v=tz_zEV9o-Ig This is on an up to date Arch install. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 497029] New: Notes outputs backwards
https://bugs.kde.org/show_bug.cgi?id=497029 Bug ID: 497029 Summary: Notes outputs backwards Classification: Applications Product: LabPlot2 Version: 2.0.1 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: liammis...@hotmail.com Target Milestone: --- Within any of my projects, opening and writing in a "notes" tab (in windows and Mac) has a strange bug where the text is output backwards. STEPS TO REPRODUCE 1. Open Labplot2 2. New Note 3. type OBSERVED RESULT Text is output backwards, from the left hand corner. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Yes macOS: Yes ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems
https://bugs.kde.org/show_bug.cgi?id=366285 Liam Murphy changed: What|Removed |Added CC||l...@lpmdesigns.com --- Comment #3 from Liam Murphy --- I am also having this issue. I have a dual boot with Windows, but separate SSD's for Windows and Linux. I've attempted manual partition editing, and the default "erase disk" and let Neon do the work. Getting same GRUB Minimal screen after rebooting when the install is complete. I get no errors during the install. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366285] System is unable to boot after installing a new copy of KDE neon in UEFI enabled systems
https://bugs.kde.org/show_bug.cgi?id=366285 --- Comment #6 from Liam Murphy --- (In reply to J Janz from comment #4) > Thank God I happened to have an image of a few weeks ago > (neon-useredition-20160713-1223-amd64.iso) and that one installed with no > erros, same as current one, but installed system boots and works ok! Updated > (even got plasma 5.7.3 last night) and still alright (well, just that sound > never came up with onboard HDMI and AMD R9 270, also through HDMI, only goes > from boot splash to dead black screen but I guess those are separate bugs). > > Well, now I'm hoping that having a closer date to where things were still on > track might help to find a related change from then to current version and > it can be fixed or reverted. Janz, any possibility of us getting that image? I would really like getting Neon on my machine. That does make me think, Neon did indeed use to work a month or two ago on this same machine. -- You are receiving this mail because: You are watching all bug changes.
