[Bug 1024704] [NEW] I window poped up informing me of a crash
Public bug reported: The bloody thing crashed and asked me to report it. Now I'm playing 20 questions. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.16 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 CasperVersion: 1.315 Date: Sat Jul 14 16:50:32 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ubiquity-2.10.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024704 Title: I window poped up informing me of a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1024704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024704] Re: I window poped up informing me of a crash
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024704 Title: I window poped up informing me of a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1024704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 829980] Re: upstart-udev-bridge eats 100% cpu calling dbus_message_iter_append_basic()
Patch works well on my MacBook 5,1 Thanks Tim Allen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/829980 Title: upstart-udev-bridge eats 100% cpu calling dbus_message_iter_append_basic() To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/829980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 674138] Re: Global appmenu breaks sloppy focus
I would like to propose a different solution: Observation: People going for the global menu-bar generally take advantage of Fitt's Law and shoot the pointer straight upward, rather than meandering about. Observation: People using focus-follows-mouse are generally in one of two states, either interacting with a single window or moving the mouse to focus a new window - they never interact with windows as they move the pointer past them. Idea: Use 'is the mouse moving' as a heuristic to determine whether to focus the window under the pointer. For example, the window manager could store the pointer coördinates when it receives a mouse-move event, then have a periodic timer that fires (say, once per frame) and compares the then-current pointer position with the last stored position. Because people rarely interact with windows while they're moving the pointer past them, and because the timer (once per frame, or ~19ms) is so much shorter than human perception (100-250ms), it shouldn't cause anyone grief - the only noticable change should be that reaching for the menu bar Just Works. If the once-per-frame counter doesn't achieve the desired effect, the usual batch of UI adjustments would be available: running the timer faster or slower than once a frame, checking whether the mouse-pointer has moved by less than a certain amount rather than an exact not equals comparison, etc. Unlike MPT's suggestion in the wiki, this would not require creation of a separate focus state; unlike the suggestion in comment #11, there's no fixed timeout that aggravates the slow (with false-positives) or the fast (with false-negatives). A single frame's delay should be much, much faster than the time required to move your hand from your pointing device to the keyboard, even if you're using a trackpoint. ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/674138 Title: Global appmenu breaks sloppy focus -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 642725] Re: [i965gm] GPU lockup da0d83f9 (IPEHR: 0x02000004) in wine
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/642725 Title: [i965gm] GPU lockup da0d83f9 (IPEHR: 0x0204) in wine -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153805] Re: No full screen on Nvidia cards (gutsy)
As a workaround, you might be interested in the snes9x-gtk package, which includes OpenGL and XVideo drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/153805 Title: No full screen on Nvidia cards (gutsy) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 642725] [NEW] [i965gm] GPU lockup da0d83f9
Public bug reported: Binary package hint: xserver-xorg-video-intel Trying to get a game working under Wine. ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Chipset: i965gm DRM.card0.DVI.D.1: status: connected enabled: enabled dpms: On modes: 1600x1200 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 edid-base64: AP///wAQrAigTFQ2MB0PAQOAKR947mOQo1dLmyURUFSlSwCBgKlAcU8BAQEBAQEBAQEBSD9AMGKwMkBAwBMAbxMRAAAe/wBDMDY0ODU3QzA2VEwg/ABERUxMIDIwMDFGUAog/QA4TB9QEAAKICAgICAgADs= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sun Sep 19 20:50:54 2010 DkmsStatus: virtualbox-ose, 3.2.8, 2.6.35-21-generic, x86_64: installed virtualbox-ose, 3.2.8, 2.6.35-22-generic, x86_64: installed DumpSignature: da0d83f9 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py InterpreterPath: /usr/bin/python2.6 MachineType: Dell Inc. Studio Hybrid 140g ProcCmdLine: root=UUID=6d64f641-e37d-4b19-95c5-8334f86ae23a ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: SourcePackage: xserver-xorg-video-intel Title: [i965gm] GPU lockup da0d83f9 UserGroups: dmi.bios.date: 02/16/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 0P096C dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: '01' dmi.modalias: dmi:bvnDellInc.:bvr1.0.10:bd02/16/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA02:cvnDellInc.:ct3:cvr'01': dmi.product.name: Studio Hybrid 140g dmi.product.version: 00 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash freeze maverick -- [i965gm] GPU lockup da0d83f9 https://bugs.launchpad.net/bugs/642725 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 642725] Re: [i965gm] GPU lockup da0d83f9
** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607817/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607818/+files/CurrentDmesg.txt ** Attachment added: DRM.card0.SVIDEO.1.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607819/+files/DRM.card0.SVIDEO.1.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607820/+files/Dependencies.txt ** Attachment added: IntelGpuDump.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607821/+files/IntelGpuDump.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607822/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607823/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607824/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607825/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607826/+files/ProcInterrupts.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607827/+files/ProcMaps.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607828/+files/ProcModules.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607829/+files/ProcStatus.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607830/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607831/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607832/+files/UdevLog.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607833/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607834/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607835/+files/Xrandr.txt ** Attachment added: glxinfo.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607836/+files/glxinfo.txt ** Attachment added: i915_error_state.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607837/+files/i915_error_state.txt ** Attachment added: peripherals.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607838/+files/peripherals.txt ** Attachment added: setxkbmap.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607839/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607840/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.launchpad.net/bugs/642725/+attachment/1607841/+files/xkbcomp.txt -- [i965gm] GPU lockup da0d83f9 https://bugs.launchpad.net/bugs/642725 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 636979] Re: Develop in UFRaw extension breaks extension-handling.
This problem is still present in F-Spot 0.8.0. -- Develop in UFRaw extension breaks extension-handling. https://bugs.launchpad.net/bugs/636979 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 636979] Re: Develop in UFRaw extension breaks extension-handling.
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/636979/+attachment/1577264/+files/Dependencies.txt -- Develop in UFRaw extension breaks extension-handling. https://bugs.launchpad.net/bugs/636979 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 636979] [NEW] Develop in UFRaw extension breaks extension-handling.
Public bug reported: Binary package hint: f-spot After upgrading to Maverick from Jaunty, my previously-functioning F-Spot installation stopped working. After some investigation, I have observed the following: - Starting f-spot from the commandline, I get (among some Gdk-WARNING messages) the following output: [Info 20:21:05.629] Initializing Mono.Addins [Warn 20:21:07.287] There's (maybe) something wrong with some of the installed extensions. You can try removing the directory addin-db-000 from ~/.config/f-spot/ - I do as it suggests and delete the named directory then start F-Spot, I get the following output: [Info 20:25:59.899] Initializing Mono.Addins After starting F-Spot, the Tools and Photo - Export to... menus are populated. - I go Edit - Manage Extensions, unfold the Tools section, select Develop in UFRaw, click the Enable button on the right-hand-side, then close the window and restart F-Spot. I get the following output: [Info 20:29:04.141] Initializing Mono.Addins [Warn 20:29:06.007] There's (maybe) something wrong with some of the installed extensions. You can try removing the directory addin-db-000 from ~/.config/f-spot/ When F-Spot opens, the Tools and Photo - Export to... menus are empty. - I open the Manage Extensions dialog as before, disable Develop in UFRaw and restart F-Spot. I get the following output: [Info 20:31:18.593] Initializing Mono.Addins ...and the various extension menus are populated once more. I conclude something about the Develop in UFRaw extension in this version of F-Spot is broken. Out of curiousity, I compared a working addin-db-001 to a broken one, and found only the following difference: --- a/working-addin-db-001/config.xml +++ b/addin-db-001/config.xml @@ -1,3 +1,5 @@ Configuration - AddinStatus / + AddinStatus +Addin id=FSpot.DevelopInUFraw,0.8 enabled=True / + /AddinStatus /Configuration ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: f-spot 0.7.2-1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 Architecture: amd64 Date: Mon Sep 13 20:12:07 2010 ProcEnviron: PATH=(cuusernameom, user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: f-spot ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Develop in UFRaw extension breaks extension-handling. https://bugs.launchpad.net/bugs/636979 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 377598] Re: [i945gm] Video corruption when disabling internal monitor
I happened to be looking through bugs.freedesktop.org and I noticed a bug that sounds very much like this one: https://bugs.freedesktop.org/show_bug.cgi?id=22264 I added a comment mentioning this bug. ** Bug watch added: freedesktop.org Bugzilla #22264 https://bugs.freedesktop.org/show_bug.cgi?id=22264 -- [i945gm] Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 367309] Re: [i945GM] xrandr backlight control is bizarre on Macbook
I've deleted the references to the brightness-button problems I could not reproduce in Karmic. ** Description changed: Binary package hint: xserver-xorg-video-intel - I'm using Jaunty on a second-generation Macbook (Macbook2,1 in Apple - parlance) with an Intel 945GM graphics chip. Since at least Intrepid, - I've had a strange and puzzling behaviour with the backlight keys. - Tonight I tried upgrading to version 2.7 of the Intel driver from the - x-updates PPA in the vain hope it might resolve the issue, but since it - didn't I sat down and took a good hard look at the problem. + I'm currently using Jaunty on a second-generation Macbook (Macbook2,1 + in Apple parlance) with an Intel 945GM graphics chip, and have + reproduced this issue on Karmic Alpha 2. I tried switching to each of the available BACKLIGHT_CONTROL methods with xrandr --output LVDS --set BACKLIGHT_CONTROL $method, then checked the available range with xrandr --prop and tried a selection of brightness settings with xrandr --output LVDS --set BACKLIGHT $value When I run xrandr --prop the default BACKLIGHT_CONTROL value is native, whose range of backlight values is the unusual range 0..296. These numbers map to brightnesses as follows: - Even numbers from 0 to 40 turn off the backlight. - Even numbers from 42 to 296 uniformly increase the brightness to full strength. - Odd numbers from 1 to 253 uniformly decrease the brightness from full to very dim. - Odd numbers greater than or equal to 255 turn off the backlight. The end result is that trying to change the brightness with F1 and F2 involves mashing one or the other until you get a brightness level you're willing to put up with and hope that nothing changes it. The legacy BACKLIGHT_CONTROL method has a range of 0..255, where every value produces the same mid-level brightness. The combination BACKLIGHT_CONTROL has a range of 0..148, half the range of the native method, and it behaves like half the native method too: - Numbers from 0 to 20 turn off the backlight. - Numbers from 21 to 148 uniformly increase the brightness from very dim to full strength. The kernel BACKLIGHT_CONTROL has a range of 0..0. Setting the backlight value to '0' produces no obvious effect (if the backlight was on, it stays on; if the backlight was off it stays off) - A side note: when I first play with the keyboard brightness buttons, - they followed the chaotic behaviour of the default, native - BACKLIGHT_CONTROL above. Now that I've been messing with the - BACKLIGHT_CONTROL value, the brightness buttons control a smooth - gradient from 'very dim' to 'full strength' regardless of the - BACKLIGHT_CONTROL, although I can't actually turn the backlight off with - the keys. I'll ascribe that to some GNOME feature being clever, and - ignore it until the underlying xrandr feature is fixed. - I would be happy if the Intel driver defaulted to combination BACKLIGHT_CONTROL on my hardware, since at least that works in a predictable and useful fashion. However, certain patterns make me suspect there's some underlying problem to be fixed - like the fact that the total 'lit' range in 'combination' mode is 127 brightness levels, which seems a far more likely range than 148. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.7.0-1ubuntu1~xup~1 ProcEnviron: PATH=(cuusernameom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@creusernameed) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Intel Corporation Device [8086:7270] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) Subsystem: Intel Corporation Device [8086:7270] -- [i945GM] xrandr backlight control is bizarre on Macbook https://bugs.launchpad.net/bugs/367309 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 367309] Re: [i945GM] xrandr backlight control is bizarre on Macbook
I burned the Karmic Koala Alpha 2 64-bit desktop image to a CD-RW, booted off it, and tried reproducing the problem using the steps in comment 0: - Brightness keys on the keyboard can now turn the backlight off, which was not previously possible. - Brightness keys now navigate a reasonably smooth gradient from full-bright to off. - xrandr's BACKLIGHT_CONTROL still defaults to 'native' - xrandr's BACKLIGHT property, under 'native' control, still exhibits all the strange odd/even behaviour mentioned in the original comment. I would say this bug has become less urgent, since my brightness keys now work properly without intervention, but the underlying problem is still present. ** Attachment added: Xorg log, as requested. http://launchpadlibrarian.net/28483060/bug-367309-Xorg.0.log -- [i945GM] xrandr backlight control is bizarre on Macbook https://bugs.launchpad.net/bugs/367309 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 377598] Re: [i945gm] Video corruption when disabling internal monitor
I burned the Karmic Koala Alpha 2 64-bit desktop image to a CD-RW, booted off it, and tried reproducing the problem using the steps in comment 0. The exact same behaviour described there is still present. It has occurred to me that the 'safe' resolution of 1024x768 may merely be the largest of the resolution my two displays have in common, rather than a maximum pixel-count limit or something. I discovered a presumably unrelated problem that if I boot Karmic while the external monitor is connected, X eventually freezes and the computer needs to be hard-booted. Unfortunately, because I was booting off a CD, rebooting erased all the log files and I do not have sufficient information to file a bug. As requested, I have attached the Xorg.0.log file that was created while I was reproducing the bug. ** Attachment added: bug-377598-Xorg.0.log http://launchpadlibrarian.net/28483120/bug-377598-Xorg.0.log -- [i945gm] Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 383510] [NEW] virt-manager does not escape apostrophes
Public bug reported: Binary package hint: virt-manager What you'll need: - An actual ISO9660 image, bootable or not. - A file with an apostrophe in the name (such as a'b.iso, without the double-quotes) Steps to reproduce: 1. Start virt-manager 2. Create a new VM. 3. Go through all the pages of the setup wizard, accepting the defaults. - When it asks for installation media, you'll want to pick your actual ISO image. - When it asks whether you want to allocate the hard-disk image, you needn't bother as it's never going to be used anyway. 4. After the wizard, the VM is automatically booted up. Hit Force Off to shut down the VM. 5. Go to the Hardware tab, select the virtual CD-ROM device, and click connect. 6. Make sure ISO Image Location is selected, then click Browse and pick the file you created earlier with an apostrophe in the name. 7. Click OK. Expected result: - Source Path updates with the path to the selected ISO. Actual result: - Source Path isn't updated. The problems are actually more severe than that: 8. Click Connect again, notice that the ISO Location field is correctly filled out. 9. Click OK. 10. This time, you get an error dialog: Error Connecting CDROM: xmlParseDoc() failed 11. Click Close on the error dialog. 12. Close all the virt-manager windows to quit it. 13. Start virt-manager again. 14. Select the VM you created earlier, then click the Open button at the bottom of the window. 15. You get an error dialog: Error bringing up domain details: Error parsing domain xml: xmlParseDoc() failed. If you examine the contents of the domain settings file in /etc/libvirt/qemu/, you'll see it contains a line like this: source file='/home/username/a'b.iso'/ Deleting the extra apostrophe and restarting libvirtd is sufficient to restore the usual operation of virt-manager. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: virt-manager 0.6.1-1ubuntu4 ProcEnviron: PATH=(cuusernameom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: virt-manager Uname: Linux 2.6.28-11-generic x86_64 ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- virt-manager does not escape apostrophes https://bugs.launchpad.net/bugs/383510 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 383510] Re: virt-manager does not escape apostrophes
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27489257/Dependencies.txt -- virt-manager does not escape apostrophes https://bugs.launchpad.net/bugs/383510 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 268387] Re: [i945gm] querying driver for supported resolutions makes screen flash
As I understand it, the situation is this: the 945GM hardware has two 'output drivers' (CRTCs) for driving displays. When xrandr runs, it asks the driver for information on all connected displays, so the driver has to disconnect one of its CRTCs from your external monitor, and temporarily hook it up to the other available outputs in turn to see if there's a display connected to any of them. Once it's done, it hooks the CRTC back up to your external monitor and your display returns. I'm using a MacBook with a 945GM chip, and I have four available outputs - LVDS (the internal panel), TMDS-1 (external DVI), VGA (external VGA) and TV. Of those, I'm always using LVDS and TMDS-1, and the VGA connector can detect that it's disconnected without having to start up a CRTC, therefore when I run xrandr on a stock install, my screen flashes black while it probes the TV output. I don't have a TV connected, and I never intend to, so what I did was modify my xorg.conf to tell it to pretend there's no TV output at all. First, I added a new top-level section: Section Monitor Identifier DisabledMonitor Option Ignore true EndSection The Ignore option means that any output connected to this monitor will be ignored. Then, I added an option to the Device section: Option Monitor-TV DisabledMonitor This connects the TV output to the output-disabling monitor section above. After making this change and logging out, running xrandr no longer causes black flashes (incidentally, black flashes caused by programs such as Totem that used XVideo are also gone). -- [i945gm] querying driver for supported resolutions makes screen flash https://bugs.launchpad.net/bugs/268387 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 377598] Re: Video corruption when disabling internal monitor
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/26858662/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/26858663/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/26858664/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/26858665/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/26858666/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/26858668/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/26858670/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/26858671/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/26858672/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/26858673/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/26858674/setxkbmap.txt ** Attachment added: system.txt http://launchpadlibrarian.net/26858675/system.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/26858676/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/26858677/xkbcomp.txt -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
Here is a long-exposure image of the problem in action, after setting the external monitor's resolution to 1152x864 (far short of the native 1600x1200 res, hence the black border). As it's a long exposure, it's a good approximation of the visual chaos, but hard to see what's actually going on. ** Attachment added: A long-exposure image of the problem in action http://launchpadlibrarian.net/26858769/DSCF2493.JPG -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] [NEW] Video corruption when disabling internal monitor
Public bug reported: Binary package hint: xserver-xorg-video-intel I have an Apple MacBook (Model Macbook2,1) with Intel GM945 integrated graphics. I also have the official proprietary-to-DVI dongle, and a Dell LCD flat-panel with a native resolution of 1600x1200. When I'm at home, my preferred setup is to use the external monitor (and an external USB keyboard and mouse), and turn off the laptop's internal display (so I don't wear out the backlight). Unfortunately, if I disable the internal display and the external display is using a resolution higher than 1024x768, the external display goes nuts. I have not experimented much with gnome-display-properties, as it has an annoying habit of trying to adjust my xorg.conf, but I spent some time playing with xrandr directly: With the internal display set to 1280x800 (native resolution) and the external display set to 1600x1200 (native resolution): - xrandr --output LVDS --below TMDS-1 works fine (putting the internal display below the external one, both active) - xrandr --output TMDS-1 --off works fine (disabling the internal display) - xrandr --output LVDS --off works as long as the TMDS-1 mode is 1024x768 or lower. Since I can't disable the internal display, my current workaround is to run xrandr --auto (enabling both displays at their native resolution) and then run xrandr --output LVDS --pos 0x0 --set BACKLIGHT 2 (overlapping the internal and external displays, and disabling the internal display's backlight - the strange value is from https://bugs.launchpad.net/bugs/367309) I will attach screenshots of the problem and a log-fragment. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.7.0-1ubuntu2~xup~1 ProcEnviron: PATH=(cuusernameom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@creusernameed) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
Here is a short-exposure image of the problem in action, after setting the external monitor's resolution to 1152x864. Being a short-exposure image, it's harder to see the image, but if you crank the brightness up, you can see the jaunty-issues.txt Vim tab in which I was keeping notes about my experimentation, and down the bottom left you can see a few yellow e/st]$ from my bash prompt. ** Attachment added: A short-exposure image of the problem in action http://launchpadlibrarian.net/26858894/DSCF2494.JPG -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
Here is a short-exposure image of the problem in action, after setting the external monitor's resolution to 1152x864. Being a short-exposure image, it's harder to see the image, but if you crank the brightness up, you can see the jaunty-issues.txt Vim tab in which I was keeping notes about my experimentation, and down the bottom left you can see a few yellow e/st]$ from my bash prompt. ** Attachment added: A short-exposure image of the problem in action http://launchpadlibrarian.net/26859330/DSCF2494.JPG -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
I re-enabled the internal display then changed the external monitor's resolution to 1152x864, and since the internal display was enabled this time it worked. This image is mostly interesting so you can see where the previous screens were getting their various garbage. ** Attachment added: An image of the problem not occurring http://launchpadlibrarian.net/26859468/DSCF2499.JPG -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
Here is a fragment of my Xorg.0.log file, generated as follows: - Set the resolution to 1024x768, took a copy of the log. - Set the resolution to 1152x864, waited a second for the problem to kick in, took a copy of the log. - Diffed the two copies of the log, extracted the extra lines and wrote them to a new file. ** Attachment added: Lines added to Xorg.0.log while the problem occurred http://launchpadlibrarian.net/26861700/extra-lines -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 377598] Re: Video corruption when disabling internal monitor
A side note: the closest existing bug seems to be bug 316000, but this bug is distinct because this bug never manifests like that bug's screenshot, and this bug never manifests when both screens are enabled, while that bug only manifests if both screens are enabled. I guess I should also mention that although I'm running the 2.7.0 Intel driver from the x-updates PPA, I experienced the same behaviour with stock Jaunty and with Intrepid. -- Video corruption when disabling internal monitor https://bugs.launchpad.net/bugs/377598 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 367309] [NEW] xrandr backlight control is bizarre on Macbook 945GM
Public bug reported: Binary package hint: xserver-xorg-video-intel I'm using Jaunty on a second-generation Macbook (Macbook2,1 in Apple parlance) with an Intel 945GM graphics chip. Since at least Intrepid, I've had a strange and puzzling behaviour with the backlight keys. Tonight I tried upgrading to version 2.7 of the Intel driver from the x-updates PPA in the vain hope it might resolve the issue, but since it didn't I sat down and took a good hard look at the problem. I tried switching to each of the available BACKLIGHT_CONTROL methods with xrandr --output LVDS --set BACKLIGHT_CONTROL $method, then checked the available range with xrandr --prop and tried a selection of brightness settings with xrandr --output LVDS --set BACKLIGHT $value When I run xrandr --prop the default BACKLIGHT_CONTROL value is native, whose range of backlight values is the unusual range 0..296. These numbers map to brightnesses as follows: - Even numbers from 0 to 40 turn off the backlight. - Even numbers from 42 to 296 uniformly increase the brightness to full strength. - Odd numbers from 1 to 253 uniformly decrease the brightness from full to very dim. - Odd numbers greater than or equal to 255 turn off the backlight. The end result is that trying to change the brightness with F1 and F2 involves mashing one or the other until you get a brightness level you're willing to put up with and hope that nothing changes it. The legacy BACKLIGHT_CONTROL method has a range of 0..255, where every value produces the same mid-level brightness. The combination BACKLIGHT_CONTROL has a range of 0..148, half the range of the native method, and it behaves like half the native method too: - Numbers from 0 to 20 turn off the backlight. - Numbers from 21 to 148 uniformly increase the brightness from very dim to full strength. The kernel BACKLIGHT_CONTROL has a range of 0..0. Setting the backlight value to '0' produces no obvious effect (if the backlight was on, it stays on; if the backlight was off it stays off) A side note: when I first play with the keyboard brightness buttons, they followed the chaotic behaviour of the default, native BACKLIGHT_CONTROL above. Now that I've been messing with the BACKLIGHT_CONTROL value, the brightness buttons control a smooth gradient from 'very dim' to 'full strength' regardless of the BACKLIGHT_CONTROL, although I can't actually turn the backlight off with the keys. I'll ascribe that to some GNOME feature being clever, and ignore it until the underlying xrandr feature is fixed. I would be happy if the Intel driver defaulted to combination BACKLIGHT_CONTROL on my hardware, since at least that works in a predictable and useful fashion. However, certain patterns make me suspect there's some underlying problem to be fixed - like the fact that the total 'lit' range in 'combination' mode is 127 brightness levels, which seems a far more likely range than 148. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xserver-xorg-video-intel 2:2.7.0-1ubuntu1~xup~1 ProcEnviron: PATH=(cuusernameom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@creusernameed) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 SourcePackage: xserver-xorg-video-intel Uname: Linux 2.6.28-11-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- xrandr backlight control is bizarre on Macbook 945GM https://bugs.launchpad.net/bugs/367309 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 367309] Re: xrandr backlight control is bizarre on Macbook 945GM
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25996088/Dependencies.txt ** Attachment added: LsHal.txt http://launchpadlibrarian.net/25996089/LsHal.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/25996090/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/25996091/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/25996092/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/25996095/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/25996097/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/25996098/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/25996100/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/25996101/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/25996102/setxkbmap.txt ** Attachment added: system.txt http://launchpadlibrarian.net/25996103/system.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/25996104/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/25996105/xkbcomp.txt -- xrandr backlight control is bizarre on Macbook 945GM https://bugs.launchpad.net/bugs/367309 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 342717] [NEW] fc-cache segfaults when scanning an italic BDF font with empty SETWIDTH_NAME
Public bug reported: Binary package hint: fontconfig Steps to reproduce: 1. Save the attached .bdf font into an empty, temporary directory. 2. Run the following command: fc-cache . Expected results: - fc-cache scans the directory, finds no usable fonts, quits cleanly. Actual results: - Segmentation fault. Notes: Deleting either of the properties in the font prevents the crash, as does changing the value of SETWIDTH_NAME to be non-empty. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: fontconfig 2.6.0-1ubuntu4 ProcEnviron: PATH=/home/username/bin:/home/username/bin-shared:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig Uname: Linux 2.6.27-11-generic i686 ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- fc-cache segfaults when scanning an italic BDF font with empty SETWIDTH_NAME https://bugs.launchpad.net/bugs/342717 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 342717] Re: fc-cache segfaults when scanning an italic BDF font with empty SETWIDTH_NAME
** Attachment added: Test-case for reproducing the crash. http://launchpadlibrarian.net/23851210/fc-cache-test.bdf ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/23851211/Dependencies.txt -- fc-cache segfaults when scanning an italic BDF font with empty SETWIDTH_NAME https://bugs.launchpad.net/bugs/342717 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 215039] Re: Xorg crashed with SIGSEGV in XkbWriteXKBGeometry()
*** This bug is a duplicate of bug 184651 *** https://bugs.launchpad.net/bugs/184651 Following the reproduction steps in the first comment, I no longer get the crash. I still can't achieve the results I wanted (A MacBook keyboard layout with Dvorak keymap) because of the Error activating XKB configuration message I alluded to above, but at least the X server doesn't crash. -- Xorg crashed with SIGSEGV in XkbWriteXKBGeometry() https://bugs.launchpad.net/bugs/215039 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 180114] Re: package libnss3-1d None [modified: /var/lib/dpkg/info/libnss3-1d.list] failed to install/upgrade: trying to overwrite `/usr/lib/nss/libfreebl3.so', which is also in package libnss3-0d
Eventually I got around it by using apt-get remove libnss3-0d (note: not aptitude), then removing all 27 packages that depended on it, then running aptitude dist-upgrade to continue upgrading to 8.04. -- package libnss3-1d None [modified: /var/lib/dpkg/info/libnss3-1d.list] failed to install/upgrade: trying to overwrite `/usr/lib/nss/libfreebl3.so', which is also in package libnss3-0d https://bugs.launchpad.net/bugs/180114 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 206477] [NEW] deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch()
*** This bug is a duplicate of bug 146256 *** https://bugs.launchpad.net/bugs/146256 Public bug reported: Binary package hint: deskbar-applet I just upgraded to Ubuntu 8.04 this evening (deskbar-applet is version: 2.22.0.1-0ubuntu1), and while trying to tweak my settings I tried to launch gconf-editor the same way I always do: 1. Super-Space to activate deskbar 2. type 'gconf' 3. hit the down arrow until Launch Configuration Editor is highlighted under History 4. hit Enter Expected result: * gconf-editor launches Actual result: * A dialog appears that says: 'Deskbar has quit unexpectedly. If you reload a panel object, it will automatically be added back to the panel.' ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Tue Mar 25 21:42:28 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/lib/deskbar-applet/deskbar-applet InterpreterPath: /usr/bin/python2.5 Package: deskbar-applet 2.22.0.1-0ubuntu1 PackageArchitecture: amd64 ProcCmdline: /usr/bin/python /usr/lib/deskbar-applet/deskbar-applet --oaf-activate-iid=OAFIID:Deskbar_Applet_Factory --oaf-ior-fd=36 ProcEnviron: LANG=en_AU.UTF-8 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SHELL=/bin/bash Signal: 11 SourcePackage: deskbar-applet StacktraceTop: ?? () from /usr/lib/libgnome-desktop-2.so.2 gnome_desktop_item_launch () ?? () PyEval_EvalFrameEx () PyEval_EvalCodeEx () Title: deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch() Uname: Linux 2.6.24-12-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner vboxusers video ** Affects: deskbar-applet (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch() https://bugs.launchpad.net/bugs/206477 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 206477] Re: deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch()
*** This bug is a duplicate of bug 146256 *** https://bugs.launchpad.net/bugs/146256 ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/12854631/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/12854632/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/12854633/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/12854634/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/12854635/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/12854636/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/12854637/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/12854638/ThreadStacktrace.txt -- deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch() https://bugs.launchpad.net/bugs/206477 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 206477] Re: deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch()
*** This bug is a duplicate of bug 146256 *** https://bugs.launchpad.net/bugs/146256 Also: I can flawlessly launch the GNOME terminal by typing 'term' and selecting it from the history, but 'gconf' crashes every time. After clearing the deskbar-applet history, I can no longer reproduce the problem; obviously there must have been some history entry left over from Gutsy that caused issues. Deskbar still shouldn't crash just from a history entry, though. -- deskbar-applet crashed with SIGSEGV in gnome_desktop_item_launch() https://bugs.launchpad.net/bugs/206477 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 180114] Re: package libnss3-1d None [modified: /var/lib/dpkg/info/libnss3-1d.list] failed to install/upgrade: trying to overwrite `/usr/lib/nss/libfreebl3.so', which is also in package libnss3-0d
This exact scenario happened to me today, trying to upgrade from 7.10 to 8.04 beta. As far as I know, I'm not using any un-official packages at all - what should I be looking for? -- package libnss3-1d None [modified: /var/lib/dpkg/info/libnss3-1d.list] failed to install/upgrade: trying to overwrite `/usr/lib/nss/libfreebl3.so', which is also in package libnss3-0d https://bugs.launchpad.net/bugs/180114 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 185280] Re: NetworkManager fouls up /etc/hosts
I messed around with network-admin until the problem stopped happening, so I took some time today to try and reproduce the problem again. I kept notes about what I was doing, which I've attached. The short version is: - In roaming mode, NetworkManager (well, network-admin, but I suspect they're closely related) likes to forget the settings I've told it, like domain name and DNS servers. The easiest way to make this happen is to reboot; I suspect renewing the DHCP lease might cause the same effect, although unplugging and re-plugging the network cable doesn't. - The fact that the Location field doesn't stay set between invocations of network-admin is confusing, especially given the larger-scale forgetting in the previous point. - It seems that the crucial factor is not the contents of the Hosts tab, but the General tab - the long delays appear when Domain is empty on the General tab, but go away when Domain is filled in. I'm not sure if this is actually a NetworkManager bug - it might be a documentation bug (The network-admin online help is rather simplistic and doesn't mention roaming mode at all, let alone tell me how I should expect it to work). If this bug is in the wrong place, I'd appreciate any help you could give me about moving it to wherever the right place might be. ** Attachment added: network-manager-log.txt http://launchpadlibrarian.net/12771288/network-manager-log.txt -- NetworkManager fouls up /etc/hosts https://bugs.launchpad.net/bugs/185280 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 185280] NetworkManager fouls up /etc/hosts
Public bug reported: (pasted from http://bugzilla.gnome.org/show_bug.cgi?id=452929 after they claimed it was Not Their Problem) I recently installed Ubuntu 7.10 on a MacBook, and this same thing happens all the time (with my wired Ethernet connection). Any X11 program pauses for about ten seconds at startup while (I assume) trying to do reverse-DNS (my test program was time xterm -e ls). Manually changing the line in /etc/hosts from: 127.0.1.1 deacon.thristian.org ...to: 127.0.1.1 deacon.thristian.org deacon resolves the issue, but after sleeping and waking the laptop, or whatever causes NetworkManager to wake up and reshuffle the config files it controls, this is automatically fixed to be: 127.0.1.1 deacon.thristian.org deacon.thristian.org ...and of course the problem is back. ** Affects: ubuntu Importance: Undecided Status: New -- NetworkManager fouls up /etc/hosts https://bugs.launchpad.net/bugs/185280 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 185280] Re: NetworkManager fouls up /etc/hosts
It looks much like this: Host Settings Host name: deacon Domain name: thristian.org -- NetworkManager fouls up /etc/hosts https://bugs.launchpad.net/bugs/185280 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
