[Bug 1880503] [NEW] aarch64 kernel module for exfat not in raspberry pi 4 build
Public bug reported: exfat support appears to be missing in linux 5.4.0-1011=raspi (Ubuntu 20.04) modprobe exfat #modprobe: FATAL: Module exfat not found in directory /lib/modules/5.4.0-1011-raspi Is it possible to add this? Thanks ** Affects: ubuntu Importance: Undecided Status: New ** Tags: focal kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880503 Title: aarch64 kernel module for exfat not in raspberry pi 4 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Re: CIFS accesses DFS referral with wrong Kerberos ticket
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS accesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Re: CIFS accesses DFS referral with wrong Kerberos ticket
I have tested 5.4.0-21.25 from focal-proposed. The DFS referrals work correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS accesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Re: CIFS accesses DFS referral with wrong Kerberos ticket
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS accesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Re: CIFS accesses DFS referral with wrong Kerberos ticket
I tried running kernel 5.4.0-14-generic from the focal repositories. The behavior is the same as with a 5.3 kernel. ** Summary changed: - CIFS acesses DFS referral with wrong Kerberos ticket + CIFS accesses DFS referral with wrong Kerberos ticket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS accesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327621/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327616/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327618/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327619/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Re: CIFS acesses DFS referral with wrong Kerberos ticket
apport information ** Tags added: apport-collected ** Description changed: kubuntu 19.10 with kernel 5.3.0-29-generic and64. This looks like a regression in the kernel CIFS module after the 4.15 & 5.0 kernels. These earlier kernels follow the DFS referrals without error. The problem: - Use mount.cifs with kerberos authentication to mount a samba server hosting a DFS root. You will get a KRB ticket for the "dfs_root" machine. - Attempt to access a host a host via a DFS referral (call this "target_host") - Access will fail with "Permission Denied". - Use Wireshark to monitor CIFS and KRB traffic. - The kernel attempts to authenticate to "target_host" using the KRB ticket for "dfs_root". Note: - A DFS target running Win2008R2 will reply with STATUS_MORE_PROCESSING_REQUIRED, then the kernel will get a KRB ticket for "target_host" and use it. The connection is then successful. - A DFS target running Samba 4.7.6 will reply with STATUS_LOGON_FAILURE. The connection fails. Expected Result: - Successful connection. - The kernel should get a KRB ticket for "target_host" and use it. (This is what kernels 4.15 and 5.0 do [and a Windows client]) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: stephen1839 F pulseaudio + /dev/snd/controlC2: stephen1839 F pulseaudio + /dev/snd/controlC0: stephen1839 F pulseaudio + /dev/snd/controlC1: stephen1839 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=UUID=4df5ccea-5eb4-45e3-a0b0-7b1311fdaba5 + InstallationDate: Installed on 2018-11-09 (459 days ago) + InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) + MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-29-generic root=UUID=f009da0b-176e-49e6-a6a0-bb594e6754a8 ro rootflags=subvol=@ + ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-29-generic N/A + linux-backports-modules-5.3.0-29-generic N/A + linux-firmware1.183.3 + RfKill: + + Tags: eoan + Uname: Linux 5.3.0-29-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-20 (114 days ago) + UserGroups: adm bacula cdrom kvm libvirt lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 09/08/2010 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F10c + dmi.board.name: GA-MA790X-UD4P + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10c:bd09/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: GA-MA790X-UD4P + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327613/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327626/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327620/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327622/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327623/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327624/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327625/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327614/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327617/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1862858/+attachment/5327615/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862858] [NEW] CIFS acesses DFS referral with wrong Kerberos ticket
Public bug reported: kubuntu 19.10 with kernel 5.3.0-29-generic and64. This looks like a regression in the kernel CIFS module after the 4.15 & 5.0 kernels. These earlier kernels follow the DFS referrals without error. The problem: - Use mount.cifs with kerberos authentication to mount a samba server hosting a DFS root. You will get a KRB ticket for the "dfs_root" machine. - Attempt to access a host a host via a DFS referral (call this "target_host") - Access will fail with "Permission Denied". - Use Wireshark to monitor CIFS and KRB traffic. - The kernel attempts to authenticate to "target_host" using the KRB ticket for "dfs_root". Note: - A DFS target running Win2008R2 will reply with STATUS_MORE_PROCESSING_REQUIRED, then the kernel will get a KRB ticket for "target_host" and use it. The connection is then successful. - A DFS target running Samba 4.7.6 will reply with STATUS_LOGON_FAILURE. The connection fails. Expected Result: - Successful connection. - The kernel should get a KRB ticket for "target_host" and use it. (This is what kernels 4.15 and 5.0 do [and a Windows client]) ** Affects: linux (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/1862858 Title: CIFS acesses DFS referral with wrong Kerberos ticket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852752] [NEW] DPMS does not switch off the monitor back light
Public bug reported: 'xset dpms force off' blanks the screen but does not switch off the HDMI (LCD) monitor backlight. 'xset -q' shows DPMS is enabled. 'tvservice -o' does switch off the monitor. No warnings/errors related to dpms in /var/log/XOrg.0.log Not sure if this is a xorg, kernel, libxcb-dpms0 or other issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1012.14-raspi2 5.3.7 Uname: Linux 5.3.0-1012-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Nov 15 18:33:52 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:17:19:0B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 eoan ubuntu uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852752 Title: DPMS does not switch off the monitor back light To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588952] Re: krdc does not agree with kdewallet manager about where the wallet lives
I noticed the same thing here. I see the krdc wallet won't remain open, so I have to unlock it every use. After some research I found: ~/.kde/share/apps/kwallet is used for kde4 applications only. ~/.local/share/kwallet is used for kde5 applications only. The kde4/5 wallet encryption is not compatible, so linking will not work. Probably the cipher is different between the kde4 and kde5 wallets. krdc is a kde4 application, so uses the ".kde" wallet. The KDE Wallet Manager is kde5, so uses the ".local" wallet. I assume the only 'fix' is a kde5 version of krdc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588952 Title: krdc does not agree with kdewallet manager about where the wallet lives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krdc/+bug/1588952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475040] [NEW] screen corruption after login
Public bug reported: I was using ubuntu 3.19.0.22 (15.04). On starting the computer, the login screen was displayed. I logged in and then shortly after the display appeared to crash (I have two monitors) bys displaying a bizarre black and white pattern. The system did not respond to ctrl-alt-del . Pressing one of the mouse buttons caused the display to revert to a regular Ubuntu background. I rebooted, but had the same problem. I then used the advanced login options to start up using kernel 3.19.0.15 and all appear to work OK. lsb_release -rd Description:Ubuntu 15.04 Release:15.04 ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: IMG_20150715_221321.jpg https://bugs.launchpad.net/bugs/1475040/+attachment/4429587/+files/IMG_20150715_221321.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475040 Title: screen corruption after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1475040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452920] Re: Dolphin terminal panel doesn't work with KF5
A recent update has fixed the problem for me. The package versions are now: dolphin 4:15.04.1-0ubuntu1~ubuntu15.04~ppa6 konsole 4:15.04.1-0ubuntu1~ubuntu15.04~ppa1 konsole-kpart 4:15.04.1-0ubuntu1~ubuntu15.04~ppa1 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1452920 Title: Dolphin terminal panel doesn't work with KF5 To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1452920/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1445916] Re: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I get the same error for the same package on apt-get upgrade, except that the first significant warning is 'insserv: warning: script 'K01smfpd' missing LSB tags and overrides'. My architecture is x86_64. Is there a workaround for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445916 Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1445916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400521] [NEW] Black boxes are drawn around various windows on the screen
Public bug reported: Black rectangles appear where graphic items like buttons or the like would be expected. This seems to affect a lot of applications. I have also seen it when hovering over a tab in Firefox and Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Mon Dec 8 22:35:43 2014 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2011-02-14 (1393 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: LANGUAGE=en_GB PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2014-05-10 (212 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Attachment added: Screenshot from 2014-12-08 22:38:13.png https://bugs.launchpad.net/bugs/1400521/+attachment/4276588/+files/Screenshot%20from%202014-12-08%2022%3A38%3A13.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400521 Title: Black boxes are drawn around various windows on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1400521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1373968] Re: GUI does not work after update
I decided to upgrade to 14.10 in the end and that made the problem go away. On 2 Nov 2014 05:30, Alejandro Dubrovsky al...@organicrobot.com wrote: I had the same issue. Turned out to be that the kernel that was actually running was not the same as the one that was being installed and, supposedly, the nvidia driver was compiling against. Do a 'uname -a' and check to see if you are running what you think you are running (in my case 3.11.0 vs 3.13.0). Also, an 'lsmod | grep nvidia' showed nothing on mine. Installing linux-generic and a reboot solved the issue for me (ie 'sudo apt-get install linux-generic') -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: After logging into PC today and running the software updater, various system updates were downloaded. I was promped to restart, which I did. At reboot, the system would get as far as displaying the login screen. After I entered my password, the system appears to hang, with no disk activity. I have a dual monitor system, but only the left monitor is active, in that it displays a purple Ubuntu splash screen, without the login box. I have tried restarting a number of times, but the result is always the same. I can log in by using the advanced options and drop into the root console. I am using Ubuntu 14.04.1 LTS. uname -a reports 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Hardware is a Dell Precision T3400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387001] Re: Automatic update crashes: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build
I believe I have the same problem. I took the attached screenshot from the Crash Report dialog. ** Attachment added: nvidia install problem Screenshot from 2014-10-29 22:18:39.png https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1387001/+attachment/4248550/+files/nvidia%20install%20problem%20Screenshot%20from%202014-10-29%2022%3A18%3A39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387001 Title: Automatic update crashes: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1387001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1365695] Re: No longer able to use GUI after update
@Alberto - I followed the steps you gave above but the problem remains. It has made no obvious difference after reboot: system hangs after login with just the left hand monitor displaying an Ubuntu background. On Mon, Oct 13, 2014 at 3:04 PM, Alberto Milone alberto.mil...@canonical.com wrote: @steveb: Please follow these steps: sudo add-apt-repository ppa:canonical-x/x-staging (say yes to the all the questions) sudo apt-get update sudo apt-get install xserver-xorg-video-intel Remove nvidia: sudo apt-get --purge remove nvidia-331 (or nvidia-331-updates, according to what you installed) sudo apt-get install nvidia-331 Restart your computer. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Confirmed Status in “ubuntu-drivers-common” source package in Trusty: Triaged Status in “xserver-xorg-video-intel” source package in Trusty: Incomplete Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension GLX missing on display :0' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+subscriptions -- You received
Re: [Bug 1365695] Re: No longer able to use GUI after update
I don't know if the bug I reported 1373968 , is the same as 1365695 or not, so I reported mine as a separate bug. My symptoms are that system boots as normal to a Ubuntu GUI login screen. After entering my password the login screen is replaced by an Ubuntu background (14.04 LTS in the bottom left corner of the left hand monitor (I have a dual monitor setup)). And then no further updates to the screen. The right hand monitor is inactive the whole time. On Tue, Oct 14, 2014 at 10:26 AM, Alejandro Dubrovsky al...@organicrobot.com wrote: Some people are reporting the blank (background) screen before the login, some after. Are they the same bug? (I suffer from the after-login variety) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Confirmed Status in “ubuntu-drivers-common” source package in Trusty: Triaged Status in “xserver-xorg-video-intel” source package in Trusty: Incomplete Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension GLX missing on display :0' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to:
Re: [Bug 1365695] Re: No longer able to use GUI after update
I would be delighted to help test the package. What do I need to do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1373968] Re: GUI does not work after update
Just checked, they are all .conf files -Steve On 3 Oct 2014 01:40, Pär Lindfors pa...@lysator.liu.se wrote: Do you have any files in /etc/modprobe.d/ that does not have a .conf extension? If you have, then this could be a duplicate of bug 1376966. Log in to the root console, and run the following to check: ls /etc/modprobe.d/|grep -v '\.conf$' -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update Status in “ubuntu-drivers-common” package in Ubuntu: New Bug description: After logging into PC today and running the software updater, various system updates were downloaded. I was promped to restart, which I did. At reboot, the system would get as far as displaying the login screen. After I entered my password, the system appears to hang, with no disk activity. I have a dual monitor system, but only the left monitor is active, in that it displays a purple Ubuntu splash screen, without the login box. I have tried restarting a number of times, but the result is always the same. I can log in by using the advanced options and drop into the root console. I am using Ubuntu 14.04.1 LTS. uname -a reports 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Hardware is a Dell Precision T3400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373968] Re: GUI does not work after update
Just tried the package downgrade (apt-get install ubuntu-drivers- common=1:0.2.91.4) and a couple of reboots but the problem is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373968] [NEW] GUI does not work after update
Public bug reported: After logging into PC today and running the software updater, various system updates were downloaded. I was promped to restart, which I did. At reboot, the system would get as far as displaying the login screen. After I entered my password, the system appears to hang, with no disk activity. I have a dual monitor system, but only the left monitor is active, in that it displays a purple Ubuntu splash screen, without the login box. I have tried restarting a number of times, but the result is always the same. I can log in by using the advanced options and drop into the root console. I am using Ubuntu 14.04.1 LTS. uname -a reports 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Hardware is a Dell Precision T3400 ** Affects: ubuntu-drivers-common (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/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373968] Re: GUI does not work after update
I am able to boot from a 14.04 live USB drive, both monitors working, so I do not think there is a graphics hardware problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814770] Re: oneiric kubuntu printer configuration fails
I also looked at other systems with Oneiric installed. a) an upgrade from Natty - works correctly b) a new Oneiric install - works correctly I found that my problem was caused by an entry in /etc/cups/printers.conf for a printer that no longer exists. The entry was for the DefaultPrinter section. I fixed it by these steps: Stop CUPS, so we can edit the conf file safely /etc/init.d/cups stop Edit /etc/cups/printers.conf from: DefaultPrinter ...the non-existent printer entries... /Printer Printer ...a valid printers entries... /Printer to: DefaultPrinter ...a valid printers entries... /Printer Restart CUPS /etc/init.d/cups start I can only assume that system-config-printer-kde needs better error handling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to system-config-printer-kde in Ubuntu. https://bugs.launchpad.net/bugs/814770 Title: oneiric kubuntu printer configuration fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer-kde/+bug/814770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814770] Re: oneiric kubuntu printer configuration fails
I have this problem on Oneiric, using package system-config-printer-kde 4:4.7.2-0ubuntu1~ppa2 The console error from systemsettings ends with: File /usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py, line 1311, in fillPrinterOptions ppd.markDefaults() AttributeError: 'bool' object has no attribute 'markDefaults' My limited Python tells me that object ppd is set to a boolean, instead of a printer object. The code has places where ppd = False is used upon errors, which would lead to this message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to system-config-printer-kde in Ubuntu. https://bugs.launchpad.net/bugs/814770 Title: oneiric kubuntu printer configuration fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer-kde/+bug/814770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
I have been running 2.6.38-11 for 6 weeks now, and there have been no more occurrences of the problem. (kernel is 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux) The cx88 driver patches have fixed the problem for me. ** Changed in: linux (Ubuntu) Status: Incomplete = 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/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
julianw, I have just installed 2.6.38-11.48 and the problems seem to be gone. I will post another comment after some more extensive use of the new kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
Looking into the changes from 2.6.25 to 2.6.38 there were many locking changes, which could be the problem: --- linux-source-2.6.35/drivers/media/video/cx88/cx88-blackbird.c 2010-08-02 08:11:14.0 +1000 +++ linux-source-2.6.38/drivers/media/video/cx88/cx88-blackbird.c 2011-03-15 12:20:32.0 +1100 @@ -12 +12 @@ - * Includes parts from the ivtv driver( http://ivtv.sourceforge.net/), + * Includes parts from the ivtv driver http://sourceforge.net/projects/ivtv/ @@ -36 +35,0 @@ -#include linux/smp_lock.h @@ -1060 +1059 @@ - lock_kernel(); + mutex_lock(dev-core-lock); @@ -1068 +1067 @@ - unlock_kernel(); + mutex_unlock(dev-core-lock); @@ -1076 +1075 @@ - unlock_kernel(); + mutex_unlock(dev-core-lock); @@ -1086 +1085 @@ - unlock_kernel(); + mutex_unlock(dev-core-lock); @@ -1097 +1096 @@ - fh); + fh, NULL); @@ -1102 +1100,0 @@ - unlock_kernel(); @@ -1105 +1103 @@ - + mutex_unlock(dev-core-lock); @@ -1122,0 +1121,2 @@ + + mutex_lock(dev-core-lock); @@ -1124,0 +1125 @@ + mutex_unlock(dev-core-lock); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
This configuration DOES HAVE the konsole problem for me: kernel 2.6.35-28-generic (amd64 maverick kernel) OR 2.6.38-8-generic (amd64 natty kernel) xserver-xorg 1.10.1-1ubuntu1 (natty package) nvidia-current 270.41.06-0ubuntu1 (natty package) This configuration DID NOT have the problem for me: kernel 2.6.35-28-generic (amd64 maverick kernel) xserver-xorg 1.9.0-0ubuntu7.3 (maverick package) nvidia-current 270.41.06-0ubuntu~xup~maverick (ubuntu x-swat package) xserver-xorg being the only difference. It looks like either an Xorg 1.10 problem, or some interaction between the nVidia driver and Xorg 1.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
(This is a GeForce GTS 250 card) A konsole / Xorg crash also gives 8 identical syslog entries: NVRM: Xid (:01:00): 13, 0001 5097 15e0 0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
After reviewing the dmesg files I posted, I can see a common call path to the problem: v4l2_open - video_open - mutex_lock The path is always related to the cx88xx drivers, for a DVB card. Is it the DVB card drivers? To test this I added a blacklist-tmp.conf file into /etc/modprobe.d containing: blacklist cx2341x blacklist cx88_blackbird blacklist cx88_dvb blacklist cx88_vp3054_i2c blacklist cx88_alsa blacklist cx8802 blacklist cx8800 blacklist cx88xx After a reboot, the problem does not appear on any of the kernels tested. That looks like the problem is in the cx88 drivers, and how they use mutex_lock(). Looking at the kernel sources, mutex_lock() is probably a widely used piece of kernel code, and problems there would be quite widespread (I guess?...) The next step will be to look at what has changed in the cx88 drivers from 2.6.35 to 2.6.38 Regarding comment #6 I do not think it relates to this issue, but in searches I have seen other similar bugs related to the kernel scheduler. I am not sure if it was the IO or the Process scheduler. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] [NEW] Multiple Tasks - blocked for more than 120 seconds INFO message
Public bug reported: After upgrade from kubuntu 10.10 to kubuntu 11.04 (amd64) tasks hang in disk sleep status. dmesg reports messages like INFO: task knotify4:2567 blocked for more than 120 seconds. Normal desktop apps fail, and cause the error message (eg digikam, amarok, knotify4, dolphin) kernels used, and the result are: 2.6.38-8-generic - problem IS present (this is the Natty generic kernel) 2.6.38-8-server - problem IS present (this is the Natty server kernel) 2.6.38-02063804 - problem IS present (this is the mainline kernel) 2.6.35-28-generic - problem is NOT evident (this is the Maverick generic kernel) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image 2.6.38.8.22 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: stephen2852 F pulseaudio /dev/snd/controlC1: stephen2852 F pulseaudio /dev/snd/controlC0: stephen2852 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a102,00100101' Controls : 39 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x807'/'USB Device 0x46d:0x807 at usb-:00:12.2-1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0807' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 6144 [100%] [30.00dB] [on] Card2.Amixer.info: Card hw:2 'CX8811'/'Conexant CX8811 at 0xf900' Mixer name : 'CX88' Components : '' Controls : 3 Simple ctrls : 2 Date: Sun May 1 20:19:45 2011 HibernationDevice: RESUME=UUID=4760f9c8-efe2-4d08-951f-19f3765dde23 MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=059a7c5a-ff5c-4fd4-bbb6-7ee66545f8d5 ro RelatedPackageVersions: linux-restricted-modules-2.6.35-28-generic N/A linux-backports-modules-2.6.35-28-generic N/A linux-firmware 1.52 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10a dmi.board.name: GA-MA790X-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10a:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790X-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
** Attachment added: dmesg for s.6.38-8-generic kernel https://bugs.launchpad.net/bugs/774773/+attachment/2102550/+files/dmesg.errors-2.6.38-8-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
** Attachment added: dmesg for 2.6.38-8-server kernel https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774773/+attachment/2102572/+files/dmesg.errors-2.6.38-8-server.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
** Attachment added: dmesg for 2.6.38-02063804 kernel https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774773/+attachment/2102575/+files/dmesg.errors-2.6.38-02063804.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774773] Re: Multiple Tasks - blocked for more than 120 seconds INFO message
The system is functional using the 2.6.35 kernel, so I can gather more data as necessary by starting up the 2.6.38 kernels. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774773 Title: Multiple Tasks - blocked for more than 120 seconds INFO message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 393240] [NEW] Samsung Q210 - No released events on brightness change
Public bug reported: Binary package hint: hal-info In reply to the original bug report: https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/52 The brightness keys make the brightness go up and down, but when using input-events, there is no released event for either key: 21:36:42.979320: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed 21:36:42.979325: EV_SYN code=0 value=0 21:36:43.266034: EV_MSC code=4 value=137 21:36:43.266064: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed 21:36:43.266068: EV_SYN code=0 value=0 21:36:43.619331: EV_MSC code=4 value=176 The result, is that when the brightness is turned down, it goes right down to zero or vise versa. The keyboard then becomes locked and I need to switch to the console and back to the desktop to fix it. Thanks ** Affects: hal-info (Ubuntu) Importance: Undecided Status: New -- Samsung Q210 - No released events on brightness change https://bugs.launchpad.net/bugs/393240 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 393240] Re: Samsung Q210 - No released events on brightness change
I now notice that a single press of FN + Brightness Up/Down is changing the brightness 1 notch, but only on the On Screen Display that appears in the top right of the screen, the brightness itself does not change! input-events is not showing any new release events now, making this problem slighty intermitent. I tried acpi_listen and nothing interesting appeared to happen. So: - No released events with input-events - Intermittent problem where brightness key appears to be un-released, locking keyboard and forcing brightness OSD to extreme low/high. - Brightness of screen never changes. Any ideas? (Samsung Q210 with Ubuntu 9.04) -- Samsung Q210 - No released events on brightness change https://bugs.launchpad.net/bugs/393240 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 333352] Re: Samsung Q210 brightness keys do not work
Sorry, I was using a terminal rather than the console. Here are the expected key mappings: code=4, value=136 = brightness up code=4, value=137 = brightness down system.hardware.primary_video.product = 1768 (0x6e8) (int) system.hardware.primary_video.vendor = 4318 (0x10de) (int) system.hardware.product = 'Q210' (string) system.hardware.serial = 'CV7893EQ700048' (string) system.hardware.uuid = 'A0F81071-D21D-B211-8000-D7586BB60F5B' (string) system.hardware.vendor = 'SAMSUNG ELECTRONICS CO., LTD.' (string) system.hardware.version = 'Not Applicable' (string) Thanks -- Samsung Q210 brightness keys do not work https://bugs.launchpad.net/bugs/52 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 333352] Re: Samsung Q210 brightness keys do not work
I'm having trouble with this step: attach to the devices one by one using sudo input-events devnum (in the input-utils package), using the number returned by lshal as part of input.device, and press the hotkey to see if an event is generated It's quite clear which device is which, but no matter what I press (normal key, function key, whatever), input-events never picks up anything: waiting for events timeout, quitting All the beforehand steps have been fine until this point (including disabling gnome-power and gnome-settings). -- Samsung Q210 brightness keys do not work https://bugs.launchpad.net/bugs/52 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 333352] [NEW] Samsung Q210 brightness keys do not work
Public bug reported: Binary package hint: hal-info Running Intrepid on a Samsung Q210 laptop. The brightness keyboard keys have no effect (FN + Up/Down arrows). xev shows no events when these keys are pressed. Sleep, volume, mute, touchpad on/off all work as expected, including on- screen graphics where appropiate. ** Affects: hal-info (Ubuntu) Importance: Undecided Status: New -- Samsung Q210 brightness keys do not work https://bugs.launchpad.net/bugs/52 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 333352] Re: Samsung Q210 brightness keys do not work
** Attachment added: lshal http://launchpadlibrarian.net/23009330/lshal ** Description changed: Binary package hint: hal-info Running Intrepid on a Samsung Q210 laptop. The brightness keyboard keys have no effect (FN + Up/Down arrows). xev shows no events when these keys are pressed. - Sleep, volume, mute, touchpad on/off all work as expected, into on + Sleep, volume, mute, touchpad on/off all work as expected, including on- screen graphics where appropiate. -- Samsung Q210 brightness keys do not work https://bugs.launchpad.net/bugs/52 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 295251] Re: Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
I have a Samsung Q210 laptop running Intrepid. The volume keys work perfectly (including on-screen graphic), but the brightness keys have no effect at all. xev shows no events when these keys are pressed. I have updated hal-info but there has been no effect. Anything else I should try? Thanks. -- Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect https://bugs.launchpad.net/bugs/295251 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 325503] Re: Grub not installed properly/at all on Sun Microsystems Blade Server 6048, blade type: X6250, When installing Ubuntu 8.10 server edition.
** Summary changed: - Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. + Grub not installed properly/at all on Sun Microsystems Blade Server 6048, blade type: X6250, When installing Ubuntu 8.10 server edition. -- Grub not installed properly/at all on Sun Microsystems Blade Server 6048, blade type: X6250, When installing Ubuntu 8.10 server edition. https://bugs.launchpad.net/bugs/325503 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 325503] Re: Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition.
** Description changed: System: Sun Microsystems Blade Server 6048 Blade type: X6250 Quad-core, Intel Xeon 5300 series processors Drives: 4x146gb sata drives Raid 0 (500GB) Software: Ubuntu Server edition 8.10 (ubuntu-8.10-server-i386.iso) Bug Info: for some reason Ubuntu 8.10 completes its install with out problems, However grub installs to the wrong location, or fails to install at all (not sure which). So the OS will install, but will then fail to load after a reboot as the bios fails to find grub in the primary boot sector. System justs hangs with a flashing prompt on a blank screen. Work around: Steps to install 1)On booting at the bios splash screen, hit f3 or f8 (f8 for remote keyboard) to enter the boot device selection window. If you miss the splash screen you can hit f3 or f8 again just after the raid controller sets its self up. 2)Boot from the install CD. follow the install instructions, hear are my recommended options: Yes to use the Active raid volume Install security updates automaticaly - Name Server 129.156.86.11 + Name Server (name.server.ip.address) Install LAMP 3)After the system install it will reboot but will not be able to progress after bios posts. So press f3 or f8 to enter the boot device menu. Boot from the install cd. When the CD loads choose the option to rescue broken system. When the broken system option has loaded choose to re install grub. This option will require you to enter a Device for the boot loader installation enter: (hd0) Then reboot the system Ubuntu and grub will now load correctly --End of Work around--- So its easy enough to fix the problem, but i felt it should be made aware of Hope you find this information useful let me know if i can be of any more assistance Steve Brown Sun Microsystems Global Service Lab -- Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. https://bugs.launchpad.net/bugs/325503 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 325503] Re: Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition.
** Summary changed: - Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing prompt on a blank screen. + Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. -- Grub not installed properly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. https://bugs.launchpad.net/bugs/325503 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 325503] Re: Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing pr
Continued testing Ubuntu with the x6250 blades, the 8.10 desktop edition installs OS and grub correctly and boots first time with out a problem. Seems the problem is only with the server edition. -- Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing prompt on a blank screen. https://bugs.launchpad.net/bugs/325503 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 325503] [NEW] Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing
Public bug reported: System: Sun Microsystems Blade Server 6048 Blade type: X6250 Quad-core, Intel Xeon 5300 series processors Drives: 4x146gb sata drives Raid 0 (500GB) Software: Ubuntu Server edition 8.10 (ubuntu-8.10-server-i386.iso) Bug Info: for some reason Ubuntu 8.10 completes its install with out problems, However grub installs to the wrong location, or fails to install at all (not sure which). So the OS will install, but will then fail to load after a reboot as the bios fails to find grub in the primary boot sector. System justs hangs with a flashing prompt on a blank screen. Work around: Steps to install 1)On booting at the bios splash screen, hit f3 or f8 (f8 for remote keyboard) to enter the boot device selection window. If you miss the splash screen you can hit f3 or f8 again just after the raid controller sets its self up. 2)Boot from the install CD. follow the install instructions, hear are my recommended options: Yes to use the Active raid volume Install security updates automaticaly Name Server 129.156.86.11 Install LAMP 3)After the system install it will reboot but will not be able to progress after bios posts. So press f3 or f8 to enter the boot device menu. Boot from the install cd. When the CD loads choose the option to rescue broken system. When the broken system option has loaded choose to re install grub. This option will require you to enter a Device for the boot loader installation enter: (hd0) Then reboot the system Ubuntu and grub will now load correctly --End of Work around--- So its easy enough to fix the problem, but i felt it should be made aware of Hope you find this information useful let me know if i can be of any more assistance Steve Brown Sun Microsystems Global Service Lab ** Affects: grub (Ubuntu) Importance: Undecided Status: New -- Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing prompt on a blank screen. https://bugs.launchpad.net/bugs/325503 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 325503] Re: Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing pr
ubuntu-8.10-server-i386.iso This was the install image used on the blades. (this bug was seen on four separate x6250 blades) ** Description changed: System: Sun Microsystems Blade Server 6048 Blade type: X6250 Quad-core, Intel Xeon 5300 series processors Drives: 4x146gb sata drives Raid 0 (500GB) - Software: Ubuntu Server edition 8.10 + Software: Ubuntu Server edition 8.10 (ubuntu-8.10-server-i386.iso) Bug Info: - for some reason Ubuntu 8.10 completes its install with out problems, However grub installs to the wrong location, or forgets to install it at all (not sure which). - So the system will install, but will then fail to boot as the bios fails to boot grub, from the primary boot sector. + for some reason Ubuntu 8.10 completes its install with out problems, However grub installs to the wrong location, or fails to install at all (not sure which). + So the OS will install, but will then fail to load after a reboot as the bios fails to find grub in the primary boot sector. System justs hangs with a flashing prompt on a blank screen. Work around: Steps to install 1)On booting at the bios splash screen, hit f3 or f8 (f8 for remote keyboard) to enter the boot device selection window. If you miss the splash screen you can hit f3 or f8 again just after the raid controller sets its self up. 2)Boot from the install CD. follow the install instructions, hear are my recommended options: Yes to use the Active raid volume Install security updates automaticaly Name Server 129.156.86.11 Install LAMP 3)After the system install it will reboot but will not be able to progress after bios posts. So press f3 or f8 to enter the boot device menu. Boot from the install cd. When the CD loads choose the option to rescue broken system. When the broken system option has loaded choose to re install grub. This option will require you to enter a Device for the boot loader installation enter: (hd0) Then reboot the system Ubuntu and grub will now load correctly --End of Work around--- So its easy enough to fix the problem, but i felt it should be made aware of Hope you find this information useful let me know if i can be of any more assistance Steve Brown Sun Microsystems Global Service Lab -- Grub not installed propperly/at all on Sun Microsystems Blade Server 6048 blade type X6250, When installing Ubuntu 8.10 server edition. Bios posts then system hangs with a flashing prompt on a blank screen. https://bugs.launchpad.net/bugs/325503 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 292836] Re: Cannot browse samba shares
I have this problem on 8.10, but only on one device. In Nautilus I can see files in shares on WinXP machines, and I can see files in shares on a Maxtor Shared Storage NAS. I can see shares on a Buffalo Terastation Pro, but when viewed in Nautilus they appear empty. If I use smb://nnn.nnn.nnn.nnn/share in Firefox, I can see file and folder names, but they are truncated - the last character of the filename is missing. Needless to say the Terastation is my main data store, so this is a showstopper for me - I'm staying with Hardy until it is sorted, with Intrepid on a partition so I can test this from time to time so I know when it is fixed. -- Cannot browse samba shares https://bugs.launchpad.net/bugs/292836 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 292836] Re: Cannot browse samba shares
I have this problem on 8.10, but only on one device. In Nautilus I can see files in shares on WinXP machines, and I can see files in shares on a Maxtor Shared Storage NAS. I can see shares on a Buffalo Terastation Pro, but when viewed in Nautilus they appear empty. If I use smb://nnn.nnn.nnn.nnn/share in Firefox, I can see file and folder names, but they are truncated - the last character of the filename is missing. Needless to say the Terastation is my main data store, so this is a showstopper for me - I'm staying with Hardy until it is sorted, with Intrepid on a partition so I can test this from time to time so I know when it is fixed. -- Cannot browse samba shares https://bugs.launchpad.net/bugs/292836 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 293806] [NEW] Upgrade failed Could not reso lve ‘gb.archive.ubuntu.com’
Public bug reported: When upgrading from Hardy to 8.10 the Update Manager (process) reports a number of unresolved addresses and errors, see the attachment for the full list. Errors begin: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/f /foomatic-db-engine/foomatic-db-engine_4.0.0~bzr219-0ubuntu1_i386.deb Could not resolve ‘gb.archive.ubuntu.com’ Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/g/gcalctool/gcalctool_5.24.1-0ubuntu1_i386.deb Could not resolve ‘gb.archive.ubuntu.com’ Failed to fetch http://gb.archive.ubuntu.com/ubuntu/pool/main/g/gconf- editor/gconf-editor_2.24.1-0ubuntu1_i386.deb Could not resolve ‘gb.archive.ubuntu.com’ ** Affects: upgrade-system (Ubuntu) Importance: Undecided Status: New -- Upgrade failed Could not resolve ‘gb.archive.ubuntu.com’ https://bugs.launchpad.net/bugs/293806 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 293806] Re: Upgrade failed Could not resolve ‘gb.archive.ubuntu.com’
** Attachment added: Upgrade error report.odt http://launchpadlibrarian.net/19349388/Upgrade%20error%20report.odt -- Upgrade failed Could not resolve ‘gb.archive.ubuntu.com’ https://bugs.launchpad.net/bugs/293806 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 85488] Re: some usb_devices fault if usb_suspend enabled
another for the list ID 04b8:0122 Seiko Epson Corp. -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
