[Bug 2067170] [NEW] sddm in Ubuntu 24.04 completely breaks multi-seat login
Public bug reported: It looks like login session from a second seat does get initialised properly. I have two seats logged in, and this is what I observe: **Only one session is reported by loginctl**: ``` loginctl list-sessions SESSION UID USERSEAT TTY 4 1000 dimanne seat0 tty2 1 sessions listed. ``` **Directory `/run/user/1001` is not created for 2nd seat**. **`DBUS_SESSION_BUS_ADDRESS` of the second user is empty**. **systemctl --user list-units prints**: ``` Failed to connect to bus: No medium found ``` **Finally, `loginctl session-status` says**: ``` Could not get properties: Unknown object 'org/freedesktop/login1/session/auto' ``` ### Why it happens I think this happens because sddm failed to properly initialise login session. This is how sddm logs look for "good" login: ``` Aug 20 09:52:17 impedance sddm[8212]: Authentication for user "dimanne" successful Aug 20 09:52:17 impedance sddm-greeter[8590]: Message received from daemon: LoginSucceeded Aug 20 09:52:17 impedance sddm-helper[9033]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Aug 20 09:52:17 impedance sddm-helper[9033]: pam_limits(sddm:session): Could not set limit for 'nofile' to soft=16777216, hard=16777216: Operation not permitted; uid=0,euid=0 Aug 20 09:52:17 impedance sddm-helper[9033]: pam_unix(sddm:session): session opened for user dimanne(uid=1000) by (uid=0) Aug 20 09:52:17 impedance sddm-helper[8362]: [PAM] Closing session Aug 20 09:52:17 impedance sddm-helper[8362]: pam_unix(sddm-greeter:session): session closed for user sddm Aug 20 09:52:17 impedance sddm-helper[8362]: [PAM] Ended. Aug 20 09:52:17 impedance sddm[8212]: Auth: sddm-helper exited successfully Aug 20 09:52:17 impedance sddm[8212]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS Aug 20 09:52:17 impedance sddm-helper[9033]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session Aug 20 09:52:17 impedance sddm-helper[9078]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket Aug 20 09:52:17 impedance sddm-helper[9033]: pam_env(sddm:session): deprecated reading of user environment enabled Aug 20 09:52:17 impedance sddm-helper[9033]: Writing cookie to "/tmp/xauth_vDhCDz" Aug 20 09:52:17 impedance sddm-helper[9033]: Starting X11 session: "" "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\"" Aug 20 09:52:17 impedance sddm[8212]: Session started true Aug 20 12:27:05 impedance sddm-greeter[8534]: Reading from "/usr/share/xsessions/plasma.desktop" ``` And this is how they look for 2nd seat ``` Aug 20 12:27:05 impedance sddm[8212]: Authentication for user "yulia" successful Aug 20 12:27:05 impedance sddm-greeter[8534]: Message received from daemon: LoginSucceeded Aug 20 12:27:05 impedance sddm-helper[56829]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Aug 20 12:27:05 impedance sddm-helper[56829]: pam_limits(sddm:session): Could not set limit for 'nofile' to soft=16777216, hard=16777216: Operation not permitted; uid=0,euid=0 Aug 20 12:27:05 impedance sddm-helper[56829]: pam_unix(sddm:session): session opened for user yulia(uid=1001) by (uid=0) Aug 20 12:27:05 impedance sddm-helper[56829]: pam_systemd(sddm:session): Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0 Aug 20 12:27:05 impedance sddm-helper[56829]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session Aug 20 12:27:05 impedance sddm-helper[56832]: pam_kwallet5: final socket path: /tmp/kwallet5_yulia.socket Aug 20 12:27:05 impedance sddm-helper[56829]: pam_env(sddm:session): deprecated reading of user environment enabled Aug 20 12:27:05 impedance sddm-helper[56829]: Writing cookie to "/tmp/xauth_MzDsqA" Aug 20 12:27:05 impedance sddm-helper[56829]: Starting X11 session: "" "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\"" Aug 20 12:27:05 impedance sddm[8212]: Session started true Aug 20 12:27:05 impedance sddm-helper[8399]: [PAM] Closing session Aug 20 12:27:05 impedance sddm-helper[8399]: pam_unix(sddm-greeter:session): session closed for user sddm Aug 20 12:27:05 impedance sddm-helper[8399]: [PAM] Ended. Aug 20 12:27:05 impedance sddm[8212]: Auth: sddm-helper exited successfully Aug 20 12:27:05 impedance sddm[8212]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS ``` Note: `Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0` It has been broken for some time, and it is surprising that it was picked for LTS Ubuntu 24.04: * https://github.com/sddm/sddm/issues/1762 * https://github.com/sddm/sddm/issues/1769 * https://github.com/sddm/sddm/issues/1778 * https://github.com/sddm/sddm/issues/1786 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: sddm 0.20.0-2ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architec
[Bug 2067163] [NEW] regression: sbsign crashes while signing an (EFI) image
Public bug reported: Reproduction: Try signing a file using sbsign where key is stored on a Yubikey, it will crash: ``` sbsign --engine pkcs11 --key 'pkcs11:manufacturer=piv_II;id=%02' --cert ./sb/db.crt --output ./sb/secboot-linux-latest.efi.signed ./sb/secboot-linux-latest.efi ``` gdb shows this backtrace: ``` Thread 1 "sbsign" received signal SIGSEGV, Segmentation fault. 0x77faf1fe in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so (gdb) bt #0 0x77faf1fe in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #1 0x77faf962 in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #2 0x77fb5567 in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #3 0x77fb58b0 in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #4 0x77fb3731 in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #5 0x77fb37bb in ?? () from /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so #6 0x77d1eed6 in RSA_sign (type=, m=m@entry=0x7fffdb80 "\224t\257>Y$\377...", m_len=m_len@entry=32, sigret=sigret@entry=0x555f89a0 "\330\322\n", siglen=siglen@entry=0x7fffdb14, rsa=rsa@entry=0x555f4270) at ../crypto/rsa/rsa_sign.c:309 #7 0x77d1d5a2 in pkey_rsa_sign (ctx=0x555eb5d0, sig=0x555f89a0 "\330\322\n", siglen=0x7fffdc30, tbs=0x7fffdb80 "\224t\257>Y$\377...", tbslen=32) at ../crypto/rsa/rsa_pmeth.c:180 #8 0x77c06817 in EVP_DigestSignFinal (ctx=ctx@entry=0x555d8c50, sigret=0x555f89a0 "\330\322\n", siglen=siglen@entry=0x7fffdc30) at ../crypto/evp/m_sigver.c:560 #9 0x77cfdcbc in PKCS7_SIGNER_INFO_sign (si=si@entry=0x555a85f0) at ../crypto/pkcs7/pk7_doit.c:952 #10 0x77cfdf9d in do_pkcs7_signed_attrib (mctx=, si=0x555a85f0) at ../crypto/pkcs7/pk7_doit.c:728 #11 PKCS7_dataFinal (p7=p7@entry=0x555f3520, bio=bio@entry=0x555a8640) at ../crypto/pkcs7/pk7_doit.c:850 #12 0x7c40 in IDC_set (image=, si=0x555a85f0, p7=0x555f3520) at /usr/src/sbsigntool-0.9.4-3.1ubuntu7/src/idc.c:216 #13 main (argc=, argv=) at /usr/src/sbsigntool-0.9.4-3.1ubuntu7/src/sbsign.c:274 (gdb) ``` It is likely that pkcs11.so is a "red herring" because I tried replacing the library with an older library from a docker image (`docker cp old_image /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so`) and it did NOT fix the issue. These are logs just before crash: ``` P:169928; T:0x133947370026816 16:44:23.956 [opensc-pkcs11] slot.c:501:slot_token_removed: slot_token_removed(0x4) P:169928; T:0x133947370026816 16:44:23.956 [opensc-pkcs11] pkcs11-session.c:145:sc_pkcs11_close_all_sessions: real C_CloseAllSessions(0x4) 0 P:169928; T:0x133947370026816 16:44:23.956 [opensc-pkcs11] slot.c:501:slot_token_removed: slot_token_removed(0x5) P:169928; T:0x133947370026816 16:44:23.956 [opensc-pkcs11] pkcs11-session.c:145:sc_pkcs11_close_all_sessions: real C_CloseAllSessions(0x5) 0 P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] slot.c:501:slot_token_removed: slot_token_removed(0x6) P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] pkcs11-session.c:145:sc_pkcs11_close_all_sessions: real C_CloseAllSessions(0x6) 0 P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] slot.c:501:slot_token_removed: slot_token_removed(0x7) P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] pkcs11-session.c:145:sc_pkcs11_close_all_sessions: real C_CloseAllSessions(0x7) 0 P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] ctx.c:1066:sc_release_context: called P:169928; T:0x133947370026816 16:44:23.957 [opensc-pkcs11] reader-pcsc.c:978:pcsc_finish: called fish: Job 1, 'sbsign --engine pkcs11 --key 'p…' terminated by signal SIGSEGV (Address boundary error) ``` Logs were collected with `set -x OPENSC_DEBUG 9`, See more logs here: https://0bin.net/paste/4-TdVHy4#f8e68wCZrtty55tjhLKAFpA2YeSQ2jl9AopYJXf3J5- ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: sbsigntool 0.9.4-3.1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 25 16:30:00 2024 InstallationDate: Installed on 2023-08-15 (284 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230815) SourcePackage: sbsigntool UpgradeStatus: Upgraded to noble on 2024-05-24 (1 days ago) ** Affects: sbsigntool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Summary changed: - regression: sbsign crashes while signing unified EFI image + regression: sbsign crashes while signing an (EFI) image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067163 Title: regression: sbsign crashes while signing an (EFI) image To
[Bug 2056735] Re: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked'
I am having slightly different issue: ``` File "/home/dimanne/devel/scripts/man/docker/build.py", line 185, in _build self._build(configs, item.as_group_name(), "", False) File "/home/dimanne/devel/scripts/man/docker/build.py", line 220, in _build self._tag(name, last_built_image_name) File "/home/dimanne/devel/scripts/man/docker/build.py", line 163, in _tag with docker.APIClient(base_url='unix://var/run/docker.sock') as client: ^^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 197, in __init__ self._version = self._retrieve_server_version() ^^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 221, in _retrieve_server_version raise DockerException( docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' ``` while trying to tag an image from python code: ``` import docker with docker.APIClient(base_url='unix://var/run/docker.sock') as client: client.tag(image=image_to_tag, repository=tag_name, tag='latest', force=True) ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056735 Title: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2056735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960702] Re: all snap apps gone after snap upgrade
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 I am not sure this bug is a duplicate of bug #1957948. Bug #1957948 is annoying, but is not serious (when I open a new console, I see a message about fish_add_path. While this bug breaks entire system (KDE cannot load) because XDG_DATA_DIRS is set incorrectly. Essentially, it renders entire system unusable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960702] Re: all snap apps gone after snap upgrade
Essentially, this bug broke entire KDE for me (not only snap packages). I was getting these weird errors right after entering login password: ``` ksplashqml KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = ksplashqml path = /usr/bin pid = 17218 KCrash: Arguments: /usr/bin/ksplashqml KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Icon theme "breeze" not found. Icon theme "breeze" not found. ``` Thank you Loic - the workaround helped! I wish they tested such changes... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945075] Re: wayland: is not possible to setup several displays
Blurry lines on 125% scale in Wayland ** Attachment added: "125scale_vs_100scale.png" https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1945075/+attachment/5528045/+files/125scale_vs_100scale.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945075 Title: wayland: is not possible to setup several displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1945075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945075] [NEW] wayland: is not possible to setup several displays
Public bug reported: I decided to try wayland and got several issues, in the order of (subjective) importance: ### Issue 1 I have two monitors, one of which is rotated 90 degrees, so I tried to set them up in wayland session (as I did in X). You can see on the screenshot "wayland_display_settings.jpg" that I specified that it is rotated and pressed "Apply", and one of them *is* rotated on the preview. However, you can see that actual content on that display is not rotated. Also, note where the task panel is located on the first display - it is in the centre of the screen. Just in case, here is xrand command I am using in X: xrandr --output DP-2 --mode 3840x2160 --pos 0x790 --scale 1.1875x1.1875 \ --output DP-0 --mode 3840x2160 --pos 4560x0 --rotate left --primary ### Issue 2 It looks like some options are missing. In X, there are: * "Replica of: None" option, which disables duplicating of image. * "Primary" checkbox, which removes panel from secondary display. but there are not such options in Wayland. ### Issue 3 Scaling deteriorates sharpness, makes thin lines blurry. See screenshot of Krusader 125scale_vs_100scale.png. Thin lines become blurry. I was using this short guide to setup Wayland: https://community.kde.org/Plasma/Wayland/Nvidia ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: kwin-wayland 4:5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Sep 25 22:41:55 2021 InstallationDate: Installed on 2021-01-30 (238 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: kwin UpgradeStatus: Upgraded to impish on 2021-09-25 (0 days ago) ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ** Attachment added: "wayland_display_settings.jpg" https://bugs.launchpad.net/bugs/1945075/+attachment/5528041/+files/wayland_display_settings.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945075 Title: wayland: is not possible to setup several displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1945075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945075] Re: wayland: is not possible to setup several displays
Forgot to mention that for the experiments / screenshots I created a fresh user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945075 Title: wayland: is not possible to setup several displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1945075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769240] Re: Images in chromium are distorted
Yes, it looks like everything is fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769240 Title: Images in chromium are distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1769240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769240] Re: Images in chromium are distorted
I am quite sure that the issue has been fixed in the new Chromium (for example I can not reproduce the bug on Google Maps anymore), but the havoc wreaked by the issue is still here. For example I still have distorted previews of sites on the home page, I suppose they have been cached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769240 Title: Images in chromium are distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1769240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768199] Re: Chromium freezes
I have tried doing it, the problem have gone, it works fine. Newer Chromium (66.0.3359.139) from the Ubuntu repos also works perfectly. I suppose you can close the bug-report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768199 Title: Chromium freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1768199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755182] Re: Horrendous latency in Chrome
Also see https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1768199/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755182 Title: Horrendous latency in Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1755182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769240] [NEW] Images in chromium are distorted
Public bug reported: See this images https://drive.google.com/open?id=1V83Jb-k1zsgRr5pBIUIy8csvgOWLbmha https://drive.google.com/open?id=1YG_xB_9iCOcseoqNEdqBSyKrf58beHA7 https://drive.google.com/open?id=1P_lgxbKMpV3VK9UaLEPcBrE7W6YsGuDP ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 21:08:06 2018 Desktop-Session: 'plasma' '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-12-16 (139 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) InstalledPlugins: Load-Avg-1min: 0.97 Load-Processes-Running-Percent: 0.3% MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-02 (32 days ago) dmi.bios.date: 08/31/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769240 Title: Images in chromium are distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1769240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768199] Re: Chromium freezes
I have just noticed that dmesg has very strange info: WARNING: kernel stack frame pointer at b2107faf in chromium-browse:1892 has bad value 648ab7fa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768199 Title: Chromium freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1768199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768199] [NEW] Chromium freezes
Public bug reported: After I updated to Ubuntu 18.04 I noticed that chromium interactions (scroll for example) and mouse pointer itself started to freeze for hundreds of milliseconds (0.1s - 0.2s). So, I was constantly scrolling (in order to reproduce the bug) while running perf top, and it pointed to this function: sudo perf top -t 1892 -d 5 --call-graph fp Children Self Shared Object Symbol - 80,55% 0,00% libc-2.27.so[.] __GI___ioctl - 76,84% __GI___ioctl 71,67% _nv029804rm - 1,12% _nv020749rm - 1,03% os_release_spinlock 0,97% _raw_spin_unlock_irqrestore - 71,69%71,67% [kernel][k] _nv029804rm 71,58% 0x18012a __GI___ioctl _nv029804rm - 16,75% 0,00% [unknown] [k] 0x0018012a 0x18012a - __GI___ioctl 15,25% _nv029804rm -8,67% 0,25% libc-2.27.so[.] syscall - 5,45% syscall 1,89% syscall_return_via_sysret - 1,05% entry_SYSCALL_64_after_hwframe - 1,22% do_syscall_64 top command also showed that this process was eating one core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 1 10:38:19 2018 Desktop-Session: 'plasma' '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-12-16 (136 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) InstalledPlugins: Load-Avg-1min: 1.64 Load-Processes-Running-Percent: 0.1% MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e3723f86-9a4d-4166-960b-88262212fcc6 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-02 (28 days ago) dmi.bios.date: 08/31/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd08/31/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: After I updated to Ubuntu 18.04 I noticed that chromium interactions (scroll for example) and mouse pointer itself started to freeze for - hundreds of milliseconds (0.1s - 0/2s). + hundreds of milliseconds (0.1s - 0.2s). So, I was constantly scrolling (in order to reproduce the bug) while running perf top, and it pointed to this function: sudo perf top -t 1892 -d 5 --call-graph fp - Children Self Shared Object Symbol + Children Self Shared Object Symbol - 80,55% 0,00% libc-2.27.so[.] __GI___ioctl -- 76,84% __GI___ioctl - 71,67% _nv029804rm - - 1,12% _nv020749rm - - 1,03% os_release_spinlock - 0,97% _raw_spin_unlock_irqrestore + - 76,84% __GI___ioctl + 71,67% _nv029804rm + - 1,12% _nv020749rm + - 1,03% os_release_spinlock + 0,97% _raw_spin_unlock_irqrestore - 71,69%71,67% [kernel][k] _nv029804rm - 71,58% 0x18012a - __GI___ioctl - _nv029804rm + 71,58% 0x18012a + __GI___ioctl + _nv029804rm - 16,75% 0,00% [unknown] [k] 0x0018012a - 0x18012a -- __GI___ioctl - 15,25% _nv029804rm + 0x18012a + - __GI___ioctl + 15,25% _nv029804rm -8,67% 0,25% libc-2.27.so[.] syscall -- 5,45% syscall - 1,89% syscall_return_via_sysret - - 1,05% entry_SYSCALL_64_after_hwframe - - 1,22% do_syscall_64 + - 5,45% syscall + 1,89% syscall_return_via_sysret + - 1,05% entry_SYSCALL_64_after_hwframe + - 1,22% do_syscall_64 top command also showed that this process was eating one core. ProblemType: Bug DistroRelease:
[Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Thank you, benvantende! Reinstalling pulseaudio has helped me too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
+1 I have encountered the same bug (NMI watchdog: BUG: soft lockup - CPU#10 stuck for 23s!). Logs could be found in the attachment. ** Attachment added: "SecondHang.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4880124/+files/SecondHang.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654782] Re: Can not pair with bluetooth headphones
** Description changed: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. - For example, my smartphone pairs with the headset in 5-15 seconds, my - laptop pairs with the headset in about 30 seconds. + For example, my smartphone pairs with the headset within 5-15 seconds, + my laptop pairs with the headset within about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB - BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 - UP RUNNING PSCAN ISCAN - RX bytes:4475 acl:0 sco:0 events:565 errors:0 - TX bytes:7214 acl:0 sco:0 commands:487 errors:0 - Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 - Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 - Link policy: RSWITCH SNIFF - Link mode: SLAVE ACCEPT - Name: 'impedance' - Class: 0x1c0104 - Service Classes: Rendering, Capturing, Object Transfer - Device Class: Computer, Desktop workstation - HCI Version: 4.0 (0x6) Revision: 0x1000 - LMP Version: 4.0 (0x6) Subversion: 0x220e - Manufacturer: Broadcom Corporation (15) + BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 + UP RUNNING PSCAN ISCAN + RX bytes:4475 acl:0 sco:0 events:565 errors:0 + TX bytes:7214 acl:0 sco:0 commands:487 errors:0 + Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 + Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 + Link policy: RSWITCH SNIFF + Link mode: SLAVE ACCEPT + Name: 'impedance' + Class: 0x1c0104 + Service Classes: Rendering, Capturing, Object Transfer + Device Class: Computer, Desktop workstation + HCI Version: 4.0 (0x6) Revision: 0x1000 + LMP Version: 4.0 (0x6) Subversion: 0x220e + Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + Soft blocked: no + Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper
[Bug 1654782] [NEW] Can not pair with bluetooth headphones
Public bug reported: I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless aebt). (If it matters, I *CAN* pair and use it on another laptop with Linux and with my android smartphone. So headset itself is working well.) Here is how I try to pair: $ bluetoothctl [NEW] Controller 54:27:1E:33:4B:85 impedance [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes [bluetooth]# scan on I tried to put my headset in pairing mode just before and after issuing "scan on" command. It ends up with nothing - I waited for 3-5 minutes. For example, my smartphone pairs with the headset in 5-15 seconds, my laptop pairs with the headset in about 30 seconds. = Here is info $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4475 acl:0 sco:0 events:565 errors:0 TX bytes:7214 acl:0 sco:0 commands:487 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) = rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no = Bluez packages installed: $ dpkg -l | grep bluez ii bluez ii bluez-btsco ii bluez-cups ii bluez-hcidump ii bluez-obexd ii bluez-tools ii libkf5bluezqt-data ii libkf5bluezqt6:amd64 ii qml-module-org-kde-bluezqt:amd64 = $ dmesg | grep -i blue [4.632406] Bluetooth: Core ver 2.21 [4.632414] Bluetooth: HCI device and connection manager initialized [4.632416] Bluetooth: HCI socket layer initialized [4.632417] Bluetooth: L2CAP socket layer initialized [4.632420] Bluetooth: SCO socket layer initialized [4.644619] Bluetooth: hci0: BCM: chip id 63 [4.660554] Bluetooth: hci0: impedance [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build [4.661798] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.061604] Bluetooth: BNEP filters: protocol multicast [ 15.061606] Bluetooth: BNEP socket layer initialized [ 48.001553] Bluetooth: RFCOMM TTY layer initialized [ 48.001558] Bluetooth: RFCOMM socket layer initialized [ 48.001562] Bluetooth: RFCOMM ver 1.11 [ 615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jan 7 22:36:22 2017 InstallationDate: Installed on 2014-07-05 (917 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-10-09 (89 days ago) dmi.bios.date: 01/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be
[Bug 1650730] [NEW] Google Music does not work anymore
Public bug reported: After upgrading chromium from 53.0.2785.143-0ubuntu1.1307 to 55.0.2883.87-0ubuntu0.16.10.1328 google music (https://play.google.com/music/listen#/home) does not work and show me this: Missing Flash Player You need the latest Adobe Flash Player to listen to music. Note: I have never had adobe flash installed: $ dpkg -l | grep "adobe\|flash" ii kwordquiz 4:16.04.3-0ubuntu1 amd64 flashcard learning program $ and it worked an hour ago (before updating)! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.10.1328 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Dec 17 12:26:57 2016 Desktop-Session: '/usr/share/xsessions/plasma' '/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-07-05 (895 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Load-Avg-1min: 1.36 Load-Processes-Running-Percent: 0.3% MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to yakkety on 2016-10-09 (68 days ago) dmi.bios.date: 01/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X79-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd01/07/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX79-DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650730 Title: Google Music does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1650730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633583] [NEW] Can not connect to Bluetooth headset
Public bug reported: I managed to pair with my wireless headset, but I was unable to connect to it. Every time I try to do it, I get this message in syslog: Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice gateway SDP record: Host is down Relating info is below Info from bluetoothctl: bluetooth]# devices Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT bluetooth]# info 00:1B:66:03:C4:66 Device 00:1B:66:03:C4:66 Name: MOMENTUM M2 AEBT Alias: MOMENTUM M2 AEBT Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: yes UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (1ddce62a-ecb1-4455-8153-0743c87aec9f) Modalias: bluetooth:v0082p004Bd010E Info from hciconfig $ sudo hciconfig -a [sudo] password for dimanne: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:73:F2:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:14866 acl:33 sco:0 events:2022 errors:0 TX bytes:17848 acl:33 sco:0 commands:1639 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance #1' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) hci1: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:2926 acl:0 sco:0 events:161 errors:0 TX bytes:5699 acl:0 sco:0 commands:157 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT rfkill: $ rfkill list 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Info from dmesg: $ dmesg | grep -i blue [5.170808] Bluetooth: Core ver 2.21 [5.170819] Bluetooth: HCI device and connection manager initialized [5.170821] Bluetooth: HCI socket layer initialized [5.170822] Bluetooth: L2CAP socket layer initialized [5.170826] Bluetooth: SCO socket layer initialized [5.185923] Bluetooth: hci0: BCM: chip id 63 [5.186665] Bluetooth: hci1: BCM: chip id 63 [5.202506] Bluetooth: hci0: impedance #2 [5.203150] Bluetooth: hci1: ChromeLinux_5818 [5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build [5.203670] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2 [5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found [5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build [5.204671] bluetooth hci1: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.359872] Bluetooth: BNEP filters: protocol multicast [ 11.359874] Bluetooth: BNEP socket layer initialized [ 34.046364] Bluetooth: RFCOMM TTY layer initialized [ 34.046368] Bluetooth: RFCOMM socket layer initialized [ 34.046371] Bluetooth: RFCOMM ver 1.11 [ 1193.523500] Bluetooth: hci0: BCM: chip id 63 [ 1193.539525] Bluetooth: hci0: BCM20702A [ 1193.540524] Bluetooth: hci0: BCM20702A1 (001.002.014) build [ 1193.540535] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2 [ 1193.540536] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found [ 1575.051358] Bluetooth: Inquiry failed: status 0x12 [ 1593.226346] Bluetooth: Inquiry failed: status 0x12 [ 1684.104314] Bluetooth: Inquiry failed: status 0x12 [ 1694.087408] Bluetooth: Inquiry failed: status 0x12 pulseaudio-module-bluetooth is installed: dpkg -l | grep pulseaudio-module-bluetooth ii pulseaudio-module-bluetooth 1:9.0-2ubuntu2 amd64 Bluetooth module
[Bug 1435641] Re: plasmashell 100% cpu on screen lock
I have recently encountered this problem again at my notebook. System info: plasmashell 5.5.5 OS: Kubuntu 16.04 Also, I have two (physical) monitors, and I noticed this problem began to arise after I detached/attached notebook from dock station or after hibernation Backtraces, perf top: I ran "top -H" and it said there are two threads on my system, which are eating CPU - plasmashell and Xorg, so here is "hottest" backtraces of these threads collected with perf top -t 3136 -d 5 --call-graph dwarf (where 3136 is thread Id from top output) Thread of plasmashell - http://pastebin.com/GPMkrWz8 (see text after RAW Paste Data) Thread of Xorg - http://pastebin.com/ZH0x7F7i (see text after RAW Paste Data) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435641 Title: plasmashell 100% cpu on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1435641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592668] Re: plasmashell is eating 100% cpu and all UI is slow
I notice, it starts to happen when psi icon (in tray) is blinking. (But it also happens without running psi. So psi icon in tray is not the only cause of this bug) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592668 Title: plasmashell is eating 100% cpu and all UI is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1592668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592668] [NEW] plasmashell is eating 100% cpu and all UI is slow
Public bug reported: plasmashell (and Xorg) processes have recently started to eat 100% cpu and all UI operations are VERY slow now. Some info from perf top: Annotate _Z7qstrcmpRK10QByteArrayPKc Zoom into plasmashell(2412) thread Zoom into libQt5Core.so.5.5.1 DSO Browse map details Run scripts for samples of thread [plasmashell] Run scripts for samples of symbol [_Z7qstrcmpRK10QByteArrayPKc] Plasmashell thread http://pastebin.com/CZtfCq7m Xorg thread http://pastebin.com/eAi9Ua9N ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: plasma-workspace 4:5.5.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 15 09:50:25 2016 InstallationDate: Installed on 2012-11-28 (1294 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: plasma-workspace UpgradeStatus: Upgraded to xenial on 2016-04-22 (53 days ago) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592668 Title: plasmashell is eating 100% cpu and all UI is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1592668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492619] Re: clang++-3.7 crashes while compiling
I already reported it to upstream - https://llvm.org/bugs/show_bug.cgi?id=24730 // They are much more faster in reviewing and responding. ** Bug watch added: LLVM #24730 https://llvm.org/bugs/show_bug.cgi?id=24730 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492619 Title: clang++-3.7 crashes while compiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1492619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492619] [NEW] clang++-3.7 crashes while compiling
Public bug reported: Here is clang output 0 libLLVM-3.7.so.1 0x7f04d387f640 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 64 1 libLLVM-3.7.so.1 0x7f04d387eaa1 2 libpthread.so.0 0x7f04d3189d10 3 clang0x012f14f8 clang::Expr::IgnoreParens() + 8 4 clang0x012f212d clang::Expr::IgnoreParenImpCasts() + 13 5 clang0x00c65899 6 clang0x00c65e17 7 clang0x00c7c874 8 clang0x00c7db4c clang::Sema::ActOnCXXDelete(clang::SourceLocation, bool, bool, clang::Expr*) + 284 9 clang0x00e1278d 10 clang0x00e0e846 11 clang0x00e1cf2d 12 clang0x00e1e3cb 13 clang0x00e1e50b 14 clang0x00e1d255 15 clang0x00e20b8f clang::Sema::SubstStmt(clang::Stmt*, clang::MultiLevelTemplateArgumentList const&) + 95 16 clang0x00e3423c clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, clang::FunctionDecl*, bool, bool) + 3756 17 clang0x00e3451a clang::Sema::PerformPendingInstantiations(bool) + 298 18 clang0x00acf3d5 clang::Sema::ActOnEndOfTranslationUnit() + 341 19 clang0x00a24cc9 clang::Parser::ParseTopLevelDecl(clang::OpaquePtr&) + 601 20 clang0x00a19ee3 clang::ParseAST(clang::Sema&, bool, bool) + 499 21 clang0x006a2fee clang::FrontendAction::Execute() + 510 22 clang0x0067a8b9 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 313 23 clang0x00661f43 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) + 1939 24 clang0x0065ca58 cc1_main(llvm::ArrayRef, char const*, void*) + 2232 25 clang0x006594de main + 1006 26 libc.so.60x7f04d2837a40 __libc_start_main + 240 27 clang0x0065bad9 _start + 41 Stack dump: 0. Program arguments: /usr/lib/llvm-3.7/bin/clang -cc1 -triple x86_64-pc-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name TTreeView.cpp -mrelocation-model pic -pic-level 2 -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -target-linker-version 2.25.1 -g -dwarf-column-info -coverage-file /home/Void/devel/build-EventManager-Qt_5_4_1_clang-Debug/client/plugins/evmanclient/.obj/TTreeView.o -resource-dir /usr/lib/llvm-3.7/bin/../lib/clang/3.7.0 -D _REENTRANT -D EVMANCLIENT_LIBRARY -D QT_QML_DEBUG -D QT_DECLARATIVE_DEBUG -D QT_PLUGIN -D QT_OPENGL_LIB -D QT_PRINTSUPPORT_LIB -D QT_WIDGETS_LIB -D QT_QUICK_LIB -D QT_GUI_LIB -D QT_QML_LIB -D QT_NETWORK_LIB -D QT_SQL_LIB -D QT_CORE_LIB -I ../../../../EventManager/client/plugins/evmanclient -I . -I ../../../../EventManager/include -I ../../../../EventManager/include -I ../../../../Botan-1.11.4/build/include -I ../../../.. /EventManager/include -I ../../../../EventManager/include -I ../../../../Botan-1.11.4/build/include -I ../../../../EventManager/shared/modeltest -I ../../../../Qt5Bin/5.5/gcc_64/include -I ../../../../Qt5Bin/5.5/gcc_64/include/QtOpenGL -I ../../../../Qt5Bin/5.5/gcc_64/include/QtPrintSupport -I ../../../../Qt5Bin/5.5/gcc_64/include/QtWidgets -I ../../../../Qt5Bin/5.5/gcc_64/include/QtQuick -I ../../../../Qt5Bin/5.5/gcc_64/include/QtGui -I ../../../../Qt5Bin/5.5/gcc_64/include/QtQml -I ../../../../Qt5Bin/5.5/gcc_64/include/QtNetwork -I ../../../../Qt5Bin/5.5/gcc_64/include/QtSql -I ../../../../Qt5Bin/5.5/gcc_64/include/QtCore -I .moc -I ../../../../Qt5Bin/5.5/gcc_64/mkspecs/linux-clang -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.2.1/../../../../include/c++/5.2.1 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.2.1/../../../../include/x86_64-linux-gnu/c++/5.2.1 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.2.1/../../../../include/x86_64-linux-gnu/c++/5.2 .1 -internal-isystem /usr/bin/../lib/gcc/x86_64-linux-gnu/5.2.1/../../../../include/c++/5.2.1/backward -internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-3.7/bin/../lib/clang/3.7.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -Wno-inconsistent-missing-override -Wall -Wno-overloaded-virtual -std=c++1y -fdeprecated-macro -fdebug-compilation-dir /home/Void/devel/build-EventManager-Qt_5_4_1_clang-Debug/client/plugins/evmanclient -ferror-limit 19 -fmessage-length 0 -fvisibility hidden -mstackrealign -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -o .obj/TTreeView.o -x c++ ../../../../EventManager/client/plugins/evmanclient/TTreeView.cpp 1. parser at end of file 2. ../../../../EventManager/include/libs/tree/../../../libs/tree/TTree.h:28:7:
[Bug 1492619] Re: clang++-3.7 crashes while compiling
** Attachment added: "TTreeView-624f65.sh" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1492619/+attachment/4458011/+files/TTreeView-624f65.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492619 Title: clang++-3.7 crashes while compiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1492619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492619] Re: clang++-3.7 crashes while compiling
** Attachment added: "TTreeView-624f65.cpp" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1492619/+attachment/4458010/+files/TTreeView-624f65.cpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492619 Title: clang++-3.7 crashes while compiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.7/+bug/1492619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458352] [NEW] Key sequence '...' is ambiguous message box on almost every shortcut
Public bug reported: Every time I enter Home, End, Shift+Ins Kate shows me dialog box, which says The key sequence 'Home' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered But when I try to fix it (and I did NOT break it, ie before updating to Kubuntu 15.04 / KDE 5 all worked well) in Configure Shortcuts, I got several problems 1) Seems that this shortcut is actually shortcut for the only action (https://img-fotki.yandex.ru/get/15581/11330794.1d/0_bc945_764f522a_orig) and there is no any ambiguity. 2) When I try to remove Home from Alternate column and assign it to Shortcut column I got cryptic message The Home shortcut is ambiguous with the following shortcut. Do you want to assign an empty shortcut to this action? Shortcut '' for action 'Move to Beginning of Line' https://img-fotki.yandex.ru/get/6517/11330794.1d/0_bc946_3d6c33e8_orig 3) And finally, I press Reassign button get correct shortcuts: https://img-fotki.yandex.ru/get/5504/11330794.1d/0_bc947_a734a49a_orig then click Ok and again try to press Home in Kate I again get dialog box from 1st point (The key sequence 'Home' is ambiguous. Use...) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: kate 4:14.12.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 24 19:19:10 2015 InstallationDate: Installed on 2014-07-05 (323 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: kate UpgradeStatus: Upgraded to vivid on 2015-02-23 (90 days ago) ** Affects: kate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458352 Title: Key sequence '...' is ambiguous message box on almost every shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1458352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to Matteo Croce from comment #66) Seems fixed here with: rm -rf ~/.cache/ Thanks, seems it helped. I was experiencing similar issues. At some point (about several minutes after login) kde suddenly freezes. I can move mount, but it does not response to mouse clicks and (global) shortcuts, it also does not update clock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385876] Re: lldb-3.5 does not work
(lldb-3.4 works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385876 Title: lldb-3.5 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1385876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385876] [NEW] lldb-3.5 does not work
Public bug reported: When I try to run binary of ls in lldb I get this $ lldb-3.5 /bin/ls Traceback (most recent call last): File string, line 1, in module ImportError: No module named lldb.embedded_interpreter error: '/bin/ls' doesn't contain the architecture x86_64 (lldb) file command says it is x86_64: $ file /bin/ls /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=9508b95ba96ff7e8535b452acb1313b08aa23c26, stripped ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lldb-3.5 (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 26 16:29:28 2014 InstallationDate: Installed on 2014-07-05 (112 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: llvm-toolchain-3.5 UpgradeStatus: Upgraded to utopic on 2014-08-30 (57 days ago) ** Affects: llvm-toolchain-3.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385876 Title: lldb-3.5 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1385876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374595] [NEW] Emask 0x3 (HSM violation)
Public bug reported: I do not know how to reopen this bug https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/445852 so I decided to create new bug. After recent update of Kubuntu 14.10 (beta), and following reboot, I got these messages in dmesg [1.534737] ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [1.534758] ata14.00: irq_stat 0x4001 [1.534771] scsi 13:0:0:0: CDB: [1.534772] Inquiry: 12 01 00 00 ff 00 [1.534776] ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 3 dma 16640 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) [1.534816] ata14: hard resetting link Full dmesg: http://paste.ubuntu.com/8434914/ ** Affects: libatasmart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374595 Title: Emask 0x3 (HSM violation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1374595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
1) Next time you might want to file the bug report using the following command so that the relevant logs are automatically attached for you: ubuntu-bug nvidia-331 I did it exactly the same way. 2) I can install ubuntu nvidia driver again, so, what logs are you interested in? 3) Any way, without installing ubuntu nvidia driver, is it normal that all nvidia binaries are placed in /usr/lib/nvidia-331/bin? It seems that system just does not know that binaries and other staff is in /usr/lib/nvidia-331/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
lsmod ** Attachment added: lsmod https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191346/+files/lsmod -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
Ok, to accelerate investigation, I installed ubuntu nvidia drivers, attached logs. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191343/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191348/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: xorg.conf https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191367/+files/xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: nvidia-prime-upstart.log https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191347/+files/nvidia-prime-upstart.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: lsmod https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191372/+files/lsmod -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
And here is set of logs if I blacklist nouveau module (add file disable-nouveau.conf /etc/modprobe.d/ with this content blacklist nouveau options nouveau modeset=0 ) ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191371/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191374/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+attachment/4191373/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] [NEW] nvidia proprietary drivers are broken
Public bug reported: I upgrade Kubuntu 14.04 to 14.10 and noticed that all desktop effects became slow. In my dmesg I have these lines [ 17.039854] init: Failed to spawn nvidia-persistenced main process: unable to execute: No such file or directory [ 17.040940] init: nvidia-prime main process (2139) terminated with status 1 And it seems that something wrong with path/directories where scripts perform search for nvidia binaries. For example, in /etc/init/nvidia-persistenced.conf we can find this: exec /usr/bin/nvidia-persistenced --user nvidia-persistenced but, I really have not nvidia-persistenced binary in /usr/bin/, it is in /usr/lib/nvidia-331/bin/ Also, after installing nvidia-331 I have not nvidia-xconfig command in shell, but I have /usr/lib/nvidia-331/bin/nvidia-xconfig ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Aug 30 15:53:02 2014 InstallationDate: Installed on 2014-07-05 (55 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: Upgraded to utopic on 2014-08-30 (0 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363408] Re: nvidia proprietary drivers are broken
Found good workaround (almost solution): Installing native drivers from Nvidia solves issue. I installed this version - http://www.nvidia.com/Download/driverResults.aspx/77525/en-us 1) Download file from nvidia site 2) Add nouveau driver to blacklist (add blacklist nouveau to /etc/modprobe.d/blacklist (create this file, if it does not exist)) 3) then run sudo update-initramfs -u 4) then reboot 5) chmod +x _here_is_path_to_downloaded_nvidia_driver_, then run it Before step 5 you probably need to reboot to level 3 After this, Kubuntu works perfectly (like before upgrade) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363408 Title: nvidia proprietary drivers are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296887] Re: Boot-time vlan network setup fails
Thank you very much. Of course, it is very interesting why (and by what system update) it was removed, or how it was working before (in case if vlan package was not installed at all). But, after installing all start working! Thanks! ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296887 Title: Boot-time vlan network setup fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303250] Re: qt5-qmake does not create .pri file for qt script module in qt5/mkspecs/modules
Thanks, it works! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303250 Title: qt5-qmake does not create .pri file for qt script module in qt5/mkspecs/modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1303250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303250] [NEW] qt5-qmake does not create .pri file for qt script module in qt5/mkspecs/modules
Public bug reported: I tried to compile QtCreator with system qmake (from Qt 5.2.1), and while running qmake I got this message: $ qmake ../qt-creator/qtcreator.pro LLVM_INSTALL_DIR=/usr/lib/llvm-3.4/ -recursive ... skipped ... Project ERROR: Unknown module(s) in QT: script It seems that qmake searches folder /usr/lib/x86_64-linux- gnu/qt5/mkspecs/modules for installed Qt modules. But the folder does not contain any file with name *script* Of course this module installed: $ aptitude show libqt5script5 Package: libqt5script5 State: installed Automatically installed: no ... So, now qmake thinks that I have not script module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt5-qmake 5.2.1+dfsg-1ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Apr 6 11:02:25 2014 InstallationDate: Installed on 2013-11-11 (145 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to trusty on 2014-02-21 (43 days ago) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303250 Title: qt5-qmake does not create .pri file for qt script module in qt5/mkspecs/modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1303250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296887] Re: Boot-time vlan network setup fails
Ping But still here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296887 Title: Boot-time vlan network setup fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296887] Re: Boot-time vlan network setup fails
I tried (already installed) 3.11.0-17-generic kernel (I thought it is not so important to test exactly the kernel version you pointed out), and issue also did NOT go away. It is still here. So it really seems that it is not kernel bug. But it is apparently bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296887 Title: Boot-time vlan network setup fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296887] Re: Boot-time vlan network setup fails
I tried first available 3.13.* kernel (in my case it was 3.13.0-11-generic) and issue did NOT go away. Network configuration does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296887 Title: Boot-time vlan network setup fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296887] [NEW] Boot-time vlan network setup fails
Public bug reported: It seems that vlan network setup fails at boot-time (but all works well after boot). This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 iface eth0.10 inet dhcp auto eth0.20 iface eth0.20 inet manual auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dimanne2784 F pulseaudio /dev/snd/controlC0: dimanne2784 F pulseaudio CurrentDesktop: KDE Date: Mon Mar 24 22:29:13 2014 HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596 InstallationDate: Installed on 2013-11-11 (133 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago) dmi.bios.date: 12/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - vlan network set up fails on boot + Boot-time vlan network setup fails ** Description changed: + It seems that vlan network setup fails at boot-time (but all works well + after boot). + This regression was introduced several (2-3) day ago. My /etc/network/interfaces $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth0.10 - iface eth0.10 inet dhcp + iface eth0.10 inet dhcp auto eth0.20 - iface eth0.20 inet manual + iface eth0.20 inet manual auto dsl-provider - iface dsl-provider inet ppp - pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf + iface dsl-provider inet ppp + pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf provider dsl-provider - - During boot I see Waiting for network configuration..., after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. + During boot I see Waiting for network configuration..., after boot in + ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces. But, if I run manually these commands AFTER boot ip link add link eth0 name eth0.10 type vlan id 10 ip link add link eth0 name eth0.20 type vlan id 20 pon dsl-provider all works perfectly. Also I tried to add 8021q in /etc/modules but it did not help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.39 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: dimanne2784 F pulseaudio - /dev/snd/controlC0: dimanne2784 F pulseaudio + USER
[Bug 1272438] [NEW] kwin 100% of cpu, second session
Public bug reported:
Steps to reproduce
Login as user1
Login as user2
Press Ctrl+Alt+F7 (to switch to first user)
kwin from second user starts to eat 100% of cpu.
Here is my investigation of what is going on
1) == GDB ==
I attached to running (and eating 100% of cpu) kwin, paused (ctrl+c command)
and run (continue command) kwin several times and watched output of info
threads command to figure out what thread is eating 100%.
What I got:
(gdb) info threads
Id Target Id Frame
3Thread 0x7fa21ecb6700 (LWP 25128) QProcessManager 0x7fa23f3c8de3
in select () at ../sysdeps/unix/syscall-template.S:81
2Thread 0x7fa21c9c6700 (LWP 25131) kwin pthread_cond_wait@@GLIBC_2.3.2
()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1Thread 0x7fa23fbfe7c0 (LWP 25123) kwin 0x7fa236ea7f84 in
__GI___pthread_mutex_lock (mutex=0x2520918) at pthread_mutex_lock.c:54
(gdb) continue
// continue, wait some time, ctrl+c
(gdb) info threads
Id Target Id Frame
3Thread 0x7fa21ecb6700 (LWP 25128) QProcessManager 0x7fa23f3c8de3
in select () at ../sysdeps/unix/syscall-template.S:81
2Thread 0x7fa21c9c6700 (LWP 25131) kwin pthread_cond_wait@@GLIBC_2.3.2
()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1Thread 0x7fa23fbfe7c0 (LWP 25123) kwin 0x7fa23f3d1957 in
__libc_recv (fd=9, buf=0x2520974, n=4096, flags=-1, flags@entry=0)
at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
// continue, wait some time, ctrl+c
(gdb) info threads
Id Target Id Frame
3Thread 0x7fa21ecb6700 (LWP 25128) QProcessManager 0x7fa23f3c8de3
in select () at ../sysdeps/unix/syscall-template.S:81
2Thread 0x7fa21c9c6700 (LWP 25131) kwin pthread_cond_wait@@GLIBC_2.3.2
()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1Thread 0x7fa23fbfe7c0 (LWP 25123) kwin 0x7fa23f3c8de3 in select ()
at ../sysdeps/unix/syscall-template.S:81
and so on...
As you can see first thread is really doing something.
Now, when I know thread number I can see backtrace:
First backtrace
[Switching to thread 1 (Thread 0x7fa23fbfe7c0 (LWP 25123))]
#0 0x7fa238b11303 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
(gdb) backtrace
#0 0x7fa238b11303 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#1 0x7fa2396d05ef in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2 0x7fa2396d08e5 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3 0x7fa2396d5e5b in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x7fa23f719956 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#5 0x7fa23f2f7de5 in __libc_start_main (main=0x4006d0, argc=3,
ubp_av=0x7e010848, init=optimized out, fini=optimized out,
rtld_fini=optimized out, stack_end=0x7e010838) at libc-start.c:260
#6 0x004006fe in _start ()
// continue, wait some time, ctrl+c
And second one (after continue and ctrl+c)
(gdb) backtrace
#0 0x7fa23f3c8de3 in select () at ../sysdeps/unix/syscall-template.S:81
#1 0x7fa2396fc33b in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2 0x7fa239701904 in
QEventDispatcherUNIXPrivate::doSelect(QFlagsQEventLoop::ProcessEventsFlag,
timeval*) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3 0x7fa239701d02 in
QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x7fa238b112f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5 0x7fa2396d05ef in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x7fa2396d08e5 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7 0x7fa2396d5e5b in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x7fa23f719956 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#9 0x7fa23f2f7de5 in __libc_start_main (main=0x4006d0, argc=3,
ubp_av=0x7e010848, init=optimized out, fini=optimized out,
rtld_fini=optimized out, stack_end=0x7e010838) at libc-start.c:260
#10 0x004006fe in _start ()
(gdb)
2) == strace ==
Now lets see which syscalls are called, I ran this command
strace -p 25123 -s 1000 -o strace1.txt
And in 1-2 seconds I got file (with 5 lines) which contains ONLY these
messages:
select(29, [4 5 9 10 14 28], [], [], {0, 0}) = 0 (Timeout)
recvfrom(9, 0x2520974, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
select(29, [4 5 9 10 14 28], [], [], {0, 0}) = 0 (Timeout)
recvfrom(9, 0x2520974, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
select(29,
[Bug 1272438] Re: kwin 100% of cpu, second session
I am not sure, but it seems, that function denoted in gdb backtrace as #0 0x7fa238b11303 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 is bool QEventDispatcherX11::processEvents(QEventLoop::ProcessEventsFlags flags) from qt-src/src/gui/kernel/qeventdispatcher_x11.cpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272438 Title: kwin 100% of cpu, second session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1272438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259465] [NEW] kde-nm-connection-editor is completely useless for setting up TLS connections
Public bug reported: Try to set up TLS connection using KDE native NetworkManager. Choose 802.1x Security tab, choose TLS in Authentication: combobox and fill all its fields, even if all key info valid, kde-nm-connection-editor does not save changes and writes to /var/log/syslog these messages Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting certificate (invalid data): (1) ca-cert Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting certificate (invalid data): (1) client-cert Dec 10 12:40:43 DimanNeYa NetworkManager[894]: Error setting private key (invalid data): (1) private-key BUT(!!!) if you accomplish all these actions in nm-applet (from package network-manager-gnome) then all start working! It will successfully create connection, this connection will be visible for kde-nm- connection-editor... PS And even now, when connection created by nm-applet and I have working internet, I can not fill Private Key password: field, ie I can fill it, but after I press Ok all changes disgarded ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plasma-nm 0.9.3.1-0ubuntu1~saucy1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Dec 10 12:34:47 2013 ExecutablePath: /usr/bin/kde-nm-connection-editor InstallationDate: Installed on 2012-11-28 (377 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plasma-nm UpgradeStatus: Upgraded to saucy on 2013-10-18 (52 days ago) ** Affects: plasma-nm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259465 Title: kde-nm-connection-editor is completely useless for setting up TLS connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1259465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253519] [NEW] psi+ off-the-record plugin stopped working
Public bug reported: After kubuntu upgrade (to 13.10) otr plugin in psi+ stopped working. Now I receive this message every time somebody with otr writes me: [12.11.2013 14:43:57] _...@jabber.org ?OTRv23? nined...@jabber.org/Laptop has requested an Off-the-Record private conversation http://otr.cypherpunks.ca/. However, you do not have a plugin to support that. See http://otr.cypherpunks.ca/ for more information. Both me and my friend have plugins, furthermore all worked well before upgrade. I already wrote about this problem to otr developers, but here is their answer, may be this helps you === My question === These messages are sent when I try to enable plugin message to='h...@jabber.ru' type='chat'subject/subjectbody?OTRv23? *m...@jabber.mipt.ru* has requested an Off-the-Record private conversation. However, you do not have a plugin to support that. See http://otr.cypherpunks.ca/ for more information./body/message message from=h...@jabber.ru/work type=chat to=m...@jabber.mipt.ru id=purple69c5da77 active xmlns=http://jabber.org/protocol/chatstates/ body?OTR:AAMC6AyTZgDELljapwM/zIOE7oBz+0qNx9Jiq8UPCE5BHc0YQd1/6J8w+vNckCyVTCNsBiXCFBQtDLzVeVal1zU3PwDXCovCc6p2Zc+m2fIPx62sXQMvfqwKsXwdCnE6uZcBiyBao2pMlFKqnkxnOJP6eh+Ri38bDdPfFXShz9h+gL3tUg73GtHiTgl+Ta2QcUvz/6ZVm6wBQ68+3Dy+HonJ5YWh+SzAohS/qIDNvec8PfpfhVhM7Qz1K7Cg4SUcJuP0vL8VJySHaqvAwQAAACBcfjTGnBVwYyDOXl0asFthnhjMyzvnbkDBdQxjEPgxEw==./body /message message to='h...@jabber.ru' type='chat'subject/subjectbody?OTR:AAMKAOgMk2YAAADAQj+fcqC/lim4YBnQWhhY3CMIGhl1UC5BjRrMK7B5eqO1c4HYn07LYFfyBEqGdhcQovaokmxqdJjrx835tB5UNQprKjOdKFr2ivONuRk/OSbFJCmCotYVyoenDFdDMWGGQPdvsfnUfSns1IHgSgnSqwi4f0JoYniCjkb8BcCUyLKa6PMJcP1JVxD2HlHd/vqQsFIn0i+cuLKFqbKGA7NePwa1fFNSV7hoxIq2zcWSvY1ao3nmusvrHoBycyrJKl7Q./body/message === Answer === The above message is indeed malformed. It contains a sender instance of 0, which is not allowed. Sounds to me like the psi+ otr plugin isn't implementing the create_instag callback properly? Or else you somehow have an instag file that explicitly contains a 0? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: psi-plus 0.16.132-1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 21 10:09:47 2013 InstallationDate: Installed on 2012-11-28 (357 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: psi-plus UpgradeStatus: Upgraded to saucy on 2013-10-18 (33 days ago) ** Affects: psi-plus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253519 Title: psi+ off-the-record plugin stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psi-plus/+bug/1253519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253519] Re: psi+ off-the-record plugin stopped working
Found workaround: upgrade psi+ from ppa https://launchpad.net/~psi- plus/+archive/ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253519 Title: psi+ off-the-record plugin stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psi-plus/+bug/1253519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227585] Re: nfs mount fails on startup
It seems that after today upgrade (here packages which were updated: http://pastebin.com/UpUQcWai) problem has been fixed. Kernel version is 3.11.0-12-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227585 Title: nfs mount fails on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1227585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227585] Re: nfs mount fails on startup
** Changed in: ubuntu Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227585 Title: nfs mount fails on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1227585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227585] [NEW] nfs mount fails on startup
Public bug reported: After updating to Kubuntu 13.10 beta (kernel version is 3.11.0-7-generic) my nfs share stopped auto-mounting during boot. Here is my fstab: dimanne@Impedance:~$ cat /etc/fstab # file system mount point type options dump pass # / was on /dev/sda1 during installation UUID=328a9124-e5ff-4c13-a7e2-559ee6a20292 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=b3a4a4a4-c563-45c1-9d6b-602b07d66c70 noneswapsw 0 0 # was on /dev/sdb1 UUID=9383ee42-aea8-4098-9533-08d1b9b04e59 /mnt/backupext4 defaults 0 2 # was on /dev/sdc1 UUID=4ad4e84a-1e0e-4cb6-a63a-753d3ffc9ff2 /mnt/freedata ext4defaults 0 2 server:/mnt/media /mnt/media nfs4defaults Also I noticed suspicious messages in dmesg: dimanne@Impedance:~$ dmesg | grep killed [ 23.436063] init: idmapd-mounting (/mnt/media) main process (455) killed by TERM signal [ 26.828198] init: failsafe main process (1119) killed by TERM signal [ 28.352642] init: kdm main process (1757) killed by TERM signal However if I mount nfs share manually (sudo mount -vvv server:/mnt/media /mnt/media) all works perfectly, but at this time I get these messages in dmesg [ 458.804009] NFS: Registering the id_resolver key type [ 458.804024] Key type id_resolver registered [ 458.804026] Key type id_legacy registered [ 473.827828] RPC: AUTH_GSS upcall timed out. [ 473.827828] Please check user daemon is running. A also tried to replace dns name server by ip and adding bg to option-list in fstab - it did not help. What is the problem, how can I fix it? $ lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227585 Title: nfs mount fails on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1227585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1227585] Re: nfs mount fails on startup
It is Kubuntu 13.10 dimanne@Impedance:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Saucy Salamander (development branch) Release:13.10 Codename: saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1227585 Title: nfs mount fails on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1227585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1113395] Re: mount.cifs on 13.04 fails to mount a samba share with 13: Permission Denied
Yes, sec=lanman helps me! Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1113395 Title: mount.cifs on 13.04 fails to mount a samba share with 13: Permission Denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1113395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
