Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Package: konsole Version: 4:18.04.0-1 Severity: important Dear Maintainer, I opened the Konsole (KDE) app, next I edited profile settings, next I selected "aspect..." tab, next I clicked on button "Obtain new theme", next a setting panel opened, next I inserted some text to search new theme in panel text box, then the crash happened! I expected that some theme should be available and installable in the konsole setting window. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f818ac7a840 (LWP 13498))] Thread 5 (Thread 0x7f8181623700 (LWP 13507)): #0 0x7f818ee2600c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f8181f5bf3b in ?? () from /usr/lib/x86_64-linux- gnu/dri/swrast_dri.so #2 0x7f8181f5bdb7 in ?? () from /usr/lib/x86_64-linux- gnu/dri/swrast_dri.so #3 0x7f818ee1ffa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #4 0x7f8191aba4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f8181e24700 (LWP 13506)): #0 0x7f818ee2600c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f8181f5bf3b in ?? () from /usr/lib/x86_64-linux- gnu/dri/swrast_dri.so #2 0x7f8181f5bdb7 in ?? () from /usr/lib/x86_64-linux- gnu/dri/swrast_dri.so #3 0x7f818ee1ffa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #4 0x7f8191aba4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f8183fff700 (LWP 13503)): #0 0x7f8191aab494 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f818e43baa0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f818e3f5c0f in g_main_context_check () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #3 0x7f818e3f60e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f818e3f625c in g_main_context_iteration () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #5 0x7f819019387b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f819014127b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f818ff90ec6 in QThread::exec() () from /lib/x86_64-linux- gnu/libQt5Core.so.5 #8 0x7f818f833545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f818ff9aaa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f818ee1ffa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #11 0x7f8191aba4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f8189eb7700 (LWP 13499)): #0 0x7f8191aaf819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f818f048cf7 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f818f04a91a in xcb_wait_for_event () from /lib/x86_64-linux- gnu/libxcb.so.1 #3 0x7f818a82ed79 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f818ff9aaa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f818ee1ffa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #6 0x7f8191aba4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f818ac7a840 (LWP 13498)): [KCrash Handler] #6 0x7f818f7b6c76 in KNSCore::Cache::requestFromCache(KNSCore::Provider::SearchRequest const&) () from /lib/x86_64-linux-gnu/libKF5NewStuffCore.so.5 #7 0x7f818f7c3214 in KNSCore::Engine::setSearchTerm(QString const&) () from /lib/x86_64-linux-gnu/libKF5NewStuffCore.so.5 #8 0x7f818fc3a620 in ?? () from /lib/x86_64-linux-gnu/libKF5NewStuff.so.5 #9 0x7f819016ba43 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f8190c90d52 in QLineEdit::textChanged(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f8190c97609 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f819016b906 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f8190c98165 in QWidgetLineControl::textChanged(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f8190c9b4ce in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f8190c9e77e in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f8190c90eaa in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f81912b3139 in KLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libKF5Completion.so.5 #18 0x7f8190b9bba7 in QWidget::event(QEvent*) () from /lib/x86_64-linux- gnu/libQt5Widgets.so.5 #19 0x7f8190c96eba in QLineEdit::event(QEvent*) () from /lib/x86_64-linux- gnu/libQt5Widgets.so.5 #20 0x7f81912b3ac2 in KLineEdit::event(QEvent*) () from /lib/x86_64-linux- gnu/libKF5Com
Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
control: tags -1 + confirmed Hi Saverio, thank you for your bug report. I confirm I reproduce the bug. This is due to the Konsole package not shipping /etc/xdg/konsole.knsrc which is required for the new stuff functionality to work. @qt-kde team, the patch is a one-liner in konsole.install but I’m not sure it qualifies for an unblock as we’re in deep freeze. Opinions ? Cheers, -- Aurélien
Processed: Re: Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Processing control commands: > tags -1 + confirmed Bug #930316 [konsole] konsole: Segmentation fault arisen when obtining new konsole themes Added tag(s) confirmed. -- 930316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Control: tag -1 important Hi Aurelien and Saverio! El lun., 10 jun. 2019 10:42, Aurélien COUDERC escribió: > control: tags -1 + confirmed > > Hi Saverio, > > thank you for your bug report. > I confirm I reproduce the bug. > > This is due to the Konsole package not shipping /etc/xdg/konsole.knsrc > which is required for the new stuff functionality to work. > > @qt-kde team, the patch is a one-liner in konsole.install but I’m not > sure it qualifies for an unblock as we’re in deep freeze. > Opinions ? > A crash deserves severity important, which might or not deserve an unblock, but will definitely be eligible for a point update. Aurelien: mind creating a merge request? >
Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Actually it would be good to know first why we are not shipping that file. El lun., 10 jun. 2019 10:45, Lisandro Damián Nicanor Pérez Meyer < perezme...@gmail.com> escribió: > Control: tag -1 important > > Hi Aurelien and Saverio! > > > El lun., 10 jun. 2019 10:42, Aurélien COUDERC > escribió: > >> control: tags -1 + confirmed >> >> Hi Saverio, >> >> thank you for your bug report. >> I confirm I reproduce the bug. >> >> This is due to the Konsole package not shipping /etc/xdg/konsole.knsrc >> which is required for the new stuff functionality to work. >> >> @qt-kde team, the patch is a one-liner in konsole.install but I’m not >> sure it qualifies for an unblock as we’re in deep freeze. >> Opinions ? >> > > A crash deserves severity important, which might or not deserve an > unblock, but will definitely be eligible for a point update. > > Aurelien: mind creating a merge request? > >>
Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Hello guys, I tried to create the file /etc/xdg/konsole.knsrc with thi content (taken from upstream): [KNewStuff3] ProvidersUrl=https://download.kde.org/ocs/providers.xml Categories=Konsole Color Schemes TargetDir=konsole AcceptHtmlDownloads=false Uncompress=archive and the bug disappears, konsole settings are able to download and show the konsole themes. No drawback observed at the moment.
Processed: Fixing severity
Processing commands for cont...@bugs.debian.org: > severity 930316 important Bug #930316 [konsole] konsole: Segmentation fault arisen when obtining new konsole themes Ignoring request to change severity of Bug 930316 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 930316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930316: konsole: Segmentation fault arisen when obtining new konsole themes
Le 10/06/2019 à 15:46, Lisandro Damián Nicanor Pérez Meyer a écrit : > Actually it would be good to know first why we are not shipping that file. Simply because it was added by upstream between 17.12.3 and 18.04.0 and the .install file was not updated accordingly. $ tar tvfa konsole_17.12.3.orig.tar.xz | grep knsrc $ tar tvfa konsole_18.04.0.orig.tar.xz | grep knsrc -rw-rw-r-- 0/0 146 2018-04-10 16:05 konsole-18.04.0/data/konsole.knsrc $ Cheers, -- Aurélien
Bug#929882: buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster
Hi khelpcenter maintainers, On Sat, 01 Jun 2019 21:30:41 +0200 pnd23 wrote: > KDE packages install their documentation files in /usr/share/doc/HTML on > buster > (in debian 8 this was: /usr/share/doc/kde/HTML). The "dhelp" package erases > this folder when it rebuilds its index. The KHelpcenter documentation gets > erased this way. This bug got cloned to khelpcenter to make sure that you change your package to conflict with the unfixed version of dhelp, to prevent the above issue from happening. I expect that dhelp may be removed from buster, but if the package isn't removed from the users system, the issue may still occur. Paul signature.asc Description: OpenPGP digital signature
Bug#911844: okular: Prints to the wrong printer
Severity: critical thanks On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote: > Package: okular > Version: 4:17.12.2-2 > Severity: critical > Tags: upstream security > > > > "critical" because a document should always go to where it is sent. > Please reduce the severity if I have overestimated the security > implications. > > The CUPS version being used is 2.2.8-5 and cups-browsed is not running. > The issue was encountered while taking another look at #911702. > > brian@test:~$ lpstat -e > aaa > realq_desktop > test > > aaa and test are local queues set up with > > lpadmin -p -v file:/home/brian/capture -E -m > drv:///sample.drv/generic.ppd > > and realq_desktop is a queue on a remote machine. > > Okular was started from a terminal. Printing to realq_desktop produces an > output of > > request id is aaa-41 (1 file(s)) > > The job is always sent to a local queue when its destination precedes > realq_desktop alphabetically. > > Removing the aaa queue gets > > /usr/bin/lp: No such file of directory (which is #911702) > > I believe printing from LibreOffice to be based on the same principles > as printing from Okular. Printing from that application is not an issue. > qpdfview is another affected application. I have retested this. There is no change on the present unstable. I cannot see why a confidential print job going to a staff printer is anything but a security issue. Maybe this is something that merits the tag of normal but explanations are in short supply. Regards, Brian.
Processed: okular: Prints to the wrong printer
Processing commands for cont...@bugs.debian.org: > severity 911844 critical Bug #911844 [okular] okular: Prints to the wrong printer Severity set to 'critical' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 911844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911844: okular: Prints to the wrong printer
Hi Brian! El lun., 10 jun. 2019 16:54, Brian Potkin escribió: > Severity: critical > thanks > > > > On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote: > > > Package: okular > > Version: 4:17.12.2-2 > > Severity: critical > > Tags: upstream security > > > > > > > > "critical" because a document should always go to where it is sent. > > Please reduce the severity if I have overestimated the security > > implications. Please feel free to prove me wrong. As far as I understand printing sometimes means an unencrypted connection to a printer, which means a man in the middle attack should be easy to achieve. Thus whenever you are printing you should already trust the network and whatever is in it. Exception is probably a printer managed directly by CUPS.
