[Bug 53835] Re: ACPI startup causes unhandled IRQ.
I've got an A8V board, and I'm trying to resolve bug https://bugs.launchpad.net/bugs/256316 , so I flashed the BIOS yesterday. Ever since, I've been affected by this bug. (On Intrepid) Can this bug be reopened ? -- ACPI startup causes unhandled IRQ. https://bugs.launchpad.net/bugs/53835 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 284854] [NEW] fglrx module fails to build
Public bug reported: The module (8,543) fails to build with dkms. After prodding a bit in dkms, I found out where it tries to build, and tried to build manually. It seems it can't find /lib/modules/./include/linux/version.h Which is correct, that file does not exist. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- fglrx module fails to build https://bugs.launchpad.net/bugs/284854 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
Re: [Bug 284854] [NEW] fglrx module fails to build
$ dpkg -s linux-headers-generic Package: linux-headers-generic Status: install ok installed Priority: optional Section: devel Installed-Size: 32 Maintainer: Ubuntu Kernel Team <[EMAIL PROTECTED]> Architecture: amd64 Source: linux-meta Version: 2.6.27.7.9 Depends: linux-headers-2.6.27-7-generic Description: Generic Linux kernel headers This package will always depend on the latest generic kernel headers available. Got it... Just won't work. Anyway, if that's required, shouldn't that be a dependency ? Mario Limonciello wrote: > Check that you have linux-headers-generic installed > > On Fri, Oct 17, 2008 at 04:18, wateenellende <[EMAIL PROTECTED]> > wrote: > >> Public bug reported: >> >> The module (8,543) fails to build with dkms. >> After prodding a bit in dkms, I found out where it tries to build, and >> tried to build manually. >> It seems it can't find /lib/modules/./include/linux/version.h >> Which is correct, that file does not exist. >> >> ** Affects: fglrx-installer (Ubuntu) >> Importance: Undecided >> Status: New >> >> -- >> fglrx module fails to build >> https://bugs.launchpad.net/bugs/284854 >> You received this bug notification because you are subscribed to fglrx- >> installer in ubuntu. >> > > -- fglrx module fails to build https://bugs.launchpad.net/bugs/284854 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
Re: [Bug 284854] [NEW] fglrx module fails to build
Just updated and tried again. No luck: Setting up fglrx-kernel-source (2:8.543-0ubuntu2) ... Adding Module to DKMS build system Doing initial module build Error! Build of fglrx.ko failed for: 2.6.27-7-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/fglrx/8.543/build/ for more information. Installing initial module Error! Could not locate fglrx.ko for module fglrx in the DKMS tree. You must run a dkms build for kernel 2.6.27-7-generic (x86_64) first. Done. Setting up xorg-driver-fglrx (2:8.543-0ubuntu2) ... F. P. Beekhof wrote: > $ dpkg -s linux-headers-generic > Package: linux-headers-generic > Status: install ok installed > Priority: optional > Section: devel > Installed-Size: 32 > Maintainer: Ubuntu Kernel Team <[EMAIL PROTECTED]> > Architecture: amd64 > Source: linux-meta > Version: 2.6.27.7.9 > Depends: linux-headers-2.6.27-7-generic > Description: Generic Linux kernel headers > This package will always depend on the latest generic kernel headers > available. > > Got it... Just won't work. > Anyway, if that's required, shouldn't that be a dependency ? > > Mario Limonciello wrote: >> Check that you have linux-headers-generic installed >> >> On Fri, Oct 17, 2008 at 04:18, wateenellende <[EMAIL PROTECTED]> >> wrote: >> >>> Public bug reported: >>> >>> The module (8,543) fails to build with dkms. >>> After prodding a bit in dkms, I found out where it tries to build, and >>> tried to build manually. >>> It seems it can't find /lib/modules/./include/linux/version.h >>> Which is correct, that file does not exist. >>> >>> ** Affects: fglrx-installer (Ubuntu) >>> Importance: Undecided >>> Status: New >>> >>> -- >>> fglrx module fails to build >>> https://bugs.launchpad.net/bugs/284854 >>> You received this bug notification because you are subscribed to fglrx- >>> installer in ubuntu. >>> >> >> > -- fglrx module fails to build https://bugs.launchpad.net/bugs/284854 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
Re: [Bug 284854] [NEW] fglrx module fails to build
Updated and tried another time: success! AFAIC, this bug can be closed. F. P. Beekhof wrote: > Just updated and tried again. No luck: > > Setting up fglrx-kernel-source (2:8.543-0ubuntu2) ... > Adding Module to DKMS build system > Doing initial module build > > Error! Build of fglrx.ko failed for: 2.6.27-7-generic (x86_64) > Consult the make.log in the build directory > /var/lib/dkms/fglrx/8.543/build/ for more information. > Installing initial module > > Error! Could not locate fglrx.ko for module fglrx in the DKMS tree. > You must run a dkms build for kernel 2.6.27-7-generic (x86_64) first. > Done. > > Setting up xorg-driver-fglrx (2:8.543-0ubuntu2) ... > > > F. P. Beekhof wrote: >> $ dpkg -s linux-headers-generic >> Package: linux-headers-generic >> Status: install ok installed >> Priority: optional >> Section: devel >> Installed-Size: 32 >> Maintainer: Ubuntu Kernel Team <[EMAIL PROTECTED]> >> Architecture: amd64 >> Source: linux-meta >> Version: 2.6.27.7.9 >> Depends: linux-headers-2.6.27-7-generic >> Description: Generic Linux kernel headers >> This package will always depend on the latest generic kernel headers >> available. >> >> Got it... Just won't work. >> Anyway, if that's required, shouldn't that be a dependency ? >> >> Mario Limonciello wrote: >>> Check that you have linux-headers-generic installed >>> >>> On Fri, Oct 17, 2008 at 04:18, wateenellende <[EMAIL PROTECTED]> >>> wrote: >>> >>>> Public bug reported: >>>> >>>> The module (8,543) fails to build with dkms. >>>> After prodding a bit in dkms, I found out where it tries to build, and >>>> tried to build manually. >>>> It seems it can't find /lib/modules/./include/linux/version.h >>>> Which is correct, that file does not exist. >>>> >>>> ** Affects: fglrx-installer (Ubuntu) >>>> Importance: Undecided >>>> Status: New >>>> >>>> -- >>>> fglrx module fails to build >>>> https://bugs.launchpad.net/bugs/284854 >>>> You received this bug notification because you are subscribed to fglrx- >>>> installer in ubuntu. >>>> >>> >>> >> > -- fglrx module fails to build https://bugs.launchpad.net/bugs/284854 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
Re: [Bug 284854] Re: fglrx module fails to build
Alberto Milone wrote: > ** Changed in: fglrx-installer (Ubuntu) >Status: New => Invalid > I'd say "resolved" is a better description than "invalid", but whatever. Actually, although it's "working", performance is horrible - can't even play movies without stuttering. fglrx is not supported by ubuntu of course, but please take note, maybe pass this on to ATI developrs... -- fglrx module fails to build https://bugs.launchpad.net/bugs/284854 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
Re: [Bug 135769] Re: [gutsy] gqview won't rotate / flip
Seems to be working now. Daniel T Chen wrote: > Is this symptom still reproducible in 8.10 beta or later? > > ** Changed in: gqview (Ubuntu) >Status: New => Incomplete > -- [gutsy] gqview won't rotate / flip https://bugs.launchpad.net/bugs/135769 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 282234] [NEW] kate ignores settings for TAB
Public bug reported: Binary package hint: kate When I press TAB, I want to have a tabulator (no spaces), and have it 8 chars wide. This is in my config under "Editing", and in previous versions was respected. The current version in Intrepid (see below for details) ignores these settings, even though they are really set correctly, and produces 2 spaces. This is extremely annoying when typing source code, I now have to copy- paste tabs from existing documents. $ dpkg -s kate Package: kate Status: install ok installed Priority: optional Section: editors Installed-Size: 2652 Maintainer: Kubuntu Developers <[EMAIL PROTECTED]> Architecture: amd64 Source: kdesdk Version: 4:4.1.2-0ubuntu1 Replaces: kate-kde4 ** Affects: kdesdk (Ubuntu) Importance: Undecided Status: New -- kate ignores settings for TAB https://bugs.launchpad.net/bugs/282234 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 282234] Re: kate ignores settings for TAB
Ok, if I give _4_ tabs, kate will replace the just-created 8 spaces by a tab. Still very annoying. -- kate ignores settings for TAB https://bugs.launchpad.net/bugs/282234 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
Re: [Bug 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
That fix is most likely for the legacy ide driver. There hasn't been activity in the kernel bugzilla to indicate that there is a fix. I've sent an email, if they say that the correct driver has indeed been patched I'll give it a spin. Philipp Dreimann wrote: > We are currently at linux version 2.6.27.2 so your fix should be > included. Tell us if it works. > -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
In the changelog for 2.6.27-rc7 is the following text. If there's a new kernel to try, let me know. commit 62ff2ecf7a4e69f7271b7f7a57aaee76ffe610f2 Author: Masoud Sharbiani <[EMAIL PROTECTED]> Date: Wed Sep 10 22:22:34 2008 +0200 ide: Fix pointer arithmetic in hpt3xx driver code (3rd try) git commit 74811f355f4f69a187fa74892dcf2a684b84ce99 causes crash at module load (or boot) time on my machine with a hpt374 controller. The reason for this is that for initializing second controller which sets (hwif->dev == host->dev[1]) to true (1), adds 1 to a void ptr, which advances it by one byte instead of advancing it by sizeof(hpt_info) bytes. Because of this, all initialization functions get corrupted data in info variable which causes a crash at boot time. This patch fixes that and makes my machine boot again. The card itself is a HPT374 raid conroller: Here is the lspci -v output: 03:06.0 RAID bus controller: HighPoint Technologies, Inc. HPT374 (rev 07) Subsystem: HighPoint Technologies, Inc. Unknown device 0001 Flags: bus master, 66MHz, medium devsel, latency 120, IRQ 28 I/O ports at 8000 [size=8] I/O ports at 7800 [size=4] I/O ports at 7400 [size=8] I/O ports at 7000 [size=4] I/O ports at 6800 [size=256] Expansion ROM at fe8e [disabled] [size=128K] Capabilities: [60] Power Management version 2 03:06.1 RAID bus controller: HighPoint Technologies, Inc. HPT374 (rev 07) Subsystem: HighPoint Technologies, Inc. Unknown device 0001 Flags: bus master, 66MHz, medium devsel, latency 120, IRQ 28 I/O ports at 9800 [size=8] I/O ports at 9400 [size=4] I/O ports at 9000 [size=8] I/O ports at 8800 [size=4] I/O ports at 8400 [size=256] Capabilities: [60] Power Management version 2 Signed-off-by: Masoud Sharbiani <[EMAIL PROTECTED]> Cc: Sergei Shtylyov <[EMAIL PROTECTED]> Cc: Andrew Morton <[EMAIL PROTECTED]> [bart: use dev_get_drvdata() per Sergei's suggestion] Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 205067] Re: libata.dma=0 not recognized as boot option
See: http://forum.fedoraforum.org/forum/printthread.php?t=171223&page=10&pp=15 maybe it'll help if you add libata.dma=0 to /etc/modprobe.d/options . -- libata.dma=0 not recognized as boot option https://bugs.launchpad.net/bugs/205067 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 256316] [NEW] kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
Public bug reported: Binary package hint: linux-image-2.6.26-5-generic I'm running Hardy on a AMD64 machine with a RAID5 array in it, ext3 formatted. It has been working fine for years, with the exception of Gutsy's kernel that couldn't handle that many IDE devices (bug 157909, fixed in hardy). To make backups, I bought an external drive and an eSata controller. The controller is not supported in Hardy's kernel (2.6.24), but it is in Intrepid, so I installed linux-image-2.6.26-5-generic from intrepid. Running this kernel causes several changes: 1) My new controller is recognized 2) All disks are now known as /dev/sd* and not /dev/hd* 3) Copying from /dev/md0 results in many filesystem errors 4) e2fsck reports massive errors on the filesystem on /dev/md0 If I reboot into 2.6.24, all problems are gone and everything is back t normal. This implies that there is a major problem somewhere! I happen to mount the device read-only, but mounting it rw will no doubt result in severe damage to the fs. I accidentally tested this by running e2fsck under 2.6.26, which did introduce real errors that I then had to fix under 2.6.24. Now, under 2.6.24, all is fine and 2.6.26 still reports many errors. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
** Attachment added: "dmesg 2.6.24" http://launchpadlibrarian.net/16672654/dmesg -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
AFAIK, assignee is maintainer of the package. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Description changed: Binary package hint: linux-image-2.6.26-5-generic I'm running Hardy on a AMD64 machine with a RAID5 array in it, ext3 formatted. It has been working fine for years, with the exception of Gutsy's kernel that couldn't handle that many IDE devices (bug 157909, fixed in hardy). To make backups, I bought an external drive and an eSata controller. The controller is not supported in Hardy's kernel (2.6.24), but it is in Intrepid, so I installed linux-image-2.6.26-5-generic from intrepid. Running this kernel causes several changes: 1) My new controller is recognized 2) All disks are now known as /dev/sd* and not /dev/hd* 3) Copying from /dev/md0 results in many filesystem errors 4) e2fsck reports massive errors on the filesystem on /dev/md0 - If I reboot into 2.6.24, all problems are gone and everything is back t + If I reboot into 2.6.24, all problems are gone and everything is back to normal. This implies that there is a major problem somewhere! I happen to mount the device read-only, but mounting it rw will no doubt result in severe damage to the fs. I accidentally tested this by running e2fsck under 2.6.26, which did introduce real errors that I then had to fix under 2.6.24. Now, under 2.6.24, all is fine and 2.6.26 still reports many errors. -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
See also http://bugzilla.kernel.org/show_bug.cgi?id=11328 -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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
Re: [Bug 282234] Re: kate ignores settings for TAB
Tuukka Verho wrote: > This is because in Kate the tab key indents instead of inserting a tab > character. If your indentation width is smaller than tab width, Kate > inserts spaces. If indentation width is larger than tab width, > indentation is done with a combination of tabs and spaces. > > You get the desired behaviour if you set the tab width to the same as > the indentation width. > > I agree that this is very confusing. One should be able to set 'indent > with tabs' and indentation width would then be determined by tab width. > What a marvelous user interface design choice! I see the developers took the precaution of not putting the two settings in the same panel, lest anyone might find out about a way to make kate behave as desired. Wait, I've got another great idea: we should let users enter the desired widths by tapping morse-code on the space bar! Or maybe we could force them to use vi... pff I really like kate and I've used it for years, but a) this change was really annoying; and b) the solution is sufficiently obscure that I couldn't find it. In the mean time I switched to another editor (geany) that can easily be configured to do what I want, and have no intention of switching back. -- kate ignores settings for TAB https://bugs.launchpad.net/bugs/282234 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdesdk in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
No problem. I picked up both the generic & server package, and tried to install them both, so I could, if needed, compare them. Installed generic first, all ok. However, it seems on must really make a choice: $ sudo dpkg -i linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb Selecting previously deselected package linux-image-2.6.27-1-server. (Reading database ... 203428 files and directories currently installed.) Unpacking linux-image-2.6.27-1-server (from linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb) ... Done. dpkg: error processing linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb (--install): trying to overwrite `/lib/firmware/atmsar11.fw', which is also in package linux-image-2.6.27-1-generic dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz Found kernel: /boot/vmlinuz.old Found kernel: /boot/vmlinuz-2.6.27-1-generic Found kernel: /boot/vmlinuz-2.6.26-5-generic Found kernel: /boot/vmlinuz-2.6.24-19-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Errors were encountered while processing: linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb I'll reboot into linux-image-2.6.27-1-generic now, and start testing On Fri, Aug 29, 2008 at 2:13 AM, Leann Ogasawara <[EMAIL PROTECTED]> wrote: > The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the > upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would > appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. > There are one of two ways you should be able to test: > > 1) If you are comfortable installing packages on your own, the linux- > image-2.6.27-* package is currently available for you to install and > test. > > --or-- > > 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer > 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. > Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. > You should then be able to test via a LiveCD. > > Please let us know immediately if this newer 2.6.27 kernel resolves the > bug reported here or if the issue remains. More importantly, please > open a new bug report for each new bug/regression introduced by the > 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please > specifically note if the issue does or does not appear in the 2.6.26 > kernel. Thanks again, we really appreicate your help and feedback. > > ** Tags added: cft-2.6.27 > > -- > kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on > 2.6.24 it is fine > https://bugs.launchpad.net/bugs/256316 > You received this bug notification because you are a direct subscriber > of the bug. > -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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
Re: [Bug 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
Well, no luck. $ uname -a Linux DeathStar 2.6.27-1-generic #1 SMP Sat Aug 23 23:19:01 UTC 2008 x86_64 GNU/Linux $ cat */*.avi > /dev/null cat: Amadeus (DVDivX)/Amadeus.The_Directors_Cut_(1984).AC3.CD1.MoonAge.ShareReacto.avi: Input/output error cat: Auberge Espagnol/AubergeEspagnol-CD2.avi: Input/output error ... from here on I stopped the test. >From syslog: Aug 29 09:02:00 DeathStar kernel: [ 1207.904014] attempt to access beyond end of device Aug 29 09:02:00 DeathStar kernel: [ 1207.904014] md0: rw=0, want=7771191736, limit=2929692160 Aug 29 09:02:00 DeathStar kernel: [ 1207.910440] attempt to access beyond end of device Aug 29 09:02:00 DeathStar kernel: [ 1207.911275] md0: rw=0, want=7771191736, limit=2929692160 Aug 29 09:03:31 DeathStar kernel: [ 1299.012020] attempt to access beyond end of device Aug 29 09:03:31 DeathStar kernel: [ 1299.012020] md0: rw=0, want=11222412024, limit=2929692160 Aug 29 09:03:31 DeathStar kernel: [ 1299.022440] attempt to access beyond end of device Aug 29 09:03:31 DeathStar kernel: [ 1299.023546] md0: rw=0, want=11222412024, limit=2929692160 As I posted in the corresponding kernel bugzilla, my suspicion is that the hpt374 driver in libata is returning bogus data when reading from disk. This includes bogus file-system metadata, which in turn induces the kernel to start reading from places on disk that do not exist - which causes the error that we observe. This theory hasn't exactly been proven, it's just my best guess. -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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 262783] [NEW] cannot install linux-image-2.6.27-1-server and linux-image-2.6.27-1-generic together
Public bug reported: Binary package hint: linux-image In the process of bug 256316 I stumbled on the following: $ sudo dpkg -i linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb Selecting previously deselected package linux-image-2.6.27-1-server. (Reading database ... 203428 files and directories currently installed.) Unpacking linux-image-2.6.27-1-server (from linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb) ... Done. dpkg: error processing linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb (--install): trying to overwrite `/lib/firmware/atmsar11.fw', which is also in package linux-image-2.6.27-1-generic dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz Found kernel: /boot/vmlinuz.old Found kernel: /boot/vmlinuz-2.6.27-1-generic Found kernel: /boot/vmlinuz-2.6.26-5-generic Found kernel: /boot/vmlinuz-2.6.24-19-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Errors were encountered while processing: linux-image-2.6.27-1-server_2.6.27-1.2_amd64.deb Now, if I'm not mistaken, the linux-image-2.6.27-1-server and linux- image-2.6.27-1-generic packages should either be installable together, or should be made aware that they conflict. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: linux-2.6.27 ** Tags added: linux-2.6.27 -- cannot install linux-image-2.6.27-1-server and linux-image-2.6.27-1-generic together https://bugs.launchpad.net/bugs/262783 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 256316] Re: kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine
I just opened a separate bug report for the failed installation of linux-image-2.6.27-1-server: bug 262783 It's tagged "linux-2.6.27" . -- kernel 2.6.26 reports massive filesystem errors on RAID5 device; but on 2.6.24 it is fine https://bugs.launchpad.net/bugs/256316 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
Re: [Bug 157909] Re: IDE0 and IDE1 taken over by SATA in Gutsy
Aaron C. de Bruyn wrote: > After pleading (because this bug totally b0rked working systems) to make > this something higher than 'wishlist', it's still sitting here almost a > year later. > > At this point it doesn't look like the developers are going to fix this > in Gutsy since they have more pressing issues (Hardy and Intrepid). > > It's fixed in Hardy. > > Why don't we just close this bug since it's going nowhere? > People affected by this bug have excellent chances of having similar experiences with Intrepid, most likely if you have a HPT473, although it hasn't been 100% proven that this driver is the cause. Hence I would like to ask your attention / effort for the following bug: https://bugs.launchpad.net/bugs/256316 which actually refers to a bug in kernel bugzilla: http://bugzilla.kernel.org/show_bug.cgi?id=11328 In short, the Intrepid kernels have switched to libata. On my system, data read with this kernel is *corrupted*. Your filesystem will look broken. If you try to "fix" your filesystem, you will be writing to it - and corrupt the data on the disk. If you can afford it, please help. Make sure your filesystems ok (fsck'ed) with the Hardy kernel. Then install the latest Intrepid kernel on your system, reboot, (mount your filesystems on HPT47x READ-ONLY!!!) and: a) do some heavy I/O or and monitor your syslog b) do "fsck -fn /dev/sdX" for your device. Note that your former /dev/hdX will now be an /dev/sdX! If anything bad happens, please report your findings. I haven't observed any problems with devices attached to other controllers than a HPT473, but you might want to check them too. If you have problems, please mention the type of controller, specify your filesystem too. If Intrepid ships with special data-corruption powers, quite a lot of people will be in deep shit. We don't need that again. Please help. -- IDE0 and IDE1 taken over by SATA in Gutsy https://bugs.launchpad.net/bugs/157909 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)
Agreed. I should add that there are bugs in KDEsu (1), which hamper the use of adept-updater etc. Of 5 computers upgraded at home and at work, two were left in a completely unusable state (one recovered so far), the third is affected by this memory-bug (2). The fourth and fifth have been running gutsy for a long time and only required some manual downloading and installing of .deb files for udev & volumeid, because this wasn't handled automatically. This was deemed "not a bug" because I "should have use adept or the upgrade manager", which was obviously not possble because of bugs (1) and (2). All in all, I'm NOT impressed: 0 out of 5 upgrades successful. For now, I recommend against upgrading. Therefore, creating the patch is very important and I hope it works out, but for now I'm too busy fixing my unbootable machine to try it. On 10/25/07, FerranRius <[EMAIL PROTECTED]> wrote: > BigPick: I'll test your patch as soon I go back home to see if I can confirm > your results. > However, I insist on what I (and others) have said. Until a definitive fix > for this has been released, this should be considered a critical bug and, as > it clearly affects many users, upgrading from Feisty should not be > recommended. > > -- > [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> > feisty) > https://bugs.launchpad.net/bugs/107188 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty) https://bugs.launchpad.net/bugs/107188 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
[Bug 158294] [gutsy/amd64] kernel won't boot
Public bug reported: Since the feisty->gutsy upgrade, my computer won't boot anymore. The old kernel still boots. Due to all the screen blanking of the fancy logo's I can't see what's going wrong, but I think I saw something like "Can't allocate memory for resource " and finally it complains about "too many ide devices" if I remember correctly. Then I will get a busybox prompt, but can't do much except reboot. There is a HPT374 (I think) ide controller in the machine. I can provide more information later. ** Affects: ubuntu Importance: Undecided Status: New -- [gutsy/amd64] kernel won't boot https://bugs.launchpad.net/bugs/158294 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
Re: [Bug 144722] Re: kdesu leads to no permission for X
> > On topic, > -it works on feisty, i386, home dir on NFS > -it works on gusty; i386, home on local disk > -it does not work on gutsy, home dir on NFS > > Did you have gutsy/NFS ? > I upgraded the "feisty, i386, home dir on NFS" machine to gutsy (with a lot of pain, there are conflicts). So now I have one gutsy/i386 and one gutsy/amd64 machine, sharing the same NFS dir. On the i386 machine kdesu/adept is working. On the amd64 machine, it doesn't. I never messed with the kdesu / kdesudo / sudo settings, so there is no reason for this behaviour. Please do fix this, this is going to hurt people. -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
Re: [Bug 132441] Re: [gutsy] udev, volumeid, dmsetup won't upgrade
I should add that even if adept would work and apt-get would not, this would be problematic because there are problems with adept-updater. See Bug 144722. On 10/3/07, Robert Persson <[EMAIL PROTECTED]> wrote: > In that case then this is a bug in apt, I think. I have just had a > similar problem with rss-glx and enblend not updating using adept. When > I tried to update them using apt-get I discovered that they needed a > particular library, which I was then able to install easily, also using > apt-get. Users should expect this kind of thing to be corrected > automatically. > > ** Changed in: apt (Ubuntu) > Sourcepackagename: udev => apt >Status: Invalid => New > > -- > [gutsy] udev, volumeid, dmsetup won't upgrade > https://bugs.launchpad.net/bugs/132441 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy] udev, volumeid, dmsetup won't upgrade https://bugs.launchpad.net/bugs/132441 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
[Bug 154806] 7.04 --> 7.10 upgrade tool crashed; out-of-memory
Public bug reported:
Binary package hint: update-manager
The tool keeps crashing. First, it hogs the memory (uses about 700 MB!), then
it crashes.
>From the "I've crashed" window:
Traceback (most recent call last):
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/dist-upgrade.py", line
59, in
app.run()
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/DistUpgradeControler.py",
line 1346, in run
self.fullUpgrade()
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/DistUpgradeControler.py",
line 1328, in fullUpgrade
if not self.doDistUpgrade():
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/DistUpgradeControler.py",
line 798, in doDistUpgrade
res = self.cache.commit(fprogress,iprogress)
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/DistUpgradeCache.py",
line 69, in commit
apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python2.5/site-packages/apt/cache.py", line 215, in commit
res = self.installArchives(pm, installProgress)
File "/usr/lib/python2.5/site-packages/apt/cache.py", line 190, in
installArchives
res = installProgress.run(pm)
File "/usr/lib/python2.5/site-packages/apt/progress.py", line 213, in run
pid = self.fork()
File "/tmp/kde-root/adept_updaterO59YFb.tmp-extract/DistUpgradeViewKDE.py",
line 244, in fork
self.child_pid = os.fork()
OSError: [Errno 12] Cannot allocate memory
/var/log/dist-upgrade/main.log:
2007-10-20 11:46:30,171 DEBUG examining: 'deb
http://ch.archive.ubuntu.com/ubuntu gutsy-backports main restricted universe
multiverse'
2007-10-20 11:46:30,171 DEBUG entry 'deb http://ch.archive.ubuntu.com/ubuntu
gutsy-backports main restricted universe multiverse' is already set to new dist
2007-10-20 11:46:30,172 DEBUG examining: 'deb-src
http://ch.archive.ubuntu.com/ubuntu gutsy-backports main restricted universe
multiverse'
2007-10-20 11:46:30,172 DEBUG entry 'deb-src
http://ch.archive.ubuntu.com/ubuntu gutsy-backports main restricted universe
multiverse' is already set to new dist
2007-10-20 11:46:30,173 DEBUG examining: 'deb http://security.ubuntu.com/ubuntu
gutsy-security main restricted'
2007-10-20 11:46:30,174 DEBUG entry 'deb http://security.ubuntu.com/ubuntu
gutsy-security main restricted' is already set to new dist
2007-10-20 11:46:30,175 DEBUG examining: 'deb-src
http://security.ubuntu.com/ubuntu gutsy-security main restricted'
2007-10-20 11:46:30,175 DEBUG entry 'deb-src http://security.ubuntu.com/ubuntu
gutsy-security main restricted' is already set to new dist
2007-10-20 11:46:30,176 DEBUG examining: 'deb http://security.ubuntu.com/ubuntu
gutsy-security universe'
2007-10-20 11:46:30,177 DEBUG entry 'deb http://security.ubuntu.com/ubuntu
gutsy-security universe' is already set to new dist
2007-10-20 11:46:30,177 DEBUG examining: 'deb-src
http://security.ubuntu.com/ubuntu gutsy-security universe'
2007-10-20 11:46:30,178 DEBUG entry 'deb-src http://security.ubuntu.com/ubuntu
gutsy-security universe' is already set to new dist
2007-10-20 11:46:30,178 DEBUG examining: 'deb
http://ch.archive.ubuntu.com/ubuntu/ gutsy universe main restricted multiverse'
2007-10-20 11:46:30,179 DEBUG entry 'deb http://ch.archive.ubuntu.com/ubuntu/
gutsy universe main restricted multiverse' is already set to new dist
2007-10-20 11:46:58,782 DEBUG demoted: 'binfmt-support gcj-4.1-base gij-4.1
libevms-2.5 libgcj7-jar libglib1.2 libgtk1.2 libgtk1.2-common libjasper-runtime
liblzo1 libportaudio0 libxmlsec1 libxmlsec1-nss libxmlsec1-openssl
openoffice.org-filter-mobiledev pmount ttf-baekmuk xmms'
2007-10-20 11:48:00,714 DEBUG Installing 'upstart-logd' (priority in required
set 'required' but not scheduled for install)
2007-10-20 11:48:01,988 DEBUG Installing 'system-services' (priority in
required set 'required' but not scheduled for install)
2007-10-20 11:48:02,867 DEBUG Installing 'startup-tasks' (priority in required
set 'required' but not scheduled for install)
2007-10-20 11:48:03,958 DEBUG Purging 'xorg-common' (Distro PostUpgradePurge
rule)
2007-10-20 11:48:04,288 DEBUG Purging 'libgl1-mesa' (Distro PostUpgradePurge
rule)
2007-10-20 11:48:04,665 DEBUG Purging 'ltsp-client' (Distro PostUpgradePurge
rule)
t0 foomatic-db-engine
2007-10-20 11:48:12,674 DEBUG Upgrade:
2007-10-20 11:48:12,678 DEBUG Free space on /: 6201040896
2007-10-20 11:48:12,679 DEBUG Dir /usr mounted on /
2007-10-20 11:48:12,681 DEBUG Dir /var mounted on /
2007-10-20 11:48:12,682 DEBUG Dir /boot mounted on /
2007-10-20 11:48:12,684 DEBUG Dir /var/cache/apt/archives mounted on /
2007-10-20 11:48:12,685 DEBUG Dir /home mounted on /
2007-10-20 11:48:12,686 DEBUG fs_free contains: '{'/var':
, '/home':
, '/boot':
, '/usr':
, '/':
,
'/var/cache/apt/archives': }'
2007-10-20 11:48:12,717 DEBUG linux-image-2.6.20-8-lowlatency
(upgrade|installed) added with 10485760 to boot space
2007-10-20 11:48:12,819 DEBUG linux-image-2.6.22-9-386 (upgrade|installed)
added with 10485760 to boot space
2007-10-20 11:48:12,952 DEBUG lin
[Bug 154806] Re: 7.04 --> 7.10 upgrade tool crashed; out-of-memory
This is the apt.log file. ** Attachment added: "apt.log" http://launchpadlibrarian.net/10080509/apt.log -- 7.04 --> 7.10 upgrade tool crashed; out-of-memory https://bugs.launchpad.net/bugs/154806 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
Re: [Bug 144722] Re: kdesu leads to no permission for X
By the way, that could be very serious problem for the following reason. Because I could not run adept-updater, I used "sudo apt-get update; sudo apt-get -y dist-upgrade" to update my system. This resulted in a problem with udev and some other packages, which were not updated. I filed a bug-report. However, this report was marked "invalid" because "if you had used adept-updater, you would have been fine." Obviously, that is not true. So I suspect there will be some trouble if this issue is not fixed and gutsy is released. -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
[Bug 144722] kdesu leads to no permission for X
Public bug reported: Binary package hint: kdesudo Using kdesu is not particularly sucessful: $ kdesu adept_updater X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device Xlib: connection to ":0.0" refused by server Xlib: No protocol specified adept_updater: cannot connect to X server :0 $ xhost + $ kdesu adept_updater ... now it works fine. ** Affects: kdesudo (Ubuntu) Importance: Undecided Status: New -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
[Bug 28047] Re: adept package alterations fail when root doesn't have read access to homdir
In fact, adept_updater if complaining _a lot_ because it cannot write to my home dir on NFS. Tells me to contact the admin etc. -- adept package alterations fail when root doesn't have read access to homdir https://bugs.launchpad.net/bugs/28047 You received this bug notification because you are a member of Kubuntu Team, which is a direct subscriber. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 144722] Re: kdesu leads to no permission for X
By the way, this is a GUTSY problem, it works fine in FEISTY, at least in my installations. On 9/26/07, jeroenvrp <[EMAIL PROTECTED]> wrote: > I can confirm this, but the solution with xhost + doesn't seem to work. > > See also bug #140793 . > > If I do e.g. kdesudo kedit, it starts kedit, but as myself, not as root > > When I do a kdesudo -u testuser kedit, it gives a: > - No protocol specified > - Xlib: connection to ":0.0" refused by server > > It gives also sometimes these error messages: > - Error: "/var/tmp/kdecache-jeroen" is owned by uid 1000 instead of uid 0. > - Error: "/tmp/ksocket-jeroenzvlc9S" is owned by uid 1000 instead of uid 0. > > Please fix. Seems very critical. > > -- > kdesu leads to no permission for X > https://bugs.launchpad.net/bugs/144722 > You received this bug notification because you are a direct subscriber > of the bug. > -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
[Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
I've got a Dell computer with a Sun keyboard attached to it. Same problem. There are hotkeys on it, and if possible they should just work. Maybe support for for a Sun keyboard is too much to ask, but the same argument goes for logitech / MS. This should be parsed as a "Sun" (the keyboard manufacturer), not a "Dell" (the computer manufacturer). Using the computer manufacturer to identify the keyboard manufacturer is plain wrong, although on a laptop you can assume they are the same. -- package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/140967 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
[Bug 146378] [gutsy] modules-assistant useless due to linux/config.h not found for many packages
Public bug reported: Binary package hint: module-assistant kernel-header packages have changed, what used to be "/usr/src/headers.../include/linux/config.h" is now "/usr/src/headers.../include/linux/autoconf.h" As a result, I could not build pwc, and many other packages. The following instructions on an obscure website worked around the problem: --- try to ln -s autoconf.h config.h in /usr/src/linux-haeders-x/include/linux this helped ** Affects: module-assistant (Ubuntu) Importance: Undecided Status: New -- [gutsy] modules-assistant useless due to linux/config.h not found for many packages https://bugs.launchpad.net/bugs/146378 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
Re: [Bug 144722] Re: kdesu leads to no permission for X
On 9/28/07, Anthony Mercatante <[EMAIL PROTECTED]> wrote: > Just tested here and I can't reproduce. Poor guy! But why are you telling me about this ? *ROFL* > kdesu adept_installer just works perfectly here even in konsole... > On topic, -it works on feisty, i386, home dir on NFS -it works on gusty; i386, home on local disk -it does not work on gutsy, home dir on NFS Did you have gutsy/NFS ? -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
[Bug 192581] [NEW] [gutsy] avahi goes berserk
Public bug reported: I have an ADSL modem that runs a DHCP server, and always assign IP addrs in the 192.168.1.x space. Recently, my box loses network every now and then. *Something* strange happens: # /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:40:63:DE:10:1C inet6 addr: fe80::240:63ff:fede:101c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:769 errors:0 dropped:0 overruns:0 frame:28 TX packets:1097 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:460770 (449.9 KB) TX bytes:106126 (103.6 KB) Interrupt:10 Base address:0xe800 eth0:avah Link encap:Ethernet HWaddr 00:40:63:DE:10:1C inet addr:169.254.4.109 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:10 Base address:0xe800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:405 errors:0 dropped:0 overruns:0 frame:0 TX packets:405 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41595 (40.6 KB) TX bytes:41595 (40.6 KB) I have no idea where the "169.254.4.109" addr comes from. It does not seem to exist on internet, google didn't find it either. The "solution" is to unplug the cable, and plug it back in. In a few seconds all will be fine again: $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:40:63:DE:10:1C inet addr:192.168.1.33 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::240:63ff:fede:101c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8954 errors:0 dropped:1 overruns:0 frame:25 TX packets:6128 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4671723 (4.4 MB) TX bytes:1067824 (1.0 MB) Interrupt:10 Base address:0xe800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:120 errors:0 dropped:0 overruns:0 frame:0 TX packets:120 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9827 (9.5 KB) TX bytes:9827 (9.5 KB) WTF ?? $ dpkg -l avahi-daemon Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii avahi-daemon 0.6.20-2ubuntu3.2 Avahi mDNS/DNS-SD daemon ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- [gutsy] avahi goes berserk https://bugs.launchpad.net/bugs/192581 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
[Bug 223557] [NEW] [hardy] rng-tools config file and man page contains error
Public bug reported: Binary package hint: rng-tools The man page of rngd mentiones: [--trng=name] (notice the 't') and the default config file "/etc/default/rng-tools" contains: #RNGDOPTIONS="--trng=intelfwh" #RNGDOPTIONS="--trng=via" However, --trng is not accepted by rngd: $ rngd --trng=help rngd: unrecognized option `--trng=help' Try `rngd --help' or `rngd --usage' for more information. $ Actually, it should be --hrng (notice the 'h'). >From "rngd --help": --hrng=name Load known-good defaults for a given HRNG. Use --hrng=help to get a list of known HRNGs $ rngd --hrng=helprngd --hrng=help RNG Description intelfwh "Intel FWH (82802AB/AC) RNG" rng-entropy=0.998, rng-buffers=5; via "VIA Padlock (Nehemiah) RNG" rng-entropy=0.750, rng-buffers=3; $ So, the man page and "/etc/default/rng-tools" need to have "--trng" changed to "--hrng" ** Affects: rng-tools (Ubuntu) Importance: Undecided Status: New -- [hardy] rng-tools config file and man page contains error https://bugs.launchpad.net/bugs/223557 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 137735] [gutsy] wine causes hard lockup - every time
Public bug reported: Binary package hint: wine Whatever I try to do with wine - configure it through the System Settings or just run a program from the command line - my computer will lock up hard after a few seconds. CPU is a VIA C3. $ dpkg -s wine Package: wine Status: install ok installed Priority: optional Section: otherosfs Installed-Size: 99904 Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]> Architecture: i386 Version: 0.9.42-0ubuntu1 ** Affects: wine (Ubuntu) Importance: Undecided Status: New -- [gutsy] wine causes hard lockup - every time https://bugs.launchpad.net/bugs/137735 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
[Bug 139898] [gutsy] icedax / cddawav conflict not properly handled
Public bug reported:
Binary package hint: icedax
Icedax and cdda2wav are in conflict. However, even though this is indicated in
the icedax package, this is somehow not understood by apt. The result is that
dpkg will detect the conflict and stop.
I've already done an "apt-get -f install", so any conflicts should really
already have been corrected.
The following packages will be upgraded:
cdda2wav
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/153kB of archives.
After unpacking 336kB of additional disk space will be used.
(Reading database ... 194584 files and directories currently installed.)
Preparing to replace cdda2wav 9:1.1.6-1ubuntu1 (using
.../cdda2wav_10%3a2.01.01a33-0ubuntu1_i386.deb) ...
Unpacking replacement cdda2wav ...
dpkg: error processing
/var/cache/apt/archives/cdda2wav_10%3a2.01.01a33-0ubuntu1_i386.deb (--unpack):
trying to overwrite `/usr/bin/cdda2ogg', which is also in package icedax
Errors were encountered while processing:
/var/cache/apt/archives/cdda2wav_10%3a2.01.01a33-0ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ apt-cache show icedax
Package: icedax
Priority: optional
Section: universe/sound
Installed-Size: 388
Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]>
Original-Maintainer: Joerg Jaspert <[EMAIL PROTECTED]>
Architecture: i386
Source: cdrkit
Version: 9:1.1.6-1ubuntu1
Replaces: cdda2wav (<< 9:1.0)
Depends: libc6 (>= 2.6)
Suggests: vorbis-tools, cdrkit-doc
Conflicts: cdda2wav (<< 9:1.0)
Filename: pool/universe/c/cdrkit/icedax_1.1.6-1ubuntu1_i386.deb
Size: 172130
MD5sum: 3ac0aedc05d882ccfcdad80359a3c8ab
SHA1: eb3ad19b532f0f225814fc5a2872e7da3389dea8
SHA256: d54eeda482284c7708e0c61861e09a8ad299cbd3e356cbea125785bc9b254818
Description: Creates WAV files from audio CDs
icedax lets you digitally copy ("rip") audio tracks from a CD, avoiding
the distortion that is introduced when recording via a sound card. Data
can be dumped into raw (cdr), wav or sun format sound files. Options control
the recording format (stereo/mono; 8/16 bits; sampling rate, etc).
.
Please install cdrkit-doc if you want most of the documentation and
README files.
Bugs: mailto:[EMAIL PROTECTED]
Origin: Ubuntu
** Affects: cdrkit (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] icedax / cddawav conflict not properly handled
https://bugs.launchpad.net/bugs/139898
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
[Bug 135769] [gutsy] gqview won't rotate / flip
Public bug reported: Binary package hint: gqview Images viewed with gqview can normally be rotated clockwise from a menu available under a right-mouse click. However, in gutsy/amd64, nothing happens. The feisty/i386 package works fine. $ dpkg -s gqview Package: gqview Status: install ok installed Priority: optional Section: graphics Installed-Size: 2752 Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]> Architecture: amd64 Version: 2.0.4-0ubuntu1 Depends: libatk1.0-0 (>= 1.13.2), libc6 (>= 2.5-5), libcairo2 (>= 1.4.0), libfontconfig1 (>= 2.4.0), libglib2.0-0 (>= 2.13.2), libgtk2.0-0 (>= 2.10.3), libpango1.0-0 (>= 1.17.1), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxfixes3 (>= 1:4.0.1), libxi6, libxinerama1, libxrandr2 (>= 2:1.2.0), libxrender1 Recommends: libjpeg-progs Suggests: gimp, xpaint Description: A simple image viewer using GTK+ Simple image browser with thumbnail capability. Uses GTK+ 2.x. Original-Maintainer: Ryan Murray <[EMAIL PROTECTED]> ** Affects: gqview (Ubuntu) Importance: Undecided Status: New -- [gutsy] gqview won't rotate / flip https://bugs.launchpad.net/bugs/135769 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
[Bug 135794] [gutsy] command-not-found not found
Public bug reported: Binary package hint: command-not-found This is just too funny: $ alien bash: /usr/bin/command-not-found: No such file or directory bash: alien: command not found version: $ dpkg -s bash Package: bash Essential: yes Status: install ok installed Priority: required Section: shells Installed-Size: 2028 Maintainer: Ubuntu Core developers <[EMAIL PROTECTED]> Architecture: amd64 Version: 3.2-0ubuntu9 Replaces: bash-doc (<= 2.05-1), bash-completion Depends: base-files (>= 2.1.12), debianutils (>= 2.15) Pre-Depends: libc6 (>= 2.6-1), libncurses5 (>= 5.6) Suggests: bash-doc Conflicts: bash-completion Conffiles: /etc/skel/.bashrc 52acca91b52f797661c89b181809b9f3 /etc/skel/.profile 7d97942254c076a2ea5ea72180266420 /etc/skel/.bash_logout 22bfb8c1dd94b5f3813a2b25da67463f /etc/bash.bashrc 0a22bcf91612bad30b41c04eaa8870df /etc/bash_completion c8bce25ea68fb0312579a421df99955c Description: The GNU Bourne Again SHell Bash is an sh-compatible command language interpreter that executes commands read from the standard input or from a file. Bash also incorporates useful features from the Korn and C shells (ksh and csh). . Bash is ultimately intended to be a conformant implementation of the IEEE POSIX Shell and Tools specification (IEEE Working Group 1003.2). . Included in the bash package is the Programmable Completion Code, by Ian Macdonald. Original-Maintainer: Matthias Klose <[EMAIL PROTECTED]> $ dpkg -s command-not-found Package: command-not-found Status: install ok installed Priority: optional Section: admin Installed-Size: 96 Maintainer: Michael Vogt <[EMAIL PROTECTED]> Architecture: all Version: 0.2.7 Depends: python, python-central (>= 0.5.8), command-not-found-data Conffiles: /etc/zsh_command_not_found faf757f575b50bc3e4801899c68f272b /etc/bash_command_not_found e6f56e9685e3e979ebd3d3b8623f93d6 obsolete Description: Suggest installation of packages in interactive bash sessions This package will install handler for command_not_found that lookups programs not currently installed but available from the repositiories. Original-Maintainer: Zygmunt Krynicki <[EMAIL PROTECTED]> Python-Version: current ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New -- [gutsy] command-not-found not found https://bugs.launchpad.net/bugs/135794 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
Re: [Bug 135794] Re: [gutsy] command-not-found not found
topdog wrote: > Bash expects the it to be at this location /usr/bin/command-not-found > The new package is installing it in the wrong location /usr/lib/command- > not-found. It is, IMHO, not in the wrong location. AFAIK, binaries in /usr/bin/ are meant for users and binaries in /usr/lib are for "internal" usage. So, it is in the right place because users are not supposed to call command-not-found themselves. > Either the /etc/bash.bashrc has to be fixed our possible a simlink > between the two locations needs to be created. If my previous comment is indeed correct, fixing /etc/bash.bashrc seems to be the right choice. -- [gutsy] command-not-found not found https://bugs.launchpad.net/bugs/135794 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
[Bug 82195] Re: Cannot modprobe fglrx
This "depmod" problem is not the only one: [EMAIL PROTECTED]:/etc/modprobe.d# ls /lib/modules/2.6.20-16-lowlatency/volatile/fglrx.ko ls: /lib/modules/2.6.20-16-lowlatency/volatile/fglrx.ko: No such file or directory [EMAIL PROTECTED]:/etc/modprobe.d# -- Cannot modprobe fglrx https://bugs.launchpad.net/bugs/82195 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
[Bug 132441] [gutsy] udev, volumeid, dmsetup won't upgrade
Public bug reported: Binary package hint: udev These 3 packages seem to be related to each other in a way that won;t allow them to upgrade... $ sudo apt-get install dmsetup Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: dmsetup: Breaks: udev (< 113-0ubuntu1) but 103-0ubuntu13 is to be installed udev: Depends: volumeid (= 103-0ubuntu13) but 113-0ubuntu6 is to be installed E: Broken packages ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- [gutsy] udev, volumeid, dmsetup won't upgrade https://bugs.launchpad.net/bugs/132441 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
Re: [Bug 132441] [gutsy] udev, volumeid, dmsetup won't upgrade
Downloading and installing the packages by hand fixes the problem. libdevmapper1.02_1.02.08-1ubuntu10_amd64.deb udev_113-0ubuntu6_amd64.deb volumeid_113-0ubuntu6_amd64.deb then apt-get -y dist-upgrade will upgrade dmsetup wateenellende wrote: > Public bug reported: > > Binary package hint: udev > > These 3 packages seem to be related to each other in a way that won;t > allow them to upgrade... > > $ sudo apt-get install dmsetup > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > > Since you only requested a single operation it is extremely likely that > the package is simply not installable and a bug report against > that package should be filed. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > dmsetup: Breaks: udev (< 113-0ubuntu1) but 103-0ubuntu13 is to be installed > udev: Depends: volumeid (= 103-0ubuntu13) but 113-0ubuntu6 is to be > installed > E: Broken packages > > ** Affects: udev (Ubuntu) > Importance: Undecided > Status: New > -- [gutsy] udev, volumeid, dmsetup won't upgrade https://bugs.launchpad.net/bugs/132441 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
[Bug 107188] Re: [patch] Upgrade tool crashed with " Cannot allocate memory"
Try this: valgrind /usr/bin/update-manager *OUCH* That's more memory-errors than I can copy-paste!! Somebody needs to debug python2.5. This is a horrible mess!! -- [patch] Upgrade tool crashed with " Cannot allocate memory" https://bugs.launchpad.net/bugs/107188 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
[Bug 107188] Re: [patch] Upgrade tool crashed with " Cannot allocate memory"
Sorry, this is a dead end road. Using the correct suppression file and python-dbg, all errors disappeared (they are false positives) , until it crashed because it can't find some gtk lib. On a second attempt, using the correct suppression file and python without debugging symbols, my system hung hard. I'm giving up -- [patch] Upgrade tool crashed with " Cannot allocate memory" https://bugs.launchpad.net/bugs/107188 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
[Bug 107188] Re: [patch] Upgrade tool crashed with " Cannot allocate memory"
For those interested, I tried this: apt-get install python2.5-dbg valgrind then, edit your /usr/bin/update-manager, line 1: #!/usr/bin/python2.5-dbg Then: valgrind --log-file=python-errors /usr/bin/update-manager This produced the attachment, and then said: Traceback (most recent call last): File "/usr/bin/update-manager", line 28, in import gtk File "/var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py", line 38, in import gobject as _gobject File "/var/lib/python-support/python2.5/gtk-2.0/gobject/__init__.py", line 30, in from gobject.constants import * File "/var/lib/python-support/python2.5/gtk-2.0/gobject/constants.py", line 22, in from _gobject import type_from_name ImportError: /var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so: undefined symbol: Py_InitModule4 Error in sys.excepthook: Traceback (most recent call last): File "/var/lib/python-support/python2.5/apport_python_hook.py", line 38, in apport_excepthook from apport.fileutils import likely_packaged File "/var/lib/python-support/python2.5/apport/__init__.py", line 1, in from apport.report import Report File "/var/lib/python-support/python2.5/apport/report.py", line 18, in from xml.parsers.expat import ExpatError File "/usr/lib/python2.5/site-packages/_xmlplus/parsers/expat.py", line 4, in from pyexpat import * ImportError: /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so: undefined symbol: Py_InitModule4 Original exception was: Traceback (most recent call last): File "/usr/bin/update-manager", line 28, in import gtk File "/var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py", line 38, in import gobject as _gobject File "/var/lib/python-support/python2.5/gtk-2.0/gobject/__init__.py", line 30, in from gobject.constants import * File "/var/lib/python-support/python2.5/gtk-2.0/gobject/constants.py", line 22, in from _gobject import type_from_name ImportError: /var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so: undefined symbol: Py_InitModule4 I'll see if I can patch things a bit... ** Attachment added: "python-errors.6189" http://launchpadlibrarian.net/10311822/python-errors.6189 -- [patch] Upgrade tool crashed with " Cannot allocate memory" https://bugs.launchpad.net/bugs/107188 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
Re: [Bug 132245] Re: Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0.
*** This bug is a duplicate of bug 155032 *** https://bugs.launchpad.net/bugs/155032 maybeway36 wrote: > *** This bug is a duplicate of bug 155032 *** > https://bugs.launchpad.net/bugs/155032 > > kdesudo is now fixed, this bug should be too (just don't use sudo for > X11 apps.) > kdesudo is NOT fixed, there is still a permission problem: $ kdesudo xterm X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device passprompt Xlib: connection to ":0.0" refused by server Xlib: No protocol specified $ dpkg -s kdesudo Package: kdesudo Status: install ok installed Priority: optional Section: kde Installed-Size: 168 Maintainer: Anthony Mercatante <[EMAIL PROTECTED]> Architecture: amd64 Version: 1.1-0ubuntu2.2 .. The bug has been diagnosed: to connect to X, you need to have access .Xauthority, which is problematic in a NFS+root_squash environment: $ ls -al ~/.X* -rw--- 1 beekhof spc 738 2008-01-20 17:44 /home/beekhof/.Xauthority Currently, the only solution I am aware of is: apt-get install kdesu; apt-get remove kdesudo kdesu works fine. -- Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0. https://bugs.launchpad.net/bugs/132245 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
Re: [Bug 132245] Re: Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0.
*** This bug is a duplicate of bug 155032 *** https://bugs.launchpad.net/bugs/155032 Maybe the conclusion that there is a problem with ~/.Xauthority is premature. Please see previous discussions on the subject. However, as you can see from my last mail, it just doesn't work, and I do remember that this was a problem shared by people having their home dir on an NFS mount, and that disabling the root_squash option resolved it. So it would seem some sort of read access to the home dir is required for root, which is denied due to root_squash. If it is not for ~/.Xauthority, I would not know what it would be for - I'm not an expert on the subject. Suggestions welcome! Frode M. Døving wrote: > *** This bug is a duplicate of bug 155032 *** > https://bugs.launchpad.net/bugs/155032 > > If the trunk version of kdesudo works like my branch when it comes to > authentication. It does not rely on ~/.Xauthority for anything at all. > It does however, rely on a writeable /tmp/ > -- Error: "/var/tmp/kdecache-privat" is owned by uid 1000 instead of uid 0. https://bugs.launchpad.net/bugs/132245 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
Re: [Bug 158294] Re: [gutsy/amd64] kernel won't boot
This bug is perfectly reproduceable, but it's very hard to gather information. In busybox, there is no dmesg or logs that I can find Any hints ? On 10/29/07, Jérôme Guelfucci <[EMAIL PROTECTED]> wrote: > ** Changed in: linux-source-2.6.22 (Ubuntu) > Sourcepackagename: None => linux-source-2.6.22 > > -- > [gutsy/amd64] kernel won't boot > https://bugs.launchpad.net/bugs/158294 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy/amd64] kernel won't boot https://bugs.launchpad.net/bugs/158294 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
[Bug 158294] Re: [gutsy/amd64] kernel won't boot
See also http://ubuntuforums.org/showthread.php?t=593841 https://bugs.launchpad.net/ubuntu/+bug/157909 The latter presents a solution. -- [gutsy/amd64] kernel won't boot https://bugs.launchpad.net/bugs/158294 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
[Bug 45563] Re: Build of fglrx module fails
Problem still present in gutsy. Tried to send an email to the maintainer - his email address does not exists anymore. Hereby for any maintainer that might stumble upon it. Hello, are you still the maintainer for the fglrx-source ? If so, please find attached a patch which solves some of the problems mentioned in bug 45563: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/45563 These problems exist apparently for a long time, and have made this package useless since Warty. The discussion on the bug page mentions the possibility of using the latest driver from ATI instead, however, this information is now outdated as: "Several distribution-specific packaging scripts are not up-to-date in this release. In particular packaging for 64-bit Ubuntu versions is known to be broken. A topic number is not available for this issue" (Release notes for 8.42.3) This leaves people with an ATI card unable to use their system properly. Using the "pre-cooked" restricted drivers is not an option for people that compile their own kernel. (For example, because are forced to do so due to bugs in the kernel shipped with Gutsy, but would like to boot their computer anyway...) Coincidentally, the existence of the "pre-cooked" drivers proves that there is a working system to compile fglrx drivers for current kernels, which begs the question why the fglrx-kernel-source package should be so faulty. Best regards, and thanks in advance for anything you can do, ** Attachment added: "fixes some packaging issues" http://launchpadlibrarian.net/10269761/fglrx-source-patch -- Build of fglrx module fails https://bugs.launchpad.net/bugs/45563 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 45563] Re: Build of fglrx module fails
> Wateenellende? That is funny :-) It's quite accurate > Actually, I think this package might be obsolete. You can download > the driver from ATI, do some magic with it and it spits out a debian > package which includes kernel source code for the latest driver. This > actually worked out of the box for me. The latest ATI drivers (8.42.3) are broken. From the release notes, see also my previous post: "Several distribution-specific packaging scripts are not up-to-date in this release. In particular packaging for 64-bit Ubuntu versions is known to be broken. A topic number is not available for this issue" - So downloading from ATI doesn't work. - This source package is a version that matches the Xorg driver in Ubuntu, so that is another good reason to try this kernel-source package. Alas - that does not work either. - Last option: use "restricted" pre-compiled packages. Unfortunately, gutsy's kernel does not boot on my machine. End result: my system thinks that I should use compiz - with Software OpenGL. I'm scrolling text in lines per minute. I am not amused. -- Build of fglrx module fails https://bugs.launchpad.net/bugs/45563 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 107188] Re: [patch] Upgrade tool crashed with " Cannot allocate memory"
There are specialized memory debugging tools, for example "valgrind". If any attempt to allocate memory would fail, I would suspect that valgrind would be able to give a nice stack trace. (recompile python without optimization & with debugging symbols!) refer to http://www.linuxjournal.com/article/6556 for a more detailed article on the subject. On 11/6/07, Michael Vogt <[EMAIL PROTECTED]> wrote: > @BigPick: Thanks for your analysis of the patch, when I read it I was > wondering what change in it might have caused that the problem got > fixed. My current theory is that the bug occur more or less random (or > with a pattern that is very hard to reproduce) so that even if the patch > itself has little effect, a upgrade test may still be successful because > the bug is not triggered within this run. I'm currently trying to > reproduce the problem with the virtualbox package in ubuntu. My current > idea of reproducing it is to install kubuntu-feisty and try various > combinations of stock kubuntu feisty install, install with updates, with > backport enabled etc. Each time a snapshot is taken before the upgrade. > > I hope using this method we will be able to find a way to reliable > trigger the bug. Everybody is welcome to help with the hunt :) (my main > machine is currently not usable, so I'm a bit slower with those tests as > I would otherwise). As for the debugging output, I think that strace is > usually a good first step. If we could get a gziped strace log when the > bug happend, that would be really cool. I suspect the actual problem > lies somewhere under the python layer of the code (in the C/C++ bits), > so pdb is probably not that helpful. gdb might, once we know a bit > better what to look for. > > Cheers, > Michael > > -- > [patch] Upgrade tool crashed with " Cannot allocate memory" > https://bugs.launchpad.net/bugs/107188 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- [patch] Upgrade tool crashed with " Cannot allocate memory" https://bugs.launchpad.net/bugs/107188 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
Re: [Bug 149609] Re: [gutsy] Running a Wine application freezes up the whole system
*** This bug is a duplicate of bug 137735 *** https://bugs.launchpad.net/bugs/137735 That doesn't *solve* the issue, that works around it. Coincidentally, this "solution" also makes sure that I can't run the application I want to, because that's a game and it needs graphics. Anyway, I guess the problem is not so much in wine but in the faulty VIA graphics/opengl drivers. Shame on VIA alejandro gonzález wrote: > *** This bug is a duplicate of bug 137735 *** > https://bugs.launchpad.net/bugs/137735 > >>From https://bugs.launchpad.net/ubuntu/+source/wine/+bug/137735 > > adding the following lines to /etc/X11/xorg.conf solves the issue: > > Section "Module" > Disable "dri" > Disable "glx" > EndSection > > > ** This bug has been marked a duplicate of bug 137735 >[gutsy] wine causes hard lockup - every time > -- [gutsy] Running a Wine application freezes up the whole system https://bugs.launchpad.net/bugs/149609 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
Re: [Bug 155032] Re: kdesu ownership change
IMHO, this is not a "NFS permission problem", because having root_squash is desirable behaviour and not a problem. Secondly users may not have control over the NFS server (such as here at work), so root_squash will always be in effect, and kdesudo should work in such an environment anyway. Anyway, now we know what's going wrong: kdesudo must work in an environment where the user's home directory is not writable by root (but currently it doesn't). On Nov 23, 2007 4:23 AM, Brian Buchanan <[EMAIL PROTECTED]> wrote: > I thought I had bug 144722 today, but it turned out to be a NFS > permission problem. /home was exported without no_root_squash i.e. > root_squash was in effect. (I was also using NFS4, fyi) I believe that > this situation would prevent the sudo (or kdesudo) process from having > access to the root owned files, such as > ~/.kde/share/config/adept_updaterrc. I set no_root_squash on the > export, remounted and my problem was solved. > > > -- > kdesu ownership change > https://bugs.launchpad.net/bugs/155032 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 144722] Re: kdesu leads to no permission for X
*** This bug is a duplicate of bug 155032 *** https://bugs.launchpad.net/bugs/155032 Hey! It worked! I can run things again! On Nov 23, 2007 9:06 AM, Frode M. Døving <[EMAIL PROTECTED]> wrote: > *** This bug is a duplicate of bug 155032 *** > https://bugs.launchpad.net/bugs/155032 > > If you did not have this problem in feisty, you can remove the kdesudo > package, to change back to the real 'kdesu'. > 'sudo dpkg -P kdesudo' in a konsole. > > While kdesu have some issues that kdesudo address, kdesudo introduces > its own bunch of new issues. > > > -- > kdesu leads to no permission for X > https://bugs.launchpad.net/bugs/144722 > You received this bug notification because you are a direct subscriber > of the bug. > -- kdesu leads to no permission for X https://bugs.launchpad.net/bugs/144722 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
Re: [Bug 155032] Re: kdesu ownership change
In that case, there must be something else wrong as well. The kdesudo ubuntu2.2 did not work for me, programs could not connect to the X server. If I recall correctly, issueing an "xhost +" would resolve that. Removing kdesudo and using kdesu instead worked for me. Other people have reported that removing the option root_squash from the NFS share made it work for them, but I am not root at the faculties main file server, so I can't test that. Frode M. Døving wrote: > The current version of kdesudo in gutsy and hardy does not need root-write > access to $HOME. > The kdesudo version released in the first gutsy, did however start programs > as root, but with the users environment variables. > This evil and ugly bug told programs like adept, dolphin, konqueror and > others, > to save their configuration files to the users $HOME/.kde/ folder, > even when the programs actually were running as the root user. > The result is root-owned files in the users home directory once a program is > executed with kdesudo. > This issue is fixed in the ubuntu2.2 version in gutsy and in the hardy > version. > > One should check the user home directory for root-ownership on configuration > files, as that can be frustrating. > Saving new configurations, bookmarks, settings etc. as the user might not > work at all, if this is the case. > -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 155032] Re: kdesu ownership change
Just read my original bug report, 144722, which is marked as duplicate of this one. On Nov 24, 2007 4:47 PM, maybeway36 <[EMAIL PROTECTED]> wrote: > Looks like someone should file another bug. > > > On Nov 24, 2007 2:29 AM, wateenellende <[EMAIL PROTECTED]> wrote: > > In that case, there must be something else wrong as well. > > > > The kdesudo ubuntu2.2 did not work for me, programs could not connect to > > the X server. If I recall correctly, issueing an "xhost +" would resolve > > that. > > > > Removing kdesudo and using kdesu instead worked for me. > > > > Other people have reported that removing the option root_squash from the > > NFS share made it work for them, but I am not root at the faculties main > > file server, so I can't test that. > > > > > > > > Frode M. Døving wrote: > > > The current version of kdesudo in gutsy and hardy does not need > > > root-write access to $HOME. > > > The kdesudo version released in the first gutsy, did however start > > > programs as root, but with the users environment variables. > > > This evil and ugly bug told programs like adept, dolphin, konqueror and > > > others, > > > to save their configuration files to the users $HOME/.kde/ folder, > > > even when the programs actually were running as the root user. > > > The result is root-owned files in the users home directory once a program > > > is executed with kdesudo. > > > This issue is fixed in the ubuntu2.2 version in gutsy and in the hardy > > > version. > > > > > > One should check the user home directory for root-ownership on > > > configuration files, as that can be frustrating. > > > Saving new configurations, bookmarks, settings etc. as the user might not > > > work at all, if this is the case. > > > > > > > -- > > > kdesu ownership change > > https://bugs.launchpad.net/bugs/155032 > > You received this bug notification because you are a direct subscriber > > of a duplicate bug. > > > > -- > kdesu ownership change > https://bugs.launchpad.net/bugs/155032 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155032] Re: kdesu ownership change
Does anyone know how connections to X are made ? If this is completely independent from any file owner issue, then bug 144722 is not a duplicate of this bug and should be treated separately. Unfortunately I can't find an "unduplicate" button. -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155032] Re: kdesu ownership change
maybeway36 wrote: > Seems like a different issue, all right. I don't use NFS, and it works > fine here. I thought the same, but maybe we are wrong. Here's why: gogh wrote: > I have exactly the same behavior as wateenellende here. > kdesu version 1.1-0ubuntu2.2 doesn't fix it. Brian Buchanan wrote: > I set no_root_squash on the export, remounted and my problem was solved. gogh wrote: > I confirm that I have the same no_root_squash behaviour. However: Frode M. Døving wrote: > The current version of kdesudo in gutsy and hardy does not need root-write > access to $HOME. But if that is the case, why would root need write-access (through "no_root_squash") on $HOME to be able to connect to X ? My guess (and only explanation) is that kdesu version 1.1-0ubuntu2.2 is still trying to write to $HOME to handle the connection to X. So, a) it seems at least related to this bug; (and we can't "unduplicate" anyway); b) kdesu version 1.1-0ubuntu2.2 needs another fix. -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155032] Re: kdesu ownership change
Just checked today, as I saw that kdesudo was updated. Still can't connect to X server. (original bug 144722, marked as duplicate of this one) I'm a bit lost, did there exist a version that did not have this problem ? If so, is this the fix that was uploaded to Hardy ? If that is the case, can we have a fix in Gutsy too ? $ dpkg -s kdesudo Architecture: amd64 Version: 1.1-0ubuntu2.2 . $ kdesudo adept_updater X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 171 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device Xlib: connection to ":0.0" refused by server Xlib: No protocol specified adept_updater: cannot connect to X server :0 -- kdesu ownership change https://bugs.launchpad.net/bugs/155032 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 135794] Re: [gutsy] command-not-found not found
Yes, we can mark it as resolved. I just don't know how to do that :-) On Nov 17, 2007 10:20 PM, RW Penney <[EMAIL PROTECTED]> wrote: > Can this bug be marked as resolved? > > Package bash-3.2-0ubuntu11, as used in xubuntu7.10, appears to correctly > reference /usr/lib/command-not-found in /etc/bash.bashrc. > > -- > [gutsy] command-not-found not found > https://bugs.launchpad.net/bugs/135794 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy] command-not-found not found https://bugs.launchpad.net/bugs/135794 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
Re: [Bug 158294] Re: [gutsy/amd64] kernel won't boot
Yes, that fixed it. On Nov 19, 2007 10:33 PM, Leann Ogasawara <[EMAIL PROTECTED]> wrote: > Hi Wateenellende, > > Just to confirm, changing the kernel config option to > CONFIG_IDE_MAX_HWIFS=10 fixes this bug for you? Thanks. > > ** Changed in: linux-source-2.6.22 (Ubuntu) >Status: New => Incomplete > > > -- > [gutsy/amd64] kernel won't boot > https://bugs.launchpad.net/bugs/158294 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy/amd64] kernel won't boot https://bugs.launchpad.net/bugs/158294 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
Re: [Bug 158294] Re: [gutsy/amd64] kernel won't boot
Hi, I just read https://wiki.ubuntu.com/StableReleaseUpdates, and the special section for Kernels: "Critical bug fixes. These are categorized as non-security issues relating to bugs that affect a large range of users. These are bugs that keep users from reliably using their systems, or prevent booting at all. These patches must pass through rigorous testing by Canonical/Ubuntu and the community at large." It would seem to me that the criteria have been met; anyone who has an extra IDE-controller in their system is likely unable to boot. Without fix, this means that using Gutsy is practically impossible, unless you take the time to recompile the kernel, then download and recompile all restricted modules (which does not work to well either). I've already fixed it for myself, so if it's not fixed I don't mind, but would recommend to reconsider anyway. Best, Fokko On Nov 20, 2007 5:20 PM, Leann Ogasawara <[EMAIL PROTECTED]> wrote: > Thanks for the confirmation. I'm retargeting this bug towards the > upcoming Hardy kernel and have tagged it as "hardy-kernel-candidate". > However against the linux-source-2.6.22 package this is being marked as > "Won't Fix" as it does not meet the criteria for a stable release > update. To learn more about the stable release update process please > refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks! > > ** Changed in: linux-source-2.6.22 (Ubuntu) >Status: Incomplete => Won't Fix > > ** Tags added: bitesize hardy-kernel-candidate > > > -- > [gutsy/amd64] kernel won't boot > https://bugs.launchpad.net/bugs/158294 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy/amd64] kernel won't boot https://bugs.launchpad.net/bugs/158294 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
Re: [Bug 157909] Re: IDE0 and IDE1 taken over by SATA in Gutsy
I second to that, and I would like to add that the result is a not a minor inconvenience, but an unbootable system. IMHO "System becomes unbootable" qualifies as excellent example of "Bugs which represent severe regressions from the previous release of Ubuntu" > > Do we even know why the setting was changed? > To my knowledge, I could very well be wrong, it is a new parameter. Matt Mossholder wrote: > I would beg to differ with the statement that this does not meet the SRU > criteria. In particular, this seems to be a "Bugs which represent severe > regressions from the previous release of Ubuntu". Previous versions > supported these configurations, while with gutsy the follow is the case: > > * the configurations impacted are common (how many SATA ports come on modern > motherboards? 6? 8?) > * the impact of fixing the situation is minimal (very slight increase in the > size of a small table) > * the systems impacted are ones specifically being targeted by Ubuntu > (desktops and small to mid-sized servers). > > In effect, gutsy has taken something that "just worked" and "just broke" > it. > > Do we even know why the setting was changed? > -- IDE0 and IDE1 taken over by SATA in Gutsy https://bugs.launchpad.net/bugs/157909 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
Re: [Bug 137735] Re: [gutsy] wine causes hard lockup - every time
The driver distributed by VIA (www.viaarena.com) does not suffer from this problem. It suffers from other problems, though. jeroenvrp wrote: > This is the right package. Also bug 149609 had this already set, so this > should be the duplicate, not the way arounf. Anyhow that doesn't matter > if the bug is marked invalid anymore. Now marked as confirmed. > > ** Changed in: xserver-xorg-video-via (Ubuntu) > Sourcepackagename: wine => xserver-xorg-video-via >Status: Invalid => Confirmed > -- [gutsy] wine causes hard lockup - every time https://bugs.launchpad.net/bugs/137735 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
Re: [Bug 157909] Re: IDE0 and IDE1 taken over by SATA in Gutsy
Even disregarding SATA at all: IDE interfaces and drives are still being used, produced, and sold, and, IMHO, it should be supported. A gutsy system is unbootable when an extra IDE controller in addition to the IDE controllers on the main board is installed, which is quite likely for anyone having >4 IDE drives. That may be rare, but sufficiently common to affect a significant number of systems. Aaron C. de Bruyn wrote: > Re the comment about motherboards and interfaces, I just purchased a new > board supports 12 SATA connections onboard. It also supports 2 IDE > connections. I'm building a mid-range storage server for my home > office. Eventually I'll have enough in the budget to toss a RAID card > in instead of doing softraid. This could complicate things more due to > the fact that a lot of SATA RAID controllers I run into present the > array as an IDE drive. > > When I did my initial testing on this bug, I noticed the 'make > menuconfig' section of the kernel would only allow me to specify a > maximum of 9. > > On one hand, it's probably unheard of to find a system that supports 9 > IDE drives (requiring 4+ IDE interfaces on the board), but on the other > hand, it's not unheard of to find RAID cards exposing themselves as IDE > drives which could give you a huge number of IDE drives for the system. > -- IDE0 and IDE1 taken over by SATA in Gutsy https://bugs.launchpad.net/bugs/157909 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
[Bug 103462] Re: [apport] thunar-tpa crashed with SIGSEGV
I seem to have the same problem. Running xubuntu, suddenly apport pops up saying that thunar crashed. ** Changed in: thunar (Ubuntu) Status: Invalid => New -- [apport] thunar-tpa crashed with SIGSEGV https://bugs.launchpad.net/bugs/103462 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
Re: [Bug 131086] Re: valgrind didn't recognize the instruction
I sure hope you realize you just asked me to a) install a beta OS on a machine; b) 3 /years/ after I filed a bug report; c) to try some code that was under active development 3 years ago; d) using a different compiler (was gcc4.2, now gcc4.4) ? Not to worry though, my job is actually not that important, I'm sure I'll find time to do that. Loïc Minier wrote: > Could you please retry with valgrind 3.6.0 in Ubuntu 10.04 LTS beta? > Thanks! > -- valgrind didn't recognize the instruction https://bugs.launchpad.net/bugs/131086 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 1454817] [NEW] Screen shows "starting version 219" after upgrade to 2015.04
Public bug reported: System was working fine with previous ubuntu version and Nvidia 640 GPU. Following upgrade to 2015.04, I only see "starting version 219". There is a problem with X. Workaround: find screwdriver, remove Nvidia gpu, use intel graphics :-( Please let me know what other information I should provide, but beware that I can only use the computer with the nvidia card removed... ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nvidia-346-updates 346.59-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 13 21:37:30 2015 InstallationDate: Installed on 2014-03-22 (417 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: nvidia-graphics-drivers-346-updates UpgradeStatus: Upgraded to vivid on 2015-04-24 (19 days ago) ** Affects: nvidia-graphics-drivers-346-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454817 Title: Screen shows "starting version 219" after upgrade to 2015.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346-updates/+bug/1454817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454817] Re: Screen shows "starting version 219" after upgrade to 2015.04
Note that this is NOT a duplicate of 1432171, see comment #23 there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454817 Title: Screen shows "starting version 219" after upgrade to 2015.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346-updates/+bug/1454817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432171] Re: [udev] Shows "starting version 219" boot message even with "quiet"
ok, see bug 1454817 for graphics issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: [udev] Shows "starting version 219" boot message even with "quiet" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1454817] Re: Screen shows "starting version 219" after upgrade to 2015.04
I didn't get it to work with nouveau either. Also not 100% sure if this is an issue with nvidia drivers or something else - X or systemd. On Sun, May 17, 2015 at 9:46 PM, Jakub Klecki wrote: > I can only say that the workaround that worked for me was deactivating > Nvidia proprietary drivers and using only Nouveau driver. Fortunately > there is no need of removing GPU :) However, it would be nice if the > issue would be fixed and we could launch the system while using original > Nvidia graphic drivers. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1454817 > > Title: > Screen shows "starting version 219" after upgrade to 2015.04 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346-updates/+bug/1454817/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454817 Title: Screen shows "starting version 219" after upgrade to 2015.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346-updates/+bug/1454817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927751] Re: unity segfaults very often since update, seemingly when I press alt-tab
*** This bug is a duplicate of bug 916879 *** https://bugs.launchpad.net/bugs/916879 OK, I've pressed alt-tab and submitted the resulting crash file to bug #916879 and marked this one as a duplicate. On 02/09/2012 05:17 PM, Omer Akram wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. However, your crash report is either missing or > challenging to deal with as a ".crash" file. Please follow these > instructions to have apport report a new bug about your crash that can > be dealt with by the automatic retracer. > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > Now open your file manager, navigate to your /var/crash directory and open > the crash report you wish to submit. > If this fails you will have to open a terminal and file your report with > 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash > is the crash you would like to report. If you get an error that you aren't > allowed to access this report you will have to file it with 'sudo ubuntu-bug > /var/crash/_my_crash_report.crash'. > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. Thanks in advance for your cooperation and understanding. > > ** Changed in: unity (Ubuntu) > Status: Confirmed => Invalid > ** This bug has been marked a duplicate of bug 916879 compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927751 Title: unity segfaults very often since update, seemingly when I press alt- tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 916879] Re: compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority()
"me too!" Please take the previous two comments into consideration. There are more people that I know that will wait with an upgrade until the bugs are ironed out, as mentioned in the previous post. That would mean that people will continue to be affected by this intrusive bug until at least the end of June or so. It would also be nice if there were a way of communicating that one agrees with a previous comment other than by posting "me too" messages. So I've asked launchpad support to add something along the lines of a "+1" or "like" button. See launchpad bug #932839. On 02/15/12 15:05, Zentai Andras wrote: > I hope this bug will be solved in Oneiric too. > I'm not planning to install Precise in the first few months after it will be > released. > (The latest verison of Precise is not so precise yet. I test it every day in > a Virtualbox environment, > but it not convinced me yet to be brave enough to upgrade my Oneiric.) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916879 Title: compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority() To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/916879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098572] [NEW] does not remember account
Public bug reported: Everytime I start empathy, I need to enter my account details. Whenever empathy closes and restarts, the information is lost. Currently, every time I therefore import settings from pidgin, and then continue. Observed behaviour: empathy forgets all account information when closed Expected behaviour: empathy should remember account information % lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 % apt-cache policy empathy empathy: Installed: 3.4.2.3-0ubuntu1 Candidate: 3.4.2.3-0ubuntu1 Version table: *** 3.4.2.3-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.1-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ** Affects: empathy (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/1098572 Title: does not remember account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1098572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1098572] Re: does not remember account
On 01/31/2013 07:21 PM, Bilal Shahid wrote: > i guess its a online accounts bug not a empathy bug > Could you clarify that statement a bit ? What is an "online accounts bug" exactly ? TIA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098572 Title: does not remember account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1098572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098572] Re: does not remember account
Hi, bug #1029289 is not a duplicate. 1) I do not have to re-authenticate, I have to re-enter all account info every time. 2) I'm logging on to MSN, not google. So, could you re-open this bug as a separate issue ? Thanks. ** This bug is no longer a duplicate of bug 1029289 Need to authorize my google account each time I boot the computer ** Changed in: empathy (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098572 Title: does not remember account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1098572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871618] [NEW] package flashplugin-installer 10.3.183.10ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 861584 *** https://bugs.launchpad.net/bugs/861584 Public bug reported: Clicked on 'install' in the ubuntu software center, then it started whining about problems. $ sudo apt-get install flashplugin-nonfree worked just fine ProblemType: Package DistroRelease: Ubuntu 11.10 Package: flashplugin-installer 10.3.183.10ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Mon Oct 10 09:23:33 2011 DuplicateSignature: Setting up flashplugin-installer (10.3.183.10ubuntu5) ... nspluginwrapper: /usr/lib/flashplugin-installer/libflashplayer.so is not a valid NPAPI plugin dpkg: error processing flashplugin-installer (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2) SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 10.3.183.10ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871618 Title: package flashplugin-installer 10.3.183.10ubuntu5 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/flashplugin-nonfree/+bug/871618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871618] Re: package flashplugin-installer 10.3.183.10ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 861584 *** https://bugs.launchpad.net/bugs/861584 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871618 Title: package flashplugin-installer 10.3.183.10ubuntu5 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/flashplugin-nonfree/+bug/871618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927751] [NEW] unity segfaults very often since update, seemingly when I press alt-tab
Public bug reported: [ 407.817045] compiz[1857]: segfault at 2712278e ip 01f6a096 sp bfb46640 error 4 in libunityshell.so[1deb000+20e000] [ 1254.028553] compiz[3787]: segfault at b ip 0828a091 sp bfe921f0 error 4 in libunityshell.so[810b000+20e000] [ 1274.678363] compiz[4634]: segfault at 43 ip 016e2091 sp bfbcc220 error 4 in libunityshell.so[1563000+20e000] [ 1559.632682] compiz[4997]: segfault at b ip 017f8091 sp bfb5ebc0 error 4 in libunityshell.so[1679000+20e000] [ 1651.900972] compiz[6725]: segfault at 51c3682b ip 0242c091 sp bfb3fb30 error 4 in libunityshell.so[22ad000+20e000] So, essentially my laptop had become unusable until I learned not to hit Alt-Tab. This started since a recent upgrade. Package: unity Status: install ok installed Priority: optional Section: gnome Installed-Size: 2480 Maintainer: Ubuntu Developers Architecture: i386 Version: 4.28.0-0ubuntu2 This is 11.10. Please let me know if you need any more information or testing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,grid,move,gnomecompat,resize,place,mousepoll,session,wall,snap,animation,imgpng,vpswitch,workarounds,fade,expo,ezoom,scale,unitymtgrabhandles,unityshell] CompositorRunning: compiz Date: Mon Feb 6 18:29:56 2012 DistUpgraded: Log time: 2011-10-19 18:58:09.060032 DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0241] Subsystem: Acer Incorporated [ALI] Device [1025:0241] MachineType: Packard Bell DOTS ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=da872ecf-7c12-4020-84a7-f39e31c415e6 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-10-22 (106 days ago) dmi.bios.date: 03/26/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DOTS dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01 dmi.modalias: dmi:bvnAcer:bvrV1.01:bd03/26/2009:svnPackardBell:pnDOTS:pvrV1.01:rvnAcer:rnDOTS:rvrV1.01:cvnAcer:ct1:cvrV1.01: dmi.product.name: DOTS dmi.product.version: V1.01 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 needs-reassignment oneiric regression-update running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927751 Title: unity segfaults very often since update, seemingly when I press alt- tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927751] Re: unity segfaults very often since update, seemingly when I press alt-tab
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927751 Title: unity segfaults very often since update, seemingly when I press alt- tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 927751] Re: unity segfaults very often since update, seemingly when I press alt-tab
On 02/06/2012 09:50 PM, Andyceo wrote: > Can confirm this issue on my Dell Inspiron 1525, but not on my Lenovo > S10-3 and HP Mini (both Atom processors). > My regular desktop PC (AMD64/ati radeon) and my pc at work(core i7/ati) have similar settings, but they are fine. Those are 64-bit, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927751 Title: unity segfaults very often since update, seemingly when I press alt- tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200529] [NEW] window manager puts text over close button
Public bug reported: When a window is maximized, the close/minimize/maximize buttons appear in the top left, and are visible when the mouse pointer hovers over the bar, but when the mouse pointer comes close to those buttons, a text appears over them and you can't click them. Which is annoying if you are trying to close a window. I'll try to attach a screenshot, using chromium as an example here. The text 'new window' covers the buttons when I try to click on them. % lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 % apt-cache policy unity unity: Installed: 5.20.0-0ubuntu2 Candidate: 5.20.0-0ubuntu2 Version table: *** 5.20.0-0ubuntu2 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.10.0-0ubuntu6 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Expected: be able to click on the close/minimize/maximize button Happened: text covers the buttons and renders them unusable ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 Uname: Linux 3.2.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Jul 12 10:34:27 2013 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity ** Attachment added: "screenshot showing text covering close/minimize/maxize buttons" https://bugs.launchpad.net/bugs/1200529/+attachment/3734281/+files/unity-bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200529 Title: window manager puts text over close button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1200529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198483] Re: install-keymap doesn't make setting permanent
The problem is now in the console-common package. The keymay is not set at boot time. Originally, I had a US-qwerty layout, then changed it to dvorak. Now, the consoles are qwerty, to log into X i have to type my password in qwerty, and then I have a dvorak session. Running the script 'sudo /etc/init.d/keymap.sh' does not fix the problem, although /etc/console/boottime.kmap.gz is definitely a dvorak layout. If I run 'sudo loadkeys -q /etc/console/boottime.kmap.gz' from the command line, it works. So my suspicion is that the /etc/init.d/keymap.sh script is broken. I have other computers on which I installed ubuntu with a dvorak keyboard right away, and the problem is not present on those. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/198483 Title: install-keymap doesn't make setting permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/198483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198483] Re: install-keymap doesn't make setting permanent
The keymaps.sh script stops because it detects setupcon, and decides that console-setup will take over. console-setup by means of setupcon loads /etc/console-setup/cached.kmap.gz , which is qwerty. Overwriting it with a dvorak-keymap and then calling: $ sudo setupcon -v $ sudo update-initramfs -k all -u will make sure all terminals have the desired keymap on boot. Question: what is the regular automated procedure to do this ? Remark: I now have dvorak on console, dvorak in X - but I must still type my password in qwerty to log into X, even though I've selected dvorak in the keyboard menu below. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/198483 Title: install-keymap doesn't make setting permanent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/198483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 627357] Re: a symbolic link is missing and the lib is not found
On 03/24/2011 09:07 PM, Steve Langasek wrote: > This is not a bug in libgd2. Properly linked applications do not > require 'libgd.so' at runtime; they access libgd.so.2 instead. > > ** Changed in: libgd2 (Ubuntu) > Status: New => Invalid > Well, in that case, it's still a bug, albeit in 'php-gd' rather than libgd2. So, could this bug be re-opened and associated with 'php-gd' ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/627357 Title: a symbolic link is missing and the lib is not found -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530569] Re: hal-disable-polling crash: buffer overflow detected
Just installed natty: Setting up laptop-mode-tools (1.57-1ubuntu1) ... * Enabling laptop mode... *** buffer overflow detected ***: hal-disable-polling terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fdcdfb8f1d7] /lib/x86_64-linux-gnu/libc.so.6(+0xfd0f0)[0x7fdcdfb8e0f0] /lib/x86_64-linux-gnu/libc.so.6(+0xfd70b)[0x7fdcdfb8e70b] hal-disable-polling[0x401579] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xff)[0x7fdcdfaafeff] hal-disable-polling[0x400f29] === Memory map: 0040-00403000 r-xp 08:71 557420 /usr/bin/hal-disable-polling 00602000-00603000 r--p 2000 08:71 557420 /usr/bin/hal-disable-polling 00603000-00604000 rw-p 3000 08:71 557420 /usr/bin/hal-disable-polling 02397000-023b8000 rw-p 00:00 0 [heap] $ dpkg -s hal Package: hal Status: install ok installed Priority: optional Section: admin Installed-Size: 1764 Maintainer: Ubuntu Developers Architecture: amd64 Version: 0.5.14-5+svn1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/530569 Title: hal-disable-polling crash: buffer overflow detected -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627357] [NEW] a symbolic link is missing and the lib is not found
Public bug reported: Binary package hint: libgd2 # dpkg -L libgd2-xpm /. /usr /usr/share /usr/share/doc /usr/share/doc/libgd2-xpm /usr/share/doc/libgd2-xpm/buildinfo.gz /usr/share/doc/libgd2-xpm/NEWS.gz /usr/share/doc/libgd2-xpm/README.html /usr/share/doc/libgd2-xpm/readme.jpn /usr/share/doc/libgd2-xpm/copyright /usr/share/doc/libgd2-xpm/README.gz /usr/share/doc/libgd2-xpm/changelog.Debian.gz /usr/lib /usr/lib/libgd.so.2.0.0 /usr/lib/libgd.so.2 As you see, there is no link '/usr/lib/libgd.so', and applications like php-gd can't find the library. The fix: # ln -s /usr/lib/libgd.so.2 /usr/lib/libgd.so # service apache2 restart Now all is fine! ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libgd2-xpm 2.0.36~rc1~dfsg-3.1ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Tue Aug 31 13:18:50 2010 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libgd2 ** Affects: libgd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- a symbolic link is missing and the lib is not found https://bugs.launchpad.net/bugs/627357 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 627357] Re: a symbolic link is missing and the lib is not found
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/627357/+attachment/1531616/+files/Dependencies.txt -- a symbolic link is missing and the lib is not found https://bugs.launchpad.net/bugs/627357 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
