[ksysguard] [Bug 436713] Plasmashell crash when screensaver starts
https://bugs.kde.org/show_bug.cgi?id=436713 philip mirabelli changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from philip mirabelli --- Loaded plasma-wayland instead of plasma. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 436713] Plasmashell crash when screensaver starts
https://bugs.kde.org/show_bug.cgi?id=436713 --- Comment #1 from philip mirabelli --- apologies its ksysguard that is running in the background -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 436713] New: Plasmashell crash when screensaver starts
https://bugs.kde.org/show_bug.cgi?id=436713 Bug ID: 436713 Summary: Plasmashell crash when screensaver starts Product: ksysguard Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: philipwmirabe...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.12.1-arch1-1 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: crash happens when the screensaver starts and ksystemlog is running in the background The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Floating point exception [KCrash Handler] #4 0x7f933c527a0b in KSignalPlotter::resizeEvent(QResizeEvent*) () at /usr/lib/libksignalplotter.so.9 #5 0x7f933b97766e in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #6 0x7f933b935762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #7 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x7f933b96d594 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () at /usr/lib/libQt5Widgets.so.5 #9 0x7f933b96e460 in QWidget::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f933b957e57 in QWidgetItem::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f933b94de94 in QBoxLayout::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f933b9540e8 in QLayoutPrivate::doResize() () at /usr/lib/libQt5Widgets.so.5 #13 0x7f933b95565e in QLayout::activate() () at /usr/lib/libQt5Widgets.so.5 #14 0x7f933b935745 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f933b96d594 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f933b96e460 in QWidget::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f933b957e57 in QWidgetItem::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f933b952026 in () at /usr/lib/libQt5Widgets.so.5 #20 0x7f933b9524a5 in QGridLayout::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f933b9540e8 in QLayoutPrivate::doResize() () at /usr/lib/libQt5Widgets.so.5 #22 0x7f933b935745 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f933b96d594 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f933b96e460 in QWidget::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f933b9540e8 in QLayoutPrivate::doResize() () at /usr/lib/libQt5Widgets.so.5 #27 0x7f933b95565e in QLayout::activate() () at /usr/lib/libQt5Widgets.so.5 #28 0x7f933b935745 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #29 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #30 0x7f933b96d594 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () at /usr/lib/libQt5Widgets.so.5 #31 0x7f933b96e460 in QWidget::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #32 0x7f933bb0abcc in QTabWidget::setUpLayout(bool) () at /usr/lib/libQt5Widgets.so.5 #33 0x7f933b97766e in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #34 0x7f933b935762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #35 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #36 0x7f933b96d594 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () at /usr/lib/libQt5Widgets.so.5 #37 0x7f933b96e460 in QWidget::setGeometry(QRect const&) () at /usr/lib/libQt5Widgets.so.5 #38 0x7f933bae272c in () at /usr/lib/libQt5Widgets.so.5 #39 0x7f933bae4f52 in () at /usr/lib/libQt5Widgets.so.5 #40 0x7f933b97766e in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #41 0x7f933ba2225f in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #42 0x7f933b935762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #43 0x7f933acea81a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at
[Skanlite] [Bug 433656] Skanlite crashes upon starting
https://bugs.kde.org/show_bug.cgi?id=433656 philip mirabelli changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from philip mirabelli --- Now resolved, a reboot of the HP PSC fixed it -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 433656] New: Skanlite crashes upon starting
https://bugs.kde.org/show_bug.cgi?id=433656 Bug ID: 433656 Summary: Skanlite crashes upon starting Product: Skanlite Version: 2.2.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: philipwmirabe...@gmail.com Target Milestone: --- SUMMARY upon opening skanlite either from cli or menu, it opens briefly then crashes with a message "opening the selected scanner failed". I have a wireless psc HP officejet 5230 and have used skanlite previously without issues. I believe the latest KDE updates may have been the cause. STEPS TO REPRODUCE 1. either issue cli command "skanlite" or click on menu icon. 2. application opens with usual dialog "searching for scanner" 3. application crashes with error message. OBSERVED RESULT application crashes and disappears off the screen EXPECTED RESULT application opens and you select the scanner SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.21.1 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426644] Screens go black / unresponsive after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=426644 philip mirabelli changed: What|Removed |Added CC||philipwmirabe...@gmail.com --- Comment #6 from philip mirabelli --- Similar problem to the one I am having with version 5.9.11-arch2-1 running plasma version 5.20.4 Qt version 5.15.2 & Kde Frameworks version 5.76.0 on a fujitsu lifebook U938 running a Mesa UHD graphics 620. When the notebook is in sleep mode upon reboot the disk sleep plasmashell remains in sleep mode. It exits sleep mode after about 5 minutes. Tried plasmashell --replace but no change. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422817] New: powerdevil locks screen with GPMDP running
https://bugs.kde.org/show_bug.cgi?id=422817 Bug ID: 422817 Summary: powerdevil locks screen with GPMDP running Product: Powerdevil Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: philipwmirabe...@gmail.com Target Milestone: --- Created attachment 129235 --> https://bugs.kde.org/attachment.cgi?id=129235=edit printout from journalctl SUMMARY When running the google play music desktop player version 4.7.1-2 from AUR and the automatic screen saver kicks in, the screen tends t stay locked and powerdevil will not deactivate. I have journalctl output which shows the issue being inability to create AF_NETLINK socket, this happened also on another pc running similar configuration. STEPS TO REPRODUCE 1. run GPMDP in background 2. leave screen to go into sleep mode 3. screen remains locked OBSERVED RESULT screen remains locked and will not reactivate. EXPECTED RESULT screensaver exits and you can log in again SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch with plasma 5.19.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION see attached printout of journalctl -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds
https://bugs.kde.org/show_bug.cgi?id=407397 --- Comment #40 from philip mirabelli --- The issue is also present in Plasma 5.18.2 running version 5.5.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds
https://bugs.kde.org/show_bug.cgi?id=407397 --- Comment #39 from philip mirabelli --- The issue is also present in Plasma 5.18.2 running version 5.5.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds
https://bugs.kde.org/show_bug.cgi?id=407397 philip mirabelli changed: What|Removed |Added Version|5.16.3 |5.18.1 CC||philipwmirabe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 philip mirabelli changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #12 from philip mirabelli --- I have updated relevant AUR packages and tested on various txt formats and the bug seems to have been fixed probably by updating to latest library versions. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #11 from philip mirabelli --- Ok I have checked my shuttle machine and the version of libkgapi is the same as on my other machine i.e. version 19.08.2-1. I have just rechecked editing a .doc file with softoffice Textmaker and it seems to work i.e. no crash bug. I shall continue to edit other files to see if they work seamlessly. On Thu, 2019-10-17 at 14:31 +, David Barchiesi wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #9 from David Barchiesi --- > (In reply to philip mirabelli from comment #8) > > I can confirm I am using: "Name : libkgapi Version: 19.08.2-1":- > > printout from terminal > > > > > > On Thu, 2019-10-17 at 13:15 +, David Barchiesi wrote: > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > --- Comment #7 from David Barchiesi --- > > > (In reply to philip mirabelli from comment #5) > > > > Ok so WPS and Abiword seem to work ok, so its ony Softoffice > > > > Textmaker > > > > that has the issue (and only on the Shuttle machine I have) on > > > > my > > > > other > > > > Fiistu laptop with the same configuration (Arch/KDE etc) it > > > > seems > > > > to > > > > work?? > > > > > > > > On Sun, 2019-10-13 at 13:23 +0000, Elvis Angelaccio wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > > > > > --- Comment #3 from Elvis Angelaccio < > > > > > elvis.angelac...@kde.org> > > > > > --- > > > > > (In reply to philip mirabelli from comment #2) > > > > > > Created attachment 123139 [details] > > > > > > kdeinit5-20191010-222009.kcrash.txt > > > > > > > > > > > > Hi, just tried editing an .rtf file and it does the same > > > > > > thing > > > > > > > > > > Using which application? > > > > > > > > > > > archlinux is using version 19.08.2-1 which has the bug fixed. > > > > > Is that the "Shuttle machine" or the "Fiistu laptop"? Do both have > the same > versions of kio-gdrive and libkgapi? > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #10 from philip mirabelli --- I have checked the Fujitsu laptop the Shuttle I can check later but its updated recently using pacman so I guess the version will be the same but I wil ocnfirm later On Thu, 2019-10-17 at 14:31 +, David Barchiesi wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #9 from David Barchiesi --- > (In reply to philip mirabelli from comment #8) > > I can confirm I am using: "Name : libkgapi Version: 19.08.2-1":- > > printout from terminal > > > > > > On Thu, 2019-10-17 at 13:15 +, David Barchiesi wrote: > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > --- Comment #7 from David Barchiesi --- > > > (In reply to philip mirabelli from comment #5) > > > > Ok so WPS and Abiword seem to work ok, so its ony Softoffice > > > > Textmaker > > > > that has the issue (and only on the Shuttle machine I have) on > > > > my > > > > other > > > > Fiistu laptop with the same configuration (Arch/KDE etc) it > > > > seems > > > > to > > > > work?? > > > > > > > > On Sun, 2019-10-13 at 13:23 +0000, Elvis Angelaccio wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > > > > > --- Comment #3 from Elvis Angelaccio < > > > > > elvis.angelac...@kde.org> > > > > > --- > > > > > (In reply to philip mirabelli from comment #2) > > > > > > Created attachment 123139 [details] > > > > > > kdeinit5-20191010-222009.kcrash.txt > > > > > > > > > > > > Hi, just tried editing an .rtf file and it does the same > > > > > > thing > > > > > > > > > > Using which application? > > > > > > > > > > > archlinux is using version 19.08.2-1 which has the bug fixed. > > > > > Is that the "Shuttle machine" or the "Fiistu laptop"? Do both have > the same > versions of kio-gdrive and libkgapi? > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #8 from philip mirabelli --- I can confirm I am using: "Name : libkgapi Version: 19.08.2-1":- printout from terminal On Thu, 2019-10-17 at 13:15 +, David Barchiesi wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #7 from David Barchiesi --- > (In reply to philip mirabelli from comment #5) > > Ok so WPS and Abiword seem to work ok, so its ony Softoffice > > Textmaker > > that has the issue (and only on the Shuttle machine I have) on my > > other > > Fiistu laptop with the same configuration (Arch/KDE etc) it seems > > to > > work?? > > > > On Sun, 2019-10-13 at 13:23 +, Elvis Angelaccio wrote: > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > --- Comment #3 from Elvis Angelaccio > > > --- > > > (In reply to philip mirabelli from comment #2) > > > > Created attachment 123139 [details] > > > > kdeinit5-20191010-222009.kcrash.txt > > > > > > > > Hi, just tried editing an .rtf file and it does the same thing > > > > > > Using which application? > > > > > archlinux is using version 19.08.2-1 which has the bug fixed. > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #5 from philip mirabelli --- Ok so WPS and Abiword seem to work ok, so its ony Softoffice Textmaker that has the issue (and only on the Shuttle machine I have) on my other Fiistu laptop with the same configuration (Arch/KDE etc) it seems to work?? On Sun, 2019-10-13 at 13:23 +, Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #3 from Elvis Angelaccio --- > (In reply to philip mirabelli from comment #2) > > Created attachment 123139 [details] > > kdeinit5-20191010-222009.kcrash.txt > > > > Hi, just tried editing an .rtf file and it does the same thing > > Using which application? > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #4 from philip mirabelli --- Softmaker Textmaker 2018 Rev 970.0826, 64 bit. I have other text editors -WPS and Abiword I haven't used them, but I'll also check and let you know, best regard Philip On Sun, 2019-10-13 at 13:23 +, Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #3 from Elvis Angelaccio --- > (In reply to philip mirabelli from comment #2) > > Created attachment 123139 [details] > > kdeinit5-20191010-222009.kcrash.txt > > > > Hi, just tried editing an .rtf file and it does the same thing > > Using which application? > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #2 from philip mirabelli --- Hi, just tried editing an .rtf file and it does the same thing - bug report attached. I also tried with a .doc file and it seems to be ok with those, regards On Thu, 2019-10-10 at 19:41 +, Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #1 from Elvis Angelaccio --- > Version of kio-gdrive and libkgapi? Does it crash with every word > file? > -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] New: Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 Bug ID: 412791 Summary: Uploading a docx file causes a crash Product: kio-gdrive Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: philipwmirabe...@gmail.com Target Milestone: --- Created attachment 123112 --> https://bugs.kde.org/attachment.cgi?id=123112=edit generated from bug utility SUMMARY uploading word documents to google drive causes kio-drive to crash STEPS TO REPRODUCE 1. 2. 3. 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.
[okular] [Bug 400559] New: Okular crash on text highlighting
https://bugs.kde.org/show_bug.cgi?id=400559 Bug ID: 400559 Summary: Okular crash on text highlighting Product: okular Version: 1.5.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: philipwmirabe...@gmail.com Target Milestone: --- Application: okular (1.5.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.16-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was simply highlighting text on a downloaded PDF which I have done many times before. I have checked on line and in the Arch forums the issue seems to be with poppler, I will downgrade to versioon 0.70.1-2. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb834f5c800 (LWP 2038))] Thread 4 (Thread 0x7fb821da1700 (LWP 2041)): #0 0x7fb838ec1afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb82236b1ac in () at /usr/lib/dri/i965_dri.so #2 0x7fb82236aee8 in () at /usr/lib/dri/i965_dri.so #3 0x7fb838ebba9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb839b5ab23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb82bfff700 (LWP 2040)): #0 0x7fb839b4b7a4 in read () at /usr/lib/libc.so.6 #1 0x7fb838226781 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb838276a50 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb838277e86 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb838277fce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb83a078fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb83a0248cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb839e6deb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb83a2caba6 in () at /usr/lib/libQt5DBus.so.5 #9 0x7fb839e77f65 in () at /usr/lib/libQt5Core.so.5 #10 0x7fb838ebba9d in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fb839b5ab23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb833566700 (LWP 2039)): #0 0x7fb839b4fc21 in poll () at /usr/lib/libc.so.6 #1 0x7fb8390e4630 in () at /usr/lib/libxcb.so.1 #2 0x7fb8390e62db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fb834b0ac5a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fb839e77f65 in () at /usr/lib/libQt5Core.so.5 #5 0x7fb838ebba9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb839b5ab23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fb834f5c800 (LWP 2038)): [KCrash Handler] #6 0x7fb8214d372f in Poppler::HighlightAnnotationPrivate::toQuadrilaterals(QList const&) const () at /usr/lib/libpoppler-qt5.so.1 #7 0x7fb8214d380f in Poppler::HighlightAnnotation::setHighlightQuads(QList const&) () at /usr/lib/libpoppler-qt5.so.1 #8 0x7fb8214d4f69 in Poppler::HighlightAnnotationPrivate::createNativeAnnot(Page*, Poppler::DocumentData*) () at /usr/lib/libpoppler-qt5.so.1 #9 0x7fb8214cfcfe in Poppler::AnnotationPrivate::addAnnotationToPage(Page*, Poppler::DocumentData*, Poppler::Annotation const*) () at /usr/lib/libpoppler-qt5.so.1 #10 0x7fb828074f39 in () at /usr/lib/qt/plugins/okular/generators/okularGenerator_poppler.so #11 0x7fb83054a9ed in () at /usr/lib/libOkular5Core.so.9 #12 0x7fb83055f254 in () at /usr/lib/libOkular5Core.so.9 #13 0x7fb83ae3d374 in QUndoStack::push(QUndoCommand*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fb83053fdda in Okular::Document::addPageAnnotation(int, Okular::Annotation*) () at /usr/lib/libOkular5Core.so.9 #15 0x7fb8306f6d1a in () at /usr/lib/qt/plugins/okularpart.so #16 0x7fb8306f7071 in () at /usr/lib/qt/plugins/okularpart.so #17 0x7fb830719798 in () at /usr/lib/qt/plugins/okularpart.so #18 0x7fb83ab07658 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fb83abadcef in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fb83071bbf5 in () at /usr/lib/qt/plugins/okularpart.so #21 0x7fb83a02594b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #22 0x7fb83aac7e04 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7fb83aacf92a in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7fb83a025c39 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7fb83aacec11 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
[k3b] [Bug 398991] New: Error reports generated
https://bugs.kde.org/show_bug.cgi?id=398991 Bug ID: 398991 Summary: Error reports generated Product: k3b Version: 18.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video DVD Assignee: k...@kde.org Reporter: philipwmirabe...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 115192 --> https://bugs.kde.org/attachment.cgi?id=115192=edit the attached was generalted by k3b SUMMARY STEPS TO REPRODUCE 1. 2. 3. EXPECTED RESULT ACTUAL RESULT SOFTWARE VERSIONS (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.
[systemsettings] [Bug 383519] New: Bluetooth service will not start
https://bugs.kde.org/show_bug.cgi?id=383519 Bug ID: 383519 Summary: Bluetooth service will not start Product: systemsettings Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: philipwmirabe...@gmail.com Target Milestone: --- bluetooth wizard will not allow me to connect my bluetooth speakers the daemon does not appear to be working. When i click "fix it" in the GUI it appears to work then when I reopen the systems settings the problem returns. Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 378373] SMB4K Crashes
https://bugs.kde.org/show_bug.cgi?id=378373 --- Comment #2 from philip mirabelli <philipwmirabe...@gmail.com> --- Hi Alexander, I am using the latest version 2.0. I have managed to fix the issue: there was a conflict with Kwallet, I had three Kwallet profiles so I deleted 2 and now I have 1 only and SMB4K works fine, no crashes etc. Great product, keep up the good work!!! regards philip On Wed, Apr 12, 2017 at 9:37 AM, Alexander Reinholdt < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=378373 > > --- Comment #1 from Alexander Reinholdt <alexander.reinho...@kdemail.net> > --- > Hi! > > First of all, I would like to know which version of Smb4K you are using? > > I see the NT_STATUS_RESOURCE_NAME_NOT_FOUND error code in the output you > pasted. Could it be that the server that shares the resource you wanted to > mount was/is offline? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 378373] New: SMB4K Crashes
https://bugs.kde.org/show_bug.cgi?id=378373 Bug ID: 378373 Summary: SMB4K Crashes Product: Smb4k Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: philipwmirabe...@gmail.com Target Milestone: --- Hi, when I try to mount a windows share I get the below message and then a short tme later it crashes. Any assistance welcome, thanks philip "retrieving the list of available domains failed: lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" mkdir failed on directory /var/cache/samba/msg.lock: Permission denied lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" added interface wlp2s0 ip=fd0c:d6bd:d6d:c100:66f3:a452:a9c7:8678 bcast= netmask=::::: added interface wlp2s0 ip=192.168.1.6 bcast=192.168.1.255 netmask=255.255.255.0 Connecting to 192.168.1.15 at port 139 Connecting to 192.168.1.15 at port 139 Could not connect to server 192.168.1.15 Connection failed: NT_STATUS_RESOURCE_NAME_NOT_FOUND return code = -1 tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file /var/cache/samba/gencache.tdb: Permission denied tdb(/var/cache/samba/gencache.tdb): tdb_transaction_start: cannot start a transaction on a read-only or internal db" -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 115923] samba client - smb4k crashes
https://bugs.kde.org/show_bug.cgi?id=115923 philip mirabelli <philipwmirabe...@gmail.com> changed: What|Removed |Added CC||philipwmirabe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361125] After upgrade to 5.6, Dropbox system tray icon is gone again
https://bugs.kde.org/show_bug.cgi?id=361125 philip mirabelli <philipwmirabe...@gmail.com> changed: What|Removed |Added CC||philipwmirabe...@gmail.com --- Comment #2 from philip mirabelli <philipwmirabe...@gmail.com> --- Hello, I have just upgraded to Kubuntu 16.04 from 15.04 and it went very well, I am now running plasma version 5.6.90 and initially the dropbox icon was showing ok, then I upgraded some packages including a new set of icons and it disappeared although dropbox is still running in the background, its annoying since I can't even uninstall dropbox from the system as it says it isn't installedhowever I just wanted to know if there was any fix for the dropbox icon missing? thanks -- You are receiving this mail because: You are watching all bug changes.
