[Desktop-packages] [Bug 401823]
This seems more like a server issue. I think it could easily be possible for the server to guarantee that XIDs are not reused within a certain time period since it issued a DestroyNotify. That won't guarantee that clients are happy, but it can certainly help. We just need to store a timestamp of the time the XID was destroyed and if the head of the recycle queue is too recent, we allocate a new XID rather than recycling. Tracking for 1.12, but I'd consider this for 1.11.x if the change is simple enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead Status in Chromium Browser: Invalid Status in Mozilla Firefox: Invalid Status in GTK+: Expired Status in xlibs: Unknown Status in firefox package in Ubuntu: Fix Released Status in firefox-3.5 package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: Fix Released Status in firefox source package in Lucid: Invalid Status in firefox-3.5 source package in Lucid: Invalid Status in gtk+2.0 source package in Lucid: Invalid Status in firefox source package in Karmic: Invalid Status in firefox-3.5 source package in Karmic: Won't Fix Status in gtk+2.0 source package in Karmic: Fix Released Bug description: karmic testing in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead previously, have had this one: (nautilus:3572): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (bug report 401822) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 35794]
Do you still have hardware to test this? Is it still an issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/35794 Title: TV out is broken with VT1621 chip Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Incomplete Bug description: I have a EPIA V-1 board which uses a trident cyberblade/i1 with a VIA VT1621 to do tv-out over the composite connector. The trident_drv.so in xserver-xorg-driver-trident is broken and displays noise on the screen (it looks as if the refresh rate is totally wrong or as if it is sending NTSC data when I have actually asked for PAL). The driver from http://www.blackfiveservices.co.uk/EPIATVOut.shtml gets it right - although you have to get tvtool from the same site and turn on PAL output once the xserver has loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/35794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 41148]
Is this still an issue. The ubuntu bug was closed due to lack of response, so I'm wondering if it has been fixed already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-savage in Ubuntu. https://bugs.launchpad.net/bugs/41148 Title: buggy display of video in totem Status in X.Org X server: Invalid Status in xserver-xorg-video-savage package in Ubuntu: Incomplete Bug description: I have display several videos (mov and wmv) with totem on a savage xorg driver and saw lots of problem of display : an example can be found here : http://www.flickr.com/photos/57244393@N00/134263889/ I have replay those video thru the vesa driver, and no problem appear. Im on a Dapper and savage driver version is 2.0.2.3-0ubuntu1. So right now, I fall back on vesa. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/41148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 313525]
Can you provide a server log for a working state and a broken state for comparison? What version change introduces the problem? A new radeon driver or a new server? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/313525 Title: [r200] Strange tremor on the monitor Status in X.Org X server: Invalid Status in xserver-xorg-driver-ati: Invalid Status in xorg-server package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-driver-ati Ubuntu Lucid with ATI FireGl 8800 card (r200 chip). lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QH [Radeon 8500] (rev 80) My monitor model is an HP p1120 -HorizSync 30-121 -VertRefresh 48-160 Since I installed intrepid I have a temblor in my monitor (In the other Ubuntu releases it works great). It is especially visible at the edges of the windows. It is very strange because all seems to be correct (with the default xorg.conf configuration): - Resultion is on the default 1600x1200 - The vertical refresh rate is on the default 85Hz - The horizontal refresh rate is on 106.3kHz I try to configure the HorizSync and VertRefresh manually editing the /etc/X11/xorg.conf file but nothing changes The tremor is only in 1600x1200 resolution. The others resolutions works well In Windows with the same settings (1600x1200 - 106.3kHz/85Hz) there is no tremor To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/313525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 148117]
This is coming from R128InitDDARegisters during init in r128_driver.c: Roff = XclksPerTransferPrecise * (DisplayFifoDepth - 4); Ron = (4 * info->ram->MB + 3 * MAX(info->ram->Trcd - 2, 0) + 2 * info->ram->Trp + info->ram->Twr + info->ram->CL + info->ram->Tr2w + XclksPerTransfer) << (11 - UseablePrecision); Not that it helps me much, but maybe someone can work with that... That being said, this driver isn't really maintained anymore since it's not used my modern devices... so I'm not sure this will ever be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/148117 Title: [r128] Rage 128: Unsuitable videomode autoselected Status in X.org xf86-video-r128: Invalid Status in xorg package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-video-ati I tested Ubunti 7.10-beta-desktop-i386 on my PCs. At one PC the X-Server was not able to start, and i saw only the commandline. This PC has a ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline an got errormessages, the X-Server didn't start: auth: creating new authority file /home/ubuntu/.serverauth.20130 xauth: creating new authority file /home/ubuntu/.Xauthority xauth: creating new authority file /home/ubuntu/.Xauthority X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6) Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 Build Date: 21 September 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 1 21:58:06 2007 (==) Using config file: "/etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in (II) Module already built-in (EE) R128(0): No DFP detected (II) Module already built-in (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752) Fatal server error: AddScreen/ScreenInit failed for driver 0 XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. *** The /etc/X11/xorg.conf: *** # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device""/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device""/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice"
[Desktop-packages] [Bug 255826]
Is this still an issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-savage in Ubuntu. https://bugs.launchpad.net/bugs/255826 Title: scrolling in Firefox causes Xorg-process to lag (S3 Savage driver) Status in X.Org X server: Invalid Status in xserver-xorg-video-savage package in Ubuntu: Invalid Bug description: In a new installation of Xubuntu hardy from alternate CD on an old Toshiba Satellite Pro 4300 Series everything seems to work but when using the scroll bar in Firefox the system becames unstable and must be rebooted to recover. The only change necessary for it to work was adding acpi=force at Kernel boot up. When this happen: - The display is not correctly updated / refreshed - The Xorg process consumes more CPU than normal (~30/40%) - Everything related to graphical windows slows down, but terminals (opened before) work correctly. Here is some information about the system and configuration: jordi@canigo:~$ lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 00:05.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 00:05.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:05.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:05.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:07.0 Communication controller: Agere Systems 56k WinModem (rev 01) 00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO 00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 20) 00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 20) 00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02) 01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11) 06:00.0 Network controller: RaLink RT2561/RT61 rev B 802.11g jordi@canigo:~$ sudo lshw -C video [sudo] password for jordi: *-display UNCLAIMED description: VGA compatible controller product: 86C270-294 Savage/IX-MV vendor: S3 Inc. physical id: 0 bus info: pci@:01:00.0 version: 11 width: 32 bits clock: 66MHz capabilities: pm agp agp-1.0 vga_controller bus_master cap_list configuration: latency=248 maxlatency=255 mingnt=4 The xorg.conf file only has "Configured video device" and "Configured Monitor", which I think is normal in Ubuntu 8.04 I think it detects correctly the card and loads the correct driver: jordi@canigo:~$ lsmod | grep savage savage 33920 2 drm82452 3 savage If you need more information, I'll provide it. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/255826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
AFAICT, nobody has followed my direction above and brought this up for discussion on xorg-devel. Without that, it's not likely to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
AFAICT, nobody has followed my direction above and brought this up for discussion on xorg-devel. Without that, it's not likely to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
I suggest you ask on xorg-devel about your patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Incomplete Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
I suggest you ask on xorg-devel about your patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
@colin-law no, this bug does not apply to Unity. This bug was filed years before Unity even existed. If it is fixed by changing to Unity, that's great for Unity users, but simply sweeping an issue under the rug because you changed window systems doesn't change the fact the the bug continues to exist in the windowing systems that the issue was reported against. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in emerald: New Status in One Hundred Papercuts: Fix Released Status in metacity: In Progress Status in ubuntu-mate: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in unity-2d: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 99255]
Created attachment 52160 photo of issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-savage in Ubuntu. https://bugs.launchpad.net/bugs/99255 Title: S3 driver displays pink banner when viewing HD videos Status in X.Org X server: Invalid Status in xserver-xorg-video-savage package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-savage It seems that the S3 savage driver for Xorg has a hardcoded limitation regarding its Xv functionality. If a video is wider than 800 pixels wide, then the rest of the screen has a pink color. For example, my 480p video that is 853x480, has 53 pixels rendered as pink color on the right side of the screen, resulting in a vertical pink banner. Same happens no matter what media player I use, as it's an Xv driver bug, not a media player one. Some facts: 1. It only happens when Xv is used. Other transports work without this bug, but without Xv you don't want to watch HD video anyway because it is too slow without acceleration. 2. When I grab a screenshot from the framebuffer, the pink banner is not there. It only renders the pink vertical banner in the screen, not in the framebuffer. 3. DRI driver is loaded, but not working (bug #99251) Section Device Identifier S3 Inc. SuperSavage IX/C SDR Driver savage Option VBERestoretrue Option hwcursor 1 Option DPMS on Option backingstore Option BusType AGP Option DmaType AGP Option DmaMode None Option AGPMode 4 Option AGPSize 16 EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/99255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 99255]
Please attach files if possible. I'm glad that your image wasn't 404ing after 4 years, so I was able to upload it to the bug. While the hardware is limited to 1Kx1K, is there something we can do to make this fail more elegantly than with the pink banner? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-savage in Ubuntu. https://bugs.launchpad.net/bugs/99255 Title: S3 driver displays pink banner when viewing HD videos Status in X.Org X server: Invalid Status in xserver-xorg-video-savage package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-savage It seems that the S3 savage driver for Xorg has a hardcoded limitation regarding its Xv functionality. If a video is wider than 800 pixels wide, then the rest of the screen has a pink color. For example, my 480p video that is 853x480, has 53 pixels rendered as pink color on the right side of the screen, resulting in a vertical pink banner. Same happens no matter what media player I use, as it's an Xv driver bug, not a media player one. Some facts: 1. It only happens when Xv is used. Other transports work without this bug, but without Xv you don't want to watch HD video anyway because it is too slow without acceleration. 2. When I grab a screenshot from the framebuffer, the pink banner is not there. It only renders the pink vertical banner in the screen, not in the framebuffer. 3. DRI driver is loaded, but not working (bug #99251) Section Device Identifier S3 Inc. SuperSavage IX/C SDR Driver savage Option VBERestoretrue Option hwcursor 1 Option DPMS on Option backingstore Option BusType AGP Option DmaType AGP Option DmaMode None Option AGPMode 4 Option AGPSize 16 EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/99255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 119341]
Is this still an issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vesa in Ubuntu. https://bugs.launchpad.net/bugs/119341 Title: glxinfo command causes Xorg to abort on Dimension E520 Status in The Dell Project: Fix Released Status in X.Org X server: Won't Fix Status in “xserver-xorg-video-vesa” package in Ubuntu: Fix Released Bug description: When running the glxinfo command on a Dimension E520 running Gutsy Tribe-1, Xorg aborts and then gdm presents the login prompt again. To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/119341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 199486]
configure.ac needs a bit more work. For example, if I pass --with-consolekit and I don't actually have it, configure should error out, but it just silently continues without consolekit. Other than that, it looks good. Mind updating the patch? Feel free to email it to xorg-devel for review, or attach here and I'll review it again. Bonus points if you use 'git format-patch' with a commit message that I can use rather than just 'git diff' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinit in Ubuntu. https://bugs.launchpad.net/bugs/199486 Title: ConsoleKit integration Status in X Window System initializer: In Progress Status in “consolekit” package in Ubuntu: Fix Released Status in “ume-config-common” package in Ubuntu: Invalid Status in “xinit” package in Ubuntu: Invalid Status in “xorg” package in Ubuntu: Invalid Status in “xinit” package in Debian: Fix Released Bug description: Hi, xinit needs to gain ConsoleKit integration just like GDM has ConsoleKit integration as more and more parts of the GNOME/FreeDesktop desktops are relying on it to grant access to DBus services: /etc/dbus-1/system.d/bluetooth.conf: policy at_console=true /etc/dbus-1/system.d/newprinternotification.conf: policy at_console=true /etc/dbus-1/system.d/nm-applet.conf:policy at_console=true /etc/dbus-1/system.d/hal.conf: policy at_console=true /etc/dbus-1/system.d/NetworkManager.conf:policy at_console=true There are some upstream patches which don't seem to work in all cases. This is critical for UME as it launches the hildon-desktop via startx. Bye, To manage notifications about this bug go to: https://bugs.launchpad.net/xinit/+bug/199486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 199486]
(In reply to comment #10) Hrm. What about the comments from Loic? I don't think our comments conflict. Loic was concerned about adding dependencies, and I was suggesting making them soft rather than hard dependencies. The only real concern that I see is Michael's: Typically xinit is not run as a root, so the user does not have enough permissions to create a session with parameters. I question weather or not we should try to move this call into X? X is setuid root. I admit that I did not read that comment the first time through as it was collapsed in my view of the bug. On darwin, we trigger a LaunchDaemon in startx to do some privileged actions for xinit (like creating /tmp/.X11-unix). How is this currently handled on other OSs? Still as an init script? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinit in Ubuntu. https://bugs.launchpad.net/bugs/199486 Title: ConsoleKit integration Status in X Window System initializer: In Progress Status in “consolekit” package in Ubuntu: Fix Released Status in “ume-config-common” package in Ubuntu: Invalid Status in “xinit” package in Ubuntu: Invalid Status in “xorg” package in Ubuntu: Invalid Status in “xinit” package in Debian: Fix Released Bug description: Hi, xinit needs to gain ConsoleKit integration just like GDM has ConsoleKit integration as more and more parts of the GNOME/FreeDesktop desktops are relying on it to grant access to DBus services: /etc/dbus-1/system.d/bluetooth.conf: policy at_console=true /etc/dbus-1/system.d/newprinternotification.conf: policy at_console=true /etc/dbus-1/system.d/nm-applet.conf:policy at_console=true /etc/dbus-1/system.d/hal.conf: policy at_console=true /etc/dbus-1/system.d/NetworkManager.conf:policy at_console=true There are some upstream patches which don't seem to work in all cases. This is critical for UME as it launches the hildon-desktop via startx. Bye, To manage notifications about this bug go to: https://bugs.launchpad.net/xinit/+bug/199486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 516123]
Please send your patch to the xorg-devel mailing list for review. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/516123 Title: xvfb does not support randr Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: Upstream bug created with patch; its essentially a one-liner. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/516123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 516123]
*** Bug 19510 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/516123 Title: xvfb does not support randr Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: Upstream bug created with patch; its essentially a one-liner. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/516123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 325074]
Please test with xorg-server-1.11.1. We believe that this is probably fixed in 1.11. If there is no response in the next month, this issue will be closed as presumed fixed. See http://lists.freedesktop.org/archives/xorg/2011-September/053561.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/325074 Title: Window redrawing does not work properly with KDE4 taskbar tooltips. Status in KDE Base Components: Won't Fix Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Bug description: On Kubuntu Jaunty, when a KDE taskbar tooltip is drawn on the screen, the last place in which a tooltip was drawn becomes transparent in any window, showing whatever is behind it. This bug only occurs, however, if the tooltip was drawn onto an area of the screen where it does not cover the window. If the tooltip covers any part of a window, then the transparent blocks where the old tooltip was do not appear. Because of this, maximized windows are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/325074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 325074]
Over to Ville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/325074 Title: Window redrawing does not work properly with KDE4 taskbar tooltips. Status in KDE Base Components: Won't Fix Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Bug description: On Kubuntu Jaunty, when a KDE taskbar tooltip is drawn on the screen, the last place in which a tooltip was drawn becomes transparent in any window, showing whatever is behind it. This bug only occurs, however, if the tooltip was drawn onto an area of the screen where it does not cover the window. If the tooltip covers any part of a window, then the transparent blocks where the old tooltip was do not appear. Because of this, maximized windows are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/325074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 325074]
This has been merged to the 1.11 branch and will be in 1.11.2 RC2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/325074 Title: Window redrawing does not work properly with KDE4 taskbar tooltips. Status in KDE Base Components: Won't Fix Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Bug description: On Kubuntu Jaunty, when a KDE taskbar tooltip is drawn on the screen, the last place in which a tooltip was drawn becomes transparent in any window, showing whatever is behind it. This bug only occurs, however, if the tooltip was drawn onto an area of the screen where it does not cover the window. If the tooltip covers any part of a window, then the transparent blocks where the old tooltip was do not appear. Because of this, maximized windows are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/325074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 106060]
No response. Closing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/106060 Title: [r128 1002:5446] Selecting the Molecule screensaver makes the PC freeze. It is completely unresponsive. Status in xf86-video-r128: Invalid Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “xserver-xorg-video-r128” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-panel Selecting the Molecule screensaver freezes my PC completely. It says Creating molecule or something like that, but it stays there, fully unresponsive to any keyboard input, and I can't click the Force Quit button either. Happens every time I try to select it, requires me to hard reset. I think it might be a compatibility problem with my graphics card. It's an ATI Rage 128 AGP card. This is a clean install of Ubuntu. The bug also affects the 1002:5046 cards. ProblemType: Bug Architecture: i386 Date: Thu Apr 12 21:49:16 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 1:2.18.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/sergei ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel Uname: Linux GP33-1 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-r128/+bug/106060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 524830]
I don't see how this could be happening in xorg-server ... my guess is that it is kernel related. Keith, can you comment? Nicolo, are you still experiencing with newer kernels? Can you attach system information: lspci -v dmesg /var/log/Xorg.*.log etc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/524830 Title: problems triggered when I open the laptop lid Status in Gnome Settings Daemon: Fix Released Status in X.Org X server: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Bug description: Binary package hint: gnome-settings-daemon The problems I have are minor, and are not present if gnome-settings-daemon is not running. They come every time I open the laptop lid (of course after having closed it, no matter for how long) 1) the first bulk of keypresses lag some seconds (no matter when I hit the keys, it can also be 1 minute after I opened the lid) then the keyboard goes back to normal work 2) some panel icons (apparently all applets) suddenly disappear and reappear (like a flahs). This does not always happen ProblemType: Bug Architecture: amd64 Date: Sat Feb 20 11:03:42 2010 DistroRelease: Ubuntu 10.04 Package: gnome-settings-daemon 2.29.90-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-13.19-generic SourcePackage: gnome-settings-daemon Uname: Linux 2.6.32-13-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/524830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 863511] Re: NetworkManager does not allow adding an IPv4 network without a gateway
How do I unexpire this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/863511 Title: NetworkManager does not allow adding an IPv4 network without a gateway Status in “network-manager-applet” package in Ubuntu: Expired Bug description: I want to add the 10.0.1.0/255.255.255.0 network to one of my interfaces, but I don't want to add a gateway on this network. NetworkManager does not enable the save button unless there is a gateway present. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:53:17 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/863511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 863514] [NEW] NetworkManager does not update the active interface on save
Public bug reported: NetworkManager does not update the current networking configuration on save. If you hit save after editing an interface, the current configuration remains unchanged. I was able to apply the changes by running: sudo /etc/init.d/network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:58:54 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/863514 Title: NetworkManager does not update the active interface on save Status in “network-manager” package in Ubuntu: New Bug description: NetworkManager does not update the current networking configuration on save. If you hit save after editing an interface, the current configuration remains unchanged. I was able to apply the changes by running: sudo /etc/init.d/network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:58:54 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/863514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 863511] [NEW] NetworkManager does not allow adding an IPv4 network without a gateway
Public bug reported: I want to add the 10.0.1.0/255.255.255.0 network to one of my interfaces, but I don't want to add a gateway on this network. NetworkManager does not enable the save button unless there is a gateway present. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:53:17 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/863511 Title: NetworkManager does not allow adding an IPv4 network without a gateway Status in “network-manager” package in Ubuntu: New Bug description: I want to add the 10.0.1.0/255.255.255.0 network to one of my interfaces, but I don't want to add a gateway on this network. NetworkManager does not enable the save button unless there is a gateway present. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:53:17 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/863511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 863511] Re: NetworkManager does not allow adding an IPv4 network without a gateway
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/863511 Title: NetworkManager does not allow adding an IPv4 network without a gateway Status in “network-manager” package in Ubuntu: New Bug description: I want to add the 10.0.1.0/255.255.255.0 network to one of my interfaces, but I don't want to add a gateway on this network. NetworkManager does not enable the save button unless there is a gateway present. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager 0.9.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Sep 30 10:53:17 2011 ExecutablePath: /usr/sbin/NetworkManager InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110920.5) IpRoute: default via 75.144.255.94 dev eth1 proto static 10.0.1.0/24 dev eth1 proto kernel scope link src 10.0.1.5 metric 1 75.144.255.88/29 dev eth1 proto kernel scope link src 75.144.255.92 169.254.0.0/16 dev eth1 scope link metric 1000 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-29T00:57:43.214046 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/863511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 857159] Re: nautilus launches indiscriminantly (it should not launch for xfce, etc)
Confirmed fixed, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/857159 Title: nautilus launches indiscriminantly (it should not launch for xfce, etc) Status in “nautilus” package in Ubuntu: Fix Released Bug description: I just did a fresh install of 11.10 current (20110920 image and current repos). I installed xubuntu-desktop. When I login choosing xubuntu as my session type, nautilus is run even though I would expect it not to. The nautilus desktop window covers my xfce desktop. The workaround is to fire up terminal and kill nautilus when I login, but that's quite annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/857159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 857159] [NEW] nautilus launches indiscriminantly (it should not launch for xfce, etc)
Public bug reported: I just did a fresh install of 11.10 current (20110920 image and current repos). I installed xubuntu-desktop. When I login choosing xubuntu as my session type, nautilus is run even though I would expect it not to. The nautilus desktop window covers my xfce desktop. The workaround is to fire up terminal and kill nautilus when I login, but that's quite annoying. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/857159 Title: nautilus launches indiscriminantly (it should not launch for xfce, etc) Status in “nautilus” package in Ubuntu: New Bug description: I just did a fresh install of 11.10 current (20110920 image and current repos). I installed xubuntu-desktop. When I login choosing xubuntu as my session type, nautilus is run even though I would expect it not to. The nautilus desktop window covers my xfce desktop. The workaround is to fire up terminal and kill nautilus when I login, but that's quite annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/857159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
