[kmymoney] [Bug 454399] kmymoney crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=454399 Manfred changed: What|Removed |Added CC||mhai...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475675] New: Budgeting Reports Need current month and year-to-date option.
https://bugs.kde.org/show_bug.cgi?id=475675 Bug ID: 475675 Summary: Budgeting Reports Need current month and year-to-date option. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: sbrog...@gmail.com Target Milestone: --- SUMMARY The Budget report section has Budgeted vs Actual This Year. Users would be greatly served by having this data for Current month and Year-to-date. If the range is changed to current month, the "Actual This Year" is also restricted to current month. Should be actual year-to-date. SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475675] Budgeting Reports Need current month and year-to-date option.
https://bugs.kde.org/show_bug.cgi?id=475675 --- Comment #2 from Manfred --- The report I would to see - my old DOS MoneyCounts had it - would be budget vs actual for the current month and the cumulative year-to-date (end of current month). The Range on the report should only affect the month shown, not the cumulative amounts. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415327] endless loop during file dialodue
https://bugs.kde.org/show_bug.cgi?id=415327 Manfred changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Manfred --- Please close, obsolete. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415327] New: endless loop during file dialodue
https://bugs.kde.org/show_bug.cgi?id=415327 Bug ID: 415327 Summary: endless loop during file dialodue Product: kdenlive Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: manfred.h...@t-online.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create new project with kdenlive 2. try to save the work 3. OBSERVED RESULT File dialogue displays frame only. KDEnlive is running in endless loop. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415327] endless loop during file dialodue
https://bugs.kde.org/show_bug.cgi?id=415327 --- Comment #2 from Manfred --- Am 20.12.19 um 18:17 schrieb emohr: > https://bugs.kde.org/show_bug.cgi?id=415327 > > emohr changed: > > What|Removed |Added > >Flags||timeline_corruption+ > CC||fritzib...@gmx.net > > --- Comment #1 from emohr --- > Thank you for reporting. > Please try with the current Kdenlive AppImage version 19.12.0a to see if there > are any packaging issues https://files.kde.org/kdenlive/release/ > > If the problem/issue doesn't occur when using the AppImage, then it's your > configuration or packaging. > The problem does not occur with the AppImage file. Removing kdenlive and reinstalling it on Lubuntu was no fix. There was an error message of GTK complaining on a missing parent for the dialogue. I will further on use the proposed Kdenlive AppImage version 19.12.0. Thank you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] New: Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 Bug ID: 389273 Summary: Copy/move selected items to anothor Album doesn't work correctly Product: digikam Version: 5.8.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: a...@manfred-doerner.de Target Milestone: --- By copying/moving selected item to another album always ignoring selected once. I it used always the whole amount images from actual album. You cann't copy/move selected items. Also when digikam copying the whole album you cann't cancel it in digikam. It is always a extra thread, that you have kill it by a terminal. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389274] New: Export selected Images to a local folder
https://bugs.kde.org/show_bug.cgi?id=389274 Bug ID: 389274 Summary: Export selected Images to a local folder Product: digikam Version: 5.8.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Export-WishForNewTools Assignee: digikam-bugs-n...@kde.org Reporter: a...@manfred-doerner.de Target Milestone: --- Just simply export selected items to a local folder is missing. Maybe removing private Tags by exporting would be nice. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 --- Comment #1 from Manfred --- Also by copying/moving some images selected by a group, any images will be copied not the selected once. This behavior is unpredictically and very strange. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 --- Comment #3 from Manfred --- I am using sqlite. The total amount of images is approx. 16.000. One album is connected as a network drive, mount via smbfs. The other album is connected to local drive. I didn't use 5.9.0. So I have to check later. Manfred Doerner -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 --- Comment #5 from Manfred --- The problem is also reproducible with version 5.9.0. Debug logs are only "[New Thread...]" and "[Threadexited]", not more. I selected 156 items and this was showed but round about 3000 items where copied. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 --- Comment #6 from Manfred --- How I reproduced: 1. Went in my my Album with 1896 images. 2. Showed all images also which are grouped. I am using grouping. 3. Selected 4+ rating. -> 156 images showed. 3. Selected all 156 images. It signed at status bar that 156 images are selected. 4. Copied to a new album. Digikam noticed that 156 images will be copied. 5. But all 1896 images where copied. That's the problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 --- Comment #7 from Manfred --- One notice more: After copying images by digikam the RAM buff/cache is always using 5.6GB. It is freezed and isn't decreasing. So I had to reboot my computer. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389273] Copy/move selected items to anothor Album doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=389273 Manfred changed: What|Removed |Added Severity|major |task --- Comment #9 from Manfred --- I investigated one more time and I can explain my mistake. I am using grouping of images. When the group is opened, the "master" image, which hold the information, looks very similar to others. It differs only by a "number" which indicates the amount of the group. So when only the "master" image is selected digikam shows that one image is selected, ok. Now when I copy/move only the one selected "master" image digikam will be copying the hole group without any information. This was a little bit confusion for me. But now I know this issue and it's ok for me. In fact the memory overflows isn't a problem of digikam. Now this topic can be closed because it isn't a bug. Many thanks for the support. Finally, digikam is a great software:-) Thanks a lot to the whole digikam team! Manfred -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 185422] Konsole TAB option "copy input": setting not being saved with desktop
https://bugs.kde.org/show_bug.cgi?id=185422 Manfred Knick changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Manfred Knick --- Hi, Kurt! As far as I am concerned, I really would not mind to have this closed - preferably as "OBSOLETE". Thanks! Kind regards Manfred Postscriptum - OT: Nowadays, I enjoy the effectiveness of extreme simplicity: dwl <- wlroots <- wayland; plus bemenu and foot - that's all to support any ( KDE ) application I might need: [ https://codeberg.org/dwl/dwl ] , perfectly providing a 2x2 Monitor workstation (Gentoo) setup as well as a "Road Warrior" Notebook. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 Manfred Musch changed: What|Removed |Added CC||manfred.mu...@gmx.de --- Comment #1 from Manfred Musch --- Created attachment 149954 --> https://bugs.kde.org/attachment.cgi?id=149954&action=edit Window list behind control panel -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #2 from Manfred Musch --- Created attachment 149955 --> https://bugs.kde.org/attachment.cgi?id=149955&action=edit Kickoff behind window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #3 from Manfred Musch --- Created attachment 149956 --> https://bugs.kde.org/attachment.cgi?id=149956&action=edit Window list started by shortcut -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #4 from Manfred Musch --- Same strange behaviour on my system. Only if I change windows two times with cover switch or flip switch then I have the normal behaviour - but not for long. I'm using 5 activities and 4 workspaces for different purposes (however mostly not always all of them at the same time), but that's not the reason for this behaviour because it also occurs with only one activity in use. Perhaps a similar phenomenon: in some cases the window list disappears behind the control panel, and even so kickoff which is theoretically in the foreground but behind an opened window (see screenshots 1 and 2). For window list even stranger: if I use a shortcut to start the list it looks totally different (see screenshot 3). Infos software / hardware: Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: X11 Processors: 4 × AMD A8-6600K APU with Radeon(tm) HD Graphics Memory: 7.0 GiB of RAM Graphics Processor: AMD ARUBA -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #6 from Manfred Musch --- (In reply to Vlad Zahorodnii from comment #5) > It looks like compositing stacking order differs from the real one, although > I can't reproduce this issue. What do you do to reproduce this bug? That's the problem, I can't say: first this step, then the next, and then it goes wrong... It seems that it has to do with changing workspaces and/or activities (say three workspaces with some windows opened, then moving between them, changing windows on one workspace, going back), but I can't describe a precise pattern (how much windows, how much workspaces and/or activities). And it only occurs after a certain time (not too much time however). So my only possibility to reproduce is to wait until it is the case... Not very satisfactory as an answer, I know. I haven't changed any settings between Plasma 5.24.5 and 5.25, it only has occurred (and occurs) in 5.25. Perhaps I should let run after a fresh start a screencast alongside to get a hint? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #7 from Manfred Musch --- (In reply to Vlad Zahorodnii from comment #5) > It looks like compositing stacking order differs from the real one, although > I can't reproduce this issue. What do you do to reproduce this bug? Now I think I have found the "moment"! I started with a new session, first in the standard activity. There I opened on first workspace a program (Kontact - which by the way I like very much), then I switched to workspace 2 and opened two programs (in my case Falkon and Firefox, but it doesn't matter). Then workspace 3 with three programs, moving one of these programs to workspace 2. Then switching to workspace opening two new programs (Konsole and Gwenview). All is working perfect insofar. And now comes the point. I switch to a second activity, start there in one of my four workspaces two programs and in a second workspace another program (the number of programs shouldn't play that role, but I only mention it to reproduce my way - and I think it is a real-case scenario for working). So far so good. But then: I switch back to the first standard activity, workspace 1 (with the three programs) - and I have the problems. It has obviously to do with switching between activities. I have read what other users have written, and I think it was the same with then: the moving between activities if you have opened programs/windows in other activities. I hope that helps. By the way: activities are a great concept. One of the main reasons I'm using KDE Plasma intensively. The best way in my eyes to adapt your pc work to your own needs! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #8 from Manfred Musch --- (In reply to Vlad Zahorodnii from comment #5) > It looks like compositing stacking order differs from the real one, although > I can't reproduce this issue. What do you do to reproduce this bug? Short correction: the two new programs mentioned in my post (Konsole and Gwenview) were started in the first workspace of the standard activity - I had the 1 omitted (but you will have noticed it). And a small addition: as soon as the window management is no longer in order, the program list also slips behind the control panel. Both problems seem connected! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #10 from Manfred Musch --- Created attachment 150060 --> https://bugs.kde.org/attachment.cgi?id=150060&action=edit Broken Activities demonstrated To reproduce how program windows are active behind inactive windows that can't be easily pushed into the background I have made a little screencast. I was able to reproduce this behaviour several times without difficulty. The effect occurred even faster than I remembered. The steps described: (1) open one window in standard activity; (2) switch to a second activity and open two windows in the same workspace there; (3) go back to standard activity and open a second window there in the same workspace as before; (4) the effect occurs. And as you can see: the control panel is also affected. By the way: the new window list is almost unusable because it has no fixed width in the panel - sometimes it's narrow and sometimes it's wide. In KDE 3.5 it was a simple button in the panel (so in Plasma 5.24 too), and the entries could be seen when you clicked on the button... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order
https://bugs.kde.org/show_bug.cgi?id=455429 --- Comment #12 from Manfred Musch --- (In reply to Vlad Zahorodnii from comment #11) > (In reply to Manfred Musch from comment #10) > > Created attachment 150060 [details] > > Broken Activities demonstrated > > > > To reproduce how program windows are active behind inactive windows that > > can't be easily pushed into the background I have made a little screencast. > > I was able to reproduce this behaviour several times without difficulty. The > > effect occurred even faster than I remembered. The steps described: (1) open > > one window in standard activity; (2) switch to a second activity and open > > two windows in the same workspace there; (3) go back to standard activity > > and open a second window there in the same workspace as before; (4) the > > effect occurs. And as you can see: the control panel is also affected. By > > the way: the new window list is almost unusable because it has no fixed > > width in the panel - sometimes it's narrow and sometimes it's wide. In KDE > > 3.5 it was a simple button in the panel (so in Plasma 5.24 too), and the > > entries could be seen when you clicked on the button... > > It looks like you have slide back effect enabled. What if you disable it? > Can you still reproduce the issue? Now I disabled the slide back effect - and the issue disappeared! Thanks for the very helpful tip! Much better the activities work normally again than to insist on the slide back effect... Of course there must be a reason that this confusing behaviour occurred with the change from 5.24 to 5.25, and the slide back effect had the advantage that it could be used as an additional clearly visible sign for changing overlapping windows - but I'm already satisfied that my activities workflow is restored! Your assumption was completely right! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 415694] Gwenview crashed after watching a video
https://bugs.kde.org/show_bug.cgi?id=415694 --- Comment #4 from Manfred Kitzbichler --- I cannot reproduce the crash anymore. That said, I am having a range of other issues that persist, such as choppy playback, frozen videos and also an unresponsive application. My prefered video player these days is mpv which doesn't seem to have any of these issues. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447253] New: Gwenview shows PEF raw images only black
https://bugs.kde.org/show_bug.cgi?id=447253 Bug ID: 447253 Summary: Gwenview shows PEF raw images only black Product: gwenview Version: 21.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: tul...@gmx.de Target Milestone: --- SUMMARY I am using Gwenview under Gentoo Linux. After the last update from version 21.04.03 to 21.08.3 (and also with 21.12.0) Gwenview is not able to display PEF (Pentax raw) images anymore. These images are shown completely black. The error message is: gwenview.libtiff: Error foo "Sorry, can not handle images with 14-bit samples" This error message comes from the Tiff library, but I it is still version 4.3.0 which worked with the older Gwenview version. I don't know if this error is directly caused by Gwenview or by another library between Gwenview and the Tiff library. So please tell me what additional information you need. ORF raw images are still shown correctly. STEPS TO REPRODUCE 1. Download a PEF file, for example from https://s3.amazonaws.com/files.dpreview.com/sample_galleries/8034986469/4876920099.pef?X-Amz-Expires=3600&response-content-disposition=attachment%3B%20filename%3D%22IMGP0593.pef%22&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA4NPXSRZN2I2XWOXX/20211220/us-east-1/s3/aws4_request&X-Amz-Date=20211220T063958Z&X-Amz-SignedHeaders=host&X-Amz-Signature=e72bdba9f09ffc7fecf5d09f3f7547252116ebd87fa7d1f0be2f2ec926714416 2. Open file in Gwenview OBSERVED RESULT The image is shown completely black with the following error message: gwenview.libtiff: Error foo "Sorry, can not handle images with 14-bit samples" EXPECTED RESULT Image is shown normally as with version 21.04 and older. SOFTWARE/OS VERSIONS Linux: Gentoo Linux with Kernel 5.10.61-gentoo-x86_64 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423889] Kwin hangs in KWin::WindowPixmap::create() / xcb_request_check
https://bugs.kde.org/show_bug.cgi?id=423889 Manfred Kitzbichler changed: What|Removed |Added CC||manfred.kitzbichler@gmail.c ||om --- Comment #7 from Manfred Kitzbichler --- Same here, OpenSUSE Tumbleweed, all latest packages. The problem appeared about 2 weeks ago on my system and it is worse when I enable Compositing. At the moment it is switched off and even though this gives me a very laggy experience with screen updates and input hanging for seconds at times, at least I don't get a complete freeze (except for the mouse pointer) as described above. Here is the output from the support info request via DBUS: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.19.2 Qt Version: 5.15.0 Qt compile version: 5.15.0 XCB compile version: 1.14 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_EGL_STREAMS: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12008000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.oxygen Theme: Plugin recommends border size: No Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: false closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 6 decorationButtonsRight: 2, 9, 3, 4, 5 borderSize: 2 gridUnit: 10 font: Noto Sans,10,-1,0,75,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: false electricBorderTiling: false electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: false hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 97 glPlatformInterface: 1 windowsBlockCompositing: false Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: eDP1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60.049 Compositing === Compositing is not active -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421922] kde-apps/akonadi-{19.08.3,19.12.2} with dev-db/mysql-8.0.19{-r1} - error: 'Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2)'
https://bugs.kde.org/show_bug.cgi?id=421922
Manfred Knick changed:
What|Removed |Added
CC||manfred.kn...@t-online.de
--- Comment #9 from Manfred Knick ---
After recent *stable* updates, problem still persists:
kde-apps/akonadi-{19.08.3,19.12.2,20.08.3}
with
dev-db/mysql-{8.0.19{-r1},8.0.21-r1}
[ https://bugs.gentoo.org/709812#c30 ]
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 429853] New: Aspect Ratio One Pixel Error
https://bugs.kde.org/show_bug.cgi?id=429853 Bug ID: 429853 Summary: Aspect Ratio One Pixel Error Product: digikam Version: 7.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Crop Assignee: digikam-bugs-n...@kde.org Reporter: ma...@comparat.de Target Milestone: --- SUMMARY If I set to 5:4 ratio and draw the rectangle on the image, the result is not exact. Have an image with 3878x3102 and crop 5:4 to 3846x3077 it is 1 Pixel wrong. If I export the image to a width of 800, then the height is 639, not 640. STEPS TO REPRODUCE 1. Take an image 2. Make an crop (i.e 5:4) 3. Look at the size result. If the short side is not dividable with 4, the result is wrong. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429853] Aspect Ratio One Pixel Error
https://bugs.kde.org/show_bug.cgi?id=429853 --- Comment #5 from Manfred Rebentisch --- If I export the picture to local storage, I can choose the width of the image. Set this to 800px and start export, then the image becomes 800x639. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 --- Comment #6 from Manfred Knick --- Burying my father took precedence. - - - - - Multiple separate X11 screens setup (Zaphod, no Xinerama), although being a perfect liable X11 option, has been ignored and explicitly labeled as "irrelevant" by the two main KDE developers and others. Thus I finally gave up on KDE and dbus broken by design. https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&email2=Manfred.Knick%40T-Online.de&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype2=substring&list_id=1818181&order=Importance&query_format=advanced is dating back to 2015 and before. Reported errors have been verified even on ctwm (!) with 4 screens. After all these years of ignorance, NEEDSINFO sounds quite bitter in my ears. The named setup is not available any more. RESOLVED as WONTFIX would be much more honest, at least. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421922] kde-apps/akonadi-{19.08.3,19.12.2} with dev-db/mysql-8.0.19{-r1} - error: 'Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2)'
https://bugs.kde.org/show_bug.cgi?id=421922 --- Comment #10 from Manfred Knick --- Does Akonadi 20.12.0 contain any progress on this issue? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 415694] New: Gwenview crashed after watching a video
https://bugs.kde.org/show_bug.cgi?id=415694 Bug ID: 415694 Summary: Gwenview crashed after watching a video Product: gwenview Version: 19.08.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: manfred.kitzbich...@gmail.com Target Milestone: --- Application: gwenview (19.08.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I watched a couple of videos. With every video the playback became more choppy. When I tried to get out of fullscreen mode, it crashed altogether. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fde41e57300 (LWP 5850))] Thread 4 (Thread 0x7fde3ba3d700 (LWP 5858)): #0 0x7fde43ac56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fde3c09301b in () at /usr/lib64/dri/i965_dri.so #2 0x7fde3c092f17 in () at /usr/lib64/dri/i965_dri.so #3 0x7fde43abef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7fde453544af in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fde3ed73700 (LWP 5852)): #0 0x7fde45349bdf in poll () at /lib64/libc.so.6 #1 0x7fde43233a5e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fde43233b2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fde458eb99b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fde458940db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fde456cc021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fde450f64f6 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fde456cd1a2 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fde43abef2a in start_thread () at /lib64/libpthread.so.0 #9 0x7fde453544af in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fde3fe24700 (LWP 5851)): #0 0x7fde45349bdf in poll () at /lib64/libc.so.6 #1 0x7fde431b6742 in () at /usr/lib64/libxcb.so.1 #2 0x7fde431b73fa in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fde3fff2f90 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fde456cd1a2 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fde43abef2a in start_thread () at /lib64/libpthread.so.0 #6 0x7fde453544af in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fde41e57300 (LWP 5850)): [KCrash Handler] #6 0x7fde46e41fcb in KIO::UDSEntry::UDSEntry(KIO::UDSEntry const&) () at /usr/lib64/libKF5KIOCore.so.5 #7 0x7fde47298fff in Gwenview::ThumbnailProvider::slotResult(KJob*) () at /usr/lib64/libgwenviewlib.so.5 #8 0x7fde458c0638 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #9 0x7fde45c0f10c in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #10 0x7fde45c0fbe3 in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5 #11 0x7fde46f86f60 in () at /usr/lib64/libKF5KIOWidgets.so.5 #12 0x7fde46f8ad42 in () at /usr/lib64/libKF5KIOWidgets.so.5 #13 0x7fde458c0eea in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fde464e2c62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7fde464ec1e0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7fde45895572 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x7fde45898208 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #18 0x7fde458ec343 in () at /usr/lib64/libQt5Core.so.5 #19 0x7fde43231d3d in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #20 0x7fde43233af0 in () at /usr/lib64/libglib-2.0.so.0 #21 0x7fde43233b2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #22 0x7fde458eb981 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #23 0x7fde458940db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #24 0x7fde4589bd42 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #25 0x561a9cc3d09d in () #26 0x7fde4527be0b in __libc_start_main () at /lib64/libc.so.6 #27 0x561a9cc3d66a in _start () [Inferior 1 (process 5850) detached] Possible duplicates by query: bug 414685, bug 413345, bug 412296, bug 412235, bug 412110. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387055] New: konsole crashes during start of KDE
https://bugs.kde.org/show_bug.cgi?id=387055 Bug ID: 387055 Summary: konsole crashes during start of KDE Product: konsole Version: 17.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: manfred.haer...@rz-online.de Target Milestone: --- Application: konsole (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.92-31-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: I started KDE with 10 instances of konsole saved at the last logout. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f068f27e8c0 (LWP 4864))] Thread 5 (Thread 0x7f0666478700 (LWP 4942)): #0 0x7f0686b0f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f067232d233 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f067232cdb7 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f0686b0a744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f068ebd8aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f0666c79700 (LWP 4941)): #0 0x7f0686b0f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f067232d233 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f067232cdb7 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f0686b0a744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f068ebd8aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0673df5700 (LWP 4870)): #0 0x7f068ebd020d in poll () at /lib64/libc.so.6 #1 0x7f06865ed314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f06865ed42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f068b1d41ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f068b181bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f068afbcf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f0689381295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f068afc1a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f0686b0a744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f068ebd8aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f067a348700 (LWP 4868)): #0 0x7f068ebd020d in poll () at /lib64/libc.so.6 #1 0x7f0686f2d3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f0686f2efcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f067c8a30d9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f068afc1a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f0686b0a744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f068ebd8aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f068f27e8c0 (LWP 4864)): [KCrash Handler] #6 0x7f0686b144a0 in __lll_unlock_elision () at /lib64/libpthread.so.0 #7 0x7f068b63812b in KSharedDataCache::find(QString const&, QByteArray*) const () at /usr/lib64/libKF5CoreAddons.so.5 #8 0x7f068db54c18 in () at /usr/lib64/libKF5IconThemes.so.5 #9 0x7f068db55b20 in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () at /usr/lib64/libKF5IconThemes.so.5 #10 0x7f068db4cd60 in KIconEngine::pixmap(QSize const&, QIcon::Mode, QIcon::State) () at /usr/lib64/libKF5IconThemes.so.5 #11 0x7f068b9dda4e in QIcon::pixmap(QWindow*, QSize const&, QIcon::Mode, QIcon::State) const () at /usr/lib64/libQt5Gui.so.5 #12 0x7f068b9ddafa in QIcon::pixmap(QSize const&, QIcon::Mode, QIcon::State) const () at /usr/lib64/libQt5Gui.so.5 #13 0x7f068c19b788 in QCommonStyle::standardPixmap(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f068c1a24f5 in QCommonStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f0673dfc241 in KStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () at /usr/lib64/libKF5Style.so.5 #16 0x7f0678204234 in () at /usr/lib64/qt5/plugins/styles/breeze.so #17 0x7f0678211d1d in () at /usr/lib64/qt5/plugins/styles/breeze.so #18 0x7f068c261425 in () at /usr/lib64/libQt5Widgets.so.5 #19 0x7f068c266620 in QLineEdit::setClearButtonEnabled(bool) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7f068e82df5f in () at /usr/lib64/libkonsoleprivate.so.17 #21 0x7f068e883b47 in () at /usr/lib64/libkonsoleprivate.so.17 #22 0x7f068e884d62 in () at /usr/lib64/libkonsoleprivate.so.17 #23 0x7f068e88e2e1 in Konsole::ViewManager::createContainer() () at /usr/lib64/libkonsoleprivate.so.17 #24 0x7f068e88efd0 in Konsole::ViewManager::createView(Kons
[konsole] [Bug 387055] konsole crashes during start of KDE
https://bugs.kde.org/show_bug.cgi?id=387055 Manfred Haertel changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Manfred Haertel --- The reason for the crashes was that the file icon-cache.kcache resided on an NFS partition. I put it on a local partition and had no more crashes. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] New: [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 Bug ID: 379914 Summary: [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab Product: konsole Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105597 --> https://bugs.kde.org/attachment.cgi?id=105597&action=edit emerge --info konsole >> 0_emerge--info-konsole.txt Description: AWESOME Issue #1784 [Multiple separate X11 screens] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab https://github.com/awesomeWM/awesome/issues/1784 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #3 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488
--- Comment #4 from Manfred Knick ---
Although confirmed as working stable multiple times,
unfortunately, Elv13 stated that nobody @ Awesome would care about
independent X11 screens ("ZaphoMode") any more;
c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff.
Same disinterest stated by leading upstream (=KDE) developers.
If really nobody cares besides me,
I do not mind to close as "WONTFIX".
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 --- Comment #2 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489
--- Comment #3 from Manfred Knick ---
Although confirmed as working stable multiple times,
unfortunately, Elv13 stated that nobody @ Awesome would care about
independent X11 screens ("ZaphoMode") any more;
c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff.
Same disinterest stated by leading upstream (=KDE) developers.
If really nobody cares besides me,
I do not mind to close as "WONTFIX".
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 --- Comment #1 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914
--- Comment #2 from Manfred Knick ---
Although confirmed as working stable multiple times,
unfortunately, Elv13 stated that nobody @ Awesome would care about
independent X11 screens ("ZaphoMode") any more;
c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff.
Same disinterest stated by leading upstream (=KDE) developers.
If really nobody cares besides me,
I do not mind to close as "WONTFIX".
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 381111] New: Plasma crash - yet again
https://bugs.kde.org/show_bug.cgi?id=38 Bug ID: 38 Summary: Plasma crash - yet again Product: plasmashell Version: 5.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfred.kitzbich...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.11.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had Firefox open but wasn't actively browsing. I worked remotely using x2go on a server and left the computer for a few minutes. When I came back the screen was in power save mode and Firefox as well as Plasma had crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8cea6538c0 (LWP 4799))] Thread 22 (Thread 0x7f8bcc756700 (LWP 17300)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f8bf9376700 (LWP 1000)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f8bfb254700 (LWP 25728)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f8bfd75f700 (LWP 25076)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f8bfe060700 (LWP 9606)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f8c0bbc6700 (LWP 9605)): #0 0x7f8cd9948b98 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #1 0x7f8cd9949d68 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f8cd994a089 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #3 0x7f8cd994a90a in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #4 0x7f8cda8fb43c in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #5 0x7f8cda8fb83c in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #6 0x7f8cda8fb8e0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #7 0x7f8cda9098c9 in () at /usr/lib64/libpulse.so.0 #8 0x7f8cd995a258 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #9 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8c1728d700 (LWP 9604)): #0 0x7f8cdeb422d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8cdeafc454 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8cdeafca
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 Manfred Knick changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WONTFIX --- Comment #5 from Manfred Knick --- > Would that be okay for you? Certainly, as already proposed at the end of comment 3 above. Julian, I'm sorry but I have given up on KDE in scenarios where I necessarily have to combine multiple different HW adapters, ensuring that special applications definitely run on their desired monitor ... Thanks for looking into the issue and for your polite, friendly statement. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401714] New: Plasma crash when connecting Bluetooth
https://bugs.kde.org/show_bug.cgi?id=401714 Bug ID: 401714 Summary: Plasma crash when connecting Bluetooth Product: plasmashell Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfred.kitzbich...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.15-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I tried to connect to my laptop from my mobile phone through Bluetooth, using the computer as audio sink. This has worked in the past. this time, coincidence or not, it seems to have killed Plasma. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faba079a880 (LWP 2107))] Thread 29 (Thread 0x7fab4dcc9700 (LWP 23304)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fab4e4ca700 (LWP 23303)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fab4f4f2700 (LWP 23302)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fab4fcf3700 (LWP 23301)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
[krunner] [Bug 395524] New: Krunner crashed when I tried to start gimp through it
https://bugs.kde.org/show_bug.cgi?id=395524 Bug ID: 395524 Summary: Krunner crashed when I tried to start gimp through it Product: krunner Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: manfred.kitzbich...@gmail.com Target Milestone: --- Application: krunner (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.16.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I opened the krunner window on the top by typing alt-F2 and typed gimp into it followed by enter. Next thing the crash reporter popped up. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa89f3a6340 (LWP 3517))] Thread 17 (Thread 0x7fa8619f0700 (LWP 1625)): #0 0x7fa89842c56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa89b227efb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa89b2206db in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa89b42a54a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa869a659ff in () at /usr/lib64/qt5/plugins/krunner_placesrunner.so #5 0x7fa8828a4710 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib64/libKF5Runner.so.5 #6 0x7fa8826842e8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fa882683060 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fa882682b2d in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fa89b226ba0 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fa89842659b in start_thread () at /lib64/libpthread.so.0 #11 0x7fa89ab1fa1f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fa8621f1700 (LWP 1624)): #0 0x7fa89842c56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa89b227efb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa882680ad5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fa882684b28 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fa88267fcfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fa882682a6b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fa89b226ba0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fa89842659b in start_thread () at /lib64/libpthread.so.0 #8 0x7fa89ab1fa1f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fa8629f2700 (LWP 1623)): #0 0x7fa89842c56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa89b227efb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa89b2206db in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa89b42a54a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #4 0x7fa869a659ff in () at /usr/lib64/qt5/plugins/krunner_placesrunner.so #5 0x7fa8828a4710 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib64/libKF5Runner.so.5 #6 0x7fa8826842e8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fa882683060 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fa882682b2d in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fa89b226ba0 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fa89842659b in start_thread () at /lib64/libpthread.so.0 #11 0x7fa89ab1fa1f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fa8631f3700 (LWP 1622)): #0 0x7fa89842c56c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa89b227efb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa882680ad5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fa882684b28 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fa88267fcfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fa882682a6b in ThreadWeaver::T
[plasmashell] [Bug 384713] New: Plasma crash - again
https://bugs.kde.org/show_bug.cgi?id=384713 Bug ID: 384713 Summary: Plasma crash - again Product: plasmashell Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfred.kitzbich...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I changed the WiFi network using the icon in the system tray. This worked, but at the same time the desktop went black and respawned plasma (I was not logged out though). -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90003e8900 (LWP 1801))] Thread 24 (Thread 0x7f8f042c7700 (LWP 29748)): #0 0x7f8ff4a37b89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8ff49f20d5 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ff49f2c5b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ff49f2e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8ffa3286ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ffa2d135a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ffa10131a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ffd24d705 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f8ffa105d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8ff92b92e8 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ff9a085df in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f8f056c8700 (LWP 29607)): #0 0x7f8ff4a37ba4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8ff49f2258 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ff49f2c5b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ff49f2e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8ffa3286ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ffa2d135a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ffa10131a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ffd24d705 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f8ffa105d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8ff92b92e8 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ff9a085df in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f8f09c86700 (LWP 27931)): #0 0x7f8ff4a37b89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8ff49f1bb0 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ff49f2be5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ff49f2e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8ffa3286ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ffa2d135a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ffa10131a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ffd24d705 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f8ffa105d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8ff92b92e8 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ff9a085df in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f8f0b1da700 (LWP 27914)): #0 0x7f8ff4a37b80 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8ff49f2451 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8ff49f2ca7 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8ff49f2e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8ffa3286ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ffa2d135a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8ffa10131a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f8ffd24d705 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f8ffa105d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f8ff92b92e8 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ff9a085df in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f8f1acac700 (LWP 21414)): #0 0x7f8fef7fc5dc in pa_pstream_ref () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #1 0x7f8fef7fcd94 in () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #2 0x7f8fef7fd169 in () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #3 0x7f8fef7fd9ef in () at /usr/lib64/pulseaudio/libpulsecommon-11.0.so #4 0x7f8ff07bd4b8 in pa_mainloop_dispatch () at /usr/lib64/lib
[kate] [Bug 379488] New: [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 Bug ID: 379488 Summary: [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen Product: kate Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105329 --> https://bugs.kde.org/attachment.cgi?id=105329&action=edit emerge --info kate >> 0_emerge--info-kate.txt Overview: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 Description of Startup Procedure: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 Observation of Patterns: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 Please, let me know which further information would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] New: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 Bug ID: 379489 Summary: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen Product: dolphin Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105331 --> https://bugs.kde.org/attachment.cgi?id=105331&action=edit emerge --info dolphin >> 0_emerge--info-dolphin.txt Apps started via file-entries' context menu pop up on a wrong X11 screen. The real pursuit may well reside inside klauncher or dbus. In case, please be so kind to re-locate (I am not a QT/KDE expert). Overview: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 Description of Startup Procedure: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 Observation of Patterns: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 Please, let me know which further information would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 --- Comment #1 from Manfred Knick --- Created attachment 105332 --> https://bugs.kde.org/attachment.cgi?id=105332&action=edit emerge --info dbus >> 0_emerge--info-dbus.txt -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #1 from Manfred Knick --- In contrast to . . . "konsole --separate" [ https://github.com/awesomeWM/awesome/issues/598#issuecomment-166920100 ] , . . . "kate --startanon" . . . "kate -s" . . . "kate --n" do not help, as already stated in [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 ] . -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 379569] New: Korganizer crashes when program is closed
https://bugs.kde.org/show_bug.cgi?id=379569 Bug ID: 379569 Summary: Korganizer crashes when program is closed Product: korganizer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kde...@scaltro.net Target Milestone: --- Application: korganizer (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.39-53-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: application works without problem but crashes when I try to close it. The problem is persistent. The user account data has been transferred from a different system and the file system with config and caches went full a couple of times while application was running. I was trying to clean up caches. This seemed to help for a short period of times but after a while the crashes came back and stayed until now. No full filesystem and migration since cache cleanup. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f799f607600 in QAbstractSlider::maximum() const () at /usr/lib64/libQtGui.so.4 #7 0x7f79a08ef334 in () at /usr/lib64/libkdeui.so.5 #8 0x7f799fed545e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #9 0x7f799f2576fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #10 0x7f799f25dc3d in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #11 0x7f79a091ee3a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #12 0x7f799febd14d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #13 0x7f799fec041d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #14 0x7f799feea7be in () at /usr/lib64/libQtCore.so.4 #15 0x7f79977a5c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x7f79977a5ed8 in () at /usr/lib64/libglib-2.0.so.0 #17 0x7f79977a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x7f799fee9f7e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #19 0x7f799f2f4606 in () at /usr/lib64/libQtGui.so.4 #20 0x7f799febbd0f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #21 0x7f799febc005 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #22 0x7f799fec1459 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #23 0x004082de in () #24 0x7f799e758b25 in __libc_start_main () at /lib64/libc.so.6 #25 0x004085a4 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 379574] New: korganizer crashes when program is closed
https://bugs.kde.org/show_bug.cgi?id=379574 Bug ID: 379574 Summary: korganizer crashes when program is closed Product: korganizer Version: 5.1.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kde...@scaltro.net Target Milestone: --- Application: korganizer (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.1.39-53-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: crash window appears when application is closed. korganizer has been updated to korganizer5 al recommended in bug report #379569. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe97fbeb800 (LWP 4154))] Thread 7 (Thread 0x7fe93d61c700 (LWP 4168)): #0 0x7fe97b741bfd in poll () at /lib64/libc.so.6 #1 0x7fe973190e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe97319119a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe9584b9426 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7fe9731b5f65 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe9736ad0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe97b74a02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe94b7fe700 (LWP 4162)): #0 0x7fe9731d2d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fe9731904a0 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe973190d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe973190f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe97c285d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe97c22cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe97c04e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fe97c05332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe9736ad0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe97b74a02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe94bfff700 (LWP 4160)): #0 0x7fe9731d2d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fe9731904a0 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe973190d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe973190f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe97c285d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe97c22cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe97c04e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fe97c05332f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe9736ad0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe97b74a02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe950ff8700 (LWP 4158)): #0 0x7fe97b756c64 in clock_gettime () at /lib64/libc.so.6 #1 0x7fe97c1047d6 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fe97c2843b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #3 0x7fe97c284945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe97c285b5e in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe9731904ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7fe973190d80 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fe973190f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7fe97c285d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7fe97c22cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fe97c04e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #11 0x7fe97c05332f in () at /usr/lib64/libQt5Core.so.5 #12 0x7fe9736ad0a4 in start_thread () at /lib64/libpthread.so.0 #13 0x7fe97b74a02d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fe9517f9700 (LWP 4156)): #0 0x7fe97b73dccd in read () at /lib64/libc.so.6 #1 0x7fe9731d1b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe973190999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe973190df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe973190f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe97c285d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe97c22cd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe97c04e61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe97c05332f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fe9736ad0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #2 from Manfred Knick --- CONFIRM: " ... awesome pretty much does the same thing as you do when you start kate from a terminal." https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298390441 At the very end, the cross-check findings concerning "FVWM -s" in [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 ] very much caught myself by suprise against all gathered expectation. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384412] New: gdbconfig - not possible to add attributes to debugger shell script
https://bugs.kde.org/show_bug.cgi?id=384412 Bug ID: 384412 Summary: gdbconfig - not possible to add attributes to debugger shell script Product: kdevelop Version: 5.1.2 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: meckschla...@eurofunk.com CC: niko.s...@gmail.com Target Milestone: --- It seems to me that the problem lies in Config::DebuggerShellEntry which is of type QURL and therefore seems no to be able to receive more than one file entry. (no --arguments). If arguments are given here, nothing is started. The tooltip states: If you want gdb to be executed by a special shell script, which for example properly sets the library path, insert it here e.g.: /path/to/script.sh --scriptArgumentsNote: your script'll be invoked like this: /path/to/script.sh --scriptArguments debugger --debuggerArguments. The workaround at the moment is to pass all arguments in the field "debugger executable". It seems that someone stopped in the middle of the job of refactoring those two fileds to the new format /path/to/script.sh --scriptArguments debugger --debuggerArguments :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #6 from Manfred Knick --- (In reply to Christoph Feck from comment #5) > Since you reported it for multiple KDE applications, .^^. ??? Sorry - I don't understand. > are there actually KDE > applications that work correctly? Lots of. > In other words, is there anything that can > be fixed inside Kate, Surely. Esp., c.f. [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298638157 ] To me, the code trying to map new KDE requests to already running ones seems broken. > or is this a general problem with all Qt5 applications? Definitely _not_ . Perhaps, you might consider reading the links referenced in "Description" above, esp. "Overview" and "... Patterns". Then, note the contradictory cross-check findings concerning ctwm and FVWM. You are welcome to use PM as desired. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381317] Crash when closing window (XWindowTasksModel::Private::removeWindow, :TaskGroupingProxyModel::Private::sourceRowsAboutToBeRemoved)
https://bugs.kde.org/show_bug.cgi?id=381317 Manfred Kitzbichler changed: What|Removed |Added CC||manfred.kitzbichler@gmail.c ||om --- Comment #6 from Manfred Kitzbichler --- *** Bug 38 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381111] Plasma crash - yet again
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #2 from Manfred Kitzbichler --- *** This bug has been marked as a duplicate of bug 381317 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374686] New: html-export
https://bugs.kde.org/show_bug.cgi?id=374686 Bug ID: 374686 Summary: html-export Product: digikam Version: 5.2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Export Assignee: digikam-de...@kde.org Reporter: m_tetzl...@gmx.de Target Milestone: --- We miss the html export function. When does she exist again in kipi-plugins? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #8 from Manfred Knick --- (In reply to Christoph Cullmann from comment #7) > Kate reuses existing instances. Which is a very good habit, indeed! > It ATM tries to reuse the "right" instance > based on your current active virtual desktop. ..^^^ Not precisely: it ignores from which X11 Screen it is requested. > kate -n will avoid that, ... No - c.f. (comment #1) : > > . . . "kate --n" > > do not help, as already stated in ... > I don't see how I can "change" kate to help your with that issue. Evaluate the _tuple_ [ X11 Screen | virtual screen ] of requesting in kate's initial code trying to identify _which_ instance of kate is running on the same X11 Screen. Two humble questions, for example: A) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n325 ff // prefer the Kate instance running on the current virtual desktop ??? Does KWindowSystem::currentDesktop() respect Multiple X11 Screens? B) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n334 ff // query instance current desktop ??? Does QDBusConnection::sessionBus() ? ??? Which sessionBus() ? Always that from Screen_0 ? Compare --> "B" in https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 . P.S.: WONTFIX is o.k. for me ... Thanks for answering! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Manfred Knick changed: What|Removed |Added CC||manfred.kn...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 --- Comment #77 from Manfred Knick --- My very puristic, highly efficient workaround: . . . . . "dwl - dwm for Wayland" My setup: . . . . . 2 x 2 monitors . . . . . . . . . . with 9 "virtual desktops" each ! + run (KDE) applications as you like, ! + on the monitor you like, ! + on the "virtual desktop" you like ! + switch via keyboard: Mod-[1-9] based upon wlroots: [ https://codeberg.org/dwl/dwl ] /* tagging - TAGCOUNT must be no greater than 31 */ #define TAGCOUNT (9) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 --- Comment #79 from Manfred Knick --- (In reply to Oded Arbel from comment #78) > (In reply to Manfred Knick from comment #77) > It is indeed very useful that KDE developers make sure that KDE applications > are available on other platforms. Yes, *very* much appreciated, indeed! And "all the best" to KDE. > This report, though, is about Plasma and KWin. If you are not using (or > planning to use) Plasma and KWin, your input is irrelevant for this ticket. I disagree: dwl demonstrates with how few LoC the long awaited ... Have you missed the term *workaround* , or did you ignore it? As many others, I have been waiting for almost 20 (yes, twenty!) years now. Perhaps, a tiny little bit of humility might be adequate? -- No more on this from me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501393] Window focus is lost after activity switch when using multiple activities and screens (Plasma 6.3.2, Frameworks 6.1.1, Qt 6.8.2)
https://bugs.kde.org/show_bug.cgi?id=501393 Manfred Musch changed: What|Removed |Added CC||manfred.mu...@gmx.de --- Comment #2 from Manfred Musch --- In my case the same behaviour, but with a different distribution. However, I'm not to 100% sure whether it goes hand in hand with the use of Activities. But it could be the case. By the way, to be clear, I'm using Activities (five, to be more precise - with four workspaces on each). - Operating System: openSUSE Tumbleweed 20250317 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 PRO 4650G with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: CSL Computer GmbH -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 497475] media-video/kaffeine-2.1.0_pre20241125 corrupt epgdata.dvb
https://bugs.kde.org/show_bug.cgi?id=497475 Manfred Knick changed: What|Removed |Added CC||manfred.kn...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 505560] smb4k stürzt ab beim Versuch einer smb Verbindung
https://bugs.kde.org/show_bug.cgi?id=505560 --- Comment #2 from Manfred Schirmer --- Auf meiner Distribution (Ubuntu 24.04.1) steht mir leider nur die Version 3.2 zur Verfügung. Die heruntergeladenen Quellen zu 4.0.3 lassen sich nicht übersetzen, cmake bricht mit Fehlermeldungen ab. Inzwischen konnte ich auf Fedora 42 die Version 4.0.0 von Smb4K testen. Damit tritt der beschriebene Fehler nicht mehr auf. Viele Grüße, Manfred -- Manfred Schirmer IT-Services In der Schweiz 7 64686 Lautertal (Odenwald) Am 17.06.25 um 05:45 schrieb Alexander Reinholdt: > https://bugs.kde.org/show_bug.cgi?id=505560 > > --- Comment #1 from Alexander Reinholdt --- > *** English version below *** > > Vielen Dank für den Problembericht. Wie ich gesehen habe, nutzen Sie eine > Entwicklungsversion von Smb4K (3.2.90). Können Sie bitte Version 4.0.3 testen > und mir dann Rückmeldung geben, ob das Problem weiterhin besteht? > > *** > > Thank you for the problem report. I have seen that you are using a development > version of Smb4K (3.2.90). Can you please test version 4.0.3 and let me know > if > the problem persists? > -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 497475] media-video/kaffeine-2.1.0_pre20241125 corrupt epgdata.dvb
https://bugs.kde.org/show_bug.cgi?id=497475 --- Comment #2 from Manfred Knick --- @ Mauro Carvalho Chehab Hi, Mauro, with 129 bugs open, dating back since 2016-08-21 , this latest one with not even one comment at all for half a year, may I humbly ask if you feel responsibility for kaffeine of should it be better honestly buried as "unmaintained upstream"? Kind regards Respectfully yours "Old (gentoo) fogey" Manfred -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 505560] New: smb4k stürzt ab beim Versuch einer smb Verbindung
https://bugs.kde.org/show_bug.cgi?id=505560 Bug ID: 505560 Summary: smb4k stürzt ab beim Versuch einer smb Verbindung Classification: Applications Product: Smb4k Version First unspecified Reported In: Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: manf...@schirmer.io Target Milestone: --- Application: smb4k (3.2.90) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.11.0 Operating System: Linux 6.11.0-105009-tuxedo x86_64 Windowing System: Wayland Distribution: TUXEDO OS DrKonqi: 6.3.2 [KCrashBackend] -- Information about the crash: Dialog zum Einhängen -> Ort: //smbhost/share -> Benutzername / Passwort -> OK -> Absturz The crash can be reproduced sometimes. -- Backtrace: Application: Smb4K (smb4k), signal: Segmentation fault [KCrash Handler] #4 0x7664eecb9db9 in ??? () at /lib/x86_64-linux-gnu/libsmb4kcore.so #5 0x7664ed0763e9 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #6 0x7664eec806d9 in Smb4KCredentialsManager::credentialsUpdated(QUrl const&) () at /lib/x86_64-linux-gnu/libsmb4kcore.so #7 0x7664eeca622e in Smb4KCredentialsManager::writeLoginCredentials(QSharedPointer const&) () at /lib/x86_64-linux-gnu/libsmb4kcore.so #8 0x7664eeea4c84 in Smb4KPasswordDialog::accept() () at /lib/x86_64-linux-gnu/libsmb4kdialogs.so #9 0x7664ed0763e9 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #10 0x7664ee1104a8 in ??? () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #11 0x7664ed0763e9 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #12 0x7664ee1a1af4 in QAbstractButton::clicked(bool) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #13 0x7664ee19959f in ??? () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #14 0x7664ee199872 in ??? () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #15 0x7664ee1a4b73 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #16 0x7664ee24160e in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #17 0x7664ee201158 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #18 0x7664ee206d17 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #19 0x7664ed0aefa0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #20 0x7664ee1fd2ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #21 0x7664ee2546c5 in ??? () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #22 0x7664ee25750d in ??? () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #23 0x7664ee201158 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #24 0x7664ed0aefa0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #25 0x7664ed4e2fff in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #26 0x7664ed5403ac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #27 0x7664ed95a794 in ??? () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #28 0x7664ea69a5c5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7664ea6f9737 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7664ea699a63 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7664ece6e6ef in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #32 0x7664ed0b14d3 in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #33 0x7664ed0b2ffd in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #34 0x6073fd011c39 in ??? () #35 0x7664ec42a1ca in __libc_start_call_main (main=main@entry=0x6073fd011560, argc=argc@entry=1, argv=argv@entry=0x7ffd46cab008) at ../sysdeps/nptl/libc_start_call_main.h:58 #36 0x7664ec42a28b in __libc_start_main_impl (main=0x6073fd011560, argc=1, argv=0x7ffd46cab008, init=, fini=, rtld_fini=, stack_end=0x7ffd46caaff8) at ../csu/libc-start.c:360 #37 0x6073fd011cf5 in ??? () [Inferior 1 (process 6720) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357189] New: Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab
https://bugs.kde.org/show_bug.cgi?id=357189 Bug ID: 357189 Summary: Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab Product: plasmashell Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfredkel...@freenet.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.2) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: First I made a System upgrade via DVD from openSUSE 13.2 x64 to openSUSE LEAP 42.1 x 64. The upgrade was done without any problems and I tryed, after the last reboot do modify the mini programs. Suddenly plasmashell crashs. Online search with google dosn't give matching results. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d83fb47c0 (LWP 12326))] Thread 17 (Thread 0x7f2d6d82d700 (LWP 12327)): #0 0x7f2d7d462c1d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2d823f9422 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f2d6d82cd00) at /usr/include/bits/poll2.h:46 #2 0x7f2d823f9422 in _xcb_conn_wait (c=c@entry=0x7c8020, cond=cond@entry=0x7c8060, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7f2d823fb00f in xcb_wait_for_event (c=0x7c8020) at xcb_in.c:693 #4 0x7f2d6f9a5c29 in QXcbEventReader::run() (this=0x7d65b0) at qxcbconnection.cpp:1214 #5 0x7f2d7db6055f in QThreadPrivate::start(void*) (arg=0x7d65b0) at thread/qthread_unix.cpp:331 #6 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d6d82d700) at pthread_create.c:309 #7 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 16 (Thread 0x7f2d66b35700 (LWP 12329)): #0 0x7f2d7d462c1d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2d79ad9e64 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f2d60003070, timeout=-1, context=0x7f2d6990) at gmain.c:4103 #2 0x7f2d79ad9e64 in g_main_context_iterate (context=context@entry=0x7f2d6990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3803 #3 0x7f2d79ad9f7c in g_main_context_iteration (context=0x7f2d6990, may_block=1) at gmain.c:3869 #4 0x7f2d7dd91a5b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2d68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f2d7dd38a63 in QEventLoop::exec(QFlags) (this=this@entry=0x7f2d66b34df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2d7db5b84a in QThread::exec() (this=this@entry=0x8b83c0) at thread/qthread.cpp:503 #7 0x7f2d80e9e5f8 in QQmlThreadPrivate::run() (this=0x8b83c0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f2d7db6055f in QThreadPrivate::start(void*) (arg=0x8b83c0) at thread/qthread_unix.cpp:331 #9 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d66b35700) at pthread_create.c:309 #10 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 15 (Thread 0x7f2d58f25700 (LWP 12330)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d58f25700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7f2d58724700 (LWP 12331)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d58724700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 13 (Thread 0x7f2d57f23700 (LWP 12332)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2d5f9d1023 in () at /usr/lib64/dri/swrast_dri.so #2 0x7f2d5f9d0b97 in () at /usr/lib64/dri/swrast_dri.so #3 0x7f2d7cc5e0a4 in start_thread (arg=0x7f2d57f23700) at pthread_create.c:309 #4 0x7f2d7d46b04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7f2d57722700 (LWP 12333)): #0 0x7f2d7cc6205f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/
[plasmashell] [Bug 357189] Plasmashell stürzt mit Segmentation Fault 11 beim Systemstart ab
https://bugs.kde.org/show_bug.cgi?id=357189 Manfred changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Manfred --- Thank you for your contribution. This was the right way. I searched in YAST for libQt5WebKit.so.5 and tried some packages of WebKit delete . That was not easy, because it has a lot of dependencies , but at last I could delete the package webkitpart . After restarting the system there was no crash anymore, so I could remove the Web browser widget. I think this problem is solved. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 Manfred Kitzbichler changed: What|Removed |Added CC||manfred.kitzbichler@gmail.c ||om --- Comment #2 from Manfred Kitzbichler --- Same here. I just did a zypper dup to the newest Tumbleweed repository with Plasma 5.8 and Qt 5.7 and I am getting a crash everytime. Also when starting the greeter manually from the console as suggested by Martin. GDB says it crashes in libQtQuick5.so: Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault. 0x75de07ff in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 --- Comment #3 from Manfred Kitzbichler --- Here is a hopefully more informative backtrace: #0 0x75de07ff in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #1 0x75dfb396 in ?? () from /usr/lib64/libQt5Quick.so.5 #2 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #3 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #4 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #5 0x75dfbb06 in ?? () from /usr/lib64/libQt5Quick.so.5 #6 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #7 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #8 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #9 0x75dfb396 in ?? () from /usr/lib64/libQt5Quick.so.5 #10 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #11 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #12 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #13 0x7fffdeb85c26 in ?? () #14 0x0098c5f0 in ?? () #15 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #16 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #17 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #18 0x75dfbea6 in ?? () from /usr/lib64/libQt5Quick.so.5 #19 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #20 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #21 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #22 0x75dfbb06 in ?? () from /usr/lib64/libQt5Quick.so.5 #23 0x76baf548 in KDeclarative::QmlObject::~QmlObject() () from /usr/lib64/libKF5Declarative.so.5 #24 0x76bb00a9 in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /usr/lib64/libKF5Declarative.so.5 #25 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #26 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #27 0x74ca91d9 in QWindow::~QWindow() () from /usr/lib64/libQt5Gui.so.5 #28 0x75decb24 in QQuickWindow::~QQuickWindow() () from /usr/lib64/libQt5Quick.so.5 #29 0x779ca319 in KQuickAddons::QuickViewSharedEngine::~QuickViewSharedEngine() () from /usr/lib64/libKF5QuickAddons.so.5 #30 0x0040d1ae in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:323 #31 qDeleteAll > (c=...) at /usr/include/qt5/QtCore/qalgorithms.h:331 #32 ScreenLocker::UnlockApp::~UnlockApp (this=0x7fffdb60, __in_chrg=) at /usr/src/debug/kscreenlocker-5.8.0/greeter/greeterapp.cpp:118 #33 0x00409ba0 in main (argc=, argv=) at /usr/src/debug/kscreenlocker-5.8.0/greeter/main.cpp:79 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 --- Comment #5 from Manfred Kitzbichler --- Does this help? #0 0x75de07ff in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #1 0x75dfb396 in ?? () from /usr/lib64/libQt5Quick.so.5 #2 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #3 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #4 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #5 0x75dfbb06 in ?? () from /usr/lib64/libQt5Quick.so.5 #6 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #7 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #8 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #9 0x75dfb396 in ?? () from /usr/lib64/libQt5Quick.so.5 #10 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #11 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #12 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #13 0x7fffdeb85c26 in ?? () #14 0x0098c370 in ?? () #15 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #16 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #17 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #18 0x75dfbea6 in ?? () from /usr/lib64/libQt5Quick.so.5 #19 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #20 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #21 0x75de09f3 in QQuickItem::~QQuickItem() () from /usr/lib64/libQt5Quick.so.5 #22 0x75dfbb06 in ?? () from /usr/lib64/libQt5Quick.so.5 #23 0x76baf548 in KDeclarative::QmlObjectPrivate::~QmlObjectPrivate (this=0x6fd0d0, __in_chrg=) at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobject.cpp:73 #24 KDeclarative::QmlObject::~QmlObject (this=0x6b0750, __in_chrg=) at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobject.cpp:201 #25 0x76bb00a9 in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine (this=0x6b0750, __in_chrg=) at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobjectsharedengine.cpp:79 #26 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #27 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #28 0x74ca91d9 in QWindow::~QWindow() () from /usr/lib64/libQt5Gui.so.5 #29 0x75decb24 in QQuickWindow::~QQuickWindow() () from /usr/lib64/libQt5Quick.so.5 #30 0x779ca319 in KQuickAddons::QuickViewSharedEngine::~QuickViewSharedEngine() () from /usr/lib64/libKF5QuickAddons.so.5 #31 0x0040d1ae in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:323 #32 qDeleteAll > (c=...) at /usr/include/qt5/QtCore/qalgorithms.h:331 #33 ScreenLocker::UnlockApp::~UnlockApp (this=0x7fffdb20, __in_chrg=) at /usr/src/debug/kscreenlocker-5.8.0/greeter/greeterapp.cpp:118 #34 0x00409ba0 in main (argc=, argv=) at /usr/src/debug/kscreenlocker-5.8.0/greeter/main.cpp:79 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 --- Comment #6 from Manfred Kitzbichler --- Just installed the whole >200MB libQtQuick5 debugsource. This is what I am getting: (gdb) bt #0 0x75de07ff in QQuickItem::~QQuickItem (this=0xf58080, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2341 #1 0x75dfb396 in QQmlPrivate::QQmlElement::~QQmlElement (this=0xf58080, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #2 QQmlPrivate::QQmlElement::~QQmlElement (this=0xf58080, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #3 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #4 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #5 0x75de09f3 in QQuickItem::~QQuickItem (this=0xf74830, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2316 #6 0x75dfbb06 in QQmlPrivate::QQmlElement::~QQmlElement (this=0xf74830, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #7 QQmlPrivate::QQmlElement::~QQmlElement (this=0xf74830, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #8 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #9 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #10 0x75de09f3 in QQuickItem::~QQuickItem (this=0xfae9a0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2316 #11 0x75dfb396 in QQmlPrivate::QQmlElement::~QQmlElement (this=0xfae9a0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #12 QQmlPrivate::QQmlElement::~QQmlElement (this=0xfae9a0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #13 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #14 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #15 0x75de09f3 in QQuickItem::~QQuickItem (this=0xf88890, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2316 #16 0x7fffdeb85c26 in ?? () #17 0x00941710 in ?? () #18 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #19 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #20 0x75de09f3 in QQuickItem::~QQuickItem (this=0x97bec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2316 #21 0x75dfbea6 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x97bec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #22 QQmlPrivate::QQmlElement::~QQmlElement (this=0x97bec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #23 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #24 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #25 0x75de09f3 in QQuickItem::~QQuickItem (this=0x9eaec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2316 #26 0x75dfbb06 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x9eaec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #27 QQmlPrivate::QQmlElement::~QQmlElement (this=0x9eaec0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlprivate.h:104 #28 0x76baf548 in KDeclarative::QmlObjectPrivate::~QmlObjectPrivate (this=0x6fd140, __in_chrg=) ---Type to continue, or q to quit--- at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobject.cpp:73 #29 KDeclarative::QmlObject::~QmlObject (this=0x6c9470, __in_chrg=) at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobject.cpp:201 #30 0x76bb00a9 in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine (this=0x6c9470, __in_chrg=) at /usr/src/debug/kdeclarative-5.26.0/src/kdeclarative/qmlobjectsharedengine.cpp:79 #31 0x747736d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #32 0x7477ca4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #33 0x74ca91d9 in QWindow::~QWindow() () from /usr/lib64/libQt5Gui.so.5 #34 0x75decb24 in QQuickWindow::~QQuickWindow (this=0x6944b0, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickwindow.cpp:1210 #35 0x779ca319 in KQuickAddons::QuickViewSharedEngine::~QuickViewSharedEngine() () from /usr/lib64/libKF5QuickAddons.so.5 #36 0x0040d1ae
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 --- Comment #7 from Manfred Kitzbichler --- This is the offending assignment: Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault. 0x75de07ff in QQuickItem::~QQuickItem (this=0xf58080, __in_chrg=) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/items/qquickitem.cpp:2341 2341QQuickAnchorsPrivate *anchor = change.listener->anchorPrivate(); -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422
--- Comment #9 from Manfred Kitzbichler ---
I did some debugging with gdb and the code line in question is visited about
two dozen times without problem. When it finally crashes that's presumably
because the "listener" entry in the "change" structure has this rather peculiar
value:
print *change.listener
$58 = {_vptr.QQuickItemChangeListener = 0x4545454545454545}
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 --- Comment #10 from Manfred Kitzbichler --- For what it's worth, after I applied the patch below to my version of libqt5declarative the problem is gone. It also has the positive side effect, that plasmashell doesn't crash anymore at logout and probably there are quite a few other Qt applications that crashed occasionally because of this bug. https://codereview.qt-project.org/#/c/170844/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 370977] New: Gwenview crash when video is paused
https://bugs.kde.org/show_bug.cgi?id=370977 Bug ID: 370977 Summary: Gwenview crash when video is paused Product: gwenview Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: manfred.kitzbich...@gmail.com CC: myr...@kde.org Application: gwenview (16.08.1) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.7.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Played a video, pressed space to pause -> crash This happens every time. When I presse ESC instead, I can get back to the browse overview without crash. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffba90839c0 (LWP 4383))] Thread 3 (Thread 0x7ffa47b1c700 (LWP 4388)): #0 0x7ffb9dbf84b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ffba4110346 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7ffba410bb82 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x7ffba410f558 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7ffb9dbf2454 in start_thread () from /lib64/libpthread.so.0 #5 0x7ffba3a1c3ff in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ffb8f439700 (LWP 4385)): #0 0x7ffba3a136ed in poll () from /lib64/libc.so.6 #1 0x7ffb9c37b876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7ffb9c37b98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ffba433279b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7ffba42dc1ea in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7ffba410a8b3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7ffba36bdc15 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7ffba410f558 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7ffb9dbf2454 in start_thread () from /lib64/libpthread.so.0 #9 0x7ffba3a1c3ff in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffba90839c0 (LWP 4383)): [KCrash Handler] #6 0x in ?? () #7 0x7ffba5c94c01 in QGraphicsItem::dragLeaveEvent(QGraphicsSceneDragDropEvent*) () from /usr/lib64/libQt5Widgets.so.5 #8 0x7ffba5cab232 in QGraphicsItemPrivate::setVisibleHelper(bool, bool, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #9 0x7ffba5cbf442 in QGraphicsProxyWidget::eventFilter(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #10 0x7ffba42ddf61 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #11 0x7ffba59be905 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7ffba59c60e1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7ffba42de200 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7ffba5a00cfa in QWidgetPrivate::hide_helper() () from /usr/lib64/libQt5Widgets.so.5 #15 0x7ffba5a05630 in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7ffba5a01028 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7ffba5a014d8 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #18 0x7ffba1c72c2c in ?? () from /usr/lib64/libphonon4qt5.so.4 #19 0x7ffba5cbb318 in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from /usr/lib64/libQt5Widgets.so.5 #20 0x7ffba87a6e79 in Gwenview::DoubleClickableProxyWidget::~DoubleClickableProxyWidget (this=0x1ea4190, __in_chrg=) at /usr/src/debug/gwenview-16.08.1/lib/documentview/videoviewadapter.cpp:186 #21 Gwenview::DoubleClickableProxyWidget::~DoubleClickableProxyWidget (this=0x1ea4190, __in_chrg=) at /usr/src/debug/gwenview-16.08.1/lib/documentview/videoviewadapter.cpp:186 #22 0x7ffba5cae4be in QGraphicsItem::~QGraphicsItem() () from /usr/lib64/libQt5Widgets.so.5 #23 0x7ffba5cae643 in QGraphicsObject::~QGraphicsObject() () from /usr/lib64/libQt5Widgets.so.5 #24 0x7ffba5cfae9c in QGraphicsWidget::~QGraphicsWidget() () from /usr/lib64/libQt5Widgets.so.5 #25 0x7ffba879bdf9 in Gwenview::DocumentView::~DocumentView (this=0x151b860, __in_chrg=) at /usr/src/debug/gwenview-16.08.1/lib/documentview/documentview.cpp:344 #26 0x7ffba430ad90 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #27 0x7ffba5cfc1ab in QGraphicsWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #28 0x7ffba59be92c in QApplicationPrivate::notify_h
[digikam] [Bug 362300] New: digikam crashed
https://bugs.kde.org/show_bug.cgi?id=362300 Bug ID: 362300 Summary: digikam crashed Product: digikam Version: 4.14.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: manfred.ha...@arcor.de Application: digikam (4.14.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Leap 42.1 new startet and afterwards Digikam started. No other activities. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffb64dac880 (LWP 12096))] Thread 6 (Thread 0x7ffb48d2e700 (LWP 12097)): #0 0x7ffb5d7b9bbd in poll () at /lib64/libc.so.6 #1 0x7ffb49874888 in () at /usr/lib64/libusb-1.0.so.0 #2 0x7ffb5c0360a4 in start_thread () at /lib64/libpthread.so.0 #3 0x7ffb5d7c1fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7ffb421fd700 (LWP 12098)): #0 0x7ffb5c03a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ffb5e31d0a6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x005e460e in () #3 0x7ffb5e31cbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7ffb5c0360a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7ffb5d7c1fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7ffb419fc700 (LWP 12099)): #0 0x7ffb5d7b5c8d in read () at /lib64/libc.so.6 #1 0x7ffb55d1fb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffb55cde999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffb55cdedf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ffb55cdef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ffb5e44afde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7ffb5e41cd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7ffb5e41d045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7ffb5e31a4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7ffb5e3fe653 in () at /usr/lib64/libQtCore.so.4 #10 0x7ffb5e31cbbf in () at /usr/lib64/libQtCore.so.4 #11 0x7ffb5c0360a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7ffb5d7c1fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7ffb411fb700 (LWP 12102)): #0 0x7ffb5c03a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ffb5e31d0a6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7ffb63507c3a in () at /usr/lib64/libdigikamcore.so.4.14.0 #3 0x7ffb5e31cbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7ffb5c0360a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7ffb5d7c1fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7ffb33821700 (LWP 12103)): #0 0x7ffb5d7b9bbd in poll () at /lib64/libc.so.6 #1 0x7ffb55cdee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ffb55cdef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ffb5e44afde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7ffb5e41cd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7ffb5e41d045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7ffb5e31a4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7ffb5e3fe653 in () at /usr/lib64/libQtCore.so.4 #8 0x7ffb5e31cbbf in () at /usr/lib64/libQtCore.so.4 #9 0x7ffb5c0360a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7ffb5d7c1fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ffb64dac880 (LWP 12096)): [KCrash Handler] #4 0x7ffb26c04ed5 in QMetaObject::className() const () at /usr/lib64/libQt5Core.so.5 #5 0x7ffb2793815f in () at /usr/lib64/libQt5Widgets.so.5 #6 0x7ffb64c228ea in call_init.part () at /lib64/ld-linux-x86-64.so.2 #7 0x7ffb64c229d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2 #8 0x7ffb64c26b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #9 0x7ffb64c227a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #10 0x7ffb64c262fb in _dl_open () at /lib64/ld-linux-x86-64.so.2 #11 0x7ffb5470602b in dlopen_doit () at /lib64/libdl.so.2 #12 0x7ffb64c227a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #13 0x7ffb547065dd in _dlerror_run () at /lib64/libdl.so.2 #14 0x7ffb547060c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #15 0x7ffb31a20a2f in () at /usr/lib64/libvlccore.so.8 #16 0x7ffb31a060db in () at /usr/lib64/libvlccore.so.8 #17 0x7ff
[kstars] [Bug 359447] In Version 2.3.0 the dialog "Initial position is below horizon" is frozen
https://bugs.kde.org/show_bug.cgi?id=359447 --- Comment #2 from Manfred Dings --- Hello, in Version 2.4.0 (installed within Kubuntu 16.04) this seems to be fixed. Thank you very much, Manfred Dings -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 361037] New: Gwenview export plugin to email images is crashing
https://bugs.kde.org/show_bug.cgi?id=361037 Bug ID: 361037 Summary: Gwenview export plugin to email images is crashing Product: gwenview Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: manfred.kitzbich...@gmail.com CC: myr...@kde.org Application: gwenview (4.14.0 pre) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.5.0-1-default x86_64 Distribution: "openSUSE 20150903 (Tumbleweed) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I selected a view images and tried to email them using the export plugin. I am getting the GUI to select image dimensions and filesize but when I press the send button the plugin crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb39f9d1940 (LWP 26194))] Thread 10 (Thread 0x7fb386c5e700 (LWP 26195)): #0 0x7fb39c3a949d in poll () at /lib64/libc.so.6 #1 0x7fb39922b264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb39922b36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb39ef7c26e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fb39ef4c3e1 in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fb39ef4c6f5 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fb39ee45a59 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fb39ef30c1d in () at /usr/lib64/libQtCore.so.4 #8 0x7fb39ee4823c in () at /usr/lib64/libQtCore.so.4 #9 0x7fb3996fa4a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb39c3b1ded in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb37ebcc700 (LWP 26201)): #0 0x7fb39c3aab13 in select () at /lib64/libc.so.6 #1 0x7fb39ef29a2f in () at /usr/lib64/libQtCore.so.4 #2 0x7fb39ee4823c in () at /usr/lib64/libQtCore.so.4 #3 0x7fb3996fa4a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb39c3b1ded in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb37e3cb700 (LWP 26608)): #0 0x7fb39c3a949d in poll () at /lib64/libc.so.6 #1 0x7fb35f1d4418 in () at /usr/lib64/libusb-1.0.so.0 #2 0x7fb3996fa4a4 in start_thread () at /lib64/libpthread.so.0 #3 0x7fb39c3b1ded in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb37700 (LWP 26609)): #0 0x7fb39970007f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb39ee48754 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7fb37ec954c8 in KIPIPlugins::KPRawThumbThread::run() () at /usr/lib64/libkipiplugins.so.4.14.0 #3 0x7fb39ee4823c in () at /usr/lib64/libQtCore.so.4 #4 0x7fb3996fa4a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb39c3b1ded in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb34d10f700 (LWP 26624)): #0 0x7fb39970007f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb39ee48754 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7fb39ac105c4 in KDcrawIface::RActionThreadBase::run() () at /usr/lib64/libkdcraw.so.23 #3 0x7fb39ee4823c in () at /usr/lib64/libQtCore.so.4 #4 0x7fb3996fa4a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb39c3b1ded in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb34c90e700 (LWP 26625)): [KCrash Handler] #6 0x7fb39bafc7a4 in XMPMeta::RegisterNamespace(char const*, char const*) () at /usr/lib64/libexiv2.so.14 #7 0x7fb39bad8ecb in WXMPMeta_RegisterNamespace_1 () at /usr/lib64/libexiv2.so.14 #8 0x7fb39bacad84 in TXMPMeta, std::allocator > >::RegisterNamespace(char const*, char const*) () at /usr/lib64/libexiv2.so.14 #9 0x7fb39bac7566 in Exiv2::XmpParser::initialize(void (*)(void*, bool), void*) () at /usr/lib64/libexiv2.so.14 #10 0x7fb39bac7a17 in Exiv2::XmpParser::encode(std::__cxx11::basic_string, std::allocator >&, Exiv2::XmpData const&, unsigned short, unsigned int) () at /usr/lib64/libexiv2.so.14 #11 0x7fb39ba5d3ec in Exiv2::JpegBase::doWriteMetadata(Exiv2::BasicIo&) () at /usr/lib64/libexiv2.so.14 #12 0x7fb39ba5e304 in Exiv2::JpegBase::writeMetadata() () at /usr/lib64/libexiv2.so.14 #13 0x7fb37eedf598 in KExiv2Iface::KExiv2::Private::saveOperations(QFileInfo const&, std::auto_ptr) const () at /usr/lib64/libkexiv2.so.11 #14 0x7fb37eee2314 in KExiv2Iface::KExiv2::Private::saveToFile(QFileInfo const&) const () at /usr/lib64/libkexiv2.so.11 #15 0x7fb37eedb683 in KExiv2Iface::KExiv2::save(QString const&) const () at /usr/lib64/libkexiv2.so.11
[kstars] [Bug 359447] New: In Version 2.3.0 the dialog "Initial position is below horizon" is frozen
https://bugs.kde.org/show_bug.cgi?id=359447 Bug ID: 359447 Summary: In Version 2.3.0 the dialog "Initial position is below horizon" is frozen Product: kstars Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: as...@partiturspiel.de When starting kstars 2.3.0 with a position currently below the horizon the dialoge "Initial position is below horizon" is frozen. There are no buttons, the background from the desktop is visible, the dialoge is not painted correctly, it must be killed by the system. Kubuntu 15.10, KDE Plasma 5.4, Kernel 4.2.0-27 generic. It definitively works under Linux Mint Cinnamon 17.3. -- You are receiving this mail because: You are watching all bug changes.
