[kdeconnect] [Bug 394513] KDEConnect on Android connecting even on mobile network
https://bugs.kde.org/show_bug.cgi?id=394513 David Heidelberg changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from David Heidelberg --- Haven't used KDE Connect in two years, no idea if the problem occurs. Someone using it should check on Android firewall. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394513] KDEConnect on Android connecting even on mobile network
https://bugs.kde.org/show_bug.cgi?id=394513 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Summary|KDEConnect on Android |KDEConnect on Android |connecting even on LTE |connecting even on mobile ||network -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394513] New: KDEConnect on Android connecting even on LTE
https://bugs.kde.org/show_bug.cgi?id=394513 Bug ID: 394513 Summary: KDEConnect on Android connecting even on LTE Product: kdeconnect Version: 1.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: da...@ixit.cz Target Milestone: --- What happening: when I disconnect from WiFi and switch to mobile connection, kdeconnect tries looking for desktop. What should happen: after disconnecting from WiFi kdeconnect should suspend itself and save battery until reconnected again. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added CC|da...@ixit.cz | -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 379434] New: Wayland: Open File dialog unable to handle "Enter" button
https://bugs.kde.org/show_bug.cgi?id=379434 Bug ID: 379434 Summary: Wayland: Open File dialog unable to handle "Enter" button Product: kwayland-integration Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: da...@ixit.cz Target Milestone: --- Hello, running latest KDE Neon developer dist. and when I: 1) run Chromium 2) push some "Open file" button on website 3) write file into textbox in KDE Open File dialog, push enter 4) it got accepted and then window reappears, until I select file with mouse or click on "OK" button. I'm guessing, problem should be in KDE Open File dialog. This behaviour worked on X11 well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)
https://bugs.kde.org/show_bug.cgi?id=371494 --- Comment #3 from David Heidelberg <da...@ixit.cz> --- Would be nice > http://www.omgubuntu.co.uk/2017/02/gnome-night-light-blue-light-filter-linux -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373668] Lock Screen should warn when the keyboard status is not default (layout/capslock)
https://bugs.kde.org/show_bug.cgi?id=373668 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added CC||da...@ixit.cz --- Comment #17 from David Heidelberg <da...@ixit.cz> --- guys, I'd like to add my 2 cents... I don't think that _keyboard layout_ indicator is visible on _lockscreen_. In Czech Republic is common to use US and CS layout, so entering password is always guess which last layout I used... :( Please add indicator in case there is more than one keyboard layout. (not saying it's great to see battery percentage, but seeing layout would be even better :D ) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373435] New: Keep Eyes Fresh: Redshift integration into KDE
https://bugs.kde.org/show_bug.cgi?id=373435 Bug ID: 373435 Summary: Keep Eyes Fresh: Redshift integration into KDE Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: da...@ixit.cz Target Milestone: --- Why think about integrating Redshift [1] into KDE? Because KDE could provide more pleasant experience by optimizing screen colors to match day time, to reduce eyes strain. Very nicely it's very nicely presented here [2]. How could it be done? I would suggest to integrate Redshift directly into settings and allow users set day & night colors. Also offer possibility to read current location (or enter it manually) to figure out, when sun goes down. Also allow possibility to disable Redshift and return original gamma and red value, in case when it's manipulated with photographic material (webdesign etc.) or battery is at critical level. Inspiration could be taken from CyanogenMod 12+ systems, where this feature is presented as LiveDisplay. Also when considering this feature, please try Redshift or some similar program at least 5 minutes, before eyes get used to different color. After while you'll see eyes adapt to new default "white" and calibrate accordingly. [1] http://jonls.dk/redshift/ [2] https://play.google.com/store/apps/details?id=com.urbandroid.lux=en -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372890] default LVDS is left without widgets
https://bugs.kde.org/show_bug.cgi?id=372890 --- Comment #2 from David Heidelberg <da...@ixit.cz> --- When I add default panel on LVDS screen is also present on DVI output when connected in dockstation. Can be this logic avoided? Solution preferably use LVDS setup from screen which include at least >= 1 widgets. Screen which has only background can be ignored when different screen is used. Not sure how to manage it in plasmashell logic, maybe use PRIMARY display widgets when only LVDS is used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372890] default LVDS is left without widgets
https://bugs.kde.org/show_bug.cgi?id=372890 --- Comment #1 from David Heidelberg <da...@ixit.cz> --- Also in case there is someone workin on plasmashell in Prague, Czech Republic, I'm willing to help with improving multi-monitor setup.. xrandr in dock: $ xrandr Screen 0: minimum 320 x 200, current 2160 x 1920, maximum 8192 x 8192 LVDS-1 connected (normal left inverted right x axis y axis) 1600x900 60.00 + 1440x900 59.89 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 connected primary 1080x1920+0+0 left (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 60.00*+ 1680x1050 59.88 1600x900 60.00 1280x1024 60.02 1440x900 59.90 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 720x400 70.08 DP-2 connected 1080x1920+1080+0 right (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 60.00*+ 1680x1050 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 720x400 70.08 DP-3 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372890] New: default LVDS is left without widgets
https://bugs.kde.org/show_bug.cgi?id=372890 Bug ID: 372890 Summary: default LVDS is left without widgets Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: da...@ixit.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 102432 --> https://bugs.kde.org/attachment.cgi?id=102432=edit plasma-org.kde.plasma.desktop-appletsrc Setup: LENOVO T430, Intel 3000 HD Dock DVI: 1080x1920 Dock DP: 1080x1920 LVDS: 1600x900 (disabled in Dock mode, laptop support only 2 simu outputs) When undocking, I sadly get only empty screen with running plasmashell. This means, there is no popups control, no NetworkManager control (sadly thanks to different bug, Wifis marked "available for all users" won't get automatically connected) $ plasmashell No metadata file in the package, expected it at: "/home/okias/Pictures/" No metadata file in the package, expected it at: "/home/okias/Pictures/" No metadata file in the package, expected it at: "/home/okias/Pictures/" Plasma Shell startup completed After removal of ".config/plasma-org.kde.plasma.desktop-appletsrc" it starts normally. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 260799] calendar lost data entered into akonadi-google
https://bugs.kde.org/show_bug.cgi?id=260799 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from David Heidelberg <da...@ixit.cz> --- Great idea... closing, no idea if it works or not. Not using google calendar for long time. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 269497] sftp: dolphin sucessfully copied 306 files, but files are not where should be!
https://bugs.kde.org/show_bug.cgi?id=269497 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from David Heidelberg <da...@ixit.cz> --- No idea, using KF5 these days, not retested... probably already OK... -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 222059] show red color when volume gain is over +0dB
https://bugs.kde.org/show_bug.cgi?id=222059 --- Comment #2 from David Heidelberg <da...@ixit.cz> --- would be nice to have it... (after 6 years).. -- You are receiving this mail because: You are watching all bug changes.
[kdm] [Bug 319076] kdm systemd file
https://bugs.kde.org/show_bug.cgi?id=319076 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from David Heidelberg <da...@ixit.cz> --- I guess systemd integration advanced a lot, so it's already fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 191909] Plasma Configuration in XML
https://bugs.kde.org/show_bug.cgi?id=191909 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Heidelberg <da...@ixit.cz> --- Plasma 5, still seeing ugly configuration files, but hey, I don't care much ;-) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 194656] Akregator - "detach tab"
https://bugs.kde.org/show_bug.cgi?id=194656 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 175202] Integration amarok widgets with plasma
https://bugs.kde.org/show_bug.cgi?id=175202 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 268782] okteta replace: eat 100% of one core
https://bugs.kde.org/show_bug.cgi?id=268782 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 276994] incorrect resize behaviour with kxrandr
https://bugs.kde.org/show_bug.cgi?id=276994 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370711] wallpaper on second monitor is always set to default
https://bugs.kde.org/show_bug.cgi?id=370711 --- Comment #5 from David Heidelberg <da...@ixit.cz> --- Addional information: when is DP monitor (with wallpaper) shutdown, xrandr reconfigure screen to only ONE display. Wallpaper is shown. When is "reconnected" DP monitor, correct wallpaper is still present on VGA output. I hope it helps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370711] wallpaper on second monitor is always set to default
https://bugs.kde.org/show_bug.cgi?id=370711 --- Comment #4 from David Heidelberg <da...@ixit.cz> --- Created attachment 101573 --> https://bugs.kde.org/attachment.cgi?id=101573=edit plasmashellrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370711] wallpaper on second monitor is always set to default
https://bugs.kde.org/show_bug.cgi?id=370711 --- Comment #3 from David Heidelberg <da...@ixit.cz> --- Created attachment 101572 --> https://bugs.kde.org/attachment.cgi?id=101572=edit plasmarc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370711] wallpaper on second monitor is always set to default
https://bugs.kde.org/show_bug.cgi?id=370711 --- Comment #2 from David Heidelberg <da...@ixit.cz> --- Created attachment 101571 --> https://bugs.kde.org/attachment.cgi?id=101571=edit plasma1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370711] New: wallpaper on second monitor is always set to default
https://bugs.kde.org/show_bug.cgi?id=370711 Bug ID: 370711 Summary: wallpaper on second monitor is always set to default Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: da...@ixit.cz CC: plasma-b...@kde.org It seems that Plasma is not able to remember second screen wallpaper and always set default (after login) Reproducible: Always KDE Neon - Developer version -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 368736] New: After clicking on "Update" button discovery crashes
https://bugs.kde.org/show_bug.cgi?id=368736 Bug ID: 368736 Summary: After clicking on "Update" button discovery crashes Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: da...@ixit.cz Application: plasma-discover (5.7.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.0-040800rc5-generic x86_64 Distribution: KDE neon User Edition 5.7 -- Information about the crash: - What I was doing when the application crashed: clicking Update button This seems to be that "1 package to update": # apt upgrade Načítají se seznamy balíků… Hotovo Vytváří se strom závislostí Načítají se stavové informace… Hotovo Entering ResolveByKeepzace… 10% Propočítává se aktualizace… Hotovo Následující balíky budou aktualizovány: neon-desktop 1 aktualizováno, 0 nově instalováno, 0 k odstranění a 0 neaktualizováno. Nutno stáhnout 3 170 B archivů. Po této operaci bude na disku použito dalších 0 B. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd025c598c0 (LWP 29532))] Thread 4 (Thread 0x7fd00b2b4700 (LWP 29535)): #0 0x7fd01e2b630c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd01e2b64ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd02318823b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd023132cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd022f57fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0238de675 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fd022f5cb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd01ff116fa in start_thread (arg=0x7fd00b2b4700) at pthread_create.c:333 #8 0x7fd022560b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fd00c4c5700 (LWP 29534)): #0 0x7fd01e2faae0 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd01e2b5c09 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd01e2b6317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd01e2b64ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd02318823b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd023132cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd022f57fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd0207a87a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fd022f5cb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd01ff116fa in start_thread (arg=0x7fd00c4c5700) at pthread_create.c:333 #10 0x7fd022560b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fd014bed700 (LWP 29533)): #0 0x7fd022554e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd01de4bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fd01de4d8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fd017144a39 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fd022f5cb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd01ff116fa in start_thread (arg=0x7fd014bed700) at pthread_create.c:333 #6 0x7fd022560b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd025c598c0 (LWP 29532)): [KCrash Handler] #6 0x7fd023b0f822 in QWindow::setGeometry(QRect const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x0040d1cf in DiscoverMainWindow::integrateObject (this=0x1253b70, object=0x0) at /workspace/build/discover/DiscoverMainWindow.cpp:194 #8 0x7fd02315fe76 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd0238cbf54 in QQmlApplicationEngine::objectCreated(QObject*, QUrl const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fd0238ccb89 in QQmlApplicationEnginePrivate::_q_finishLoad(QObject*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fd0238cce52 in QQmlApplicationEnginePrivate::startLoad(QUrl const&, QByteArray const&, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fd0238cce8d in QQmlApplicationEngine::load(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x0040ccd2 in
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 David Heidelberg <da...@ixit.cz> changed: What|Removed |Added CC||da...@ixit.cz --- Comment #3 from David Heidelberg <da...@ixit.cz> --- ping, have nextCloud* News support would be nice! * or formely ownCloud - same API -- You are receiving this mail because: You are watching all bug changes.
