[Ubuntu-x-swat] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
I'm wondering if the anti-aliasing mode is a bit of a red hearing here, or only partially related. In my case, the app that triggers this is CLion 2023.3. Except in my case, I can reproduce it consistently simply by *changing* the anti-aliasing setting between subpixel and grayscale (in *either* direction) and clicking "apply." But once I log back in and re-launch the app, the system works fine and doesn't crash (regardless of the setting). Outside of that action, the bug behaves more like a time-bomb. There seems to be like a 5% chance that clicking the "debug" icon in the toolbar will take down my X session. Most of the time it works fine, until it doesn't. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] Re: Xorg crash report after resume
I don't see a "Closed" status. The closest thing I see to make it go away is "Invalid", but I would say that you can close it, unless the thing to do is add Crash to the config by default so it isn't a manual step. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] Re: Xorg crash report after resume
Adding Crash to the config file seems to have done the trick. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] Re: Xorg crash report after resume
>From that bug report I followed this step: "It works to edit /etc/apport/crashdb.conf and add 'Crash' to the 'problem_types': ['Bug', 'Package', 'Crash'], or to make that change in a separate file and run". So I'll see how that fares. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] Re: Xorg crash report after resume
Output of ls -l total 2320 -rw-r- 1 root whoopsie 2373147 Feb 1 13:35 _usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] Re: Xorg crash report after resume
1. I'm not sure what you mean by the ID of the bug. The file is owned by root, group whoopsie 2. The contents of the file whoopsie-id are: ad2a60d37ef07a75f5bb69241962893c2ee51bf68be6d93a3b37992aaf2d45370ac7a5094e472b57985c4979bd5355af775f1d483c51977972fa4f743003d70c 3. didn't do this part -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1814174] [NEW] Xorg crash report after resume
Public bug reported: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814174/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1720701] [NEW] Add multiarch metadata to libpixman-1-dev
Public bug reported: Release: Artful Aardvark 17.10 Package version: 0.34.0-1 After modifying libpixman-1-dev to be Multi-Arch: same, and checking that it installs architecture-specific files appropriately, and successfully building and installing both the amd64 and i386 versions simultaneously, it seems like libpixman-1-dev can be upgraded to get multiarch support fairly easily. ** Affects: pixman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/1720701 Title: Add multiarch metadata to libpixman-1-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1720701/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1720692] Re: Add multiarch metadata to libxkbcommon*dev packages
** Description changed: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. + + Also, tests/x11comp is actually deactivated, and seems to be the only + place that uses one of the x11-xkb-utils binaries, so maybe this + dependency can just be removed? ** Description changed: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. - Also, tests/x11comp is actually deactivated, and seems to be the only - place that uses one of the x11-xkb-utils binaries, so maybe this - dependency can just be removed? + Also, tests/x11comp is actually deactivated (since Mar 13, 2016 + upstream), and seems to be the only place that uses one of the x11-xkb- + utils binaries, so maybe this dependency can just be removed? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1720692 Title: Add multiarch metadata to libxkbcommon*dev packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1720692/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1720692] [NEW] Add multiarch metadata to libxkbcommon*dev packages
Public bug reported: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. ** Affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New ** Description changed: + Release: Artful Aardvark 17.10 + Package Version: 0.7.1-2 + As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1720692 Title: Add multiarch metadata to libxkbcommon*dev packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1720692/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1376903] Re: Caps lock delay
It appears this would also affect numlock as well. (and yes, it's a problem that's affecting me as well--which makes it impossible to type stuff in Linux since I routinely use the caps lock key for a lot of different scenarios). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1376903 Title: Caps lock delay To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1376903/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1527829] [NEW] displayport MST external monitors don't return from sleep mode
Public bug reported: When displays go to sleep, upon return from sleep the two monitors attached to a belkin mini displayport to 2x HDMI, do not return from sleep. This results in part of the desktop being inaccessible, until the external displays are unplugged, and then plugged back in. Sometimes, Xorg will also back down to one monitor. The data accompanying this report is for an instance where the power save mode caused Xorg to drop to the primary monitor only. This is on Ubuntu 15.10 on a Dell XPS 13 (9333) with integrated intel HD 4400 graphics. There are two external monitors connected by HDMI to a belkin DP-MST adapter which connects to the mini-displayport. A single- HDMI-to-mini-displayport belkin adapter works as expected (coming out of power save). xserver-xorg-video-intel: Installed: 2:2.99.917+git20150808-0ubuntu4 Expected behavior: Displays go to sleep, and upon returning all displays are still present and all wake. Xorg.0.log, relevant happenings: [ 189.711] (II) intel(0): Disabled output DP1-1 [ 189.711] (II) intel(0): Disabled output DP1-2 [ 189.739] (II) intel(0): resizing framebuffer to 1920x1080 [ 189.745] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 190.339] (II) intel(0): Enabled output DP1-1 [ 190.351] (II) intel(0): Enabled output DP1-2 dmesg relevant happenings: [ 190.031929] [ cut here ] [ 190.032008] WARNING: CPU: 1 PID: 1114 at /build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:476 intel_pipe_will_have_type.isra.41+0x6e/0x80 [i915]() [ 190.032015] WARN_ON(num_connectors == 0) [ 190.032019] Modules linked in: [ 190.032025] drbg ansi_cprng ctr ccm rfcomm vmw_vsock_vmci_transport vsock vmw_vmci bnep snd_hda_codec_hdmi arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_wmi hid_rmi sparse_keymap kvm dell_laptop crct10dif_pclmul dcdbas crc32_pclmul dell_smm_hwmon aesni_intel iwlmvm aes_x86_64 lrw mac80211 gf128mul glue_helper ablk_helper cryptd iwlwifi uvcvideo serio_raw videobuf2_vmalloc videobuf2_memops videobuf2_core cfg80211 v4l2_common videodev media snd_hda_codec_realtek hid_multitouch snd_hda_codec_generic lpc_ich shpchp joydev input_leds snd_soc_rt5640 btusb btrtl snd_soc_rl6231 btbcm btintel snd_soc_core bluetooth snd_compress snd_hda_intel mei_me mei snd_hda_codec snd_hda_core ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi [ 190.032158] snd_seq snd_seq_device snd_timer snd acpi_als kfifo_buf dw_dmac industrialio dw_dmac_core soundcore snd_soc_sst_acpi 8250_dw i2c_designware_platform dell_rbtn i2c_designware_core spi_pxa2xx_platform intel_smartconnect mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 hid_generic usbhid uas usb_storage i915 i2c_algo_bit drm_kms_helper psmouse drm ahci libahci wmi video sdhci_acpi sdhci i2c_hid hid [ 190.032287] CPU: 1 PID: 1114 Comm: Xorg Not tainted 4.2.0-21-generic #25-Ubuntu [ 190.032293] Hardware name: Dell Inc. XPS13 9333/0GFTRT, BIOS A04 03/19/2014 [ 190.032298] 187f4872 880212327ad8 817e9449 [ 190.032309] 880212327b30 880212327b18 8107b3d6 [ 190.032318] 8802119e1800 8801f0382d80 6667 [ 190.032327] Call Trace: [ 190.032342] [] dump_stack+0x45/0x57 [ 190.032354] [] warn_slowpath_common+0x86/0xc0 [ 190.032364] [] warn_slowpath_fmt+0x55/0x70 [ 190.032420] [] intel_pipe_will_have_type.isra.41+0x6e/0x80 [i915] [ 190.032474] [] intel_modeset_compute_config.part.90+0x460/0xb80 [i915] [ 190.032496] [] ? drm_atomic_helper_check_modeset+0x62/0x970 [drm_kms_helper] [ 190.032600] [] intel_modeset_compute_config+0x42/0x50 [i915] [ 190.032667] [] intel_crtc_set_config+0x28f/0x580 [i915] [ 190.032736] [] ? drm_modeset_lock_all_crtcs+0x90/0xa0 [drm] [ 190.032783] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 190.032839] [] drm_mode_setcrtc+0x3e9/0x500 [drm] [ 190.032879] [] drm_ioctl+0x125/0x610 [drm] [ 190.032889] [] ? fsnotify+0x316/0x4a0 [ 190.032922] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 190.032937] [] do_vfs_ioctl+0x295/0x480 [ 190.032946] [] ? __sb_end_write+0x35/0x70 [ 190.032953] [] ? vfs_write+0x15a/0x1a0 [ 190.032962] [] SyS_ioctl+0x79/0x90 [ 190.032986] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 190.033013] ---[ end trace 9834aabfe51525cf ]--- [ 190.033036] [ cut here ] (so on) Other warnings: [ 190.068878] WARNING: CPU: 0 PID: 1114 at /
[Ubuntu-x-swat] [Bug 1468834] Re: lightdm does not source .xsession
I don't follow the reason for closing this... It seems like maybe you're thinking I said this bug is all wrong, but it's not. The point is that instead of *sourcing* $HOME/.xsession, the Xsession system script should *exec* it if it exists, completely bypassing the rest of the system Xsession script. The debian manual I linked to actually describes that behavior. The point is, Ubuntu appears to ignore it entirely. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1468834 Title: lightdm does not source .xsession To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468834] Re: lightdm does not source .xsession
>From the debian manual: > any user who defines "~/.xsession" or "~/.Xsession" is able to customize the action of "/etc/X11/Xsession" by completely overriding the system code. It does (or did) that by executing the script via exec... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1468834 Title: lightdm does not source .xsession To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468834] Re: lightdm does not source .xsession
It may well have, but it's a change that's bad. For what it's worth, the Debian manuals still document this: https://www.debian.org/doc/manuals/debian- reference/ch07.en.html#_customizing_the_x_session_classic_method I've been a member of the Linux community for 20 years--Take comfort in the fact that these shell scripts have often changed rather arbitrarily over the years on many different distributions, and the owners of those changes seemingly do not understand the consequences of the changes they have made. This stuff was designed this way for a reason... It's supposed to make it easy for the user to customize their X window system session regardless of what shell they use or how they have their environment set up. This change is one of several that actually work against that goal. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1468834 Title: lightdm does not source .xsession To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468834] Re: lightdm does not source .xsession
Try: man xsession The X window system has been reading this file since forever. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1468834 Title: lightdm does not source .xsession To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
Awesome. it's finally working. Added the trusty proposed repo and updated( it updated quite a lot of other stuff). I was able to install the amd drivers for my Radeon hd 8600 m series with the catalyst center. I am on Ubuntu 14.04.2. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1424491/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
Affects me too. Ubuntu gnome 14.04.2 AMD A6-5200 APU with Radeon(TM) HD Graphics × 4 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1424491/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
Hi,
I was wondering if someone could help me out on this.
I would like to apply the patch, but have very little ubuntu knowledge.
I am running ubuntu 14.04 and have found I get this problem.
The workaround in #22 works for me, but makes the fonts hard to read.
This is why I would like to use Alexander's patch.
However, I am not sure how to do it.
I checked my system for xfsettingsd and displays.c but could not find either
sudo . -name displays.c -print
returns nothing (run from the root dir)
I assume that if I can find displays.c all I need to do is go to that directory
and do:
patch < {patchname}
Any/All help appreciated.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1308105
Title:
Xfce resets TV mode to NULL when power cycled
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad
I'll just add that this problem (not surprisingly) also exists on my Lenovo Helix. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1026046 Title: Missing support for thumb resting on bottom of clickpad To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad
Where is this problem originating? Is it a bug in the synaptics driver or is it just a missing feature? Is there something making is particularly hard to fix? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1026046 Title: Missing support for thumb resting on bottom of clickpad To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
I am also having an issue where my system completely locks up. Mouse / keyboard are unresponsive and I am unable to ssh in from another system. This is a new build with all new hardware: ASUS H81I-PLUS Socket 1150 w/ Intel H81 Chipset Intel Pentium G3220 Dual-Core Processor @ 3.0 GHz Team Vulcan 8GB (2 x 4GB) 240-Pin DDR3 1600 (under clocked to 1333 by the BIOS) Intel 330 Series 60GB SSD on-board Intel graphics connected via HDMI to a 24" Samsung LCD TV I was originally running openSuSE 13.3 w/KDE, but as this system is meant to be a multimedia system, it was causing more trouble that I wanted to deal with. I do not recall it freezing at any time. I then installed Kubuntu 13.10 64bit as the multimedia support is better than SuSE. This is when I started to get multiple lock ups. I thought maybe it was due to something not being happy with 13.10, so I installed 12.04.3 LTS w/ KDE 4.12. I also removed the 8GB 'Team' memory and installed a single 4GB ADATA 1333MHz DIMM. This appeared to have resolved the issue, but it locked up on me three times yesterday. Once while using Amarok (remote mySQL database & collection on a FreeNAS NFS share), once while just using the desktop and another while attempting to play an 800MB .MKV file in XBMC standalone (remote mySQL, file located on a FreeNAS NFS share). I've checked the various logs, and there does not appear to be anything of any relevance as nothing 'crashes' exactly, the entire system just locks. I've disabled all power management features & functions. No wi-fi hardware installed / enabled. Cat 6 gigabit network connection. Microsoft Sculpt bluetooth keyboard w/ ASUS bluetooth dongle - paired with bluemon Microsoft ARC wireless mouse w/ MS wireless dongle -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/993187 Title: ubuntu 12.04 completely freezes frequently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1159609] Re: random freeze
I'm sorry I forgot to mention it, but I had the same problem with random locking up when I used the ATI graphics that came with the computer. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1159609 Title: random freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1159609/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1159609] [NEW] random freeze
Public bug reported: The system locks up at random. It may not lock for a day after booting up the machine. It may lock up after a few minutes of booting up the machine. Sometimes the display just freezes, displaying whatever was last being displayed on the monitor. Sometimes the monitor displays a solid color when locking up. The machine does not respond to pings nor any of the key combinations involving sysrq. The only way to recover is a hard reset. The machine is running Kubuntu 12.04.2 LTS Release:12.04 The computer is a HP Pavilion p6-2003w Desktop PC. The url giving its specs is below. http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03052733&lang=en&cc=us&contentType=SupportFAQ&prodSeriesId=5151865&prodTypeId=12454 Motherboard AAHD2-HY (Holly) Manufacturer: Pegatron Form factor: uATX: 24.38 cm (9.6 inches) x 24.38 cm (9.6 inches) Chipset: AMD Hudson-D2 FCH Memory sockets: 2 x DDR3 Front side bus speeds: 100 MHz UMI (Unified Media Interface) Processor socket: FM1 Expansion Slots: PCI-Express Generation 2 speed 1 PCI Express x16 3 PCI Express x1 1 PCI Express Mini Card x1 Processor AMD E2 3200 Processor TDP: 65W Operating speed: Up to 2.4 GHz Number of cores: 2 Socket: FM1 Bus speed: 4.0 GT/s HT3 Memory 4 GB Amount: 4 GB Speed: PC3-10600 MB/sec Type: DDR3-1333 The above is the memory it came with. I have since added another identical 4GB. This upgrade did not affect the random lockup problem. Built in graphics AMD E-Series Processors E2-3200 HD 6370D65W This is the on board graphics. I have added an NVIDIA geforce 210 1024MB card. This upgrade did not affect the random lockup problem. Sound/Audio Integrated Realtek ALC 656 Audio *Integrated audio is not available if a sound card is installed. Built-in High Definition 5.1 channel audio Audio codec: Realtek ALC 656 Networking LAN: 1000-Base-T Interface: PCI Express x1 Technology: Realtek RTL8111E gigabit ethernet controller Data transfer speeds: up to 10/100/1000 Mb/s Transmission standards: 1000-Base-T Ethernet I added an additional RTL8111 PCIe nic. This also did not affect the locking up issue. The machine came with windows7. I soon replaced it with XP. The random lockup bug didn't show itself until I replaced windows with Kubuntu. For a few weeks I tried Slackware 14.0 64bit and did not experience any problem with randome freezes during this time. When I reinstalled Kubuntu, the random lockup bug returned. Thanks for your help. Derek ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Sun Mar 24 20:01:49 2013 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) MarkForUpload: True ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu precise -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1159609 Title: random freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1159609/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1089171] Re: x server crashes while running Inkscape
Ove, thank you. I'm now running Inkscape under the xorg-edgers repository X server and it's been stable for several hours. (Better than not getting my holiday cards done!) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1089171 Title: x server crashes while running Inkscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1089171/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1089171] [NEW] x server crashes while running Inkscape
Public bug reported: X server crashes while running Inkscape (v. 0.48.3.1 r9886) while trying to perform any operation on the workspace. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,water,compiztoolbox,move,resize,snap,mousepoll,gnomecompat,grid,regex,imgpng,place,session,wall,vpswitch,animation,unitymtgrabhandles,workarounds,fade,expo,scale,opacify,ezoom,unityshell] CompositorRunning: None Date: Tue Dec 11 19:53:34 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] InstallationDate: Installed on 2012-10-19 (53 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 2306CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=1c4b211c-ee1e-4dbd-a1d5-591db928b646 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET32WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET32WW(1.12):bd05/30/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1089171 Title: x server crashes while running Inkscape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1089171/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 96676] Re: function keys don't work in gnome-terminal
I've read through all of the comments, related bugs, etc, but I'm wondering: is there any way to fix this via termcap or without changing code for gnome-terminal? Otherwise xterm seems to be the only option for me to run emacs in a tmux session because many of my bindings are Ctrl- Fx. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/96676 Title: function keys don't work in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/96676/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 894132] Re: unity does not start using xinerama and multi-monitor
Hi, I've upgraded to 12.04 and the issue still exists. The ubuntu_2d session loads but not ubuntu. I'll dig in further... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/894132 Title: unity does not start using xinerama and multi-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/894132/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589275] Re: client application error messages fill up disk in .xsession-errors
Oh. I'd just like to note that: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/661494/comments/7 is a bit more compact if you guys can use that approach Also. https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/661494/comments/8 another possible source of disc space abuse. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/589275 Title: client application error messages fill up disk in .xsession-errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/589275/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 894132] Re: unity does not start using xinerama and multi-monitor
Hi, I'm still running 11.04 and the result is the same. I plan on upgrading soon and will post my findings. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/894132 Title: unity does not start using xinerama and multi-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/894132/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 969860] Re: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers)
Here's my stack trace. dstack kept hanging, so I just ran gdb manually. This appears to be the same bug, but the workarounds don't help. This is a: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5430 Series] And the ioctl that loops is ioctl(13, 0xc00c645c, 0x7fff5a9fde00) = 0 Where 13 is /dev/ati/card0. fglrx is 2:8.960-0ubuntu1, x86_64, Ubuntu 12.04 ** Attachment added: "dstack.trace" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/969860/+attachment/3221797/+files/dstack.trace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/969860 Title: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/969860/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 894132] Re: unity does not start using xinerama and multi-monitor
Hi, I can confirm I have this problem using two AMD cards on a triple monitor setup. Unity_2d session works and running 'unity --reset' does not render the 3d version of unity and the display results in broken windows. I've attached the log (run_unity_reset.log) Some other info: uname -a Linux ringo 2.6.38-13-generic #55-Ubuntu SMP Tue Jan 24 15:34:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux /usr/lib/nux/unity_support_test -p OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI FirePro V4800 (FireGL) OpenGL version string: 4.1.11272 Compatibility Profile Context FireGL Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity supported: yes lspci | grep VGA 03:00.0 VGA compatible controller: ATI Technologies Inc FirePro V4800 04:00.0 VGA compatible controller: ATI Technologies Inc FirePro V4800 grep 'Output.*connected' /var/log/Xorg.0.log [44.955] (II) fglrx(0): Output DFP1 connected [44.955] (II) fglrx(0): Output DFP2 connected [44.955] (II) fglrx(0): Output DFP3 disconnected [44.955] (II) fglrx(0): Output CRT1 disconnected [45.247] (II) fglrx(1): Output DFP1 disconnected [45.247] (II) fglrx(1): Output DFP2 disconnected [45.247] (II) fglrx(1): Output DFP3 connected [45.247] (II) fglrx(1): Output CRT1 disconnected Hope this helps. ** Attachment added: "output when running unity --reset from unity_2d session" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/894132/+attachment/2791190/+files/run_unity_reset.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/894132 Title: unity does not start using xinerama and multi-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/894132/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 894132] Re: unity does not start using xinerama and multi-monitor
I'm also attaching my Xorg.conf and output of Xorg.0.log. Section "ServerLayout" Option "Xinerama" Identifier "amdcccle Layout" Screen 0 "amdcccle-Screen[3]-0" 0 0 Screen "amdcccle-Screen[3]-1" 3200 0 EndSection Section "Monitor" Identifier "0-DFP1" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" Option "PreferredMode" "1600x1200" Option "TargetRefresh" "60" Option "Position" "0 0" Option "Rotate" "normal" Option "Disable" "false" EndSection Section "Monitor" Identifier "0-DFP2" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" Option "PreferredMode" "1600x1200" Option "TargetRefresh" "60" Option "Position" "1600 0" Option "Rotate" "normal" Option "Disable" "false" EndSection Section "Monitor" Identifier "1-DFP3" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" Option "PreferredMode" "1600x1200" Option "TargetRefresh" "60" Option "Position" "0 0" Option "Rotate" "normal" Option "Disable" "false" EndSection Section "Device" Identifier "amdcccle-Device[3]-0" Driver "fglrx" Option "Monitor-DFP1" "0-DFP1" Option "Monitor-DFP2" "0-DFP2" BusID "PCI:3:0:0" EndSection Section "Device" Identifier "amdcccle-Device[3]-1" Driver "fglrx" Option "Monitor-DFP3" "1-DFP3" BusID "PCI:4:0:0" EndSection Section "Screen" Identifier "amdcccle-Screen[3]-0" Device "amdcccle-Device[3]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Virtual 3200 3200 Depth 24 EndSubSection EndSection Section "Screen" Identifier "amdcccle-Screen[3]-1" Device "amdcccle-Device[3]-1" DefaultDepth 24 SubSection "Display" EndSubSection EndSection ** Attachment added: "Xorg.0.log file when logging into a Ubuntu session." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/894132/+attachment/2791197/+files/Xorg.0.log_xinerama_ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/894132 Title: unity does not start using xinerama and multi-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/894132/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 770283] Re: [fglrx]title bar does not update on non-maximized windows
Happens in 11.10 Gnome Classic running compiz & ATI 11.9 (fglrx 8.892). Shaded windows still show their window decorations. Using Ctrl+Alt+Shift+Left/Right to move windows between workspaces/viewports is also broken - window just returns to the screen it started on. Seems like window's got totally screwed over with the Unity re- writes...and they still aren't addressing any issues they created even after a second release. 7 months and only a tiny bit of triaging on this...can't we even get a "report this upstream/to compiz/to AMD" or "we are dropping support for gnome classic, bugger off" so we know you are actively ignoring it, instead of passively ignoring it? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/770283 Title: [fglrx]title bar does not update on non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/770283/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771716] Re: middle click emulation not working
Comment #19 worked for me. I had to *install* gpointing-device-settings first, but once I did, and enabled that for PS/2 mouse, I got my paste back. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/771716 Title: middle click emulation not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/771716/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 791900] Re: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output
Behaviour unchanged with that metacity pref flipped, however, I *did* discover that gstreamer-properties is misleading. I have to test with totem. If I switch in gstreamer-properties (no Xv to Xv) the test button *sometimes* succeeds (shows test pattern instead of blackness). However, if I go into totem, the videos still fail to play until I switch back to no Xv in gstreamer-properties. Restart of gstreamer-properties pretty much always confirms the blackness w/ test button. Probably some gui bug in application. One guess, the switch of gui pref not instantly applied so when I hit test I'm still on No Xv. Perhaps the Test button should be greyed if the option has been changed until it is confirmed it is updated in system or something. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/791900 Title: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/791900/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 791900] Re: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output
Ok. Problem persisted after reboot. So apparently it is independent of video driver. BTW, external VGA monitor *did* fail until I used nvidia driver, but I didn't file that since nvidia fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/791900 Title: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/791900/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 791900] Re: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output
Well. I sincerely apologise. I *was* on nouveau and I saw this behaviour. I used gstreamer-properties under nvidia and thought I saw an ok test screen, but I must have screwed up somehow? 'cause now I'm back to blackness in nvidia as well. The only thing I can think of is it is related to suspend on closed lid, which seems to occasionally muddle brightness. I'm going to reboot now, and see if I still get a black screen on vids. At this instant though, it appears the behaviour is the same regardless of whether I am using nouveau or nvidia. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/791900 Title: Sony VPC-F11 (VPCF11GGX) Totem and other gstreamer apps have a black screen unless No Xv is selected in gstreamer-properties under Video Default Output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/791900/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771716] Re: middle click emulation not working
Same behaviour, touchpad on a Sony VPC-F11GGX ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=11 [slave pointer (2)] Very annoying behaviour, especially with terminal windows. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/771716 Title: middle click emulation not working ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 661494] Re: Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs
FWIW, I tried modifying mine to add a head -c and it seems just fine. I hope this issue can get a little more attention, since it can have significant stability impact in the pathological case. -- Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs https://bugs.launchpad.net/bugs/661494 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 661494] Re: Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs
Or.. piping to any command capable of doing a rolling log would be even better. -- Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs https://bugs.launchpad.net/bugs/661494 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 661494] [NEW] Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs
Public bug reported: Binary package hint: x11-apps Recently, I discovered a system that had been completely shut down for a rather ridiculous reason. Over a period of 21 hours, a user's .xsession-filled with the following: Starting Oracle Universal Installer... Checking installer requirements... Checking operating system version: must be redhat-4, redhat-5, SuSE-9 or SuSE-10 Passed All installer requirements met. Checking Temp space: must be greater than 400 MB. Actual 384320 MBPassed Checking swap space: must be greater than 512 MB. Actual 7730MBPassed Checking monitor: must be configured to display at least 256 colorsFailed >>> Could not execute /usr/X11R6/bin/xdpyinfo Checking if CPU speed is above 300 MHz.Actual 2992 MHzPassed Some optional pre-requisite checks have failed (see above). Continue? (y/n) [n] Continue? (y/n) [n] Continue? (y/n) [n] Continue? (y/n) [n] Continue? (y/n) [n] Continue? (y/n) [n] ... repeat that last portion about 20 billion times, approximately 256,000 repetitions of the phrase per second, until: # ls -lh .xsession-errors -rw--- 1 1000 1000 373G 2010-08-26 13:11 .xsession-errors Now. I have looked into the history of this, and I've noted that this sort of thing happens periodically. Users file a bug, and it is closed. Now, I'm aware that this is obviously the fault of misbehaving apps... But. Is there any reason this couldn't be mitigated? I've read elsewhere that right now the syntax for this file is xinit calling: exec >"$ERRFILE" 2>&1 Could that not be changed to: exec 2>&1 | head -c 500 > "$ERRFILE" Or something similar? Thanks! ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New -- Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs https://bugs.launchpad.net/bugs/661494 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 609938] Re: fglrx fails build on 2.6.35-10-generic
great! long for ubuntu10.10… 2010/9/24, mogens busk <609...@bugs.launchpad.net>: > The new package solves the problem, just run the following commands. > sudo apt-get update > sudo apt-get dist-upgrade > sudo apt-get install fglrx > go to system, administration, proprietary drivers and enable the driver > reboot > every thing ok > (driver version 2:8.780-0ubuntu1, kernel 2.6.35-22) > > -- > fglrx fails build on 2.6.35-10-generic > https://bugs.launchpad.net/bugs/609938 > You received this bug notification because you are a direct subscriber > of a duplicate bug (625654). > > Status in “fglrx-installer” package in Ubuntu: Confirmed > > Bug description: > After upgrading to Ubuntu Maverick 10.10, fglrx fails to build against the > latest kernel. > > The version of fglrx I have installed is 2:8.723.1-0ubuntu4. > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: fglrx 2:8.723.1-0ubuntu4 > ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5 > Uname: Linux 2.6.35-10-generic i686 > Architecture: i386 > CheckboxSubmission: fd01eb15b59ed67c9dd8540fc136fdae > CheckboxSystem: fc73f07fcd9845bb95fa3ca6b8be7ef2 > DRM.card0.HDMI_Type_A.1: > status: disconnected > enabled: disabled > dpms: On > modes: > edid-base64: > DRM.card0.VGA.1: > status: disconnected > enabled: disabled > dpms: On > modes: > edid-base64: > Date: Mon Jul 26 00:08:44 2010 > DkmsStatus: > fglrx, 8.723.1: added > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-10-generic > root=UUID=eb8d1d11-9ffa-457c-949b-2c5dec76ff74 ro quiet splash > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: fglrx-installer > dmi.bios.date: 04/29/2002 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: HV84510A.86A.0040.P11.0204291648 > dmi.board.name: D845WN > dmi.board.vendor: Intel Corporation > dmi.board.version: AAA64179-207 > dmi.chassis.type: 2 > dmi.modalias: > dmi:bvnIntelCorp.:bvrHV84510A.86A.0040.P11.0204291648:bd04/29/2002:svn:pn:pvr:rvnIntelCorporation:rnD845WN:rvrAAA64179-207:cvn:ct2:cvr: > system: > distro: Ubuntu > codename: maverick > architecture: i686 > kernel: 2.6.35-10-generic > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/609938/+subscribe > -- fglrx fails build on 2.6.35-10-generic https://bugs.launchpad.net/bugs/609938 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 609938] Re: fglrx fails build on 2.6.35-10-generic
thanks to Felix Kuehling ... his advice may help. but i'm in colledge now,without my computer,i can't try it... waitting for your good news 2010/9/16 Fsolda > Do you know if will be there a new version of this driver in the final > version of Ubuntu Maverick? > > > Em Qua, 2010-09-15 às 21:59 +, Felix Kuehling escreveu: > > This happens every time Ubuntu updates their kernel and/or Xorg version > > and leaves the old fglrx driver in place that was never designed to work > > with those new X.org and kernel versions. > > > > Maybe one way to save users this kind of trouble in the future would be > > to add versioned dependencies to fglrx to make it conflict with kernel > > or X.org versions newer than what was in the last stable Ubuntu release. > > This way, if a user explicitly or implicitly updates their X.org or > > kernel to a new major version, they'd be forced to uninstall fglrx > > first. > > > > -- > fglrx fails build on 2.6.35-10-generic > https://bugs.launchpad.net/bugs/609938 > You received this bug notification because you are a direct subscriber > of a duplicate bug (625654). > > Status in “fglrx-installer” package in Ubuntu: Confirmed > > Bug description: > After upgrading to Ubuntu Maverick 10.10, fglrx fails to build against the > latest kernel. > > The version of fglrx I have installed is 2:8.723.1-0ubuntu4. > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: fglrx 2:8.723.1-0ubuntu4 > ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5 > Uname: Linux 2.6.35-10-generic i686 > Architecture: i386 > CheckboxSubmission: fd01eb15b59ed67c9dd8540fc136fdae > CheckboxSystem: fc73f07fcd9845bb95fa3ca6b8be7ef2 > DRM.card0.HDMI_Type_A.1: > status: disconnected > enabled: disabled > dpms: On > modes: > edid-base64: > DRM.card0.VGA.1: > status: disconnected > enabled: disabled > dpms: On > modes: > edid-base64: > Date: Mon Jul 26 00:08:44 2010 > DkmsStatus: > fglrx, 8.723.1: added > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-10-generic > root=UUID=eb8d1d11-9ffa-457c-949b-2c5dec76ff74 ro quiet splash > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: fglrx-installer > dmi.bios.date: 04/29/2002 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: HV84510A.86A.0040.P11.0204291648 > dmi.board.name: D845WN > dmi.board.vendor: Intel Corporation > dmi.board.version: AAA64179-207 > dmi.chassis.type: 2 > dmi.modalias: > dmi:bvnIntelCorp.:bvrHV84510A.86A.0040.P11.0204291648:bd04/29/2002:svn:pn:pvr:rvnIntelCorporation:rnD845WN:rvrAAA64179-207:cvn:ct2:cvr: > system: > distro: Ubuntu > codename: maverick > architecture: i686 > kernel: 2.6.35-10-generic > > > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/609938/+subscribe > -- fglrx fails build on 2.6.35-10-generic https://bugs.launchpad.net/bugs/609938 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625654] Re: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524229/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524230/+files/CurrentDmesg.txt ** Attachment added: "DKMSBuildLog.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524231/+files/DKMSBuildLog.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524232/+files/Dependencies.txt ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524233/+files/DkmsStatus.txt ** Attachment added: "GdmLog.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524234/+files/GdmLog.txt ** Attachment added: "GdmLog1.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524235/+files/GdmLog1.txt ** Attachment added: "GdmLog2.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524236/+files/GdmLog2.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524237/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524238/+files/Lsusb.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524239/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524240/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524241/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524242/+files/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524243/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524244/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524245/+files/UdevLog.txt ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524246/+files/XorgLog.txt ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524247/+files/XorgLogOld.txt ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524248/+files/Xrandr.txt ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524249/+files/glxinfo.txt ** Attachment added: "make.log.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524250/+files/make.log.txt ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524251/+files/peripherals.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524252/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524253/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/625654/+attachment/1524254/+files/xkbcomp.txt -- package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/625654 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625654] [NEW] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build
Public bug reported: I do want to know how to solve it . ubuntu says E: fglrx: subprocess installed post-installation script returned error exit status 10 E: fglrx-amdcccle: dependency problems - leaving unconfigured ProblemType: Package DistroRelease: Ubuntu 10.10 Package: fglrx 2:8.723.1-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic x86_64 Architecture: amd64 Date: Sat Aug 28 11:39:17 2010 ErrorMessage: fglrx kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: BIOSTAR Group TA890GXE PackageVersion: 2:8.723.1-0ubuntu4 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=a0db49e8-8fd5-42c5-ac07-6d559eabf19e ro quiet splash SourcePackage: fglrx-installer Title: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build dmi.bios.date: 07/09/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: TA890GXE dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd07/09/2010:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.name: TA890GXE dmi.sys.vendor: BIOSTAR Group system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-19-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package maverick -- package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/625654 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 605225] Re: returning from suspend or hibernation causes video card to flicker and you must reboot to fix. Cannot close laptop.
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/51896547/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/51896548/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/51896549/Dependencies.txt ** Attachment added: "GdmLog.txt" http://launchpadlibrarian.net/51896550/GdmLog.txt ** Attachment added: "GdmLog1.txt" http://launchpadlibrarian.net/51896551/GdmLog1.txt ** Attachment added: "GdmLog2.txt" http://launchpadlibrarian.net/51896552/GdmLog2.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/51896553/Lspci.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/51896554/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/51896555/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/51896556/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/51896557/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/51896558/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/51896559/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/51896560/UdevLog.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/51896561/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/51896562/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/51896563/Xrandr.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/51896564/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/51896565/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/51896566/xkbcomp.txt -- returning from suspend or hibernation causes video card to flicker and you must reboot to fix. Cannot close laptop. https://bugs.launchpad.net/bugs/605225 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 605225] [NEW] returning from suspend or hibernation causes video card to flicker and you must reboot to fix. Cannot close laptop.
Public bug reported: Binary package hint: xorg If laptop lid is closed or you set the unit to suspend or hibernate, when you try to reactivate unit. The screen will flicker uncontrollably and you are forced to restart computer if you are lucky enough to see where the mouse is. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 Architecture: amd64 Date: Tue Jul 13 20:21:41 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 5100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=93bd83c1-f933-4432-922b-70c8f1bd82af ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5100 dmi.product.version: V3.13 dmi.sys.vendor: Acer glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-23-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- returning from suspend or hibernation causes video card to flicker and you must reboot to fix. Cannot close laptop. https://bugs.launchpad.net/bugs/605225 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 553739] Re: [gm45] Mouse Cursor changes from white to black
I'm actually seeing the same thing and I'm using the custom binary NVidia drivers. The custom pointer was working fine in 9.10 but now I get the described behavior in 10.04 after the upgrade. -- [gm45] Mouse Cursor changes from white to black https://bugs.launchpad.net/bugs/553739 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] Re: glxgears randomly reports vertical sync, but isn't sync'd
Assume a package upgrade fixed this sometime during karmic. ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 569271] Re: [RS780 KMS] no poweroff on halt with KMS enabled
Ok, I created a workaround that uses upstart instead . I just created an upstart job in /etc/init that removes the module. The job file is attached. ** Attachment added: "uloadradeon.conf" http://launchpadlibrarian.net/45596476/uloadradeon.conf -- [RS780 KMS] no poweroff on halt with KMS enabled https://bugs.launchpad.net/bugs/569271 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 568738] Re: Could not boot into Ubuntu 10.04 release candidate
I reinstalled Windows and Ubuntu 9.10 creating a dual partition on my hard drive. Went into Ubuntu 9.10 and installed updates. Then installed restricted extras. Upgraded to 10.04 release candidate. Photo attached is a list of boot options. Highlighted option in photo is the only option that has not given me problems other than running only in low graphics mode. Boot option on top of list worked after first going into highlighted option and then restarting computer, but only in low graphics mode and no ability to connect to my wireless router. Restarted computer, went to highlighted option and opened System > Preferences > Monitors. Got message "It appears that your graphics driver does not support the necessary extensions to use this tool. Do you want to use your graphics driver vendor's tool instead?." Clicked yes. Got message "You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server." Did a google search using message and found a command on Ubuntu forums "sudo nvidia-xconfig and then ctrl+alt+backspace to reset X." Did so, restarted computer, went back into boot options and picked top option. Graphics now worked and got online okay, but after 3 minutes the computer and router disconnected from each other and I kept getting a window asking me to enter the keycode for the router. I kept retrying and quit after the third attempt. Restarted computer, went back to top of boot options, again graphics worked but still could not connect to router. Turned off computer, restarted router, turned on computer, went back to same option, did not make a difference. 10.04 with low graphics will work great if I keep using the highlighted option as shown in attached photo. Graphics work great for boot option at top of list but cannot connect online. Hope this helps some more. ** Attachment added: "Photo of Ubuntu and Windows boot options." http://launchpadlibrarian.net/45544977/DSC_0607.JPG -- Could not boot into Ubuntu 10.04 release candidate https://bugs.launchpad.net/bugs/568738 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 568738] Re: Could not boot into Ubuntu 10.04 release candidate
Did as asked but this is what I got: de...@derek-desktop:~$ apport-collect BUGNUMBER Usage: apport-collect apport-collect: error: You need to specify a report number to update de...@derek-desktop:~$ > Date: Sat, 24 Apr 2010 12:12:01 + > From: br...@bryceharrington.org > To: milleniumy2k...@hotmail.com > Subject: [Bug 568738] Re: Could not boot into Ubuntu 10.04 release candidate > > Hi Derek, > > > Please run the command 'apport-collect BUGNUMBER', which will attach several > files we need for debugging. > > [This is an automated message. Apologies if it has reached you > inappropriately; please just reply to this message indicating so.] > > > ** Tags added: needs-xorglog > > ** Tags added: needs-lspci-vvnn > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > -- > Could not boot into Ubuntu 10.04 release candidate > https://bugs.launchpad.net/bugs/568738 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in NULL Project: Invalid > Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete > > Bug description: > I did a clean install of Ubuntu 10.04 release candidate from a CD image. > Install worked fine but now it will not boot Ubuntu. All I got was a blank > screen that kept attempting to come up with an image. I kept getting repeat > messages that my monitor is going to sleep (standby mode). I asked a friend > who is in the Ubuntu community if he could help me. He sent me a link to the > alternate CD image site. I tried downloading and installing but got the same > result. Then I tried his other suggestion, which was to boot the live CD, get > information from terminal using the "lspci" command, copy the information and > submit a bug report. When I went to make the bug report, another problem > occurred. I clicked on the log in / register link and then I was disconnected > from the wireless network. I waited for it to reconnect online, instead got a > message asking me for the network passcode, which was filled correctly to > begin with. I just hit enter to try again and it gave me the same message. > Rebooted live CD, went through the steps with terminal but could not get back > online no matter how many times I tried to get back on. > > Below is the information I got from terminal after reinstalling 9.10: > > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. > > de...@derek-desktop:~$ lspci > 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM > Controller (rev 02) > 00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express > Root Port (rev 02) > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #4 (rev 02) > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #5 (rev 02) > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #2 (rev 02) > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio > Controller (rev 02) > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 > (rev 02) > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 > (rev 02) > 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 > (rev 02) > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #1 (rev 02) > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #2 (rev 02) > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #3 (rev 02) > 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #6 (rev 02) > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #1 (rev 02) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) > 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface > Controller (rev 02) > 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port > SATA AHCI Controller (rev 02) > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev > 02) > 01:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax > Modem > 01:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70) > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B > PCI Express Gigabit Ethernet controller (rev 02) > 03:00.0 Multimedia video controller: Conexant Systems, Inc. Hauppauge Inc. > HDPVR-1250 model 1196 (rev 0f) > 04
[Ubuntu-x-swat] [Bug 569271] Re: [RS780 KMS] no poweroff on halt with KMS enabled
I was able to come up with workaround of sorts. After doing some research, I figured out how to manually unload the radeon module, and created an script to do that (attached) which I placed in init.d and, after running update-rc.d, I got to work... sort of. Apparently it only works properly when I am in single-user (recovery) mode (it did not work here before though). The problem is that in normal mode it apparently uses upstart for everything, and I haven't been able to find out how to run the script properly via upstart. ** Attachment added: "script to manually unload radeon module" http://launchpadlibrarian.net/45460746/uloadradeon -- [RS780 KMS] no poweroff on halt with KMS enabled https://bugs.launchpad.net/bugs/569271 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 568738] Re: Could not boot into Ubuntu 10.04 release candidate
Hello guys. Sorry if I have not responded lately. I have been busy with some other things. Thank you Philip and Bryce for your assistance. I should be back again this evening or first thing tomorrow morning. -- Could not boot into Ubuntu 10.04 release candidate https://bugs.launchpad.net/bugs/568738 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 569271] Re: [RS780 KMS]no poweroff on halt with KMS enabled
** Summary changed: - no poweroff on halt with KMS enabled (Radeon HD3200) + [RS780 KMS]no poweroff on halt with KMS enabled ** Description changed: Binary package hint: xserver-xorg-video-ati - I have an HP tx2500z laptop, which has a Radeon HD 3200 card, and I am - using the free driver. By default, the kernel (2.6.32-21-generic) seems - to have KMS enabled, and as a result when I shutdown the machine (via - halt or shutdown -hP or otherwise) it never powers off, just continues - to show the Plymouth shutdown splash, though all HDD activity has - ceased. When I add "radeon.modeset=0" to my grub command line, disabling - KMS, I am able to shutdown just fine. + I have an HP tx2500z laptop, which has a Radeon HD 3200 (RS780) card, + and I am using the free driver. By default, the kernel + (2.6.32-21-generic) seems to have KMS enabled, and as a result when I + shutdown the machine (via halt or shutdown -hP or otherwise) it never + powers off, just continues to show the Plymouth shutdown splash, though + all HDD activity has ceased. When I add "radeon.modeset=0" to my grub + command line, disabling KMS, I am able to shutdown just fine. I tried adding "modprobe -r radeon" to /etc/init.d/halt but when shutting down it prints a message that the module radeon is still in use, so it seems that when KMS is enabled it can't remove the module and hence is unable to poweroff. The problem still exists if I rename my xorg.conf. I also tried using newer kernels from the ubuntu kernel PPA (such as 2.6.33-02063302-generic and 2.6.34-020634rc5-generic) but the problem persisted. The problem exists even for a fresh installation. Obviously disabling KMS is a workable fix, but I would prefer to have it enabled if not for this. Package version: 1:6.13.0-1ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-radeon 1:6.13.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Fri Apr 23 19:02:21 2010 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.32-21-generic, i686: installed EcryptfsInUse: Yes InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419) MachineType: Hewlett-Packard HP Pavilion tx2500 Notebook PC ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=UUID=cf7b0aba-0857-4e6e-8790-ade683c2aba5 ro radeon.modeset=0 quiet splash ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/zsh + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/zsh SourcePackage: xserver-xorg-video-ati dmi.bios.date: 08/18/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F1 dmi.board.vendor: Quanta dmi.board.version: 97.22 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0F:bd08/18/2009:svnHewlett-Packard:pnHPPaviliontx2500NotebookPC:pvrRev1:rvnQuanta:rn30F1:rvr97.22:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion tx2500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard system: - distro: Ubuntu - codename: lucid - architecture: i686 - kernel: 2.6.32-21-generic + distro: Ubuntu + codename: lucid + architecture: i686 + kernel: 2.6.32-21-generic ** Summary changed: - [RS780 KMS]no poweroff on halt with KMS enabled + [RS780 KMS] no poweroff on halt with KMS enabled -- [RS780 KMS] no poweroff on halt with KMS enabled https://bugs.launchpad.net/bugs/569271 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 569271] Re: no poweroff on halt with KMS enabled (Radeon HD3200)
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/45138200/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/45138201/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/45138202/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/45138203/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/45138204/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/45138205/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/45138206/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/45138207/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/45138208/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/45138209/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/45138210/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/45138211/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/45138212/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/45138213/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/45138214/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/45138215/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/45138216/glxinfo.txt ** Attachment added: "make.log.txt" http://launchpadlibrarian.net/45138217/make.log.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/45138218/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/45138219/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/45138220/xkbcomp.txt -- no poweroff on halt with KMS enabled (Radeon HD3200) https://bugs.launchpad.net/bugs/569271 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 569271] [NEW] no poweroff on halt with KMS enabled (Radeon HD3200)
Public bug reported: Binary package hint: xserver-xorg-video-ati I have an HP tx2500z laptop, which has a Radeon HD 3200 card, and I am using the free driver. By default, the kernel (2.6.32-21-generic) seems to have KMS enabled, and as a result when I shutdown the machine (via halt or shutdown -hP or otherwise) it never powers off, just continues to show the Plymouth shutdown splash, though all HDD activity has ceased. When I add "radeon.modeset=0" to my grub command line, disabling KMS, I am able to shutdown just fine. I tried adding "modprobe -r radeon" to /etc/init.d/halt but when shutting down it prints a message that the module radeon is still in use, so it seems that when KMS is enabled it can't remove the module and hence is unable to poweroff. The problem still exists if I rename my xorg.conf. I also tried using newer kernels from the ubuntu kernel PPA (such as 2.6.33-02063302-generic and 2.6.34-020634rc5-generic) but the problem persisted. The problem exists even for a fresh installation. Obviously disabling KMS is a workable fix, but I would prefer to have it enabled if not for this. Package version: 1:6.13.0-1ubuntu5 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-radeon 1:6.13.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Fri Apr 23 19:02:21 2010 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.32-21-generic, i686: installed EcryptfsInUse: Yes InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419) MachineType: Hewlett-Packard HP Pavilion tx2500 Notebook PC ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=UUID=cf7b0aba-0857-4e6e-8790-ade683c2aba5 ro radeon.modeset=0 quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: xserver-xorg-video-ati dmi.bios.date: 08/18/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F1 dmi.board.vendor: Quanta dmi.board.version: 97.22 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0F:bd08/18/2009:svnHewlett-Packard:pnHPPaviliontx2500NotebookPC:pvrRev1:rvnQuanta:rn30F1:rvr97.22:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion tx2500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug halt i386 kms lucid radeon -- no poweroff on halt with KMS enabled (Radeon HD3200) https://bugs.launchpad.net/bugs/569271 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 558923] Re: binaries installed by fglrx-amdcccle not added to PATH
seems to have been fixed with a recent update (package version is now 2:8.721-0ubuntu10 ). -- binaries installed by fglrx-amdcccle not added to PATH https://bugs.launchpad.net/bugs/558923 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 558923] Re: binaries installed by fglrx-amdcccle not added to PATH
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/43500336/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/43500337/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/43500338/Dependencies.txt ** Attachment added: "DkmsStatus.txt" http://launchpadlibrarian.net/43500339/DkmsStatus.txt ** Attachment added: "GdmLog.txt" http://launchpadlibrarian.net/43500340/GdmLog.txt ** Attachment added: "GdmLog1.txt" http://launchpadlibrarian.net/43500341/GdmLog1.txt ** Attachment added: "GdmLog2.txt" http://launchpadlibrarian.net/43500342/GdmLog2.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/43500343/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/43500344/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/43500345/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/43500346/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/43500347/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/43500348/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/43500349/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/43500350/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/43500351/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/43500352/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/43500353/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/43500354/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/43500355/Xrandr.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/43500356/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/43500357/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/43500358/xkbcomp.txt -- binaries installed by fglrx-amdcccle not added to PATH https://bugs.launchpad.net/bugs/558923 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 558923] [NEW] binaries installed by fglrx-amdcccle not added to PATH
Public bug reported: Binary package hint: fglrx-amdcccle according to Synaptic "view installed files" for package "amdcccle" the binaries (amdcccle, amdupdaterandrconfig, and amdxdg-su) were installed to "/usr/lib/fglrx/bin". This is not in $PATH, and no symlinks were created to directories that were. Additionally, the .desktop files were created in /usr/share/fglrx and hence are not detected either. No man entries are present for the binaries either. I am not sure if this is because I am using XFCE, or something specific about my system. I did try reinstalling the package, to no effect. 1)Description: Ubuntu lucid (development branch) Release: 10.04 2) fglrx-amdcccle 2:8.721-0ubuntu7 3) expected binaries to be added to PATH, or symlinks to the binaries created, man pages for the binaries to be created, and the .desktop files to be created in /usr/share/applications or somewhere else the system expects .desktop files 4) binaries installed in /usr/lib/fglrx/bin, not added to PATH and no symlinks created. .desktop files created in /usr/share/fglrx/, which was not detected by the system (no entries added to the menu nor appearing in application search). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: fglrx-amdcccle 2:8.721-0ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx wl Architecture: i386 Date: Thu Apr 8 19:51:02 2010 InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3) MachineType: Hewlett-Packard HP Pavilion tx2500 Notebook PC ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic root=UUID=46208bdf-f8cb-442a-b80b-ddf354381738 ro usbcore.autosuspend=1 crashkernel=384M-2G:64M,2G-:128M quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: fglrx-installer dmi.bios.date: 08/18/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F1 dmi.board.vendor: Quanta dmi.board.version: 97.22 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0F:bd08/18/2009:svnHewlett-Packard:pnHPPaviliontx2500NotebookPC:pvrRev1:rvnQuanta:rn30F1:rvr97.22:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion tx2500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-19-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amdcccle apport-bug flgrx i386 lucid -- binaries installed by fglrx-amdcccle not added to PATH https://bugs.launchpad.net/bugs/558923 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 469870] Re: S-video is missing entirely on xrandr report - unable to use S-video
I implied it, but I forgot to actually say that, for me, this is a regression from Jaunty's radeon driver. -- S-video is missing entirely on xrandr report - unable to use S-video https://bugs.launchpad.net/bugs/469870 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 469870] Re: S-video is missing entirely on xrandr report - unable to use S-video
** Attachment added: "S-video isn't even mentioned in the X log!" http://launchpadlibrarian.net/34916687/Xorg.0.log -- S-video is missing entirely on xrandr report - unable to use S-video https://bugs.launchpad.net/bugs/469870 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 469870] [NEW] S-video is missing entirely on xrandr report - unable to use S-video
Public bug reported: Binary package hint: xserver-xorg-video-ati Recent install of Karmic. Have 'options radeon modeset=1' in a file under the /etc/modprobe.d directory to enable KMS. I have had no problems with compiz/glxgears/Xv - everything works perfectly (no crashes/artifacts/problems of any kind) & "graphics/video stay inside their windows". Prior to Karmic I had a tv-out script to enable my S-Video output & move the Xv output to it using xrandr/xvattr; however, in karmic xrandr does not recognize that there is an S-video connection on my card (Radeon 9550 RV350). $ xrandr Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm x 255mm 1440x900 59.9*+ 1280x1024 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60075.0 60.3 56.2 640x48075.0 60.0 720x40070.1 0x0 0.0 Previously, there would have been an entry similar to "S-video disconnected (normal left inverted right x axis y axis)" after the DVI-0 listings. This is now gone. Even forcing the connection gives an error: $ xrandr --output S-video --set load_detection 1 X Error of failed request: BadRROutput (invalid Output parameter) Major opcode of failed request: 149 (RANDR) Minor opcode of failed request: 15 (RRGetOutputProperty) Serial number of failed request: 24 Current serial number in output stream: 24 I am using all default configurations (xorg.conf doesn't exist), except for the KMS switch being set to on. Attachment: Xorg.0.log - Sorry it's so big, I did a few VT switches and it likes to re-log all the EDID data each time... ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- S-video is missing entirely on xrandr report - unable to use S-video https://bugs.launchpad.net/bugs/469870 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] Re: glxgears randomly reports vertical sync, but isn't sync'd
Using the Alpha 5 Live CD, I could not reproduce this issue. Compiz was on (by default). I could not test it with radeon.modeset=1, as that resulted in a non-booting system. The false sync reporting issue appears to have been fixed. However, in 9.04 when I exit glxgears using the window manager's X button I get the following: XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after * requests (* known processed) with 0 events remaining. In the Alpha 5 Live CD, I get the following using the same exit method: XIO: fatal IO error 11 (Resource temporarily unavailabe) on X server ":0.0" after * requests (* known processed) with 0 events remaining. [In both cases, * is a number based on how long glxgears was running.] Exiting with the Esc key, reports no errors. -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 96991] Re: (Needs radeon-rewrite) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI
Using the Alpha 5 Live CD, I pressed F6 to edit the options and added radeon.modeset=1 just before the 'quiet splash -- ' parameters. Once the boot process started, the screen said something like "unknown boot option, ignoring" in reference to the modeset option. Boot process continued normally, until after the boot splash went away (prior to gdm starting): my screen went into power saving mode and the computer did nothing. Ctrl-Alt-Del had no effect and I had to hard reset the system. I am using an ATI Radeon 9550 (RV350) 256MB graphics card (manufactured by ATI) on a Biostar M7NCD motherboard with an nVidia nForce2 400 + MCP chipset. If there is any further testing/debugging I can do from the Live CD, please let me know. -- (Needs radeon-rewrite) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI https://bugs.launchpad.net/bugs/96991 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] Re: glxgears randomly reports vertical sync, but isn't sync'd
I'll get on it. I have a few programs to test on Karmic Alpha 4. -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 96991] Re: (Needs UXA/DRI2) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI
I also agree with: Oliver Mattos' postings from 2008-04-27 and 2008-07-18; Vytas' post from 2008-10-03 "...enabling obviously crippled software does more harm than good..." - just look at the dups; & David Fokkema's post on 2008-10-05. Compiz should not be enabled by default with ati driver until this is fixed. Having a default not work properly when simply disabling the Visual Effects setting makes it work is annoying to users. Disabling it by default could prevent the user from being disappointed/annoyed. Then, when they activate it, it's their own fault for messing with things. Isn't that the Linux way? ;) -- (Needs UXA/DRI2) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI https://bugs.launchpad.net/bugs/96991 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 96991] Re: (Needs UXA/DRI2) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI
Regarding ati/radeon and the video not moving with the window when compiz is used, I have a workaround: [I am using medibuntu's mplayer, I assume it will work with the normal one too. My xorg.conf is blank.] Open video in mplayer, let it play, & stop the video - leave mplayer open. Open video in a new instance of mplayer: the video stays in its window when moved, all compiz effects (Alt-Tab, wobble, cube, etc.) work with the video staying inside its window. The original mplayer instance can be closed at any time after the second has started. [This might work in totem as well, but I do not know how to open multiple instances of totem.] Once all instances of mplayer are closed, you have to re-do the workaround for it to work again. -- (Needs UXA/DRI2) 3D stuff breaks with Compiz: Redirected Direct Rendering is needed in DRI https://bugs.launchpad.net/bugs/96991 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 384333] Re: [i915gm] Xorg infinite loop, backtrace thru synaptics driver
I've upgraded to Karmic Alpha-2, as requested. The bug still crops up intermittently, where an application (especially Eclipse) will hang when I'm interacting with the GUI using the mouse. Contrary to my earlier report, it doesn't seem to be specific to Synaptics, as I've reproduced the bug while using an external mouse only. On the most recent hang, I sshed into the hung machine as before, and looked at the Xorg.0.log. Unfortunately, it did not contain a backtrace as it did before. Before I could do much more investigating, the machine locked up -- my ssh session hung, and further attempts to start a new session failed. I was still able to reboot the machine with CTRL-ALT- SYSRQ-S-U-B. Attached is the Xorg.0.log from the hung session, although it doesn't appear to have been modified since the preceding boot (or maybe the preceding wake from suspend). ** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/28667828/Xorg.0.log.old -- [i915gm] Xorg infinite loop, backtrace thru synaptics driver https://bugs.launchpad.net/bugs/384333 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 59417] Re: Scroll lock does not work in X
I can confirm all problem-related comments in Jaunty. xev shows the button press, mod3 is blank, "xmodmap -e 'add mod3 = Scroll_Lock'" works for current session. I have not applied it to .Xmodmap/.xmodmap yet, as there are conflicting results as to where to put it and whether it works. If it's related, see Bug 393285. Keyboard: Saitek Eclipse Model # KU-0418, Assembly # KU-0573. -- Scroll lock does not work in X https://bugs.launchpad.net/bugs/59417 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 384333] Re: [i915gm] Xorg infinite loop, backtrace thru synaptics driver
I've been at a conference for the last week and had to have a stable system, so I switched temporarily to metacity. I can say that the bug doesn't seem to manifest itself in this case -- I've only seen it with compiz enabled. I've just re-enabled compiz and followed the first few steps that Geir suggested for catching the full backtrace. I'll update when I have one. -- [i915gm] Xorg infinite loop, backtrace thru synaptics driver https://bugs.launchpad.net/bugs/384333 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 384333] Re: Xorg infinite loop, backtrace thru synaptics driver
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27589267/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/27589268/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/27589269/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/27589270/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/27589271/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/27589272/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/27589273/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/27589274/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/27589275/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/27589276/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/27589277/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/27589278/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/27589279/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/27589280/xkbcomp.txt -- Xorg infinite loop, backtrace thru synaptics driver https://bugs.launchpad.net/bugs/384333 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 384333] [NEW] Xorg infinite loop, backtrace thru synaptics driver
Public bug reported: Binary package hint: xorg Since the upgrade from Intrepid to Jaunty, X will hang randomly. It has happened in Firefox (while scrolling a webpage with the touchpad), OpenOffice (moving mouse and clicking an icon), and Eclipse several times while interacting with UI elements using the mouse pointer. When X hangs, the mouse moves but no UI elements respond. I am not able to switch virtual terminals, and CTRL-ALT-BKSP and CTRL-ALT-DEL do not respond, but CTRL-ALT-PRTSC-S-U-B is able to restart the machine. On the most recent hang, I found that I was able to SSH into the machine. The Xorg.log indicated a likely infinite loop, with the following backtrace: [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b] 1: /usr/X11R6/bin/X(mieqEnqueue+0x2d9) [0x8114c89] 2: /usr/X11R6/bin/X(xf86PostButtonEvent+0x105) [0x80d8405] 3: /usr/lib/xorg/modules/input//synaptics_drv.so [0xa6ac1729] 4: /usr/lib/xorg/modules/input//synaptics_drv.so [0xa6ac3bf9] 5: /usr/X11R6/bin/X [0x80c7da7] 6: /usr/X11R6/bin/X [0x80b82cc] 7: [0xb8016400] 8: /usr/lib/libdrm.so.2(drmCommandNone+0x32) [0xb7924ee2] 9: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb78bb68f] 10: /usr/X11R6/bin/X [0x817d1cb] 11: /usr/X11R6/bin/X [0x8145f88] 12: /usr/X11R6/bin/X [0x80f8b98] 13: /usr/X11R6/bin/X(BlockHandler+0x58) [0x80911c8] 14: /usr/X11R6/bin/X(WaitForSomething+0x124) [0x8132974] 15: /usr/X11R6/bin/X(Dispatch+0x7e) [0x808d2be] 16: /usr/X11R6/bin/X(main+0x3bd) [0x80722ed] 17: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7be2775] 18: /usr/X11R6/bin/X [0x80717a1] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [...repeats a few dozen times...] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnqueue: more than six valuator events; dropping. [...these two repeat in alternation until the machine is rebooted...] I suspect the synaptics driver, since each hang involves interacting with UI elements using the mouse, immediately before the crash. I honestly can't say whether all these crashes happened while using the *touchpad* as opposed to a USB mouse, but the most recent one was the touchpad, and it's entirely possible that all the hangs I've experienced were during touchpad use. Lots of information should be attached via the ubuntu-bug tool -- please let me know if there's anything else I can add. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-12-generic (bui...@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-12-generic i686 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Xorg infinite loop, backtrace thru synaptics driver https://bugs.launchpad.net/bugs/384333 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] Re: glxgears randomly reports vertical sync, but isn't sync'd
Got more weird results today: de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately 1/4 the monitor refresh rate. 7636 frames in 5.0 seconds = 1527.029 FPS 7814 frames in 5.0 seconds = 1562.751 FPS 7776 frames in 5.0 seconds = 1555.102 FPS de...@dereksbox:~$ glxgears -sync Usage: -display set the display to run on -stereo run in stereo mode -fullscreen run in fullscreen mode -info display OpenGL renderer info -geometry WxH+X+Y window geometry de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 7732 frames in 5.0 seconds = 1546.356 FPS 7817 frames in 5.0 seconds = 1563.353 FPS 7461 frames in 5.0 seconds = 1492.181 FPS 1/4 the monitor refresh rate now! -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 290704] Re: [fglrx]Computer freeze when switching user
Similar problem when using ATI driver, version 9.5 and Radeon 2600HD. Compiz is enabled. $ lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600XT] Computer blanks out the screen and freezes. I cannot connect via SSH even. On a related note, can anyone recommend a good nvidia card for Linux with full 3D support? :-) -- [fglrx]Computer freeze when switching user https://bugs.launchpad.net/bugs/290704 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] [NEW] glxgears randomly reports vertical sync, but isn't sync'd
Public bug reported: This just started out of nowhere, very weird... ** de...@dereksbox:~$ date Tue Jun 2 01:31:08 EDT 2009 de...@dereksbox:~$ cat /etc/X11/xorg.conf de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. de...@dereksbox:~$ glxgears 7438 frames in 5.0 seconds = 1487.485 FPS de...@dereksbox:~$ cat /etc/X11/xorg.conf de...@dereksbox:~$ date Tue Jun 2 01:31:28 EDT 2009 de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 7549 frames in 5.0 seconds = 1509.673 FPS 7578 frames in 5.0 seconds = 1515.598 FPS 7662 frames in 5.0 seconds = 1532.291 FPS de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 7511 frames in 5.0 seconds = 1502.188 FPS 7611 frames in 5.0 seconds = 1522.030 FPS de...@dereksbox:~$ ubuntu-bug Usage: /usr/bin/ubuntu-bug |||<.crash file> de...@dereksbox:~$ whereis glxgears glxgears: /usr/bin/glxgears /usr/share/man/man1/glxgears.1.gz de...@dereksbox:~$ ubuntu-bug /usr/bin/glxgears de...@dereksbox:~$ date Tue Jun 2 01:37:19 EDT 2009 de...@dereksbox:~$ glxgears 7510 frames in 5.0 seconds = 1501.818 FPS 6711 frames in 5.0 seconds = 1342.109 FPS de...@dereksbox:~$ glxgears 7470 frames in 5.0 seconds = 1493.899 FPS de...@dereksbox:~$ glxgears de...@dereksbox:~$ glxgears de...@dereksbox:~$ glxgears 7697 frames in 5.0 seconds = 1539.268 FPS ** Seemingly goes away...Then, I do a '$ clear' ** de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 6963 frames in 5.0 seconds = 1392.431 FPS 7610 frames in 5.0 seconds = 1521.945 FPS de...@dereksbox:~$ date Tue Jun 2 01:38:54 EDT 2009 de...@dereksbox:~$ glxgears 7499 frames in 5.0 seconds = 1499.638 FPS de...@dereksbox:~$ glxgears 7439 frames in 5.0 seconds = 1487.707 FPS 7663 frames in 5.0 seconds = 1532.571 FPS ** And, it came back for a while. ** de...@dereksbox:~$ glxgears 7431 frames in 5.0 seconds = 1486.017 FPS de...@dereksbox:~$ glxgears de...@dereksbox:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. de...@dereksbox:~$ date Tue Jun 2 01:42:03 EDT 2009 ** Above, I canceled the second run very quickly, hit the up arrow>enter to re-run it very quickly, and it came back... This is just weird. As you can see from my first excerpt, my xorg.conf is empty. My refresh rate is obviously not 1500+Hz, it's the default for my DVI monitor, 60Hz. Reproducibility? Not sure how I reproduced it, just did it a bunch and the warning comes up occasionally. Good luck with this one, -Derek PS - Second bug(?) - Firefox seems to think 'framerate' is not a correct word... :) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: mesa-utils 7.4-0ubuntu3.1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 SourcePackage: mesa Uname: Linux 2.6.28-11-generic i686 XorgConf: ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 382636] Re: glxgears randomly reports vertical sync, but isn't sync'd
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27397286/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/27397287/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/27397288/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/27397289/LsPci.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/27397290/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/27397291/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/27397292/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/27397293/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/27397294/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/27397295/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/27397296/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/27397297/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/27397298/xkbcomp.txt -- glxgears randomly reports vertical sync, but isn't sync'd https://bugs.launchpad.net/bugs/382636 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
