[Ubuntu-x-swat] [Bug 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Okay, I'm in. I replace the window manager installing compiz and now I can login with nvidia 304. Steps: - Install compiz - Add "compiz --replace" to autostart - Install nvidia-304 - Reboot Result: In first login, I have a loop and in the second time that I enter password, I am enable to login. Notes: This confirms that is an incompatibility with budgie window manager and nvidia 304. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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
Re: [Ubuntu-x-swat] [Bug 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
I suspect you will have the same issue with gnome-shell. budgie and gnome-shell use the same window manager. On 25 March 2017 at 18:04, Diogo Gomes <1675...@bugs.launchpad.net> wrote: > Yes, I know. > > This GPU driver works well in Ubuntu, Ubuntu Mate, etc. > > Only not works in Budgie. > > I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE > neither, only in Mate DE. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1675830 > > Title: > nvidia 304 graphics causes Login loop in Ubuntu Budgie > > Status in Ubuntu Budgie: > New > Status in nvidia-graphics-drivers-304 package in Ubuntu: > New > > Bug description: > Nvidia 304 graphics kills budgie-window manager process and causes > login loop in Ubuntu Budgie. > > Steps: > - Enter password > - System shows top bar (half cropped) > - Sometimes dock appears > - Screen goes off (with no signal in monitor) > - Screen shows login screen again > > System description: > - OS: Ubuntu Budgie 17.04 (daily build) > - GPU: Nvidia GeForce 6150SE nForce 430 > > Packages: > - Budgie Desktop 10.2.9 > - Nvidia Graphics Drivers 304 > > Notes: > The system it's updated (full-upgrade) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+subscriptions -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Yes, I know. This GPU driver works well in Ubuntu, Ubuntu Mate, etc. Only not works in Budgie. I test install Budgie DE in Ubuntu Mate and I can't login in Bugdie DE neither, only in Mate DE. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1676079] Re: fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build
** Tags removed: need-duplicate-check -- 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/1676079 Title: fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1676079/+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 1676079] [NEW] fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build
Public bug reported: user@machine:~$ sudo apt-get install -y fglrx fglrx-core fglrx-amdcccle fglrx-dev ... Configurando fglrx-core (2:15.201.2-0ubuntu0.14.04.1) ... update-alternatives: a usar /usr/lib/fglrx-core/ld.so.conf para disponibilizar /etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) em modo automático Loading new fglrx-core-15.201.2 DKMS files... First Installation: checking all kernels... Building only for 4.4.0-66-generic Building for architecture x86_64 Building initial module for 4.4.0-66-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/fglrx-core.0.crash' Error! Bad return status for module build on kernel: 4.4.0-66-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.201.2/build/make.log for more information. update-initramfs: deferring update (trigger activated) A processar 'triggers' para initramfs-tools (0.103ubuntu4.6) ... update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic A processar 'triggers' para libc-bin (2.19-0ubuntu6.11) ... A seleccionar pacote anteriormente não seleccionado fglrx. ... user@machine:~$ cat /var/lib/dkms/fglrx-core/15.201.2/build/make.log DKMS make.log for fglrx-core-15.201.2 for kernel 4.4.0-66-generic (x86_64) Sáb Mar 25 14:34:03 BRT 2017 /usr/sbin/dkms: linha 73: cd: /var/lib/dkms/fglrx/15.201.2/build: Arquivo ou diretório não encontrado AMD kernel module generator version 2.1 doing Makefile based build for kernel 2.6.x and higher rm -rf *.c *.h *.o *.ko *.a .??* *.symvers make -C /lib/modules/4.4.0-66-generic/build SUBDIRS=/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x modules make[1]: Entrando no diretório `/usr/src/linux-headers-4.4.0-66-generic' CC [M] /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘firegl_major_proc_read’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be len = seq_printf(m, "%d\n", major); ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function ‘KCL_fpu_save_init’: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: error: ‘XSTATE_FP’ undeclared (first use in this function) if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP)) ^ /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: At top level: /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6498:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ make[2]: ** [/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o] Erro 1 make[1]: ** [_module_/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x] Erro 2 make[1]: Saindo do diretório `/usr/src/linux-headers-4.4.0-66-generic' make: ** [kmod_build] Erro 2 build failed with return value 2 user@machine:~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty user@machine:~$ uname -a Linux machine 4.4.0-66-generic #87~14.04.1-Ubuntu SMP Fri Mar 3 17:32:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-core 2:15.201.2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-66-generic Date: Sat Mar 25 12:46:41 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201.2: added Error! Could not locate dkms.conf file. File: does not exist. DuplicateSignature: dkms:fglrx-core:2:15.201.2-0ubuntu0.14.04.1:/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0640] InstallationDate: Installed on 2014-08-18 (950 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 5547 PackageVersion: 2:15.201.2-0ubuntu0.14.04.1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
[Ubuntu-x-swat] [Bug 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Okay, I was hoping that I'd be able to suggest, as a simple fix, trying a newer driver. But I see that v304 is, indeed, the most recent Linux driver available for your GPU. http://www.nvidia.com/Download/Find.aspx?lang=en-us -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
** Description changed: - After enter password, it starts appearing top bar, dock and then the - screen goes off followed by login screen. + Nvidia 304 graphics kills budgie-window manager process and causes login + loop in Ubuntu Budgie. + + Steps: + - Enter password + - System shows top bar (half cropped) + - Sometimes dock appears + - Screen goes off (with no signal in monitor) + - Screen shows login screen again + + + System description: + - OS: Ubuntu Budgie 17.04 (daily build) + - GPU: Nvidia GeForce 6150SE nForce 430 + + + Packages: + - Budgie Desktop 10.2.9 + - Nvidia Graphics Drivers 304 + + + Notes: The system it's updated (full-upgrade) - - Ubuntu Budgie 17.04 (daily build) - Budgie Desktop 10.2.9 ** Description changed: Nvidia 304 graphics kills budgie-window manager process and causes login loop in Ubuntu Budgie. - Steps: - Enter password - System shows top bar (half cropped) - Sometimes dock appears - Screen goes off (with no signal in monitor) - Screen shows login screen again - System description: - OS: Ubuntu Budgie 17.04 (daily build) - GPU: Nvidia GeForce 6150SE nForce 430 - Packages: - Budgie Desktop 10.2.9 - Nvidia Graphics Drivers 304 - Notes: The system it's updated (full-upgrade) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
My GPU is Nvidia GeForce 6150SE nForce 430 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1551022] Re: mouse pointer leaves trail
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on a Intel J3160 processor. Connection is dual monitor VGA + HDMI What do you need qua logging or actions to solve this issue? ** Attachment added: "Mouse Pointer Trails" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+attachment/4845654/+files/MousePointerTrails.png -- 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/1551022 Title: mouse pointer leaves trail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
Sorry if I missed this in your bug report, but what model Nvidia GPU are you testing? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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 1671799] Re: FFe: xserver 1.19.3
Ot to FFe Bug filed regarding PRIME synchronization with hybrid hardware implemented via nvidia-prime Bug 1674304 -- 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/1671799 Title: FFe: xserver 1.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799/+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 1675830] Re: nvidia 304 graphics causes Login loop in Ubuntu Budgie
I would recommend you try this staging PPA - https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging it brings the latest X stack - if it resolves your issues please report that fact here on the bug report tracking the request to bring this X stack to zesty: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1675830 Title: nvidia 304 graphics causes Login loop in Ubuntu Budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1675830/+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] [Build #12352508] i386 build of mesa 17.0.2-1ubuntu1~16.04~0.1 in ubuntu xenial RELEASE [~ubuntu-x-swat/ubuntu/x-staging]
* Source Package: mesa * Version: 17.0.2-1ubuntu1~16.04~0.1 * Architecture: i386 * Archive: ~ubuntu-x-swat/ubuntu/x-staging * Component: main * State: Failed to build * Duration: 13 minutes * Build Log: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12352508/+files/buildlog_ubuntu-xenial-i386.mesa_17.0.2-1ubuntu1~16.04~0.1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lgw01-49 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of mesa 17.0.2-1ubuntu1~16.04~0.1 in ubuntu xenial RELEASE https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12352508 You are receiving this email because your team Ubuntu-X is the owner of this archive. ___ 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] [Build #12352505] amd64 build of mesa 17.0.2-1ubuntu1~16.04~0.1 in ubuntu xenial RELEASE [~ubuntu-x-swat/ubuntu/x-staging]
* Source Package: mesa * Version: 17.0.2-1ubuntu1~16.04~0.1 * Architecture: amd64 * Archive: ~ubuntu-x-swat/ubuntu/x-staging * Component: main * State: Failed to build * Duration: 10 minutes * Build Log: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12352505/+files/buildlog_ubuntu-xenial-amd64.mesa_17.0.2-1ubuntu1~16.04~0.1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lgw01-02 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of mesa 17.0.2-1ubuntu1~16.04~0.1 in ubuntu xenial RELEASE https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12352505 You are receiving this email because your team Ubuntu-X is the owner of this archive. ___ 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] [Build #12357920] i386 build of wayland 1.12.0-1~16.04~0.1 in ubuntu xenial RELEASE [~ubuntu-x-swat/ubuntu/x-staging]
* Source Package: wayland * Version: 1.12.0-1~16.04~0.1 * Architecture: i386 * Archive: ~ubuntu-x-swat/ubuntu/x-staging * Component: main * State: Failed to build * Duration: 2 minutes * Build Log: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12357920/+files/buildlog_ubuntu-xenial-i386.wayland_1.12.0-1~16.04~0.1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lgw01-04 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of wayland 1.12.0-1~16.04~0.1 in ubuntu xenial RELEASE https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12357920 You are receiving this email because your team Ubuntu-X is the owner of this archive. ___ 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] [Build #12357917] amd64 build of wayland 1.12.0-1~16.04~0.1 in ubuntu xenial RELEASE [~ubuntu-x-swat/ubuntu/x-staging]
* Source Package: wayland * Version: 1.12.0-1~16.04~0.1 * Architecture: amd64 * Archive: ~ubuntu-x-swat/ubuntu/x-staging * Component: main * State: Failed to build * Duration: 2 minutes * Build Log: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12357917/+files/buildlog_ubuntu-xenial-amd64.wayland_1.12.0-1~16.04~0.1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lcy01-25 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of wayland 1.12.0-1~16.04~0.1 in ubuntu xenial RELEASE https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/x-staging/+build/12357917 You are receiving this email because your team Ubuntu-X is the owner of this archive. ___ 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 1676019] [NEW] Weston does not start from LightDM
Public bug reported: Mar 25 11:01:06 hostname systemd[1]: Started Session c12 of user alice. Mar 25 11:01:06 hostname kernel: [ 293.23] weston[5337]: segfault at 7efe9b93d820 ip 7efe9b93d820 sp 7ffc6d468518 error 14 in libXdmcp.so.6.0.0[7efe9c1d7000+5000] Weston works fine to manually run from console using 'weston-launch' though. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: weston 1.12.0-3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Sat Mar 25 11:04:41 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1184 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: weston UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 11:01:07 2017 xserver.configfile: default xserver.errors: Failed to load module "vesa" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu9 xserver.video_driver: modeset ** Affects: weston (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu zesty ** Description changed: Mar 25 11:01:06 hostname systemd[1]: Started Session c12 of user alice. Mar 25 11:01:06 hostname kernel: [ 293.23] weston[5337]: segfault at 7efe9b93d820 ip 7efe9b93d820 sp 7ffc6d468518 error 14 in libXdmcp.so.6.0.0[7efe9c1d7000+5000] + + Weston works fine to manually run from console using 'weston-launch' + though. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: weston 1.12.0-3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Sat Mar 25 11:04:41 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2013-12-26 (1184 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7 SourcePackage: weston UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M.
[Ubuntu-x-swat] [Bug 1676007] [NEW] package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error e
Public bug reported: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.handoff=7 SourcePackage: libxrandr Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RCK3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3450:pvr:rvnDellInc.:rn0RCK3X:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 09:44:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3~trusty1 ** Affects: libxrandr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1676007/+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 1676007] Re: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1676007/+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 1676002] [NEW] Xorg freeze
Public bug reported: The system freezes randomly since I installed Ubuntu 16.04. I think there's a problem with nvidia drivers. The graphic card is Nvidia GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used Ubuntu 12.04 without problems for almost 5 years with 173 Nvidia driver (which it's recommended), but it's not avaliable. Now when I try to use privete drivers the only avaliable driver is Nvidia 304.xx, but it causes a black screen at start the PC. I can use the terminal to uninstall the nvidia drivers and login, but then the system freezes very frecuently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 25 08:11:57 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C73 [GeForce 7050 / nForce 610i] [1043:82ae] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=5edf19ce-c17b-4661-bfff-4b32af86a9e4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N73-AM ACPI BIOS Revision 0201 dmi.board.name: P5N73-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N73-AMACPIBIOSRevision0201:bd06/11/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N73-AM:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 08:05:47 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu xenial -- 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/1676002 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676002/+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 :
[Ubuntu-x-swat] [Bug 1675364] Re: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running)
gnome-chess log. (if i manually launch gnome-chess with Xmir it works fine, same native, it only doesn't work if i launch from the launcher/app drawer) Mar 24 20:54:07 pixel-desktop gnome-chess[18994]: Ignoring unknown Mir event 11 Mar 24 20:54:07 pixel-desktop gnome-chess[18994]: Ignoring unknown Mir event 8 Mar 24 20:54:07 pixel-desktop xmir-helper[18986]: pasted: Qt: Session management error: Could not open network socket Mar 24 20:54:42 pixel-desktop xmir-helper[18986]: pasted: The X11 connection broke: I/O error (code 1) Mar 24 20:54:42 pixel-desktop xmir-helper[18986]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Mar 24 20:54:42 pixel-desktop xmir-helper[18986]: after 7 requests (6 known processed) with 0 events remaining. Mar 24 20:54:49 pixel-desktop gnome-chess[18994]: AT-SPI: Could not obtain desktop path or name -- 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/1675364 Title: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675364/+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 1675970] Re: various code running
*** This bug is a duplicate of bug 1675969 *** https://bugs.launchpad.net/bugs/1675969 ** This bug has been marked a duplicate of bug 1675969 various code running -- 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/1675970 Title: various code running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675970/+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
