[Bug 2061269] Re: Alacritty panics on startup when used on Wayland
Same issue as described. How do I get the update to get alacritty working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061269 Title: Alacritty panics on startup when used on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-alacritty/+bug/2061269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961605] [NEW] Small window boxes are unstable and keep changing color
Public bug reported: The small window boxes are unstable, so they keep changing their color. I have taken screenshots and uploaded them here: https://mega.nz/folder/pctAQaSa#NcHgtpiwKIZs7Alm51f6sA (If you need, I can share the video recording of the screen). The screenshots are for the app BreakTimer, but the issue also happens for other apps, e.g., Zoom. During Zoom meeting, when I share my screen, the small window box containing my and other person's video suffer from this issue, i.e., this small window keeps changing colors. I am then hardly able to see myself or other person in the video and have to hide the video to concentrate. The problem most probably appeared after a recent update. Here, is the relevant information from '/var/log/apt/history.log' file: Start-Date: 2022-02-18 08:20:57 Commandline: aptdaemon role='role-commit-packages' sender=':1.331' Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libdrm-nouveau2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-nouveau2:i386 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), libegl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), signal-desktop:amd64 (5.30.0, 5.32.0), libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), snapd:amd64 (2.51.1+20.04ubuntu2, 2.54.3+20.04.1), ubuntu-advantage-tools:amd64 (27.5~20.04.1, 27.6~20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 3.4.0-2ubuntu1.1), google-chrome-stable:amd64 (98.0.4758.80-1, 98.0.4758.102-1), python-apt-common:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), language-pack-en:amd64 (1:20.04+20210802, 1:20.04+20220211), initramfs-tools-bin:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), linux-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libxnvctrl0:amd64 (470.57.01-0ubuntu0.20.04.2, 470.57.01-0ubuntu0.20.04.3), libdrm-amdgpu1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-amdgpu1:i386 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), ubuntu-drivers-common:amd64 (1:0.9.0~0.20.04.4, 1:0.9.0~0.20.04.5), python3-distupgrade:amd64 (1:20.04.36, 1:20.04.37), ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37), libdrm2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm2:i386 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), language-pack-en-base:amd64 (1:20.04+20210802, 1:20.04+20220211), ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37), libdrm-intel1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:i386 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), mesa-vdpau-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), mesa-vdpau-drivers:i386 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), linux-firmware:amd64 (1.187.25, 1.187.26), mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), initramfs-tools-core:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), initramfs-tools:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), python3-apt:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), mesa-va-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libglx-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libdrm-common:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1) End-Date: 2022-02-18 08:24:41 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 16:35:12 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
[Bug 1959094] [NEW] package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 2
Public bug reported: program stopped ProblemType: Package DistroRelease: Ubuntu 21.04 Package: elpa-magit 2.99.0.git0957.ge8c7bd03-1 ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22 Uname: Linux 5.11.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 26 14:36:23 2022 ErrorMessage: installed elpa-magit package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: magit Title: package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: magit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959094 Title: package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/1959094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Awais Bin Zahid (awais924) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723857 Title: onscreen keyboard appears whenever i touch touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724790] [NEW] Can't see the remote desktop
Public bug reported: Hello, X2GoClient does not work. I cant see the remote desktop. A trick that make the x2goclient work is to open a terminal, then write "export TMP=/tmp", then write "x2goclient --debug". Best regards. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: x2goclient 4.0.5.1-1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 19 11:47:25 2017 InstallationDate: Installed on 2014-08-14 (1161 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) 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: x2goclient UpgradeStatus: Upgraded to xenial on 2017-05-18 (153 days ago) ** Affects: nxcomp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Bug watch added: github.com/ArcticaProject/nx-libs/issues #535 https://github.com/ArcticaProject/nx-libs/issues/535 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724790 Title: Can't see the remote desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nxcomp/+bug/1724790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724790] Re: Can't see the remote desktop
See IRC freenode #x2go on 2017/09/19 [09:08] == jta_1972 [b2c10097@gateway/web/freenode/ip.178.193.0.151] has joined #x2go [09:15] Hello, [09:15] I have a problem. [09:15] The log of x2go are here : https://dpaste.de/VCVT [09:16] Ionic: I built the latest release, 3.5.99.10 [09:16] Line 157: I can't understand why I can't reach the Xdisplay. [09:17] It's working fine, and I've cleaned up the packaging so it doesn't do silly things, like what was causing the cwd to get set weirdly [09:18] I delete .xauthority, reboot : nothing works! [09:18] I had a look a the x2goserver ebuild as well, since actually that seems broken in gentoo currently, but that one is rather long and needs a bit more effort to untangle what's being done [09:18] Must I reinstall a package? [09:20] Ionic: so, I'll stick with this for now as it's working and I am on an up-to-date 3.5 release, and if it does crash it actually writes a core dump now, so I can at least debug it, if the rare crash bug(s) I experience should reoccur. When I feel like spending a weekend on it, I guess I'll try and sort out 3.6 and newer x2goserver [09:20] mbecroft: 3.5.99.x is actually the 3.6-release beta. [09:21] Oh [09:21] Well, then, it basically works fine [09:21] I didn't even need to upgrade x2goserver like you suggested I might [09:22] The current maintainer said he is very busy and would appreciate some help. So I'll at least send him the 3.5.99.10 ebuild for possible inclusion (in 'beta' status) for those who wish to use it [09:23] jta_1972: "Error: Error 2 'No such file or directory' checking '/tmp/user/1003/.X11-unix'." That's your problem. [09:24] I've removed years of crap from the ebuild, which means it is much simpler and installs everyting in the expected way, but could possibly mean it is no longer compatible with some other packages that use it, like freenx and qtnx. I haven't tested that, I'm just guessing. [09:25] Thank your uli421. How can I solve this problem? Must I reinstall X11? [09:25] Ionic: Also, I'm just about to actually test this, but it appears extra nxagent options can be specified in /etc/x2go/x2goagent.options - hopefully no need to hack the x2gostartagent script [09:26] mbecroft: you should upgrade the server as only new version know about the new nx-libs. Older x2goservers will not setup the environment correctly [09:26] jta_1972: it is on you client side. Check /var/log/Xorg.0.log. [09:26] uli421: Well this is what was told to me, but it is actually working fine as far as I can see. What specifically might I expect to not be working right? [09:27] I did have a look at x2goserver, but the ebuilt is way complex and failing in a non-obvious way (even on the *current* version) so I have deferred that for now [09:28] mbecroft: xinerama will not work [09:28] I don't believe I use Xinerama, so if that's all, it's no loss to me for now [09:29] mbecroft: you can check on the server side: ps waux | grep x2goagent -> get pid -> grep -i xinerama /proc/PID/maps -> should NOT use the xinerama lib of NX but from the system. [09:32] jta_1972: I think even a simple xterm or xclock will not work for your client in the current setup [09:33] uli421: let me check [09:34] uli421: It is using the system-supplied libXinerama [09:35] I don't believe there is any NX-supplied libXinerama; at least, if there is, my ebuild does not install it [09:35] Everything I've tested seems to be absolutely fine, except the font path default being bad. The was the only thing I've had to fix (by setting it in my .xsession) [09:35] uli421: thank your. The X0.lor are here https://dpaste.de/axF2. I don't see nothing strange. [09:36] uli421: sorry Xorg.0.log. [09:37] uli421: Specifically, it's using libXinerama from x11-libs/libXinerama, which is part of xorg that is already installed on my system [09:37] Is there anything else I should check? [09:40] jta_1972: sudo lsof -p $(pidof Xorg) | grep unix should show you where your X11-socket is. [09:41] mbecroft: that's good. Please check this: strings /proc/PID/environ | grep LD_ [09:42] uli421: Thank you. My X11 socket is there: /tmp/.X11-unix [09:43] uli421: How can I bind x2go to the socket? [09:44] uli421: There is no output (nothing in the environment beginning with LD_) [09:46] uli421: The output of sudo lsof -p ... is here: https://dpaste.de/gbGC [09:51] Hmm, ok so I need to get my head around "nx/nx" options vs. direct arguments to the nxagent command...maybe I do have to hack x2gostartagent to set those after all. [09:53] jta_1972: I don't know why x2go is trying another socket. Please paste echo $DISPLAY and xauth list $DISPLAY [09:55] == yppo [~144...@h-2-106.a230.priv.bahnhof.se] has left #x2go [] [09:56] uli421: there the output of the instructions. [09:56] jean@sibold-desktop:/$ echo $DISPLAY :0 jean@sibold-desktop:/$ xauth list $DISPLAY sibold-desktop/unix:0 MIT-MAGIC-COOKIE-1 9e2e15549e3b0ea58acd88576c61ca07 [09:56]
[Bug 1720301] Re: Airplane key not recognized
Hello, Well the problem comes after a "sudo update-grub". How can I make the update-grub without messing around the hotkeys? Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720301 Title: Airplane key not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1720301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720301] Re: Airplane key not recognized
Does anybody have an idea? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720301 Title: Airplane key not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1720301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720301] [NEW] Airplane key not recognized
Public bug reported: Hello, Computer : Clevo N240JU Kernel : 4.10.0-35-generic Release : Ubuntu 16.4.03 LTS Keyboard : FR_CH layout For my computer, when I touch the combination [FN]+[F11] it does something unattended. The stroke toggle the bluetooth but don't toggle the wifi. How can I make that the key combination work normaly? Something really strange too : the combination is not recognized in acpi_listen nor xev. But the bluetooth is really toggled... Best regards. Jean Tinguely Awais. PS : in relation with this question https://answers.launchpad.net/ubuntu/+question/658741 PS 2 : detail of more investigations here https://swisslinux.org/forum/viewtopic.php?pid=25060#p25060 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 29 08:35:59 2017 InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720301 Title: Airplane key not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1720301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720301] Re: Airplane key not recognized
It's a fresh install for OEM mode. Now the bug is seen when the user is created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720301 Title: Airplane key not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1720301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006786] [NEW] package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
*** This bug is a duplicate of bug 982609 *** https://bugs.launchpad.net/bugs/982609 Public bug reported: I want to do permanent mounting via linux client and window server. I need to install samba4 but it is giving above error when i use the following command in the terminal. sudo apt-get install samba4 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu May 31 10:55:00 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 126 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: samba4 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006786 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1006786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006786] Re: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126
*** This bug is a duplicate of bug 982609 *** https://bugs.launchpad.net/bugs/982609 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006786 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1006786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000892] [NEW] i forgot my login keyring
Public bug reported: UBUNTU 10.10 - THE MAVERICK MEERKAT - RELEASED IN OCTOBER 2010AND SUPPORTED UNTIL APRIL 2012 I WANT TO CHANGE MY LOGIN KEYRING I HAVE FORGOT MY OLD LOGIN KEYRING ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: seahorse 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Thu May 17 22:09:15 2012 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-dell-maverick-une-20101010-0 ExecutablePath: /usr/bin/seahorse InstallationMedia: Ubuntu 10.10 Maverick - Build i386 LIVE Binary 20101010-01:50 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: seahorse ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug i386 maverick ubuntu-une -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000892 Title: i forgot my login keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1000892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000892] Re: i forgot my login keyring
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000892 Title: i forgot my login keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1000892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541859] Re: unable to restart ubuntu
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/41289512/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/41289513/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/41289514/ArecordDevices.txt ** Attachment added: BootDmesg.gz http://launchpadlibrarian.net/41289515/BootDmesg.gz ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/41289516/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt http://launchpadlibrarian.net/41289517/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt http://launchpadlibrarian.net/41289518/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/41289519/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41289520/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/41289521/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/41289522/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/41289523/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/41289524/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/41289525/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/41289526/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/41289527/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/41289528/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/41289529/UdevLog.txt ** Attachment added: WifiSyslog.gz http://launchpadlibrarian.net/41289530/WifiSyslog.gz -- unable to restart ubuntu https://bugs.launchpad.net/bugs/541859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541859] [NEW] unable to restart ubuntu
Public bug reported: when ever i restart ubuntu a command proment comes and in the end it say your system is going to restart something like that but it never does. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: awais 1632 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 28 Simple ctrls : 20 Date: Thu Mar 18 17:04:17 2010 DistroRelease: Ubuntu 9.10 Failure: oops InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=/dev/sda1 loop=/hostname/disks/root.disk ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-20.58-generic RelatedPackageVersions: linux-backports-modules-2.6.31-20-generic N/A linux-firmware 1.26 RfKill: SourcePackage: linux Tags: kernel-oops Title: WARNING: at /build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xcb/0xe0() Uname: Linux 2.6.31-20-generic i686 dmi.bios.date: 08/18/2004 dmi.bios.vendor: Intel Corp. dmi.bios.version: SR84510A.46T.0012.P05.0408182053 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrSR84510A.46T.0012.P05.0408182053:bd08/18/2004:svn:pn:pvr:rvn:rn:rvr:cvn:ct2:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops -- unable to restart ubuntu https://bugs.launchpad.net/bugs/541859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
