[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Sure thing: $ sudo systemctl status ssh [sudo] password for andrewta: ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s ago Process: 918 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 918 (code=exited, status=255) Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code.../a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-...'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time ove...t. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Start request repeated to...y. Feb 24 14:44:04 janus-40 systemd[1]: Failed to start OpenBSD Secure Shell s...r. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'start...'. Hint: Some lines were ellipsized, use -l to show in full. journalctl -u ssh -- Logs begin at Wed 2016-02-24 14:44:03 CST, end at Sat 2016-02-27 12:32:17 CST. -- Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
After boot starting ssh has never fails to start and correctly runs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
After boot starting ssh has never fails to start and correctly runs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Sure thing: $ sudo systemctl status ssh [sudo] password for andrewta: ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s ago Process: 918 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 918 (code=exited, status=255) Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code.../a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-...'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time ove...t. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Start request repeated to...y. Feb 24 14:44:04 janus-40 systemd[1]: Failed to start OpenBSD Secure Shell s...r. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'start...'. Hint: Some lines were ellipsized, use -l to show in full. journalctl -u ssh -- Logs begin at Wed 2016-02-24 14:44:03 CST, end at Sat 2016-02-27 12:32:17 CST. -- Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549473] [NEW] ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Public bug reported: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug boot ssh wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549473] [NEW] ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Public bug reported: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug boot ssh wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
@ebraz: I Have this problem still. I am on 12.10 on all of my PC's and I have this issue mostly with my ASUS 1225b. My Dell c521 just started doing it too but I noticed something interesting. If I boot up and the keyboard and mouse do not respond and then I leave it alone for up to an hour, when I retry without a reset It seems to have reinitialized the Mouse and Keyboard. Have a dell laptop that runs flawlessly on 12.10 but my main two boxes have developed glitches with 12.10. Wish I had the knowledge to debug these issues myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
I #'d (commented) out the line that said GRUB_CMDLINE_LINUX_DEFAULT=quiet splash Inserted : GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i8042.reset i8042.nomux updated grub Tried with reset, nomux, and both. It fixed the keyboard and touchpad issue but broke the login. I get three separate results. 1)During boot i get the blueish screen that appears during all boots before the splash that covers the boot scroll. No button will take it away and show the boot log scroll. Just stays bluish till I manually reset. 2) The bluish screen turns to a Splash and a generic login box appears. Then typing in my info, brings up a symbol that says that I am logged in but doesnt disappear and goto the desktop. It just stays on the splash and login window. 3) Just like result two except the screen goes blueish and an error window comes up and says failed to login to gnome session. I have checked my install iso with md5sum and the install on the usb. I have reinstalled with UEFI option on the boot menu screen(which doesn't install) and the regular option on that screen 12 times now. The live usb boots and runs flawlessly. The installation works after the first boot and then just crumbles more and more each boot. I am just now taking my first C programming class so this is out of my league but am familiar with bash and willing to fix this if i can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
It may help to know that I am running the most recent version of Ubuntu gnome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1014240] Re: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup
This is an Issue I am having aswell. I will try the update of grub with [GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i8042.reset i8042.nomux] Ill post if this helps me. Thank you for the solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014240 Title: [Asus eeepc 1225B] Keyboard and Touchpad randomly not working at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1014240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049461] Re: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build
Daniel van Vugt (vanvugt): Here is my terminal activity with requested command: andrewta@mars-40:~$ find /var/lib/dkms/fglrx-updates -name make.log andrewta@mars-40:~$ andrewta@mars-40:~$ find /var/lib/dkms/fglrx-updates -name make andrewta@mars-40:~$ find /var/lib/dkms/fglrx-updates /var/lib/dkms/fglrx-updates /var/lib/dkms/fglrx-updates/8.982 /var/lib/dkms/fglrx-updates/8.982/build /var/lib/dkms/fglrx-updates/8.982/build/kcl_acpi.c /var/lib/dkms/fglrx-updates/8.982/build/drm_compat.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_iommu.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_agp.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_str.c /var/lib/dkms/fglrx-updates/8.982/build/drm_proc.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_debug.c /var/lib/dkms/fglrx-updates/8.982/build/firegl_public.c.rej /var/lib/dkms/fglrx-updates/8.982/build/2.6.x /var/lib/dkms/fglrx-updates/8.982/build/2.6.x/Makefile /var/lib/dkms/fglrx-updates/8.982/build/drmP.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_agp.h /var/lib/dkms/fglrx-updates/8.982/build/kcl.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_debug.h /var/lib/dkms/fglrx-updates/8.982/build/dkms.conf /var/lib/dkms/fglrx-updates/8.982/build/kcl.h /var/lib/dkms/fglrx-updates/8.982/build/libfglrx_ip.a /var/lib/dkms/fglrx-updates/8.982/build/kcl_type.h /var/lib/dkms/fglrx-updates/8.982/build/drm.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_iommu.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_io.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_ioctl.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_wait.h /var/lib/dkms/fglrx-updates/8.982/build/firegl_public.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_config.h /var/lib/dkms/fglrx-updates/8.982/build/make.sh /var/lib/dkms/fglrx-updates/8.982/build/fglrxko_pci_ids.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_osconfig.h /var/lib/dkms/fglrx-updates/8.982/build/patches /var/lib/dkms/fglrx-updates/8.982/build/patches/replace-for_each_cpu_mask-with-for_each_possible_cpu.patch /var/lib/dkms/fglrx-updates/8.982/build/patches/replace-do_mmap-and-do_munmap-with-vm_mmap-and-vm_mu.patch /var/lib/dkms/fglrx-updates/8.982/build/patches/fix-build-issue-on-i386-where-TS_USEDFPU-is-no-longe.patch /var/lib/dkms/fglrx-updates/8.982/build/patches/replace-global-lock-with-a-driver-specific-mutex.patch /var/lib/dkms/fglrx-updates/8.982/build/kcl_ioctl.c /var/lib/dkms/fglrx-updates/8.982/build/kcl_wait.c /var/lib/dkms/fglrx-updates/8.982/build/drm_os_linux.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_str.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_io.h /var/lib/dkms/fglrx-updates/8.982/build/firegl_public.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_acpi.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_pci.h /var/lib/dkms/fglrx-updates/8.982/build/kcl_pci.c /var/lib/dkms/fglrx-updates/8.982/source andrewta@mars-40:~$ Please list which to attach or next POA. Clemens Fuchslocher (clemens-fuchslocher): Here's some terminal activity after reffering to your post on bug #1022898. Can you tell if this is the same issue and should I still remove the patch from the archive? andrewta@mars-40:~$ uname -srvmpio Linux 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux andrewta@mars-40:~$ root@mars-40:~# apt-get install fglrx-updates Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: fglrx-amdcccle-updates The following packages will be REMOVED: fglrx fglrx-amdcccle The following NEW packages will be installed: fglrx-amdcccle-updates fglrx-updates 0 upgraded, 2 newly installed, 2 to remove and 38 not upgraded. Need to get 0 B/72.0 MB of archives. After this operation, 1,715 kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 171020 files and directories currently installed.) Removing fglrx-amdcccle ... Removing fglrx ... Removing all DKMS Modules Done. update-alternatives: removing manually selected alternative - switching x86_64-linux-gnu_gl_conf to auto mode update-alternatives: using /usr/lib/pxpress/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode. update-alternatives: warning: skip creation of /usr/bin/amdcccle because associated file /usr/lib/fglrx/bin/amdcccle (of link group x86_64-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/share/applications/ubuntu-amdcccle.desktop because associated file /usr/share/fglrx/amdcccle.desktop (of link group x86_64-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/share/applications/ubuntu-amdccclesu.desktop because associated file /usr/share/fglrx/amdccclesu.desktop (of link group x86_64-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: skip creation of /etc/OpenCL/vendors/amdocl32.icd because associated file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl32.icd (of link group
[Bug 1049461] [NEW] fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build
Public bug reported: I added the fglrx in the list of additional hardware and it activated fine (downloaded and installed) (with its own quirks, thats another story though) I had an option to add fglrx post release updates and when finished it says it failed and to check /var/log/jockey In that log I have no idea how to interpret the data or what to do next so I clicked on the pop up that said send bug report. I am a computer Science major half way through my undergrad. I have decent knowledge about coding and want to contribute to ubuntu one day but I have no idea how to start. I am on Precise Pangolin I expected my asus 1225b to have a working graphics driver that allowed me to easily use the HDMI and not have issues with the sound through HDMI and have the brightness setting to be saved to my preference. What happened is the Post release updates package wont install which I assume has the fix for the issues I have been experiencing. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx-updates 2:8.982-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DKMSKernelVersion: 3.2.0-31-generic Date: Tue Sep 11 22:59:20 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) PackageVersion: 2:8.982-0ubuntu0.1 SourcePackage: fglrx-installer-updates Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049461 Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1049461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049461] Re: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049461 Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1049461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
