[Bug 1181441] Re: 10de:05e2 [DX79SI] nouveau corruption and then hang
I have experienced this bug on. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS" Ubuntu 3.13.0-40.69-generic 3.13.11.10 I have just switched to the nVidia Proprietary driver as it's happened about four times. I've attached an exceprt of my /var/log/syslog from when it happened. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181441/+attachment/4276333/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181441 Title: 10de:05e2 [DX79SI] nouveau corruption and then hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036673] Re: empathy-accounts corrupted and now crashing/broken
The difference I am seeing in my situation is that when I remove the duplicate google account that is failing to authenticate, I can no longer use the Accounts window. It opens, then immediately closes. If I run it from a bash shell I get: $ empathy-accounts ** ERROR:empathy-contact-widget.c:402:contact_widget_details_update_edit: assertion failed: (spec != NULL) Aborted (core dumped) $ Would the core file be useful to debugging this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036673 Title: empathy-accounts corrupted and now crashing/broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1036673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036673] Re: empathy-accounts corrupted and now crashing/broken
Having searched, I think I have Bug #1187355 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036673 Title: empathy-accounts corrupted and now crashing/broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1036673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036673] Re: empathy-accounts corrupted and now crashing/broken
I am experiencing this same problem. What extra information can I provide to improve the situation? I'm on 12.04 LTS and I'm up to date as of 2013-12-03@12:43 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036673 Title: empathy-accounts corrupted and now crashing/broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1036673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853849] Re: Update Fails due to btrfs not being able to take a snapshot
I'm getting the same error messages on 12.04.2 LTS ian@ubuntu-pc:~$ lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 ian@ubuntu-pc:~$ sudo apt-btrfs-snapshot supported [sudo] password for ian: Supported Failure using Updater shows this error: installArchives() failed: Supported Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-t8mziy/@' in '/tmp/apt-btrfs-snapshot-mp-t8mziy/@apt-snapshot-2013-03-19_08:02:05' Supported Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-9V5i0H/@' in '/tmp/apt-btrfs-snapshot-mp-9V5i0H/@apt-snapshot-2013-03-19_08:02:06' Supported Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-WAjeCZ/@' in '/tmp/apt-btrfs-snapshot-mp-WAjeCZ/@apt-snapshot-2013-03-19_08:02:06/@' ERROR: cannot snapshot '/tmp/apt-btrfs-snapshot-mp-WAjeCZ/@' On the command line, it works fine. See attached ** Attachment added: "success using apt-get on cli" https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/853849/+attachment/3582718/+files/apt-btrfs-snapshot_cli-success.text ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853849 Title: Update Fails due to btrfs not being able to take a snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/853849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244160] [NEW] ltsp-update-kernels does not create separate pxelinux directory in /var/lib/tftpboot for a client in a non-default location
Public bug reported: Binary package hint: ltsp-server Version: Ubuntu 8.04 "Hardy" ltsp-server: Installed: 5.0.40~bzr20080212-0ubuntu7 Candidate: 5.0.40~bzr20080212-0ubuntu7 Version table: *** 5.0.40~bzr20080212-0ubuntu7 0 500 http://gb.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 5.0.40~bzr20080212-0ubuntu6 0 500 http://gb.archive.ubuntu.com hardy/main Packages If you create additional builds of the client, with this: ltsp-build-client --base /opt/ltsp-test Then change the dhcp server entry, so that the Root-path is: /opt/ltsp-test Then run this: ltsp-update-kernels The client should boot and pick up the small pxelinux, then swapping out the 4Mb initrd for the NBD image as the '/' of the filesystem. It should mount the NBD image in /opt/ltsp-test. It ends up mounting the default one in /opt/ltsp, instead of the new one in /opt/ltsp-test. I have tried to look into why this is, and I have found the file in the initrd.img that contains the instructions as to which NBD to mount: If you: mkdir /tmp/pxelinux-initrd cd /tmp/pxelinux-initrd zcat /var/lib/tftpboot/ltsp/i386/initrd.img | cpio -i This extracts the initrd that is mounted for pxelinux to use, during the PXEboot process. In here is: scripts/ltsp_nbd This file looks to the variable 'nbdroot' to get the ipaddress and port number to mount the NBD image from. This variable is not being set correctly. when an alternative client build is created. The DHCP server is specifying /opt/ltsp-test to show that a different image needs to be used. This does not seem to be picked up to get the system to mount the alternative NBD image. The ltsp_nbd script defaults to port 2000. It is possible to specify a different NBD server and port, as arguments to the kernel in the pxelinux.cfg, using the nbdroot=: But this means configuration needs to be done in two places. It should only need to be done once, when the ltsp-build-client --base is issued. I may be completely missing something, and not understanding how this works. ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: ltsp-server Version: Ubuntu 8.04 "Hardy" ltsp-server: Installed: 5.0.40~bzr20080212-0ubuntu7 Candidate: 5.0.40~bzr20080212-0ubuntu7 Version table: *** 5.0.40~bzr20080212-0ubuntu7 0 500 http://gb.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 5.0.40~bzr20080212-0ubuntu6 0 500 http://gb.archive.ubuntu.com hardy/main Packages If you create additional builds of the client, with this: ltsp-build-client --base /opt/ltsp-test Then change the dhcp server entry, so that the Root-path is: /opt/ltsp-test Then run this: ltsp-update-kernels The client should boot and pick up the small pxelinux, then swapping out the 4Mb initrd for the NBD image as the '/' of the filesystem. It should mount the NBD image in /opt/ltsp-test. It ends up mounting the default one in /opt/ltsp, instead of the new one in /opt/ltsp-test. I have tried to look into why this is, and I have found the file in the initrd.img that contains the instructions as to which NBD to mount: If you: mkdir /tmp/pxelinux-initrd cd /tmp/pxelinux-initrd zcat /var/lib/tftpboot/ltsp/i386/initrd.img | cpio -i This extracts the initrd that is mounted for pxelinux to use, during the PXEboot process. In here is: scripts/ltsp_nbd This file looks to the variable 'nbdroot' to get the ipaddress and port number to mount the NBD image from. This variable is not being set correctly. when an alternative client build is created. The DHCP server is specifying /opt/ltsp-test to show that a different image needs to be used. This does not seem to be picked up to get the system to mount the alternative NBD image. The ltsp_nbd script defaults to port 2000. It is possible to specify a different NBD server and port, as arguments to the kernel in the pxelinux.cfg, using the nbdroot=: But this means configuration needs to be done in two places. It should only need to be done once, when the ltsp-build-client --base is issued. I may be completely missing something, and not understanding how this works. - - The ltsp-build-client sets up the pxelinux for the default client, but - not for any subsequent ones -- ltsp-update-kernels does not create separate pxelinux directory in /var/lib/tftpboot for a client in a non-default location https://bugs.launchpad.net/bugs/244160 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 205072] Re: macbook 3.1: Resume from suspend sometimes fails.
** Description changed: On my macbook 3.1 suspend and resume works over 50% of the time, however when it does not work, this happens: * I open the lid of my macbook 3,1 - * The led next the infra-red port goes out + * The led next to the infra-red port goes out * The dvd drive makes it's usual noise * Then nothing The screen does not display anything, it is as if the screen is not given power. The bug seems to be a more comprehensive failure of the resume as I cannot power the system down using known working keyboard shortcuts. There is a similar bug https://help.ubuntu.com/community/MacBook_Santa_Rosa#head-b34e7facb238e50588835bb1030e0a2e0906c940 but this similar bug allows you to see something on the screen if you look carefully. It is just the backlight that does not come on. I don't know how to debug this but I assume I would have to perform some sort of pre-emptive strike. Establishing something that observes the state of things when the system is suspended, then logging that state if resume succeeds. From this log one could perhaps see that one state is not listed. I suspect it is something to do with one of the following: * Connected to mains power during suspend * Disconnected/Connected to mains power while suspended * On battery power during resume * On mains power during resume * Any other combination of power state, including charge level of battery. -- macbook 3.1: Resume from suspend sometimes fails. https://bugs.launchpad.net/bugs/205072 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 205059] Re: macbook 3.1: Internal speakers don't silence when headphone socket is used from boot.
** Summary changed: - macbook 3.1: Internal speakers don't silence when headphone socket is used + macbook 3.1: Internal speakers don't silence when headphone socket is used from boot. ** Description changed: - I have a MacBook 3,1 and when I connect headphones or speakers to the - headphones socket, audio comes out of the headphones and the MacBook's - internal speakers. + edited: [EMAIL PROTECTED] + I have a MacBook 3,1 and when I connect headphones or speakers to the headphones socket, before booting the laptop, audio comes out of both the headphones and the MacBook's internal speakers. If, the headphones are unplugged and replaced, normal operation is restored. - I suppose this means that the function of switching from speakers to - headphones is software or firmware controlled. + If I perform the same scenario in OSX leopard, nothing goes wrong. I + suppose this means that the function of switching from speakers to + headphones is software controlled. -- macbook 3.1: Internal speakers don't silence when headphone socket is used from boot. https://bugs.launchpad.net/bugs/205059 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 205059] Re: macbook 3.1: Internal speakers don't silence when headphone socket is used
ramaboo, you are absolutely right. That is the actual behaviour I am getting. I did not look into this thoroughly enough. I am going to change the bug title and description. I am using Gutsy by the way. -- macbook 3.1: Internal speakers don't silence when headphone socket is used https://bugs.launchpad.net/bugs/205059 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 205072] Re: macbook 3.1: Resume from suspend sometimes fails.
I'm using Gutsy. The Graphics card is reported as the following, by lspci: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) As far as assigning this to a package, I can't see a field for package in the "Edit description/tags" page, and the only other link I can see relating to package is "Also affects: + Distribution/Package…" in the top right. I this second link the one I should use? Also I don't know which package suspend-resume issues should be filed under -- macbook 3.1: Resume from suspend sometimes fails. https://bugs.launchpad.net/bugs/205072 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 162083] Re: macbook3, 1 and apple aluminum keyboards fn key does not work
** Tags added: macbook3.1 -- macbook3,1 and apple aluminum keyboards fn key does not work https://bugs.launchpad.net/bugs/162083 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 162347] Re: no sound on rev3 MacBook (Santa Rosa)
** Tags added: macbook3.1 -- no sound on rev3 MacBook (Santa Rosa) https://bugs.launchpad.net/bugs/162347 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 193544] Re: Synaptics touchpad not detected on MacBook Santa Rosa
*** This bug is a duplicate of bug 173411 *** https://bugs.launchpad.net/bugs/173411 ** Tags added: macbook3.1 -- Synaptics touchpad not detected on MacBook Santa Rosa https://bugs.launchpad.net/bugs/193544 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 27109] Re: nautilus uses 100% cpu after closing a ssh session
I get the same as screwITfix on gutsy. It takes about 10 seconds for nautilus to come down from 100% CPU usage when you unmount the connection -- nautilus uses 100% cpu after closing a ssh session https://bugs.launchpad.net/bugs/27109 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 162090] Re: appletouch does not recognize trackpad in macbook3, 1
This patch did not work for me. I don't have amd64 architecture. Is there anything in the patch that makes it architecture specific? When the Xorg log says "synaptics module", is that a kernel module, or a module in Xorg? -- appletouch does not recognize trackpad in macbook3,1 https://bugs.launchpad.net/bugs/162090 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 158544] Re: feature request: bring back menu option from 2.19.6.1
If this is the ability of deskbar to float above the gnome-panel, and not create a completely new window, then I second this request. -- feature request: bring back menu option from 2.19.6.1 https://bugs.launchpad.net/bugs/158544 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 118819] Re: power button freezes ubuntu, missing hibernate and suspend buttons
*** This bug is a duplicate of bug 118537 *** https://bugs.launchpad.net/bugs/118537 I'm getting the one minute delay with Gutsy now, even though we're now on final release. -- power button freezes ubuntu, missing hibernate and suspend buttons https://bugs.launchpad.net/bugs/118819 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 90902] Re: prism54: eeprom failed
Oh good On 26/08/07, Stefano Rivera <[EMAIL PROTECTED]> wrote: > For the record, Prism54 now works beautifully in Gutsy's 2.6.22-10 > > -- > prism54: eeprom failed > https://bugs.launchpad.net/bugs/90902 > You received this bug notification because you are a direct subscriber > of the bug. > -- Ian Ohr -- prism54: eeprom failed https://bugs.launchpad.net/bugs/90902 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
The firmware suggested in 90902 is for usb hardware. There is only one listing there for pci firmware and according to an md5sum, this is no different to the firmware shipped with feisty. I don' think this is a duplicate of bug 90902. If it is then the fix proposed in 90902 won't work. Unless usb firmware is not specific to usb hardware, bug then why would it be prism54usb? ** This bug is no longer a duplicate of bug 90902 prism54: eeprom failed -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
*** This bug is a duplicate of bug 90902 *** https://bugs.launchpad.net/bugs/90902 Wait, I see it now under the bug title -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
*** This bug is a duplicate of bug 90902 *** https://bugs.launchpad.net/bugs/90902 Has this bug actually been marked as a duplicate of Bug# 90902? -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
** Attachment added: "dmesg-2.log" http://librarian.launchpad.net/7451634/dmesg-2.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
** Attachment added: "dmesg-1.log" http://librarian.launchpad.net/7451632/dmesg-1.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
** Attachment added: "lspci-vvn.log" http://librarian.launchpad.net/7451628/lspci-vvn.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
Posted vvn twice, sorry. ** Attachment added: "lspci-vv.log" http://librarian.launchpad.net/7451631/lspci-vv.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
** Attachment added: "uname-a.log" http://librarian.launchpad.net/7451616/uname-a.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] Re: netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
** Attachment added: "lspci-vvn.log" http://librarian.launchpad.net/7451626/lspci-vvn.log -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 106987] netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom
Public bug reported: kernel hackers be aware: At first glance this appears to be a bug in the driver p54. But I have discovered a workaround which suggests it's not. This is why I did not put this against the linux-source-2.6.20 package. I have my system in a state now where if I boot the pc with the Netgear wireless card inserted, the output from dmesg shows: [ 36.698584] :03:00.0 (prism54pci): Cannot read eeprom! [ 36.698656] prism54pci: probe of :03:00.0 failed with error -22 The system does not show the network device wlan0. If I remove the card and re-insert it, problem solved, the card initialises, wlan0 appears and off I go to grab the latest ep. of lugradio. I have also booted from cold *without* the card inserted, and then proceeded to insert it, this works and I'm on the internet in seconds. I really need some help narrowing down the cause of this, obviously the environment the card is initialised in during boot is different to when it is inserted after boot. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Tags: netgear prism54 wireless ** Description changed: kernel hackers be aware: At first glance this appears to be a bug in the driver p54. But I have discovered a workaround which suggests it's not. - This is why I did not put this agalinux-source-2.6.20 package. + This is why I did not put this against the linux-source-2.6.20 package. I have my system in a state now where if I boot the pc with the Netgear wireless card inserted, the output from dmesg shows: [ 36.698584] :03:00.0 (prism54pci): Cannot read eeprom! [ 36.698656] prism54pci: probe of :03:00.0 failed with error -22 The system does not show the network device wlan0. If I remove the card and re-insert it, problem solved, the card initialises, wlan0 appears and off I go to grab the latest ep. of lugradio. I have also booted from cold *without* the card inserted, and then proceeded to insert it, this works and I'm on the internet in seconds. I really need some help narrowing down the cause of this, obviously the environment the card is initialised in during boot is different to when it is inserted after boot. ** Tags added: netgear prism54 wireless -- netgear WG511v1 PCMCIA card: prism54pci Cannot read eeprom https://bugs.launchpad.net/bugs/106987 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 105234] Re: Network manager says disconnected but is connected and working
I see this as fixed today on a system with wired eth0 and statically assigned IP. -- Network manager says disconnected but is connected and working https://bugs.launchpad.net/bugs/105234 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 105357] Re: Feisty wireless broken after update
I'm gonna file another bug in case my problem is a separate issue. I will post the bug# here after I have done that. -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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 90902] Re: prism54: eeprom failed
#90902 I apologise. This is not the bug I am experiencing. My bug is #105357. Sorry for the confusion. I did look into the source code for where this "eeprom read failed!" message is generated. The driver attempts to read the eeprom from the device but when it examines the buffer where the response from the card should be, there is less than the expected amount of data there. I suspect the usb URB puts no data in this buffer, because the system is requesting the information from the wrong device, or sent a malformed request. The former suggests a problem with usb device enumeration, the latter would be a problem with the driver itself. I am not a developer so this could all be horribly wrong. See /usr/src/linux/ubuntu/wireless/p54/prism54usb.c if you install the linux-source package and extract it to /usr/src/linux. Line 354 contains the condition to error out or not. That's pretty much the extent of my investigation until I realised this wasn't my itch, but is very similar. I get [ 37.620108] :03:00.0 (prism54pci): Cannot read eeprom! [ 37.620189] prism54pci: probe of :03:00.0 failed with error -22 -- prism54: eeprom failed https://bugs.launchpad.net/bugs/90902 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
Hi Peter, I have a Netgear WG511v1 with the isl3880 chipset that uses the prism54 driver natively. I too had no problem with this card until upgrading to Feisty on 2007-04-05. I clicked around with network-manager for a bit and got to the System | Administration |Network dialog. This showed two wireless devices although I only have the one prism54 card. wmaster0 was selected and wlan0 was not. I swapped it so that wlan0 was enabled. network-manager then showed me my home wireless network when I left clicked on the network-manager icon. I clicked to join the wireless network and it appeared not to be working. When I hovered over the network-manager icon it said something similar to "waiting to reteive key". What was hidden from me at the time due to a compiz bug was that network-manager had spawned a window asking me to enter the WEP key to join the network. A few alt-tab's later and I had input the key and joined the network. I hope this helps. I have not rebooted this machine and I had to remove and replace the PCMCIA card before the driver would load properly. I did this before all the network-manager "fun". dmesg was showing this when I first booted the machine. [ 36.698584] :03:00.0 (prism54pci): Cannot read eeprom! [ 36.698656] prism54pci: probe of :03:00.0 failed with error -22 -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90902] Re: prism54: eeprom failed
I'm suffering with this after having upgraded to Feisty on Thursday 2007-04-05. Is there any way I can provide extra, useful information for this bug report. Also is there any kind of workaround in the mean time as the wireless is this PCs only direct internet access. I'm fine to burn some .debs to CD to get a workaround installed until this is fixed. Apart from this issue I'm pretty damn impressed with Feisty. -- prism54: eeprom failed https://bugs.launchpad.net/bugs/90902 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 102870] Re: keytouch diables the right SHIFT key when installed.
** Tags added: keyboard -- keytouch diables the right SHIFT key when installed. https://bugs.launchpad.net/bugs/102870 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 102870] keytouch diables the right SHIFT key when installed.
Public bug reported: Binary package hint: keytouch Steps to reproduce: 1. Install keytouch 2. Attempt to enter a capital letter by using the right shift key 3. Small letter appears 3. Uninstall keytouch 4. Shift key resumes normal operation Setup specifics: Ubuntu version: Fiesty 7.04 Keyboard: Compaq KB-9963 ** Affects: keytouch (Ubuntu) Importance: Undecided Status: Unconfirmed -- keytouch diables the right SHIFT key when installed. https://bugs.launchpad.net/bugs/102870 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 95240] Re: keytouch user level preferences are in administration instead of preferences menu
I can see this as a problem also. Keytouch is used to define per-user mappings of the extra keys on a keyboard. This is something that should be in the System|Preferences menu, not in the System|Administration menu. The Keytouch Editor is however in the correct place, as this related to hardware specifics, like the keyboard model. It needs privileged access to certain files. ** Changed in: keytouch (Ubuntu) Status: Unconfirmed => Confirmed -- keytouch user level preferences are in administration instead of preferences menu https://bugs.launchpad.net/bugs/95240 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 74050] Re: tomboy in kubuntu (kde): the applet not visible in the main panel
I see this similarly in xubuntu, but because xubuntu's System tray dynamically expands to the size of the icon, you see it expand width- ways by 2pixels. You can't even click where Tomboy would be. If it's fixed in Feisty does that mean it will never be fixed in Edgy? -- tomboy in kubuntu (kde): the applet not visible in the main panel https://launchpad.net/bugs/74050 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58545] Re: mp3 plugin causes very bad sound distortion
Projected April release. I think fiesty will be very exciting. Thanks Seb -- mp3 plugin causes very bad sound distortion https://launchpad.net/bugs/58545 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58545] Re: mp3 plugin causes very bad sound distortion
Daniel Holbach, I don't believe there is an upstream bug number, but there is a specific line in the changelog for this package, from fluendo: https://core.fluendo.com/gstreamer/svn/trunk/gst-fluendo-mp3/ChangeLog at 2006-09-06 Towards the bottom of this entry you will see the phrase: "Fix a nasty array index overflow that was resulting in noise in the left channel for some builds only." I suspect that this is the bug, but it has no referenced bug number. This describes pretty well the problem I have suffered. See duplicate of this bug, Bug #74989. -- mp3 plugin causes very bad sound distortion https://launchpad.net/bugs/58545 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74989] Re: [edgy] rhythmbox's mp3 playback generates an extra thumping noise.
I believe you are correct on the fix date. The part in the entry log that seems to fit with what I am experiencing is: "Fix a nasty array index overflow that was resulting in noise in the left channel for some builds only." I forgot to mention that the sound was only occurring in the left speaker / left channel. If I remove the fluendo mp3 package, what will be used in place of it for gstreamer mp3 playback? -- [edgy] rhythmbox's mp3 playback generates an extra thumping noise. https://launchpad.net/bugs/74989 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74989] Re: [edgy] rhythmbox's mp3 playback generates an extra thumping noise.
What does this mean for me as an Edgy user. Do I have to wait for Feisty to get the fix for this, or will the fix be backported? Do you have any tips on finding the original bug in the gstreamer bugzilla. Would it be worth me going IRC on their asses. Just to politely ask where I could find the fix, then maybe apply it myself. Alternatively would there be a way to get a backported version of gstreamer. I don't want to break the package dependencies stuff. If there's a backport I'd take that. -- [edgy] rhythmbox's mp3 playback generates an extra thumping noise. https://launchpad.net/bugs/74989 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75341] Master volume slider has no effect on volume
Public bug reported: Sliding the master volume control on the gnome-panel or in the Volume Control dialogue does nothing. I have an onboard intel audio chipset, it appears as an Intel ICH5: dmesg|grep ICH5 [17179573.336000] ICH5: IDE controller at PCI slot :00:1f.1 [17179573.336000] ICH5: chipset revision 2 [17179573.336000] ICH5: not 100% native mode: will probe irqs later ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Summary changed: - Master volume slider has no effect on volume + Master volume slider has no effect on volume level -- Master volume slider has no effect on volume level https://launchpad.net/bugs/75341 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74989] [edgy] rhythmbox's mp3 playback generates an extra thumping noise.
Public bug reported: Binary package hint: rhythmbox When I playback an mp3 file using rhythmbox, i get this odd, semi rhythmical thumping noise over the top of the music being played. In case you ask, this is not the actual music, or indeed specific mp3 files. It seems that all mp3 files generate this in rhythmbox. It is not limited to rhythmbox, but it does appear to be limited to gstreamer applications. Totem generates the same odd sound. Xmms does not generate this problem. I assigned this bug to rhythmbox because that is where I initially found it, and where other users probably will too. I suspect the bug is actually in the gstreamer0.10-plugins-ugly package. Sadly I could not find a bug describing this problem in the gstreamer bugzilla. I'm not much good at searching big bugzillas though, someone else should look for it. The upside is that whatever the source of the bug, a more recent gstreamer build eliminates the problem :D I have been using Jokosher-0.2 for a bit. The script for installing this on ubuntu: * Grabs a particular cvs version of gstreamer (2006-11-13) * Builds it in a subdir your home directory * Sets up environment variables so that you can run Jokosher with the cvs gstreamer without interfering with the Edgy packaged gstreamer. Clever Aq I just used this to run rhythmbox in the same cvs gstreamer environment, and no more thumping over mp3 playback :D My request is for a clever person to find and backport the fix gstreamer have made in their cvs 2006-11-13 version. Pleeese. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Unconfirmed -- [edgy] rhythmbox's mp3 playback generates an extra thumping noise. https://launchpad.net/bugs/74989 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34199] Re: Evolution Exchange broken
I am suffering the same problem with evolution 2.8 on Edgy, obviously I'm connecting to an exchange server. The problem seems to be intermittent. 1. Boot Ubuntu 2. Start evolution 3. Folders are populated an messages appear in the list for the selected folder, but there is no access to the contents of messages. 4. Error message appears: --- Error while refreshing folder. Lost connection to Evolution Exchange backend process --- I looked at top, and unless I close evolution, the: evolution-exchange-storage --oaf-activate- iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.8 --oaf-ior- fd=34 process is using 99% cpu. Solutions I've attempted are: a) evolution --force-shutdown b) opening and closing evolution about 4 times Solution b) seems to work, but obviously not a good one to have. I will try and get some kind of debug information to add to this bug report. Are there any specifics that would be good. Also, why is there no assignee to this bug? ** Summary changed: - Evolution Exchange broken + Evolution loses connection with Exchange backend process ** Summary changed: - Evolution loses connection with Exchange backend process + Evolution cannot connect to Exchange backend process -- Evolution cannot connect to Exchange backend process https://launchpad.net/bugs/34199 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67712] Additional DNS search domain does not persist after reboot
Public bug reported: Binary package hint: gnome-system-tools I am currently using the release candidate of Ubuntu 6.10 ( Edgy ) I currently have my DNS settings automatically configured via DHCP, but I wish to manually add one extra search domain. The list automatically has one search domain, and I decided to add the second using the "network-admin" tool from gnome-system-tools. 1. System->Administration->Networking 2. Select DNS tab 3. Click "add" adjacent to search domains 4. Fill in field 5. Click close 5. Reboot 6. Open System->Administration->Networking again 7. Go to DNS tab 8. Additional search domain gone I use this extra search domain so I can ssh into a machine on our network, via it's short name. There are about 3-5 machines on this domain. ssh [EMAIL PROTECTED] instead of ssh [EMAIL PROTECTED] ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- Additional DNS search domain does not persist after reboot https://launchpad.net/bugs/67712 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46091] Re: APM error on shutdown
I know it seems odd for someone to chime in like this, but since the reporter of the bug has decided this is fixed, Shouldn't this have been closed about 2 months ago? -- APM error on shutdown https://launchpad.net/bugs/46091 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 9870] Re: Better spam filtering for evolution
** Tags added: evolution -- Better spam filtering for evolution https://launchpad.net/bugs/9870 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25106] Re: evolution-exchange: unable to setup exchange account
** Tags added: evolution -- evolution-exchange: unable to setup exchange account https://launchpad.net/bugs/25106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
