[okular] [Bug 458722] New: Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 Bug ID: 458722 Summary: Bad rendering of data matrix code in Okular (blurry in some conditions) Product: okular Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- Created attachment 151820 --> https://bugs.kde.org/attachment.cgi?id=151820&action=edit PDF test file for Data Matrix Code 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. Open with Okular a PDF file which contains small Data Matrix Codes (similar to QR Code) 2. If this Data Matrix Code is small then you will notice a bad rendering (blurry rendering), much more noticeable when printing on black and white laser print. 3. Open the same PDF with another PDF reader (Xpdf, firefox PDF reader) : you will notice better rendering, sharp rendering OBSERVED RESULT Blurry Data Matrix Codes on screen display and on black and white laser print for small Data Matrix Code EXPECTED RESULT The Data Matrix Code should be sharp, like other PDF reader. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Another way to reproduce the problem : buy PDF stamps on french La Poste website : https://www.laposte.fr/mon-timbre-en-ligne These stamps have small Data Matrix code, Okular doesn't manage to display them with accuracy, we can see blurry rendering, both on screen and on laser print. You can also open the attached file "GS1_DataMatrix_Guideline.pdf" with okular, on page 20 you will notice that the data matrix code is bad rendered (blurry areas) if you compare with PDF firefox reader or Xpdf the rendering is much better. Data Matrix code on wikipedia : https://en.wikipedia.org/wiki/Data_Matrix -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458722] Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 --- Comment #2 from Potomac --- (In reply to Albert Astals Cid from comment #1) > Okular doesn't do any PDF rendering. > > Please report the issue at > https://gitlab.freedesktop.org/poppler/poppler/-/issues/new?issue Not sure if poppler is the culprit, as it is used also by Xpdf, and Xpdf doesn't have problem for rendering data matrix code. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458722] Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 --- Comment #3 from Potomac --- I created a bug report for poppler : https://gitlab.freedesktop.org/poppler/poppler/-/issues/1291 But as I said I am not sure if poppler is the root cause, I think Okular may not use correctly poppler (bad parameters when calling poppler API ?) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458722] Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 --- Comment #4 from Potomac --- Created attachment 151859 --> https://bugs.kde.org/attachment.cgi?id=151859&action=edit Comparison between Okular and Xpdf for rendering Data Matrix image. Here is a comparison between Okular and Xpdf for rendering Data Matrix image, we can see that Okular doesn't manage to display correctly the data matrix, it's a little blurry. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426935] New: Print preview displays a blank page
https://bugs.kde.org/show_bug.cgi?id=426935 Bug ID: 426935 Summary: Print preview displays a blank page Product: okular Version: 1.11.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY The print preview feature doesn't work in okular 1.11.1, it displays a blank page instead a preview of the print. I use archlinux. STEPS TO REPRODUCE 1. Install okular 1.11.1 and the last version of Qt5 5.15.1 2. Open a PDF document 3. Then click on the menu "file, print preview" OBSERVED RESULT I see a blank page EXPECTED RESULT I should see the preview of the print SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux, plasma 5.19.5 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION When running from the console I can see the error messages when I click on the menu "file, print preview" : $ okular ATTENTION: default value of option vblank_mode overridden by environment. Settings::instance called after the first use - ignoring Unable to open the initial device, quitting. (libspectre) ghostscript reports: fatal internal error -100org.kde.okular.generators.spectre: Generated image does not match wanted size: [0x0] vs requested [574x812] QImage::scaled: Image is a null image Unable to open the initial device, quitting. (libspectre) ghostscript reports: fatal internal error -100org.kde.okular.generators.spectre: Generated image does not match wanted size: [0x0] vs requested [557x788] QImage::scaled: Image is a null image Unable to open the initial device, quitting. (libspectre) ghostscript reports: fatal internal error -100org.kde.okular.generators.spectre: Generated image does not match wanted size: [0x0] vs requested [80x113] QImage::scaled: Image is a null image Unable to open the initial device, quitting. (libspectre) ghostscript reports: fatal internal error -100org.kde.okular.generators.spectre: Generated image does not match wanted size: [0x0] vs requested [557x788] QImage::scaled: Image is a null image -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 425469] kmix 20.08.0 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=425469 --- Comment #14 from Potomac --- For your information I still have the bug despite kmix 20.08.2-2 version. I use archlinux, I have 2 soundcards installed on my system : - sound card from the motherboard gigabyte GA-P35-DS3L : Realtek ALC888 - Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02) Not sure if it's the same bug, here is my original bug report from august 2020 about kmixctrl component : https://bugs.kde.org/show_bug.cgi?id=425686 at each startup I see this error on dmesg : kmixctrl[766]: segfault at 0 ip sp 7fff8c7d4418 error 14 in kmixctrl[5617ae3ba000+2000] despite the segfault kmix is still running fine on background -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 425469] kmix 20.08.0 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=425469 --- Comment #15 from Potomac --- Hello, with the new version kmix 20.08.2-2 it is ok the bug is gone, thanks -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 425469] kmix 20.08.0 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=425469 --- Comment #17 from Potomac --- I confirm that the bug is back again with kmix 20.08.3-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472303] Glitches on the system tray at boot (random bug) when using old AMD radeon cards (radeon driver)
https://bugs.kde.org/show_bug.cgi?id=472303 Potomac changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Potomac --- Problem solved after the upgrade of linux kernel and mesa packages : - linux (6.4.4.arch1-1 -> 6.4.6.arch1-1) - mesa (23.1.3-2 -> 23.1.4-2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472303] New: Glitches on the system tray at boot (random bug) when using old AMD radeon cards (radeon driver)
https://bugs.kde.org/show_bug.cgi?id=472303 Bug ID: 472303 Summary: Glitches on the system tray at boot (random bug) when using old AMD radeon cards (radeon driver) Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mister.free...@laposte.net CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 160316 --> https://bugs.kde.org/attachment.cgi?id=160316&action=edit glitches on the system tray, at the bottom of the screen SUMMARY Randomly at boot I can see glitches on the system tray (see the attached image file), these glitches disapears if I disconnect/reconnect to plasma. STEPS TO REPRODUCE 1. Use an old amd radeon graphic card (like AMD radeon HD4650) with the radeon driver 2. Use a rolling release linux distribution like arch linux 3. At boot I can see glitches on the system tray 4. If I disconnect/reconnect the plasma session then the glitches disapears OBSERVED RESULT Glitches on the system tray EXPECTED RESULT No glitches on the system tray SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux 64 bits, plasma 5.27.6-1 (available in About System) KDE Plasma Version: 5.27.6-1 KDE Frameworks Version: 5.108.0-1 Qt Version: 5.15.10 ADDITIONAL INFORMATION linux kernel : 6.4.3 -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 425686] New: Segfault for kmixctrl 4.6 at startup
https://bugs.kde.org/show_bug.cgi?id=425686 Bug ID: 425686 Summary: Segfault for kmixctrl 4.6 at startup Product: kmix Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KMix Panel Docking Assignee: es...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY I use archlinux (a rolling release linux distro), since a recent update I notice at startup segmentation fault related to kmixctrl (version 4.6) in dmesg : [ 72.047675] kmixctrl[787]: segfault at 0 ip sp 7ffd2a3ff0e8 error 14 in kmixctrl[5628352c9000+2000] [ 72.047682] Code: Bad RIP value. You can also trigger the bug by opening a console, then type "kmixctrl", you will notice a segmentation fault message, if you use the last release version of KDE plasma, kde frameworks application, and QT5 (5.15 version). the backtrace : (gdb) bt #0 0x in ?? () #1 0x7606b2c1 in ?? () from /usr/lib/pulseaudio/libpulsecommon-13.0.so #2 0x7606d860 in pa_socket_client_unref () from /usr/lib/pulseaudio/libpulsecommon-13.0.so #3 0x772c5c58 in ?? () from /usr/lib/libpulse.so.0 #4 0x772c5d72 in ?? () from /usr/lib/libpulse.so.0 #5 0x77f2b41d in ?? () from /usr/lib/libkmixcore.so.5 #6 0x77f2b439 in ?? () from /usr/lib/libkmixcore.so.5 #7 0x77f07a15 in Mixer::~Mixer() () from /usr/lib/libkmixcore.so.5 #8 0x77f07a2a in Mixer::~Mixer() () from /usr/lib/libkmixcore.so.5 #9 0x77f012e7 in MixerToolBox::deinitMixer() () from /usr/lib/libkmixcore.so.5 #10 0x6796 in ?? () #11 0x774dc152 in __libc_start_main () from /usr/lib/libc.so.6 #12 0x683e in ?? () SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux 64 bits, (available in About System) KDE Plasma Version: 5.19.4-2 KDE Frameworks Version: 5.73 Qt Version: 5.15 ADDITIONAL INFORMATION Despite the segfault kmix seems to work (volume applet is Ok). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 426006] New: Sometimes the contextual menu doesn't display after a right mouse click
https://bugs.kde.org/show_bug.cgi?id=426006 Bug ID: 426006 Summary: Sometimes the contextual menu doesn't display after a right mouse click Product: kate Version: 20.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY I use archlinux, kate 20.08.0, Qt 5.15, plasma 5.19. Randomly the contextual menu doesn't display inside a tab of kate (text zone), when I do a right mouse click. To get a contextual menu I have to open a second tab, and then do a right mouse click, then the contextual menu is then possible on the first tab. I didn't manage to get the exact conditions for triggering the bug, but it can occur when there is a single tab inside kate, and after editing/pasting text, saving a document inside a single tab, randomly the right mouse click doesn't bring the contextual menu. It's not a hardware problem (mouse) because at the same time I can use the right mouse click in other applications (firefox, libreoffice). STEPS TO REPRODUCE - Install kate 20.08.0 - Install Qt 5.15 - Use plasma 5.19 - open kate, edit/past/save text on the single tab - try to do a right mouse click on the single tab --> randomly it will not work OBSERVED RESULT no contextual menu when doing a right mouse click EXPECTED RESULT a contextual menu should occur, a workaround is to open a second tab, and do a right mouse click in the second tab, after this action the contextual menu is possible on the first tab SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux 64 bits, plasma 5.19 (available in About System) KDE Plasma Version: 5.19 KDE Frameworks Version: 5.73 Qt Version: 5.15 Kate version : 20.08 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425471] Context menu stops working after I close a tab
https://bugs.kde.org/show_bug.cgi?id=425471 --- Comment #2 from Potomac --- Sometimes the bug occurs also without opening a new tab, just open kate, type or past some text, save the text, try to select one word with the left click, randomly the right-click doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413163] New: Panel takes long time to display on boot
https://bugs.kde.org/show_bug.cgi?id=413163 Bug ID: 413163 Summary: Panel takes long time to display on boot Product: plasmashell Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mister.free...@laposte.net Target Milestone: 1.0 SUMMARY I use archlinux, since plasma 5.17.0 I notice that after plasma has booted the panel doesn't appear immediately, the wallpaper and icons on desktop appear first, and the panel appears only after a delay of 5 seconds, this weird delay doesn't occur with the previous versions of plasma, I use hard disk (not SSD), STEPS TO REPRODUCE 1. Install plasma 5.17.0 OBSERVED RESULT - At cold boot you will notice that the panel is the last element to appear, after a long delay of 5 seconds - With the previous version this latency doesn't exist for the panel EXPECTED RESULT The panel should appear quickly after the boot, shortly after the display of desktop, SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux 64 bits, plasma 5.17.0 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Potomac changed: What|Removed |Added CC||mister.free...@laposte.net --- Comment #167 from Potomac --- Not sure if it's the same bug but I have also a weird font rendering since a recent plasma update, I use archlinux, all KDE softwares (konsole, kate etc...) has a bad font rendering, the height of the fonts seem a little smaller than usual, and are less sharp than usual. I have a 24 inch monitor 1920x1080 pixels, I don't see manually dpi. As a workaround I set QT_AUTO_SCREEN_SCALE_FACTOR to 0. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #168 from Potomac --- My system uses a DPI value of 96 : $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (508x285 millimeters) resolution:96x96 dots per inch $ xdpyinfo | grep dots resolution:96x96 dots per inch -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #169 from Potomac --- Created attachment 125013 --> https://bugs.kde.org/attachment.cgi?id=125013&action=edit difference with QT_AUTO_SCREEN_SCALE_FACTOR enabled/disabled in konsole Here is a comparison in konsole when QT_AUTO_SCREEN_SCALE_FACTOR is set to 1 (slightly blurry fonts), and when QT_AUTO_SCREEN_SCALE_FACTOR is set to 0 (sharp fonts, better rendering). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #171 from Potomac --- (In reply to Christoph Feck from comment #170) > Potomac, are you sure it was a Plasma update that broke it? The net is full > of font rendering regression reports since Qt was updated to version 5.14.0. Yes, the problem started with the update of plasma (5.17.4 to 5.17.5) and KDE softwares (19.12.0 -> 19.12.1), on these new versions the "high dpi support" has been enabled by kde developers, which triggers problems on my configuration (24 inch monitor 1920x1080, DPI 96, graphic card : amd radeon HD4650 pcie, radeon driver open source) : +// enable high dpi support +QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps, true); +QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true); + https://cgit.kde.org/konsole.git/commit/?id=54820e0ff2745add8b8353f538ad67d66b657d49 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417803] New: Clock needs more margin to the right
https://bugs.kde.org/show_bug.cgi?id=417803 Bug ID: 417803 Summary: Clock needs more margin to the right Product: plasmashell Version: 5.18.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mister.free...@laposte.net Target Milestone: 1.0 Created attachment 126109 --> https://bugs.kde.org/attachment.cgi?id=126109&action=edit lack of right margin for the digital clock SUMMARY Since plasma 5.18 I notice that the clock doesn't have a right margin, it's too close the screen border, and the setup icon (which was present to the right of the clock on the previous versions of plasma) has disapeared. This lack of right margin for the clock gives a weird look on the task bar, when we looking at the clock, (see the attached file). please add a slight right margin to the clock,or give the user the ability of setting a right margin to the clock. STEPS TO REPRODUCE 1. Update to the 5.18 version of plasma 2. After reconnection you will notice that the clock is too close to the screen border (no right margin) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux, plasma 5.18 (available in About System) KDE Plasma Version: 5.18 KDE Frameworks Version: 5.67.0 Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417803] Clock needs more margin to the right when placed on a horizontal panel
https://bugs.kde.org/show_bug.cgi?id=417803 --- Comment #1 from Potomac --- Niccolo Venerandi : can you provide the link to the commit/fix ? Is it this commit ? : https://phabricator.kde.org/D27438 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 --- Comment #5 from Potomac --- (In reply to Mauro Carvalho Chehab from comment #3) > (In reply to Potomac from comment #1) > Kaffeine already suggests a name, with is based on the TV standard. Btw, you > could use the same source name for both DVB-T tuners. It only makes sense to > use different names if you have, for example, two DVB-S devices, each > connected to a different dish. the name must be different if we have 2 TV tuner card pci, the problem is that kaffeine by default uses the same name for both TV tuner pci card ( "terrestrial" ), which brings a bug when we want to select the second TV card for the channel search ( as the name is the same then only one card would appear in the combo-box --> "terrestrial" ), in my case if I set the same name for both cards then I can not chose the second card in the combobox "name" when I want to select the card -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 --- Comment #6 from Potomac --- Created attachment 110947 --> https://bugs.kde.org/attachment.cgi?id=110947&action=edit combobox "name" should have a different name for each device here is a screenshot of the problem : - by default with kaffeine 2.0.14 the combobox "source" is not set - and the combobox "name" is set to the same name for both TV cards, which is not good, because the second card will not be present in the combobox "source" when we want to do a channel search ( menu television --> channel, combobox : source ) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 Potomac changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INVALID |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 --- Comment #7 from Potomac --- Created attachment 110948 --> https://bugs.kde.org/attachment.cgi?id=110948&action=edit missing item in the combobox Here is another screenshot which shows the bug when the same name is set for both TV tuner cards PCI : - the 2 devices has the same name : "terrestrial" - I go to the menu "television -> channels", I notice that there is only one item ( the first TV card ) in the combobox "source" - the solution is to set a different name for each device ( "tuner#1", "tuner#2" ), it's the only way for having 2 items in the combobox "source" -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 --- Comment #10 from Potomac --- (In reply to Mauro Carvalho Chehab from comment #9) > > Why do you need to distinguish between the two, if both are connected to the > same TV source, provided that you can use both at the same time? Because each card is connected to a different antenna : - my fisrt card is connected to an indoor antenna, in order to receive regulars TV channels of my country, 27 TV channels : https://fr.wikipedia.org/wiki/Liste_des_cha%C3%AEnes_de_t%C3%A9l%C3%A9vision_en_France - my second card is connected to a cable antenna ( but it is still a DVB-T signal ), which provides one additional channel ( sport channel : "sfr sport 2" ) and also the 27 TV channels but this 27 TV channels are broadcasted on different channels with this second antenna that's why I need to be able to select the 2 cards in the combobox "source" when I want to do a channel search : - First I need to select the first card in order to have the 27 TV channels in DVB-T - Then I need to select the second card in order to have the additionnal TV channel provided by my cable antenna ( in DVB-T ) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] New: underscore character not visible with Bitstream Vera Sans Mono roman font
https://bugs.kde.org/show_bug.cgi?id=390665 Bug ID: 390665 Summary: underscore character not visible with Bitstream Vera Sans Mono roman font Product: kate Version: 17.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- Hello, I use archlinux 64 bits, with Kate I notice that if I type an underscore character then I can't see it until I insert a line break, this problem occurs when the font "Bitstream Vera Sans Mono Roman" is used, with others fonts I don't have this problem, version of kate : 17.12.2-1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] underscore character not visible with "Bitstream Vera Sans Mono roman" and "dejavu mono" fonts
https://bugs.kde.org/show_bug.cgi?id=390665 Potomac changed: What|Removed |Added Summary|underscore character not|underscore character not |visible with Bitstream Vera |visible with "Bitstream |Sans Mono roman font|Vera Sans Mono roman" and ||"dejavu mono" fonts -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] underscore character not visible with "Bitstream Vera Sans Mono roman" and "dejavu mono" fonts
https://bugs.kde.org/show_bug.cgi?id=390665 --- Comment #1 from Potomac --- the bug occurs also with "deja vu mono" font -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] underscore character not visible with "Bitstream Vera Sans Mono roman" and "dejavu mono" fonts
https://bugs.kde.org/show_bug.cgi?id=390665 --- Comment #2 from Potomac --- Created attachment 110786 --> https://bugs.kde.org/attachment.cgi?id=110786&action=edit bottom of character not visible I made some tests, the first test : - I use the "hack" font and font size lesser than 12, the bottom of the characters are not visible the second test : - I still use the "hack font" and font size "12", but I have inserted a line break : the bottom of the characters are now visible, see the screenshot in attachment -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390665] underscore character not visible with "Bitstream Vera Sans Mono roman" and "dejavu mono" fonts
https://bugs.kde.org/show_bug.cgi?id=390665 --- Comment #3 from Potomac --- (In reply to Potomac from comment #2) > > - I still use the "hack font" and font size "12", but I have inserted a line > break : the bottom of the characters are now visible, > > > see the screenshot in attachment correction : the font size is still lesser than "12", the bug doesn't occur when font size is "12" and greater -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] New: Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 Bug ID: 390934 Summary: Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards Product: kaffeine Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: mister.free...@laposte.net Target Milestone: --- Hello, I use archlinux 64 bits and kaffeine 2.0.14, when I want to use my 2 PCI tuner TV cards ( leadtek winfast DTV1800-H and leadteak winfast DTV1000-T ) then I notice that kaffeine doesn't find these 2 tuners, they are not on the combo-box "sources" in kaffeine options, these 2 TV tuners cards work without problems with others software like vlc and mplayer, so it's a bug related to kaffeine 2.0.14, I tried to delete kaffeine configuration in ~/.local/share/kaffeine but it doesn't solve the problem, with a previous version of kaffeine there is no problem, the console output of kaffeine 2.0.14 : $ kaffeine kaffeine.dvb: Using built-in dvb device manager kaffeine.dev: Found dvb device P14f18802107d665f: Conexant CX22702 DVB-T kaffeine.dev: Found dvb device P14f18802107d6654: Zarlink ZL10353 DVB-T QObject::connect: No such slot DvbTab::hideCursor() in this output kaffeine seems to found 2 TV tuner cards but kaffeine doesn't show these 2 cards in the GUI, so I can not start a channel search -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 --- Comment #1 from Potomac --- I found the explanation, when I go to the menu "television, configure television" I notice than in tab "Device 1" and tab "Device 2" the combobox "source" is set to "no source" instead of "autoscan", and no name are set to these device, I can see the information "terrestrial" greyed in the GUI, I have to select "autoscan" for the source for each tab ( "Device 1" and "Device 2" ) and I have to put a name for each device in the textbox "Name", I think an improvement for Kaffeine would be to automatically select "autoscan" and put a random name ( "tuner#1", "tuner#2" etc... ) when kaffeine autodetect a TV tuner card, it's not normal to force the user to manually select "autoscan" and force him to put a name, these things should be automatically done by kaffeine -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] New: oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 Bug ID: 403978 Summary: oxygen theme incompatible with qt5 5.12.1-1 libs Product: Oxygen Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY I use archlinux, since a recent update of qt5 packages (to the 5.12.1-1 version) I notice that kde-plasma is broken if the oxygen theme is used, the desktop displays but the mouse doesn't move, and the harddisk led blink for a long time, the entire system seems frozen (but I can open a terminal with ctrl-alt-f2), if I downgrade qt5 to the previous version (5.12.0) then the oxygen theme is usable, no bugs, and If I use the default theme (breeze) then no problem with the last version of qt5 libs (5.12.1-1) so there is an incompatibility between oxygen 5.14.5 and qt5 5.12.1-1 STEPS TO REPRODUCE 1. install kde plasma 5.14.5 2. use the oxygen theme 5.14.5 3. update to the last qt5 lib release version (5.12.1-1) 4. reboot your system 5. you will notice that kde-plasma hangs when desktop is displayed (mouse frozen) OBSERVED RESULT the desktop is frozen, we can not move the mouse, harddisk led blinks a long time EXPECTED RESULT kde plasma should not frozen when oxygen theme is used with the last version of qt5 (5.12.1-1) SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: archlinux 64 bits, kde plasma 5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION I use radeon HD4650 pci-e graphic card, with the open source driver (radeon), openGL2.0 acceleration in plasma settings for the compositer -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #1 from Potomac --- list of qt5 packages I use in 5.12.1 version (last release version) : qt5-base qt5-sensors qt5-script qt5-x11extras qt5-multimedia qt5-speech qt5-svg qt5-declarative qt5-graphicaleffects qt5-quickcontrols qt5-quickcontrols2 qt5-location qt5-tools qt5-webchannel qt5-webengine qt5-webkit qt5-xmlpatterns -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #3 from Potomac --- the bug occurs with the very recent qt5 libs archlinux package : 5.12.1-1 version, date release : 2019-02-04, the previous version (5.12.0-1) doesn't have problem with oxygen theme, all versions before 5.12.1 works with oxygen theme, you can see here the files that have changed in qt5 5.12.1 version : https://wiki.qt.io/Qt_5.12.1_Change_Files -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #4 from Potomac --- for the reproducibility of the bug it's important to reboot or disconnet/reconnect to a new kde session after switching the theme to oxygen -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #6 from Potomac --- (In reply to Johan Klokkhammer Helsing from comment #5) > Also, it would probably be useful for whoever is going to debug this if you > could attach a log with WAYLAND_DEBUG=1 set in the environment. Ok I will test with WAYLAND_DEBUG=1 set in the environment, but I don't know if I use currently wayland in plasma, I use the default settings in archlinux, and I think by default it's the x11 session for plasma in archlinux -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #8 from Potomac --- some archlinux users reported an excessive memory consumption with Qt5 5.12.1 when oxygen theme is used, which leds to an extreme slowness (mouse doesn't move, high usage of the swap file) : https://bbs.archlinux.org/viewtopic.php?pid=1830703 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #9 from Potomac --- I did a git bisect and I manage to find the faulty Qt5 commit, it's the commit : [9d90c0edac91b35ec96646fd3e6cdd339639ca79] QImage: merge the size calculations with proper (non-UB) checks https://github.com/qt/qtbase/commit/9d90c0edac91b35ec96646fd3e6cdd339639ca79 If I revert this commit then the bug disapears, all is ok, no memory leak with oxygen theme, I created a patch which reverts the faulty commit : https://bugreports.qt.io/secure/attachment/80855/revert_size_calculations_with_proper_non-UB_checks.patch -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #10 from Potomac --- Created attachment 117975 --> https://bugs.kde.org/attachment.cgi?id=117975&action=edit patch for qt5-base 5.12.1 patch which reverts the faulty qt5 commit 9d90c0edac91b35ec96646fd3e6cdd339639ca79 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] New: Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 Bug ID: 402842 Summary: Can not print with kate and kwrite Product: kate Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY I use archlinux, I can not print with kate (18.12.0-1 version) and kwrite, I get an error from cups : [CAPTFILTER] Input File Error If I use okular then I can print without problem, no problem also with libreoffice, so there is a problem for the print feature in kate and kwrite, my printer is a usb device "Canon LBP 3000" STEPS TO REPRODUCE 1. install kate (18.12.0-1 version) 2. use a usb printer device like canon lpb 3000 3. print a text from kate or kwrite 4. you will notice that the printer will refuse to print 5. if you try another software (okular, libreoffice) then you can print without problems OBSERVED RESULT no print with kate and kwrite EXPECTED RESULT the printer should print SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux 64 bits, plasma-framework 5.53.0-1, plasma-desktop 5.14.4-2, kate 18.12.0-1 Qt Version: 5.12.0-1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #1 from Potomac --- the complete error message from cups when I try to print with kate/kwrite : [CAPTFILTER] Input File Error paused - "ccp send_data error, exit" it seems that kate/kwrite use improper print options compared to my printer driver (paper format, margins for example, something that trigger an error on the printer driver) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #2 from Potomac --- Created attachment 117299 --> https://bugs.kde.org/attachment.cgi?id=117299&action=edit log of cups when a print has failed here is a debug log of cups, we have much more details -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #3 from Potomac --- it is in fact a bug of Qt5 when a component generates PDF, when the locale of the user is not english then numbers inside PDF are displayed with comma separator instead point, which triggers a malformed PDF, and an error in cups, for example for MediaBox objects the comma is used by Qt5 which is bad : /MediaBox [0 0 595,00 842,00] see this archlinux thread forum : https://bbs.archlinux.org/viewtopic.php?pid=1824924#p1824924 and my bugreport : https://bugreports.qt.io/browse/QTBUG-72868 a workaround is to set LC_NUMERIC to "C" before running a Qt5 application : LC_NUMERIC=C kate -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #4 from Potomac --- Qt developpers have released a patch in order to fix this bug : https://codereview.qt-project.org/#/c/249357/ https://codereview.qt-project.org/#/c/249357/2/src/gui/painting/qpdf.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403094] New: Spacing too large between icons in "folder view mode" in the desktop
https://bugs.kde.org/show_bug.cgi?id=403094 Bug ID: 403094 Summary: Spacing too large between icons in "folder view mode" in the desktop Product: plasmashell Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: mister.free...@laposte.net Target Milestone: 1.0 Created attachment 117397 --> https://bugs.kde.org/attachment.cgi?id=117397&action=edit spacing too large between icons SUMMARY I use archlinux, since plasma 5.14.5 I notice that the spacing between icons is too large when the desktop is configured in "folder view mode", with the previous versions of plasma the spacing was smaller, I think it's a bug in 5.14.5, maybe triggered by one of these two commits : https://cgit.kde.org/plasma-desktop.git/commit/containments/desktop/package/contents/ui/FolderItemDelegate.qml?id=5323adb7cfac55b2f702076d4f4ae7939b97c296 https://cgit.kde.org/plasma-desktop.git/commit/containments/desktop/package/contents/ui/FolderView.qml?id=78da28e7ab7d51e46fa26788d4890b692996ad36 STEPS TO REPRODUCE 1. install plasma 5.14.5 2. configure your desktop to "folder view mode" 3. select a directory to display on the desktop 4. you will notice that the spacing between the icons on the desktop is too large (see the screenshot as attached file) OBSERVED RESULT the spacing between the icons on the desktop is too large EXPECTED RESULT the spacing should be more smaller, like the previous version of plasma (5.14.4) SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: archlinux 64 bits, plasma 5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 18.12.1 Qt Version: 5.12.0 ADDITIONAL INFORMATION I use the oxygen theme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403094] Spacing too large between icons in "folder view mode" in the desktop
https://bugs.kde.org/show_bug.cgi?id=403094 --- Comment #1 from Potomac --- (In reply to Potomac from comment #0) > with the previous versions of plasma the spacing was smaller, I think it's a > bug in 5.14.5, maybe triggered by one of these two commits : > > https://cgit.kde.org/plasma-desktop.git/commit/containments/desktop/package/ > contents/ui/FolderItemDelegate. > qml?id=5323adb7cfac55b2f702076d4f4ae7939b97c296 > > https://cgit.kde.org/plasma-desktop.git/commit/containments/desktop/package/ > contents/ui/FolderView.qml?id=78da28e7ab7d51e46fa26788d4890b692996ad36 > If I revert these 2 commits then the bug disapears, the spacing becomes smaller, like the previous version of plasma (5.14.4) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 380943] New: bad rendering logout screen
https://bugs.kde.org/show_bug.cgi?id=380943 Bug ID: 380943 Summary: bad rendering logout screen Product: Oxygen Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: style Assignee: hugo.pereira.da.co...@gmail.com Reporter: mister.free...@laposte.net Target Milestone: --- Created attachment 105966 --> https://bugs.kde.org/attachment.cgi?id=105966&action=edit dark font color and dark background Hello, I use archlinux 64 bits, Plasma 5.10.1, with oxygen theme, since plasma 5.10.0 I notice that the logout screen is badly rendered when the oxygen theme is used, the background color is too dark ( dark blue ), as the font color is also dark ( dark grey ) then the readability of the text ( reboot, shutdown, halt ) is very difficult ( see my screenshot ), it seems that the oxygen package doesn't have a "Logout.qml" file, it uses the breeze version ( usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml ), which can explain the bug, in usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml file this line 120 triggers the bug : //use "black" because this is intended to look like a general darkening of the scene. a dark gray as normal background would just look too "washed out" color: root.rgbToHsv(PlasmaCore.ColorScope.backgroundColor).v > 128 ? PlasmaCore.ColorScope.backgroundColor : "black" if I delete this line and replace it by this then all is ok : color: PlasmaCore.ColorScope.backgroundColor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395011] New: K menu displays sometimes wrong items
https://bugs.kde.org/show_bug.cgi?id=395011
Bug ID: 395011
Summary: K menu displays sometimes wrong items
Product: plasmashell
Version: master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: k...@davidedmundson.co.uk
Reporter: mister.free...@laposte.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
Hello,
I use archlinux, plasma 5.12.5, oxygen theme is installed,
my K menu is configured as "classic style menu" (like windows 9.x),
sometimes when I click on K menu I notice a weird bug :
- randomly when I click on the K menu I notice that the "recent used
applications" menu displays wrong items, instead of application names I see a
list of file names of recent used documents (same items of "recent used
documents" menu)
If I reclick on k menu then the bug disapears, it's a random bug, I have this
bug since a recent archlinux package upgrade ("pacman -Syu")
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 395011] K menu displays sometimes wrong items
https://bugs.kde.org/show_bug.cgi?id=395011 Potomac changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Potomac --- It is a complete different bug (not bug 394013) and it's not resolved, despite I use the last version of plasma, the bug here is not related to a graphic issue, the items of submenu "recent used applications" sometimes displays the contains of submenu "recent used documents" -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen
https://bugs.kde.org/show_bug.cgi?id=373274 Potomac changed: What|Removed |Added CC||mister.free...@laposte.net --- Comment #2 from Potomac --- I can confirm this bug, randomly after several hours ksmserver eats too much ram, for example on systems with 4 Gb ram ksmserver can eat 3 Gb, which can cause swap disk operatin, and slowdown the PC, I use archlinux 64 bits, plasma 5.9.3-1 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 501070] Truncated display of decoration buttons window when exiting fullscreen mode on video application (VLC, youtube)
https://bugs.kde.org/show_bug.cgi?id=501070 Potomac changed: What|Removed |Added CC||mister.free...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 501070] New: Truncated display of decoration buttons window when exiting fullscreen mode on video application (VLC, youtube)
https://bugs.kde.org/show_bug.cgi?id=501070 Bug ID: 501070 Summary: Truncated display of decoration buttons window when exiting fullscreen mode on video application (VLC, youtube) Classification: Plasma Product: Oxygen Version: 6.3.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: win deco Assignee: unassigned-b...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- Created attachment 179122 --> https://bugs.kde.org/attachment.cgi?id=179122&action=edit Buttons truncated after using fullscreen video mode (youtube). SUMMARY When using the oxygen theme with plasma 6.3.2 then decoration buttons (top right of the window) can be truncated when exiting "fullscreen mode" on application that can display video (VLC, internet browser with youtube) : STEPS TO REPRODUCE 1. Use a linux distro (I use Arch Linux) 2. Install plasma 6.3.2 3. Install Oxygen theme 4. Run in fullscreen mode a video (VLC, youtube with your favorite browser) 5. Exit fullscreen mode 6. You will notice that the 3 buttons of the window (top right) are truncated (cut off at half height) OBSERVED RESULT The 3 buttons (minimize window, maximize window, close app) of the window (top right) are truncated (cut off at half height) EXPECTED RESULT The 3 buttons of the window (top right) should not be truncated. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux, Plama 6.3.2 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION - The problem doesn't exist if I use breeze theme. See attachment for illustration of the problem. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 500976] Window size not restored correctly after exiting full screen.
https://bugs.kde.org/show_bug.cgi?id=500976 Potomac changed: What|Removed |Added CC||mister.free...@laposte.net --- Comment #5 from Potomac --- I confirm the bug, it happens always with oxygen theme and Plasma 6.3.2. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv
https://bugs.kde.org/show_bug.cgi?id=351774 --- Comment #20 from Potomac --- @Mauro Carvalho Chehab : do you have an example of command line for libVLC if we want to setup the video output ? I don't find help about libVLC and parameters -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv
https://bugs.kde.org/show_bug.cgi?id=351774 --- Comment #22 from Potomac --- (In reply to Mauro Carvalho Chehab from comment #21) > > --no-video-title-show -V xcb_glx > or: > > --no-video-title-show -V xcb_xv > > and re-start Kaffeine. these settings doesn't solve the problem, I always have this high CPU usage, this bug occurs when I switch the TV channel, with the first channel ( when kaffeine starts ) the CPU usage is Ok ( 15% ), but when I change the channel the CPU usage randomly becomes very high, in console I can read this : [7f5e580c5d58] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding. the switching seems to trigger the bug, maybe kaffeine should reset something in libVLC when the user changes the TV channel, in order to be sure that correct parameters will be used -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 351774] --no-xlib" to libvlc_new() error when watching tv
https://bugs.kde.org/show_bug.cgi?id=351774 --- Comment #17 from Potomac --- I still have the same bug with the 2.0.1 version : too much high CPU usage when I watch TV ( 100% CPU usage ), the main problem is the VLC backend, kaffeine 2.0.1 seems to use it badly, and we don't have a way to configure vlc backend inside kaffeine ( for example VDPAU, xv, x11 for the video output ), that's why there is a high CPU usage if the default settings choosen by kaffeine is not suitable for the graphic driver, and I discover another bug : when I click on "file-> exit" kaffeine 2.0.1 is still running ( the GUI disapears but kaffeine process is still running, I had to kill the process ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] New: left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 Bug ID: 356764 Summary: left mouse click on taskbar is randomly not detected Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: mister.free...@laposte.net CC: plasma-b...@kde.org I use archlinux 64 bits, since plasma 5.5.1-1 packages I notice a bug : - sometimes the left mouse click is not detected when I click on the plasma taskbar ( or K menu ), for example if firefox is minimized on the taskbar then sometimes a mouse click for restoring the firefox window doesn't work, I have to do this mouse click twice in order to restore the window, this bug doesn't occur with plasma 5.5.0, I can reproduce this bug on my PC ( archlinux 64 bits ) and on a qemu virtual machine i686, this bug occurs randomly ( you have to test at least 10 times in order to trigger the bug, for example 3 windows opened or minimized, then try to click on the taskbar in order to minimize/restore one of these 3 windows, you will notice that sometimes the mouse click is not detected by plasma 5.5.1 ) Reproducible: Sometimes Steps to Reproduce: - update to plasma 5.5.1-1 packages - open 3 programs ( for example : firefox, thunderbird, dolphin ) - sometimes when you want to minimize or restore a window ( firefox, thunderbird, dolphin for example ) the plasma taskbar doesn't detect the left mouse click - this bug doesn't occur with the previous versions of plasma ( for example 5.5.0 ) you need to try at least 10 times because it's a random bug, this bug can also occur if you try to click on the K menu Actual Results: the taskbar sometimes doesn't detect the left mouse click Expected Results: the plasma taskbar should have detected the left mouse click and should minimize/restore the window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 Potomac changed: What|Removed |Added Version|master |5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #3 from Potomac --- on archlinux this bug seems solved with plasma-workspace 5.5.1-4 package : https://bugs.archlinux.org/task/47399 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #4 from Potomac --- a patch has been released in order to fix this bug : https://quickgit.kde.org/?p=plasma-workspace.git&a=commitdiff&h=1390b4&o=plain linux distros should apply this patch quickly, for archlinux it's already done with plasma-workspace 5.5.1-4 package version -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356839] plasma 5 doesn't start on very old PCs who have a graphic card who supports only openGL 1.3
https://bugs.kde.org/show_bug.cgi?id=356839 Potomac changed: What|Removed |Added Summary|plasma 5 doesn't start on |plasma 5 doesn't start on |very old PCs who have a |very old PCs who have a |graphic card who support|graphic card who supports |only openGL 1.3 |only openGL 1.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356839] New: plasma 5 doesn't start on very old PCs who have a graphic card who support only openGL 1.3
https://bugs.kde.org/show_bug.cgi?id=356839 Bug ID: 356839 Summary: plasma 5 doesn't start on very old PCs who have a graphic card who support only openGL 1.3 Product: plasmashell Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mister.free...@laposte.net CC: bhus...@gmail.com, plasma-b...@kde.org I tried to install plasma 5.5.1 on a very old PC ( pentium 2.4 Ghz, graphic card radeon 9000 AGP ) with archlinux 32 bits, the driver for the graphic card : radeon open source driver, and I get only a black screen at startup, the PC seems frozen, I tried with startx : black screen and no cursor mouse, the PC is frozen, sddm seems to have the same problem : a black screen, I am unable to see the login/password page, what are the minimal hardware requirements in order to use plasma 5 ? it seems that plasma 5 can not boot if the graphic card supports only openGL 1.3, there is someting in plasma 5 who prevents old graphic cards to work, if I use kdm and kde 4.x there is no problem with this old PC, and there is also no problem with lxqt ( who uses Qt5 libs ) Reproducible: Always Steps to Reproduce: 1. install plasma 5.5.1 on a very old PC ( from 2003 for example, with a graphic card who supports only openGL 1.3 ) 2. try to boot plasma 5.5.1 ( startx or sddm ) 3. you will get a black screen at startup, with keyboard frozen and no mouse cursor Actual Results: black screen, keyboard frozen and no cursor mouse Expected Results: plasma 5.5.1 should start on old PCs, even if the graphic card is very old and supports only openGl 1.3 -- You are receiving this mail because: You are watching all bug changes.
