[03:57] hi,... looking for help, kmail crash, and every time crash.. please help here is my terminal print. https://pastebin.com/FkCnEneK [05:07] kmail cant open, Need help.. [05:08] it was just working, then suddnly crash, and since then its keep crashing when ever I try to open it. [05:13] DShreyas was added by: DShreyas [05:18] (Photo, 882x617) https://irc-attachments.kde.org/SIMUROVB/file_3793.jpg This is my System info. Krunner crashes when I type something in the krunner. [05:19] (Photo, 927x105) https://irc-attachments.kde.org/BWkDNTFk/file_3795.jpg and if I try to to run it from konsole after the crash, the above error appears [05:19] can anybody help me to sort out the problem [05:20] Anyone send files to your system via Bluetooth from Android? [05:21] It's been years but it never seems to work [05:29] jaafar: bluetooth files transfer works fine here (kubuntu 17.10...) [05:31] DarinMiller: thanks so much for responding... Can you walk me through it? Android displays a PIN, kubuntu does not and seems to think it is connected. Android shows failure message. [05:31] I'm also 17.10 [05:32] Clickon the bt icon near the clock. [05:32] okay [05:32] Then click on settings icon in the upper right of the popup window... [05:33] okay, I've seen that one a lot lately :) [05:33] it's up [05:33] My Android will appear here as "connected" [05:33] though Android itself thinks it failed [05:33] sry if I am repeating what you have tried many times... but just covering the bases... [05:33] at the moment, not present. What's next? [05:34] no worries at all, makes sense [05:35] On the Adapters tab, ensure the Powered box is checked and set visibility to Always Visible (for now). [05:35] On the Advanced Setting tab, ensure Enable Bluetooth integration is checked. [05:36] all as specified [05:37] Ok, back on the Devices tab, click the plus [+] button. [05:38] * DarinMiller funny, I can see my neighbors soundbar.... I should play some holiday music for him.... [05:38] :) [05:38] OK my Android device is visible [05:39] on your phone, tap and hold the bt icon to bring up the bt connections [05:39] On the PC screen, select your phone and click the next button. [05:39] hm, I have the "bluetooth settings" open, if that's what you mean [05:40] on Android [05:40] And on my PC I have a "Connect" but no "Next" [05:40] Does the phone show the spinning search option somewhere on the screen? [05:41] spinning search option... no [05:41] it does list my PC though [05:41] This is the "bluetooth settings" menu, I guess, which does list visible bt devices [05:41] Find the bt screen on the phone where you have the scan option for paring devices... [05:41] I know if I click on my PC name it will attempt to connect [05:41] which fails [05:42] DarinMiller this screen does scan when I first bring it up [05:42] Is it enough that it shows my PC name or should I look for some other menu? [05:42] I only iniate connect from the PC side, and confirm on the phone side. [05:42] because it's there [05:42] DarinMiller: shall I try to initiate from the PC side now? [05:42] by clicking "Connect" [05:42] yes. [05:43] OK that causes my Android to display a PIN [05:43] shall I click "pair" on Android? [05:43] yes, accept on the phone... [05:43] Android displays "pairing" [05:44] then confirm on the pc side. [05:44] when you say "confirm" on the PC side, I'm not sure what you mean [05:44] it seems to think it is connected [05:44] no PIN was displayed on the PC [05:45] On mine, I confirm the code on the phone, then the PC wizard want confimation that the pin was correct. [05:45] OK now Android says "Couldn't pair with xxx because of an incorrect PIN or passkey" [05:45] which is what usually happens [05:45] I will try the process again without pausing [05:45] Ensure to delete your device from the list and try again. [05:46] OK will try that [05:46] Yes, time windows are very small. Do not let your phone screen blank out or you may miss the window. [05:46] OK I have removed Android from the list of known devices and will try again [05:46] very good. [05:47] Same problem [05:47] Android displays PIN, I say connect, long pause, error message from Android [05:48] OK, I have the following BT packages installed: [05:48] maybe I need dpkg-reconfigure :) [05:48] https://paste.ubuntu.com/26161809/ [05:49] check your list with this command: apt list *blue* | grep installed [05:51] DarinMiller: I checked it by attempting to install all of those :) no changes made [05:51] so I think they must be there [05:52] actually I have a lot more bluez modules than you do [05:52] Have you connected any other bt devices such as a speaker? [05:52] I believe so [05:53] btw this is a problem I've seen for years [05:53] How many device connection options are listed on the PC? [05:53] something like 20+ [05:53] including somebody's MacBook Pro [05:53] https://pastebin.com/Ef1kjWxP Kmail keep crahing, any idea how to fix it ? [05:53] and a bunch of MAC addresses [05:53] I have had BT issues with my PC's over the years, but in the last year, most of the BT issues have been fixed.. [05:54] I haven't had any luck sending files from my Android devices... several generations of them, and many versions of kubuntu [05:54] What verion of Android? [05:54] I just assumed it doesn't work [05:55] 7.1.2 [05:55] but this has been true for some time [05:55] starting with a Samsung Infuse maybe 3, 4 years ago [05:55] I am running 7.0 here. [05:55] S7. [05:55] what could explain Kubuntu failing to display the PIN dialog? [05:56] that's what it's supposed to do, right? [05:56] mozammel: Sry, I don't use kmail, so I can't help much. [05:56] just a sec, I will delete mine again, and let you know.. [05:58] OK the pin popped up on the PC screen and on the phone at the same time. I confirmed on the phone 1st, then on the PC and everything worked fine. [05:58] Testing on 2nd PC.... [05:59] 2nd PC connected and paired just fine. By chance is your phone paired to a set of headphones another device in the house? [06:00] nope [06:00] If so, disconnect that device and start the connection process again. Current BT devices can only connect to one device at a time. [06:01] I am going to test with a bluetooth speaker now [06:02] run this command: sudo lshw > t.txt && kate t.txt & [06:02] then in kate search for "blue" [06:03] what brand of BT adapter is listed? [06:03] DarinMiller: sorry should I try the speaker or no... [06:03] you had asked previously [06:04] yes, try the speaker [06:04] also break up the previous command: sudo lshw > t.txt [06:04] then: kate t.txt [06:08] Does the speaker work with either PC or the phone? [06:09] OK speaker works with PC [06:09] sorry that took a bit of audio configuration [06:09] np. :) [06:09] it is paired and can output audio from Spotify [06:09] I will switch to your other question now [06:10] very good. [06:11] DarinMiller: I assume this is the one that interests you: http://paste.ubuntu.com/26161874/ [06:13] Android can pair with the speaker too [06:15] that adapter is exactly what I have in the 2nd PC I tested. [06:16] I presume some software issue [06:17] It's like some part of the negotiation is busted [06:17] On the PC side, try clearning all BT devices from the list. on the phone side, clear the PC if its listed. Then try again. [06:17] DarinMiller: what do you think about me removing and reinstalling some packages [06:17] or some other kind of reconfiguration? [06:17] or deleting files out of my ~/.config or ~/.kde [06:17] etc. [06:18] I have been upgrading for a long time instead of clean installing [06:18] you could use the sudo apt purge [06:18] then reinstall. [06:18] purge should clear any of the config files. [06:20] Here's the weird thing: the PC side thinks it is connected [06:20] despite never displaying the PIN or whatever [06:20] it's the Android side that thinks it failed [06:21] blowing away all packages matching *blue* :) [06:21] A system restart is necessary [06:22] wish me luck [06:23] my desktop system has been upgraded several times (I think since 15.04 days, but not exactly sure). My desktop has Asus BT card and until this last year, I was having similar problems as yours. [06:23] But now, all my BT devices are working great. I connect to speakers, receiver and phones [06:24] oh wow, with the PIN issue? [06:25] I mean, did Android pause and then fail with a PIN-related error? [06:25] yes, seems the hookup would almost work then fail at the last step. [06:26] Well, hopefully the master purge will work :) [06:26] back in 5 [06:26] Ensure pulseaudio-module-bluetooth is re-installed as my intel system would not connect to speakers without it (even on 17.10) [06:27] cu in 5 [06:28] jaafar: your back! whew...! [06:29] you're^ [06:31] BOOYAH [06:31] DarinMiller: yeah the grand purge did it [06:32] All working as you described now [06:32] good to know! [06:32] Perhaps the "Next" vs "Connect" should have been a sign [06:32] Now I have "Next" where before I had "Connect" [06:33] yes, I was confused by the "connect" button as mine said next. [06:33] Did you send a file? It should work now. [06:33] DarinMiller: very much appreciate your help [06:33] yep, it worked :) [06:34] awesome. You actually solved the problem. I was just the rubber ducky... :) === himcesjf_ is now known as him-cesjf [06:34] that has been an irritant for so long [06:34] DarinMiller: but I would not have known that it "should" work without your information [06:34] I had assumed it was just broken and nobody had time to fix it [06:34] Or was aware, etc. [06:35] OK one more for you but very trivial! [06:35] glad I could help. [06:35] I have to select "reboot" (or powerdown, etc.) twice every time [06:35] Ok, its getting late... [06:35] do you observe that? [06:35] there is a fine workaround, I am just curious [06:36] K menu, Leave, Reboot [06:36] nothing happens [06:36] K menu, Leave, Reboot [06:36] it reboots [06:36] oh, I am aware of the issue, but I do not know the fix. I suspect it's possibly a package like your bluetooth, but I have not clue. [06:36] haha so it is known :) [06:37] thanks DarinMiller enjoy your well-deserved rest and thanks for helping out in the channel [06:37] in sys setting, do you have the restart prompt enabled? (checking sys settting location, just a sec...) [06:38] oh man, listen, don't stay up on my account I was just wondering about that [06:39] it just take a sec... sys setting -> Startup and Shutdown [06:39] Desktop session tab, turn off Confirm logout and see if that fixed the issue. [06:40] OK [06:40] that will cause me to vanish [06:40] so I will try it later :) [06:40] yes. [06:40] appreciate the tip [06:40] ok, gn [06:40] gn to you too [06:45] jaafar: do you have Steam running? [06:45] As that will halt shutdowns [06:45] There are other apps as well [06:56] (Photo, 1280x1135) https://irc-attachments.kde.org/IOEHcmoB/file_3797.jpg [06:57] hateball: nope. Anyway it does work, the second time... [06:57] * jaafar should install Steam [07:13] Good morning === rudra_ is now known as rudra === kallesbar_ is now known as kallesbar [10:43] Hi! .... [10:43] What requirements do I need to have to install the latest version of kubuntu? [10:43] please help me! === DooWopBox is now known as Sauce_ === JonathanS is now known as JonathanD === JonathanD is now known as JonathanS === himcesjf_ is now known as him-cesjf [11:29] Hi folks === ForceRecon_ is now known as ForceRecon === ForceRecon is now known as Guest83175 === ForceRecon_ is now known as forcerecon === forcerecon is now known as ForceRecon [16:51] <[Relic]> Thinking of installing 17.04(usb already made) and then dist upgrading to 17.10. Any forseeable problems with that or should I make a new 17.10 and just install that? [17:00] The latter, every time. Regardless of what you're doing, less chance of problems just to install what version you want. [19:52] * ronnoc raises hand - count me in for the Breeze Dark theme by default :) [19:52] ronnoc: thanks [19:54] acheronuk: Anytime. It's classy and kool. === danny is now known as Guest4042 [21:16] BTW - anyone else use Akregator and have issues on start of a corrupted feed file that was automatically restored from backup? [21:35] hi [22:32] oi === trane is now known as trane_0 === ubott2 is now known as ubottu