[kio] [Bug 374907] No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 Saurav Sengupta changed: What|Removed |Added Platform|unspecified |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] New: Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 Bug ID: 375386 Summary: Hotplugged HDMI audio not available Product: Phonon Version: 4.8.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: sit...@kde.org Reporter: saurav1@gmail.com CC: myr...@kde.org, romain.per...@gmail.com Target Milestone: 4.8 KDE SC 5.8.5 On a Lenovo Ideapad 110-15ISK (80UD) the Intel HDMI port operates by hotplugging. However, connecting a TV does not make the HDMI audio output available, although the video works. The laptop's own speaker output continues to function. Manually selecting any HDMI configuration/profile creates a dummy output with no sound. In other desktop environments, such as GNOME, the HDMI audio output becomes available automatically on connecting the TV. Output of aplay -l is:- List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Version|4.8.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 --- Comment #1 from Saurav Sengupta --- I found the correct HDMI device (HDMI 2) by installing GNOME and checking through that. On selecting the correct device/port the audio works. However, obviously this is a very tortuous and unintuitive way of determining which device/port number will work. The GUI should at least provide an indication of which one is plugged in. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] HDMI device number for hotplugged audio cannot be determined easily
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Summary|Hotplugged HDMI audio not |HDMI device number for |available |hotplugged audio cannot be ||determined easily -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] HDMI device number for hotplugged audio cannot be determined easily
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349744] [RFE] Provide keyboard shortcut for toggling airplane mode
https://bugs.kde.org/show_bug.cgi?id=349744 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com --- Comment #2 from Saurav Sengupta --- Yes, this functionality is missing. Airplane mode can be toggled through the GUI widget, but making this programmatically accessible and setting the XF86WLAN key to toggle it by default would be very nice. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375502] New: Kate (part) does not use default indentation mode for new files
https://bugs.kde.org/show_bug.cgi?id=375502 Bug ID: 375502 Summary: Kate (part) does not use default indentation mode for new files Product: kate Version: 16.04.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: saurav1@gmail.com Target Milestone: --- The default indentation mode (at least for the Normal mode) is not applied to new files, i.e., to files which are not (yet) saved and thus do not have an associated indentation mode. The status for bug #142087 shows "resolved fixed" but that was for old versions of Kate and the same problem now occurs with Kate 16.04 on KDE SC 5.8.5. To reproduce: 1. Set the default indentation mode in Kate to Normal. 2. Open a new document but do not save it. 3. Type a line with leading indentation. 4. Press Enter. Result: The new line does not inherit the indentation of the preceding one, although the default indentation mode of Normal should make it do so. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375502] Kate (part) does not use default indentation mode for new files
https://bugs.kde.org/show_bug.cgi?id=375502 Saurav Sengupta changed: What|Removed |Added Platform|unspecified |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349744] [RFE] Provide keyboard shortcut for toggling airplane mode
https://bugs.kde.org/show_bug.cgi?id=349744 --- Comment #3 from Saurav Sengupta --- The XF86WLAN key toggles Wi-Fi, which is fine, but this does not toggle the "airplane" mode in the plasmoid/widget. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 374907] New: No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 Bug ID: 374907 Summary: No warning for insufficient space on target when copying Product: kio Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: fa...@kde.org Reporter: saurav1@gmail.com Target Milestone: --- While copying files to a device which has insufficient space for the whole set of files being copied, only as many files are copied as will fit, and then the process ends without informing the user that all the files could not be copied due to insufficient space. This behaviour is wrong. The user may not be aware at all that all files were not copied. The system should inform the user of this condition. This may be related to the old bug #243160, but that bug is for a much older version of KIO, and the actual results in this case are different - the notification of copying finished that is shown is exactly the same as the one for a complete, successful copy operation, whereas the actual results for the old bug are that the user is notified of the failure. I have experienced this with KIO version 5.28.0 using Dolphin 16.04.3 on Plasma 5.8.5, but I could not find the KIO version on the list of versions available for this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381780] New: Copy completion notifications sometimes incorrectly appear in top-left
https://bugs.kde.org/show_bug.cgi?id=381780 Bug ID: 381780 Summary: Copy completion notifications sometimes incorrectly appear in top-left Product: plasmashell Version: 5.10.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: saurav1@gmail.com CC: mklape...@kde.org Target Milestone: 1.0 Sometimes, the notification for completion of copying files, etc., appears in the top-left corner of the desktop instead of in the bottom-right corner with the default horizontal bottom layout of the main panel. This appears to be a regression since either Plasma 5.10, or Frameworks 5.35, I'm not sure which. I never experienced it with 5.9.x/5.34. The problem does not occur every time, which makes it difficult to reproduce. Also, turning the notifications applet off and on, or moving it out of the system tray does not help. There was a similar case with Plasma 4: see bug #314831, but it seems that it was never fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #13 from Saurav Sengupta --- Tested with what is probably a pre-release of Frameworks 5.36 on Kubuntu 17.10, along with Plasma 5.10.3 and Applications 17.04.2. The notifications appear in the bottom-right as expected, and as yet have not appeared on the top-left. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #28 from Saurav Sengupta --- I should mention that I tested with 5.36 on Kubuntu 17.10 as a sort of "fresh install" by upgrading from 5.35 to 5.36 BEFORE logging in to KDE for the first time. I don't get many notifications, but the ones I got were all in the bottom-right, including those that would always appear in the top-left with 5.35. Are people testing this with 5.36 upgraded from 5.35 which was already being used for KDE sessions, or 5.36 being used the first time onwards on a fresh installation? Perhaps someone could test with a new user account in the former case? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #30 from Saurav Sengupta --- Perhaps 5.36 works correctly with new user accounts, especially if you can replicate the exact circumstance(s) in which you get misplaced notifications in old accounts. In that case, it would be a matter of figuring out what old configuration is causing the problem to remain. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 Saurav Sengupta changed: What|Removed |Added CC|saurav1@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382450] New: Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 Bug ID: 382450 Summary: Dolphin shows "Delete File" for folders Product: dolphin Version: 17.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: saurav1@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 106695 --> https://bugs.kde.org/attachment.cgi?id=106695&action=edit Dolphin shows "Delete File" for folders 1. Enable the 'Delete' service for Dolphin (17.04.x). 2. Right-click a folder (or a selection of folders). 3. The context menu shows "Delete File" (see attached screenshot). Folders are usually not called files, so this could show just "Delete" as it did previously, which would cover all cases. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382450] Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 --- Comment #3 from Saurav Sengupta --- I've also linked this downstream to Ubuntu - https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1703151, though I'm not sure if Dolphin bugs are looked into on Launchpad. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] New: Lock screen does not correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 Bug ID: 382925 Summary: Lock screen does not correct foreground colours for dark background colour Product: kscreenlocker Version: 5.10.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: saurav1@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 106969 --> https://bugs.kde.org/attachment.cgi?id=106969&action=edit Lock screen with a dark background When using a dark colour for the lock screen background (Plain Colour mode), the foreground colours appear dark and are not easily visible. This is not the case with the Breeze SDDM theme, which shows light (white) foreground colours against a dark background colour (although I have a feeling that it will use light colours against a light background as well!). See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 --- Comment #1 from Saurav Sengupta --- I've just noticed that this happens with the Fedora Twenty Six desktop theme, not with Breeze. Perhaps this should be reported to Red Hat; I'm sorry for creating the confusion. I don't know where the system's desktop themes are stored, or I could attach a copy of the Fedora Twenty Six theme, if these needs any further investigation. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not use correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 Saurav Sengupta changed: What|Removed |Added Summary|Lock screen does not|Lock screen does not use |correct foreground colours |correct foreground colours |for dark background colour |for dark background colour -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not use correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 --- Comment #3 from Saurav Sengupta --- (In reply to Martin Flöser from comment #2) > Please report to Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=1476602 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 382450] Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 --- Comment #5 from Saurav Sengupta --- Thanks for the fix. I'll wait for it downstream on Fedora or Kubuntu or something. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 374907] No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 --- Comment #2 from Saurav Sengupta --- This report is more than a year old and the problem seems to be gone; perhaps this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386237] New: Date is clipped with several fonts
https://bugs.kde.org/show_bug.cgi?id=386237 Bug ID: 386237 Summary: Date is clipped with several fonts Product: plasmashell Version: 5.11.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: saurav1@gmail.com Target Milestone: 1.0 Created attachment 108584 --> https://bugs.kde.org/attachment.cgi?id=108584&action=edit Screenshot showing clipped date in Plasma Calendar plasmoid The large date text (day of the month) which appears in the Calendar plasmoid when the PIM events plugin is active, is clipped short at the right edge for some dates. This happens with several fonts, including the default Noto Sans, but on the other hand, does not happen with some fonts, such as DejaVu Sans and Droid Sans. Changing the font size changes which dates get clipped. For example, on the system I face this issue on, the date '26' is clipped with Noto Sans 10pt, whereas '25' is clipped with Noto Sans 9pt. A screenshot is attached, showing the bottom-right edge of '25' clipped short when using the Noto Sans font in Plasma 5.11.2. This occurs in Plasma 5.10.5 and later; I have not tested with earlier versions. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407065] Debugging silently does not work without CMAKE_BUILD_TYPE=DEBUG
https://bugs.kde.org/show_bug.cgi?id=407065 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413707] Option to expand tab widths in Dolphin
https://bugs.kde.org/show_bug.cgi?id=413707 --- Comment #4 from Saurav Sengupta --- (In reply to Nate Graham from comment #3) > Would you be interested in submitting > a patch to to this for Dolphin? I've never worked on KDE, but I'm willing to give it a try, though I think that someone more experienced will most probably precede me. Anyway, I'll report here if I'm able to do something. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413707] Option to expand tab widths in Dolphin
https://bugs.kde.org/show_bug.cgi?id=413707 --- Comment #2 from Saurav Sengupta --- Any news on whether/when this is going to be addressed? It's now Plasma 5.18.1, Frameworks 5.67, and Dolphin (Applications) 19.12.2. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413707] New: Option to expand tab widths in Dolphin
https://bugs.kde.org/show_bug.cgi?id=413707 Bug ID: 413707 Summary: Option to expand tab widths in Dolphin Product: dolphin Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: saurav1@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123645 --> https://bugs.kde.org/attachment.cgi?id=123645&action=edit Configuring tab widths to fill the the viewing space SUMMARY An option to increase tab widths in Dolphin so that the tabs occupy the full view, such as that available in Konsole (screenshot attached), would be welcome. This makes it easier to locate and click on the tabs by providing more screen area to them. STEPS TO REPRODUCE 1. Start Dolphin 2. Open more than one tab OBSERVED RESULT The tabs are small and do not occupy the top of the full viewing area. EXPECTED RESULT Their should be an option to make them do so. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413707] Option to expand tab widths in Dolphin
https://bugs.kde.org/show_bug.cgi?id=413707 --- Comment #1 from Saurav Sengupta --- *There should be option Sorry about the spelling mistake. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 374907] No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 --- Comment #2 from Saurav Sengupta --- This report is more than a year old and the problem seems to be gone; perhaps this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382450] Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 --- Comment #3 from Saurav Sengupta --- I've also linked this downstream to Ubuntu - https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1703151, though I'm not sure if Dolphin bugs are looked into on Launchpad. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] New: Lock screen does not correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 Bug ID: 382925 Summary: Lock screen does not correct foreground colours for dark background colour Product: kscreenlocker Version: 5.10.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: saurav1@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 106969 --> https://bugs.kde.org/attachment.cgi?id=106969&action=edit Lock screen with a dark background When using a dark colour for the lock screen background (Plain Colour mode), the foreground colours appear dark and are not easily visible. This is not the case with the Breeze SDDM theme, which shows light (white) foreground colours against a dark background colour (although I have a feeling that it will use light colours against a light background as well!). See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 --- Comment #1 from Saurav Sengupta --- I've just noticed that this happens with the Fedora Twenty Six desktop theme, not with Breeze. Perhaps this should be reported to Red Hat; I'm sorry for creating the confusion. I don't know where the system's desktop themes are stored, or I could attach a copy of the Fedora Twenty Six theme, if these needs any further investigation. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not use correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 Saurav Sengupta changed: What|Removed |Added Summary|Lock screen does not|Lock screen does not use |correct foreground colours |correct foreground colours |for dark background colour |for dark background colour -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 382925] Lock screen does not use correct foreground colours for dark background colour
https://bugs.kde.org/show_bug.cgi?id=382925 --- Comment #3 from Saurav Sengupta --- (In reply to Martin Flöser from comment #2) > Please report to Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=1476602 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 382450] Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 --- Comment #5 from Saurav Sengupta --- Thanks for the fix. I'll wait for it downstream on Fedora or Kubuntu or something. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386237] New: Date is clipped with several fonts
https://bugs.kde.org/show_bug.cgi?id=386237 Bug ID: 386237 Summary: Date is clipped with several fonts Product: plasmashell Version: 5.11.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: saurav1@gmail.com Target Milestone: 1.0 Created attachment 108584 --> https://bugs.kde.org/attachment.cgi?id=108584&action=edit Screenshot showing clipped date in Plasma Calendar plasmoid The large date text (day of the month) which appears in the Calendar plasmoid when the PIM events plugin is active, is clipped short at the right edge for some dates. This happens with several fonts, including the default Noto Sans, but on the other hand, does not happen with some fonts, such as DejaVu Sans and Droid Sans. Changing the font size changes which dates get clipped. For example, on the system I face this issue on, the date '26' is clipped with Noto Sans 10pt, whereas '25' is clipped with Noto Sans 9pt. A screenshot is attached, showing the bottom-right edge of '25' clipped short when using the Noto Sans font in Plasma 5.11.2. This occurs in Plasma 5.10.5 and later; I have not tested with earlier versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381780] New: Copy completion notifications sometimes incorrectly appear in top-left
https://bugs.kde.org/show_bug.cgi?id=381780 Bug ID: 381780 Summary: Copy completion notifications sometimes incorrectly appear in top-left Product: plasmashell Version: 5.10.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: saurav1@gmail.com CC: mklape...@kde.org Target Milestone: 1.0 Sometimes, the notification for completion of copying files, etc., appears in the top-left corner of the desktop instead of in the bottom-right corner with the default horizontal bottom layout of the main panel. This appears to be a regression since either Plasma 5.10, or Frameworks 5.35, I'm not sure which. I never experienced it with 5.9.x/5.34. The problem does not occur every time, which makes it difficult to reproduce. Also, turning the notifications applet off and on, or moving it out of the system tray does not help. There was a similar case with Plasma 4: see bug #314831, but it seems that it was never fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #13 from Saurav Sengupta --- Tested with what is probably a pre-release of Frameworks 5.36 on Kubuntu 17.10, along with Plasma 5.10.3 and Applications 17.04.2. The notifications appear in the bottom-right as expected, and as yet have not appeared on the top-left. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #28 from Saurav Sengupta --- I should mention that I tested with 5.36 on Kubuntu 17.10 as a sort of "fresh install" by upgrading from 5.35 to 5.36 BEFORE logging in to KDE for the first time. I don't get many notifications, but the ones I got were all in the bottom-right, including those that would always appear in the top-left with 5.35. Are people testing this with 5.36 upgraded from 5.35 which was already being used for KDE sessions, or 5.36 being used the first time onwards on a fresh installation? Perhaps someone could test with a new user account in the former case? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 --- Comment #30 from Saurav Sengupta --- Perhaps 5.36 works correctly with new user accounts, especially if you can replicate the exact circumstance(s) in which you get misplaced notifications in old accounts. In that case, it would be a matter of figuring out what old configuration is causing the problem to remain. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 Saurav Sengupta changed: What|Removed |Added CC|saurav1@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382450] New: Dolphin shows "Delete File" for folders
https://bugs.kde.org/show_bug.cgi?id=382450 Bug ID: 382450 Summary: Dolphin shows "Delete File" for folders Product: dolphin Version: 17.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: saurav1@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 106695 --> https://bugs.kde.org/attachment.cgi?id=106695&action=edit Dolphin shows "Delete File" for folders 1. Enable the 'Delete' service for Dolphin (17.04.x). 2. Right-click a folder (or a selection of folders). 3. The context menu shows "Delete File" (see attached screenshot). Folders are usually not called files, so this could show just "Delete" as it did previously, which would cover all cases. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] New: Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 Bug ID: 375386 Summary: Hotplugged HDMI audio not available Product: Phonon Version: 4.8.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: sit...@kde.org Reporter: saurav1@gmail.com CC: myr...@kde.org, romain.per...@gmail.com Target Milestone: 4.8 KDE SC 5.8.5 On a Lenovo Ideapad 110-15ISK (80UD) the Intel HDMI port operates by hotplugging. However, connecting a TV does not make the HDMI audio output available, although the video works. The laptop's own speaker output continues to function. Manually selecting any HDMI configuration/profile creates a dummy output with no sound. In other desktop environments, such as GNOME, the HDMI audio output becomes available automatically on connecting the TV. Output of aplay -l is:- List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Version|4.8.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] Hotplugged HDMI audio not available
https://bugs.kde.org/show_bug.cgi?id=375386 --- Comment #1 from Saurav Sengupta --- I found the correct HDMI device (HDMI 2) by installing GNOME and checking through that. On selecting the correct device/port the audio works. However, obviously this is a very tortuous and unintuitive way of determining which device/port number will work. The GUI should at least provide an indication of which one is plugged in. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] HDMI device number for hotplugged audio cannot be determined easily
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Summary|Hotplugged HDMI audio not |HDMI device number for |available |hotplugged audio cannot be ||determined easily -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 375386] HDMI device number for hotplugged audio cannot be determined easily
https://bugs.kde.org/show_bug.cgi?id=375386 Saurav Sengupta changed: What|Removed |Added Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349744] [RFE] Provide keyboard shortcut for toggling airplane mode
https://bugs.kde.org/show_bug.cgi?id=349744 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com --- Comment #2 from Saurav Sengupta --- Yes, this functionality is missing. Airplane mode can be toggled through the GUI widget, but making this programmatically accessible and setting the XF86WLAN key to toggle it by default would be very nice. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375502] New: Kate (part) does not use default indentation mode for new files
https://bugs.kde.org/show_bug.cgi?id=375502 Bug ID: 375502 Summary: Kate (part) does not use default indentation mode for new files Product: kate Version: 16.04.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: saurav1@gmail.com Target Milestone: --- The default indentation mode (at least for the Normal mode) is not applied to new files, i.e., to files which are not (yet) saved and thus do not have an associated indentation mode. The status for bug #142087 shows "resolved fixed" but that was for old versions of Kate and the same problem now occurs with Kate 16.04 on KDE SC 5.8.5. To reproduce: 1. Set the default indentation mode in Kate to Normal. 2. Open a new document but do not save it. 3. Type a line with leading indentation. 4. Press Enter. Result: The new line does not inherit the indentation of the preceding one, although the default indentation mode of Normal should make it do so. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375502] Kate (part) does not use default indentation mode for new files
https://bugs.kde.org/show_bug.cgi?id=375502 Saurav Sengupta changed: What|Removed |Added Platform|unspecified |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 349744] [RFE] Provide keyboard shortcut for toggling airplane mode
https://bugs.kde.org/show_bug.cgi?id=349744 --- Comment #3 from Saurav Sengupta --- The XF86WLAN key toggles Wi-Fi, which is fine, but this does not toggle the "airplane" mode in the plasmoid/widget. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 374907] New: No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 Bug ID: 374907 Summary: No warning for insufficient space on target when copying Product: kio Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: fa...@kde.org Reporter: saurav1@gmail.com Target Milestone: --- While copying files to a device which has insufficient space for the whole set of files being copied, only as many files are copied as will fit, and then the process ends without informing the user that all the files could not be copied due to insufficient space. This behaviour is wrong. The user may not be aware at all that all files were not copied. The system should inform the user of this condition. This may be related to the old bug #243160, but that bug is for a much older version of KIO, and the actual results in this case are different - the notification of copying finished that is shown is exactly the same as the one for a complete, successful copy operation, whereas the actual results for the old bug are that the user is notified of the failure. I have experienced this with KIO version 5.28.0 using Dolphin 16.04.3 on Plasma 5.8.5, but I could not find the KIO version on the list of versions available for this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 374907] No warning for insufficient space on target when copying
https://bugs.kde.org/show_bug.cgi?id=374907 Saurav Sengupta changed: What|Removed |Added Platform|unspecified |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
