[konsole] [Bug 366232] New: Konsole sets $LANG to en_US.US-ASCII on startup and tab creation
https://bugs.kde.org/show_bug.cgi?id=366232 Bug ID: 366232 Summary: Konsole sets $LANG to en_US.US-ASCII on startup and tab creation Product: konsole Version: 16.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dsgamec...@gmail.com If Konsole isn't told specifically not to (via the environment variable list in the profile settings area), it sets $LANG to en_US.US-ASCII when launched, overriding the default locale. Reproducible: Always Steps to Reproduce: 1. Edit the current Konsole profile, setting at least one environment variable and not setting $LANG. Apply your changes. 2. Open a new tab 3. Check $LANG Actual Results: $LANG is en_US.US-ASCII Expected Results: $LANG should be en_US.UTF-8, which is the only locale generated on the system and the only one uncommented in /etc/locale.gen and specified in /etc/locale.conf. An incorrect $LANG, especially if that locale doesn't exist on the system, causes problems for mandb, among other things. I first noticed it because mandb errored when installing packages via pacman. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348668] Playback of an animated title clip causes crash
https://bugs.kde.org/show_bug.cgi?id=348668 Wegwerf changed: What|Removed |Added Ever confirmed|0 |1 CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |CONFIRMED --- Comment #4 from Wegwerf --- Gianluca, as there have been fixes to the title producer some time ago, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the big is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top
https://bugs.kde.org/show_bug.cgi?id=364837 --- Comment #8 from Jean-Baptiste Mardelle --- Git commit 98a3d5800d787414e44fc53ff3a39e78655fc7e4 by Jean-Baptiste Mardelle. Committed on 29/07/2016 at 07:03. Pushed by mardelle into branch 'Applications/16.08'. Workaround Qt bug 54676 causing high CPU usage M +28 -13 src/bin/bin.cpp M +6-0src/bin/bin.h http://commits.kde.org/kdenlive/98a3d5800d787414e44fc53ff3a39e78655fc7e4 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350556] 15.08 - Segfault when editing large project with many "Speed" effects
https://bugs.kde.org/show_bug.cgi?id=350556 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Paul, as there have been fixes and chances to the speed effect some time ago, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? Please make sure that you upgrade MLT to at least 6.2.0 too. If the big is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349544] First start setup dialog is not vertically resizable
https://bugs.kde.org/show_bug.cgi?id=349544 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Kai, is this bug still present in recent stable version 16.04.2? If not, can you please be so kind as to close this report? Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349323] Crash when add directory with several FLAC files to prtoject
https://bugs.kde.org/show_bug.cgi?id=349323 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Egor, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349660] Ripple delete doesn't work on last frame of a project
https://bugs.kde.org/show_bug.cgi?id=349660 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Sam, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350558] 15.08 - Segfault when trying to add title clip
https://bugs.kde.org/show_bug.cgi?id=350558 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #4 from Wegwerf --- Paul, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? Please make sure to upgrade MLT to at least 6.2.0 too. If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349544] First start setup dialog is not vertically resizable
https://bugs.kde.org/show_bug.cgi?id=349544 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jean-Baptiste Mardelle --- The first start dialog has been rewritten for Kdenlive 16.08 and does not have this problem, closing the bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350587] Crashing every 5-10 minutes during normal playback
https://bugs.kde.org/show_bug.cgi?id=350587 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #5 from Wegwerf --- Sam, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351407] KDE/kactivitymanagerd crashes when moving playhead with mouse
https://bugs.kde.org/show_bug.cgi?id=351407 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Egor, can you please try with a recent Archlinux and stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. To me your report points towards an upstream Archlinux issue because in any case neither KF5 sessions nor your X11 server should restart. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348856] Crop start reset to 0 when using proxy clips
https://bugs.kde.org/show_bug.cgi?id=348856 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #6 from Wegwerf --- Hugh, Bjorn, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350739] Cannot create directory /home/user/kdenlive
https://bugs.kde.org/show_bug.cgi?id=350739 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Jem, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349725] clip get corrupted and wont move
https://bugs.kde.org/show_bug.cgi?id=349725 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349688] Impossibly slow seeking and response times
https://bugs.kde.org/show_bug.cgi?id=349688 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- Sam, can you please try with a stable Kdenlive 16.04.2 and MLT 6.2.0 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366183] brush doesn't work after a while working
https://bugs.kde.org/show_bug.cgi?id=366183 --- Comment #2 from raquelan...@gmail.com --- Hi, thanks for your answer! When it happened to me the first time I was just simply dranwing and I added a new layer with the icon provided in the menu, I did not change any the settings of the layer. To color the image I'm following a tutorial of how to use G'Mic, so after using the function "split layer" I cannot use the brush over the layers, any stroke/eraser is working over the layers. All layers are visisble and non locked, any selection apply :( . 2016-07-27 22:34 GMT+02:00 Sven Langkamp via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=366183 > > Sven Langkamp changed: > >What|Removed |Added > > > CC||sven.langk...@gmail.com > > --- Comment #1 from Sven Langkamp --- > Check if you changed anything in the layer settings. Is the layer a paint > layer, is it visible and not locked. Is there a selection. > > If it's limited to one file only then we might need the file. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 365604] AutoCatalog of disks
https://bugs.kde.org/show_bug.cgi?id=365604 --- Comment #2 from Alexander --- All more just. Without GUI, but in future may be maked and GUI frontend. After every success burn of CD in user directory K3B put (for example) new utf8 text file with list of K3B project. ~/CatalogCD --- 20160729:NameOfProject1.txt --- 20160729:NameOfProject2.txt --- ... Or in other just, comfortable for programmers, users, in traditional for *nix form. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 365604] AutoCatalog of disks
https://bugs.kde.org/show_bug.cgi?id=365604 --- Comment #3 from Alexander --- More precise: ~/CatalogCD --- 20160729-11:02:45_NameOfProject1.txt --- 20160729-11:40:22_NameOfProject2.txt --- ... If make GUI (or pair backend/GUI): it may be extended to add by it already existing disks by scanning it content. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366233] New: Brush tool no longer draws but cursor is still visible and moving
https://bugs.kde.org/show_bug.cgi?id=366233 Bug ID: 366233 Summary: Brush tool no longer draws but cursor is still visible and moving Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPU Canvas Assignee: krita-bugs-n...@kde.org Reporter: contramuf...@gmail.com In the middle of my drawing, I am no longer able to draw. The brush moves along with the cursor - everything works as intended - but I simply cannot put color onto the canvas. I have tried to close the program and reopen the file, but the brush again does not register the stroke. The problem appears to fix itself when I create a new project. When I switch tabs back to my original project it appears that the canvas was actually scrolled all the way to the right, which may explain why none of the strokes were drawn on the canvas. This appears to be a canvas rendering problem in which the position of the canvas is not where it is shown. Reproducible: Couldn't Reproduce I have OpenGL disabled. After I managed to "fix" the bug, Krita no longer differentiates between the nib of my tablet pen and the eraser of the pen. Interestingly, the first brush I tried to use when I found out I could no longer draw on the canvas was the eraser by using the back end of the tablet pen. I also remember some lag and similar effects in the canvas when I was zooming in and out with the tablet, so it may be an issue with receiving input from a tablet. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 365604] AutoCatalog of disks
https://bugs.kde.org/show_bug.cgi?id=365604 Leslie Zhai changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Leslie Zhai --- K3b rip CD has a debugging output shown as https://pbs.twimg.com/media/CogtrCUUkAAlGXs.jpg you mean like this? and save the log to ~/CatalogCD? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] New: Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234
Bug ID: 366234
Summary: Import from card readers starts automatically when
digikam is started
Product: digikam
Version: 5.0.0
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Import-Config
Assignee: digikam-de...@kde.org
Reporter: wolfram.kro...@gmail.com
When starting the digikam application attempts to import from my card readers
several times. Since I usually don't have cards inserted in all four slots (in
fact I hardly have any card inserted) digikam presents me error popups ("please
insert media in drive x"). That's two popups per drive before the splash screen
is shown and another one per drive after.
In total I have to click away 12 popups. The behaviour is the same whatever
option I select (Cancel, Retry, Continue). This is really annoying.
Reproducible: Always
Steps to Reproduce:
1. start digikam
2.
3.
Expected Results:
digikam is supposed to search for new items in the collections that I have set
up. That works fine. But I don't expect digikam to consider in any other
location without being explicitly told to.
It wasn't like that during the first days after installation, it appeared only
yesterday, although I didn't change the installation. Therefore I suspect a
settings problem. But I didn't change any settings recently and I didn't find
any setting that controls the startup behaviour.
But I used the Batch Queue Manager yesterday for the first time. Maybe this
triggered the problems.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- There is no relation between BQM and Import tool. The problem is not reproducible here with Windows 7 32 or 64 bits. Installation is in place since few weeks and is used to test the application. What do you see in DebugView when digiKam is started ? https://technet.microsoft.com/en-us/sysinternals/debugview.aspx -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #167 from Simone Gaiarin --- To start fresh I've also removed all the files in ./.local/share/kscreen/. In my case some of them were read only (I've set them so time ago) and caused problems. As I said everything works better now, but to reach a good result I need to perform the steps in a very specific order or I can still end up in bad configurations. As an example Working process: 1. Laptop only (so primary) - Place a panel 2. Attach external monitor - Set external monitor as primary (panel is not moved from laptop to external) - Move the panel manually to the external screen 3. Detach external monitor - Panel moves to laptop correctly Non working process: 1. Laptop only (so primary) - Place a panel 2. Attach external monitor - Set external monitor as primary (panel is not moved from laptop to external) 3. Detach external monitor - Panel disappears 4. Reattach external monitor - No more panels (invisible panel) What seems to be partially broken is that sometimes, switching the primary output won't move the panel right away, and the operation needs to be done manually. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366180] Environment variable XDG_DATA_DIRS may be incorrect?
https://bugs.kde.org/show_bug.cgi?id=366180 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Harald Sitter --- > DESKTOP_SESSION=/usr/share/xsessions/plasma which will be prepended to the variable by a core x11 setup script > $ grep -r SESSION\": /etc/X11/Xsession.d/60x11-common_xdg_path > > XDG_CONFIG_DIRS="$DEFAULT_XDG_CONFIG_DIRS"/xdg-"$DESKTOP_SESSION":"$XDG_CONFIG_DIRS" > XDG_DATA_DIRS=/usr/share/"$DESKTOP_SESSION":"$XDG_DATA_DIRS" So I am guessing that every DM other than SDDM actually treats DESKTOP_SESSION as the basename (excluding suffix) of the xsession file name. Please forward this bug to SDDM on github. As for your actual problem of icons not working. This probably has nothing to do with it since /usr/share//usr/share/xsessions/plasma == /usr/share/usr/share/xsessions/plasma which is a valid path, and the XDG spec doesn't mandate that the paths in the variable exist at all, so even though it is malformed it shouldn't matter. That said, depending on how Nylas renders the systray icons and whether it has own icon lookup code involved it is entirely possible that the lookup code is incorrect and breaks on non-existant paths in XDG_DATA_DIRS. I suggest you file a bug report with the Nylas authors as they are probably in a better position to guess where the problem might be. -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 366000] No tiles showing, and the app closes when I click anywhere in playing area.
https://bugs.kde.org/show_bug.cgi?id=366000 --- Comment #1 from Frederik Schwarzer --- Hi Michael, can you please post the [Game] and [General] sections of your kshisenrc file from the ~/.config folder? Regards, Frederik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #2 from Wolfram Kroiss --- Created attachment 100370 --> https://bugs.kde.org/attachment.cgi?id=100370&action=edit complete log until album view is visible -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #3 from Wolfram Kroiss --- Created attachment 100371 --> https://bugs.kde.org/attachment.cgi?id=100371&action=edit log from start until the first popup is shown -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #4 from Wolfram Kroiss --- Created attachment 100372 --> https://bugs.kde.org/attachment.cgi?id=100372&action=edit log from start until the last series of popups is shown (after splash screen) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364061] plasmashell using 100% CPU time
https://bugs.kde.org/show_bug.cgi?id=364061 --- Comment #4 from DimanNe --- I have recently encountered this problem again at my notebook. System info: plasmashell 5.5.5 OS: Kubuntu 16.04 Also, I have two (physical) monitors, and I noticed this problem began to arise after I detached/attached notebook from dock station or after hibernation Backtraces, perf top: I ran "top -H" and it said there are two threads on my system, which are eating CPU - plasmashell and Xorg, so here is "hottest" backtraces of these threads collected with perf top -t 3136 -d 5 --call-graph dwarf (where 3136 is thread Id from top output) Thread of plasmashell - http://pastebin.com/GPMkrWz8 (see text after RAW Paste Data) Thread of Xorg - http://pastebin.com/ZH0x7F7i (see text after RAW Paste Data) -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 366000] No tiles showing, and the app closes when I click anywhere in playing area.
https://bugs.kde.org/show_bug.cgi?id=366000 Frederik Schwarzer changed: What|Removed |Added Version|unspecified |1.10.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #5 from Wolfram Kroiss --- attached a few log files. BTW: My PC runs on Windows 10 64-bit. Digikam 5.0.0 was installed on 20/07/2016 (5.0.0-2) via http://download.kde.org/stable/digikam/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366235] New: Crashed on usb-hdd failure.
https://bugs.kde.org/show_bug.cgi?id=366235 Bug ID: 366235 Summary: Crashed on usb-hdd failure. Product: dolphin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jodr...@live.com Application: dolphin (16.04.3) Qt Version: 5.7.0 Frameworks Version: 5.24.0 Operating System: Linux 4.4.0-31-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: I was opening a pretty big compress file (Bz2) ~1.5 GiB, and got and error stating the reading of the file did not reach the end of it. I noticed the other files on the same directory where missing as well as the disk on the devices list. Checked the power to the hdd and it was cut due to a loose connector, while fastenig it i got the crashed. - Unusual behavior I noticed: First a hang, then kwin sort of crashed as well, since the close/minimize buttons disappeared then the whole desktop crashed as well and restarted a moment later with the crash reporting assitant on the panel. This may related to bug 362841 -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b6a10e8c0 (LWP 5539))] Thread 4 (Thread 0x7f7b44d32700 (LWP 5542)): #0 0x7f7b5ebc9ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7b5eb84939 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b5eb852cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b5eb854ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7b6482d30b in QEventDispatcherGlib::processEvents (this=0x7f7b48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7b647d7d9a in QEventLoop::exec (this=this@entry=0x7f7b44d31d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f7b645fd044 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f7b64601c28 in QThreadPrivate::start (arg=0xd2eae0) at thread/qthread_unix.cpp:344 #8 0x7f7b60cc26fa in start_thread (arg=0x7f7b44d32700) at pthread_create.c:333 #9 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f7b4f4c2700 (LWP 5541)): #0 0x7f7b69b099cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b5ebc8740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b5eb84e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b5eb85340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7b5eb854ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7b6482d30b in QEventDispatcherGlib::processEvents (this=0x7f7b480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7b647d7d9a in QEventLoop::exec (this=this@entry=0x7f7b4f4c1cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f7b645fd044 in QThread::exec (this=this@entry=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #8 0x7f7b6a1f07a5 in QDBusConnectionManager::run (this=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #9 0x7f7b64601c28 in QThreadPrivate::start (arg=0x7f7b6a264d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #10 0x7f7b60cc26fa in start_thread (arg=0x7f7b4f4c2700) at pthread_create.c:333 #11 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f7b55692700 (LWP 5540)): #0 0x7f7b69b0de8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b5e2b4c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f7b5e2b68d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7b5825ea39 in QXcbEventReader::run (this=0xa49370) at qxcbconnection.cpp:1337 #4 0x7f7b64601c28 in QThreadPrivate::start (arg=0xa49370) at thread/qthread_unix.cpp:344 #5 0x7f7b60cc26fa in start_thread (arg=0x7f7b55692700) at pthread_create.c:333 #6 0x7f7b69b19b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7b6a10e8c0 (LWP 5539)): [KCrash Handler] #6 0x7f7b69a48418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f7b69a4a01a in __GI_abort () at abort.c:89 #8 0x7f7b645e8811 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1680 #9 QMessageLogger::fatal (this=this@entry=0x7ffc3c07f7e0, msg=msg@entry=0x7f7b6a24df80 "Cannot construct placeholder
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #6 from caulier.gil...@gmail.com --- "D:/Eigene Dateien/Eigene Bilder/fotos" where you store database files and collection of photo is a removable media ? Do you have any Antivirus software working in background around D: ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366236] New: Main menu toolbar is doubled on Ubuntu
https://bugs.kde.org/show_bug.cgi?id=366236 Bug ID: 366236 Summary: Main menu toolbar is doubled on Ubuntu Product: kdenlive Version: 16.04.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: asla...@vsechno-atd.cz The main toolbar with options File, Edit, Project, etc, is doubled – one in the Ubuntu upper bar and one just under it. Correctly, only the OS one (upper one) should be displayed. It's not a big problem, but it takes space and looks strange. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #7 from Wolfram Kroiss --- Yes. There is antivirus and also a backup job runs in the background. Probably you need to remove their debug messages. The complete log was made first. Then I closed digikam and restarted, creating the two other log files. So I guess you can safely assume that only those events that appear in all logs are relevant. BTW: I tried with one card inserted. The behaviour is similar except that I don't get the popup for the drive holding the card. BTW2: Whenever I push the Import button in digikam (or I select any specific card reader in Menu-->Import-->Card Reader, even if I select the inserted card) digikam would present me the same series of popups. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366210] Source Compiling stops with error
https://bugs.kde.org/show_bug.cgi?id=366210 --- Comment #1 from Albert Vaca --- There is no error message shown in the output you pasted. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 366237] pextrw - Unrecoginzed instruction
https://bugs.kde.org/show_bug.cgi?id=366237 Vasiliy Olekhov changed: What|Removed |Added CC||olek...@gmail.com --- Comment #1 from Vasiliy Olekhov --- It seems that nasm generates SSE4_1 version, which is not supported on Celeron E3400 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366210] Source Compiling stops with error
https://bugs.kde.org/show_bug.cgi?id=366210
--- Comment #2 from Harald Schugt ---
This is the complete output:
schugt@linux-c0qp:~/tmp/kdeconnect-kde-master> make
[ 0%] Automatic moc for target kdeconnectcore
[ 0%] Built target kdeconnectcore_automoc
[ 0%] Building CXX object
core/CMakeFiles/kdeconnectcore.dir/backends/lan/landevicelink.cpp.o
In file included from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/devicelink.h:27:0,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:30,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.cpp:23:
/home/schugt/tmp/kdeconnect-kde-master/core/networkpackage.h:52:77: warning:
extended initializer lists only available with -std=c++11 or -std=gnu++11
[enabled by default]
explicit NetworkPackage(const QString& type, const QVariantMap &body =
{});
^
/home/schugt/tmp/kdeconnect-kde-master/core/networkpackage.h:52:77: warning:
extended initializer lists only available with -std=c++11 or -std=gnu++11
[enabled by default]
/home/schugt/tmp/kdeconnect-kde-master/core/networkpackage.h:65:77: warning:
extended initializer lists only available with -std=c++11 or -std=gnu++11
[enabled by default]
template T get(const QString& key, const T& defaultValue = {})
const {
^
In file included from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:30:0,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.cpp:23:
/home/schugt/tmp/kdeconnect-kde-master/core/backends/devicelink.h:43:29:
warning: defaulted and deleted functions only available with -std=c++11 or
-std=gnu++11 [enabled by default]
virtual ~DeviceLink() = default;
^
In file included from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/uploadjob.h:30:0,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:31,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.cpp:23:
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/server.h:40:13:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
~Server() override = default;
^
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/server.h:40:26:
warning: defaulted and deleted functions only available with -std=c++11 or
-std=gnu++11 [enabled by default]
~Server() override = default;
^
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/server.h:42:39:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
QSslSocket* nextPendingConnection() override;
^
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/server.h:43:34:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
bool hasPendingConnections() const override;
^
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/server.h:46:53:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
void incomingConnection(qintptr socketDescriptor) override;
^
In file included from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:31:0,
from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.cpp:23:
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/uploadjob.h:39:16:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
void start() override;
^
In file included from
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.cpp:23:0:
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:41:30:
warning: scoped enums only available with -std=c++11 or -std=gnu++11 [enabled
by default]
enum ConnectionStarted : bool { Locally, Remotely };
^
/home/schugt/tmp/kdeconnect-kde-master/core/backends/lan/landevicelink.h:46:18:
warning: override controls (override/final) only available with -std=c++11 or
-std=gnu++11 [enabled by default]
QString name() override;
[Akonadi] [Bug 366238] New: KMail does not fetch mails from imap.kabelmail.de
https://bugs.kde.org/show_bug.cgi?id=366238 Bug ID: 366238 Summary: KMail does not fetch mails from imap.kabelmail.de Product: Akonadi Version: 16.04 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: franz-joseph.barth...@kabelmail.de CC: kdepim-b...@kde.org, vkra...@kde.org Initially, https://bugs.kde.org/show_bug.cgi?id=364045 has been resolved. Thank you for your effort in fixing this bug. Now, on openSUSE Tumbleweed using KDEPIM 16.04.3, the imap resource does not fetch mails. I am using a fresh user and a fresh akonadi with only one imap inbox. Furthermore, using 'akonadiconsole' and deleting the corresponding cash 'Clear Akonadi Cash' does not solve the problem. 'akonadictl restart' shows some information like: log_imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 223 Local: 0 Reproducible: Always Steps to Reproduce: 1. create some mail account on imap.kabelmail.de 2. try to fetch mails 3. observe that all mails are missing Actual Results: The protocol issued by 'akonadictl restart' shows lines such as: log_imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 223 Local: 0 Expected Results: All mails should be fetched from server. I repeated the configuration several times on openSUSE Leap 42.1 and openSUSE Tumbleweed with both KDEPIM 16.04.3 using old and new (fresh) users. I like to exclude any local misconfiguration. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366210] Source Compiling stops with error
https://bugs.kde.org/show_bug.cgi?id=366210 --- Comment #3 from Albert Vaca --- It looks like you are using an (old?) compiler that doesn't support c++11 by default. You will need to add "-std=c++11 " in the CXXFLAGS parameter in Cmake to enable it. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 366239] New: Feature Request: Missing features found in KSnapshot
https://bugs.kde.org/show_bug.cgi?id=366239 Bug ID: 366239 Summary: Feature Request: Missing features found in KSnapshot Product: Spectacle Version: unspecified Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: chrisret...@gmx.com Spectacle Version 16.04.3 using KDE 5_16.07 for Slackware, consisting of the KDE Frameworks 5.24.0, Plasma 5.7.2 and Applications 16.04.3 on top of Qt 5.6.1. Spectacle looks to be a good replacement for KSnapshot. One of the things KSnapshot had that Spectacle does not is the Section of Windows and Freehand Region mode of taking a screenshot. Section of Windows is really handy for capturing sections of windows such an the section inside the window. It would be awesome if these two mode with added to Spectacle. Reproducible: Always Steps to Reproduce: NA: Feature Request Actual Results: NA: Feature Request Expected Results: NA: Feature Request NA: Feature Request -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 366237] New: pextrw - Unrecoginzed instruction
https://bugs.kde.org/show_bug.cgi?id=366237 Bug ID: 366237 Summary: pextrw - Unrecoginzed instruction Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: olek...@gmail.com Created attachment 100373 --> https://bugs.kde.org/attachment.cgi?id=100373&action=edit sample project valgrind complains about unrecognized instruction, generated by NASM assembler. A sample project is attached. YASM and NASM generate different instructions: Yasm listing: 1 %line 1+1 test_pextrw.nas 2 [bits 64] 3 [default rel] 4 5 [section .text align=16] 6 7 [global test_pextrw] 8 test_pextrw: 9 0F1007 movups xmm0, [rdi] 10 0003 66480FC5C000pextrw rax, xmm0, 0 11 0009 C3 ret 12 nasm listing: 1 [bits 64] 2 [default rel] 3 4 [section .text align=16] 5 6 [global test_pextrw] 7 test_pextrw: 8 0F1007movups xmm0, [rdi] 9 0003 66480F3A15C000pextrw rax, xmm0, 0 10 000A C3ret 11 NASM 2.12.02rc7 (latest rc) yasm 1.3.0.28.g51af (current git) valgrind-3.12.0.SVN (current svn) yasm generates instruction that executes on Intel Celeron E3400 nasm's instruction causes "illegal hardware instruction" exception on Celeron E3400 both versions work on Core i7-4770S This might be a bug in nasm. I'll report to the nasm team too. valgrind error messages on nasm version: vex amd64->IR: unhandled instruction bytes: 0x66 0x48 0xF 0x3A 0x15 0xC0 0x0 0xC3 0x90 0x90 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F3A vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==6168== valgrind: Unrecognised instruction at address 0x400583. ==6168==at 0x400583: ??? (test_pextrw.nas:9) ==6168==by 0x4E4FCDC: (below main) (in /lib64/libc-2.12.so) ==6168== 1. Your program has a bug and erroneously jumped to a non-code ==6168==location. If you are running Memcheck and you just saw a ==6168==warning about a bad jump, it's probably your program's fault. ==6168== 2. The instruction is legitimate but Valgrind doesn't handle it, ==6168==i.e. it's Valgrind's fault. If you think this is the case or ==6168==you are not sure, please let us know and we'll try to fix it. ==6168== Either way, Valgrind will now raise a SIGILL signal which will ==6168== probably kill your program. ==6168== ==6168== Process terminating with default action of signal 4 (SIGILL) ==6168== Illegal opcode at address 0x400583 ==6168==at 0x400583: ??? (test_pextrw.nas:9) ==6168==by 0x4E4FCDC: (below main) (in /lib64/libc-2.12.so) code produced by yasm works under valgrind without errors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365898] Clicking with left button on the desktop (sometimes) hides all windows
https://bugs.kde.org/show_bug.cgi?id=365898 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 365014 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365014] All windows hide on repeating desktop click
https://bugs.kde.org/show_bug.cgi?id=365014 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #21 from Christoph Feck --- *** Bug 365898 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #8 from caulier.gil...@gmail.com --- I suspect that the removable media D:/ is the problem here. I suspect that KDE Solid framework do not work under Windows. Removable media UUID is provided by Solid and is registered in database Can you try 2 workaround in a new account : 1/ store database files somewhere in C:/ and use removable media to store collections. 2/ store all somewhere in C:/ (databases and collections). For both, look if the problem is reproducible. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #3 from Dominik George --- (In reply to Laurent Montel from comment #2) > Please provide a mail (as mbox) which has this bug please. > Thanks Sorry, that request does not make any sense to me. Please read the bug report again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #9 from Wolfram Kroiss --- What do you mean with "removable media D:\". This is the second partition of my hdd. I can't move data to C: because the first partition is just large enough to hold the OS and the applications. I have >200GB of images which I'm not going to move anywhere else. I'll wait until the backup is done (probably not before tomorrow afternoon/evening). Then I will reboot the machine, deactivate anti-virus, and start digikam before any other application was started. Let's see if the problem still appears then. If yes, we would at least have a clean debug log. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366183] brush doesn't work after a while working
https://bugs.kde.org/show_bug.cgi?id=366183 --- Comment #3 from Sven Langkamp --- Check the alpha lock state of the layer after the split. Also make sure that you don't have the group layer selected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366233] Brush tool no longer draws but cursor is still visible and moving
https://bugs.kde.org/show_bug.cgi?id=366233 Sven Langkamp changed: What|Removed |Added CC||sven.langk...@gmail.com --- Comment #1 from Sven Langkamp --- You could check if Instant preview is on and if so turn that off and see if that makes a difference. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 365598] Version kf5 frameworks. Failure to update share prices
https://bugs.kde.org/show_bug.cgi?id=365598 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #2 from Robby Engelmann --- *** Bug 366229 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 366229] Online Update Quotes does not work since last Kmymoney git snapshot
https://bugs.kde.org/show_bug.cgi?id=366229 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Robby Engelmann --- *** This bug has been marked as a duplicate of bug 365598 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366240] New: KWin crashed when opening Plasma digital clock settings
https://bugs.kde.org/show_bug.cgi?id=366240 Bug ID: 366240 Summary: KWin crashed when opening Plasma digital clock settings Product: kwin Version: 5.7.0 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dennis.schri...@uni-heidelberg.de Application: kwin_x11 (5.7.0) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: I right clicked the Plasma digital clock and selected "Digital Clock Settings". The settings window opened and KWin crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3029793940 (LWP 3598))] Thread 5 (Thread 0x7f3019eaa700 (LWP 4433)): #0 0x7f3040df5f73 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f303ec8ca1f in qt_safe_select (nfds=12, fdread=fdread@entry=0x7f300c000a58, fdwrite=fdwrite@entry=0x7f300c000ce8, fdexcept=fdexcept@entry=0x7f300c000f78, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f303ec8e45e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f300c000f78, writefds=0x7f300c000ce8, readfds=0x7f300c000a58, nfds=, this=0x7f300c0923d0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f300c0008c0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f303ec8e972 in QEventDispatcherUNIX::processEvents (this=0x7f300c0923d0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f303ec39e4a in QEventLoop::exec (this=this@entry=0x7f3019ea9c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f303ea629e4 in QThread::exec (this=this@entry=0x2c35490) at thread/qthread.cpp:500 #7 0x7f3039510405 in QQmlThreadPrivate::run (this=0x2c35490) at qml/ftw/qqmlthread.cpp:141 #8 0x7f303ea67808 in QThreadPrivate::start (arg=0x2c35490) at thread/qthread_unix.cpp:341 #9 0x7f303a3ac464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f3040dfd30d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f300a33c700 (LWP 3639)): #0 0x7f303a3b209f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f303de02574 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f303dee9f00 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f303de025b9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f303a3ac464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f3040dfd30d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f30192e7700 (LWP 3626)): #0 0x7f3040df5f73 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f303ec8ca1f in qt_safe_select (nfds=13, fdread=fdread@entry=0x7f301a78, fdwrite=fdwrite@entry=0x7f301d08, fdexcept=fdexcept@entry=0x7f301f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f303ec8e45e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f301f98, writefds=0x7f301d08, readfds=0x7f301a78, nfds=, this=0x7f3018c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f3018e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f303ec8e972 in QEventDispatcherUNIX::processEvents (this=0x7f3018c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f303ec39e4a in QEventLoop::exec (this=this@entry=0x7f30192e6c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f303ea629e4 in QThread::exec (this=this@entry=0x20604e0) at thread/qthread.cpp:500 #7 0x7f3039510405 in QQmlThreadPrivate::run (this=0x20604e0) at qml/ftw/qqmlthread.cpp:141 #8 0x7f303ea67808 in QThreadPrivate::start (arg=0x20604e0) at thread/qthread_unix.cpp:341 #9 0x7f303a3ac464 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f3040dfd30d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f301bb17700 (LWP 3615)): #0 QEventDispatcherUNIXPrivate::initThreadWakeUp (this=this@entry=0x7f30140008e0) at kernel/qeventdispatcher_unix.cpp:268 #1 0x7f303ec8e426 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f30140008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:189 #2 0x7f303ec8e972 in QEventDispatche
[krita] [Bug 366241] New: Brush Settings' Test Area locks up if you press weird combinations of buttons. Only restarting Kitra fixes it.
https://bugs.kde.org/show_bug.cgi?id=366241 Bug ID: 366241 Summary: Brush Settings' Test Area locks up if you press weird combinations of buttons. Only restarting Kitra fixes it. Product: krita Version: 3.0.1 Alpha Platform: unspecified OS: All Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: phi...@gmail.com Sometimes the Test area gets confused when you press multiple mouse (or tablet) buttons at once and stops drawing anything until your restart kitra. Reproducible: Always Steps to Reproduce: Reproduction with a mouse: 1. Create new document, Open Brush settings. 2. Start Drawing into the test area with left click 3. While still holding left click, press the right mouse button. Actual Results: Notice that you can't draw in the test area any more. Nothing short of restarting Krita will fix it. Expected Results: Not having to restart Krita every time I hit the wrong button on my stylus. I've managed to reproduce this on both Windows 10 and Linux on both Krita 3.0 and 3.0.1 alpha with some mixed results, like either middle clicking and right clicking while holding left mouse will lock it on Linux. But on windows only right click triggers it when using the mouse and only middle click triggers it when using a drawing tablet (I have a Wacom PTZ-630) I'm pretty sure that the same bug (or a closely related one) exists in the main canvas too, but I haven't managed to reliably reproduce it: only sporadically on windows and only with a tablet (and it fixes itself when you switch brushes). -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore
https://bugs.kde.org/show_bug.cgi?id=354130 Vadim Dyadkin changed: What|Removed |Added CC||dyad...@lns.pnpi.spb.ru --- Comment #19 from Vadim Dyadkin --- I have the same problem in Gentoo. Ktp works with jabberd2 but not with ejabberd. Psi works with both. Patch from comment 13 solves the problem with ejabberd. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 365825] Show desktop applet shortcut broken
https://bugs.kde.org/show_bug.cgi?id=365825 Syam changed: What|Removed |Added CC||get.so...@gmail.com --- Comment #1 from Syam --- I can confirm this bug with Plasma 5.7.1 on Fedora 24. Setting a keyboard shortcut for "Show Desktop" widget on the panel has no effect. However, if I go to System Settings > Shortcuts > Global Keyboard Shortcuts > KWin and assign the shortcut to "Show Desktop" item, it works. PS: I think it might be wrong to assign the bug against "kdeplasma-addons". Somebody please change to the right product. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #5 from Michael --- Also a usable workaround for me on Neon: export QT_SCREEN_SCALE_FACTORS= && dolphin %u -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366242] New: mxf files are randomly incorrectly seeking
https://bugs.kde.org/show_bug.cgi?id=366242 Bug ID: 366242 Summary: mxf files are randomly incorrectly seeking Product: kdenlive Version: 16.04.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: asla...@vsechno-atd.cz In Kdenlive 16.07.80, when imported an .MXF clip and played, it randomly seeks. I can jump to any time of the clip, and another part is playing. Audio and video is desynchronized and when playing from the beginning, video is often freezed. It happens both when playing from project bin and from timeline. Using MLT 6.3.0. In old Kdenlive 0.9, this didn't happen. When I convert the clip to another format, everything is ok. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #168 from achat1...@free.fr --- Hello, ok so in light of the noticed improvement I explained, I have tried something different to see the extent of the improvement. Where I normally want all my panels and widget on my primary screen, I decide to also create a panel on my secondary screen (bottom edge of the screen). When I do so, the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc gets amended with the following section being added: [Containments][256] activityId= formfactor=2 immutability=1 lastScreen=1 location=4 plugin=org.kde.panel wallpaperplugin=org.kde.image Where indeed the panel I create is attached to my secondary screen, Screen 1. Now if I play with Kscreen while my desktop is as I want, all changes done through the GUI work like a charm, it's very reactive, I can change which monitor is the primary screen back and forth and it all works very well with everything int he right place. Now when I unplug my external monitor, I get a messed up desktop (as I explained in my previous post) but interestingly I can see that the section in ~/.config/plasma-org.kde.plasma.desktop-appletsrc shown above gets modified. LastScreen=1 becomes LastScreen=0. Hence when I restart plasma, all panels, including the one that was supposed to secondary screen end up on primary screen. The other sections in the file don't get affected by plugging and unplugging but elements of all other sections are already on LastScreen=0 to start with! And this was the improvement I noticed and describe in my last post, the position of all my panels and widgets was remembered correctly - all on primary screen - but was just not applied when plugging and unplugging - I had to restart plasma to get the right desktop. This improvement unfortunately turns out not to be true for elements that we want on secondary screen. So what is the conclusion of all this: -Plugging and unplugging modifies the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc. To my understanding only user actions like creating/modify panels and widgets should affect this file since (i think) it is there to record the desktop config created by the user. I don't see why hardware/device actions should affect it. -That file is not being read properly anyway (whether or not it contains the right or wrong config) when plugging and unplugging. I should say that I am just an enthusiastic user and unfortunately don't have the back-end knowledge of how it really all works but anyway hope my observations may be useful to actual developers :) On this topic, is there a good space to send positive message to plasma devs? I must say that, despite talking about bugs on here a lot, I am truly impressed by their work, especially plasma 5.7 which I think is very very slick, so would love to write on some wall a big WELL DONE to the team!! -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 353124] Juk ignores folder removal
https://bugs.kde.org/show_bug.cgi?id=353124 --- Comment #1 from Francois Gouget --- This bug was also present in Debian's 4:15.08.3-1 JuK package, and I just verified that it is still present in 4:16.04.2-1. Note that I could not update this bug's Version field since it tops out at 3.11. Is that when JuK stopped being maintained? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #10 from caulier.gil...@gmail.com --- Ah so D:/ is not a removable disk as i suspected Ok. How D:/ is formatted ? NTFS ? FAT ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #11 from Wolfram Kroiss --- NTFS. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 365604] AutoCatalog of disks
https://bugs.kde.org/show_bug.cgi?id=365604 Alexander changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Alexander --- Not-not. On proprietary side for example (and more-more other) http://www.wincatalog.com/dvd-catalogue.html , but very more just at first time: LIST of files and directories in every burned project. Not LOG. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 365604] AutoCatalog of disks
https://bugs.kde.org/show_bug.cgi?id=365604 Alexander changed: What|Removed |Added Resolution|FIXED |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365146] Panel disappears on primary laptop screen after closing and reopening lid
https://bugs.kde.org/show_bug.cgi?id=365146 Sebastian Kügler changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |NEEDSINFO --- Comment #4 from Sebastian Kügler --- Needs retesting with master / 5.8, this bug is most likely fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360219] Right Click opens files
https://bugs.kde.org/show_bug.cgi?id=360219 --- Comment #25 from Eike Hein --- This is actually caused by a Qt bug; my fix for it is stuck since a while ago - https://codereview.qt-project.org/#/c/146786/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351217] top panel auto-hide issue: hidden panel still occupies desktop space for some widget functions
https://bugs.kde.org/show_bug.cgi?id=351217 --- Comment #6 from achat1...@free.fr --- Since someelse, experienced, I have just tried again, now on manjaro with plasma 5.7.2 Qt 5.7 and Framework 5.24 and indeed still same problem of widgets being swallowed by (auto)hidden top panel when you move them in the zone of panel would be if visible. However opening panel settings on top panel doesn't seem to mess up widgets layout anymore on my system... -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 270245] After an incorrect password is changing the size of the input window (regression)
https://bugs.kde.org/show_bug.cgi?id=270245 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #12 from Christoph Feck --- The size increasing when additional messages need to be displayed is intended. The wrong initial minimum size should be fixed in kde-cli-extras master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366243] New: Something's really wrong with the update sceduler/kisstroke/etc.
https://bugs.kde.org/show_bug.cgi?id=366243 Bug ID: 366243 Summary: Something's really wrong with the update sceduler/kisstroke/etc. Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com I am getting a similar situation all the time where suddenly Krita freezes, and when I close it down I get a crash, and the backtrace is unique every time. Sometimes it has to do with multiple windows, sometimes with layers changing, sometimes it's signalled by a full freeze, sometimes by the layers not updating when painting on them, othertimes it's signalled by Krita refusing to save because the stroke doesn't end. It is not reliably reproducable, it just randomly happens when using krita for any measure of time. Beware a ton of thread 1 backtraces following: Reproducible: Sometimes Crash 1(don't remember) Thread 1 (Thread 0x77f0e8c0 (LWP 2963)): #0 KisStroke::lodBuddy (this=this@entry=0x0) at /home/krita/kde/src/krita/libs/image/kis_stroke.cpp:292 #1 0x731a815c in KisStrokesQueue::addJob (this=, id=..., data=0x139b96f0) at /home/krita/kde/src/krita/libs/image/kis_strokes_queue.cpp:255 #2 0x731b1055 in KisUpdateScheduler::addJob (this=0x11fd5168, id=..., data=data@entry=0x139b96f0) at /home/krita/kde/src/krita/libs/image/kis_update_scheduler.cpp:187 #3 0x731c8835 in KisImage::addJob (this=this@entry=0xd1b7440, id=..., data=data@entry=0x139b96f0) at /home/krita/kde/src/krita/libs/image/kis_image.cc:1272 #4 0x7fffad402983 in KisToolMove::moveBySpinY (this=0x12235300, newY=) at /home/krita/kde/src/krita/plugins/tools/basictools/kis_tool_move.cc:509 #5 0x7fffad41058b in KisToolMove::qt_static_metacall (_o=0x12235300, _c=, _id=, _a=) at /home/krita/kde/build/plugins/tools/basictools/moc_kis_tool_move.cpp:160 #6 0x75777cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #7 0x7fffad40ece1 in MoveToolOptionsWidget::sigSetTranslateY (this=, _t1=0) at /home/krita/kde/build/plugins/tools/basictools/moc_kis_tool_movetooloptionswidget.cpp:229 #8 0x7fffad404260 in MoveToolOptionsWidget::on_translateYBox_valueChanged (this=, arg1=) at /home/krita/kde/src/krita/plugins/tools/basictools/kis_tool_movetooloptionswidget.cpp:185 #9 0x7fffad40f22b in MoveToolOptionsWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at /home/krita/kde/build/plugins/tools/basictools/moc_kis_tool_movetooloptionswidget.cpp:143 #10 0x7fffad410c35 in MoveToolOptionsWidget::qt_metacall (this=0x13944b50, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0x7fffbbe0) at /home/krita/kde/build/plugins/tools/basictools/moc_kis_tool_movetooloptionswidget.cpp:201 #11 0x75778352 in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #12 0x768bf32e in QSpinBox::valueChanged(int) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #13 0x766cec63 in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #14 0x7663f75a in ?? () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 ---Type to continue, or q to quit--- #15 0x766ced14 in QSpinBox::setValue(int) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5 #16 0x7fffad403ea1 in MoveToolOptionsWidget::slotSetTranslate (this=, newPos=...) at /home/krita/kde/src/krita/plugins/tools/basictools/kis_tool_movetooloptionswidget.cpp:171 #17 0x7fffad3ff2fa in KisToolMove::slotNodeChanged (this=this@entry=0x12235300, nodes=...) at /home/krita/kde/src/krita/plugins/tools/basictools/kis_tool_move.cc:526 #18 0x7fffad4105ac in KisToolMove::qt_static_metacall (_o=0x12235300, _c=, _id=, _a=) at /home/krita/kde/build/plugins/tools/basictools/moc_kis_tool_move.cpp:161 #19 0x75777cef in QMetaObject::activate(QObject*, int, int, void**) () from /home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5 #20 0x77990b75 in KisNodeManager::sigUiNeedChangeSelectedNodes (this=this@entry=0xc332ad8, _t1=...) at /home/krita/kde/build/libs/ui/moc_kis_node_manager.cpp:434 #21 0x777091e1 in KisNodeManager::slotSetSelectedNodes (this=0xc332ad8, nodes=...) at /home/krita/kde/src/krita/libs/ui/kis_node_manager.cpp:680 #22 0x7fffaaf15d7f in KisLayerBox::setCanvas (this=0xd681890, canvas=0xe3a6308) at /home/krita/kde/src/krita/plugins/dockers/defaultdockers/kis_layer_box.cpp:299 #23 0x72778dac in KoCanvasControllerWidget::Private::activate (this=0xda5b990) at /home/krita/kde/src/krita/libs/flake/KoCanvasControllerWidget.cpp:150 #24 0x7793d393 in KisViewManager::setCurrentView (this=0xc3327f0, view=view@entry=0xe3d1920) at /home/krita/kde/src/krita/lib
[plasmashell] [Bug 366166] all icons tiny on hidpi screen
https://bugs.kde.org/show_bug.cgi?id=366166 Lukas Schneiderbauer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Lukas Schneiderbauer --- Okay, I see the problem now. In 5.6. I had to set QT_AUTO_SCREEN_SCALE_FACTOR=1 in /etc/profile.d since the plasma-internal scaling options did not work any more (coming from 5.5). It seems plasma overrides this option now and relies again on the scaling options one can set in systemsettings. So it works again. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366244] New: Plasma crashed after login with new user
https://bugs.kde.org/show_bug.cgi?id=366244 Bug ID: 366244 Summary: Plasma crashed after login with new user Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ehler...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Worked fine until I installed nvidia drivers. So I removed those 3 drivers and the problem still persists. I created a new user to make sure something wasn't messed up in my home directory, but the new user crashed immediatly after logging in. I had to disable nouveau to use nv, otherwise I could start the xserver at all. I couldn't get to the log screen until I switched the display manager from sddm to any of the others (currently using kdm). I have nvidia Quadro FX1500 graphics card on an HP xw8400 Workstation. Just installed OpenSUSE Leap 42.1. Had worked fine on previous OpenSUSE versions up to 12.3. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc484ec7c0 (LWP 28619))] Thread 10 (Thread 0x7fdc257d3700 (LWP 28633)): #0 0x7fdc411ff03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc2b9d3ac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fdc2b9d3637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fdc24fd2700 (LWP 28634)): #0 0x7fdc411ff03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc2b9d3ac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fdc2b9d3637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fdc247d1700 (LWP 28635)): #0 0x7fdc411ff03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc2b9d3ac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fdc2b9d3637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fdc23fd0700 (LWP 28636)): #0 0x7fdc411ff03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc2b9d3ac3 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fdc2b9d3637 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fdc2178c700 (LWP 28637)): #0 0x7fdc419f1bfd in poll () at /lib64/libc.so.6 #1 0x7fdc3e0cee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdc3e0cef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fdc4231ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fdc422c5d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fdc420e761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fdc453fbe18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fdc420ec32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fdc15c9a700 (LWP 28638)): #0 0x7fdc419edccd in read () at /lib64/libc.so.6 #1 0x7fdc3e10fb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdc3e0ce999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fdc3e0cedf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fdc3e0cef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fdc4231ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fdc422c5d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fdc420e761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fdc453fbe18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fdc420ec32f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fdc411fb0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fdc419fa02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fdc0700 (LWP 28639)): #0 0x7fdc3e110cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fdc3e0cef68 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdc4231ed8b in
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #4 from Laurent Montel --- Ok so sorry if you can't provide a test case I will not lose my time against it. That's all. I don't have a lot of time to debug/test/fix etc. so if you don't want to help me it so I will not lose my time against this bug. I am more bugs to fix. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348161] wma support (edit: my bad it's a more global problem, can't render at all)
https://bugs.kde.org/show_bug.cgi?id=348161 --- Comment #3 from ali...@riseup.net --- Am sorry but more than a year has passed since I reported the bug so that I don't recall which version it was nor and from which rep I don't even have any wma file left to try it again now plus I' trying an other OS -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #5 from Dominik George --- (In reply to Laurent Montel from comment #4) > Ok so sorry if you can't provide a test case I will not lose my time against > it. > That's all. > I don't have a lot of time to debug/test/fix etc. so if you don't want to > help me it so I will not lose my time against this bug. > I am more bugs to fix. > Regards. Well, this bug simply is *not* about opening a specific mail inside KMail, but about *composing* a new one from a mailto: link, e.g. when called from a web browser. There simply *is no* mail anyone could provide as mbox, because the bug is not about displaying mail. Test cases for the mailto: feature have already been posted in the initial bug report. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363586] Kmail2 handles mailto: incorrectly. urlencoded does not work
https://bugs.kde.org/show_bug.cgi?id=363586 --- Comment #6 from Dominik George --- > Test cases for the mailto: feature have already been posted in the initial > bug report. You can find several millions of other test cases at http://bugs.debian.org - simply choose a random bug report and click a random „reply“ link. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 366245] New: heigt value used in globe projection leads to blurred images
https://bugs.kde.org/show_bug.cgi?id=366245 Bug ID: 366245 Summary: heigt value used in globe projection leads to blurred images Product: marble Version: 1.14 (KDE Applications 16.04) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: k...@opensource.sf-tec.de The height values on bigger zoom levels differs from globe to merkator projection, so the tiles will get scaled and everything on them becomes blurred. On high zoom levels there is no reason to not use the same height value, the globe effect is so small it should be entirely ignored there. Reproducible: Always Steps to Reproduce: 1. use a map of something like 40x20 kilometers or anything smaller 2. switch between globe and merkator projections 3. observe that the images get blurred in globe 4. zoom in even more, where the same problem will be visible for any other zoom level -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] New: Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 Bug ID: 366246 Summary: Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds Product: plasmashell Version: 5.7.2 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: rpedr...@xstore.co.za CC: plasma-b...@kde.org Since upgrading to Plasma 5.7, I've had an issue where the taskbar will randomly disappear for a few seconds and then reappear. Also my desktop background goes black so I assume it's actually plasmashell that is restarting. I can force the issue by running the "About System" system settings module. There is no other specific desktop action that I can point to that causes this issue. dmesg shows nothing and system logs have no clue. This may relate to a much higher CPU usage than normal since the upgrade to Plasma 5.6. CPU usage of the plasmashell process is now directly linked to the no. of task bar icons in use. Reproducible: Sometimes Steps to Reproduce: 1. Use desktop 2. I can force the issue by restart the "About System" system settings module 3. Actual Results: Taskbar disappears Expected Results: Taskbar should not disappear Slackware 14.2 Plasma 5.7.2 Frameworks 5.24.0 QT 5.6.1 Kernel 4.4.14 NVidia 367.27 Multi-monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |FIXED --- Comment #1 from Eike Hein --- Not useful without a crash backtrace. "About System" is third-party code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 --- Comment #3 from Eike Hein --- Check for the crash handler icon in the system tray area. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 --- Comment #4 from Robby Pedrica --- There is nothing because the entire system tray goes missing while plasmashell restarts, and nothing after the restart. If that is the only option then I guess there is no way to provide info on this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366247] New: Digikam writes metadata to some files only not every one
https://bugs.kde.org/show_bug.cgi?id=366247 Bug ID: 366247 Summary: Digikam writes metadata to some files only not every one Product: digikam Version: 5.0.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: Database-Maintenance Assignee: digikam-de...@kde.org Reporter: aegor...@gmail.com I have a folder with 60 JPGs, none of them are read only; all of them are full access for all users in NTFS properties; every single picture has a tag. However, if I sync the metadata to images, I can see that only 23 pictures have tags written to the metadata, the rest have a sidecar file (xmp) Reproducible: Sometimes Steps to Reproduce: 1. Add tags to multiple images in digikam 2. Write metadata to images 3. Open windows file explorer, go to file properties - details - tags Actual Results: Some images have tags, some don't Expected Results: Every image you add a tag in digikam to should have a tag in file properties I think the malfunction happens not every time. I did not check every single file in other folders but I took a quick look at they seem to be fine. Star ratings have been written to metadata without errors. All starred images have tags written to metadata. All pictures with faces detected have tags written to metadata. The bug might be related to Bug 361378 - Tags are not being removed from files metadata I tried to switch the lazy synchronization on and off but the result is the same. I tried to remove one tag and add it again but the result is the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366246] Plasmashell restarts randomly, taskbar disappears and reappears after +/- 10 seconds
https://bugs.kde.org/show_bug.cgi?id=366246 --- Comment #2 from Robby Pedrica --- Hi Eike Is there any way for me to provide a backtrace or crash info? As mentioned, there is nothing in dmesg ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366247] Digikam writes metadata to some files only not every one
https://bugs.kde.org/show_bug.cgi?id=366247 --- Comment #2 from wildcowboy --- Here is a screenshot of the folder in windows file explorer. https://goo.gl/photos/Qpzono8Jh5FxVC4d8 Every single file is supposed to have a tag "zoo". I wish I could show tags as a column in digikam table view. You would see the difference between file explorer and digikam side by side then. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366247] Digikam writes metadata to some files only not every one
https://bugs.kde.org/show_bug.cgi?id=366247 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Using single core to process image give better results ? >Open windows file explorer, go to file properties - details - tags And you expect to see Windows explorer to give right metadata ? You must check on image metadata as well. Look in XMP metadata tags viever in digiKam or Showfoto for details (do not use tags filter here). Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366248] New: SDDM background change does no effect
https://bugs.kde.org/show_bug.cgi?id=366248 Bug ID: 366248 Summary: SDDM background change does no effect Product: systemsettings Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: yy...@gmx.com SDDM background change does no effect Reproducible: Always Steps to Reproduce: 1.open kcm-sddm and your SDDM theme background 2.do logout from your kde plasma session 3. Actual Results: previous background is still active in SDDM Expected Results: new background is active in SDDM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366248] SDDM background change does no effect
https://bugs.kde.org/show_bug.cgi?id=366248 --- Comment #1 from Dr. Chapatin --- step 1: 1.open kcm-sddm and change your SDDM theme background -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366247] Digikam writes metadata to some files only not every one
https://bugs.kde.org/show_bug.cgi?id=366247 --- Comment #3 from wildcowboy --- (In reply to caulier.gilles from comment #1) > Using single core to process image give better results ? > I am not sure I understood you fully. Digikam is not asking you whether to use all processor cores or work on a single core when you click on "sync" icon in thumbbar or select all files, go to "item" menu then "write metadata to selected images" . There is a checkbox for it in the menu "tools" - "maintenance" but digikam usually crashes on my computer if I check the box so I stopped using it and normally leave it unchecked. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings
https://bugs.kde.org/show_bug.cgi?id=180051 David Jarvie changed: What|Removed |Added CC||djar...@kde.org --- Comment #104 from David Jarvie --- Created attachment 100374 --> https://bugs.kde.org/attachment.cgi?id=100374&action=edit Patch to initialise Qt printer dialog with CUPS settings There is a Qt code review, https://codereview.qt-project.org/#/c/32127/, with a patch for initialising the Qt printer dialog with all the CUPS settings, including default printer, duplex mode and greyscale/colour. This worked for me with Qt 4.8.6. I attach a patch file obtained from this code review. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366247] Digikam writes metadata to some files only not every one
https://bugs.kde.org/show_bug.cgi?id=366247 --- Comment #4 from wildcowboy --- (In reply to caulier.gilles from comment #1) > >Open windows file explorer, go to file properties - details - tags > > And you expect to see Windows explorer to give right metadata ? Since windows explorer reads metadata I am expecting to see there the tags I added in digikam > You must check on image metadata as well. Look in XMP metadata tags viever > in digiKam or Showfoto for details (do not use tags filter here). > > Gilles Caulier Could you walk me through on what should I do here please. I have never heard of "XMP metadata tags viewer" and never used "showfoto" either. I did open the last one though but I could not figure out how to make it showing tags -- You are receiving this mail because: You are watching all bug changes.
[abakus] [Bug 366249] New: SZY 1~855-709--2847@@ EPSON PRINTER tech support phone number , EPSON PRINTER customer care phone number USA..
https://bugs.kde.org/show_bug.cgi?id=366249 Bug ID: 366249 Summary: SZY 1~855-709--2847@@ EPSON PRINTER tech support phone number , EPSON PRINTER customer care phone number USA.. Product: abakus Version: 0.90 Platform: Compiled Sources OS: OpenBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k.h...@gmx.de Reporter: dheer...@codehot.co.uk EPSON PRINT++1*8*5*5*7*0*9*2*8*4*7*++SUPPORT PHONE NUMBER..CUSTOMER SUPPORT PHONE NUMBER USA@@EpSOn Printer Support Number !!18(00)-709-2847 EpSOn Printer support number us EpSOn Printer support phone number, EpSOn Printer Tech Support Phone Number Describe USA@@Call, 1-855-709-2847 for all type help by EpSOn Printer support phone number, Intuit EpSOn Printer Tech Support Phone Number, EpSOn Printer Help Desk Phone Number, EpSOn Printer tech support number, EpSOn Printer technical support phone number,@@@ EpSOn Printer phone number, EpSOn Printer technical support number, EpSOn Printer support phone number, EpSOn Printer technical support, EpSOn Printer Customer Service Phone Number, EpSOn Printer Customer Service Number, EpSOn Printer Customer Support Phone Number, EpSOn Printer Customer Support Number, EpSOn Printer Customer Service Helpline Number, EpSOn Printer Customer Care Number, EpSOn Printer support team phone number, @ EpSOn Printer help number-EpSOn Printer Helpline Number; EpSOn Printer help phone number-EpSOn Printer Helpline Number, EpSOn Printer Tech Support Toll free Number, EpSOn Printer Support Telephone Number, EpSOn Printer Tech Support Telephone number, EpSOn Printer Tech Support contact number, EpSOn Printer support contact number, EpSOn Printer technical support contact number. Call, EpSOn Printer tech support phone number, Intuit EpSOn Printer Tech Support Phone Number, EpSOn Printer Help Desk Phone Number, EpSOn Printer tech support number, EpSOn Printer technical support phone number, EpSOn Printer phone number, EpSOn Printer technical support number, EpSOn Printer support phone number. It is very popular toll free number which provide by EpSOn Printer technical support, EpSOn Printer Customer Service Phone Number, EpSOn Printer Customer Service Number, EpSOn Printer Customer Support Phone Number, EpSOn Printer Customer Support Number, EpSOn Printer Customer Service Helpline Number, EpSOn Printer Customer Care Number, EpSOn Printer support team phone number. Call, EpSOn Printer tech support phone number, Intuit EpSOn Printer Tech Support Phone Number, EpSOn Printer Help Desk Phone Number, EpSOn Printer tech support number, EpSOn Printer technical support phone number, EpSOn Printer phone number, EpSOn Printer technical support number, EpSOn Printer support phone number, EpSOn Printer technical support, EpSOn Printer Customer Service Phone Number, EpSOn Printer Customer Service Number, EpSOn Printer Customer Support Phone Number, EpSOn Printer Customer Support Number, EpSOn Printer Customer Service Helpline Number, EpSOn Printer Customer Care Number, EpSOn Printer support team phone number, EpSOn Printer help number-EpSOn Printer Helpline Number; EpSOn Printer help phone number, EpSOn Printer Helpline Number, EpSOn Printer Tech Support Toll free Number, EpSOn Printer Support Telephone Number, EpSOn Printer Tech Support Telephone number, EpSOn Printer Tech Support contact number, EpSOn Printer support contact number, EpSOn Printer technical support contact number, EpSOn Printer support phone number, EpSOn Printer payroll support phone number. EpSOn Printer payroll customer support phone number EpSOn Printer Support Helpline Number, EpSOn Printer contact number EpSOn Printer tech support phone number EpSOn Printer support team phone number EpSOn Printer contact number 1855-709-2847 EpSOn Printer technical help telephone number, EpSOn Printer technical help contact number, EpSOn Printer technical support contact number, EpSOn Printer contact number, EpSOn Printer contact phone number, EpSOn Printer contact telephone number, EpSOn Printer 24 hour contact number, EpSOn Printer customer support contact number, EpSOn Printer customer service contact number, EpSOn Printer official number, EpSOn Printer official contact number, EpSOn Printer 855 contact number, EpSOn Printer toll free number, 855 number for EpSOn Printer support, EpSOn Printer 24/7 support phone number EpSOn Printer support phone number,EpSOn Printer support phone number,EpSOn Printer help phone number, EpSOn Printer technical support number.EpSOn Printer support number, EpSOn Printer phone number, EpSOn Printer tech support number, EpSOn Printer customer support number, EpSOn Printer customer support phone number, EpSOn Printer customer service phone number, EpSOn Printer payroll customer service phone number, EpSOn Printer support phone number. Help@Call 1-855-709-2847/.E
[Active] [Bug 366250] New: Tech Support C@ll @@@$I8557092847+++ Epson Printer c.u.s.t.o.m.e.r S.u.p.p.o.rt p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l
https://bugs.kde.org/show_bug.cgi?id=366250 Bug ID: 366250 Summary: Tech Support C@ll @@@$I8557092847+++ Epson Printer c.u.s.t.o.m.e.r S.u.p.p.o.rt p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l Product: Active Version: unspecified Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: act...@kde.org Reporter: dheer...@codehot.co.uk ((moti))Call @@@++ USA I8557O92847 EPSON p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8557O92847 EPSON p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON printer Tech Support phone number,EPSON technical support phone number 1 I8557O92847 .EPSON Tech Support Number EPSON Tech EPSON tech support, EPSON tech support number, EPSON tech support phone number, EPSON technical support, EPSON technical support number, EPSON technical support phone number, EPSON tech support number, EPSON support number, EPSON Tech support phone number, EPSON support phone number, EPSON technical support phone number, EPSON technical support number,Support Phone Number for EPSON printer Phone Number for EPSON CustomerService Technical Support Telephone Number EPSON printer support number EPSON EPSON printer tech support number EPSON EPSON printer technical support number EPSON EPSON printer technical support phone number EPSON EPSON printer customer service number EPSON EPSON internet security technical support EPSON technical support phone number EPSON EPSON tech support phone number EPSON EPSON customer support phone number I-855-709-2847 EPSON EPSON printer support phone number EPSON EPSON support phone EPSON tech support EPSON customer support EPSON phone support EPSON support number EPSON EPSON technical support EPSON printer customer support phone number EPSON EPSON printer tech support phone number EPSON contact EPSON support EPSON printer technical support phone number ~!~I8557092847++ EPSON EPSON phone number EPSON tech support EPSON support ticket EPSON customer support number EPSON EPSON tech support number EPSON EPSON technical support number EPSON EPSON support center EPSON telephone support call EPSON support EPSON printer support support EPSON EPSON billing support EPSON printer technical support number EPSON support EPSON printer EPSON online support EPSON contact support EPSON printer support number EPSON EPSON printer customer support number EPSON EPSON printer tech support number EPSON support for EPSON EPSON phone number EPSON EPSON customer service phone number EPSON EPSON contact phone number EPSON EPSON printer phone number EPSON EPSON printer customer service phone number EPSON phone number EPSON for EPSON customer service EPSON software phone number EPSON phone number EPSON for EPSON EPSON customer service telephone number EPSON EPSON helpline phone number EPSON EPSON contact number EPSON EPSON customer service number EPSON EPSON customer service phone number ~!~I8557092847++ EPSON us EPSON customer service phone number EPSON usa EPSON telephone number EPSON EPSON phone number EPSON usa EPSON printer contact number EPSON EPSON number EPSON EPSON contact number EPSON usa EPSON printer helpline number EPSON EPSON helpline number EPSON EPSON customer number EPSON EPSON printer customer service number EPSON EPSON contact telephone number EPSON contact number EPSON for EPSON EPSON software contact number EPSON EPSON toll free number EPSON EPSON telephone number EPSON uk EPSON registration number EPSON EPSON toll free number EPSON usa EPSON customer service EPSON software customer service contact EPSON customer service EPSON customer service phone EPSON printer customer service EPSON service EPSON printer technical support EPSON printer customer support EPSON technical support reviews telephone EPSON printer EPSON tech support phone number EPSON EPSON printer tech support phone number EPSON EPSON printer customer service EPSON technical support phone number EPSON EPSON printer free printer support EPSON customer service billing EPSON customer service email address EPSON customer service reviews contact EPSON customer service EPSON tech support number EPSON usa EPSON printer support number EPSON EPSON printer contact number EPSON EPSON customer service phone number EPSON EPSON technical support usa EPSON technical support number EPSON EPSON tech support phone EPSON tech support number EPSON EPSON customer service telephone number EPSON EPSON printer customer support number EPSON EPSON printer phone number EPSON EPSON printer online support EPSON customer service number EPSON EPSON tech
[Akonadi] [Bug 366213] akonadi server not starting
https://bugs.kde.org/show_bug.cgi?id=366213
--- Comment #2 from guyl ---
(In reply to Laurent Montel from comment #1)
> Without more information we can't help you :)
> Perhaps it's because you didn't start your computer ?:)
> Perhaps it's because you don't have akonadi installed in your computer :)
>
> it's very important to add more information as:
> - which is the version ?
> - What is the error in console when you use akonadictl start
> - what is the error in log file
> - etc.
>
> So I think when you create a bug report you need to add more info.
>
> Regards
Hi, thx for helping
I use version KDE 4.14.13
here is the Konsole output
guy@kubuntuguy:~$ akonadictl start
Starting Akonadi Server...
done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
guy@kubuntuguy:~$ search paths: ("/usr/local/sbin", "/usr/local/bin",
"/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games",
"/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec",
"/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/guy/.local/share/akonadi/mysql.conf",
"--datadir=/home/guy/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-guy.zov9ly/mysql.socket")
stdout: ""
stderr: "160729 9:37:39 [Note] /usr/sbin/mysqld (mysqld
5.5.50-0ubuntu0.14.04.1) starting as process 11680 ...
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418937]
1: akonadiserver() [0x418b92]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36cb0) [0x7ff589606cb0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7ff589606c37]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7ff58960a028]
5:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102)
[0x7ff58ae08c92]
6: akonadiserver() [0x41aa3d]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0)
[0x7ff58aea3470]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11ab3d) [0x7ff58aeb2b3d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31)
[0x7ff58aebb721]
10: akonadiserver() [0x47fa69]
11: akonadiserver() [0x41b687]
12: akonadiserver() [0x41dd15]
13: akonadiserver() [0x4e23d4]
14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e)
[0x7ff58af2dc1e]
15:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d)
[0x7ff58af154dd]
16:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed)
[0x7ff58af18b3d]
17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1aaf83) [0x7ff58af42f83]
18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x254)
[0x7ff588cd5e04]
19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49048) [0x7ff588cd6048]
20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)
[0x7ff588cd60ec]
21:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x71)
[0x7ff58af427a1]
22:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)
[0x7ff58af140af]
23:
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175)
[0x7ff58af143a5]
24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89)
[0x7ff58af19b79]
25: akonadiserver() [0x412ec5]
26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7ff5895f1f45]
27: akonadiserver() [0x41388e]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)
search paths: ("/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin",
"/sbin", "/bin", "/usr/games", "/usr/local/games", "/usr/sbin",
"/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/guy/.local/share/akonadi/mysql.conf",
"--datadir=/home/guy/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-guy.zov9ly/mysql.socket")
stdout: ""
stderr: "160729 9:37:39 [Note] /usr/sbin/mysqld (mysqld
5.5.50-0ubuntu0.14.04.1) starting as process 11695 ...
"
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver() [0x418937]
1: akonadiserver() [0x418b92]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36cb0) [0x7f5d1228fcb0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f5d1228fc37]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0
[systemsettings] [Bug 366248] SDDM background change does no effect
https://bugs.kde.org/show_bug.cgi?id=366248 Rog131 changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #2 from Rog131 --- A dublicate of the Bug 344867 - Setting custom background image in kcm_sddm does not work : https://bugs.kde.org/show_bug.cgi?id=344867 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365301] QtCreator installation fails
https://bugs.kde.org/show_bug.cgi?id=365301 neopara...@gmail.com changed: What|Removed |Added CC||neopara...@gmail.com --- Comment #1 from neopara...@gmail.com --- Created attachment 100375 --> https://bugs.kde.org/attachment.cgi?id=100375&action=edit output of installation output of "sudo apt-get install qtcreator" -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362241] Rectangular Region option does not preview and does not save an image after 15.12.3-2 -> 16.04.0-1
https://bugs.kde.org/show_bug.cgi?id=362241 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com --- Comment #9 from Stuart K. Smith --- Rectanglar Region capture does not work below about 400x300 ish Version 16.04.3 on KDEneon Why is this marked "Resolved?" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348161] wma support (edit: my bad it's a more global problem, can't render at all)
https://bugs.kde.org/show_bug.cgi?id=348161 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 Patrice Grundmann changed: What|Removed |Added CC||patrice.grundm...@gmail.com --- Comment #6 from Patrice Grundmann --- The problem still exist in Akregator Version 5.1.3 ! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366251] New: cant bind Win-q to switch to desktop
https://bugs.kde.org/show_bug.cgi?id=366251 Bug ID: 366251 Summary: cant bind Win-q to switch to desktop Product: systemsettings Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: zel...@gmail.com I binded all my change work space keys to win-1,win- win-e, win-a etc... all works but the win-q one seems not to work at all (its bound to ws 5) i looked and didnt see any other keys bound to that. Reproducible: Always Steps to Reproduce: 1. open system (kwin) keyboard configuration 2. define switch to desktop 5 as Win-q 3. dosent switch Actual Results: expect the key combo to switch to ws-5 Expected Results: dosent switch -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 366252] New: KOrganizer crashes after last upgrade
https://bugs.kde.org/show_bug.cgi?id=366252
Bug ID: 366252
Summary: KOrganizer crashes after last upgrade
Product: neon
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Packages Dev Edition [unstable]
Assignee: neon-b...@kde.org
Reporter: menakvis...@yandex.ru
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
After last upgrade of Neon developers unstable (July 29, 2016) the KOrganizer
crashes. The window appears for some fraction of a second and closes. Running
in Konsole gives such output:
vishap@vishap-desktop:~$ korganizer
log_kidentitymanagement: IdentityManager: There was no default identity.
Marking first one as default.
""
()
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
"/subscriber/korganizer_6163_lHsgWM"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
"ETMCalendar"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
"/subscriber/korganizer_6163_2sRplz"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
log_kidentitymanagement: IdentityManager: There was no default identity.
Marking first one as default.
log_kidentitymanagement: IdentityManager: There was no default identity.
Marking first one as default.
log_kidentitymanagement: IdentityManager: There was no default identity.
Marking first one as default.
log_kidentitymanagement: IdentityManager: There was no default identity.
Marking first one as default.
"/subscriber/korganizer_6163_ZYwZKx"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
"/subscriber/korganizer_6163_5fF3VQ"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
"/subscriber/korganizer_6163_ZkgHMd"
connectToServer "/tmp/akonadi-vishap.YMjd36/akonadiserver.socket"
KServiceTypeTrader: serviceType "KOrganizer/Part" not found
done
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: Subtree: 1 QSet(12, 1, 11)
org.kde.akonadi.ETM: collection: "DeclinedInvitations"
org.kde.akonadi.ETM: collection: "Search"
org.kde.akonadi.ETM: collection: "OpenInvitations"
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: collection: "akonadi_ical_resource_0"
org.kde.akonadi.ETM: Subtree: 10 QSet(10)
org.kde.akonadi.ETM: collection: "Дни рождения и годовщины"
org.kde.akonadi.ETM: Fetch job took 301 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 5
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Fetch job took 73 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: Fetch job took 97 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: Fetch job took 112 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
PLUGIN : identifier "application/octet-stream@QByteArray"
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_addressee.desktop"
for ("text/vcard", "text/directory") @ ("legacy", "default",
"KContacts::Addressee")
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_contactgroup.desktop"
for ("application/x-vnd.kde.contactgroup") @ ("legacy", "default",
"KContacts::ContactGroup")
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_kalarm.desktop" for
("application/x-vnd.kde.alarm", "application/x-vnd.kde.alarm.active",
"application/x-vnd.kde.alarm.archived", "application/x-vnd.kde.alarm.template")
@ ("default", "KAlarmCal::KAEvent")
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_kcalcore.desktop"
for ("text/calendar", "application/x-vnd.akonadi.note",
"application/x-vnd.kde.notes") @ ("default", "KCalCore::Incidence*")
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_mail.desktop" for
("message/rfc822", "message/news", "text/x-vnd.akonadi.note") @ ("legacy",
"default", "KMime::Message*")
registering Desktop file
"/usr/share/akonadi/plugins/serializer//akonadi_serializer_socialfeeditem.desktop"
for ("text/x-vnd.akonadi.socialfeeditem") @ ("Akonadi::SocialFeedItem")
ItemSerializerPluginLoader: found 33 plugins.
PLUGIN : identifier "text/directory@KContacts::
