[dolphin] [Bug 428637] dolphin sort order option doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=428637 Christian Janoff changed: What|Removed |Added CC||kdeb...@janoff.de --- Comment #10 from Christian Janoff --- @Michael: That "__IMAGES" / "fotos" directory ... is this a mounted network drive or a normal $HOME subdirectory? Can you attach one of the photos to this ticket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430977] New: kickoff doesn't select the application if its name is typed in quickly (after login)
https://bugs.kde.org/show_bug.cgi?id=430977
Bug ID: 430977
Summary: kickoff doesn't select the application if its name is
typed in quickly (after login)
Product: plasmashell
Version: 5.19.5
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: k...@davidedmundson.co.uk
Reporter: kdeb...@janoff.de
CC: plasma-b...@kde.org
Target Milestone: 1.0
Created attachment 134404
--> https://bugs.kde.org/attachment.cgi?id=134404=edit
screenshot of the described behaviour after pressing "kaf"
SUMMARY
When application name is typed in quickly the first time after KDE login,
kickoff finds it but doesn't highlight/select it. So simply pressing Enter to
start it immediately is not possible.
STEPS TO REPRODUCE
1. login to a new KDE session (!)
2. open kickoff (I clicked the KDE plasma icon in the lower left corner)
3. quickly (!) type three letters ("kaf" in my case to select the kaffeine
application)
OBSERVED RESULT
a) After typing the three letters "kaf" nothing is highlighted/selected
although "kaffeine" is now the only entry in the list. kickoff already lists
kaffeine after typing the first letter "k" (together with other applications
starting with "k", see below).
I attached a screenshot.
After opening the kickoff menu a second time it is selected:
b) Open menu, press k: kaffeine, konsole and kate are found, nothing selected
(???)
c) Open menu, press ka: kaffeine and kate are found, kaffeine is selected
d) Open menu, press kaf: kaffeine is found and selected
EXPECTED RESULT
If kaffeine is the only entry in the list it should be highlighted/selected
automatically.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Gentoo Linux
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kaffeine] [Bug 429144] New: Stopping recording via button not possible anymore after switching TV channel
https://bugs.kde.org/show_bug.cgi?id=429144 Bug ID: 429144 Summary: Stopping recording via button not possible anymore after switching TV channel Product: kaffeine Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mchehab+sams...@kernel.org Reporter: kdeb...@janoff.de Target Milestone: --- SUMMARY Sometimes I forget to stop recording before switching to another live TV channel which I cannot view/record in parallel. After switching back to the previous TV channel I cannot stop its recording. kaffeine version is 2.0.18. STEPS TO REPRODUCE 1. start recording of channel A by clicking floppy disk icon 2. try to switch to channel B on a different transponder 3. confirm the error popup and switch back to channel A OBSERVED RESULT After starting the floppy disk button icon changes to a red "recording" button icon (which means recording is in progress). After trying to switch to channel B a popup appears that all devices are used for recording which is expected since kaffeine is still recording channel A and channel B is on a different transponder (so they cannot be recorded in parallel). Live TV stopped in this case. After switching back to channel A live TV starts again. But the red button is not visible anymore. Instead it's the floppy disk icon again -> It's not possible to stop recording: When you click on it a second recording of the same channel starts. EXPECTED RESULT It should be possible to stop a recording via the recording icon if we come back to a channel which is being recorded. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429138] New: "Configure Icon Sizes" does not change icon sizes
https://bugs.kde.org/show_bug.cgi?id=429138 Bug ID: 429138 Summary: "Configure Icon Sizes" does not change icon sizes Product: systemsettings Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@janoff.de Target Milestone: --- SUMMARY Trying to change icon sizes in system settings doesn't actually change the icon sizes. Right-clicking on the desktop does. STEPS TO REPRODUCE 1. open "System Settings" 2. go to "Icons" 3. select "Configure Icon Sizes" 4. change the setting for "Desktop" 5. right-click on the desktop 6. select "Icons"->"Icon Size" and choose a different icon size OBSERVED RESULT - after step 4 all desktop icons still have the same size - after step 6 the desktop icons change the size immediately EXPECTED RESULT - setting "Configure Icon Sizes" has immediate effect SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (neon-user-20201105-0946.iso) (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409667] kdenlive crashes on startup with ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread"
https://bugs.kde.org/show_bug.cgi?id=409667 Christian Janoff changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||kdeb...@janoff.de --- Comment #3 from Christian Janoff --- Confirming this with Linux: Gentoo KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419914] Wish: Select next folder entry after deleting
https://bugs.kde.org/show_bug.cgi?id=419914 Christian Janoff changed: What|Removed |Added Version|unspecified |19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419914] New: Wish: Select next folder entry after deleting
https://bugs.kde.org/show_bug.cgi?id=419914 Bug ID: 419914 Summary: Wish: Select next folder entry after deleting Product: dolphin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kdeb...@janoff.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Wish: a) After deleting a folder entry (file or directory) and releasing the Delete key please select the next entry in the folder so that another entry can simply be deleted by pressing the Delete key again. b) The next entry shall be selected after releasing the Delete key. STEPS TO REPRODUCE 1. delete a file or directory by pressing and releasing the Delete key 2. press Delete again OBSERVED RESULT - nothing happens EXPECTED RESULT - next folder entry is selected SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.67.0 Qt 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411718] Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718 --- Comment #7 from Christian Janoff --- Created attachment 126933 --> https://bugs.kde.org/attachment.cgi?id=126933=edit Simple example Python file used to describe the bug -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411718] Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718 Christian Janoff changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Christian Janoff --- I'm (finally) able to provide the requested info: "xdg-mime query filetype example.py" returns "text/x-modelica" I also managed to analyse this further, down to kmimetypefinder5 which gets called by that xdg tool: "kmimetypefinder5 example.py" returns "text/x-modelica" while (non-KDE:) "mimetype --brief --dereference example.py returns "text/x-python". So it seems to be a kmimetypefinder5 problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411642] Mit der startet Dolphin mit leeren Verzeichnispfad. Start eines zweiten Dolphin-Fenster nicht möglich
https://bugs.kde.org/show_bug.cgi?id=411642 Christian Janoff changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Christian Janoff --- Waiting for info. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391913] Error message when I try to paste contents after rename source folder
https://bugs.kde.org/show_bug.cgi?id=391913 Christian Janoff changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Christian Janoff --- Can confirm this bug. KDE neon 5.16.4 Konsole Version: 19.08.1 KDE Frameworks: 5.62.0 Qt: 5.12.3 I attached a video (see above). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391913] Error message when I try to paste contents after rename source folder
https://bugs.kde.org/show_bug.cgi?id=391913 Christian Janoff changed: What|Removed |Added CC||kdeb...@janoff.de --- Comment #2 from Christian Janoff --- Created attachment 122565 --> https://bugs.kde.org/attachment.cgi?id=122565=edit Video describing behaviour of bug 391913 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411173] Empty "Date Photographed" column in details view mode
https://bugs.kde.org/show_bug.cgi?id=411173 Christian Janoff changed: What|Removed |Added CC||kdeb...@janoff.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Christian Janoff --- I can confirm this bug. KDE neon 5.16.4 Konsole Version: 19.08.1 KDE Frameworks: 5.62.0 Qt: 5.12.3 The following image has valid EXIF data including creation dates (though I'm not sure which would be the right one). https://github.com/ianare/exif-samples/blob/master/jpg/Canon_40D.jpg Verify with the "exiftool" command: $ exiftool Canon_40D.jpg ExifTool Version Number : 10.80 File Name : Canon_40D.jpg Directory : . File Size : 7.8 kB File Modification Date/Time : 2019:09:09 17:52:41+02:00 File Access Date/Time : 2019:09:09 17:52:41+02:00 File Inode Change Date/Time : 2019:09:09 17:52:41+02:00 File Permissions: rw-rw-r-- File Type : JPEG File Type Extension : jpg MIME Type : image/jpeg JFIF Version: 1.01 Exif Byte Order : Little-endian (Intel, II) Make: Canon Camera Model Name : Canon EOS 40D Orientation : Horizontal (normal) X Resolution: 72 Y Resolution: 72 Resolution Unit : inches Software: GIMP 2.4.5 Modify Date : 2008:07:31 10:38:11 Y Cb Cr Positioning : Co-sited Exposure Time : 1/160 F Number: 7.1 Exposure Program: Manual ISO : 100 Exif Version: 0221 Date/Time Original : 2008:05:30 15:56:01 Create Date : 2008:05:30 15:56:01 Components Configuration: Y, Cb, Cr, - Shutter Speed Value : 1/166 Aperture Value : 7.0 Exposure Compensation : 0 Metering Mode : Multi-segment Flash : On, Fired Focal Length: 135.0 mm User Comment: Sub Sec Time: 00 Sub Sec Time Original : 00 Sub Sec Time Digitized : 00 Flashpix Version: 0100 Color Space : sRGB Exif Image Width: 100 Exif Image Height : 68 Interoperability Index : R98 - DCF basic file (sRGB) Interoperability Version: 0100 Focal Plane X Resolution: 4438.356164 Focal Plane Y Resolution: 4445.969125 Focal Plane Resolution Unit : inches Custom Rendered : Normal Exposure Mode : Manual White Balance : Auto Scene Capture Type : Standard GPS Version ID : 2.2.0.0 Compression : JPEG (old-style) Thumbnail Offset: 1120 Thumbnail Length: 1378 Profile CMM Type: Linotronic Profile Version : 2.1.0 Profile Class : Display Device Profile Color Space Data: RGB Profile Connection Space: XYZ Profile Date Time : 1998:02:09 06:49:00 Profile File Signature : acsp Primary Platform: Microsoft Corporation CMM Flags : Not Embedded, Independent Device Manufacturer : Hewlett-Packard Device Model: sRGB Device Attributes : Reflective, Glossy, Positive, Color Rendering Intent: Perceptual Connection Space Illuminant : 0.9642 1 0.82491 Profile Creator : Hewlett-Packard Profile ID : 0 Profile Copyright : Copyright (c) 1998 Hewlett-Packard Company Profile Description : sRGB IEC61966-2.1 Media White Point : 0.95045 1 1.08905 Media Black Point : 0 0 0 Red Matrix Column : 0.43607 0.22249 0.01392 Green Matrix Column : 0.38515 0.71687 0.09708 Blue Matrix Column : 0.14307 0.06061 0.7141 Device Mfg Desc : IEC http://www.iec.ch Device Model Desc : IEC 61966-2.1 Default RGB colour space - sRGB Viewing Cond Desc : Reference Viewing Condition in IEC61966-2.1 Viewing Cond Illuminant : 19.6445 20.3718 16.8089 Viewing Cond Surround : 3.92889 4.07439 3.36179 Viewing Cond Illuminant Type: D50 Luminance : 76.03647 80 87.12462 Measurement Observer: CIE 1931 Measurement Backing : 0 0 0 Measurement Geometry: Unknown Measure
[dolphin] [Bug 411642] Mit der startet Dolphin mit leeren Verzeichnispfad. Start eines zweiten Dolphin-Fenster nicht möglich
https://bugs.kde.org/show_bug.cgi?id=411642 Christian Janoff changed: What|Removed |Added CC||kdeb...@janoff.de --- Comment #1 from Christian Janoff --- Hallo, vielen Dank für Deinen Bug Report! Ich würde Dir gerne dabei helfen, weil mir nicht klar ist, was eigentlich der Fehler war. Du hast leider die Vorlage auch nicht ausgefüllt. Ich habe es jetzt so verstanden, dass Dolphin beim Starten einfach einen weiteren Reiter öffnet statt einem neuen Fenster. Deine Erwartung ist also, dass sich ein Fenster öffnet, aber beobachtet hast Du einen Reiter in einem bereits existierenden Fenster, richtig? Mir ist auch nicht klar, was "Dolphin startet mit leeren Verzeichnispfad" genau bedeutet. Wie wird Dolphin dabei gestartet? Per Startmenü? Es ist sicherlich hilfreich, die Vorlage auszufüllen. Also die Schritte aufzuzählen, wie Du *genau* vorgegangen bist (z.B. "1. Öffne das Startmenü und klicke auf Dolphin"), was Du beobachtet hast und für jeden Schritt, was Deine Erwartung ist. (Ein Video davon wäre natürlich grandios, falls Du die Möglichkeit dazu hast, ist aber natürlich nicht nötig.) Hilfreich ist auch die Information, ob der Fehler immer auftritt oder nur sporadisch und notwendige Dolphin-Einstellungen. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 --- Comment #5 from Christian Janoff --- (In reply to Kurt Hindenburg from comment #1) > It doesn't crash here - just exits Konsole as expected. The only difference > I see is I'm on Qt5.12.x I have another (Gentoo) installation with exactly the same behaviour: Konsole quits after pressing Ctrl+D in Tab 1. Konsole 19.04.3 KDE Frameworks 5.60.0 Qt 5.12.3 But: Is it really expected that Konsole quits after the user pressed Ctrl+D in Tab 1? There's still Tab 2 which is read-only and should ignore the Ctrl+D (even if "Copy input to all tabs in the current window" is selected). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 Christian Janoff changed: What|Removed |Added Ever confirmed|0 |1 CC||kdeb...@janoff.de Status|REPORTED|CONFIRMED --- Comment #4 from Christian Janoff --- I can confirm this bug. It's 100% reproducible for me with KDE neon. KDE neon 5.16.4 Konsole Version: 19.08.1 KDE Frameworks: 5.62.0 Qt: 5.12.3 Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f49696215c0 (LWP 4209))] Thread 7 (Thread 0x7f493e123700 (LWP 4215)): #0 0x7f49604949f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560da5742d48) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560da5742cf8, cond=0x560da5742d20) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560da5742d20, mutex=0x560da5742cf8) at pthread_cond_wait.c:655 #3 0x7f49487112bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f4948710d97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f496048e6db in start_thread (arg=0x7f493e123700) at pthread_create.c:463 #6 0x7f4968f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f493e924700 (LWP 4214)): #0 0x7f49604949f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560da5742be8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560da5742b98, cond=0x560da5742bc0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560da5742bc0, mutex=0x560da5742b98) at pthread_cond_wait.c:655 #3 0x7f49487112bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f4948710d97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f496048e6db in start_thread (arg=0x7f493e924700) at pthread_create.c:463 #6 0x7f4968f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f493f125700 (LWP 4213)): #0 0x7f49604949f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560da5742a88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560da5742a38, cond=0x560da5742a60) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560da5742a60, mutex=0x560da5742a38) at pthread_cond_wait.c:655 #3 0x7f49487112bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f4948710d97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f496048e6db in start_thread (arg=0x7f493f125700) at pthread_create.c:463 #6 0x7f4968f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f493f926700 (LWP 4212)): #0 0x7f49604949f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560da5742928) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560da57428d8, cond=0x560da5742900) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560da5742900, mutex=0x560da57428d8) at pthread_cond_wait.c:655 #3 0x7f49487112bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f4948710d97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f496048e6db in start_thread (arg=0x7f493f926700) at pthread_create.c:463 #6 0x7f4968f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f494bfff700 (LWP 4211)): #0 0x7f4968f13bf9 in __GI___poll (fds=0x7f4944004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f495e7475c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f495e7476dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f49655e1dcb in QEventDispatcherGlib::processEvents (this=0x7f4944000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f496558303a in QEventLoop::exec (this=this@entry=0x7f494bffed70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f49653aa4ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f4962ddf015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f49653abc72 in QThreadPrivate::start (arg=0x7f4963056d80) at thread/qthread_unix.cpp:361 #8 0x7f496048e6db in start_thread (arg=0x7f494bfff700) at pthread_create.c:463 #9 0x7f4968f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f49540b0700 (LWP 4210)): #0 0x7f4968f13bf9 in __GI___poll (fds=0x7f49540afca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4960abd747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f
[konsole] [Bug 411332] Konsole doesn't respect "Start in same directory as current tab" when splitting view
https://bugs.kde.org/show_bug.cgi?id=411332 Christian Janoff changed: What|Removed |Added CC||kdeb...@janoff.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Christian Janoff --- Can confirm for Konsole 19.08.1 / KDE neon 5.16.4 Splitting does not respect the "Start in same directory as current tab" profile setting. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411718] Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718 --- Comment #1 from Christian Janoff --- I forgot: Edit the file with Kate. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411718] New: Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718
Bug ID: 411718
Summary: Dolphin shows the wrong file type for Python
Product: dolphin
Version: 19.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: kdeb...@janoff.de
CC: elvis.angelac...@kde.org
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. activate "Type" column in Dolphin to be able to see the file type text
2. create new text file "example.py"
3. write "class Example:" as line 1, press Ctrl+S to save
OBSERVED RESULT
a) after step 2: Dolphin shows Python file type
b) after step 3: Dolphin shows "Modelica model" file type
c) shell command "file example.py" says "example.py: Python script, ASCII text
executable"
d) even after typing a correct Python class the file type stays "Modelica
model"
(Example:
class Example:
def f(self):
pass
print('Hello')
)
EXPECTED RESULT
- file type is Python
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: KDE Neon 5.16.4
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 361313] Application launcher (kickoff) doesn't get mouse focus depending on window focus policy
https://bugs.kde.org/show_bug.cgi?id=361313 --- Comment #2 from Christian Janoff <kdeb...@janoff.de> --- Thanks for trying to reproduce it Alexander, I also can't reproduce this anymore. KDE 5.34.0 Qt 5.7.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361313] New: Application launcher (kickoff) doesn't get mouse focus depending on window focus policy
https://bugs.kde.org/show_bug.cgi?id=361313
Bug ID: 361313
Summary: Application launcher (kickoff) doesn't get mouse focus
depending on window focus policy
Product: plasmashell
Version: 5.6.1
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: k...@davidedmundson.co.uk
Reporter: kdeb...@janoff.de
CC: plasma-b...@kde.org
Application launcher (kickoff) doesn't get the focus when the window focus
policy is set to "focus under mouse" (and above).
Reproducible: Always
Steps to Reproduce:
1. set "focus under mouse" or "focus strictly under mouse" in system settings
2. click application launcher icon ("K" icon)
3. type something
Actual Results:
Application launcher doesn't get the focus. This happens even when no windows
are open.
Expected Results:
Application launcher should always get the focus, regardless of the window
focus policy.
--
You are receiving this mail because:
You are watching all bug changes.
