Re: Is Kicker's search box fixed?
On dinsdag 19 juli 2016 17:52:54 CEST Borden Rhodes wrote: > Am I to infer, then, that everything's working in 5.23.0 of libkf5plasma5? There have been several bug reports which resulted from mixed framework libraries from version 5.22 and 5.23. Getting them all on 5.23 fixed that. See https://lists.debian.org/debian-kde/2016/07/msg00065.html for details. signature.asc Description: This is a digitally signed message part.
Re: Is Kicker's search box fixed?
On Tuesday, July 19, 2016 05:52:54 PM Borden Rhodes wrote: > > Thanks, > > > > > On Tuesday, July 19, 2016 03:08:29 AM Borden Rhodes wrote: > >> Good morning, > >> > >> Around the time of the KF5 upgrade on Stretch, typing into Kicker's > >> search box krashed Plasma. I notice that it doesn't do that anymore, > >> but the search box also doesn't generate any search results. Is it > >> working for anybody else and, if so, what do I have to > >> install/clear/configure to get it working again? > >> > >> With thanks, > On 19 July 2016 at 14:53, Tim Folger wrote: > > I had the same problem after upgrading on Stretch. There is a workaround: > > Temporarily replace "testing" with "unstable" in your > > /etc/apt/sources.list. Then do apt-get update, followed by: > > apt-get install libkf5plasma5 > > This fixed the search box issue for me, and also fixed a problem with > > right- clicks on the desktop and taskbar not working. > > Finally, remember to change your /etc/apt/sources.list back to testing or > > stretch, followed by an apt-get update. > > > > Tim > Thank you for the responses. Am I to infer, then, that everything's > working in 5.23.0 of libkf5plasma5? If so, I'll wait for it to come > down the pike and retest then. I don't know if everything's working in 5.23.0. Maybe someone who is better informed will know.
Re: Is Kicker's search box fixed?
Thank you for the responses. Am I to infer, then, that everything's working in 5.23.0 of libkf5plasma5? If so, I'll wait for it to come down the pike and retest then. Thanks, On 19 July 2016 at 14:53, Tim Folger wrote: > I had the same problem after upgrading on Stretch. There is a workaround: > Temporarily replace "testing" with "unstable" in your /etc/apt/sources.list. > Then do apt-get update, followed by: > apt-get install libkf5plasma5 > This fixed the search box issue for me, and also fixed a problem with right- > clicks on the desktop and taskbar not working. > Finally, remember to change your /etc/apt/sources.list back to testing or > stretch, followed by an apt-get update. > > Tim > On Tuesday, July 19, 2016 03:08:29 AM Borden Rhodes wrote: >> Good morning, >> >> Around the time of the KF5 upgrade on Stretch, typing into Kicker's >> search box krashed Plasma. I notice that it doesn't do that anymore, >> but the search box also doesn't generate any search results. Is it >> working for anybody else and, if so, what do I have to >> install/clear/configure to get it working again? >> >> With thanks, >
Cloud Storage Manager
I've been trying to find a reasonable way to get Google Drive mounted onto my machine and not have it be horrible. After a couple searches I found some references to something in KDE called "Cloud Storage Manager" and "Cloud Storage Service". Does this simply not exist in Debian? Thanks. -- Rubin ru...@starset.net
Re: Is Kicker's search box fixed?
I had the same problem after upgrading on Stretch. There is a workaround: Temporarily replace "testing" with "unstable" in your /etc/apt/sources.list. Then do apt-get update, followed by: apt-get install libkf5plasma5 This fixed the search box issue for me, and also fixed a problem with right- clicks on the desktop and taskbar not working. Finally, remember to change your /etc/apt/sources.list back to testing or stretch, followed by an apt-get update. Tim On Tuesday, July 19, 2016 03:08:29 AM Borden Rhodes wrote: > Good morning, > > Around the time of the KF5 upgrade on Stretch, typing into Kicker's > search box krashed Plasma. I notice that it doesn't do that anymore, > but the search box also doesn't generate any search results. Is it > working for anybody else and, if so, what do I have to > install/clear/configure to get it working again? > > With thanks,
Re: KDEPIM ready to be more broadly tested
On Tuesday, July 19, 2016 4:38:58 PM CEST Sandro Knauß wrote: > looks like: https://bugs.kde.org/show_bug.cgi?id=362958 Indeed. Thanks for the pointer. -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Re: KDEPIM ready to be more broadly tested
Moin, > Calendar buttons are gone: I used to have a set of button to manage meeting > when I got an invite from outlook users (i.e. a mail with an ics > attachment). I cannot view the content of the calendar invite. looks like: https://bugs.kde.org/show_bug.cgi?id=362958 regards, sandro signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
Am Dienstag 19 Juli 2016, 11:14:30 schrieb Christian Hilberg: > Am Dienstag 19 Juli 2016, 11:01:21 schrieb Christian Hilberg: > > [...] > > While syncing the IMAP folders, the process got stuck at 100% at one > > folder[...] > > Trying to resolve this now... > > Funny, oftentimes, Akonadiconsole shows a several thousand percent > of "completeness" for the IMAP resource when trying to "Synchronize all", > before the connection to the Akonadi server fails. This happens for > seemingly random folders, now this one, then that one. > > The Akonadi debugger information view shows a message which translates > to "Connection to the akonadi service cannot be established". > > Many of the folders are biggish, some thousand messages. Maybe a timeout > of some sort? Reduced the guilty folder's size, still: ... log_imapresource: Detected inconsistency in local cache, we're missing some messages. Server: 547 Local: 500 log_imapresource: Refetching complete mailbox. QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x1e64810) "kontact_6660_EbGSKI" false Database "akonadi" opened using driver "QMYSQL" New notification bus: "/subscriber/kontact_6660_EbGSKI" akonadicore_log: Invalid command, the world is going to end! QIODevice::read (QLocalSocket): device not open akonadicore_log: "Cannot connect to the Akonadi service." Shutting down "akonadi_imap_resource_0" ... Database "akonadi" opened using driver "QMYSQL" Invalid command: no such handler for Transaction akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Error during ItemSync: "Cannot connect to the Akonadi service." Shutting down "0x2126a20" ... ... The IMAP resource seems to crash need to restart Akonadi, otherwise nothing will work with this resource after the logged fail. Looks like [0], though it is claimed to have been fixed in 16.04.3 ... Best, Christian [0] https://bugs.kde.org/show_bug.cgi?id=364045 -- kernel concepts GmbH Tel: +49-271-771091-11 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ Geschäftsführer: Nils Faerber, Ole Reinhardt HR Siegen, HR B 9613
Re: KDEPIM ready to be more broadly tested
On Sunday, July 17, 2016 8:18:35 PM CEST Lisandro Damián Nicanor Pérez Meyer wrote: > If you run unstable but have refrained from installing the kdepim packages > up to now, we would appreciate it if you go ahead and install them now, > reporting any issues that you may find. Calendar buttons are gone: I used to have a set of button to manage meeting when I got an invite from outlook users (i.e. a mail with an ics attachment). I cannot view the content of the calendar invite. As a work-around, I right click on the ics part (in message structure window), open it with korganization and merge it in my calendat. Unfortunately, the meeting is set using local time zone and does not take into account the time zone of the organizer of the meeting. So some meeting are off by a few hours. Thanks for working on kdepim :-) All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Re: KDEPIM ready to be more broadly tested
Am Dienstag 19 Juli 2016, 11:01:21 schrieb Christian Hilberg: > [...] > While syncing the IMAP folders, the process got stuck at 100% at one > folder[...] > Trying to resolve this now... Funny, oftentimes, Akonadiconsole shows a several thousand percent of "completeness" for the IMAP resource when trying to "Synchronize all", before the connection to the Akonadi server fails. This happens for seemingly random folders, now this one, then that one. The Akonadi debugger information view shows a message which translates to "Connection to the akonadi service cannot be established". Many of the folders are biggish, some thousand messages. Maybe a timeout of some sort? Regards, Christian -- kernel concepts GmbH Tel: +49-271-771091-11 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ Geschäftsführer: Nils Faerber, Ole Reinhardt HR Siegen, HR B 9613
Re: KDEPIM ready to be more broadly tested
Am Montag 18 Juli 2016, 09:00:45 schrieb Lisandro Damián Nicanor Pérez Meyer: > On domingo, 17 de julio de 2016 8:18:35 P. M. ART Lisandro Damián Nicanor > Pérez Meyer wrote: > > As was posted [a couple of weeks ago], the latest version of KDE > > This is of course KDEPIM :) Of *course*. :-) Updated my Sid box today, got KDEPIM and libs 16.04.3. Wanted to check whether my favourite issue [0] had been fixed. =) Created a fresh user on the box, logged in for the first time into Plasma5, and started Kontact. MySQL refused to start up properly (while tests 1..4 passed): ---8<--- Test 5: ERROR MySQL server log contains errors. Details: The MySQL server error log file '/home/chris/.local/share/akonadi/db_data/mysql.err' contains errors. File content of '/home/chris/.local/share/akonadi/db_data/mysql.err': 160719 9:09:39 [Note] Plugin 'FEDERATED' is disabled. 160719 9:09:39 InnoDB: The InnoDB memory heap is disabled 160719 9:09:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160719 9:09:39 InnoDB: Compressed tables use zlib 1.2.8 160719 9:09:39 InnoDB: Using Linux native AIO 160719 9:09:39 InnoDB: Initializing buffer pool, size = 80.0M 160719 9:09:39 InnoDB: Completed initialization of buffer pool 160719 9:09:39 InnoDB: highest supported file format is Barracuda. 160719 9:09:39 InnoDB: Waiting for the background threads to start 160719 9:09:40 InnoDB: 5.5.46 started; log sequence number 1622641 160719 9:09:40 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 160719 9:09:40 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 160719 9:09:40 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure 160719 9:09:40 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.46-0+deb8u1' socket: '/tmp/akonadi-chris.raoZs2/mysql.socket' port: 0 (Debian) 160719 9:09:40 [Note] /usr/sbin/mysqld: Normal shutdown 160719 9:09:40 InnoDB: Starting shutdown... 160719 9:09:42 InnoDB: Shutdown completed; log sequence number 1622651 160719 9:09:42 [Note] /usr/sbin/mysqld: Shutdown complete ---8<--- >From what I found in the reports, this looks like [1]. I have checked that * there is enough free disk space (~7GB free) * the Akonadi directory structure under ~/.local/share/akonadi has the right permissions (this is not a migrated DB, but freshly created, as noted above) So I thought this might be a wrong default setting with the table types, as Akonadi requires InnoDB, as noted in [1]. But then, the log above shows that InnoDB is used. As I am running the tests inside a virtual box, I assumed I might have had too little memory reserved. Cleared the users' home, increased virtual machine mem from 4GB to 8GB and started over. Alas, same thing happened. A migration might eat up truckloads of mem, but a fresh install with no IMAP account yet -- just the MySQL DB -- I think 8GB of mem should suffice. After quitting the email account wizard and Kontact alltogether, and starting Kontact anew, no error dialog was shown. However, 'akonadictl status' keeps telling that the service is down. Trying the hint provided in [2] (deleting the db_data Akonad
Is Kicker's search box fixed?
Good morning, Around the time of the KF5 upgrade on Stretch, typing into Kicker's search box krashed Plasma. I notice that it doesn't do that anymore, but the search box also doesn't generate any search results. Is it working for anybody else and, if so, what do I have to install/clear/configure to get it working again? With thanks,
