[systemsettings] [Bug 486882] System settings ugly screen preview
https://bugs.kde.org/show_bug.cgi?id=486882 Theo Grueninger changed: What|Removed |Added Version|unspecified |6.0.4 Platform|Other |unspecified -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486882] System settings ugly screen preview
https://bugs.kde.org/show_bug.cgi?id=486882 --- Comment #1 from Theo Grueninger --- Created attachment 169373 --> https://bugs.kde.org/attachment.cgi?id=169373=edit system settings wallpaper -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486882] New: System settings ugly screen preview
https://bugs.kde.org/show_bug.cgi?id=486882 Bug ID: 486882 Summary: System settings ugly screen preview Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: theo.gruenin...@web.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 169372 --> https://bugs.kde.org/attachment.cgi?id=169372=edit System settings arrange screens preview SUMMARY In the system settings for the monitors there is a preview for arranging the monitors that doesn't look like KDE Plasma 6, but maybe like Plasma 4. The color gradient makes it look very old. This preview of the monitors is also present in the new wallpaper settings. STEPS TO REPRODUCE 1. Open system settings 2. Go to "Display and Monitor" or "Wallpaper" OBSERVED RESULT Very ugly and old looking preview of the screens EXPECTED RESULT Modern and Plasma 6-like preview of the screens SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 481144] import tracker impossible, neither from homebank (TAG / ETIQUETTE) nor from a .csv file
https://bugs.kde.org/show_bug.cgi?id=481144 --- Comment #4 from theo --- Bonsoir Stéphane, Réaction supersonique ! /Et trop rapide de ma part ! Correction :/ Ci-dessous marche (enfin) *pour HomeBank* et NON pour skrooge ... Pour import d'un .csv : cela marche enfin (!) avec TAG comme nom du champ et un nombre correct de séparateurs. Ci-joint 3 fichiers : Stephane.xhb, Stephane.skg et Acc.csv, ce dernier essayé d'importer avec en-têtes Tracker & Etiquette. Cdt, Theo PS : Je suis d'origine un NL, depuis 10 ans en France; belle lange que je maîtrise partiellement. Le 09/02/2024 à 21:41, Stephane MANKOWSKI a écrit : > https://bugs.kde.org/show_bug.cgi?id=481144 > > Stephane MANKOWSKI changed: > > What |Removed |Added > > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Stephane MANKOWSKI --- > Hi, > > Could you provide me a minimalist xhb file with a tag to reproduce the > issue ? > -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 481144] import tracker impossible, neither from homebank (TAG / ETIQUETTE) nor from a .csv file
https://bugs.kde.org/show_bug.cgi?id=481144 --- Comment #2 from theo --- Bonsoir Stéphane, Réaction supersonique ! Mes excuses pour import d'un .csv : cela marche enfin (!) avec TAG comme nom du champ et un nombre correct de séparateurs. Par contre à partir d'un .xhb, non. Ci-joint un maigre fichier qui, j'espère, vous sera utile. Cdt, Theo PS : Je suis d'origine un NL, depuis 10 ans en France; belle lange que je maîtrise partiellement. Le 09/02/2024 à 21:41, Stephane MANKOWSKI a écrit : > https://bugs.kde.org/show_bug.cgi?id=481144 > > Stephane MANKOWSKI changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Stephane MANKOWSKI --- > Hi, > > Could you provide me a minimalist xhb file with a tag to reproduce the issue ? > -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 481144] New: import tracker impossible, neither from homebank (TAG / ETIQUETTE) nor from a .csv file
https://bugs.kde.org/show_bug.cgi?id=481144 Bug ID: 481144 Summary: import tracker impossible, neither from homebank (TAG / ETIQUETTE) nor from a .csv file Classification: Applications Product: skrooge Version: 2.30.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: theo.ra...@gmail.com Target Milestone: --- SUMMARY *** *** STEPS TO REPRODUCE 1. import from a .xhb file or .csv file 2. check field TRACKER 3. empty, not loaded OBSERVED RESULT field TRACKER not filled EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: WSL / UBUNTU KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 457791] Krusader do not open ISO files
https://bugs.kde.org/show_bug.cgi?id=457791
Theo changed:
What|Removed |Added
CC||alpha0...@yahoo.de
--- Comment #6 from Theo ---
I can confirm the problem under openSUSE Tumbleweed, kio_iso version
2.99.40git560~e1988e9-122.1 [1]. Following Guidelines and HOWTOs [2], I find
that kioslave5 aborts with a segmentation fault:
$ export KDE_SLAVE_DEBUG_WAIT=iso
$ krusader # press Enter on ISO image file
kioslave5: 'gdb kioslave5 16493' to debug
kioslave5: 'kill -SIGCONT 16493' to continue
$ gdb kioslave5 16493
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
QObject::thread (this=0x0) at kernel/qobject.cpp:1520
1520return d_func()->threadData.loadRelaxed()->thread.loadAcquire();
(gdb) backtrace
#0 QObject::thread (this=0x0) at kernel/qobject.cpp:1520
#1 0x7f6721935b87 in KIO::SlaveBase::SlaveBase (this=,
protocol=..., pool_socket=..., app_socket=..., this=,
protocol=...,
pool_socket=..., app_socket=...) at
/usr/src/debug/kio-5.100.0/src/core/slavebase.cpp:266
#2 0x7f6721a39c01 in kio_isoProtocol::kio_isoProtocol
(app="local:/run/user/1000/krusaderJXESmB.2.slave-socket" = {...},
pool= "",
this=0x7ffd6b6611b0) at
/usr/src/packages/BUILD/krusader-2.99.40git560~e1988e9/plugins/iso/iso.cpp:72
#3 kdemain (argc=, argv=) at
/usr/src/packages/BUILD/krusader-2.99.40git560~e1988e9/plugins/iso/iso.cpp:50
#4 0x55bbc8fbd370 in main (argc=5, argv=0x7ffd6b661418) at
/usr/src/debug/kio-5.100.0/src/kioslave/kioslave.cpp:152
[1] https://build.opensuse.org/package/show/KDE:Unstable:Extra/krusader
[2]
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves
--
You are receiving this mail because:
You are watching all bug changes.
[kactivitymanagerd] [Bug 462008] if you change the activity (select from background image with accent color on) then a short flickering is shown before he changes the activity
https://bugs.kde.org/show_bug.cgi?id=462008 Theo Grueninger changed: What|Removed |Added CC||theo.gruenin...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 462008] New: if you change the activity (select from background image with accent color on) then a short flickering is shown before he changes the activity
https://bugs.kde.org/show_bug.cgi?id=462008 Bug ID: 462008 Summary: if you change the activity (select from background image with accent color on) then a short flickering is shown before he changes the activity Classification: Plasma Product: kactivitymanagerd Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: theo.gruenin...@web.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 153873 --> https://bugs.kde.org/attachment.cgi?id=153873=edit Shows the bug in a short clip SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Change the activity with press Meta + Tab on Desktop OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 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.
[kwin] [Bug 461124] Broken icons and fonts when using 2 monitors with different resolutions via integrated and discrete graphics card in Arch Linux, xorg
https://bugs.kde.org/show_bug.cgi?id=461124 Martel Theo changed: What|Removed |Added CC||martelt...@gmail.com --- Comment #2 from Martel Theo --- I have the exact same visual problem, with a slightly different configuration : Laptop with one monitor on the iGPU, and an external monitor on the Nvidia dGPU (both same resolution), running latest Arch Linux. When I launch the plasma session with both screen active, I don't have any icons on the desktop, and the font used for the Window title is changed (and any change using the Fonts menu in the system parameters app doesn't have any effect). If I launch the plasma session with the external monitor unplugged, and only plug it afterwards, I keep the icons, but the font of all window titles immediately changes (and cannot be changed). The only relevant (?) line I could find in journalctl when I plug the external monitor is : ' kwin_x11[935]: Failed to compute left/right minimum bearings for "mtx" ' (mtx beeing the font that is forced used on the titles). The problem appeared with the update to Plasma 5.26, Plasma 5.25.x was working correctly. I tried downgrading Mesa to the version before (22.1.7, from mid-August), but I didn't change anything. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 452661] New: Falkon frozen while autosaving the running session
https://bugs.kde.org/show_bug.cgi?id=452661 Bug ID: 452661 Summary: Falkon frozen while autosaving the running session Product: Falkon Version: 22.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- STEPS TO REPRODUCE 1. Use Falkon with many tabs. 2. Open new tab. OBSERVED RESULT After a few seconds Falkon autosaves the running session into the file session.dat under the profile directory. Falkon freezes until the saving has finished. EXPECTED RESULT The application should stay usable when doing background tasks the user cannot control. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439180] Make the number of often uses applications configurable
https://bugs.kde.org/show_bug.cgi?id=439180 --- Comment #1 from Theo --- (In reply to Theo from comment #0) > For me, the 14 most used applications are shown Apparently, this number depends on the cached score of the applications. If the score of an app is below a certain relative threshold, it will not be shown in the menu/dashboard. This is definitely not the desired behavior for me. I don't want an often used application to never show up because it is used less frequently than the top most used applications. This is the command I use to check the score: $ sqlite3 -header -column $HOME/.local/share/kactivitymanagerd/resources/database "SELECT targettedResource,cachedScore FROM ResourceScoreCache WHERE initiatingAgent IS 'org.kde.plasma.kicker' ORDER BY cachedScore DESC;" | less -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 439190] New: Command line option --profile has no effect on an already running instance
https://bugs.kde.org/show_bug.cgi?id=439190 Bug ID: 439190 Summary: Command line option --profile has no effect on an already running instance Product: Falkon Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- SUMMARY The command line option '--profile' is ignored if there are running instances with the default profile and the target profile. STEPS TO REPRODUCE 1. Start Falkon with default profile: $ falkon 2. Start a second instance with another profile: $ falkon --no-remote --profile test 3. Try to control the second instance from the command line: $ falkon --profile test --new-tab www.falkon.org $ falkon --profile test --fullscreen OBSERVED RESULT The commands apply to the first instance using the default profile. EXPECTED RESULT The commands should observe the option '--profile' and apply to the second instance using the profile 'test'. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 438254] unending loading process
https://bugs.kde.org/show_bug.cgi?id=438254 Theo changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #2 from Theo --- Looks like a duplicate of bug 434203. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439180] New: Make the number of often uses applications configurable
https://bugs.kde.org/show_bug.cgi?id=439180 Bug ID: 439180 Summary: Make the number of often uses applications configurable Product: plasmashell Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: alpha0...@yahoo.de CC: plasma-b...@kde.org Target Milestone: 1.0 The Application Menu/Dashboard can be configured to show often used applications but there seems to be no way to configure the number of items that are shown. For me, the 14 most used applications are shown on the Application Dashboard and I would like to increase this number. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439179] New: Applications started from the search do not score as often used
https://bugs.kde.org/show_bug.cgi?id=439179 Bug ID: 439179 Summary: Applications started from the search do not score as often used Product: plasmashell Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: alpha0...@yahoo.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Applications that are started from the search function in the Application Menu/Dashboard do not get their cached score updated. This means the applications will not qualify to be shown in the often used application menu, no matter how often they are used over the search. STEPS TO REPRODUCE 1. Pick an application and check the cached score in the resource score cache. 2. Start the application from the search in Application Menu (Kicker) or the Application Dashboard. 3. Check the cached score again. OBSERVED RESULT The cached score is unchanged. EXPECTED RESULT The cached score should increase. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20210524 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I use the following command to check the score of often used applications: $ sqlite3 -header -column $HOME/.local/share/kactivitymanagerd/resources/database "SELECT targettedResource,cachedScore FROM ResourceScoreCache WHERE initiatingAgent IS 'org.kde.plasma.kicker' ORDER BY cachedScore DESC;" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439178] New: Often used favorites decrease number of often used applications in menu
https://bugs.kde.org/show_bug.cgi?id=439178 Bug ID: 439178 Summary: Often used favorites decrease number of often used applications in menu Product: plasmashell Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: alpha0...@yahoo.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The number of often used applications that are shown in the Application Menu/Dashboard depends on how many favorites score as most used applications in the "resource score cache". In the following, I assume that 14 is the hard coded maximum number of often used applications shown in the menu. STEPS TO REPRODUCE 1. Start with no favorites and more than 14 applications with a score in the resource score cache. 2. Set (for example) 12 of the often used applications shown in the menu as favorites. OBSERVED RESULT Only 2 applications are shown as often used and no more than that, no matter how high the cached score of any other application is. EXPECTED RESULT The menu should show the configured number of often used applications, or less only if there are not enough applications recorded in the cache. It makes sense to exclude often used favorites from the often used application selection, but this shouldn't decrease the total number of often used applications shown in the menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20210524 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I use the following command to check the score of often used applications: $ sqlite3 -header -column $HOME/.local/share/kactivitymanagerd/resources/database "SELECT targettedResource,cachedScore FROM ResourceScoreCache WHERE initiatingAgent IS 'org.kde.plasma.kicker' ORDER BY cachedScore DESC;" -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 416844] New: Media with audio does no play (after update to Qt 5.14?)
https://bugs.kde.org/show_bug.cgi?id=416844 Bug ID: 416844 Summary: Media with audio does no play (after update to Qt 5.14?) Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- Any media with audio refuses to play. It doesn't play silently, it does not play at all. This affects YouTube and SoundCloud, for instance. The problem appeared after the update of Qt from 5.13.1 to 5.14 on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407155] Some widgets on the desktop move to different locations on boot or after plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=407155 --- Comment #3 from Theo Launay --- Thanks you so much ! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 408518] New: [Vertical Tabs] Duplicate tab opens at bottom instead of next to current tab
https://bugs.kde.org/show_bug.cgi?id=408518 Bug ID: 408518 Summary: [Vertical Tabs] Duplicate tab opens at bottom instead of next to current tab Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- "Duplicate tab" after right-click on a tab opens the new tab at the bottom of the vertical tab tree. It should open below the duplicated tab in the tab tree. In the horizontal tab bar the new tab appears, as expected, next to the duplicated tab. Note that this is a similar problem as in https://bugs.kde.org/show_bug.cgi?id=393656. New tabs are opened next to the current in the horizontal tab bar but at the bottom of the vertical side bar. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396609] Google translation bar bookmarklet does not work
https://bugs.kde.org/show_bug.cgi?id=396609 --- Comment #5 from Theo --- (In reply to Juraj from comment #4) > - Remove: v.style.display='none'; >It will display some selectbox to manually trigger translating > - Use the select box to trigger the translating, the translate bar will > appear I confirm that this workaround works as described, and here is an interesting observation: once this workaround has been applied and a page has been translated, the original bookmarklet works now on any page on the same site, but only as long as I don't click "Show original" in the translation bar. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396609] Google translation bar bookmarklet does not work
https://bugs.kde.org/show_bug.cgi?id=396609 Theo changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #3 from Theo --- The translation bookmarklet still doesn't work for me in Falkon 3.1.0. The_assassin's example works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407155] New: Weather widget moves by itself at boot
https://bugs.kde.org/show_bug.cgi?id=407155 Bug ID: 407155 Summary: Weather widget moves by itself at boot Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Weather Assignee: kosse...@kde.org Reporter: launat...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Each time I boot Kubuntu, the weather widget moves by itself somewhere else. Graphical components are locked. STEPS TO REPRODUCE 1. Boot OS. OBSERVED RESULT Weather widget moves by itself. EXPECTED RESULT it shouldn't move. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Already happened on Kubuntu 18.10 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396609] New: Google translation bar bookmarklet does not work
https://bugs.kde.org/show_bug.cgi?id=396609
Bug ID: 396609
Summary: Google translation bar bookmarklet does not work
Product: Falkon
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: alpha0...@yahoo.de
Target Milestone: ---
The bookmarklet for the Google translation bar found on
https://googlesystem.blogspot.com/2009/11/google-translation-bar.html works in
Firefox, but not in Falkon. It doesn't work for me in Chrome/Chromium either,
but there you have this functionality built-in. Can the bookmarklet be made to
work in Falkon? Note that you have to replace "http" by "https" to make it work
in Firefox:
javascript:{d=document;b=d.body;o=d.createElement('scri'+'pt');o.setAttribute('src','https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit');o.setAttribute('type','text/javascript');b.appendChild(o);v=b.insertBefore(d.createElement('div'),b.firstChild);v.id='google_translate_element';v.style.display='none';p=d.createElement('scri'+'pt');p.text='function%20googleTranslateElementInit(){new%20google.translate.TranslateElement({pageLanguage:%22%22},%22google_translate_element%22);}';p.setAttribute('type','text/javascript');b.appendChild(p);}void%200
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023 --- Comment #13 from Theo --- (In reply to Nikita Melnichenko from comment #10) > If you feel there is a bug in > KCompressionDevice implementation, could you please file a bug against the > product "frameworks-karchive" to discuss with the devs? Here it is: https://bugs.kde.org/show_bug.cgi?id=395471 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 395296] [kio_iso] Reading files on ISO images reads the ISO image file from the beginning
https://bugs.kde.org/show_bug.cgi?id=395296 --- Comment #4 from Theo --- (In reply to Nikita Melnichenko from comment #3) > Currently I can't confirm the bug. I browse a >1Gb iso file, read files in > it and IO monitor doesn't show any huge activity. Can you elaborate on this? > Is it possible to confirm without debugging the read calls? The problem should be obvious from the time it takes to load a file from the ISO iamge. I can also see it by monitoring Disk Troughput//Rate/Read Data in KDE System Monitor. I should mention that I need to do $ echo 3 > /proc/sys/vm/drop_caches after each try if the image file is only 1GB or so in size. Otherwise, the data will come from the cache. I noticed the problem first with a 3.4 GB ISO, which is too big to be cached: http://distfiles.gentoo.org/releases/x86/12.0/livedvd-x86-amd64-32ul-2012.iso (this one is detected as MIME type "text/plain", see https://bugs.freedesktop.org/show_bug.cgi?id=80877). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 395296] [kio_iso] Reading files on ISO images reads the ISO image file from the beginning
https://bugs.kde.org/show_bug.cgi?id=395296
--- Comment #2 from Theo ---
(In reply to Theo from comment #1)
> else if ("model/x.stl-binary") {
Obviously, this must read
else if ("model/x.stl-binary" == mimtype) {
but this turns out to not work that well after all because MIME type detection
seems to be unreliable, even if we ignore the false detection as
"model/x.stl-binary", which, as opposed to my earlier claim, has been fixed
recently:
https://bugs.freedesktop.org/show_bug.cgi?id=106330#c21
Testing some more ISO images, I came across a image file that is detected as
"text/plain", while others are correctly detected as "application/x-cd-image"
by kmimetypefinder5, but are passed as "application/octet-stream" to
KIso::prepareDevice in iso/kiso.cpp. So to make it work with all of my sample
ISOs, I used the following atrocity:
else if ("model/x.stl-binary" == mimetype ||
"application/octet-stream" == mimetype ||
"text/plain" == mimetype) {
setDevice(new QFile(filename));
}
I think KIso::KIso and KIso::prepareDevice (kiso.cpp) need some attention by
someone who knows how to handle MIME type detection. Right now it seems to be
quite a mess: Why is KIso::KIso considering compressed tar filed? Why does it
care about KOffice docs? Why are gzip and bzip2 treated explicitly, as opposed
to xz, which also works? Why are ISOs detected as "application/octet-stream",
although kmimetypefinder5 sees them as "application/x-cd-image"?
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-karchive] [Bug 395471] KCompressionDevice seeks to wrong position
https://bugs.kde.org/show_bug.cgi?id=395471 --- Comment #1 from Theo --- (In reply to Theo from comment #0) > which can be fixed by > preceding any seek with seek(0): > > https://bugs.kde.org/show_bug.cgi?id=372023#c9 I am mistaken here. It only fixes one of the two problems described in that bug report. The other problem is fixed by resetting the offset to 0 when opening the device: https://bugs.kde.org/show_bug.cgi?id=372023#c8 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023 --- Comment #11 from Theo --- (In reply to Theo from comment #9) > The following workaround fixes both the incomplete file listing > and the wrong file data on the first try (makes my previously posted fix > unnecessary): Insert > > dev->seek(0); I'm afraid I was wrong about that. This only fixes the directory listing. For the correct file data on the first try the previous fix from comment #8 is required. (I think I accidentally kept the changes from the first fix while testing the second fix.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 395471] New: KCompressionDevice seeks to wrong position
https://bugs.kde.org/show_bug.cgi?id=395471 Bug ID: 395471 Summary: KCompressionDevice seeks to wrong position Product: frameworks-karchive Version: 5.46.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: alpha0...@yahoo.de CC: kdelibs-b...@kde.org Target Milestone: --- Disclaimer: I don't have a full understanding of anything I'm going to talk about, so this bug may as well be a case of wrong usage or a lack of documentation. There is a problem with kio_iso that is caused by receiving data from KCompressionDevice from the wrong offset position, and which can be fixed by preceding any seek with seek(0): https://bugs.kde.org/show_bug.cgi?id=372023#c9 As I understand it, KCompressionDevice and its Filter's QFileDevice both inherit a 'pos' and 'devicePos' member variable from QFileDevice. My investigation of the kio_iso bug revealed that these two sets of variables get out of sync, so that the data coming from the QFileDevice does not correspond to the offset position stored in KCompressionDevice's 'pos' variable. In case this is not a bug in KCompressionDevice, is there some sort of documentation available that explains how one is supposed to avoid a situation like that? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 395296] [kio_iso] Reading files on ISO images reads the ISO image file from the beginning
https://bugs.kde.org/show_bug.cgi?id=395296
--- Comment #1 from Theo ---
(In reply to Theo from comment #0)
> Would QFile[2] be a better alternative for uncompressed image
> files?
This seems to work for me. With the following I don't have to wait an
unacceptable amount of time every time I open a file from a big ISO image: I
added the lines
else if ("model/x.stl-binary") {
setDevice(new QFile(filename));
}
after
if ("inode/blockdevice" == mimetype)
setDevice(new QFileHack(filename));
in
void KIso::prepareDevice(const QString & filename,
const QString & mimetype, bool forced)
in kiso.cpp. The mime type of ISO files is actually "application/x-cd-image",
but there is an unfixed bug[1] that causes them to be wrongly detected as
"model/x.stl-binary", so I used this for my test.
[1] https://bugs.freedesktop.org/show_bug.cgi?id=99421#c15
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023
--- Comment #9 from Theo ---
(In reply to Theo from comment #8)
> This does not fix the issue of missing files in the directory listing,
> compare for instance the contents of '/ISO9660' and '/El Torito BootJoliet
> level 3' when browsing sgd_cdrom_1.30.iso as archive.
This is caused by the same problem: KCompressionDevice and its QFile, both
derived from QIODevice, have member variables 'pos' and 'devicePos' that get
out of sync. The following workaround fixes both the incomplete file listing
and the wrong file data on the first try (makes my previously posted fix
unnecessary): Insert
dev->seek(0);
before
if (dev->seek((qint64)start << (qint64)11)) {
if ((dev->read(buf, len << 11u)) != -1) return (len);
}
in the callback function 'readf' in kiso.cpp. This seek is done in
KCompressionDevice::seek(qint64 pos) only in some cases, see
kcompressiondevice.cpp[1]:
if (d->deviceReadPos < pos) { // we can start from here
[...]
} else {
// we have to start from 0 ! Ugly and slow, but better than the
previous
// solution (KTarGz was allocating everything into memory)
if (!seek(0)) { // recursive
return false;
}
[...]
}
Apparently, this is considered ugly, but I start to believe that
KCompressionDevice is broken, and unless someone explains to me why I'm wrong
and how KCompressionDevice is supposed to work I see no other way to fix this
(again, I'm not a developer and might have no clue what I'm talking about).
Ceterum censeo KCompressionDevice should not be used on uncompressed ISO files
anyway: https://bugs.kde.org/show_bug.cgi?id=395296
[1]
https://api.kde.org/frameworks/karchive/html/kcompressiondevice_8cpp_source.html#l00178
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 395296] New: [kio_iso] Reading files on ISO images reads the ISO image file from the beginning
https://bugs.kde.org/show_bug.cgi?id=395296 Bug ID: 395296 Summary: [kio_iso] Reading files on ISO images reads the ISO image file from the beginning Product: krusader Version: 2.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: alpha0...@yahoo.de CC: krusader-bugs-n...@kde.org Target Milestone: --- Loading file data from an ISO image via the ISO KIO Slave reads the ISO image file from the beginning every time. For big image files this is a huge waste of time and resource. The cause seems to be the usage of KArchives's KCompressionDevice[1], for which the authors have not bothered to implement a random access mechanism. Instead, seeks are realized as reads from the beginning. Would QFile[2] be a better alternative for uncompressed image files? [1] https://api.kde.org/frameworks/karchive/html/classKCompressionDevice.html [2] http://doc.qt.io/qt-5/qfile.html -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394938] Can't run .desktop files
https://bugs.kde.org/show_bug.cgi?id=394938 Theo changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||alpha0...@yahoo.de --- Comment #2 from Theo --- Can confirm that Krusader in normal mode opens with associated application, even when I select "Run" in drop down menu. I'm not sure if I like what Dolphin is doing to the .desktop file: when I choose "Execute", Dolphin changes the content of the file by prepending "#!/usr/bin/env xdg-open" and modifies permissions without asking. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023
--- Comment #8 from Theo ---
(In reply to Nikita Melnichenko from comment #7)
> if you feel like you can
> help figuring out the reason, you're more than welcome to do this. I can
> help you with the debugging setup, etc.
What would this setup roughly look like? Using my distributor's
debuginfo/debugsource packages and investigating with GDB, I can say the
following so far (note that I might not really know what I'm doing here, and
that I can provide details on my findings if necessary):
kio_iso uses KArchive's KCompressionDevice[1] to access the ISO file. The
device is created in KIso::prepareDevice and KCompressionDevice's constructor
creates a QIODevice and a QFileDevice. The corresponding *Private devices have
separate sets of member variables 'pos' and 'devicePos' that get out of sync
when the QFileDevice is closed at the end of KIso::openArchive. The QFileDevice
is reset to offset zero while QIODevice keeps the offset positions it has after
reading the ISO file system. When the ISO file is opened for reading the file
data, QFileDevice's offset positions are treated as if they haven't been reset
and subsequent seeks fall short of the requested offset.
Now I don't know whether QIODevice's offset should be reset when the
QFileDevice is closed after reading the file system or when it is opened for
reading the requested file data, but I tried the latter after reading the
following in the Qt documentation:
"When subclassing QIODevice, you must call QIODevice::seek() at the start of
your function to ensure integrity with QIODevice's built-in buffer."[2]
Replacing
if (size && !m_isoFile->device()->isOpen())
m_isoFile->device()->open(QIODevice::ReadOnly);
by
if (size && !m_isoFile->device()->isOpen()) {
m_isoFile->device()->open(QIODevice::ReadOnly);
m_isoFile->device()->seek(0);
}
in kio_isoProtocol::getFile (iso/iso.cpp) seems to work and I get the correct
file data on the first try.
This does not fix the issue of missing files in the directory listing, compare
for instance the contents of '/ISO9660' and '/El Torito BootJoliet level 3'
when browsing sgd_cdrom_1.30.iso as archive.
Regarding my question about reading through a lot of data when requesting file
data, it seems that the problem here is kio_iso's use of KCompressionDevice for
uncompressed ISO files. KCompressionDevice does not seem to support random
access and a seek is implemented as a read from the beginning, even for
uncompressed files. This seems like a really stupid idea since ISO files tend
to be big and should be read with a method that supports random access.
[1] https://api.kde.org/frameworks/karchive/html/classKCompressionDevice.html
[2] http://doc.qt.io/qt-5/qiodevice.html#seek
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 395112] Empty bar graph in Wayback Machine's calendar view
https://bugs.kde.org/show_bug.cgi?id=395112 --- Comment #3 from Theo --- (In reply to David Rosca from comment #2) > It does use QtWebEngine, not QtWebKit. That makes more sense (given that I even mentioned QtWebEngineProcess in my comment). For the record: Qt WebEngine was updated from 5.10.1 to 5.11.0 (openSUSE Tumbleweed libqt5-qtwebengine). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395112] Empty bar graph in Wayback Machine's calendar view
https://bugs.kde.org/show_bug.cgi?id=395112 --- Comment #1 from Theo --- Funny story: after an update (including libQt5WebKit5 5.212~alpha2) this problem is gone. (Unrelated: I'm also pleasantly surprised that there is no longer a QtWebEngineProcess for every unloaded restored tab when Falkon loads the last session on start. This saves a lot of memory when there are many tabs.) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395112] New: Empty bar graph in Wayback Machine's calendar view
https://bugs.kde.org/show_bug.cgi?id=395112 Bug ID: 395112 Summary: Empty bar graph in Wayback Machine's calendar view Product: Falkon Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- See for example https://web.archive.org/web/*/falkon.org. The time line at the top misses grid lines and the bars that indicate how often the page has been saved. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394757] Tab bar jumps when tab is selected first time after start
https://bugs.kde.org/show_bug.cgi?id=394757 --- Comment #5 from Theo --- There is the same problem with the KrViewer's tab bar, only worse. When I try to scroll to the right, the tabs will jump back immediately, making it impossible to access the tabs that are out of view. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #48 from Theo --- (In reply to rlk from comment #45) > So interestingly enough if I click on the device notifier icon its window > *does* pop up. So what's the difference between the device notifier and the > application menu? It gets more interesting. When I click first on the activity manager widget, which also works, and then on the app launcher, the app launcher will not be suppressed. Or the app launcher might be working just fine after I have restarted plasmashell... This erratic behavior made me think for months that this is just another quirk of the buggy plasmashell and not some interference with an incompatible setting. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023 --- Comment #6 from Theo <alpha0...@yahoo.de> --- (In reply to Nikita Melnichenko from comment #5) > (In reply to Theo from comment #4) > > It happens with every ISO image I try. I did a test with a small sample size > > of ISO images and the data offset seems to be off by the same sector count > > on the first try for a given ISO. I got 52, 64, and 80 2K sectors ahead for > > three different CDs/DVDs. > > How did you determine this? By brute force. I opened a file on the ISO with Okteta using iso:/, copied the first 16 bytes of binary garbage in hex format, then fed this into a binary grep on the whole ISO image to get the offset. The same for the correct data after reloading the file. I did this for more than one file for every tested ISO image. I use https://github.com/tmbinc/bgrep for the binary grep, but it should also be possible to use standard grep (or some other method), albeit not as fast: https://stackoverflow.com/questions/4180081/binary-grep-on-linux/17168777#17168777 Example: $ okteta iso:/home/user/sgd_cdrom_1.30.iso/ISO9660/grubdetect.lua $ bgrep -A 20 C78508FFC7850CFF sgd_cdrom_1.30.iso | sed 's/\\x//g' sgd_cdrom_1.30.iso: 00042800 c78508ffc7850cff0080 sgd_cdrom_1.30.iso: 00042872 c78508ffc7850cff In this case I have to use "-A" to check that the first match is the correct one. After reloading the file in Okteta: $ bgrep 23216C75610A0A66756E6374696F6E20 sgd_cdrom_1.30.iso sgd_cdrom_1.30.iso: 0005c800 $ echo 'ibase=16;(0005C800-00042800)/800' | bc -l 52. > > For instance, for > > > > https://sourceforge.net/projects/supergrub2/files/1.30/ > > > > kio_iso seems to deliver data that is 52 sectors ahead on the first try. > > This image is not identified as ISO in my krusader (v2.7). Could this be related to this annoyance: https://bugs.freedesktop.org/show_bug.cgi?id=99421#c20? I get this nonsense: $ kmimetypefinder5 sgd_cdrom_1.30.iso model/x.stl-binary > Dolphin > recognizes it fine and reads from the first try. For example, I can browse to > > iso:/.../sgd_cdrom_1.30.iso/El Torito BootJoliet level 3/boot/grub/ > > without a problem. If the link is directly copied to Krusader, it also opens > the link fine. Doesn't make a difference whether I use Krusader or any other KDE program. It seems to depend only on the iso:/ protocol. Did you also try opening a file on the ISO to check if the data is correct? There might also be a problem with some missing files in the directory listing (comment #0). > > By the way, is it normal that a lot of data is read when I access a small > > file on a big ISO image? > > I'm not sure as I'm not familiar with the format. It's unexpected because one should get the position of the file from the file system on the ISO and then go directly to the file without reading a lot of data from the image. But maybe I have a completely wrong idea about how ISO 9606 works... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394611] Cannot select folders via "select group"
https://bugs.kde.org/show_bug.cgi?id=394611 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #1 from Theo <alpha0...@yahoo.de> --- Can confirm for 2.6.0, official openSUSE Tumbleweed. Also, Alt++ for selecting all doesn't work for me. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394757] Tab bar jumps when tab is selected first time after start
https://bugs.kde.org/show_bug.cgi?id=394757 --- Comment #2 from Theo <alpha0...@yahoo.de> --- Created attachment 112911 --> https://bugs.kde.org/attachment.cgi?id=112911=edit Tabs jump on first selection of a tab (In reply to Toni Asensi Esteve from comment #1) > Can you attach screenshots to this bug report? The first image shows the tab bar of the left panel after Krusader has been startet. There are 13 open tabs and they do not fit all into the horizontal space. The second image shows the situation after selecting tab number 11 with a mouse click: all tabs have made a jump to the right and tab 11 is now as far to right as it can be while still being visible. This annoying behavior happens only when tab 11 has not been selected before in the current Krusader session. Repeating the test with selecting tab 11 a second time in the same session would not change the position of the tabs. Selecting another previously unselected tab causes a jump if the first tab is not fully visible. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394758] New: F7 Mkdir does not create subdirectories
https://bugs.kde.org/show_bug.cgi?id=394758 Bug ID: 394758 Summary: F7 Mkdir does not create subdirectories Product: krusader Version: 2.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: alpha0...@yahoo.de CC: krusader-bugs-n...@kde.org Target Milestone: --- Press F7 and enter "a/b". Expected: the directories ./a and ./a/b are created. Unexpected result: the directories ./a and ./b are created and there is a message "Error: The folder ./b does not exist". -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 394757] New: Tab bar jumps when tab is selected first time after start
https://bugs.kde.org/show_bug.cgi?id=394757 Bug ID: 394757 Summary: Tab bar jumps when tab is selected first time after start Product: krusader Version: 2.6.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: alpha0...@yahoo.de CC: krusader-bugs-n...@kde.org Target Milestone: --- This happens when there is not enough horizontal space for the entire tab bar to fit in. After Krusader has started and reloaded the last session, the tab bar will jump every time a tab far enough to the right is selected with a mouse click for the first time. After the jump, the tab is positioned as far to the right as possible. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023 --- Comment #4 from Theo <alpha0...@yahoo.de> --- (In reply to Nikita Melnichenko from comment #3) > What's the example of such a file? The smaller the better. It happens with every ISO image I try. I did a test with a small sample size of ISO images and the data offset seems to be off by the same sector count on the first try for a given ISO. I got 52, 64, and 80 2K sectors ahead for three different CDs/DVDs. For instance, for https://sourceforge.net/projects/supergrub2/files/1.30/ kio_iso seems to deliver data that is 52 sectors ahead on the first try. By the way, is it normal that a lot of data is read when I access a small file on a big ISO image? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #41 from Theo <alpha0...@yahoo.de> --- (In reply to Martin Flöser from comment #39) > (In reply to Theo from comment #37) > > Is the panel I intact with being unfocused relevant to the problem of the > > app launcher not getting the focus? In other words, if the panel was > > focused, would it be allowed to pass the focus to the app launcher? Does anybody know the answer to this question? > > If so, is the panel never getting the focus the actual bug here? > > No, a panel is not supposed to get focus That looks to me like a "window specific rule" that ships with the panel widget, and which is unexpected by users who direct their "focus" on the panel when they click the app launcher button. I understand that this is not a KWin question, but the curt reply makes me think a simply minded user like me is obviously not supposed to understand the infinitive wisdom behind this behavior of the panel. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 372023] ISO files listing/extracting broken
https://bugs.kde.org/show_bug.cgi?id=372023 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #2 from Theo <alpha0...@yahoo.de> --- Can confirm for kio_iso 2.6.0-2.1 from openSUSE Tumbleweed. I don't know about missing files, but I get binary garbage on the first try opening a file. Reloading the opened file (for instance by pressing F5 in KrViewer, KWrite, or Okteta) gives me the correct data of the file. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 344460] Can't enter into iso images if the path contains symlinked dirs
https://bugs.kde.org/show_bug.cgi?id=344460 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #5 from Theo <alpha0...@yahoo.de> --- Can confirm under Plasma 5 for kio_iso 2.6.0-2.1 from openSUSE Tumbleweed. Absolute symlinks work, relative don't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #37 from Theo <alpha0...@yahoo.de> --- (In reply to Martin Flöser from comment #12) > First of all let's have a look at what the help provides: "New windows get > activated only if no window is currently active or if they belong to the > currently active application. [...]" > [...] > Now let's look at it from a pure window manager perspective: The panel is > not the active application, in fact the panel is marked to never gain focus. > When clicking the app launcher a new window opens. It's a window just like > any other window. The window manager does not know that it is an app > launcher. We currently have a window activated and it's not Plasma, so the > window won't get focus and won't activate. Which in turn results in the app > launcher closing directly as it closes when losing focus. Is the panel I intact with being unfocused relevant to the problem of the app launcher not getting the focus? In other words, if the panel was focused, would it be allowed to pass the focus to the app launcher? If so, is the panel never getting the focus the actual bug here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914
Theo <alpha0...@yahoo.de> changed:
What|Removed |Added
Resolution|WONTFIX |---
CC||alpha0...@yahoo.de
Status|RESOLVED|REOPENED
--- Comment #32 from Theo <alpha0...@yahoo.de> ---
This still isn't fixed in KWin 5.12.5 and it needs to be fixed. Call me an
idiot user, but I had this problem for months before I realized what caused the
problem, had my bug report finally ready to submit when I spotted this bug
under "Possible Duplicates". No amount of mental gymnastics ("technically" this
is not a bug) can justify leaving the user with this broken behavior as it is,
which is not even consistent: the activity management widget is not suppressed
by stealing prevention High, and once it is open, I can also open the
Application Menu and Weather Widget. A simple warning in the setting dialog
would actually be good enough for a fix. I have lost all hope for a well
working focus stealing prevention anyway.
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 394247] New: [Vertical Tabs] Add "Unload Tree" to Tab Tree drop-down menu
https://bugs.kde.org/show_bug.cgi?id=394247 Bug ID: 394247 Summary: [Vertical Tabs] Add "Unload Tree" to Tab Tree drop-down menu Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- It would be useful to have an "Unload Tree" menu item when right-clicking on a tab in the tab tree, which would unload the whole sub-tree starting with the clicked tab. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393925] UpdateSchemaFromV7ToV9 fails due to duplicate key in album_2
https://bugs.kde.org/show_bug.cgi?id=393925 --- Comment #3 from Theo van Rijn <theo.van.r...@gmail.com> --- The migration tool worked like a charm, the new schema does not have any of the superfluous indexes any more. The DB size shrank from almost 2GB to just over 200MB. Thanks Maik! For both solutions. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394066] New: [Vertical Tabs] No tab switching with mouse wheel on full sidebar
https://bugs.kde.org/show_bug.cgi?id=394066 Bug ID: 394066 Summary: [Vertical Tabs] No tab switching with mouse wheel on full sidebar Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- When the tabs don't fit into the vertical space of the sidebar, a scrollbar appears and the mouse wheel can no longer be used to switch tabs. Instead, it causes normal vertical scrolling. Desired behavior is normal scrolling only when the mouse cursor is on the scrollbar, and tab switching when the mouse cursor is located over the tabs. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391438] Zoom preferences not remembered
https://bugs.kde.org/show_bug.cgi?id=391438 --- Comment #7 from Theo <alpha0...@yahoo.de> --- (In reply to Mykola Krachkovsky from comment #6) > IMHO, better to keep Ctrl+± as "per tab" (temporary) Nah, it's better to be consistent with other browsers and the needs of the majority[citation needed]. Of course there is also an obvious solution to this disagreement: make the keyboard shortcuts configurable as it is common in KDE applications. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391438] Zoom preferences not remembered
https://bugs.kde.org/show_bug.cgi?id=391438 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #5 from Theo <alpha0...@yahoo.de> --- (In reply to Mykola Krachkovsky from comment #3) > It's not clear what is exactly annoying. It is annoying to adjust the zoom every time a web page from a certain site is opened in a new tab. Sure, sometimes you want a different zoom only temporarily and in this case it is annoying to revert the remembered zoom level. But there is a reason that Chromium remembers the zoom level: most people are probably more annoyed by the first scenario. As a solution to this dilemma there could be two different sets of keyboard shortcuts, for instance Ctrl+± for remembered zoom levels and Ctrl+Shift+± for temporary zoom levels. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393976] New: [Vertical Tabs] Last closed tab is not reopened in correct position with Ctrl+Shift+T
https://bugs.kde.org/show_bug.cgi?id=393976 Bug ID: 393976 Summary: [Vertical Tabs] Last closed tab is not reopened in correct position with Ctrl+Shift+T Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- When reopening the last closed tab with Ctrl+Shift+T, the tab appears at the end of the tab tree, not at the position in the tree where it was closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393925] UpdateSchemaFromV7ToV9 fails due to duplicate key in album_2
https://bugs.kde.org/show_bug.cgi?id=393925 Theo van Rijn <theo.van.r...@gmail.com> changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393925] New: UpdateSchemaFromV7ToV9 fails due to duplicate key in album_2
https://bugs.kde.org/show_bug.cgi?id=393925
Bug ID: 393925
Summary: UpdateSchemaFromV7ToV9 fails due to duplicate key in
album_2
Product: digikam
Version: 5.9.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Database-Migration
Assignee: digikam-bugs-n...@kde.org
Reporter: theo.van.r...@gmail.com
Target Milestone: ---
After upgrading to Digikam 5.9.0, the database upgrade failed with this error:
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 8
digikam.coredb: Core database: makeUpdates 8 to 9
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Duplicate entry
'111-dsc00025.jpg' for key 'album_2'" 1062 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV9" ]
Statement [ "ALTER TABLE Images MODIFY COLUMN name LONGTEXT CHARACTER SET utf8
COLLATE utf8_general_ci NOT NULL;" ]
digikam.coredb: Core database: schema update to V 9 failed!
digikam.coredb: Core database: cannot process schema initialization
A query on the Images table showed there was one row with album = '111' and
name = 'dsc00025.jpg'. I found 2 indexes on the table Images ('album_2' and
'album_3') that are not defined in dbconfig.xml. After dropping both indexes
the migration was smooth & Digikam started normal.
My Digikam database is ancient and must have been updated numerous times. I
expect these superfluous indexes were created by earlier updates. I found more
duplicate indexes on tables like AlbumRoots, Album & Tags. A function to drop
such superfluous indexes on migration might help to prevent data migration
issues.
I raised this bug to make you aware. For me the issue is solved already.
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 393746] New: [Vertical tabs] Unloaded tabs look the same as loaded tabs
https://bugs.kde.org/show_bug.cgi?id=393746 Bug ID: 393746 Summary: [Vertical tabs] Unloaded tabs look the same as loaded tabs Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- It would be nice to have a clear visual difference between loaded and unloaded tabs, for instance another background color for unloaded tab as opposed to the light default background for loaded tabs in the case of the default theme. I would like to spot loaded tabs easily when I want to free memory by unloading tabs that I don't need at the moment. This means that graying out text for unloaded tabs wouldn't work well for me, since the difference to normal text isn't very eye-catching. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393656] New: [Vertical Tabs] Open empty tab next to current in tree or as a child
https://bugs.kde.org/show_bug.cgi?id=393656 Bug ID: 393656 Summary: [Vertical Tabs] Open empty tab next to current in tree or as a child Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- A new empty tab always appears at the end of the tab tree. There should be the option to automatically open it next to the active tab. It is also desirable to have the possibility of opening a new empty tab as a child of the active tab, for instant by middle-click on the "New Tab" button at the bottom of the side bar. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393567] New: [Vertical Tabs] Collapse status of child nodes of a collapsed node is not preserved after restart
https://bugs.kde.org/show_bug.cgi?id=393567 Bug ID: 393567 Summary: [Vertical Tabs] Collapse status of child nodes of a collapsed node is not preserved after restart Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- Normally, collapsing and expanding a node doesn't change the collapse status of the child nodes in the tab tree. This doesn't work when a node is collapsed before Falkon is shut down and then expanded after Falkon has been started again: in the restored session, the child nodes are all expanded now. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393495] New: [Vertical Tabs] Branches of the tab tree cannot be drag-and-dropped between windows
https://bugs.kde.org/show_bug.cgi?id=393495 Bug ID: 393495 Summary: [Vertical Tabs] Branches of the tab tree cannot be drag-and-dropped between windows Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- Tabs that are childless nodes of the tab tree can be drag-and-dropped between different windows. This is not possible for branches with child tabs. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393483] No spellcheck
https://bugs.kde.org/show_bug.cgi?id=393483 --- Comment #2 from Theo <alpha0...@yahoo.de> --- (In reply to private2.6.3 from comment #1) > You must select language you want to use (just click on it)! Thank you, it works. Maybe the preference dialog should have a hint that I have to select from the listed languages. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393483] New: No spellcheck
https://bugs.kde.org/show_bug.cgi?id=393483 Bug ID: 393483 Summary: No spellcheck Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- Spell check is not working for me (openSUSE Tumbleweed official repository). The dictionaries /usr/share/qt5/qtwebengine_dictionaries/*.bdic are found by Falkon and listed in preferences. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393480] New: SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 Bug ID: 393480 Summary: SSL Error: Server's certificate does not match the URL Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: alpha0...@yahoo.de Target Milestone: --- On some sites (for instance https://socialblade.com/) I get the following error message: SSL Certificate Error! The page you are trying to access has the following errors in the SSL certificate: Server's certificate does not match the URL. Would you like to make an exception for this certificate? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #21 from Theo <alpha0...@yahoo.de> --- (In reply to Silver Salonen from comment #20) > keyboard input does not work until I haven't inserted password for > Keyring. Same for me when I start Skype any time during a KDE session. The Gnome Keyring prompt seem to block all keyboard input for anything but itself. If I remember correctly, this also happened with the graphical password prompt for the SSH agent (x11-ssh-askpass by Jim Knoble) that used to ask for my passphrase at the start of the session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #18 from Theo <alpha0...@yahoo.de> --- (In reply to Nate Graham from comment #16) > Anything left to investigate here? Can we close the bug? IBus is no longer killed by switching to TTY after I updated to Plasma 5.11.0 on my openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 --- Comment #12 from Theo <alpha0...@yahoo.de> --- (In reply to Theo from comment #6) > This happens often > after my system has been stalled when running out of memory. Once my system > is responding again, the IBus daemon for the desktop user is gone. For the record, apparently IBus is indeed killed when switching to TTY. I wasn't aware of this when I wrote that comment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376966] Keyboard input does not work for some applications
https://bugs.kde.org/show_bug.cgi?id=376966 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #6 from Theo <alpha0...@yahoo.de> --- I have this problem on openSUSE Tumbleweed, KDE Plasma 5.10.5. Keystrokes are registered only sporadically in all KDE applications as described in https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721 (that bug seems to be about input fields only, though). This happens often after my system has been stalled when running out of memory. Once my system is responding again, the IBus daemon for the desktop user is gone. Running 'ibus-daemon --xim -d' as user fixes the keyboard input problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379112] New: App "Discover" crashes regularly
https://bugs.kde.org/show_bug.cgi?id=379112 Bug ID: 379112 Summary: App "Discover" crashes regularly Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: themoole...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-19-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: This app crashed when installing an application from the store. This is a common occurence. It also often crashes when uninstalling applications. Another issue I have is that the cursor will freeze such that it is in text-selection mode and I am unable to click on anything within the discover application. I experience crashes with the discover app very regularly. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9afcb328c0 (LWP 3197))] Thread 13 (Thread 0x7f9ac0a3d700 (LWP 4954)): #0 0x7f9af8cfc3a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9af2d81a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9af2d8249b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9af8ca688a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9af8ad3fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9af4eb36da in start_thread (arg=0x7f9ac0a3d700) at pthread_create.c:456 #9 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 12 (Thread 0x7f9a857fa700 (LWP 4951)): #0 0x7f9af4eb98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9af8ad9a86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8ad52b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9af4eb36da in start_thread (arg=0x7f9a857fa700) at pthread_create.c:456 #5 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 11 (Thread 0x7f9ac1e9a700 (LWP 4950)): #0 0x7f9af4eb98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9af8ad9a86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8ad52b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9af4eb36da in start_thread (arg=0x7f9ac1e9a700) at pthread_create.c:456 #5 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 10 (Thread 0x7f9a66ffd700 (LWP 4949)): #0 0x7f9af8cfb0ee in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9af8cfb163 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8cfc4fe in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af2d81a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9af2d8249b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9af8ca688a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9af8ad3fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9af4eb36da in start_thread (arg=0x7f9a66ffd700) at pthread_create.c:456 #11 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7f9aa7fff700 (LWP 3212)): #0 0x7f9af80d018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9af2d82576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4
[okular] [Bug 374539] Crash when viewing a rotated PDF
https://bugs.kde.org/show_bug.cgi?id=374539 Theo <alpha0...@yahoo.de> changed: What|Removed |Added CC||alpha0...@yahoo.de --- Comment #3 from Theo <alpha0...@yahoo.de> --- > Specfically it happened with this PDF file: > https://web.archive.org/web/20050521074830/http://informatik.unibas.ch:80/ > lehre/ss03/algorechnen/online/folien/lekt5.pdf Same for me with openSUSE Tumbleweed. Hardware (AMD/ATI RS780, Radeon HD 3200) is run by radeon driver. Software versions: Okular 1.0.3 (KDE Applications 16.12.3) KDE Frameworks 5.31.0 Qt 5.7.1 Poppler 0.52.0 Linux kernel 4.10.3 -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 361832] System settings; account details; user manager: doesn't display the other users. I'm administrator. Using Kubuntu 15.10.
https://bugs.kde.org/show_bug.cgi?id=361832 Theo Sutton-Marceau <theosuttonmarc...@gmail.com> changed: What|Removed |Added Summary|System settings doesn't |System settings; account |show the other users. |details; user manager: ||doesn't display the other ||users. I'm administrator. ||Using Kubuntu 15.10. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361832] New: System settings doesn't show the other users.
https://bugs.kde.org/show_bug.cgi?id=361832 Bug ID: 361832 Summary: System settings doesn't show the other users. Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: theosuttonmarc...@gmail.com Doesn't show the other users in account details in system settings. I'm using Kubuntu 15.10 . Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
