[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Upgrading the BIOS to version A14 solved the problem for me: I still see psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. but no erratic movement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267786] Re: Referencer hangs on Ubuntu 13.10: gtk thread related changes?
** Changed in: referencer Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267786 Title: Referencer hangs on Ubuntu 13.10: gtk thread related changes? To manage notifications about this bug go to: https://bugs.launchpad.net/referencer/+bug/1267786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267786] Re: Referencer hangs on Ubuntu 13.10: gtk thread related changes?
** Changed in: referencer Milestone: None => 1.2.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267786 Title: Referencer hangs on Ubuntu 13.10: gtk thread related changes? To manage notifications about this bug go to: https://bugs.launchpad.net/referencer/+bug/1267786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279066] Re: Referencer crashes on pasting BibTex entries
Do you have any BibTex entry that causes a crash? ** Changed in: referencer (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/279066 Title: Referencer crashes on pasting BibTex entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/279066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315107] Re: Key Values for Documents Need to be constrained to one word
** Changed in: referencer (Ubuntu) Status: New => Fix Committed ** Changed in: referencer (Ubuntu) Assignee: (unassigned) => Mads Chr. Olesen (shiyee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315107 Title: Key Values for Documents Need to be constrained to one word To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/315107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267786] Re: Referencer hangs on Ubuntu 13.10: gtk thread related changes?
** Changed in: referencer Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267786 Title: Referencer hangs on Ubuntu 13.10: gtk thread related changes? To manage notifications about this bug go to: https://bugs.launchpad.net/referencer/+bug/1267786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262820] Re: Hangs when adding a document
*** This bug is a duplicate of bug 1267786 *** https://bugs.launchpad.net/bugs/1267786 ** This bug has been marked a duplicate of bug 1267786 Referencer hangs on Ubuntu 13.10: gtk thread related changes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262820 Title: Hangs when adding a document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/1262820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256567] Re: gtk deadlocks in referencer
*** This bug is a duplicate of bug 1267786 *** https://bugs.launchpad.net/bugs/1267786 ** This bug has been marked a duplicate of bug 1267786 Referencer hangs on Ubuntu 13.10: gtk thread related changes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256567 Title: gtk deadlocks in referencer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/1256567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267786] Re: Referencer hangs on Ubuntu 13.10: gtk thread related changes?
For my own notes: There is a new Gnome3 thumbnailer described at http://askubuntu.com/questions/199110/how-can-i-instruct-nautilus-to- pre-generate-thumbnails/201997#201997 ** Also affects: referencer (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/1267786 Title: Referencer hangs on Ubuntu 13.10: gtk thread related changes? To manage notifications about this bug go to: https://bugs.launchpad.net/referencer/+bug/1267786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267786] [NEW] Referencer hangs on Ubuntu 13.10: gtk thread related changes?
Public bug reported: Pretty much any interaction involving dialogs, even opening the about dialog will cause Referencer to hang. The backtrace looks something like: #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x74144192 in _L_lock_1142 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x74144110 in __GI___pthread_mutex_lock (mutex=0x7773a0) at pthread_mutex_lock.c:104 #3 0x754d13a1 in g_mutex_lock (mutex=) at /build/buildd/glib2.0-2.38.1/./glib/gthread-posix.c:213 #4 0x7649dcba in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #5 0x754913b6 in g_main_dispatch (context=0x7b0b40) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3065 #6 g_main_context_dispatch (context=context@entry=0x7b0b40) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3641 #7 0x75491708 in g_main_context_iterate (context=0x7b0b40, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3712 #8 0x75491b0a in g_main_loop_run (loop=0x178a320) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3906 #9 0x7685d277 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #10 0x77a3d3bd in Gtk::Main::run(Gtk::Window&) () from /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1 #11 0x004a7dfc in RefWindow::run (this=this@entry=0x7fffdc80) at RefWindow.C:108 #12 0x00428568 in main (argc=1, argv=0x7fffdf18) at main.C:96 ** Affects: referencer Importance: Critical Status: Confirmed ** Also affects: referencer (Ubuntu) Importance: Undecided Status: New ** No longer affects: referencer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267786 Title: Referencer hangs on Ubuntu 13.10: gtk thread related changes? To manage notifications about this bug go to: https://bugs.launchpad.net/referencer/+bug/1267786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262820] Re: Hangs when adding a document
** Changed in: referencer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262820 Title: Hangs when adding a document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/1262820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256567] Re: gtk deadlocks in referencer
** Changed in: referencer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256567 Title: gtk deadlocks in referencer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/referencer/+bug/1256567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781653] Re: Mouse is sometimes grabbed, making only keyboard interaction possible
I have not had problems in Ubuntu 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781653 Title: Mouse is sometimes grabbed, making only keyboard interaction possible To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/781653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781653] Re: Mouse is sometimes grabbed, making only keyboard interaction possible
I have now figured out that the "ISACTIVE:true" in .xsession-errors comes from the "Nagios Checker" firefox plugin, when focusing/unfocusing the main area of Firefox. I have disabled that plugin and will try to see if that removes the issue. To clarify: I suspect there is a bug somewhere in Unity, that is just triggered by this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781653 Title: Mouse is sometimes grabbed, making only keyboard interaction possible -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781653] [NEW] Mouse is sometimes grabbed, making only keyboard interaction possible
Public bug reported: Binary package hint: unity Sometimes (unsure of what triggers the bug) the mouse is grabbed by an application (e.g. Firefox). Then the mouse can only be used to interact with that single application, but keyboard interaction still works with that and other apps. When closing the application that has grabbed the mouse, the "next focused" application grabs the mouse, and so on. Running "unity --replace &" seems to ungrab the mouse. When the mouse is grabbed the following is seen in .xsession-errors when clicking the mouse (one or two lines per click): ... ISACTIVE:true ISACTIVE:false ISACTIVE:true ISACTIVE:false ISACTIVE:true ISACTIVE:false ISACTIVE:true ISACTIVE:false ISACTIVE:true ISACTIVE:false ... I'm not 100% certain this is a bug in Unity, but it has only appeared after upgrading to natty. I suspect it might be triggered by some interaction with playing Flash in Firefox, but the problem persists after closing Firefox. I have tried to find the string "ISACTIVE" in different source packages, but no luck. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.12-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,put,move,vpswitch,regex,animation,snap,place,mousepoll,grid,gnomecompat,session,workarounds,expo,imgpng,resize,wall,unitymtgrabhandles,ezoom,staticswitcher,fade,scale,unityshell] Date: Thu May 12 14:18:55 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: LANGUAGE=da_DK:en PATH=(custom, user) LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-05-03 (9 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781653 Title: Mouse is sometimes grabbed, making only keyboard interaction possible -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 781653] Re: Mouse is sometimes grabbed, making only keyboard interaction possible
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/781653 Title: Mouse is sometimes grabbed, making only keyboard interaction possible -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658342] Re: gnome-settings-daemon uses 100% cpu after maverick upgrade
*** This bug is a duplicate of bug 625793 *** https://bugs.launchpad.net/bugs/625793 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/658342/+attachment/1684561/+files/Dependencies.txt ** This bug has been marked a duplicate of bug 625793 Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] * You can subscribe to bug 625793 by following this link: https://bugs.launchpad.net/indicator-application/+bug/625793/+subscribe -- gnome-settings-daemon uses 100% cpu after maverick upgrade https://bugs.launchpad.net/bugs/658342 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 658342] [NEW] gnome-settings-daemon uses 100% cpu after maverick upgrade
*** This bug is a duplicate of bug 625793 *** https://bugs.launchpad.net/bugs/625793 Public bug reported: Binary package hint: gnome-settings-daemon After upgrade to maverick gnome-settings-daemon uses 100% cpu. Seems to be related to having multiple keyboard layouts (Danish QWERTY and Norway DVORAK in my case, with caps-lock as toggle). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-settings-daemon 2.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 11 15:15:26 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: PATH=(custom, user) LANG=da_DK.utf8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- gnome-settings-daemon uses 100% cpu after maverick upgrade https://bugs.launchpad.net/bugs/658342 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 613335] Re: multiadm triggers assert in gnome-keyring code
Sorry to people who got subscribed: I wanted to document in MultiADM that this is related to https://bugs.launchpad.net/ubuntu/+source /libgnome-keyring/+bug/554077 but obviously failed... -- multiadm triggers assert in gnome-keyring code https://bugs.launchpad.net/bugs/613335 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 613335] Re: multiadm triggers assert in gnome-keyring code
Just got a crash: ** (multiadm:18720): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached ** ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached Aborted ** Also affects: libgnome-keyring (Ubuntu) Importance: Undecided Status: New ** Changed in: libgnome-keyring (Ubuntu) Status: New => Invalid -- multiadm triggers assert in gnome-keyring code https://bugs.launchpad.net/bugs/613335 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 516605] Re: Limitation on the number of virtual desktops
Well, compiz actually tries to prevent this configuration from occuring. To get a faulty configuration one needs to configure compiz and then hot-plug the monitor. The bug is about the limit existing. You are very welcome to close it as unsupported or similar; I fully realize that fixing it is a very large task - but at least now people will be aware that the limitation exists and why. -- Limitation on the number of virtual desktops https://bugs.launchpad.net/bugs/516605 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 516605] Re: Limitation on the number of virtual desktops
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/38709873/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/38709874/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38709875/Dependencies.txt ** Attachment added: "GconfCompiz.txt" http://launchpadlibrarian.net/38709876/GconfCompiz.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/38709877/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/38709878/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/38709879/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/38709880/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/38709881/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/38709882/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/38709883/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/38709884/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/38709885/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/38709886/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/38709887/Xrandr.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38709888/XsessionErrors.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/38709889/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/38709890/monitors.xml.txt -- Limitation on the number of virtual desktops https://bugs.launchpad.net/bugs/516605 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 516605] [NEW] Limitation on the number of virtual desktops
Public bug reported: Binary package hint: compiz I have a nVidia twin-view setup with 2 screens, 1900x1200 and 1680x1050. I would like to use 12 horizontal virtual desktops. This is currently not possible. I have dug a bit into the code (compiz and Xorg), and it seems the underlying issue is that the X-server does not support window positions outside [-32768;32768], because it uses the "short" variable type. The setup I would like would require a desktop size of 43200x1200 pixels, and as such fails in funny ways (windows suddenly changing positions, etc.). ProblemType: Bug Architecture: i386 CompizPlugins: [core,move,resize,place,decoration,animation,ccp,put,gnomecompat,regex,extrawm,png,workarounds,text,session,neg,ring,svg,video,annotate,dbus,imgjpeg,resizeinfo,snap,cube,switcher,rotate,scale,scaleaddon,scalefilter] Date: Wed Feb 3 16:35:13 2010 DistroRelease: Ubuntu 9.10 MachineType: LENOVO. 27469BG NonfreeKernelModules: nvidia Package: compiz 1:0.8.4-0ubuntu2 PackageArchitecture: all PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G98 [GeForce 9300M GS] [10de:06e9] (rev a1) ProcCmdLine: root=UUID=33eaae46-59a3-41fc-b364-be069d0ed531 ro quiet splash ProcEnviron: LANGUAGE=da_DK.UTF-8 PATH=(custom, user) LANG=da_DK.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: compiz Uname: Linux 2.6.31-17-generic i686 dmi.bios.date: 09/05/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET46WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 27469BG dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET46WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET46WW dmi.modalias: dmi:bvnLENOVO:bvr6AET46WW:bd09/05/2008:svnLENOVO.:pn27469BG:pvrThinkPadSL500:rvnLENOVO:rn27469BG:rvrLENOVO6AET46WW:cvnLENOVO:ct10:cvrLENOVO6AET46WW: dmi.product.name: 27469BG dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO. system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-17-generic ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Limitation on the number of virtual desktops https://bugs.launchpad.net/bugs/516605 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 411935] Re: Empathy preserves configuration information upon apt-get purge
I'm unable to find an authoritative source for this, but purge is not meant to delete files in users' home dirs. The reference to configuration files is files stored under /etc, which are removed when you use purge. See http://ubuntuforums.org/archive/index.php/t-870311.html -- Empathy preserves configuration information upon apt-get purge https://bugs.launchpad.net/bugs/411935 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 318265] Re: Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while these codes can be up to 8 digits long
** Bug watch added: GNOME Bug Tracker #582435 http://bugzilla.gnome.org/show_bug.cgi?id=582435 ** Also affects: network-manager-applet via http://bugzilla.gnome.org/show_bug.cgi?id=582435 Importance: Unknown Status: Unknown -- Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while these codes can be up to 8 digits long https://bugs.launchpad.net/bugs/318265 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 318265] Re: Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while these codes can be up to 8 digits long
As a work-around you can use the SIM card in a mobile phone enter the PUK-code there, and set a new PIN-code, then use the SIM card without problems. -- Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while these codes can be up to 8 digits long https://bugs.launchpad.net/bugs/318265 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 371503] Re: nm-applet puk entry allows too few digits
*** This bug is a duplicate of bug 318265 *** https://bugs.launchpad.net/bugs/318265 ** This bug has been marked a duplicate of bug 318265 Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while these codes can be up to 8 digits long -- nm-applet puk entry allows too few digits https://bugs.launchpad.net/bugs/371503 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 109312] Re: Tray icon plugin works erratically
The packages from Saïvann Carignan also solves the problem for me! -- Tray icon plugin works erratically https://bugs.launchpad.net/bugs/109312 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 307824] Re: imap sync performance regression in intrepid
Initial observations: First start of evolution after installing ppa packages failed, as in the sync was taking forever (this also happened before, so I'm not sure its a regression), so I killed all evolution processes Second start, sync seems faster than usual. I will continue testing in the next few days. -- imap sync performance regression in intrepid https://bugs.launchpad.net/bugs/307824 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 260059] Re: lilo needs to warn if initrd is too large
I fail to understand your argumentation. If the supposed fix ("large-
memory") is in Lilo, how can this be a kernel problem?
"add a check to lilo that will tell the user that their initrd.img is
over a certain size and that they might want to add the "large-memory"
option to lilo.conf. This *definitely* needs to go into an SRU, IMNSHO."
There _is already_ such a check in Lilo. It just seems to be a heuristic
that is slightly off. Instead of changing properties of this bug, could
you please test the patch i attached instead?
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
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 260059] Re: lilo needs to warn if initrd is too large
Oh bugger. I tried emailing John Coffman, the author of LILO, to get his
take on this (the previous comment), but the mail bounced.
It pretty much sums up my _suspicions_:
LILO has a heuristic to determine when the "large-memory" option is needed, but
it underestimates, leading to this edge case. We are very close to the
estimated compression ratio that LILO has.
My proposed solution:
Make LILO be more pessimistic about its estimate. This (untested) patch should
do it:
--- boot.c.orig 2008-08-30 12:44:51.0 +0200
+++ boot.c 2008-08-30 14:36:51.0 +0200
@@ -84,7 +84,7 @@
die("Can't load kernel at mis-aligned address 0x%08lx\n",hdr.start);
descr->flags |= FLAG_LOADHI;/* load kernel high */
hi_sectors = sectors - setup; /* number of sectors loaded high */
- hi_sectors *= 3;/* account for decompression */
+ hi_sectors *= 4;/* account for decompression */
if (hi_sectors < HIGH_4M) hi_sectors = HIGH_4M;
}
geo_close(&geo);
It basically makes LILO assume that the initrd has a compression ratio
of 4, therefore much sooner warning the user that "large-memory" is
required (and actually behaving as if "large-memory" was specified).
Soren: Could you test that this patch correctly gives a warning if you
run LILO (without the large-memory option)?
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
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 260059] LILO question about too big
Hi John! I hope you can answer a question I have about the LILO bootloader (version 22.8), raised by a bug-report in Ubuntu ( https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/260059 ). I have CC'ed the bug report for reference. In boot.c there is the following two lines, for calculating the number of high sectors needed for loading the initrd (IIUC): hi_sectors = sectors - setup; /* number of sectors loaded high */ hi_sectors *= 3;/* account for decompression */ My question is about the "account for decompression" part. How precise is the number 3? Is it heuristic, or is it completely precise? The reporter in the bug has an initrd image of size 24574976 (gunzipped) and 8257993 (gzipped). The ratio of compression, 2.976, is therefore very close to 3. My second question, if my speculations are correct, is: Would it hurt to raise the number to e.g. 4? My understanding is that this would just make lilo behave as if "large-memory" was specified, in many more cases, potentially avoiding this gray area. Thank you very much for taking the time to respond :-) -- Mads Chr. Olesen <[EMAIL PROTECTED]> shiyee.dk -- lilo needs to warn if initrd is too large https://bugs.launchpad.net/bugs/260059 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 260059] Re: lilo needs to warn if initrd is too large
Could you provide the size of the initrd image, gunzipped? -- lilo needs to warn if initrd is too large https://bugs.launchpad.net/bugs/260059 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 260059] Re: lilo needs to warn if initrd is too large
Hmm, the issue doesn't seem as straightforward after all. In lilo there is already a check for a too large initrd (boot.c, search for FLAG_TOOBIG). I wonder why it wasn't triggered. Could you attach your lilo.conf? And, if possible, the output of running lilo with a couple of "-v" flags (and without the "large-memory" option)? -- lilo needs to warn if initrd is too large https://bugs.launchpad.net/bugs/260059 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 251822] Re: Cannot authenticate to some webdav shares
I can confirm that the package from -proposed fixes this problem. -- Cannot authenticate to some webdav shares https://bugs.launchpad.net/bugs/251822 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 251822] Re: Cannot authenticate to some webdav shares
If access to an affected server is required for testing, please ping me and I can probably set one up. -- Cannot authenticate to some webdav shares https://bugs.launchpad.net/bugs/251822 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 251822] Re: Cannot authenticate to some webdav shares
This issue has now been resolved in libsoup trunk. ** Tags added: patch ** Attachment added: "This is the patch applied to libsoup trunk." http://launchpadlibrarian.net/16345372/soup-auth-digest-default-to-md5-patch-r1113-r1114-from-svn.patch -- Cannot authenticate to some webdav shares https://bugs.launchpad.net/bugs/251822 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 251822] [NEW] Cannot authenticate to some webdav shares
Public bug reported: Binary package hint: gvfs When trying to mount some webdav shares (which worked fine under gnomevfs), gvfs is unable to authenticate. This is due to the server not returning an algorithm to use, and libsoup (which gvfs uses for webdav) interprets this wrongly. The RFC is clear that this must be interpreted as MD5 should be used. Attached (one-liner) patch fixes this issue for me. Bug #223521 is possibly a dupe of this one. ** Affects: gvfs Importance: Unknown Status: Unknown ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Affects: libsoup2.4 (Ubuntu) Importance: Undecided Status: New -- Cannot authenticate to some webdav shares https://bugs.launchpad.net/bugs/251822 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 251822] Re: Cannot authenticate to some webdav shares
** Attachment added: "Make libsoup default to MD5 as digest algorithm (as stated by the RFC)" http://launchpadlibrarian.net/16301544/libsoup-digest-algorithm-default.patch ** Bug watch added: GNOME Bug Tracker #544681 http://bugzilla.gnome.org/show_bug.cgi?id=544681 ** Also affects: gvfs via http://bugzilla.gnome.org/show_bug.cgi?id=544681 Importance: Unknown Status: Unknown ** Also affects: libsoup2.4 (Ubuntu) Importance: Undecided Status: New -- Cannot authenticate to some webdav shares https://bugs.launchpad.net/bugs/251822 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 220516] Re: gvfs dav backend does not handle redirects [PATCH]
Hmm, sorry for the noise - my bug seems to be unrelated, but related to specifying a username in the URI and there after being redirected. ** Changed in: gvfs (Ubuntu) Status: New => Invalid -- gvfs dav backend does not handle redirects [PATCH] https://bugs.launchpad.net/bugs/220516 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 220516] Re: gvfs dav backend does not handle redirects [PATCH]
** Attachment added: "patch from upstream at http://svn.gnome.org/viewvc/gvfs/branches/gnome-2-22/daemon/gvfsbackenddav.c?view=patch&r1=1725&r2=1741&pathrev=1741"; http://launchpadlibrarian.net/13785307/94_from_svn_fix_dav_redirect_issue.patch ** Bug watch added: GNOME Bug Tracker #528218 http://bugzilla.gnome.org/show_bug.cgi?id=528218 ** Also affects: gvfs via http://bugzilla.gnome.org/show_bug.cgi?id=528218 Importance: Unknown Status: Unknown -- gvfs dav backend does not handle redirects [PATCH] https://bugs.launchpad.net/bugs/220516 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 220516] Re: gvfs dav backend does not handle redirects [PATCH]
** Attachment added: "screenshot of problem" http://launchpadlibrarian.net/13784525/Sk%C3%A6rmbillede-nautilus.png -- gvfs dav backend does not handle redirects [PATCH] https://bugs.launchpad.net/bugs/220516 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 220516] [NEW] gvfs dav backend does not handle redirects [PATCH]
Public bug reported: Binary package hint: gvfs-backends The gvfs dav backend does not handle redirects. This is fixed upstream, and has a very small patch. Would be really nice to have this in, before the release. ** Affects: gvfs Importance: Unknown Status: Unknown ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- gvfs dav backend does not handle redirects [PATCH] https://bugs.launchpad.net/bugs/220516 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 190904] Re: Does not support routed virtual network
This patch is now in libvirt trunk. -- Does not support routed virtual network https://bugs.launchpad.net/bugs/190904 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 190904] Re: Does not support routed virtual network
** Attachment added: "Updated patch, see discussion on libvirt mail list" http://launchpadlibrarian.net/12554211/routed-virtual-net.0.4.0.patch -- Does not support routed virtual network https://bugs.launchpad.net/bugs/190904 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 190904] Re: Does not support routed virtual network
** Attachment added: "Updated patch" http://launchpadlibrarian.net/12519061/routed-virtual-net.patch -- Does not support routed virtual network https://bugs.launchpad.net/bugs/190904 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 190904] Re: Does not supported routed virtual network
Please see the attached patch, which allows the use of a stanza (dev is optional), much like the stanza. Comments welcome :-) ** Attachment added: "Allow use of " http://launchpadlibrarian.net/12356895/routed-virtual-net.patch -- Does not supported routed virtual network https://bugs.launchpad.net/bugs/190904 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 191636] Re: [hardy] dnsmasq fails to start the dhcp server
AHA! Creating the directory /var/lib/libvirt/ seems to be the solution -- [hardy] dnsmasq fails to start the dhcp server https://bugs.launchpad.net/bugs/191636 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 191636] [NEW] [hardy] dnsmasq fails to start the dhcp server
Public bug reported: With libvirt0 version 0.4.0-2ubuntu4, i get the following upon /etc/init.d/libvirt-bin start: Feb 13 18:23:04 lukas kernel: [79696.733582] vnet0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. Feb 13 18:23:04 lukas kernel: [79696.731640] vnet0: starting userspace STP failed, starting kernel STP Feb 13 18:23:04 lukas dnsmasq[23835]: cannot open or create lease file (null): �F^Y�% Feb 13 18:23:04 lukas dnsmasq[23835]: FAILED to start up Feb 13 18:23:14 lukas kernel: [79706.938876] vnet0: no IPv6 routers present ... and the dhcp server on the "default" virtual network does not respond. Any hints on debugging appreciated :-) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- [hardy] dnsmasq fails to start the dhcp server https://bugs.launchpad.net/bugs/191636 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 191385] [NEW] [hardy] libvirt-bin should depend on iptables
Public bug reported: If iptables is not installed, /etc/init.d/libvirtd start gives this error: libvir: QEMU error : failed to add iptables rule to allow DHCP requests from 'virbr0' : Invalid argument Failed to autostart network 'default': failed to add iptables rule to allow DHCP requests from 'virbr0' : Invalid argument ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- [hardy] libvirt-bin should depend on iptables https://bugs.launchpad.net/bugs/191385 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 182918] Re: E: Type '“deb' is not k nown on line 44 in source list /etc/apt/sources.lis
Have you edited your /etc/apt/sources.list file manually, or only used tools? The error comes from a line that has an erroneus " at the start, e.g. "deb ... instead of deb ... -- E: Type '“deb' is not known on line 44 in source list /etc/apt/sources.lis https://bugs.launchpad.net/bugs/182918 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 139445] Re: Unable to deactivate shortcut key for some general actions
For the moment I'm using the attached script after each re-login, as a workaround. ** Attachment added: "Workaround script" http://launchpadlibrarian.net/9297234/fix-compiz-keybindings.sh -- Unable to deactivate shortcut key for some general actions https://bugs.launchpad.net/bugs/139445 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 139445] Unable to deactivate shortcut key for some general actions
Public bug reported: Binary package hint: compizconfig-settings-manager I'm unable to disable the shortcut keys for the actions found under "General Options" -> "Actions" -> "General", such as: * Close Window (Alt+f4) * Maximize (Alt+f10) * Minimize * Slow animations * ... I have tried both editing the cell and pressing Backspace, and double-clicking the row to get a dialog. After doing any of these, the treeview reloads, and the shortcut is still the same. I have found a work-around, by using gconf-editor, and editing the keys under /apps/compiz/general/allscreens/options/ . This works for all actions, but after a reboot/relogin(?) most keys are reset to their default shortcut (applies to close window, maximize, minimize, etc., but not to e.g. Slow animations). It seems to not work for the keys that are highlighted with a blue color in ccsm. Maybe this resetting after reboot is a bug in compiz as well? ** Affects: compizconfig-settings-manager (Ubuntu) Importance: Undecided Status: New -- Unable to deactivate shortcut key for some general actions https://bugs.launchpad.net/bugs/139445 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 138917] Re: network-manager 0.6.5-0ubuntu11 broken
Reading the patches that went into 0.6.5-0ubuntu11, its probably 41t_nm_device_wireless_index_ctrl_sockets_by_run_count.patch thats causing the problems, more specifically the hunk: @@ -2808,27 +2822,30 @@ wpa_driver = "madwifi"; else if (!strcmp (kernel_driver, "hostap_pci") || !strcmp (kernel_driver, "hostap_cs") || !strcmp (kernel_driver, "hostap_plx")) wpa_driver = "hostap"; else wpa_driver = "wext"; /* wpa_cli -g/var/run/wpa_supplicant-global interface_add eth1 "" wext /var/run/wpa_supplicant */ if (!nm_utils_supplicant_request_with_check (ctrl, "OK", __func__, NULL, - "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET "\t", iface, wpa_driver)) + "INTERFACE_ADD %s\t\t%s\t" WPA_SUPPLICANT_CONTROL_SOCKET "%d\t", iface, wpa_driver, self->priv->run_count)) Which seems to add an integer to the end of the command, making the path invalid (/var/run/wpa_supplicant exists on my system, /var/run/wpa_supplicant2 does not...) -- network-manager 0.6.5-0ubuntu11 broken https://bugs.launchpad.net/bugs/138917 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 138917] Re: network-manager 0.6.5-0ubuntu11 broken
** Attachment added: "Working nm" http://launchpadlibrarian.net/9233999/working-nm.log -- network-manager 0.6.5-0ubuntu11 broken https://bugs.launchpad.net/bugs/138917 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 138917] Re: network-manager 0.6.5-0ubuntu11 broken
** Attachment added: "Segfaulting nm" http://launchpadlibrarian.net/9233998/broken-nm.log -- network-manager 0.6.5-0ubuntu11 broken https://bugs.launchpad.net/bugs/138917 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 138917] Re: network-manager 0.6.5-0ubuntu11 broken
The difference is in the lines: Sep 11 13:55:46 localhost NetworkManager: SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant2^I' Sep 11 13:55:46 localhost NetworkManager: SUP: response was 'FAIL' (broken) vs. Sep 11 17:29:56 localhost NetworkManager: SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant^I' Sep 11 17:29:56 localhost NetworkManager: SUP: response was 'OK' (working) -- network-manager 0.6.5-0ubuntu11 broken https://bugs.launchpad.net/bugs/138917 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 138917] network-manager 0.6.5-0ubuntu11 broken
Public bug reported: Binary package hint: network-manager The recent upgrade of network-manager to 0.6.5-0ubuntu11 has broken network-manager support for me, NetworkManager seems to segfault. Syslog attached. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- network-manager 0.6.5-0ubuntu11 broken https://bugs.launchpad.net/bugs/138917 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 138734] Re: [Gutsy] Cannot burn, n-c-b sends wrong device parameter to cdrecord
It seems I had a locally installed version of n-c-b. The one from the Ubuntu package works flawlessly. This bug can be closed, very sorry for the disturbance.. ** Changed in: nautilus-cd-burner (Ubuntu) Status: Incomplete => Invalid -- [Gutsy] Cannot burn, n-c-b sends wrong device parameter to cdrecord https://bugs.launchpad.net/bugs/138734 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 138734] [Gutsy] Cannot burn, n-c-b sends wrong device parameter to cdrecord
Public bug reported: Binary package hint: nautilus-cd-burner I'm unable to burn an ISO-file to a disk, using nautilus-cd-burner. The symptoms is that n-c-b locks up, and consumes more and more memory. The problem is that n-c-b calls cdrecord as: cdrecord fs=16m dev=0,1,0 -eject -dao driveropts=burnfree -v -data -nopad ubuntu-7.04-desktop-i386.iso When run from the command line, it produces this output, ad libitum: TOC Type: 1 = CD-ROM scsidev: '0,1,0' scsibus: 0 target: 1 lun: 0 WARNING: the deprecated pseudo SCSI syntax found as device specification. Support for that may cease in the future versions of wodim. For now, the device will be mapped to a block device file where possible. Run "wodim --devices" for details. Unable to open this SCSI ID. Trying to map to old ATA syntax.This workaround will disappear in the near future. Fix your configuration.Unable to open this SCSI ID. Trying to map to old ATA syntax.This workaround will disappear in the near future. Fix your configuration.Unable to open this SCSI ID. Trying to map to old ATA syntax.This workaround will disappear in the near future. Fix your configuration.Unable to open this SCSI ID. Trying to map to old ATA syntax.This workaround will disappear in the near future. Fix your configuration.Unable to open this SCSI ID. Trying to map to old ATA syntax.This workaround will disappear in the near future. Fix your configuration.Unable to open this SCSI ID. Trying to map to When running cdrecord as: cdrecord fs=16m dev=/dev/cdrom -eject -dao driveropts=burnfree -v -data -nopad ubuntu-7.04-desktop-i386.iso It works fine. n-c-b should probably be updated to use the new syntax. ** Affects: nautilus-cd-burner (Ubuntu) Importance: Undecided Status: New -- [Gutsy] Cannot burn, n-c-b sends wrong device parameter to cdrecord https://bugs.launchpad.net/bugs/138734 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 130334] Re: [Gutsy] xvncviewer support broken by new version 4.1.1
service-discovery-applet is an Avahi service browser for the gnome panel. You add it to your gnome panel, click the icon choose "VNC Remote Access" (given that you have a vnc service advertised at your LAN), and click a service to connect to it. -- [Gutsy] xvncviewer support broken by new version 4.1.1 https://bugs.launchpad.net/bugs/130334 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 130606] Ctrl+N hotkey bound to both "New Folder" and "Next Unread Item"
Public bug reported: Binary package hint: liferea The Ctrl+N hotkey is bound to both "New Folder" and "Next Unread Item". ** Affects: liferea (Ubuntu) Importance: Undecided Status: New -- Ctrl+N hotkey bound to both "New Folder" and "Next Unread Item" https://bugs.launchpad.net/bugs/130606 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 130334] Re: [Gutsy] xvncviewer support broken by new version 4.1.1
** Attachment added: "xvnc4viewer-sda.patch" http://launchpadlibrarian.net/8693856/xvnc4viewer-sda.patch -- [Gutsy] xvncviewer support broken by new version 4.1.1 https://bugs.launchpad.net/bugs/130334 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 130334] [Gutsy] xvncviewer support broken by new version 4.1.1
Public bug reported: Binary package hint: service-discovery-applet The current version of xvnc4viewer in Gutsy does not support the "-xrm *passwordDialog:true" option which the plugin passes to it. Just removing the parameters works, as the new default is opening a X password dialog, see attached patch. Possibly some version detection should be done, to assert whether to pass the parameter. ** Affects: service-discovery-applet (Ubuntu) Importance: Undecided Status: New -- [Gutsy] xvncviewer support broken by new version 4.1.1 https://bugs.launchpad.net/bugs/130334 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 85031] Re: [apport] apt-listchanges crashed with IOError in mail_changes()
Still seeing this in gutsy with apt-listchanges version 2.74ubuntu2 Probably apt-listchanges should just depend on "mail-transport-agent" ? -- [apport] apt-listchanges crashed with IOError in mail_changes() https://bugs.launchpad.net/bugs/85031 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 122863] Re: package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes
Attached is the output of grep tex /var/log/dpkg.log.1 Hope this helps :-) ** Attachment added: "grep tex /var/log/dpkg.log.1" http://launchpadlibrarian.net/8289449/tex-dpkg.log -- package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes https://bugs.launchpad.net/bugs/122863 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 122863] Re: package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes
man, 02 07 2007 kl. 12:02 +, skrev Ming Hua: > > > I cannot find any information in /var/log/aptitude* about version > > > numbers. > > > > Did you use aptitude for upgrading? > > Considering that Ubuntu's default/standard package manager is not > aptitude (gnome-app-install or update-manager?), most likely the > reporter is not using aptitude. > Actually I am, but I think I used apt-get for the dist-upgrade :-( -- Mads Chr. Olesen <[EMAIL PROTECTED]> shiyee.dk -- package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes https://bugs.launchpad.net/bugs/122863 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 122863] Re: package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes
søn, 01 07 2007 kl. 20:54 +, skrev Frank Küster: > One morething which is strange is that the original reporter said that > there were *two* fork bombs after each other, and that the first was > "related" to mktexlsr, but still there were *etex* processes running. > > This I cannot explain anyhow, I assume that the bug reporter mixed > something up, please ask him to clarify that (I'm in a hurry, leaving > for holiday, and have no time to look up the launchpad bug and > reporter's e-mail address, sorry). To clarify (according to memory): Output: Running mktexlsr. This may take some time... Spawning of about 900 etex processes (which seem to stay) Output: done. Building format(s) --all . This may take some time... Spawning of _many_ more processes I did not have texlive installed in feisty, only tetex (and xmltex and jadetex). > > I'm not sure what texlive and tex-common versions feisty had, but > > if I assume it resembles sarge (tex-common 1.0*), *then* I do not > have > > an explanation. > > We should really try to get exact version numbers (aptitude log?) I cannot find any information in /var/log/aptitude* about version numbers. -- Mads Chr. Olesen <[EMAIL PROTECTED]> shiyee.dk -- package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes https://bugs.launchpad.net/bugs/122863 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 122863] Re: package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes
removing xmltex and jadetex seems to solve the problem :-) Thanks! - I guess this bug can be closed -- package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes https://bugs.launchpad.net/bugs/122863 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 122863] package texlive-base-bin 2007-11 failed to install/upgrade: post-installation script spawns thousands of processes
Public bug reported:
Upgrading from feisty to gutsy today (28-06-07).
Log (some danish locale):
Sætter texlive-base-bin (2007-11) op...
Running mktexlsr. This may take some time... done.
Building format(s) --all . This may take some time... dpkg: fejl under
behandling af texlive-base-bin (--configure):
underproces post-installation script dræbt af signal (Interrupt)
When the post-inst script of texlive-base-bin runs, it spawns around 900 "etex"
processes in the first step ("Running mktexlsr...").
When running the second step ("Building format(s)...") it gets up to around
2500 "etex" processes, until the system reached a load average of 731 and i
killed the post-inst script.
Please tell me what information i can provide to help solve this bug. I
suspect it might be some upgrading from tetex thing?
ProblemType: Package
Architecture: i386
Date: Thu Jun 28 17:33:32 2007
ErrorMessage: underproces post-installation script dræbt af signal (Interrupt)
Package: texlive-base-bin 2007-11
SourcePackage: texlive-bin
** Affects: texlive-bin (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-package
--
package texlive-base-bin 2007-11 failed to install/upgrade: post-installation
script spawns thousands of processes
https://bugs.launchpad.net/bugs/122863
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 23369] Re: firefox(-gnome-support) should get proxy from gconf
Yes, I also tested whether it works, admittedly only by setting the proxy and seeing that i'm still able to connect which should not be possible if it used the non-accessible proxy server. -- firefox(-gnome-support) should get proxy from gconf https://bugs.launchpad.net/bugs/23369 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 23369] Re: firefox(-gnome-support) should get proxy from gconf
In my testing, it does NOT work. When setting config.use_system_prefs the settings you listed become "locked", and the firefox network dialog becomes grayed out. The settings from gconf is however not used, in about:config e.g. type is 0 (no proxy) and the various host fields are blank. I have tried to get debug info using export NSPR_LOG_FILE=/tmp/firefox-debug.log export NSPR_LOG_MODULES="all:5" firefox but the only mention of system-pref is: -1221551264[805c548]: Loaded library /usr/lib/firefox/components/libsystem-pref.so (load lib) Currently compiling firefox with DEB_BUILD_OPTIONS=debug to see if that makes any difference to the debug output. -- firefox(-gnome-support) should get proxy from gconf https://bugs.launchpad.net/bugs/23369 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 104043] Re: Dia: automatic file name extension for export
** Bug watch added: GNOME Bug Tracker #439935 http://bugzilla.gnome.org/show_bug.cgi?id=439935 ** Also affects: dia (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=439935 Importance: Unknown Status: Unknown -- Dia: automatic file name extension for export https://bugs.launchpad.net/bugs/104043 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 95055] Re: keyboard shortcut for drawing an ellipse is unusable
*** This bug is a duplicate of bug 69049 *** https://bugs.launchpad.net/bugs/69049 ** This bug has been marked a duplicate of bug 69049 Several tool hotkeys do not work -- keyboard shortcut for drawing an ellipse is unusable https://bugs.launchpad.net/bugs/95055 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 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal
This is possibly also the cause for bug #77106 -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 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 115801] max inotify user watches in the kernel should be increased for beagle indexing to be optimal
Public bug reported: Binary package hint: beagle As described by Joe Shaw in http://thomas.apestaart.org/log/?p=482#comment-2699 beagle will fall- back to continously indexing a user's files, if it fails to inotfy watch all directories for changes. The described solution is increasing /proc/sys/fs/inotify/max_user_watches to some higher value. Increasing this number should not have any adverse effects, unless the watches are actually used. On my system I increased the number to 32768, as i have almost that many sub-directories in my homedir: find . -type d | wc -l I increased the value by adding "fs.inotify.max_user_watches = 32768" to /etc/sysctl.conf, not sure if it can be done in some way only if beagle has been installed? ** Affects: beagle (Ubuntu) Importance: Undecided Status: Unconfirmed -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 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 112601] Re: Cannot connect to Jabber server
I just noticed that you seem to be registering with the server? ** (telepathy-gabble:11973): DEBUG: parse_parameters: accepted value 1 for param register Try to just log in normally. -- Cannot connect to Jabber server https://bugs.launchpad.net/bugs/112601 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 112601] Re: Cannot connect to Jabber server
The problem is the lines: ** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The certificate can not be trusted. ** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The certificate has expired. ** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The server doesn't provide a certificate. ** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The server hostname doesn't match the one in the certificate. The server's ssl certificate is not accepted. There is a parameter for Gabble called "ignore-ssl-errors" which will solve your problem, but I dont't think it can be set from within Gossip's UI. Alternatively, you could connect without SSL? -- Cannot connect to Jabber server https://bugs.launchpad.net/bugs/112601 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 112601] Re: Cannot connect to Jabber server
could you try to run gabble in debug mode? 1. Start "GABBLE_DEBUG=all telepathy-gabble" in a terminal 2. Start gossip as usual 3. paste the output from the terminal in this bug report -- Cannot connect to Jabber server https://bugs.launchpad.net/bugs/112601 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 94385] Re: Can't connect to Jabber accounts
Login ID: [EMAIL PROTECTED] Server: murrayc.com If you use SSL, port should be 5223, 5222 otherwise. -- Can't connect to Jabber accounts https://launchpad.net/bugs/94385 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78098] Re: http_proxy defined incorrectly
Alex: The interaction with gnome-session is that gnome-session sets the env.
var. according to gconf, and this setting is then inherited by all other apps
in the session, see pstree:
│ └─gnome-session─┬─Xgl
│ ├─beagle-search───2*[{beagle-search}]
│ ├─evolution-alarm───2*[{evolution-alarm}]
│ ├─gnome-cups-icon
│ ├─gnome-panel
│ ├─nautilus
│ ├─nm-applet
│ ├─2*[ssh-agent]
│ ├─update-notifier
│ └─{gnome-session}
For example gnome-terminal sees the env. var. as overruling the gconf
values, and thus stops obeying changes to the gconf settings for the
duration of the session.
Gnome-session does _NOT_ set the env. var. if "use_http_proxy" is not
set. The problem is that gnome-session is only able to check _once_ at
startup, and this setting is then inherited and overruling.
--
http_proxy defined incorrectly
https://launchpad.net/bugs/78098
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78098] Re: http_proxy defined incorrectly
Attached patch is preliminary fix (disables proxy env. var. setting). Also filed in gnome bugzilla, bug #398140. ** Attachment added: "Disable proxy setting in gnome-session" http://librarian.launchpad.net/5786647/no-setting-proxy-env.patch -- http_proxy defined incorrectly https://launchpad.net/bugs/78098 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78098] Re: http_proxy defined incorrectly
Investigating further, I think the bug is in gnome-session which have had some changes to set the http_proxy environment variable according to the gconf settings - this however interferes with gnome-terminal's idea that if the environment variable is set it should obey this. The root of the problem is that gnome-session assumes the proxy settings to be constant during the session (because the environment is inherited by child processes, and cannot be changed), which is not true. Maybe these changes should be backed out of gnome-session, as gnome-terminal already handles it? Also see gnome bug #84315 -- http_proxy defined incorrectly https://launchpad.net/bugs/78098 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78098] Re: http_proxy defined incorrectly
I'm seeing an issue, that if the proxy is set ("manual proxy configuration") on
bootup, changes to the proxy-settings are ignored.
If the proxy is set to "Direct internet connection" on bootup spawned terminals
obey the settings set at the time they are spawned (as expected).
Looking at the code for gnome-terminal I suspect that http_proxy is set as an
environment variable, in which case it will always use that.
This is reinforced, by booting with proxy on, starting a terminal, running
"unset http_proxy" and then spawning a new terminal with "gnome-terminal" -
this new terminal obeys the proxy settings from the control center.
Is this the same issue you are seeing?
--
http_proxy defined incorrectly
https://launchpad.net/bugs/78098
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76872] Re: boot fails: does not detect hda any more (port conflict?)
I can also confirm bug and that the fix works. -- boot fails: does not detect hda any more (port conflict?) https://launchpad.net/bugs/76872 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
