[plasmashell] [Bug 488681] New: Desktop recycle bin icon behaves weirdly when using systemd-homed
https://bugs.kde.org/show_bug.cgi?id=488681 Bug ID: 488681 Summary: Desktop recycle bin icon behaves weirdly when using systemd-homed Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: simonecenton...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 170604 --> https://bugs.kde.org/attachment.cgi?id=170604&action=edit Screenshot of a broken trash icon on desktop SUMMARY When using a normal unix user, it does not seem to do weird things, but under systemd-homed sometimes it doesn't show up, sometimes it does but it's broken (see attachment). STEPS TO REPRODUCE 1. Create systemd-homed user 2. Place the trash .desktop file into the desktop 3. Poke it SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336936] Okteta's window is too tall in windowed mode
https://bugs.kde.org/show_bug.cgi?id=336936 Simone changed: What|Removed |Added CC||simonecenton...@gmail.com --- Comment #9 from Simone --- Can reproduce with Plasma 6.1 running Okteta 0.26.15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should when unmaximizing
https://bugs.kde.org/show_bug.cgi?id=487498 --- Comment #3 from Simone --- Interestingly, this also happens when creating a new user with plasma 6.1 vanilla configuration, except that it does not happen anymore only for blender, but with all Wayland apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should when unmaximizing
https://bugs.kde.org/show_bug.cgi?id=487498 --- Comment #5 from Simone --- I'm sorry, i thought this was a Kwin bug because it behaves as expected on other compositors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 --- Comment #44 from Simone --- was the fix merged for 6.0.3? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] New: Some Wayland clients retain a bigger window size than they should
https://bugs.kde.org/show_bug.cgi?id=487498 Bug ID: 487498 Summary: Some Wayland clients retain a bigger window size than they should Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: simonecenton...@gmail.com Target Milestone: --- SUMMARY This happens with Blender (and also telegram-desktop under certain circumstances), under X11 and gnome-wayland when you minimize the just-opened window it minimizes to make space, while on plasma Wayland it does not. This might have to do with faulty clients (both Blender and Telegram use custom toolkits). STEPS TO REPRODUCE 1. Open Blender on Wayland session 2. Drag the window down OBSERVED RESULT The windows remains of a bigger size EXPECTED RESULT The window should be smaller SOFTWARE/OS VERSIONS Distro: Arch Linux KDE Plasma Version: 6.1 Beta -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should
https://bugs.kde.org/show_bug.cgi?id=487498 --- Comment #1 from Simone --- Created attachment 169792 --> https://bugs.kde.org/attachment.cgi?id=169792&action=edit This video compares the behaviour both on Plasma and Gnome -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should
https://bugs.kde.org/show_bug.cgi?id=487498 --- Comment #2 from Simone --- I might have not specified that when you resize after the opening of the window it DOES retain, while it doesn't when it was just opened. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should when unmaximizing
https://bugs.kde.org/show_bug.cgi?id=487498 Simone changed: What|Removed |Added Summary|Some Wayland clients retain |Some Wayland clients retain |a bigger window size than |a bigger window size than |they should |they should when ||unmaximizing -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451589] New: Lockscreen shaking
https://bugs.kde.org/show_bug.cgi?id=451589 Bug ID: 451589 Summary: Lockscreen shaking Product: kscreenlocker Version: 5.24.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: simone.sala.scu...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When the screen locks the whole screen starts shaking and glitching. Also glitches with default Breeze. Running /ust/lib/kscreenlocker_greet --testing I get no errors and the lockscreen works as it should. Video: https://www.reddit.com/r/kde/comments/tfmzca/lockscreen_shaking/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.28-1-MANJARO (64-bit) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION Integrated Intel Graphics - Mesa Intel UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427686] New: Activity switcher only showing in the primary monitor
https://bugs.kde.org/show_bug.cgi?id=427686 Bug ID: 427686 Summary: Activity switcher only showing in the primary monitor Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Activity Switcher Assignee: ivan.cu...@kde.org Reporter: s.scalabri...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have a laptop connected with an external monitor. After updating to Plasma 5.20, when I open the activity switcher on the external monitor, it opens on the laptop monitor, while when I try to open it on the laptop monitor it just doesn't show (at least when the external monitor is connected). STEPS TO REPRODUCE 1. Connect at least two displays to the system (laptop + external monitor, in my case) 2a. Open the activity switcher on the non-primary monitor (e.g., right click on the desktop of the non-primary screen, "Show Activity Switcher") 2b. Open the activity switcher on the primary monitor (e.g., right click on the desktop of the primary screen, "Show Activity Switcher") OBSERVED RESULT 2a: The activity switcher opens on the primary monitor 2b: The activity switcher does not open EXPECTED RESULT 2a: The activity switcher opens on the non-primary monitor 2b: The activity switcher opens on the primary monitor SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION - This can be reproduced also by using other methods for opening the activity switcher (e.g., the "Activities" switcher or the keyboard shortcut); - The resolution of my primary monitor is 1920x1080, while the one of my external monitor is 2560x1440. - The version I selected for the bug report is "master", while it is 5.20, actually: 5.20 was one of the options I could select at the time I submitted the bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] New: Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 Bug ID: 464015 Summary: Psd files don't load layers correctly Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Android 13.x Status: REPORTED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: simonedr...@gmx.de Target Milestone: --- Created attachment 155119 --> https://bugs.kde.org/attachment.cgi?id=155119&action=edit Bug layers SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Create new picture 2. Create painting layers and draw 3. Save as psd file 4. Close the file and/or Krita 5. Open psd file or any psd file which was saved before OBSERVED RESULT All layers are white or show slim red/blue/green or grey lines Layers don't show content EXPECTED RESULT Layers show content of what was previously drawn SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 Simone changed: What|Removed |Added CC||simonedr...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #2 from Simone --- Created attachment 155142 --> https://bugs.kde.org/attachment.cgi?id=155142&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #3 from Simone --- Created attachment 155143 --> https://bugs.kde.org/attachment.cgi?id=155143&action=edit Psd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #4 from Simone --- Created attachment 155144 --> https://bugs.kde.org/attachment.cgi?id=155144&action=edit Krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #5 from Simone --- Hi, this may have happened after the update to 5.1.5. I have created psd files before the update and they were fine. Apparently, after the update none of my files show correctly. 1. File>New>Create 2. Draw on paint layer 3. File>Save as>Psd 4. Close file 5. Open file either via recent files or File>Open 6. Paint layer is white -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #6 from Simone --- Created attachment 155145 --> https://bugs.kde.org/attachment.cgi?id=155145&action=edit New file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #7 from Simone --- Created attachment 155146 --> https://bugs.kde.org/attachment.cgi?id=155146&action=edit New file 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #8 from Simone --- Created attachment 155147 --> https://bugs.kde.org/attachment.cgi?id=155147&action=edit Draw and save file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #9 from Simone --- Created attachment 155148 --> https://bugs.kde.org/attachment.cgi?id=155148&action=edit Saving -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #10 from Simone --- Created attachment 155149 --> https://bugs.kde.org/attachment.cgi?id=155149&action=edit Closed file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #11 from Simone --- Created attachment 155150 --> https://bugs.kde.org/attachment.cgi?id=155150&action=edit Reopen file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #12 from Simone --- Created attachment 155151 --> https://bugs.kde.org/attachment.cgi?id=155151&action=edit Open a previously saved file with lots of layers -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #13 from Simone --- Created attachment 155152 --> https://bugs.kde.org/attachment.cgi?id=155152&action=edit All layers are grey in preview and white on canvas -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #14 from Simone --- I just uninstalled Krita and installed again. It's the same issue. Not sure whether it's important but on the Google Store it says "Krita (Early Access)". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #17 from Simone --- Hi, I installed Krita for desktop and my old files look normal. The issue is with Krita on my Samsung Galaxy tablet S8 Ultra, SM-X900. I tried an experiment: 1. Save a file in Krita as psd (I noticed that after saving, the file name does not show in the header, even though it shows correctly in the recent files) 2. Open file in Clip Studio Paint and draw, save it as psd 3. Open the file in Krita Please check the attached files, it's all white after opening in Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #18 from Simone --- Created attachment 155194 --> https://bugs.kde.org/attachment.cgi?id=155194&action=edit Test file created with Krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #19 from Simone --- Created attachment 155195 --> https://bugs.kde.org/attachment.cgi?id=155195&action=edit Test file opened and saved in Csp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #20 from Simone --- Created attachment 155196 --> https://bugs.kde.org/attachment.cgi?id=155196&action=edit 1 draw in Krita, save file as psd, no file name -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #21 from Simone --- Created attachment 155197 --> https://bugs.kde.org/attachment.cgi?id=155197&action=edit 2 file name and preview available in recent files -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #22 from Simone --- Created attachment 155198 --> https://bugs.kde.org/attachment.cgi?id=155198&action=edit 3 open and draw in csp and save -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464015] Psd files don't load layers correctly
https://bugs.kde.org/show_bug.cgi?id=464015 --- Comment #23 from Simone --- Created attachment 155199 --> https://bugs.kde.org/attachment.cgi?id=155199&action=edit 4 open file in Krita, canvas is white -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 328616] When accepting invitation into google calendar resource im set as organizer
https://bugs.kde.org/show_bug.cgi?id=328616
Simone changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://invent.kde.org/pim/
||libkgapi/commit/a48887dbbc9
||bdc7da50c1f93c7235c16620bba
||36
Status|CONFIRMED |RESOLVED
Version Fixed In||5.17
--- Comment #2 from Simone ---
Git commit a48887dbbc9bdc7da50c1f93c7235c16620bba36 by Simone Scalabrino.
Committed on 19/12/2020 at 10:09.
Pushed by knauss into branch 'master'.
First attempt to fix bug 328616
As reported in https://bugs.kde.org/show_bug.cgi?id=328616, when a user
accepts an invitation to an event, when it is loaded on Google Calendar,
it creates a new event with the user as the organizer. To prevent this,
the "import" API should be used instead of the "insert" API.
With this change, the organizer is checked against the account name of
the user: if they match, the event is created (previous implementation),
otherwise the event is imported ("import" API).
This still requires some tests to check if it does not break anything.
FIXED-IN: 5.17
M +1-1autotests/calendar/data/event1_create_request.txt
M +2-2autotests/calendar/data/event2.json
M +2-2autotests/calendar/data/event2_create_request.txt
M +2-2autotests/calendar/data/event2_create_response.txt
M +2-2autotests/calendar/data/event2_modify_request.txt
M +2-2autotests/calendar/data/event2_modify_response.txt
M +2-2autotests/calendar/data/events_fetch_page2_response.txt
M +10 -0src/calendar/calendarservice.cpp
M +8-0src/calendar/calendarservice.h
M +12 -1src/calendar/eventcreatejob.cpp
https://invent.kde.org/pim/libkgapi/commit/a48887dbbc9bdc7da50c1f93c7235c16620bba36
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 Simone changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Simone --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487498] Some Wayland clients retain a bigger window size than they should when unmaximizing
https://bugs.kde.org/show_bug.cgi?id=487498 --- Comment #6 from Simone --- Hello, it took me long to figure this out. It's not KWin's fault but some clients do actually start with a too much large window and Mutter/X11 change their state to maximized and set a minimized size, to make it pleasant to use. KWin on wayland doesn't do this yet. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399571] [KNS] Update button can take a long time to get enabled when any backends are slow to update
https://bugs.kde.org/show_bug.cgi?id=399571 Simone changed: What|Removed |Added CC||s.scalabri...@gmail.com --- Comment #4 from Simone --- Same problem here. Trivial workaround: Removing the kns file from the system (e.g., /etc/xdg/kalzium.knsrc on Arch) or moving it somewhere else. What about making KNS updates optional? I mean, all the KNS providers could be listed in "settings" with a checkbox to enable/disable them, just like other sources (e.g. Flatpak). If a provider becomes unavailable, they could be easily disabled from the UI (without removing system files). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400469] New: Wrong character representation in file names with slash
https://bugs.kde.org/show_bug.cgi?id=400469
Bug ID: 400469
Summary: Wrong character representation in file names with
slash
Product: dolphin
Version: 18.08.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: s.scalabri...@gmail.com
CC: elvis.angelac...@kde.org
Depends on: 309192
Target Milestone: ---
Created attachment 115975
--> https://bugs.kde.org/attachment.cgi?id=115975&action=edit
Example of file name
When I use "/" in a file name, for example "test 1/2/3", the characters do not
appear as they are intended (in the example, I see something like "test ½/3",
see the attachment).
STEPS TO REPRODUCE
1. Create a new file with name "test 1/2/3"
OBSERVED RESULT
The file name is not rendered correctly (something similar to "test ½/3")
EXPECTED RESULT
The correct rendering would be "test 1⁄2⁄3", with the "⁄" character instead of
"/". As an alternative, I would expect an error.
SOFTWARE VERSIONS
Distribution: Arch Linux
KDE Plasma Version: 5.14.2
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=309192
[Bug 309192] KIO turns slash character ("/") into "⁄" when writing file
names--but not directory names
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 309192] KIO turns slash character ("/") into "⁄" when writing file names--but not directory names
https://bugs.kde.org/show_bug.cgi?id=309192 Simone changed: What|Removed |Added Blocks||400469 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400469 [Bug 400469] Wrong character representation in file names with slash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408185] New: While closing one of two samba windows opened, the backmost crashed
https://bugs.kde.org/show_bug.cgi?id=408185 Bug ID: 408185 Summary: While closing one of two samba windows opened, the backmost crashed Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: s.fos...@protonmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-20-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I was exploring one single password protected samba share with two windows opened in different folders. Before, the two windows was minimized and hovering the folder icon in the bottom bar showed me the grayed preview selection of the two. Hovering one of the two windows, the red close options showed. Clicking on the red x to close one dolphin crashed -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff26170f6c0 (LWP 26255))] Thread 2 (Thread 0x7ff243df5700 (LWP 26257)): #0 0x7ff260f92bf9 in __GI___poll (fds=0x7ff23c01a740, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff253eed5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff253eed6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff25b1a69bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff25b14ba1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff25af6a23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff25b623d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff25af6f17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff25605f6db in start_thread (arg=0x7ff243df5700) at pthread_create.c:463 #9 0x7ff260f9f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff26170f6c0 (LWP 26255)): [KCrash Handler] #6 0x55a8adbc0200 in () #7 0x7ff25cff0606 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #8 0x7ff25cff06a9 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #9 0x7ff25b17a24b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff25b183a7b in QObject::~QObject() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff25cfca579 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #12 0x7ff260ec1041 in __run_exit_handlers (status=0, listp=0x7ff261269718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #13 0x7ff260ec113a in __GI_exit (status=) at exit.c:139 #14 0x7ff260e9fb9e in __libc_start_main (main=0x55a8ac2ed730, argc=2, argv=0x7ffdf1559e88, init=, fini=, rtld_fini=, stack_end=0x7ffdf1559e78) at ../csu/libc-start.c:344 #15 0x55a8ac2ed76a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409516] New: [Wayland] Windows never start maximized
https://bugs.kde.org/show_bug.cgi?id=409516 Bug ID: 409516 Summary: [Wayland] Windows never start maximized Product: kwin Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- SUMMARY When I open any program in the Xorg session (e.g., Kate), KWin remembers the geometry of the window from the last time I used the same program and it re-applies it to the current window. Specifically, if the window was maximized in a previous working session, when I open the same program again the window is maximized. This does not happen in Wayland. Instead, the window is close to being maximized (same size of the screen), but it is not. This is not nitpicking, it affects usability and I find it really annoying: I usually move the mouse pointer straight to the upper-left corner of the screen to close a window; however, if the window is not actually maximized, the close button is not focused and I have to slightly move the mouse lower-right to close the window. STEPS TO REPRODUCE 1. Open Kate in a Wayland session 2. Maximize the window 3. Close Kate 4. Open Kate again OBSERVED RESULT The window is not maximized, i.e., if you open the context menu on the window's title bar, "Maximise" is not checked. EXPECTED RESULT The window should be actually maximized, i.e., if you open the context menu on the window's title bar, "Maximise" should be checked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.1.15-arch1-1-ARCH KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION The only KWin script enabled is "Enforces Window Decorations on GTK+ window" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409517] New: [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 Bug ID: 409517 Summary: [Wayland] KMail freezes Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- SUMMARY KMail randomly freezes in the Wayland session. This can happen at any moment, either a few seconds after I open it or after some minutes. STEPS TO REPRODUCE 1. Open KMail in the Wayland session 2. Open and scroll emails for a while OBSERVED RESULT KMail freezes. It is necessary to close it. EXPECTED RESULT KMail should keep working normally. SOFTWARE/OS VERSIONS KMail version: 19.04.2 Linux/KDE Plasma: 5.1.15-arch1 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] New: [Wayland] Panning is laggy
https://bugs.kde.org/show_bug.cgi?id=409644 Bug ID: 409644 Summary: [Wayland] Panning is laggy Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- Okular version: 19.04.2 SUMMARY Using a 4K external display with my laptop in Wayland makes the "Browse tool" very laggy. For example, if I press the left mouse button, I move the pointer and I release the button, the viewing area of the PDF moves, but 4/5 times more slowly than the mouse pointer, i.e., it keeps moving when I release the button. If I do the same in the "Thumbnails" area, instead, it works correctly. I think this is similar to https://bugs.kde.org/show_bug.cgi?id=387567. I can experience the problem when: 1) the "Browse tool" is used in the PDF area; 2) the scrollbar of the PDF area is moved. Okular works correctly when: 1) I browse the thumbnails of the PDF; 2) I use the mouse wheel. STEPS TO REPRODUCE 1. Open a PDF Okular with a 4K external monitor connected 2. Press the left button in the PDF view area, move the pointer, release the button OBSERVED RESULT The movement is significantly slower than the pointer, the viewport keeps moving even after the mouse button is released. EXPECTED RESULT The viewport moves as fast as the mouse pointer and it stops when the left button is released. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.1.15-arch1 (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Monitors: dual monitor, one 4K (external, scaled 2x), one 1080p (integrated in the laptop, not scaled) VGA controller: Intel Corporation UHD Graphics 630 ADDITIONAL INFORMATION This happens only in Wayland, not in X11. If I remember correctly, it doesn't happen when I don't connect the external monitor. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Simone changed: What|Removed |Added Summary|[Wayland] Panning is laggy |[Wayland] Panning in Okular ||is laggy with 4K monitor -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 387567] Panning and window resizing in gwenview is laggy
https://bugs.kde.org/show_bug.cgi?id=387567 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409644 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387567 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409647] New: [Wayland] KWin keeps the window of a crashed program half visible
https://bugs.kde.org/show_bug.cgi?id=409647 Bug ID: 409647 Summary: [Wayland] KWin keeps the window of a crashed program half visible Product: kwin Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- Created attachment 121414 --> https://bugs.kde.org/attachment.cgi?id=121414&action=edit Screenshot SUMMARY Not sure if it is KWin's or Plasma's fault. In Wayland, a program I am writing that is based on pyqt5 crashed because of a bug. The window did not completely disappear, but I cannot interact with it. STEPS TO REPRODUCE Not sure it is easy to reproduce. I didn't try to do this again. 1. Open a program based on PyQt5 2. Make it crash OBSERVED RESULT The window does not completely disappear EXPECTED RESULT The window should disappear SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.1.15-arch1 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION The window is just on a single virtual desktop. Please, see the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 --- Comment #24 from Simone --- Created attachment 121490 --> https://bugs.kde.org/attachment.cgi?id=121490&action=edit WAYLAND_DEBUG=1 konsole &>konsole.log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 --- Comment #25 from Simone --- I can confirm the same issue on plasma-workspace-5.15.5-1.fc30 The workaround is to set a fixed cursor size in KDE system settings (24px in my case). If I leave it as default 'dependent on resolution' the cursor is really huge. I don't have XCURSOR_SIZE set in my env. If I run the app with XCURSOR_SIZE=24 it works as expected. The cursor is displayed at correct size on window decorations and GTK/Xwayland apps. Debug info in konsole.log attachment -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]
https://bugs.kde.org/show_bug.cgi?id=409954 Simone changed: What|Removed |Added CC||simonebondi...@gmail.com --- Comment #7 from Simone --- Can confirm. The dialogs either do not show or show after a long delay, but the FTP connections stay alive and have to be manually closed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410972] New: [Arch] AUR support
https://bugs.kde.org/show_bug.cgi?id=410972 Bug ID: 410972 Summary: [Arch] AUR support Product: Discover Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: s.scalabri...@gmail.com CC: aleix...@kde.org Target Milestone: --- It would be nice if Discover had a backend for AUR packages (https://aur.archlinux.org). I have some AURs installed on my system, and I need to use something different than Discover to update them. If such a feature was implemented, I would probably use only Discover for package updating. STEPS TO REPRODUCE 1. Install an AUR package (e.g. spotify) on an Arch Linux system 2. Wait for a new version to become available OBSERVED RESULT Discover does not show any update for the AUR. EXPECTED RESULT Discover shows the updates for the AUR and it allows to install it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.2.8 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This is somewhat related to https://bugs.kde.org/show_bug.cgi?id=407096, but it is complementary. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410972] [Arch] AUR support
https://bugs.kde.org/show_bug.cgi?id=410972 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=407096 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407096] Wish - Allow Arch packages (.pkg.tar.gz) to be installed locally
https://bugs.kde.org/show_bug.cgi?id=407096 Simone changed: What|Removed |Added Blocks||410972 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=410972 [Bug 410972] [Arch] AUR support -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410972] [Arch] AUR support
https://bugs.kde.org/show_bug.cgi?id=410972 Simone changed: What|Removed |Added Depends on||407096 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=407096 [Bug 407096] Wish - Allow Arch packages (.pkg.tar.gz) to be installed locally -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407096] Wish - Allow Arch packages (.pkg.tar.gz) to be installed locally
https://bugs.kde.org/show_bug.cgi?id=407096 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=410972 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395953] New: Falkon does not work well with Plasma activities
https://bugs.kde.org/show_bug.cgi?id=395953 Bug ID: 395953 Summary: Falkon does not work well with Plasma activities Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: s.scalabri...@gmail.com Target Milestone: --- Falkon is not fully integrated in Plasma activities yet. For example, I am in the activity A and I open Falkon. Then I switch to the activity B, I click on the link "https://www.falkon.org/"; (e.g., on KMail). I expect that the link is opened in a new window of Falkon in activity B. Instead, Falkon opens the links in the existing window in the activity A, and it switches back to A. This is annoying, since it "breaks" the activity separation. At the moment, I have to manually open an empty instance of Falkon in B and then click on the link. I'm using the latest version of Falkon (3.0.1) on the latest version of Plasma (15.13.2). Not sure if this should be fixed in Falkon or in Plasma, since other applications have the same problem (e.g., Kate). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395953] Falkon does not work well with Plasma activities
https://bugs.kde.org/show_bug.cgi?id=395953 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=348012 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348012] Opening files arbitrarily switches to other Activities
https://bugs.kde.org/show_bug.cgi?id=348012 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=395953 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395954] New: Broken KDE activities integration
https://bugs.kde.org/show_bug.cgi?id=395954 Bug ID: 395954 Summary: Broken KDE activities integration Product: kate Version: 18.04.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- This is an annoying "bug" that appears when you use Plasma activities. How to reproduce: * Create two activities in Plasma, A and B * Switch to A * Open an instance of Kate * Switch to B * Open Dolphin (or any other file manager) * Open a text file (e.g., "text.txt") Expected result: Kate opens a new instance in B with "text.txt" Actual result: Kate opens "text.txt" in the already opened window in A, and the activity is switched. At the moment I have to manually open a new instance of kate in B before opening the file, but when I forget it is annoying, because I have to close the tab in A, switch back to B, open a new instance and, finally, open my file. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348012] Opening files arbitrarily switches to other Activities
https://bugs.kde.org/show_bug.cgi?id=348012 Simone changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=395954 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395953] Falkon does not work well with Plasma activities
https://bugs.kde.org/show_bug.cgi?id=395953 --- Comment #2 from Simone --- Any reasons for that? I don't expect a full KDE integration from other browsers, I didn't expect from QupZilla either. But since Falkon is part of the KDE project, I think that it should have that. Of course, not a priority, but why not? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395954] Broken KDE activities integration
https://bugs.kde.org/show_bug.cgi?id=395954 Simone changed: What|Removed |Added Ever confirmed|0 |1 Assignee|kwrite-bugs-n...@kde.org|s.scalabri...@gmail.com Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Simone --- Created attachment 113672 --> https://bugs.kde.org/attachment.cgi?id=113672&action=edit This is a patch I created that fixes the problem. The attached patch fixes the problem. I tested it in my environment (Plasma 15.13), but I think it should be tested also (i) in Wayland (without activities) and (ii) in a different DE. What I did is the following: 1) added a QDBus service to get the activities linked to a kate instance 2) added a check in the main in which, after all the other checks, if it still wants not to create a new instance, it makes sure that at least one of the currently running instances is in the current activity. If no instance is in the current activity, it forces a new instance. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 397598] New: Kile crashes when I right click on tabs
https://bugs.kde.org/show_bug.cgi?id=397598 Bug ID: 397598 Summary: Kile crashes when I right click on tabs Product: kile Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: s.scalabri...@gmail.com Target Milestone: --- How to reproduce: - Open two files in Kile - Right click on one of the tabs - Kile crashes I can always reproduce this. I cloned the repository few minutes ago and tried to find the cause: it seems that the problem is in line 530 of kileviewmanager.cpp (action5 is null, maybe?). I tried to remove all the lines involving "action5" and Kile does not crash anymore. However this is not a proper fix, I guess, because I removed the menu item. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 397598] Kile crashes when I right click on tabs
https://bugs.kde.org/show_bug.cgi?id=397598 Simone changed: What|Removed |Added Platform|Other |Archlinux Packages CC||s.scalabri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 389383] Crashes when I press tab in R
https://bugs.kde.org/show_bug.cgi?id=389383 --- Comment #5 from Simone --- Thank you for fixing it! -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 389383] New: Crashes when I press tab in R
https://bugs.kde.org/show_bug.cgi?id=389383 Bug ID: 389383 Summary: Crashes when I press tab in R Product: LabPlot2 Version: 2.4.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: s.scalabri...@gmail.com Target Milestone: --- Application: labplot2 (2.4.0) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.14.13-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: If I write something in a R CAS Worrksheet and I pressed "tab" (auto-complete), LabPlot crashes. Specifically, I tried to write "box" and I hit tab. The crash can be reproduced every time. -- Backtrace: Application: labplot2 (labplot2), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc583e8dd00 (LWP 29590))] Thread 2 (Thread 0x7fc565b25700 (LWP 29595)): #0 0x7fc57b4bc469 in () at /usr/lib/libQt5Core.so.5 #1 0x7fc57b4bac1a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #2 0x7fc57b4bb1f6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #3 0x7fc57b4bc8df in () at /usr/lib/libQt5Core.so.5 #4 0x7fc573da3549 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #5 0x7fc573da3f4e in () at /usr/lib/libglib-2.0.so.0 #6 0x7fc573da413e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #7 0x7fc57b4bcb94 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7fc57b45ed0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #9 0x7fc57b26e78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #10 0x7fc577d81416 in () at /usr/lib/libQt5DBus.so.5 #11 0x7fc57b273b2d in () at /usr/lib/libQt5Core.so.5 #12 0x7fc5768c508c in start_thread () at /usr/lib/libpthread.so.0 #13 0x7fc57a618e1f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fc583e8dd00 (LWP 29590)): [KCrash Handler] #5 0x7fc57b496b08 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /usr/lib/libQt5Core.so.5 #6 0x7fc54e861ce8 in () at /usr/lib/qt/plugins/cantor/backends/cantor_rbackend.so #7 0x7fc54c984c76 in () at /usr/lib/qt/plugins/libcantorpart.so #8 0x7fc57b49100f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x7fc54c980d31 in () at /usr/lib/qt/plugins/libcantorpart.so #10 0x7fc57c4ec7e6 in QGraphicsScene::keyReleaseEvent(QKeyEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7fc57c4fba47 in QGraphicsScene::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7fc57c1dae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7fc57c1e2816 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fc57b4606c0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7fc57c51a328 in QGraphicsView::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7fc57c1dae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7fc57c1e3da3 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7fc57b4606c0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fc57c23898b in () at /usr/lib/libQt5Widgets.so.5 #20 0x7fc57c1dae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7fc57c1e2816 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7fc57b4606c0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x7fc57b9ce012 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #24 0x7fc57b9d3166 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #25 0x7fc57b9aabbc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #26 0x7fc56ac8e2fd in () at /usr/lib/libQt5XcbQpa.so.5 #27 0x7fc57b45ed0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7fc57b467ff8 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #29 0x55addb880a07 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 389383] Crashes when I press tab in R
https://bugs.kde.org/show_bug.cgi?id=389383 --- Comment #2 from Simone --- I have Cantor 17.12.1-2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454
Simone changed:
What|Removed |Added
CC||simone.tolo...@gmail.com
--- Comment #42 from Simone ---
Confirmed in Fedora 29 stable.
libmtp-1.1.16-1.fc29.x86_64
In /lib/udev/rules.d/69-libmtp.rules:
ACTION!="add", ACTION!="bind", GOTO="libmtp_rules_end"
ENV{MAJOR}!="?*", GOTO="libmtp_rules_end"
SUBSYSTEM=="usb", GOTO="libmtp_usb_rules"
GOTO="libmtp_rules_end"
LABEL="libmtp_usb_rules"
Still get the error.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 --- Comment #43 from Simone --- I'm sorry I was wrong, seems to work now. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Simone changed: What|Removed |Added CC||simone.tolo...@gmail.com --- Comment #22 from Simone --- Still an issue on: plasma-workspace-5.14.4-1.fc29 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384848] New: Discover crashes when I search for something
https://bugs.kde.org/show_bug.cgi?id=384848 Bug ID: 384848 Summary: Discover crashes when I search for something Product: Discover Version: 5.10.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: s.scalabri...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.12.13-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I open Discover, I type something in the search box, it shows me some results and the spinner "Still looking" at the bottom; then, after few seconds, it crashes. I'm on ArchLinux. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5261794e80 (LWP 7134))] Thread 13 (Thread 0x7f520d6c4700 (LWP 7158)): #0 0x7f525ceb1cbb in poll () at /usr/lib/libc.so.6 #1 0x7f52574d8c09 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f52574d8d1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f525d7ee084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f525d791ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f525d5ab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #7 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f520f176700 (LWP 7150)): #0 0x7f52596c46cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f525d5b14a1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f525d5ac586 in () at /usr/lib/libQt5Core.so.5 #3 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #4 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f520f977700 (LWP 7149)): #0 0x7f52596c46cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f525d5b14a1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f525d5ac586 in () at /usr/lib/libQt5Core.so.5 #3 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #4 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f5224a7c700 (LWP 7148)): #0 0x7f52596c46cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f525d5b14a1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f525d5ac586 in () at /usr/lib/libQt5Core.so.5 #3 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #4 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f52261e2700 (LWP 7147)): #0 0x7f525d5a7a4f in QMutex::unlock() () at /usr/lib/libQt5Core.so.5 #1 0x7f525d7edfa2 in () at /usr/lib/libQt5Core.so.5 #2 0x7f52574d8148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f52574d8b3b in () at /usr/lib/libglib-2.0.so.0 #4 0x7f52574d8d1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f525d7ee084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f525d791ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f525d5ab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #9 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f52269e3700 (LWP 7144)): #0 0x7f525d5a79dc in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7f525d7edf8f in () at /usr/lib/libQt5Core.so.5 #2 0x7f52574d8148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f52574d8b3b in () at /usr/lib/libglib-2.0.so.0 #4 0x7f52574d8d1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f525d7ee084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f525d791ffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f525d5ab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f525d5b015b in () at /usr/lib/libQt5Core.so.5 #9 0x7f52596be08a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f525cebc1bf in clone () at /usr/lib/libc.so.6 Thread 7 (
[kwin] [Bug 490822] Since Plasma 6 - Wayland / XWayland - Correct resolution is not getting detected in some applications
https://bugs.kde.org/show_bug.cgi?id=490822 Simone changed: What|Removed |Added CC||simonecenton...@gmail.com --- Comment #1 from Simone --- Happens to me as well -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371681] New: Configuration with laptop lid closed is overwritten/lost when lid is opened
https://bugs.kde.org/show_bug.cgi?id=371681 Bug ID: 371681 Summary: Configuration with laptop lid closed is overwritten/lost when lid is opened Product: KScreen Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: simg...@gmail.com Target Milestone: --- Created attachment 101784 --> https://bugs.kde.org/attachment.cgi?id=101784&action=edit Kscreen log Connect HDMI > Close the lid > Open the lid When I have an external HDMI monitor connected and I close the laptop the current kscreen configuration is renamed appending the suffix lidOpened and a new one with the same identifier is created. In this way I can configure the monitors in different way depending if the lid is open or not. The problem is that when I open the lid again the *_lidOpened config file is removed (probably renamed causing the overwrite of the other configuration) and only one config files remains, losing the configuration of the case when the lid is closed. Closing the lid indeed results in a wrong configuration of the screens. The attached kscreen.log incudes the following operations: Connect HDMI > Close the lid > Open the lid -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371681] Configuration with laptop lid closed is overwritten/lost when lid is opened
https://bugs.kde.org/show_bug.cgi?id=371681 --- Comment #1 from Simone Gaiarin --- Created attachment 101785 --> https://bugs.kde.org/attachment.cgi?id=101785&action=edit Lid closed config file before opening the lid -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371681] Configuration with laptop lid closed is overwritten/lost when lid is opened
https://bugs.kde.org/show_bug.cgi?id=371681 --- Comment #2 from Simone Gaiarin --- Created attachment 101786 --> https://bugs.kde.org/attachment.cgi?id=101786&action=edit Lid opened config file before opening the lid -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 345225] External monitors not activated after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=345225 Simone Gaiarin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #13 from Simone Gaiarin --- I mark this as solved. In my case updating to Kernel 4.6 solved the problem. So it seems it was unrelated from KScreen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351390] Corrupted kscreen config breaks KDE startup process
https://bugs.kde.org/show_bug.cgi?id=351390 --- Comment #7 from Simone Gaiarin --- In my case it's not happening anymore in Plasma 5.8.2. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend
https://bugs.kde.org/show_bug.cgi?id=364044 Simone Gaiarin changed: What|Removed |Added CC|simg...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351390] Corrupted kscreen config breaks KDE startup process
https://bugs.kde.org/show_bug.cgi?id=351390 Simone Gaiarin changed: What|Removed |Added CC|simg...@gmail.com | -- 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 --- Comment #5 from Simone Gaiarin --- Fixed for me in Plasma 5.8.2. -- 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 Simone Gaiarin changed: What|Removed |Added CC|simg...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346535] KScreen does not detect external monitor the second time unless user logs out
https://bugs.kde.org/show_bug.cgi?id=346535 --- Comment #6 from Simone Gaiarin --- Fixed for me in Plasma 5.8.2. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346535] KScreen does not detect external monitor the second time unless user logs out
https://bugs.kde.org/show_bug.cgi?id=346535 Simone Gaiarin changed: What|Removed |Added CC|simg...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 368713] Solid doesn't detect disk as mounted
https://bugs.kde.org/show_bug.cgi?id=368713 Simone Gaiarin changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Simone Gaiarin --- Solved somehow, but I don't know how exactly. Probably not related to solid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348231] Bring window to current activity when selected
https://bugs.kde.org/show_bug.cgi?id=348231 --- Comment #6 from Simone Gaiarin --- I'm still facing the problem that some applications (like VLC) are opened in another activity but the activity is not switched. I've set a special rule: "Specific Application settings" > Size and Position > Activity:Apply Initially:MultimediaActivity Running KDE 5.8.2. What info can I provide to debug this behaviour? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362226] Baloo index keeps obsolete directory entries
https://bugs.kde.org/show_bug.cgi?id=362226 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com --- Comment #1 from Simone Gaiarin --- I second this. My index is 8 GB, because any time I add some temporary folder this is indexed and then never forgotten. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 312919] high CPU usage for copying notification
https://bugs.kde.org/show_bug.cgi?id=312919 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend
https://bugs.kde.org/show_bug.cgi?id=360058 --- Comment #17 from Simone Gaiarin --- I confirm the behaviour described in comment 15. I'm experiencing exactly the same. Sergio explained it in a much more clear way than me. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371131] Multi monitor configuration not respected
https://bugs.kde.org/show_bug.cgi?id=371131 --- Comment #3 from Simone Gaiarin --- After reporting this bug I did some more extensive tests, and I've isolated two problems: Laptop lid configuration lost: https://bugs.kde.org/show_bug.cgi?id=371681 KScreen doesn't recognise the new configuration after waking up notebook: https://bugs.kde.org/show_bug.cgi?id=360058 I think we can close this bug and continue the conversation in the other two bug pages that are more specific. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348231] Bring window to current activity when selected
https://bugs.kde.org/show_bug.cgi?id=348231 --- Comment #8 from Simone Gaiarin --- So the behaviour is a little inconsistent among applications. When I tie the following applications to a specific activity and I open them: - VLC opens in the target activity and the current activity is NOT switched - kate, atom and others opens in the target activity and the current activity is switched to the target activity I agree with you that a popup telling the user what's going on would be useful, but also the behaviour should be somehow consistent among applications. As it is now seems a little random. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #102 from Simone Gaiarin --- After a superficial test, copying files over the network (that was usually killing the CPU) the problem seems not be present in Plasma 5.8.4. But since the problem kicks in randomly this test is not enough to say it's solved. On Tue, Nov 29, 2016 at 4:44 PM Jos van den Oever wrote: > https://bugs.kde.org/show_bug.cgi?id=356479 > > --- Comment #101 from Jos van den Oever --- > For me it's fixed since Plasma 5.8. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 373110] New: Screens configuration is not changed when connecting/disconnecting external monitors
https://bugs.kde.org/show_bug.cgi?id=373110 Bug ID: 373110 Summary: Screens configuration is not changed when connecting/disconnecting external monitors Product: KScreen Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: simg...@gmail.com Target Milestone: --- Since few days (probably from when I updated to Plasma 5.8.4) when I undock/dock the notebook the screen configuration is not changed at all. kscreen.log is not filled. It seems that KScreen is doing nothing. Example: Undock notebook: - In KCM I can still see 3 screens - Panel not moved - Mouse can exit the notebook screen Redock notebook - External screens not activated I need to reboot every time I dock/undock. Sometimes docking causes the crash of X, showing the login window afterwards. How can I debug this and provide more information? The kscreen.log is not populated after I undock, so I don't think is so useful. System: Manjaro Kernel: 4.8.9 Xorg-server: 1.18.4 KScreen: 5.8.4 Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller Display Server: X.Org 1.18.4 driver: intel Resolution: 1920x1080@60.02hz, 1920x1200@59.95hz, 1680x1050@59.95hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 13.0.1 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 373118] New: Cantor crashes on close
https://bugs.kde.org/show_bug.cgi?id=373118 Bug ID: 373118 Summary: Cantor crashes on close Product: cantor Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: fil...@kde.org Reporter: simg...@gmail.com CC: alexanderrie...@gmail.com Target Milestone: --- Application: cantor (16.08.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.9-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Running the python 3 backend. Clicking the X button to close the app makes the app crash. drkonqi suggest me to send the bug report. The crash can be reproduced every time. -- Backtrace: Application: Cantor (cantor), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9b29d4f7c0 (LWP 6260))] Thread 2 (Thread 0x7f9b0f49c700 (LWP 6262)): #0 0x7f9b20c697a7 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f9b20c6bc2b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f9b20c6c6ab in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9b20c6c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f9b26a9a72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9b26a4423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9b268670f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9b23091e55 in () at /usr/lib/libQt5DBus.so.5 #8 0x7f9b2686bd78 in () at /usr/lib/libQt5Core.so.5 #9 0x7f9b224ea454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f9b25f6a7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f9b29d4f7c0 (LWP 6260)): [KCrash Handler] #6 0x in () #7 0x7f9b26a719ce in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #8 0x7f9b29391655 in KParts::Part::setStatusBarText(QString const&) () at /usr/lib/libKF5Parts.so.5 #9 0x7f9afffcbb3b in () at /usr/lib/qt/plugins/libcantorpart.so #10 0x7f9b00010d83 in () at /usr/lib/qt/plugins/libcantorpart.so #11 0x7f9b26a71659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7f9b2981587e in Cantor::Session::statusChanged(Cantor::Session::Status) () at /usr/lib/libcantorlibs.so.16 #13 0x7f9b024e43cd in PythonSession::logout() () at /usr/lib/libcantor_pythonbackend.so #14 0x7f9afffdb469 in () at /usr/lib/qt/plugins/libcantorpart.so #15 0x7f9afffdb529 in () at /usr/lib/qt/plugins/libcantorpart.so #16 0x7f9b26a6fdc1 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #17 0x7f9b2776889b in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #18 0x7f9b27768b89 in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #19 0x7f9b26a6fdc1 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #20 0x7f9b2776889b in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #21 0x7f9b278b5299 in QStackedWidget::~QStackedWidget() () at /usr/lib/libQt5Widgets.so.5 #22 0x7f9b26a6fdc1 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #23 0x7f9b2776889b in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #24 0x7f9b278c1be9 in QTabWidget::~QTabWidget() () at /usr/lib/libQt5Widgets.so.5 #25 0x7f9b26a6fdc1 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #26 0x7f9b2776889b in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #27 0x7f9b28e0832e in KMainWindow::~KMainWindow() () at /usr/lib/libKF5XmlGui.so.5 #28 0x0040da22 in () #29 0x7f9b26a724f0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #30 0x7f9b2776d0eb in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #31 0x7f9b2786b48b in QMainWindow::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #32 0x7f9b28e0ae6a in KMainWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #33 0x7f9b28e5c875 in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #34 0x7f9b27725e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #35 0x7f9b2772d581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #36 0x7f9b26a45de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #37 0x7f9b26a4856d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #38 0x7f9b26a9a303 in () at /usr/lib/libQt5Core.so.5 #39 0x7f9b20c6c587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #40 0x7f9b20c6c7f0 in () at /usr/lib/libglib-2.0.so.0 #41 0x7f9b20c6c
[cantor] [Bug 356103] Python 3 backend is not functional
https://bugs.kde.org/show_bug.cgi?id=356103
--- Comment #10 from Simone Gaiarin ---
Seems to work now. Version: 16.08.3
I get some weird output though sometimes, I don't know if it's normal.
Steps:
a = 1 OK
b = 2
{'errorPythonBackend': , '__spec__': None, 'a': 1, '__doc__': None,
'__loader__': , 'scipy': , 'matplotlib': , 'CatchOutPythonBackend': ,
'outputPythonBackend': , '__builtins__': , '__package__': None, 'numpy': ,
'sys': , '__name__': '__main__', 'b': 2}
c = a + b OK
import numpy as np OK
dd = np.array([1,2,3]) OK
Reevaluate b = 2 then it's OK
That output appears only if I do Evaluate Worksheet, while with evaluate entry
it's fine.
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 370137] When second screen is connected the session restarts
https://bugs.kde.org/show_bug.cgi?id=370137 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com --- Comment #2 from Simone Gaiarin --- Same problem here since 1-2 weeks. Tried with 4.8 and 5.7 kernel and still happens. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370137] When second screen is connected the session restarts
https://bugs.kde.org/show_bug.cgi?id=370137 --- Comment #4 from Simone Gaiarin --- Yes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370137] When second screen is connected the session restarts
https://bugs.kde.org/show_bug.cgi?id=370137 --- Comment #5 from Simone Gaiarin --- It's happening since few days to me, so it may be Plasma 5.8.4 or some kernel, Xorg update. I see that others had problem recently: https://bbs.archlinux.org/viewtopic.php?pid=1670832#p1670832 but I'm not using Nvidia and also with a 4.7 series kernel the problem persists, so may be something else. This other bug appeared at the same time, so they may be related: https://bugs.kde.org/show_bug.cgi?id=373110 System: Manjaro Kernel: 4.8.9 or 4.7.10 Xorg-server: 1.18.4 KScreen: 5.8.4 Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller Display Server: X.Org 1.18.4 driver: intel Resolution: 1920x1080@60.02hz, 1920x1200@59.95hz, 1680x1050@59.95hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 13.0.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370648] SDDM Breeze theme hardly usable on multiscreen set up with different DPIs
https://bugs.kde.org/show_bug.cgi?id=370648 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com --- Comment #1 from Simone Gaiarin --- I can confirm this. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369158] Breeze sddm theme broken on dual monitor setup (no cursor)
https://bugs.kde.org/show_bug.cgi?id=369158 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com --- Comment #1 from Simone Gaiarin --- I also experience the lack of cursor. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464585] Visually mark hardlinks
https://bugs.kde.org/show_bug.cgi?id=464585 Simone Gaiarin changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Simone Gaiarin --- My personal preference: - text: normal because a hard link is a normal file at the end - icon: little number mark Regarding the text. I would exclude italic because it can mislead the user in thinking it is a symlink. I would exclude semi-bold because the icon becomes too flashy respect the others. -- You are receiving this mail because: You are watching all bug changes.
